Redundant SIP trunks vs Redundant MGCP-controled PRIs

Unanswered Question

Has anyone used multiple SIP trunks within a Route Group/Route List for redundancy? I'm curious as to the level of awareness CUCM has for a failed SIP trunk; for example, CUCM would be ignorant to PRI failures of an H323 gateway, but would be aware of an MGCP gateway's PRI status. Can anyone speak to how SIP redundancy would measure-up against MGCP for notifying CUCM of a potential trunk failure to PSTN? I'd be curious to hear any real-life experiences you guys have with redundant SIP trunks.


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
gogasca Sun, 09/14/2008 - 20:34

In CUCM there is not SIP keepalive or SIP trunk registration.

CUCM will be aware that SIP call failed when one of our Timers for call proceeding expire or if using TCP, TCP socket was not able to be open or first INVITE failed...etc

We can still handle those.

Hope this helps


This Discussion