Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Transfering Outgoing Calls Together

Status
Not open for further replies.

sdacm

IS-IT--Management
Apr 26, 2005
12
US
Is it possible in IP Office 2.1(27) to transfer 2 outgoing calls together? The only way we have been able to accomplish this is by "conferencing" the calls together and placing the call on hold. This is not ideal since it then ties up 1 of the agents 3 call appearance buttons. It is also a problem because we've noticed that sometimes when the 2 parties complete their conversation the call will sometimes not disconnect. Any suggestions would be greatly appreciated.
 
You cannot do that right now. It is possible in the 2.1.34 beta release but it may be gone in the general maintenance release wich is planned for the end of May.
 
try this:

create a conference Rendezvous for example with number 501 under a dss key.

call party 1 and xfer to that button;
call party 2 and xfer to that button;;
Both calls are then in a conference but at least you will be able to hang up without ending the conference call..

I use this all the time for operators how need to set up two outbound calls and connect them.
Works fine but you cannot see if the call is still active. The LED doesn't show that. When you press the dss key, you will be included again in the call..

Arnoud


 
When I raised this with Avaya they said that this type of operation was not allowed in the ISDN specifications so it was diliberatly blocked

If this is the case I cant see them changing it (or if they do they will probably treat it as a bug & "fix" it :-( )
 
I spoke to my telco rep about my problem and he emailed me with info regarding the following ISDN service:

2BCT - 2 B-Channel Transfer (aka TBCT, Call Transfer Disconnect)
Allows the ISDN PRI to connect two calls, transfer the call together and then release the parties from the ISDN PRI. Calls can be transferred outside of the system.
Billing for the original two calls continues in the same manner as if the transfer had not occurred and the controller of the transfer was still connected to both calls. Meaning, once the controller drops off and leaves the two calls connected, and if it’s a long distance call, the controller is still paying for that call.

If I purchase this service, do you think that the IP Office will allow outbound to outbound transfers?
 
No, the IPO will enable an inbound call to be transfered to an outbound call but it will not allow an outbound call to be transfered to an outbound call.

thsi is design intent by according to Avaya.
 
What in the ISDN specification caused Avaya to diliberatly block this feature? Is it a security related issue?
 
I have absolutltly no Idea, that is just what they told me.
if you require any more info you will have to place a call with them direct but I doubt it will get you anywhere :-(

(I am due to attend an upgrade coures at Avaya soon, I will try to mug someone whor knows while I am there)
 
Set up a three party conference, press hold and drop.
The two will stay in the conference.
 
This is b*llsh*t. If this against ISDN specifications why does it work on an Avaya Index and CM (Definity) ? They (Development) know it's a problem but as long nobody complains it's low priority.
 
It is worth mentioning that Definity, INDeX & IP Office developement teams are totaly sepperate.

Avaya say its not alowed, you say its B******t, I couldnt possibly comment ;-)
 
As i said before, it is possible in 2.1.34 and i think it will be permanent in future builds.
You do need the 2.1.34 manager to enable the feature, by default it is diabled.
 
It certainly isn't in the ITU ISDN standards. It may be in the national telecoms providers or regulators implementation of the standards.

Certainly in the early days of PRI in the UK, good old BT imposed lots of restrictions about what ISDN tricks they would allow (in order to protect there revenue stream and in order to charge you for a "service" - the service actually being a standard ISDN feature).
 
Is call manager build 2.1.34 part of IP Office 3.0?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top