Configuring the communications between the SIP Edge Proxy Server and the Sametime SIP Proxy/Registrar
Designate whether the IBM® SIP Edge Proxy Server's communication with the Sametime® SIP Proxy/Registrar's transport type is secure, and define the basic SIP Edge Proxy Server routing settings.
About this task
When the SIP Edge Proxy Server receives a message, it determines whether the package was received from a Sametime SIP Proxy/Registrar by checking the network address the message was received from.
In a clustered environment with a MAC forwarding load balancer in front of the SIP Edge Proxy Server, or when there is no load balancer in front of the SIP Edge Proxy cluster, this is the address of the WebSphere® SIP proxy server that sits in front of the SIP Proxy/Registrar cluster. In a NAT environment, this address might not match the physical IP address of the WebSphere SIP proxy server because NAT can translate the address to a different IP address. To determine how the SIP Edge Proxy Server sees packets coming from the SIP Proxy/Registrar, consult with a network administrator or run a network analyzing tool on the WebSphere SIP proxy servers that sit in front of the SIP Edge Proxy cluster and analyze the source IP address of the packets sent from the SIP Proxy/Registrar.
In addition, if the SIP Edge Proxy cluster is fronted by a NAT forwarding load balancer, the SIP Edge Proxy Server might see all packets sent by external clients or the SIP Proxy/Registrar as received from the same IP address, that is, the IP address of the load balancer. To allow the SIP Edge Proxy Server to distinguish between external users and the SIP Proxy/Registrar, allocate a separate connection pool on the load balancer for the traffic received from the SIP Proxy/Registrar. Consult a load balancer administrator for other options.
Since there are no System Solutions Console administrative pages for the IBM SIP Edge Proxy Server configuration, perform configuration updates by manually editing the edge-proxy.xml file.