Loa d Ba la nce r Conf ig ur at io n
If WebLogic SIP Server subsequently sends a NOTIFY request to the UAC, the sequence shown
in Figure 3-3 takes place:
Figure 3-3 NOTIFY Sequence
LSS 1 10.1.1.1
LB 1.2.3.4
UAC A 2.3.4.5
|
|
|
|
|
|
|(1) NOTIFY
|
|
|----------------------->|
|
| (10.1.1.1->2.3.4.5)
|(2) NOTIFY
|
|
|----------------------->|
|
| (1.2.3.4->2.3.4.5)
|
|
|
|
|
|(3) 200 OK
|
|
|<-----------------------|
|
| (2.3.4.5->1.2.3.4)
|
|(4) 200 OK
|
|
|<-----------------------|
|
| (2.3.4.5->10.1.1.1)
|
|
|
|
|
As in the previous sequence, the IP address translation takes place in the WebLogic SIP
Server->UAC direction for the source IP address, and UAC->WebLogic SIP Server direction for
the destination IP address.
Note that this setup does not require the load balancer to maintain session state information or to
be SIP-aware. The complete message trace from Figure 3-3 is shown in Listing 3-4 below.
Listing 3-4 Complete NOTIFY Message Trace
No.
Time
1 5.430952
Source
10.1.1.1
Destination
2.3.4.5
Protocol Info
SIP
Request:
NOTIFY sip:[email protected]:9999
Internet Protocol, Src: 10.1.1.1 (10.1.1.1), Dst: 2.3.4.5 (2.3.4.5)
User Datagram Protocol, Src Port: 42316 (42316), Dst Port: 9999 (9999)
Session Initiation Protocol
Configuring Network Resources
3-7