This page shows an initial RCS presence subscription and notification example. The UE registers, exchanges HTTP/XCAP-style configuration and presence-content transactions, subscribes to watcher and presence event packages, publishes its own presence capability, and receives NOTIFY messages from the presence server. The flow is an implementation example of the Presence Subscription/Notify Model, so the exact sequence can vary by UE and network policy.

Use the flow as a reference for correlating SIP registration, SIP SUBSCRIBE/NOTIFY/PUBLISH transactions, HTTP resource updates, and XML presence bodies. The important troubleshooting points are the dialog identifiers, Event package, Subscription-State, Content-Type, PIDF or watcherinfo XML body, and RCS service capability parameters.

• Flow Summary
• 1) REGISTER
• HTTP Configuration and Content Resource Transactions
  • H1) HTTP GET
  • H3) HTTP PUT
  • H11) HTTP PUT
• 3) Watcher Information SUBSCRIBE
• 5) Watcher Information NOTIFY
• 7) Presence SUBSCRIBE
• 9) Presence PUBLISH
• 11) Presence NOTIFY
• 21) OPTIONS Capability Check

Flow Summary

The table below lists the SIP, HTTP, and XML transactions in chronological order. SIP messages establish IMS registration and presence event subscriptions, while HTTP transactions update or retrieve presence-related resources used by the RCS service.

1) REGISTER sip:test-rcs.com

REGISTER sip:test-rcs.com SIP/2.0

Call-ID: 3Ag0yaUAAA@192.168.1.1

CSeq: 1 REGISTER

From: <sip:+339012341234@test-rcs.com>;tag=PBg0yaUCAA

To: <sip:+339012341234@test-rcs.com>

Via: SIP/2.0/UDP 192.168.1.1:5060;keep;branch=z9hG4bKbf994bf8ba37e52882a1ac4ba748f008383138;rport

Max-Forwards: 70

Contact: <sip:192.168.1.1:5060;transport=UDP>;+sip.instance="<urn:gsma:imei:356432059050620>";

This message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, 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.

+g.oma.sip-im;

+g.3gpp.cs-voice;

+g.gsma.rcs.ipcall;

+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;automata;

+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-is,

urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.fthttp"

Supported: path, gruu

Allow: INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER

Route: <sip:192.168.1.2:5060;transport=udp;lr>

Expires: 600000

User-Agent: IM-client/OMA1.0 Test-RCS-client/2.5.13

Authorization: Digest username="X",uri="sip:test-rcs.com",algorithm=MD5,realm="X",nonce="",response=""

Content-Length: 0

This message clip highlights the following parameters: Route, Authorization, Expires, Content-Length, Supported, Allow, User-Agent, nonce, response, realm, algorithm. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

H1) HTTP GET

GET /org.openmobilealliance.xcap-directory/users/sip%3A%2B339012341234%40Test-rcs.com/directory.xml HTTP/1.1

Host: 192.168.1.2:8080

User-Agent: Test-RCS-client 2.5.13

Authorization: Basic WDpY

This 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-Length: 0

This message clip highlights the following parameters: 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.

H2) HTTP 200 OK

HTTP/1.1 200 OK

Date: Thu, 19 Jun 2014 15:30:47 GMT

This message clip highlights the following parameters: 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.

Etag:

Content-Type: application/vnd.oma.xcap-directory+xml

Content-Length: 251

This 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.

<?xml version="1.0" encoding="UTF-8"?>

<xcap-directory xmlns="urn:oma:xml:xdm:xcap-directory">

<folder auid="rls-services"> </folder>

<folder auid="resource-lists"> </folder>

<folder auid="org.openmobilealliance.pres-rules"> </folder>

</xcap-directory>

H3) HTTP PUT

PUT /rls-services/users/sip%3A%2B339012341234%40Test-rcs.com/index HTTP/1.1

Host: 192.168.1.2:8080

User-Agent: Test-RCS-client 2.5.13

Authorization: Basic WDpY

This 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/rls-services+xml

Content-Length:461

This 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.

<?xml version="1.0" encoding="UTF-8"?>

<rls-services xmlns="urn:ietf:params:xml:ns:rls-services" xmlns:rl="urn:ietf:params:xml:ns:resource-lists">

<service uri="sip:+339012341234@Test-rcs.com;pres-list=rcs">

<resource-list>http://192.168.1.2:8080/resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs%22%5D</resource-list>

<packages>

<package>presence</package>

</packages>

</service></rls-services>

H4) HTTP 201 Created

HTTP/1.1 201 Created

Date: Thu, 19 Jun 2014 15:30:47 GMT

Content-Length: 0

This 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.

H5) HTTP PUT

PUT /resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index HTTP/1.1

Host: 192.168.1.2:8080

User-Agent: Test-RCS-client 2.5.13

Authorization: Basic WDpY

This 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/resource-lists+xml

Content-Length:1180

This 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.

<?xml version="1.0" encoding="UTF-8"?>

<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists">

<list name="oma_buddylist">

<external anchor="http://192.168.1.2:8080/resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs%22%5D"/>

</list>

<list name="oma_grantedcontacts">

<external anchor="http://192.168.1.2:8080/resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs%22%5D"/>

</list>

<list name="oma_blockedcontacts">

<external anchor="http://192.168.1.2:8080/resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs_blockedcontacts%22%5D"/>

<external anchor="http://192.168.1.2:8080/resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs_revokedcontacts%22%5D"/>

</list>

<list name="rcs">

<display-name>My presence buddies</display-name>

</list>

<list name="rcs_blockedcontacts">

<display-name>My blocked contacts</display-name>

</list>

<list name="rcs_revokedcontacts">

<display-name>My revoked contacts</display-name>

</list>

</resource-lists>

H6) HTTP 201 Created

HTTP/1.1 201 Created

Date: Thu, 19 Jun 2014 15:30:48 GMT

Content-Length: 0

This 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.

H7) HTTP PUT

PUT /org.openmobilealliance.pres-rules/users/sip%3A%2B339012341234%40Test-rcs.com/pres-rules HTTP/1.1

Host: 192.168.1.2:8080

User-Agent: Test-RCS-client 2.5.13

Authorization: Basic WDpY

This 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/auth-policy+xml

Content-Length:2204

This 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.

<?xml version="1.0" encoding="UTF-8"?>

<cr:ruleset xmlns:ocp="urn:oma:xml:xdm:common-policy" xmlns:pr="urn:ietf:params:xml:ns:pres-rules" xmlns:cr="urn:ietf:params:xml:ns:common-policy">

<cr:rule id="wp_prs_allow_own">

<cr:conditions>

<cr:identity><cr:one id="sip:+339012341234@Test-rcs.com"/></cr:identity>

</cr:conditions>

<cr:actions><pr:sub-handling>allow</pr:sub-handling></cr:actions>

<cr:transformations>

<pr:provide-services><pr:all-services/></pr:provide-services>

<pr:provide-persons><pr:all-persons/></pr:provide-persons>

<pr:provide-devices><pr:all-devices/></pr:provide-devices>

<pr:provide-all-attributes/>

</cr:transformations>

</cr:rule>

<cr:rule id="rcs_allow_services_anonymous">

<cr:conditions><ocp:anonymous-request/></cr:conditions>

<cr:actions><pr:sub-handling>allow</pr:sub-handling></cr:actions>

<cr:transformations>

<pr:provide-services><pr:all-services/></pr:provide-services>

<pr:provide-all-attributes/>

</cr:transformations>

</cr:rule>

<cr:rule id="wp_prs_unlisted">

<cr:conditions><ocp:other-identity/></cr:conditions>

<cr:actions><pr:sub-handling>confirm</pr:sub-handling></cr:actions>

</cr:rule>

<cr:rule id="wp_prs_grantedcontacts">

<cr:conditions>

<ocp:external-list>

<ocp:entry anc="http://192.168.1.2:8080/resource-lists/users/sip:+339012341234@Test-rcs.com/index/~~/resource-lists/list%5B@name=%22oma_grantedcontacts%22%5D"/>

</ocp:external-list>

</cr:conditions>

<cr:actions><pr:sub-handling>allow</pr:sub-handling></cr:actions>

<cr:transformations>

<pr:provide-services><pr:all-services/></pr:provide-services>

<pr:provide-persons><pr:all-persons/></pr:provide-persons>

<pr:provide-devices><pr:all-devices/></pr:provide-devices>

<pr:provide-all-attributes/>

</cr:transformations>

</cr:rule>

<cr:rule id="wp_prs_blockedcontacts">

<cr:conditions>

<ocp:external-list>

<ocp:entry anc="http://192.168.1.2:8080/resource-lists/users/sip:+339012341234@Test-rcs.com/index/~~/resource-lists/list%5B@name=%22oma_blockedcontacts%22%5D"/>

</ocp:external-list>

</cr:conditions>

<cr:actions><pr:sub-handling>block</pr:sub-handling></cr:actions>

</cr:rule>

</cr:ruleset>

H8) HTTP 201 Created

HTTP/1.1 201 Created

Date: Thu, 19 Jun 2014 15:30:48 GMT

Content-Length: 0

This 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.

H9) HTTP GET

GET /resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs%22%5D HTTP/1.1

Host: 192.168.1.2:8080

User-Agent: Test-RCS-client 2.5.13

Authorization: Basic WDpY

This 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-Length: 0

This message clip highlights the following parameters: 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.

H10) HTTP 200 OK

HTTP/1.1 200 OK

Date: Thu, 19 Jun 2014 15:30:49 GMT

This message clip highlights the following parameters: 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.

Etag: E292

Content-Type: application/xcap-el+xml

Content-Length: 118

This 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.

<list name="rcs" xmlns="urn:ietf:params:xml:ns:resource-lists">

<display-name>My presence buddies</display-name>

</list>

H11) HTTP PUT

PUT /resource-lists/users/sip%3A%2B339012341234%40Test-rcs.com/index/~~/resource-lists/list%5B@name=%22rcs%22%5D/entry%5B@uri=%22sip%3A%2B339012341234%40Test-rcs.com%22%5D HTTP/1.1

Host: 192.168.1.2:8080

User-Agent: Test-RCS-client 2.5.13

Authorization: Basic WDpY

This 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:55

This 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:+339012341234@Test-rcs.com'></entry>

H12) HTTP 201 Created

HTTP/1.1 201 Created

Date: Thu, 19 Jun 2014 15:30:50 GMT

Content-Length: 0

This 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.

3) SUBSCRIBE sip:+339012341234@test-rcs.com

SUBSCRIBE sip:+339012341234@test-rcs.com SIP/2.0

Call-ID: M6g0yaUDAA@192.168.1.1

CSeq: 1 SUBSCRIBE

From: "test user" <sip:+339012341234@test-rcs.com>;tag=M6g0yaUEAA

To: <sip:+339012341234@test-rcs.com>

Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bKde579051f561c89dff9a1272bf84f9a4383138;rport

Max-Forwards: 70

Route: <sip:192.168.1.2:5060;transport=udp;lr>

Expires: 3600

User-Agent: IM-client/OMA1.0 Test-RCS-client/2.5.13

Contact: <sip:192.168.1.1:5060;transport=UDP>;+sip.instance="<urn:gsma:imei:356432059050620>"

Allow: INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER

This message clip highlights the following parameters: Via, Route, Contact, Expires, CSeq, Call-ID, From, To, Max-Forwards, Allow, 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.

Event: presence.winfo

Accept: application/watcherinfo+xml

Content-Length: 0

This message clip highlights the following parameters: 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.

5) NOTIFY sip:192.168.1.1:5060;transport=udp

NOTIFY sip:192.168.1.1:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.1.2:51416;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee90;rport;transport=udp

Via: SIP/2.0/TCP 192.168.1.2:6061;branch=z9hG4bK23d85090f6ff4f7a9e6da67814f96d45;rport=49790

Max-Forwards: 69

From: <sip:presence@test-rcs.com>;tag=0cfe3495adda4142b88a2f341e9cb8d8

To: <sip:+339012341234@test-rcs.com>;tag=M6g0yaUEAA

This 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 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: 221

CSeq: 1 NOTIFY

Call-ID: M6g0yaUDAA@192.168.1.1

This 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>

<watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="0" state="full">

<watcher-list resource="sip:+339012341234@test-rcs.com" package="presence" />

</watcherinfo>

7) SUBSCRIBE sip:+339012341234@test-rcs.com;pres-list=rcs

SUBSCRIBE sip:+339012341234@test-rcs.com;pres-list=rcs SIP/2.0

Call-ID: 8Ih0yaUFAA@192.168.1.1

CSeq: 1 SUBSCRIBE

From: "test user" <sip:+339012341234@test-rcs.com>;tag=8Ih0yaUGAA

To: <sip:+339012341234@test-rcs.com;pres-list=rcs>

Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bKcad78c485b12e9ff2a8410e4d375722f383138;rport

Max-Forwards: 70

Route: <sip:192.168.1.2:5060;transport=udp;lr>

Expires: 3600

User-Agent: IM-client/OMA1.0 Test-RCS-client/2.5.13

Contact: <sip:192.168.1.1:5060;transport=UDP>;+sip.instance="<urn:gsma:imei:356432059050620>"

Allow: INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER

This message clip highlights the following parameters: Via, Route, Contact, Expires, CSeq, Call-ID, From, To, Max-Forwards, Allow, 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.

Event: presence

Supported: eventlist

Content-Length: 0

This message clip highlights the following parameters: Content-Length, Supported. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

9) PUBLISH sip:+339012341234@test-rcs.com

PUBLISH sip:+339012341234@test-rcs.com SIP/2.0

Call-ID: xSh0yaUHAA@192.168.1.1

CSeq: 1 PUBLISH

From: <sip:+339012341234@test-rcs.com>;tag=xSh0yaUIAA

To: <sip:+339012341234@test-rcs.com>

Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK84da5f074a2ba56ea1c0d63f7fa45a54383138;rport

Max-Forwards: 70

Route: <sip:192.168.1.2:5060;transport=udp;lr>

Expires: 3600

This message clip highlights the following parameters: Via, Route, Expires, CSeq, Call-ID, 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.

SIP-If-Match: ac63be7e9042439dad76da16904cf48d

User-Agent: IM-client/OMA1.0 Test-RCS-client/2.5.13

This message clip highlights the following parameters: 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.

Event: presence

Content-Type: application/pidf+xml

Content-Length: 2122

This 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.

<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns:opd="urn:oma:xml:pde:pidf:ext" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0" entity="sip:+339012341234@test-rcs.com">

<tuple id="t1">

<status><basic>open</basic></status>

<op:service-description>

<op:service-id>org.openmobilealliance:File-Transfer</op:service-id>

<op:version>1.0</op:version>

</op:service-description>

<contact>sip:+339012341234@test-rcs.com</contact>

<timestamp>2014-06-19T06:30:45.000Z</timestamp>

</tuple>

<tuple id="t2">

<status><basic>open</basic></status>

<op:service-description>

<op:service-id>org.gsma.imageshare</op:service-id>

<op:version>1.0</op:version>

</op:service-description>

<contact>sip:+339012341234@test-rcs.com</contact>

<timestamp>2014-06-19T06:30:45.000Z</timestamp>

</tuple>

<tuple id="t3">

<status><basic>open</basic></status>

<op:service-description>

<op:service-id>org.gsma.videoshare</op:service-id>

<op:version>1.0</op:version>

</op:service-description>

<contact>sip:+339012341234@test-rcs.com</contact>

<timestamp>2014-06-19T06:30:45.000Z</timestamp>

</tuple>

<tuple id="t4">

<status><basic>open</basic></status>

<op:service-description>

<op:service-id>org.openmobilealliance:IM-session</op:service-id>

<op:version>1.0</op:version>

</op:service-description>

<contact>sip:+339012341234@test-rcs.com</contact>

<timestamp>2014-06-19T06:30:45.000Z</timestamp>

</tuple>

<tuple id="t5">

<status><basic>open</basic></status>

<op:service-description>

<op:service-id>org.3gpp.cs-videotelephony</op:service-id>

<op:version>1.0</op:version>

</op:service-description>

<contact>sip:+339012341234@test-rcs.com</contact>

<timestamp>2014-06-19T06:30:45.000Z</timestamp>

</tuple>

</presence>

11) NOTIFY sip:192.168.1.1:5060;transport=udp

NOTIFY sip:192.168.1.1:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.1.2:51417;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee93;rport;transport=udp

Via: SIP/2.0/TCP 192.168.1.2:6061;branch=z9hG4bK299ad82d0390455982d5f305d9d68a43;rport=49793

Max-Forwards: 69

From: <sip:presence@test-rcs.com>;tag=9ab957cb0149442b9e4a6d99d93f3d21

To: <sip:+339012341234@test-rcs.com>;tag=8Ih0yaUGAA

This 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

Contact: <sip:presence@test-rcs.com>

Content-Type: application/pidf+xml

This 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: 0

CSeq: 1 NOTIFY

Call-ID: 8Ih0yaUFAA@192.168.1.1

This 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>

13) NOTIFY sip:192.168.1.1:5060;transport=udp

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 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 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 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>

<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>

H13) HTTP PUT

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 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 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@anritsu-rcs.com;user=phone'></entry>

H14) HTTP 201 Created

HTTP/1.1 201 Created

Date: Thu, 19 Jun 2014 15:37:52 GMT

Content-Length: 0

This 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.

H15) HTTP PUT

PUT /pidf-manipulation/users/sip%3A%2B339012341234%40Test-rcs.com/perm-presence HTTP/1.1

Host: 192.168.1.2:8080

User-Agent: Test-RCS-client 2.5.13

Authorization: Basic WDpY

This 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/pidf+xml

Content-Length:882

This 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.

<?xml version="1.0" encoding="UTF-8"?>

<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns:opd="urn:oma:xml:pde:pidf:ext" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:+339012341234@Test-rcs.com">

<pdm:person id="p1">

<op:overriding-willingness>

<op:basic>open</op:basic>

</op:overriding-willingness>

<ci:homepage></ci:homepage>

<rpid:status-icon opd:etag="1403159871372" opd:fsize="2193" opd:contenttype="image/jpeg" opd:resolution="96x96">http://192.168.1.2:8080/org.openmobilealliance.pres-content/users/sip%3A%2B339012341234%40Test-rcs.com/oma_status-icon/rcs_status_icon</rpid:status-icon>

<pdm:note></pdm:note>

<pdm:timestamp>2014-06-19T06:37:51.000Z</pdm:timestamp>

</pdm:person>

</presence>

H16) HTTP 201 Created

HTTP/1.1 201 Created

Date: Thu, 19 Jun 2014 15:37:52 GMT

Content-Length: 0

This 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.

15) NOTIFY sip:192.168.1.1:5060;transport=udp

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 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 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 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>

<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>

17) NOTIFY sip:192.168.1.1:5060;transport=udp

NOTIFY sip:192.168.1.1:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.1.2:51420;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee9d;rport;transport=udp

Via: SIP/2.0/TCP 192.168.1.2:6061;branch=z9hG4bKe1e99f24f4614aa993621438073cbf80;rport=49827

Max-Forwards: 69

From: <sip:presence@test-rcs.com>;tag=9ab957cb0149442b9e4a6d99d93f3d21

To: <sip:+339012341234@test-rcs.com>;tag=8Ih0yaUGAA

This 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

Contact: <sip:presence@test-rcs.com>

Content-Type: application/pidf+xml

This 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: 842

CSeq: 2 NOTIFY

Call-ID: 8Ih0yaUFAA@192.168.1.1

This 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>

<presence

xmlns="urn:ietf:params:xml:ns:pidf"

xmlns:op="urn:oma:xml:prs:pidf:oma-pres"

xmlns:opd="urn:oma:xml:pde:pidf:ext"

xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model"

xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"

xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"

entity="sip:+339012341234@test-rcs.com">

<pdm:person id="p1">

<op:overriding-willingness>

<op:basic>open</op:basic>

</op:overriding-willingness><ci:homepage></ci:homepage>

<rpid:status-icon opd:etag="1403159871372" opd:fsize="2193" opd:contenttype="image/jpeg" opd:resolution="96x96">http://192.168.1.2:8080/org.openmobilealliance.pres-content/users/sip%3A%2B339012341234%40test-rcs.com/oma_status-icon/rcs_status_icon

</rpid:status-icon>

<pdm:note></pdm:note>

<pdm:timestamp>2014-06-19T06:37:51.000Z</pdm:timestamp>

</pdm:person>

</presence>

19) NOTIFY sip:192.168.1.1:5060;transport=udp

NOTIFY sip:192.168.1.1:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.1.2:51421;branch=z9hG4bKb7a8715cd9d04e019149483fac110bee9f;rport;transport=udp

Via: SIP/2.0/TCP 192.168.1.2:6061;branch=z9hG4bKfbca33dd3d5641bca3ef48f012e1b505;rport=49835

Max-Forwards: 69

From: <sip:presence@test-rcs.com>;tag=9ab957cb0149442b9e4a6d99d93f3d21

To: <sip:+339012341234@test-rcs.com>;tag=8Ih0yaUGAA

This 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

Contact: <sip:presence@test-rcs.com>

Content-Type: application/pidf+xml

This 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: 3997

CSeq: 3 NOTIFY

Call-ID: 8Ih0yaUFAA@192.168.1.1

This 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>

<presence

xmlns="urn:ietf:params:xml:ns:pidf"

xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns:opd="urn:oma:xml:pde:pidf:ext" xmlns:opd11="urn:oma:xml:pde:pidf:ext:1.1" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps"xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" entity="sip:+330123456789@test-rcs.com">

<tuple id="a0">

<status><basic>open</basic></status>

<op:service-description>

<op:service-id>org.openmobilealliance:StandaloneMsg</op:service-id>

<op:version>2.0</op:version>

</op:service-description>

<contact>sip:+330123456789@test-rcs.com</contact>

<timestamp>2014-06-19T06:40:16.4438118Z</timestamp>

</tuple>

21) OPTIONS sip:192.168.1.1:5060;transport=udp

OPTIONS sip:192.168.1.1:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.1.2:51422;branch=z9hG4bKb7a8715cd9d04e019149483fac110beea0;rport;transport=udp

Via: SIP/2.0/TCP 192.168.1.2:49755;branch=z9hG4bKec290e95eb714990adc88d84f09a6367;rport=49836

Max-Forwards: 69

From: <sip:+330123456789@test-rcs.com>;tag=33ad62399bdc451d92591e2d9e29903a

To: <sip:+339012341234@test-rcs.com>

Date: Thu, 19 Jun 2014 15:40:39 GMT

Expires: 3600

Contact: <sip:+330123456789@test-rcs.com>;

+g.3gpp.cs-voice;video;

+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.msg,urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.largemsg,urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";

+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.im,urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.fullsfgroupchat,urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.ftthumb,urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.fthttp,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.sp,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.dp,urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.geopull"

CSeq: 1 OPTIONS

Call-ID: 334cb0b603964d348a011fc8f87c82cd

Content-Length: 0

This message clip highlights the following parameters: Via, Contact, Expires, CSeq, Call-ID, From, To, Content-Length, Max-Forwards, 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.

Record-Route: <sip:192.168.1.2;lr>

22) 200 OK

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.1.2:51422;branch=z9hG4bKb7a8715cd9d04e019149483fac110beea0;rport=51422;transport=udp;

This 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:49755;branch=z9hG4bKec290e95eb714990adc88d84f09a6367;rport=49836

From: <sip:+330123456789@test-rcs.com>;tag=33ad62399bdc451d92591e2d9e29903a

To: <sip:+339012341234@test-rcs.com>;tag=4Ax2yaUJAA

CSeq: 1 OPTIONS

Call-ID: 334cb0b603964d348a011fc8f87c82cd

Contact: <sip:192.168.1.1:5060;transport=UDP>;

This message clip highlights the following parameters: Contact, CSeq, Call-ID, From, To. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

+sip.instance="<urn:gsma:imei:356432059050620>";

+g.gsma.rcs.ipcall;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;automata;

+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.im,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.ft,urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.fthttp,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.dp,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.sp"

Accept-Contact: *;

This message clip highlights the following parameters: Accept-Contact. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

+g.gsma.rcs.ipcall;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;automata;

+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.im,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.ft,urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.fthttp,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.dp,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.sp"

Allow: INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER

This message clip highlights the following parameters: Allow. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

Server: IM-client/OMA1.0 Test-RCS-client/2.5.13

Content-Length: 0

This message clip highlights the following parameters: 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.