CUBE and SIP REFER on 2811 and 15.1(4)M7 ?

jbollen · ‎08-05-2014

Dear All,

While setting up a configuration for my customer, I _had_ to use a 2811 with 15.1(4)M7. The set-up looks schematically like this:

IVR == SIP Trunk == 2811 -z-> PSTN with BRI

One of the tests is the IVR (10.90.17.153) transferring a call coming from the PSTN via the 2811 (10.64.157.253) back out to the PSTN via the same 2811. When the IVR stays in the speech path (tromboning and thus not releasing the call) all goes well. When the IVR sends aSIP REFER to the 2811, the latter seems not to like that: upon arrival of the SIP INVITE of the IVR a call is set up to the PSTN and as soon as the call is answered (Q931 CONNECT received) the IVR sends a SIP REFER:

Received:
REFER sip:01234@10.64.157.253:5060 SIP/2.0
Via: SIP/2.0/UDP 10.90.17.153:5060;branch=z9hG4bKf049af9b5a43f113278720357114791d
From: <sip:4242@10.64.157.253>;tag=07661277
To: <sip:01234@10.64.157.253>;tag=9FBD33E4-FBD
Call-Id: 13E8B29E2401CFBF0F802D23BE84E16CD60409C3E0@10.90.17.153
CSeq: 2 REFER
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, REFER
Contact: <sip:4242@10.90.17.153:5060>
Content-Length: 0
Max-Forwards: 70
Supported: timer
Supported: ms-bypass
User-Agent:
X-xxxxUUID: E8B29E2401CFBF0F802E23BE84E16CD6
Refer-To: <sip:3366@10.64.157.253:5060?Replaces=F9967AF6-1B1911E4-8834C95D-2FDEC030%4010.64.157.253%3bto-tag%3d9FBD126C-101A%3bfrom-tag%3d05af7727>
Referred-By: sip:10.90.17.153:5060

which results in "debug voip ccapi inout" in:

004982: 14:25:29.960: //34161/FCC5EC368835/CCAPI/cc_api_call_facility:
   Interface=0x4A8843D4, Call Id=34161
004983: 14:25:29.964: //34161/FCC5EC368835/CCAPI/cc_api_get_ssCTreRoutingNotSupported:
   CallInfo(ssCTreRoutingNotSupported=FALSE)
004984: 14:25:29.964: //34161/FCC5EC368835/CCAPI/ccConferenceDestroy:
   Conference Id=0x39, Tag=0x0

And the call is - as you can guess - disconnected. So I read the document on " dynamic REFER handling on the Cisco UBE" and that insinuates that one should use 15.2 or higher to have the CUBE deal with a SIP REFER and consume it.

Is this really a prerequisite for a CUBE to be able to deal with a REFER? I can imagine that SIP REFER was already longer supported by the CUBE e.g. in a set-up where CUCM would send REFER to txfer a call back to the originating gateway. Any thoughts?

Kind regards and many thansk in advance!

Jan

Ayodeji Okanlawon · ‎08-05-2014

Jan,

We will need to see the full sip traces to get an idea of what is going on.

Please rate all useful posts

jbollen · ‎08-05-2014

yes, I understand that you're eagerly waiting to troubleshoot this but before we dive too deep in details, I'd like to know whether the CUBE functionality on IOS 15.1 can handle an incoming SIP REFER that is trying to transfer a call from the 2811 to the 2811. Or does one really need 15.2 ?

I guess that the key to the problem might be in "cc_api_get_ssCTreRoutingNotSupported" in the output of "debug voice ccapi inout".

cheers,

Jan