Avaya IVR Call Transfer to External number Using Blind Tranfer.

[Laraib_karim]

I have made an IVR , And wan to tranfer to call to External number , I am using Blind transfer to transfer call to Mobile number. It has two strange behaviour , With sip phone with registered on Avaya SM, asking Auth code, and With H.323 phone when user dial IVR extension which is in AEP registered in SM , isgetting deisconnected . Same thing is working fine in vectory routing. Does any one have Idea , what need to do in cm or sm. IN trace it has 1166 denial event .

 

[ISDNman]

My educated guess is that it cannot be done on the majority of systems. The exceptions would be systems entirely created by non-phone savvy engineers (IT folks without background in telephone switching).

Keep in mind that in many ways Calling Line ID (AKA caller ID) is a logical extension of the pre-SS7 ANI (automatic number identification). ANI was intended to pass information to the long distance provider for billing purposes.

In your scenario the PBX is originating a new call and then completing the transfer (in many cases PBXes do this as a so-called trombone transfer where two trunks are tied up for the duration of the call). As the originator it's local DID extension is correct in this scenario. Quite possibly the PBX could be programmed to give the BTN (Billing telephone number, usually the main business number) for the PBX trunks instead, but that doesn't help you. Using the incoming caller information seems incorrect in this case, at least IMHO.

I believe the solution is to make the cell phones part of the Avaya system. I cannot recall if it was Avaya or a third party, but at NPR we had a system where the cell phones could be linked to the PBX and became similar to an extension in a "Follow-me" fashion. Calls to a particular extension would ring that extension and the cell phone simultaneously. My guess transfers to cell phones that were configured that way would get the CLID just like a phone.

To summarize, you need to make it look like an internal transfer versus an external transfer.

The bad news is, if I am right, it means an additional software license and associated costs. Although it is a good feature for many organization and could be justified perhaps. Your best bet may be to ask a knowledgeable Avaya sales person, not support.

Best of luck.