UC7.12a SIP Integration Failover

Unanswered Question
Jul 8th, 2009

Hi,

we are testing a SIP integration from UC7.x to CUCM 7.x with HA - we are forcing the secondary to stop taking calls. What should the user experience be in this scenario, we have to wait atleast 75 seconds before failover kicks in (i.e the primary starts taking the calls). Doing the same test using a sccp integration shows much better results i.e the failover is initiated within seconds. Any advise / previous experience of this would be appreciated...TIA, Jeff

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Markus Schneider Mon, 07/13/2009 - 18:11

Pressing the "stop taking calls" button isn't really a fair comparison. When you press that button with the SCCP integration, it unregisters its ports, so CUCM immediately can't route calls to it. If things go down where neither side is aware the failure occurred (e.g. pull the ethernet cable to the server), then times will be more similar.

That said, you may be able to improve things for SIP by tweaking the SIP trunk profile. You may try adjusting the SIP retry INVITE counter to 3 or other such timers.

Actions

This Discussion