[cisco-voip] Change RNA expire response on SIP trunk

[Mark Holloway]

SIP 480 is Temporarily Unavailable and SIP 486 is User Busy. 

Did they tell you what their RNA timer expiry is?  Were you seeing the call ring for longer than what they say the expiry is set to?  The expiry settings should live in their SIP Registrar platform, not their SBC.  If I'm understanding correctly, a call from Verizon rings into a CUCM phone, user doesn't answer, CUCM/CUBE sends a 480 Temp Unavailable, and Verizon does not take action on that?  


On Apr 26, 2011, at 7:03 PM, Mike Lydick wrote:

> Reviewed the call flow with Verizon and they were not responding to the 480 status we sent back. They should have been sending back a cancel after their RNA timer expired or after we sent back the user busy but they were not. Issue is not resolved but it appears to be with the providers SBC.
> 
> Someone once told me not to rely on the the provider...
> 
> Thanks for the suggestions
> 
> Best Regards,
> 
> Mike Lydick
> 
> 
> 
> 
> On Tue, Apr 26, 2011 at 12:29 PM, Ryan Ratliff <rratliff at cisco.com> wrote:
> Couple ways to do this.
> 
> One would be via SIP transparency and normalization script on CUCM before it goes out to CUBE.
> 
> The other would be a SIP profile on CUBE.  See https://supportforums.cisco.com/docs/DOC-16174?decorator=print for an example of using a profile to modify a header.
> 
> -Ryan
> 
> On Apr 26, 2011, at 11:43 AM, Mike Lydick wrote:
> 
> We have a redundant CUBE's with CM8.5. Verizon wants to see a sip status 408 and not 404 when we expire RNA timers. So when we send back the 404, Verizon sends back another call setup, assuming that something went wrong with the call. This cause multiple call attempts until we hit all the available inbound (CM) dial-peers.
> 
> Has any had to map cause codes for verizon or change the default response to RNA timer with a similar setup?
> 
> 
> Best Regards,
> 
> Mike Lydick
> 
> 
> _______________________________________________
> cisco-voip mailing list
> 
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110427/cd5f0c14/attachment.html>