[cisco-voip] SIP Trunk Redundancy

[Chris Ward (chrward)]

You would need to look at the traces to verify, but it may just be the
time it takes to failover. You probably need to mess with the SIP
profiles and timers to get the trunks to failover in a timely manner. I
think by default it may take 15+ seconds (depends on # of retires and
time between retries) for a SIP trunk call to failover to the next
member of a route group.

 

-Chris

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ted Nugent
Sent: Monday, November 23, 2009 2:14 PM
To: Cisco VoIPoE List
Subject: [cisco-voip] SIP Trunk Redundancy

 

I'm working with a client that has 3 sites where the PRIs were replaced
by SIP trunks. Everything appears to be running fine with the exception
of outbound trunk redundancy. The appear to have just removed the PRIs
from the existing RGs and replaced them with the SIP trunks. The problem
is that if a SIP trunk goes down its not rerouting to the next trunk,
they are just getting dead air. I'm assuming that this is similar to the
issue seen with H323 trunks and why a gatekeeper would be needed for
this but what are the options for SIP? I can probably get by with using
Locations CAC for FO if the trunks fills but not sure about if it
actually goes down and CUCM can determine that. CUCM 7.12 and no CUBE. 

 





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