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

[Bob Zanett (AM)]

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-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan Charles
Sent: Thursday, February 09, 2012 10:46 AM
To: Nick Matthews
Cc: cisco-voip at 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 <matthnick at gmail.com<mailto:matthnick at 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

On Tue, Feb 7, 2012 at 3:32 PM, Roger Wiklund <roger.wiklund at gmail.com<mailto:roger.wiklund at gmail.com>> wrote:
>> 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
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip



itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120209/87e07adc/attachment.html>