RFC3087 - Control of Service Context using SIP Request-URI(2)

时间:2005-02-17 来源: 作者: 点击:
To: TheLittleGuy sip: UserB@wcom.com ;tag=3145678 Call-Id: 12345600@here.com CSeq: 1 ACK Content-Length: 0 ACK F10 ACK sip: UserB-dep-fb@vm.wcom.com SIP/2.0 Proxy-VM Via: SIP/2.0/UDP wcom.com:5060 Vi
  
To: TheLittleGuy <sip:UserB@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK
Content-Length: 0

ACK F10 ACK sip:UserB-dep-fb@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuy <sip:UserB@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK
Content-Length: 0

/* RTP streams are established between A and B2. VM
system starts IVR dialog for message-deposit on busy
for UserB */

/* User A Hangs Up with VM system. Alternatively, the
VM system could initiate the BYE*/

BYE F11 BYE sip:UserB@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
Route: <sip:UserB-dep-fnb@vm.wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuy <sip:UserB@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

BYE F12 BYE sip: UserB-dep-fnb@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuy <sip:UserB@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F13 SIP/2.0 200 OK
VM->Proxy Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuy <sip:UserB@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F14 SIP/2.0 200 OK
Proxy->A Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuy <sip:UserB@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

4.2.3 Direct call to a subscriber's mailbox

User A calls UserB's mailbox directly. This flow assumes that
"sip:UserB-dep@vm.wcom.com" maps to UserB's mailbox and the behavior
of "generic message deposit"

User A Proxy VM Service
| | |
| INVITE F1 | |
|------------------>| |
| | INVITE F2 |
| (100 Trying) F3 |---------------------->|
|<------------------| |
| | 200 OK F4 |
| 200 OK F5 |<----------------------|
|<------------------| |
| | |
| ACK F6 | |
|------------------>| ACK F7 |
| |---------------------->|
| | |
| RTP Both Ways - Deposit Msg for B |
|<-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m->|
| | |
| BYE F8 | |
|------------------>| BYE F9 |
| |---------------------->|
| | |
| | 200 OK F10 |
| |<----------------------|
| 200 OK F11 | |
|<------------------| |
| | |

Flow Id Comments

INVITE F1 INVITE sip:UserB-VM@vm.wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-VM@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: TheBigGuy <sip:UserA@here.com>
Proxy-Authorization:Digest username="UserA",
realm="MCI WorldCom SIP",
nonce="ea9c8e88df84f1cec4341ae6cbe5a359", opaque="",
uri="sip:UserB-VM@wcom.com", response=<appropriately
calculated hash goes here>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserA 2890844526 2890844526 IN IP4 client.here.com
s=Session SDP

c=IN IP4 100.101.102.103
t=0 0
m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/8000

/*Client for A prepares to receive data on port 49170
from the network. */

INVITE F2 INVITE sip:UserB-dep@vm.wcom.com SIP/2.0
Proxy->B1 Via: SIP/2.0/UDP wcom.com:5060; branch=1
Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:UserB-VM@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-VM@vm.wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: TheBigGuy <sip:UserA@here.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserA 2890844526 2890844526 IN IP4 client.here.com
s=Session SDP
c=IN IP4 100.101.102.103
t=0 0
m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/8000

(100 Trying SIP/2.0 100 Trying
F3 Via: SIP/2.0/UDP here.com:5060
Proxy->A) From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-VM@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Content-Length: 0

200 OK F4 SIP/2.0 200 OK
VM->Proxy Via: SIP/2.0/UDP wcom.com:5060; branch=1
Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:UserB-VM@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: TheLittleGuyVoiceMail <sip:UserB-
dep@vm.wcom.com>
Content-Type: application/sdp

Content-Length: <appropriate value>
v=0
o=UserB 2890844527 2890844527 IN IP4 vm.wcom.com
s=Session SDP
c=IN IP4 110.111.112.114
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

200 OK F5 SIP/2.0 200 OK
Proxy->A Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:UserB-VM@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact TheLittleGuyVoiceMail <sip:UserB-
dep@vm.wcom.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserB 2890844527 2890844527 IN IP4 vm.wcom.com
s=Session SDP
c=IN IP4 110.111.112.114
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

ACK F6 ACK sip:UserB-VM@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
Route:<sip:UserB-dep@vm.wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK
Content-Length: 0

ACK F7 ACK sip:UserB-dep@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK

Content-Length: 0
/* RTP streams are established between A and VM. VM
system starts IVR dialog for generic message-deposit
for UserB */

/* User A Hangs Up with VM system. Alternatively, the
VM system could initiate the BYE*/

BYE F8 BYE sip:UserB-VM@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
Route:<sip:UserB-dep@vm.wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

BYE F9 BYE sip: UserB-dep@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F10 SIP/2.0 200 OK
VM->Proxy Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F11 SIP/2.0 200 OK
Proxy->A Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: TheLittleGuyVoiceMail <sip:UserB-
VM@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

4.3 Message Retrieval Scenarios

4.3.1 Call to retrieve messages believed to be from a known subscriber

Some user uses a SIP client on UserA's desk to call the voice mail
system to retrieve messages. The SIP client has authenticated itself
to the proxy using credentials assigned to the device. The proxy can
make a weak assumption that the caller is the device owner. The URI
of "sip:UserA-retrieve@vm.wcom.com" maps to UserA's mailbox and the
behavior of "retrieve messages after prompting for and verifying
PIN." The VM System trusts the proxy, and will not accept calls from
an untrusted source. The proxy will not allow direct calls to
UserA-retrieve@vm.wcom.com. The proxy will forward calls placed to
VoiceMail@wcom.com to UserA-retrieve@vm.wcom.com only for calls
placed from a client device assigned to UserA.

User A Proxy VM Service
| | |
| INVITE F1 | |
|------------------>| |
| | INVITE F2 |
| (100 Trying) F3 |---------------------->|
|<------------------| |
| | 200 OK F4 |
| 200 OK F5 |<----------------------|
|<------------------| |
| | |
| ACK F6 | |
|------------------>| ACK F7 |
| |---------------------->|
| | |
| RTP Both Ways - VM prompts for PIN
|<-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m->|
| | |
| BYE F8 | |
|------------------>| BYE F9 |
| |---------------------->|
| | |
| | 200 OK F10 |
| |<----------------------|
| 200 OK F11 | |
|<------------------| |
| | |

Flow Id Comments

INVITE F1 INVITE sip:VoiceMail@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: TheBigGuy <sip:UserA@here.com>
Proxy-Authorization:Digest username="UserAPhone",
realm="MCI WorldCom SIP",
nonce="ea9c8e88df84f1cec4341ae6cbe5a359", opaque="",
uri="sip:VoiceMail@wcom.com", response=<appropriately
calculated hash goes here>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserA 2890844526 2890844526 IN IP4 client.here.com
s=Session SDP
c=IN IP4 100.101.102.103
t=0 0
m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/8000

/*Client for A prepares to receive data on port 49170
from the network. */

INVITE F2 INVITE sip:UserA-retrieve@vm.wcom.com SIP/2.0
Proxy->B1 Via: SIP/2.0/UDP wcom.com:5060; branch=1
Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:VoiceMail@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: TheBigGuy <sip:UserA@here.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserA 2890844526 2890844526 IN IP4 client.here.com
s=Session SDP
c=IN IP4 100.101.102.103
t=0 0
m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/8000

(100 Trying SIP/2.0 100 Trying
F3 Via: SIP/2.0/UDP here.com:5060
Proxy->A) From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Content-Length: 0

200 OK F4 SIP/2.0 200 OK
VM->Proxy Via: SIP/2.0/UDP wcom.com:5060; branch=1
Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:VoiceMail@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: VoiceMailSystem <sip:UserA-
retrieve@vm.wcom.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserB 2890844527 2890844527 IN IP4 vm.wcom.com
s=Session SDP
c=IN IP4 110.111.112.114
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

200 OK F5 SIP/2.0 200 OK
Proxy->A Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:VoiceMail@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact VoiceMailSystem <sip: UserA-
retrieve@vm.wcom.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserB 2890844527 2890844527 IN IP4 vm.wcom.com
s=Session SDP
c=IN IP4 110.111.112.114
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

ACK F6 ACK sip:VoiceMail@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
Route:<sip:UserA-retrieve@vm.wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK
Content-Length: 0

ACK F7 ACK sip:UserA-retrieve@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>; tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK
Content-Length: 0

/* RTP streams are established between A and VM. VM
determines that the call is likely from UserA, and
starts a message retrieval session, prompting for
PIN*/

/* User A Hangs Up with VM system. Alternatively, the
VM system could initiate the BYE*/

BYE F8 BYE sip: VoiceMail@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
Route:<sip:UserA-retrieve@vm.wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

BYE F9 BYE sip: UserA-retrieve@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F10 SIP/2.0 200 OK
VM->Proxy Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>

To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F11 SIP/2.0 200 OK
Proxy->A Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

4.3.2 Call to retrieve messages from an authenticated subscriber

UserA to call the voice mail system to retrieve messages.
Assumptions: The caller is authenticated using UserA's credentials.
"sip:UserA-retrieve-auth@vm.wcom.com" maps to UserA's mailbox and the
behavior of "retrieve messages." The voice mail service trusts the
proxy not to forward any calls to that URI unless the call is
authenticated to be from UserA.

Given these assumptions, The VM service may choose not require a PIN
for calls to this URI.

User A Proxy VM Service
| | |
| INVITE F1 | |
|------------------>| |
| | INVITE F2 |
| (100 Trying) F3 |---------------------->|
|<------------------| |
| | 200 OK F4 |
| 200 OK F5 |<----------------------|
|<------------------| |
| | |
| ACK F6 | |
|------------------>| ACK F7 |
| |---------------------->|
| | |
| RTP Both Ways - Deposit Msg for B |
|<-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m-m->|
| | |
| BYE F8 | |
|------------------>| BYE F9 |
| |---------------------->|
| | |
| | 200 OK F10 |
| |<----------------------|
| 200 OK F11 | |
|<------------------| |
| | |

Flow Id Comments

INVITE F1 INVITE sip:VoiceMail@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: TheBigGuy <sip:UserA@here.com>
Proxy-Authorization:Digest username="UserA",
realm="MCI WorldCom SIP",
nonce="ea9c8e88df84f1cec4341ae6cbe5a359", opaque="",
uri="sip:VoiceMail@wcom.com", response=<appropriately
calculated hash goes here>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserA 2890844526 2890844526 IN IP4 client.here.com
s=Session SDP

c=IN IP4 100.101.102.103
t=0 0
m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/8000

/*Client for A prepares to receive data on port 49170
from the network. */

INVITE F2 INVITE sip:UserA-retrieve-auth@vm.wcom.com SIP/2.0
Proxy->B1 Via: SIP/2.0/UDP wcom.com:5060; branch=1
Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:VoiceMail@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: TheBigGuy <sip:UserA@here.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserA 2890844526 2890844526 IN IP4 client.here.com
s=Session SDP
c=IN IP4 100.101.102.103
t=0 0
m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/8000

(100 Trying SIP/2.0 100 Trying
F3 Via: SIP/2.0/UDP here.com:5060
Proxy->A) From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Content-Length: 0

200 OK F4 SIP/2.0 200 OK
VM->Proxy Via: SIP/2.0/UDP wcom.com:5060; branch=1
Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:VoiceMail@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact: VoiceMailSystem <sip:UserA-retrieve-
auth@vm.wcom.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserB 2890844527 2890844527 IN IP4 vm.wcom.com
s=Session SDP
c=IN IP4 110.111.112.114
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

200 OK F5 SIP/2.0 200 OK
Proxy->A Via: SIP/2.0/UDP here.com:5060
Record-Route: <sip:VoiceMail@wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 INVITE
Contact VoiceMailSystem <sip: UserA-retrieve-
auth@vm.wcom.com>
Content-Type: application/sdp
Content-Length: <appropriate value>

v=0
o=UserB 2890844527 2890844527 IN IP4 vm.wcom.com
s=Session SDP
c=IN IP4 110.111.112.114
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

ACK F6 ACK sip:VoiceMail@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
Route: <sip:UserA-retrieve-auth@vm.wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK
Content-Length: 0

ACK F7 ACK sip:UserA-retrieve-auth@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>; tag=3145678
Call-Id: 12345600@here.com
CSeq: 1 ACK
Content-Length: 0

/* RTP streams are established between A and VM. VM
determines that the call is likely from UserA, and
starts a message retrieval session. Since the proxy
has already authenticated the identity of UserA, the
VM does not need to prompt for PIN. */

/* User A Hangs Up with VM system. Alternatively, the
VM system could initiate the BYE*/

BYE F8 BYE sip:VoiceMail@wcom.com SIP/2.0
A->Proxy Via: SIP/2.0/UDP here.com:5060
Route:<sip:UserA-retrieve-auth@vm.wcom.com>
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

BYE F9 BYE sip: UserA-retrieve-auth@vm.wcom.com SIP/2.0
Proxy->VM Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F10 SIP/2.0 200 OK
VM->Proxy Via: SIP/2.0/UDP wcom.com:5060
Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

200 OK F11 SIP/2.0 200 OK
Proxy->A Via: SIP/2.0/UDP here.com:5060
From: TheBigGuy <sip:UserA@here.com>
To: VoiceMail <sip:VoiceMail@wcom.com>;tag=3145678
Call-Id: 12345600@here.com
CSeq: 2 BYE
Content-Length: 0

5. Security Considerations

This document discusses a usage of SIP/2.0 as defined by RFC2543[1].
It introduces no additions, modifications, or restrictions to the
protocol defined therein. Any implementation of the concepts in this
document is subject to the issues discussed there.

6. Acknowledgments

The authors would like to thank Chris Cunningham, Steve Donovan, Alan
Johnston, Henry Sinnreich, Kevin Summers, John Truetken, and Dean
Willis for their discussion of and contribution to this work.

References

[1] Handley, M., Schulzrinne, H., Schooler, E. and J. Rosenberg,
"SIP: Session Initiation Protocol", RFC2543, March 1999.

Authors' Addresses

Ben Campbell
dynamicsoft
5100 Tennyson Parkway
Suite 1200
Plano, TX 75024

EMail: bcampbell@dynamicsoft.com

Robert J. Sparks
dynamicsoft
5100 Tennyson Parkway
Suite 1200
Plano, TX 75024

EMail: rsparks@dynamicsoft.com

Full Copyright Statement

Copyright (C) The Internet Society (2001). All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

Funding for the RFCEditor function is currently provided by the
Internet Society.

------分隔线----------------------------
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------
最新评论 查看所有评论
发表评论 查看所有评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
评价:
表情:
用户名: 密码: 验证码:
推荐内容