Avaya Support Forums  

Go Back   Avaya Support Forums > Small and Medium Business Communications

Thread Tools Search this Thread Display Modes
Old 04-28-2016, 09:59 AM
zicca zicca is offline
Aspiring Member
Join Date: Mar 2012
Posts: 2
zicca has 10 reputation points
Default transfer REFER over sip trunk IP Office

Hello, I have an IPO 9.1 with a sip trunk to an IVR. This answers the call and after that transfers to an extension. The transfer allways fail and IPO send a sip/2.0 481 call leg/transaction does not exist.
I read that ipo doesn´t support blind transfer over sip trunk. Is this really?


extension 2048 call to 2555 (shortcode to sip trunk) and the IVR wants to transfer to 2022 with REFER

15:55:42 179045044mS SIP Call Rx: 18
REFER sip:2048@;transport=udp SIP/2.0
Via: SIP/2.0/UDP;branch=z9hG4bK-d87543-3b31095555533328-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:2555@>
To: "2048"<sip:2048@>;tag=c2138128ede4e6f c
From: <sip:2555@>;tag=9b6e8477
Call-ID: 2199291a97490c6dd6942eeb803df65d
Refer-To: <sip:2022@>
Referred-By: <sip:2555@>
Content-Length: 0

15:55:42 179045045mS Sip: ac1063c800000778 18.1912.0 299 SIPTrunk Endpoint(f18ad434) Blind transfer is not allowed
15:55:42 179045046mS SIP Call Tx: 18
SIP/2.0 481 Dialog/Transaction Does Not Exist
Via: SIP/2.0/UDP;branch=z9hG4bK-d87543-3b31095555533328-1--d87543-;rport
From: <sip:2555@>;tag=9b6e8477
Call-ID: 2199291a97490c6dd6942eeb803df65d
Supported: timer
Server: IP Office build 153
To: "2048" <sip:2048@>;tag=c2138128ede4e6fc
Content-Length: 0

Thanks a lot.
Reply With Quote
Old 01-24-2017, 04:22 PM
mordek mordek is offline
Aspiring Member
Join Date: Aug 2015
Posts: 2
mordek has 10 reputation points
Default Same issue

I'm running into the same thing with 9.1.9 SIP trunked to a QS/1 IVR. I've read that the IPO doens't support this?
Reply With Quote
Old 01-30-2017, 02:46 AM
kirchenlo kirchenlo is offline
Join Date: Nov 2010
Posts: 195
kirchenlo has 15 reputation pointskirchenlo has 15 reputation points


this is what I found in the "IP Office Public SIP Trunks Overview and Specification" PDF. The document is from 2013, I will see if I find a more recent one.

"For public SIP trunks, IP Office supports only consultative call transfer using REFER.
Consultative transfer is also known as Attended. With consultative transfer, the TransferOR
puts the Primary call on hold and establishes a Consult call to another party. After the
consultation, the TransferOR completes the transfer, causing the TransferEE to connect to the Transfer Target, thereby replacing the Transfer Target’s call with the TransferOR."

So it seems that IP Office does not support blind transfer over SIP Trunk.
Reply With Quote
Old 01-30-2017, 08:15 AM
mordek mordek is offline
Aspiring Member
Join Date: Aug 2015
Posts: 2
mordek has 10 reputation points

Thanks, you are correct. This is directly from Avaya tech support;

"I passed on the information to tier 4 and unfortunately the blind transfer is not supported and this is the only solution that is currently within place.
I will relay your request, but strongly suspect they will confirm the above to be the case."
Reply With Quote
Old 06-23-2017, 12:19 PM
davis624 davis624 is offline
Join Date: Aug 2015
Posts: 4
davis624 has 10 reputation points

Our BP has a case open with Avaya. Our inbound SIP trunks calls hit SM, then AAEP. AAEP redirects the call after user input with a "Refer-To: <sip:xxxxx" to get the call back to SM, then over to AAEP. The call then drops.
Of course ISDN is working without issue...
Reply With Quote


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 11:42 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.