transfer REFER over sip trunk IP Office

[zicca]

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?

IPO: 172.16.99.200:5060
IVR: 172.16.99.201:5080


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@172.16.99.200:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 172.16.99.201:5080;branch=z9hG4bK-d87543-3b31095555533328-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:2555@172.16.99.200>
To: "2048"<sip:2048@172.16.99.200>;tag=c2138128ede4e6f c
From: <sip:2555@172.16.99.200>;tag=9b6e8477
Call-ID: 2199291a97490c6dd6942eeb803df65d
CSeq: 3 REFER
Refer-To: <sip:2022@172.16.99.200:5060>
Referred-By: <sip:2555@172.16.99.200>
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 172.16.99.201:5080;branch=z9hG4bK-d87543-3b31095555533328-1--d87543-;rport
From: <sip:2555@172.16.99.200>;tag=9b6e8477
Call-ID: 2199291a97490c6dd6942eeb803df65d
CSeq: 3 REFER
Supported: timer
Server: IP Office 9.1.6.0 build 153
To: "2048" <sip:2048@172.16.99.200>;tag=c2138128ede4e6fc
Content-Length: 0


Thanks a lot.

[mordek]

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?

[kirchenlo]

Hello,

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.

[mordek]

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."

[davis624]

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...