Addressbook Update
|
Step |
Direction |
Protocol |
Message |
Comments |
|
|
UA1 <-- Proxy/UA2 |
SIP |
NOTIFY |
Send Addressbook update to a UE(330123456789) |
|
|
UA1 --> Proxy/UA2 |
SIP |
200 OK | |
|
|
UA1 --> Proxy/UA2 |
HTTP | PUT/XML | |
|
|
UA1 <-- Proxy/UA2 |
HTTP | 201 Created | |
|
(5) |
UA1 <-- Proxy/UA2 |
SIP |
NOTIFY | |
|
|
UA1 --> Proxy/UA2 |
SIP |
200 OK |
NOTIFY sip:192.168.1.1:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:51418;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee95;rport;transport=udp
Via: SIP/2.0/TCP 192.168.1.2:6061;branch=z9hG4bKdacba03107bf4493a4c2823e59ed1195;rport=49804
Max-Forwards: 69
From: <sip:presence@test-rcs.com>;tag=0cfe3495adda4142b88a2f341e9cb8d8
To: <sip:+339012341234@test-rcs.com>;tag=M6g0yaUEAA
This SIP message clip highlights the following parameters: Via, From, To, Max-Forwards. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
Event: presence.winfo
Contact: <sip:presence@test-rcs.com>
Content-Type: application/watcherinfo+xml
This SIP message clip highlights the following parameters: Contact, Content-Type. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
Subscription-State: active
Content-Length: 368
CSeq: 2 NOTIFY
Call-ID: M6g0yaUDAA@192.168.1.1
This SIP message clip highlights the following parameters: CSeq, Call-ID, Content-Length. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
Record-Route: <sip:192.168.1.2;lr>
<?xml version="1.0" encoding="utf-8"?>
<watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="1" state="full">
<watcher-list resource="sip:+339012341234@test-rcs.com" package="presence">
<watcher status="pending" id="5c7c3f58" display-name="RCS-VUA" event="subscribe">
sip:+330123456789@test-rcs.com
</watcher>
</watcher-list>
</watcherinfo>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:51418;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee95;rport=51418;transport=udp;
This SIP message clip highlights the following parameters: Via. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
received=192.168.1.2,SIP/2.0/TCP 192.168.1.2:6061;
branch=z9hG4bKdacba03107bf4493a4c2823e59ed1195;rport=49804
From: <sip:presence@test-rcs.com>;tag=0cfe3495adda4142b88a2f341e9cb8d8
To: <sip:+339012341234@test-rcs.com>;tag=M6g0yaUEAA
CSeq: 2 NOTIFY
Call-ID: M6g0yaUDAA@192.168.1.1
Content-Length: 0
This SIP message clip highlights the following parameters: CSeq, Call-ID, From, To, Content-Length. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
PUT /resource-lists/users/sip%3A%2B339012341234%40test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs%22%5D/entry%5B@uri=%22sip%3A%2B330123456789%40test-rcs.com%3Buser%3Dphone%22%5D HTTP/1.1
Host: 192.168.1.2:8080
User-Agent: TEST-RCS-client 2.5.13
Authorization: Basic WDpY
This SIP message clip highlights the following parameters: Authorization, User-Agent. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
X-3GPP-Intended-Identity: "X"
Content-type: application/xcap-el+xml
Content-Length:66
This SIP message clip highlights the following parameters: Content-Type, Content-Length. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
<entry uri='sip:+330123456789@test-rcs.com;user=phone'></entry>
HTTP/1.1 201 Created
Date: Thu, 19 Jun 2014 15:32:03 GMT
Content-Length: 0
This SIP message clip highlights the following parameters: Content-Length, Date. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
NOTIFY sip:192.168.1.1:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:51419;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee96;rport;transport=udp
Via: SIP/2.0/TCP 192.168.1.2:6061;branch=z9hG4bKf7b78f04185f427fb6f0bcfcace167de;rport=49810
Max-Forwards: 69
From: <sip:presence@test-rcs.com>;tag=0cfe3495adda4142b88a2f341e9cb8d8
To: <sip:+339012341234@test-rcs.com>;tag=M6g0yaUEAA
This SIP message clip highlights the following parameters: Via, From, To, Max-Forwards. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
Event: presence.winfo
Contact: <sip:presence@test-rcs.com>
Content-Type: application/watcherinfo+xml
This SIP message clip highlights the following parameters: Contact, Content-Type. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
Subscription-State: active
Content-Length: 496
CSeq: 3 NOTIFY
Call-ID: M6g0yaUDAA@192.168.1.1
This SIP message clip highlights the following parameters: CSeq, Call-ID, Content-Length. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
Record-Route: <sip:192.168.1.2;lr>
<?xml version="1.0" encoding="utf-8"?>
<watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="4" state="full">
<watcher-list resource="sip:+339012341234@test-rcs.com" package="presence">
<watcher status="active" id="5c7c3f58" display-name="RCS-VUA" event="approved">sip:+330123456789@test-rcs.com</watcher>
<watcher status="active" id="9a20aee7" display-name="test user" event="approved">sip:+339012341234@test-rcs.com</watcher>
</watcher-list>
</watcherinfo>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:51419;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee96;rport=51419;transport=udp;
This SIP message clip highlights the following parameters: Via. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
received=192.168.1.2,SIP/2.0/TCP 192.168.1.2:6061;
branch=z9hG4bKf7b78f04185f427fb6f0bcfcace167de;rport=49810
From: <sip:presence@test-rcs.com>;tag=0cfe3495adda4142b88a2f341e9cb8d8
To: <sip:+339012341234@test-rcs.com>;tag=M6g0yaUEAA
CSeq: 3 NOTIFY
Call-ID: M6g0yaUDAA@192.168.1.1
Content-Length: 0
This SIP message clip highlights the following parameters: CSeq, Call-ID, From, To, Content-Length. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.