These CommuniGate Pro SIP Farm features make the Load Balancer "session binding" table useless (when used for SIP UDP) (note that this is not needed with the CommuniGate Pro SIP Farm).ĬommuniGate Pro SIP Farm distributes SIP request packets by relaying them between the frontend Servers,Īccording to the SIP Farm algorithms the SIP Farm algorithms redirect the SIP response packets to theįrontend Server that has sent the related SIP request. When the remote device sends a response packet, this table record allows the Load Balancer to send the response to the "proper" frontend Server The Binding table for some Load Balancer port v (and the Load Balancer VIP address) contains IP address-port pairs: Many Load Balancers create "session binding" for incoming UDP requests, in the same way they process incoming TCP connections - even if they do not implement any SIP-special techniques. Thus, these SIP-specific Load Balancer techniques are not required with CommuniGate Pro. Request handling if a request or response packet is received by any SIP Farm member. CommuniGate Pro SIP Farm technology ensures proper Usually these techniques are based on the request Call-ID field and thus fail very often. ![]() SIP-specific techniques implemented in some Load Balancers allow them to send all "related" requests to the same server. the Load Balancer should not keep any information about an incoming UDP packet after it has been redirected to some frontend server. incoming packets should not create any "session" in the Load Balancer, i.e.Some Load Balancers use SIP-specific processing for port 5060 by default: consult with your Load Balancer manufacturer. the Load Balancer should not apply any SIP-specific logic to these packets if your Load Balancer has any SIP-specific options, make sure they are switched off.incoming packets should be redirected evenly to F1, F2, F3 frontend server addresses, to the same port 5060.Configure the Load Balancer to process incoming UDP packets received on its VIP address and port 5060: The frontend servers have IP addresses F1, F2, F3. Leave the Server-wide WAN IP Address field empty. open the Network pages in the Settings realm of the CommuniGate Pro WebAdmin Interface, and specify the VIP address as the Cluster-wide WAN IP address. ![]() create DNS SIP SRV records for all your Cluster Domains pointing to this "sip-service" name.select a "sip-service" DNS domain name (such as ), and create a DNS A- or AAAA- record for that name, pointing to the VIP address. ![]() assign the VIP address to the Load Balancer.Performs Network Address Translation for frontend Servers.įirst select the "virtual" IP address (VIP) - this is the only address your Cluster SIP users will "see": This method is used for small Cluster installations, when the frontend Servers do not have direct access to the Internet, and the Load Balancer These requests are always redirected to the specified Cluster member and processed on that member,ĬommuniGate Pro のクラスタでは、クラスタのサーバーのうちSIP ファーム機能が有効になっている 注意: a SIP request can explicitly address some Cluster member (most in-dialog requests do). Select this option for Backend Servers that do not have direct access to the InternetĪnd thus cannot send SIP requests directly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |