test 24781785-BEA-WebLogic | Page 10

Ma na gi ng We bLo gic S IP Ser ver Ne two rk Reso ur ces If your system uses a multihomed load balancer having two public addresses, you must also define a pair of channels to configure both public addresses. If the engine tier server has only one NIC, you must define a second, logical address on the NIC to configure a dedicated channel for the second public address. In addition, you must configure your IP routing policies to define which logical address is associated with each public load balancer address. Enabling DNS Support WebLogic SIP Server supports DNS for resolving the transport, IP address and port number of a proxy required to send a SIP message. This matches the behavior described in RFC 3263. DNS may also used when routing responses in order to resolve the IP address and port number of a destination. WARNING: Because DNS resolution is performed within the context of SIP message processing, any DNS performance problems result in increased latency performance. BEA recommends using a caching DNS server in a production environment to minimize potential performance problems. To configure DNS support: 1. Log in to the Administration Console for the WebLogic SIP Server domain you want to configure. 2. Click Lock & Edit to obtain a configuration lock. 3. Select the SipServer node in the left pane of the Console. 4. Select the Configuration->General tab in the right pane. 5. Select Enable DNS Server Lookup. 6. Click Save to save your changes. 7. Click Activate Changes to apply the configuration. When you enable DNS lookup, the server can use DNS to: 1-4 z Discover a proxy server’s transport, IP address, and port number when a request is sent to a SIP URI. z Resolve an IP address and/or port number during response routing, depending on the contents of the Sent-by field. Configuring Network Resources