[cisco-voip] CUBE Issues with SIP Reinvite...

Discussion:

Jonathan Charles

2012-02-07 17:49:42 UTC

So, our carrier is routing toll free calls to a third-party and those calls
are getting a reinvite invoked.

We are ignoring the reinvite and they dump the call.

Topology is SIP Provider - SIP - CUBE - H.323 - CCM 8.6

I have added this sip-profile (from a previous post)...

voice service voip
ip address trusted list
ipv4 10.0.0.0 255.0.0.0
ipv4 172.16.0.0 255.240.0.0
ipv4 172.20.0.0 255.255.255.0
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol pass-through g711ulaw
h323
h225 display-ie ccm-compatible
modem passthrough nse payload-type 101 codec g711ulaw
sip
bind control source-interface GigabitEthernet0/0.700
bind media source-interface GigabitEthernet0/0.700
sip-profiles 1
!
voice class sip-profiles 1
request REINVITE sip-header Allow-Header modify "UPDATE, " " "
request INVITE sip-header Allow-Header modify " UPDATE, " " "
response 180 sip-header Allow-Header modify " UPDATE, " " "
response 200 sip-header Allow-Header modify " UPDATE, " " "
!

At the 15 minute mark of the call, we get the reinvite to see if we are
still alive:

*Feb 7 17:41:29.419 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:***@2.2.2.2:5060 SIP/2.0
Via: SIP/2.0/UDP 72.11.192.82:5060
;branch=z9hG4bKpeibqn0080kgu05p7220sbc1rosu1.1
From: <sip:***@72.11.192.82>;tag=266630096-1328635552106
To: <sip:***@2.2.2.2>;tag=3B2EDDA4-E82
Call-ID: B5972919-50E711E1-A08CC205-***@2.2.2.2
CSeq: 745327741 INVITE
Contact: <sip:72.11.192.82:5060;transport=udp>
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Supported:
Accept: multipart/mixed,application/media_control+xml,application/sdp
Max-Forwards: 19
Content-Type: application/sdp
Content-Length: 179

v=0
o=- 23022424 1 IN IP4 1.1.1.1
s=-
c=IN IP4 1.1.1.1
t=0 0
m=audio 41510 RTP/AVP 0 105
a=silenceSupp:off - - - -
a=ptime:20
a=rtpmap:105 telephone-event/8000

*Feb 7 17:41:29.427 UTC: //4748/0092A0C5E201/SIP/Msg/ccsipDisplayMsg:
Sent:

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 72.11.192.82:5060
;branch=z9hG4bKpeibqn0080kgu05p7220sbc1rosu1.1
From: <sip:***@72.11.192.82>;tag=266630096-1328635552106
To: <sip:***@2.2.2.2>;tag=3B2EDDA4-E82
Date: Tue, 07 Feb 2012 17:41:29 GMT
Call-ID: B5972919-50E711E1-A08CC205-***@2.2.2.2
CSeq: 745327741 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0

We ignore this reinvite (CUBE thing), and the call is dumped by the remote
side.

*Feb 7 17:42:29.415 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:***@2.2.2.2:5060 SIP/2.0
Via: SIP/2.0/UDP 72.11.192.82:5060
;branch=z9hG4bKpeibqn0080kgu05p7220sdc1rocv1.1
From: <sip:***@72.11.192.82>;tag=266630096-1328635552106
To: <sip:***@2.2.2.2>;tag=3B2EDDA4-E82
Call-ID: B5972919-50E711E1-A08CC205-***@2.2.2.2
CSeq: 745327742 BYE
Max-Forwards: 19
Content-Length: 0

*Feb 7 17:42:29.435 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 72.11.192.82:5060
;branch=z9hG4bKpeibqn0080kgu05p7220sdc1rocv1.1
From: <sip:***@72.11.192.82>;tag=266630096-1328635552106
To: <sip:***@2.2.2.2>;tag=3B2EDDA4-E82
Date: Tue, 07 Feb 2012 17:42:29 GMT
Call-ID: B5972919-50E711E1-A08CC205-***@2.2.2.2
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 745327742 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=47266,OS=7558192,PR=47707,OR=7633120,PL=0,JI=0,LA=0,DU=943
Content-Length: 0

We have spiked the SIP Session Expires Timer to 7800 seconds, but that has
had no effect... the SIP provider says they are conforming to the SIP
standard and it is us that is configured incorrectly.

Any ideas?

Jonathan

Roger Wiklund

2012-02-07 20:32:29 UTC

Permalink

We have spiked the SIP Session Expires Timer to 7800 seconds, but that has
had no effect... the SIP provider says they are conforming to the SIP
standard and it is us that is configured incorrectly.
Any ideas?

I had re-invite problems a month ago with a SIP-SIP CUBE running
15.1.4M IOS. Downgrading to 15.1.2 or up to 15.2 fixed the problem.
Looks like a bug.

/Roger

Nick Matthews

2012-02-07 22:23:36 UTC

Permalink

H.323-SIP isn't recommended. I'm also not sure if SIP profiles
actually doing anything in H.323-SIP.

I would try this SIP-SIP to see if you have better luck.

-nick

Post by Roger Wiklund

I had re-invite problems a month ago with a SIP-SIP CUBE running
15.1.4M IOS. Downgrading to 15.1.2 or up to 15.2 fixed the problem.
Looks like a bug.
/Roger
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip

Jonathan Charles

2012-02-09 16:45:40 UTC

Permalink

I am pretty sure SIP to SIP on a cube is not supported, or at least it
doesn't work.

I have tried connecting a SIP trunk from CUCM to the CUBE (and a SIP trunk
to the provider) and the calls always fail (I need to try it again and
debug why...)

The solution here was the SIP Session Expires timer set to 8 hours, now we
add that to our invite and they just don't prompt us again.... of course,
you will need your provider to care that you sent it...

Jonathan

Post by Nick Matthews
H.323-SIP isn't recommended. I'm also not sure if SIP profiles
actually doing anything in H.323-SIP.
I would try this SIP-SIP to see if you have better luck.
-nick

Post by Roger Wiklund

Post by Jonathan Charles
We have spiked the SIP Session Expires Timer to 7800 seconds, but that

has

Post by Roger Wiklund

Post by Jonathan Charles
had no effect... the SIP provider says they are conforming to the SIP
standard and it is us that is configured incorrectly.
Any ideas?

Bob Zanett (AM)

2012-02-09 17:13:54 UTC

Permalink

I am not sure about the SIP-to-SIP not working. This was working years ago, as I helped a very large medical firm begin to utilize SIP to telco. At the time, I was able to experiment with all types of internetworking:

* SIP to SIP to CUCM

* SIP to H323 to CUCM

* SIP to H323 with Gatekeeper to CUCM
Now as for SIP to H323 - I don't believe I would recommend this even if it was supported due to the consumption of resources. I know that you can do H323 to SIP utilizing Cisco's Session Management Edition.

Also, we have several Enterprise Contact Centers utilizing SIP to telco and SIP proxy - using CUBE. One item missing from CUBE is CPA (call progress analysis) - though this should be coming soon.

With SIP, one has to understand the capabilities of the opposing party. I have seen issues from ptime, DTMF-relay, codec and offer type. As for re-invite, you want to make sure that if you are transferring the call around internally that you do not pass the re-invite back out to the telco -as they most likely will not know what to do with it.

What is the use case of the re-invite?

Kind Regards -

Bob Zanett
Technical Services Architect

From: cisco-voip-***@puck.nether.net [mailto:cisco-voip-***@puck.nether.net] On Behalf Of Jonathan Charles
Sent: Thursday, February 09, 2012 10:46 AM
To: Nick Matthews
Cc: cisco-***@puck.nether.net
Subject: Re: [cisco-voip] CUBE Issues with SIP Reinvite...

I am pretty sure SIP to SIP on a cube is not supported, or at least it doesn't work.

I have tried connecting a SIP trunk from CUCM to the CUBE (and a SIP trunk to the provider) and the calls always fail (I need to try it again and debug why...)

The solution here was the SIP Session Expires timer set to 8 hours, now we add that to our invite and they just don't prompt us again.... of course, you will need your provider to care that you sent it...

Jonathan

On Tue, Feb 7, 2012 at 4:23 PM, Nick Matthews <***@gmail.com<mailto:***@gmail.com>> wrote:
H.323-SIP isn't recommended. I'm also not sure if SIP profiles
actually doing anything in H.323-SIP.

I would try this SIP-SIP to see if you have better luck.

-nick

Post by Roger Wiklund

Post by Jonathan Charles
We have spiked the SIP Session Expires Timer to 7800 seconds, but that has
had no effect... the SIP provider says they are conforming to the SIP
standard and it is us that is configured incorrectly.
Any ideas?

itevomcid

Nick Matthews

2012-02-09 17:33:24 UTC

Permalink

You may want to start here:
http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-sipsip.html

-nick

Post by Jonathan Charles
I am pretty sure SIP to SIP on a cube is not supported, or at least it
doesn't work.
I have tried connecting a SIP trunk from CUCM to the CUBE (and a SIP trunk
to the provider) and the calls always fail (I need to try it again and debug
why...)
The solution here was the SIP Session Expires timer set to 8 hours, now we
add that to our invite and they just don't prompt us again.... of course,
you will need your provider to care that you sent it...
Jonathan

H.323-SIP isn't recommended. I'm also not sure if SIP profiles
actually doing anything in H.323-SIP.
I would try this SIP-SIP to see if you have better luck.
-nick

Post by Roger Wiklund

Roger Wiklund

2012-02-10 12:37:07 UTC

Permalink

Post by Jonathan Charles
I am pretty sure SIP to SIP on a cube is not supported, or at least it
doesn't work.

Of course SIP-SIP works. I have done at least 5 installations last
year with SIP-SIP CUBE. I don't know where this rumor comes from that
SIP-SIP is not working, I've seen this at least a couple of times
now...