" /> SIP HA issue - Genesys CTI User Forum

Author Topic: SIP HA issue  (Read 2162 times)

Offline Noufal

  • Full Member
  • ***
  • Posts: 106
  • Karma: -6
SIP HA issue
« on: October 14, 2018, 01:28:30 PM »
Advertisement
Dear Experts,

Having issue with SIP HA, if Secondary becomes Primary agent can not hear any voice .

what are the field to be checked

Offline genesysguru

  • Sr. Member
  • ****
  • Posts: 293
  • Karma: 12
    • Genesys Guru Blog
Re: SIP HA issue
« Reply #1 on: October 15, 2018, 02:07:13 PM »
What SIP HA method are you using and is this on Windows or Linux. Check you HA scripts are working and the VIP interface up/down is OK. Also ensure that everything is configured to use the SIP VIP address where relevant. After that it is a case of understanding the SIP signalling and following the RTP streams.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: SIP HA issue
« Reply #2 on: October 15, 2018, 02:52:24 PM »
What type of HA architecture for SIP do you use (IP takeover, bonding, External balancer, SIP proxy,..)?

Offline Noufal

  • Full Member
  • ***
  • Posts: 106
  • Karma: -6
Re: SIP HA issue
« Reply #3 on: October 18, 2018, 05:14:14 AM »
It is Windows NLB , And everything configured on VIP

Offline genesysguru

  • Sr. Member
  • ****
  • Posts: 293
  • Karma: 12
    • Genesys Guru Blog
Re: SIP HA issue
« Reply #4 on: October 18, 2018, 04:37:09 PM »
Check router Gratuitous ARP

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: SIP HA issue
« Reply #5 on: October 19, 2018, 10:05:34 AM »
Is your RM or MCP running on same server as the Genesys SIP server?

Offline Noufal

  • Full Member
  • ***
  • Posts: 106
  • Karma: -6
Re: SIP HA issue
« Reply #6 on: October 21, 2018, 05:35:55 AM »
Yes , RM/MCP and SIP running on same machine 

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: SIP HA issue
« Reply #7 on: October 22, 2018, 07:07:50 AM »
As I know, Windows NLB has a limitation, where the cluster IP address:port is not accessible from cluster node which is stopped/non-active at this moment