Follow-up to Post: Inbound Issues in a 2-server load balancing system (master replication)

[nocstaff]

This is a followup to https://www.pbxforums.com/threads/i...oad-balancing-system-master-replication.8668/

I tried the dual registration and it in fact is causing issues with BLF's, call parks, etc. I do not care about load balancing, I just want to have a failover that does not require my interaction if my primary server fails. How do I accomplish this if I cannot use dual registration?

 

[ja133]

with an SBC

 

[krooney]

we use AWS route 53 with dns failover

 

[pbxgeek]

Both of the above would work

 

[ja133]

we use AWS route 53 with dns failover

Freeswitch can crash and yet still respond to the SIP tcp port that you’re monitoring in AWS. How are you handling such instances? Have you found a way for route 53 to specifically check for SIP options?

 

[DigitalDaz]

Freeswitch can crash and yet still respond to the SIP tcp port that you’re monitoring in AWS. How are you handling such instances? Have you found a way for route 53 to specifically check for SIP options?

I have been running this exact scenario for over 10 years now and have never had any problems.

You do present an interesting scenario though that I think could be resolved easy enough, just have aws check and endpoint that does an options ping, maybe I'll vibe code that