Is there a reason the industry standard of using DNS SRV records wouldnt apply here? Be aware if this is access side and performing nat traversal you may encounter issues with far end nat devices barking if your response comes from a different IP than the original request went to. On 4/19/2016 2:32 PM, Sykes, Aaron wrote:
Has anyone had any success load balancing SIP? More specifically distributing SIP registrations across a number of access SBCs and maintaining persistence based on source IP. By maintaining source IP persistence subsequent calls would go to the SBC to which they are registered. In this case each of several SBCs cache registrations for a single SIP registrar. Has anyone used F5 or Kamailio for this..or some other SIP proxy or load balancer?
Thank You,
Aaron
------------------------------------------------------------------------ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops