1 to 1 Chat
|
Step |
Direction |
Protocol |
Message |
Comments |
|
|
UA1 --> Proxy/UA2 |
SIP/SDP |
INVITE | |
|
|
UA1 <-- Proxy/UA2 |
SIP |
100 Trying | |
|
(3) |
UA1 <-- Proxy/UA2 |
SIP |
183 Session Progress | |
|
(4) |
UA1 <-- Proxy/UA2 |
SIP/SDP |
200 OK | |
|
(5) |
UA1 --> Proxy/UA2 |
SIP |
ACK | |
|
|
UA1 --> Proxy/UA2 |
MSRP |
SEND | |
|
|
UA1 <-- Proxy/UA2 |
MSRP |
200 OK | |
|
(8) |
UA1 --> Proxy/UA2 |
MSRP |
SEND | Send Text 'Hello' |
|
|
UA1 <-- Proxy/UA2 |
MSRP |
200 OK | |
|
(10) |
UA1 <-- Proxy/UA2 |
MSRP |
SEND | Delivery Notification |
|
(11) |
UA1 --> Proxy/UA2 |
MSRP |
200 OK | |
|
|
UA1 <-- Proxy/UA2 |
MSRP |
SEND | Is Composing .. (typing indicator) |
|
(13) |
UA1 --> Proxy/UA2 |
MSRP |
200 OK | |
|
|
UA1 <-- Proxy/UA2 |
MSRP |
SEND | Send Text 'Hi' |
|
(15) |
UA1 --> Proxy/UA2 |
MSRP |
200 OK | |
|
|
UA1 --> Proxy/UA2 |
MSRP |
SEND | Delivery Notification |
|
|
UA1 <-- Proxy/UA2 |
MSRP |
200 OK |
INVITE sip:+14448880000@sharetechnote.com;user=phone SIP/2.0
Conversation-ID: 6b79b8bc937e4985b1dffd062b687bd7
Contribution-ID: d5e4121aeec2cc59546ebaef8966ef185a2f37f0
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session
P-Preferred-Identity: <sip:310410123456789@sharetechnote.com>
P-Early-Media: supported
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
User-Agent: Test IMS 5.0
CSeq: 1 INVITE
Max-Forwards: 70
P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=31041000010000000
Route: <sip:[2001:0:0:1::2]:5060;lr>
a: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session"
c: application/sdp
f: <sip:310410123456789@sharetechnote.com>;tag=284849603
i: 508868544@2001::1:4c16:9c0f:4986:9e6d
k: timer
l: 363
m: <sip:310410123456789@[2001::1:4c16:9c0f:4986:9e6d]:5060;transport=UDP>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session"
t: <sip:+14448880000@sharetechnote.com;user=phone>
v: SIP/2.0/TCP [2001::1:4c16:9c0f:4986:9e6d]:5060;branch=z9hG4bK2563646430smg;transport=TCP
v=0
o=TEST-IMS-UE 1234562 0 IN IP6 2001::1:4c16:9c0f:4986:9e6d
s=SS VOIP
c=IN IP6 2001::1:4c16:9c0f:4986:9e6d
t=0 0
m=message 8880 TCP/MSRP *
a=accept-types:message/cpim application/im-iscomposing+xml // See Ref [2]
a=accept-wrapped-types:text/plain message/imdn+xml
a=setup:active
a=path:msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
a=msrp-cema
a=sendrecv
This SIP message clip highlights the following parameters: Route, CSeq, P-Access-Network-Info, 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.
SIP/2.0 100 Trying
Via: SIP/2.0/TCP [2001::1:4c16:9c0f:4986:9e6d]:5060;branch=z9hG4bK2563646430smg;transport=TCP
Max-Forwards: 70
From: <sip:310410123456789@sharetechnote.com>;tag=284849603
To: <sip:+14448880000@sharetechnote.com;user=phone>
Call-ID: 508868544@2001::1:4c16:9c0f:4986:9e6d
CSeq: 1 INVITE
Content-Length: 0
This SIP message clip highlights the following parameters: Via, CSeq, Call-ID, From, To, Content-Length, 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/2.0 183 Session Progress
Max-Forwards: 70
Via: SIP/2.0/TCP [2001::1:4c16:9c0f:4986:9e6d]:5060;branch=z9hG4bK2563646430smg;transport=TCP
From: <sip:310410123456789@sharetechnote.com>;tag=284849603
To: <sip:+14448880000@sharetechnote.com;user=phone>;tag=b2fbe90a8c2e488ba04ad6d0c0956a6c
Call-ID: 508868544@2001::1:4c16:9c0f:4986:9e6d
CSeq: 1 INVITE
Contact: <sip:+14448880000@sharetechnote.com>
This SIP 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.
Record-Route: <sip:[2001:0:0:1::2]:5060;lr>
Content-Length: 0
This SIP 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.
Via: SIP/2.0/TCP [2001::1:4c16:9c0f:4986:9e6d]:5060;branch=z9hG4bK2563646430smg;transport=TCP
From: <sip:310410123456789@sharetechnote.com>;tag=284849603
To: <sip:+14448880000@sharetechnote.com;user=phone>;tag=b2fbe90a8c2e488ba04ad6d0c0956a6c
Call-ID: 508868544@2001::1:4c16:9c0f:4986:9e6d
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE
Contact: <sip:[2001:0:0:1::2]:49466;transport=tcp>
Content-Type: application/sdp
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, 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.
Record-Route: <sip:[2001:0:0:1::2]:5060;lr>
Content-Length: 292
v=0
o=- 1192 5963 IN IP6 2001:0:0:1::2
s=-
c=IN IP6 2001:0:0:1::2
m=message 16000 TCP/MSRP *
a=accept-types:message/cpim application/im-iscomposing+xml
a=accept-wrapped-types:*
a=path:msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
a=msrp-cema
a=setup:passive
This SIP 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.
SIP/2.0 200 OK
Max-Forwards: 70
ACK sip:[2001:0:0:1::2]:49466;transport=UDP SIP/2.0
CSeq: 1 ACK
Max-Forwards: 70
Route: <sip:[2001:0:0:1::2]:5060;lr>
f: <sip:310410123456789@sharetechnote.com>;tag=284849603
i: 508868544@2001::1:4c16:9c0f:4986:9e6d
l: 0
m: <sip:310410123456789@[2001::1:4c16:9c0f:4986:9e6d]:5060;transport=UDP>
t: <sip:+14448880000@sharetechnote.com;user=phone>;tag=b2fbe90a8c2e488ba04ad6d0c0956a6c
v: SIP/2.0/UDP [2001::1:4c16:9c0f:4986:9e6d]:5060;branch=z9hG4bK1597981393smg;transport=UDP
This SIP message clip highlights the following parameters: Route, CSeq, 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.
MSRP kePLNmnn6eCcn7lB9X SEND
To-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
From-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
Message-ID: IeGt4q5QsCmzD
Success-Report: no
Failure-Report: yes
-------kePLNmnn6eCcn7lB9X$
MSRP kePLNmnn6eCcn7lB9X 200 OK
To-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
From-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
-------kePLNmnn6eCcn7lB9X$
MSRP RgGcYXJW2nHr SEND
To-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
From-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
Message-ID: ZNsPlykpMApIABRrejarbO37ADMMae
Success-Report: no
Failure-Report: yes
Byte-Range: 1-430/430
Content-Type: message/cpim
From: <sip:anonymous@anonymous.invalid> // Ref [2]
To: <sip:anonymous@anonymous.invalid>
This SIP message clip highlights the following parameters: From, To, 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.
DateTime: 2015-02-24T06:48:09Z
NS: imdn <urn:ietf:params:imdn>
NS: MyFeatures <mailto:RCSFeatures@test.com>
MyFeatures.PANI: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=31041000010000000
imdn.Message-ID: wYcJuXBbGOfCtBqIPQqz0I
imdn.Disposition-Notification: positive-delivery, display
Content-type: text/plain;charset=UTF-8
Content-Length: 5
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.
Hello
-------RgGcYXJW2nHr$
MSRP RgGcYXJW2nHr 200
To-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
From-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
-------RgGcYXJW2nHr$
MSRP 69172e29 SEND
To-Path: msrp://[2001:0000:0000:0001:4C16:9C0F:4986:9E6D]:8880/FmnP;tcp
From-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
Message-ID: fd2f8f3e7c
Byte-Range: 1-500/500
Content-Type: message/cpim
From: <sip:anonymous@anonymous.invalid>
To: <sip:anonymous@anonymous.invalid>
This SIP message clip highlights the following parameters: From, To, 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.
DateTime: 2015-02-24T06:48:10.7749079Z
NS: imdn <urn:ietf:params:imdn>
imdn.Message-ID: 2252a2757d
Content-Type: message/imdn+xml
This SIP message clip highlights the following parameters: 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.
Content-Disposition: notification
<imdn xmlns="urn:ietf:params:xml:ns:imdn">
<message-id>wYcJuXBbGOfCtBqIPQqz0I</message-id>
<delivery-notification>
<status>
<delivered />
</status>
</delivery-notification>
</imdn>
-------69172e29$
MSRP 69172e29 200 OK
To-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
From-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
Message-ID: fd2f8f3e7c
-------69172e29$
MSRP 9bc7cfab SEND
To-Path: msrp://[2001:0000:0000:0001:4C16:9C0F:4986:9E6D]:8880/FmnP;tcp
From-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
Message-ID: 214dbfa419
Byte-Range: 1-292/292
Content-Type: application/im-iscomposing+xml
This SIP message clip highlights the following parameters: 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.
<isComposing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd" xmlns="urn:ietf:params:xml:ns:im-iscomposing">
<state>active</state>
<refresh>30</refresh>
</isComposing>
-------9bc7cfab$
MSRP 9bc7cfab 200 OK
To-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
From-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
Message-ID: 214dbfa419
-------9bc7cfab$
MSRP 3c60188b SEND
To-Path: msrp://[2001:0000:0000:0001:4C16:9C0F:4986:9E6D]:8880/FmnP;tcp
From-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
Message-ID: c10258ab0f
Byte-Range: 1-303/303
Content-Type: message/cpim
From: sip:anonymous@anonymous.invalid
To: sip:anonymous@anonymous.invalid
This SIP message clip highlights the following parameters: From, To, 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.
DateTime: 2015-02-24T06:48:26.5388096Z
NS: imdn <urn:ietf:params:imdn>
imdn.Message-ID: dc5ebabb21
imdn.Disposition-Notification: positive-delivery, display
Content-Length: 2
Content-Type: text/plain; charset=utf-8
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.
hi
-------3c60188b$
MSRP 3c60188b 200 OK
To-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
From-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
Message-ID: c10258ab0f
-------3c60188b$
To: <sip:anonymous@anonymous.invalid>
This SIP message clip highlights the following parameters: 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.
DateTime: 2015-02-24T06:48:25-00:00
NS: imdn <urn:ietf:params:imdn>
imdn.Message-ID: tZLoOeSS8nxrj0Pi4s7JGAyP9GUqJB
Content-Disposition: notification
Content-type: message/imdn+xml
Content-Length: 276
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.
<imdn xmlns="urn:ietf:params:xml:ns:imdn">
<message-id>dc5ebabb21</message-id>
<datetime>2015-02-24T06:48:25-00:00</datetime>
<delivery-notification>
<status>
<delivered/>
</status>
</delivery-notification>
</imdn>
-------r9n1kGghKfCnHKkwpgZNgV0f6s1$
MSRP r9n1kGghKfCnHKkwpgZNgV0f6s1 200
To-Path: msrp://[2001::1:4c16:9c0f:4986:9e6d]:8880/FmnP;tcp
From-Path: msrp://[2001:0000:0000:0001:0000:0000:0000:0002]:16000/558f02b9d0;tcp
-------r9n1kGghKfCnHKkwpgZNgV0f6s1$
Reference :
[1] RCC.07_RCS5_2_advanced_communications_specification_v5.0 - 3.3 1-to-1 Chat
[2] RCC.07_RCS5_2_advanced_communications_specification_v5.0 - 3.3.4.1 Technical Realization of 1-to-1 Chat features common to both OMA SIMPLE IM and OMA CPM
[3] RCC.07_RCS5_2_advanced_communications_specification_v5.0 - 3.3.4.2 Technical Realization of 1-to-1 Chat features when using OMA SIMPLE IM
[4] RCC.07_RCS5_2_advanced_communications_specification_v5.0 - 3.3.4.3 Technical Realization of 1-to-1 Chat features when using OMA CPM