As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

Enhanced HA Resilience for Network Disruptions

Starting with version 8.1.103.61, SIP Server supports enhanced high-availability resilience for network disruptions. With this feature, switchovers can be triggered when SIP Server detects MSML VOIP Service DNs and/or Trunk DNs that are out of service. After a switchover, a backup (new primary) SIP Server can place MSML VOIP Service DNs and/or Trunk DNs back in service and proceed with calls processing, minimizing or avoiding network outages.

switchover-on-msml-oos
Setting: [TServer] section, the SIP Server Application (in standalone mode) or the VOIP Service DN with service-type=sip-cluster-nodes (in SIP Cluster mode)
Default Value: false
Valid Values: true, false
Changes Take Effect: For the next call

Specifies the SIP Server action in case of losing connectivity with MSML VOIP Service DNs. When set to true, in the case of strict matching only, VOIP Service DNs with the same or alternative geo-location are considered. After detecting that those DNs are out of service, SIP Server checks one more time that MSML VOIP Service DNs are unresponsive, before reporting the SERVICE_UNAVAILABLE status to LCA/SCS in order to trigger a switchover.

switchover-on-trunks-oos
Setting: [TServer] section, the SIP Server Application (in standalone mode) or the VOIP Service DN with service-type=sip-cluster-nodes (in SIP Cluster mode)
Default Value: false
Valid Values: true, false
Changes Take Effect: For the next call

Specifies the SIP Server action in case of losing connectivity with Trunk DNs. When set to true, in the case of strict matching only, Trunk DNs with the same or alternative geo-location are considered. After detecting that those DNs are out of service, SIP Server checks one more time that Trunk DNs are unresponsive, before reporting the SERVICE_UNAVAILABLE status to LCA/SCS in order to trigger a switchover.

This page was last edited on September 11, 2020, at 21:12.

Feedback

Comment on this article:

blog comments powered by Disqus