Con fig ur in g Loa d Ba la nce r Ad dr ess es
Note: The Windows XP IPv6 implementation does not support dual mode sockets, and cannot
be used with any available JVMs to support IPv6. Using IPv6 with a network channel
throws the following exception with either the Sun or JRockit JVMs:
Address family not supported by protocol family: bind .
For more information see
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6230761
Note that each SIP network channel configured on an engine supports either IPv6 or IPv4 traffic.
You cannot mix IPv4 and IPv6 traffic on a single channel. A single engine can be configured with
both an IPv4 and IPv6 channel to support multiple, separate networks.
It is also possible for WebLogic SIP Server engine and data tier nodes to communicate on IPv4
(or IPv6) while supporting the other protocol version for external SIP traffic. To configure engine
and data tier nodes on an IPv6 network, simply specify IPv6 listen addresses for each server
instance.
See “Creating a New SIP or SIPS Channel” on page 1-6 for information about configuring IPv4
and IPv6 network channels.
Configuring Load Balancer Addresses
If your system uses one or more load balancers to distribute connections to the engine tier, you
must configure SIP network channels to include a load balancer address as the external listen
address. When a SIP channel has an external listen address that differs from the channel’s
primary listen address, WebLogic SIP Server embeds the host and port number of the external
address in SIP headers such as Response . In this way, subsequent communication for the call is
directed to the public load balancer address, rather than the local engine tier server address (which
may not be accessible to external clients).
If a network channel does not have a configured external listen address, the primary listen address
is embedded into SIP headers.
Multiple Load Balancers and Multihomed Load Balancers
If your system uses two load balancers, you must define two channels on each engine tier server
(one for each network connection to each load balancer) and assign the external listen address to
the corresponding load balancer. When a particular network interface on the engine tier server is
selected for outbound traffic, the network channel associated with that NIC’s address is examined
to determine the external listen address to embed in SIP headers.
Configuring Network Resources
1-3