Loa d Ba la nce r Conf ig ur at io n
rport-Based Configuration
RFC 3581 improves SIP and NAT interactions by allowing the client to request that the server
send responses to a UDP port number from the request rather than from the Via. In order for both
SUBSCRIBE and NOTIFY to work correctly, both the UAC as well as WebLogic SIP Server
must support RFC 3581. Figure 3-6 illustrates the SUBSCRIBE flow.
Figure 3-6 rport SUBSCRIBE Sequence
UAC A 2.3.4.5
LB 1.2.3.4
WLSS 1 10.1.1.1
|
|
|
|
|
|
|(1) SUBSCRIBE
|
|
|----------------------->|
|
| (2.3.4.5->1.2.3.4)
|(2) SUBSCRIBE
|
|
|----------------------->|
|
| (10.1.4.5->10.1.1.1)
|
|
|
|
|
|(3) 200 OK
|
|
|<-----------------------|
|
| (10.1.1.1->10.1.4.5 ) |
|(4) 200 OK
|
|
|<-----------------------|
|
| (1.2.3.4->2.3.4.5 )
|
|
|
|
|
The complete message trace from Figure 3-6 is shown in Listing 3-7 below.
Listing 3-7 Complete Message Trace for rport SUBSCRIBE
No.
Time
1 1.425250
Source
2.3.4.5
Destination
1.2.3.4
Protocol Info
SIP
Request:
SUBSCRIBE sip:[email protected]:5060
Internet Protocol, Src: 2.3.4.5 (2.3.4.5), Dst: 1.2.3.4 (1.2.3.4)
User Datagram Protocol, Src Port: 9999 (9999), Dst Port: sip (5060)
Session Initiation Protocol
Configuring Network Resources
3-15