Loa d Ba la nce r Conf ig ur at io n
Max-Forwards: 70
Event: ua-profile
Expires: 10
Content-Length: 0
No.
Time
3 3.430903
Source
10.1.1.1
Destination
10.1.3.4
Protocol Info
SIP
Status: 200 OK
Internet Protocol, Src: 10.1.1.1 (10.1.1.1), Dst: 10.1.3.4 (10.1.3.4)
User Datagram Protocol, Src Port: 42316 (42316), Dst Port: 2222 (2222)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
To: sut ;tag=82722c03
Content-Length: 0
Contact:
CSeq: 1 SUBSCRIBE
Call-ID: [email protected]
Figure 3-7 illustrates the NOTIFY flow.
Note that while source address NAT is enabled for both directions (UAS->WebLogic SIP Server
and WebLogic SIP Server->UA), the load balancer can correctly identify the destination address
in Step 3 by relying on receiving responses on the same port number as the one used to send
requests. This implies that the load balancer maintains state.
Configuring Network Resources
3-17