Supplementary Service is a huge set of services that comprises of many different services as listed below. Since these are huge topics, it would take long time to complete this page. This is just initial post and continue to be updated.
|
Items |
References |
|
|
3GPP TS24.607 |
||
|
3GPP TS24.607 |
||
|
3GPP TS24.608 |
||
|
3GPP TS24.608 |
||
|
3GPP TS24.604 |
||
|
Communication Forwarding on Subscriber Not Reachable (CFNRc) |
||
|
3GPP TS24.610 |
||
|
3GPP TS24.615 |
||
|
3GPP TS24.605/147 |
||
| Message Waiting Indication (MWI) |
3GPP TS24.606 |
|
| Communication Barring |
3GPP TS24.611 |
|
|
Unstructured Supplementary Service Data (USSD) using IMS |
3GPP TS24.390 |
|
Originating Identification Presentation (OIP)
With this service, the terminating user (the Callee, the receiving party) can identify by the originating user ID displayed (Presented) on the display. That is, with OIP, the originating user (the Caller) can provide it's ID to be displayed on the terminating user (the Callee).
Originating Identification Restriction (OIR)
With this service, the originating user (the Caller) can prevent its ID from displayed (presented) on the display of the terminating user (the Callee)
Terminating Identification Presentation (TIP)
The Terminating Identification Presentation (TIP) service provides the originating party (the Caller) with the possibility of receiving identity information in order to identify the terminating party(the Callee).
The network shall deliver the Terminating Identity to the originating party on communication acceptance regardless of the terminal capability to handle the information.
Terminating Identification Restriction (TIR)
The Terminating Identification Restriction (TIR) is a service offered to the connected party which enables the connected party to prevent presentation of the terminating identity information to originating party.
This is a service that enable diverting an incoming call to some other destination. There are variations of this diversion and followings are the items described in 3GPP 24.604.
- Communication Forwarding Unconditional (CFU)
- Communication Forwarding on Busy user (CFB)
- Communication Forwarding on no Reply (CFNR)
- Communication Forwarding on Subscriber Not Reachable (CFNRc)
- Communication Deflection (CD)
- Communication Forwarding on Not Logged-in (CFNL)
- Communication Diversion Notification (CDIVN)
< Communication Forwarding Unconditional (CFU) >
Following is a example of Call Forwarding Test using a test system (Anritsu MD8475A). Brief description on UA is described below.
- UA1 : A test mobile phone with IMSdroid installed on it
- UA2 : Virtual UA embedded with the test system
- UA3 : A software based IMS UA running on a separate PC (Boghe : http://code.google.com/p/boghe/)
NOTE : Following sequence is just a high level view of the overall flow for simplicity. For more detailed sequence diagram, A.1.3 “Communication forwarding on no reply” of TS 24.604 (I think/hope the sequence in my note would be easier to follow and grasp the big picture. I would suggest you to understand the big picture here first and then refer to 24.604)
(A) SIP/SDP Request: INVITE sip:UA2@Sharetechnote-cscf.com | , with session description
INVITE sip:UA2@Sharetechnote-cscf.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.11:58475;branch=z9hG4bK250253573;rport
From: <sip:UA1@Sharetechnote-cscf.com>;tag=390680916
To: <sip:UA2@Sharetechnote-cscf.com>
Contact: <sip:UA1@192.168.1.11:58475;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Call-ID: 0452befc-bfd8-afe1-fff8-65286703bad9
CSeq: 1500260822 INVITE
Content-Type: application/sdp
Content-Length: 695
Max-Forwards: 70
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Accept-Contact, 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.
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 android-ngn-stack/v2.544.836 (doubango r836 - L-06D)
This SIP message clip highlights the following parameters: P-Access-Network-Info, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Preferred-Identity: <sip:user@Sharetechnote-cscf.com>
Supported: 100rel
v=0
o=doubango 1983 678901 IN IP4 192.168.1.11
s=-
c=IN IP4 192.168.1.11
t=0 0
a=tcap:1 RTP/AVPF
m=audio 11286 RTP/AVP 9 98 99 97 8 0 96 3 18 101
a=ptime:20
a=silenceSupp:off - - - -
a=rtpmap:9 G722/8000/1
a=rtpmap:98 SPEEX/16000/1
a=rtpmap:99 SPEEX/32000/1
a=rtpmap:97 SPEEX/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:96 iLBC/8000/1
a=fmtp:96 mode=20
a=rtpmap:3 GSM/8000/1
a=rtpmap:18 g729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-16
a=pcfg:1 t=1
a=sendrecv
a=rtcp-mux
a=ssrc:4050946750 cname:ldjWoB60jbyQlR6e
a=ssrc:4050946750 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2
a=ssrc:4050946750 label:Doubango.Audio
This SIP message clip highlights the following parameters: 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.
(B) SIP/SDP Request: INVITE sip:UA3@192.168.1.3:61657;transport=udp | , with session description
INVITE sip:UA3@192.168.1.3:61657;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:60971;branch=z9hG4bK07ec3b4acc4a4392a7bedaa6532051df8d;rport;transport=udp
Via: SIP/2.0/UDP 192.168.1.11:58475;branch=z9hG4bK250253573;rport=58475
From: <sip:UA1@Sharetechnote-cscf.com>;tag=390680916
To: <sip:UA2@Sharetechnote-cscf.com>
Contact: <sip:UA1@192.168.1.11:58475;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Call-ID: 0452befc-bfd8-afe1-fff8-65286703bad9
CSeq: 1500260822 INVITE
Content-Type: application/sdp
Content-Length: 695
Max-Forwards: 69
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Accept-Contact, 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.
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 android-ngn-stack/v2.544.836 (doubango r836 - L-06D)
Supported: 100rel
This SIP message clip highlights the following parameters: P-Access-Network-Info, Supported, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:user@Sharetechnote-cscf.com>
Record-Route: <sip:192.168.1.2;lr>
v=0
o=doubango 1983 678901 IN IP4 192.168.1.11
s=-
c=IN IP4 192.168.1.11
t=0 0
a=tcap:1 RTP/AVPF
m=audio 11286 RTP/AVP 9 98 99 97 8 0 96 3 18 101
a=ptime:20
a=silenceSupp:off - - - -
a=rtpmap:9 G722/8000/1
a=rtpmap:98 SPEEX/16000/1
a=rtpmap:99 SPEEX/32000/1
a=rtpmap:97 SPEEX/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:96 iLBC/8000/1
a=fmtp:96
< Communication Forwarding on Busy user (CFB) >
NOTE : Following sequence is just a high level view of the overall flow for simplicity. For more detailed sequence diagram, A.1.3 “Communication forwarding on no reply” of TS 24.604 (I think/hope the sequence in my note would be easier to follow and grasp the big picture. I would suggest you to understand the big picture here first and then refer to 24.604)
(A) INVITE sip:UA1@ims.mnc246.mcc081.3gppnetwork.org SIP/2.0
Via: SIP/2.0/TCP [2001:0:0:1::2]:58110;branch=z9hG4bK680245c87bed4ef089641f3f7cc62263f580f1da;transport=tcp
Max-Forwards: 70
Call-ID: c55a5d495a874c14bc886ec31edf3eef
CSeq: 18001 INVITE
To: sip:UA1@ims.mnc246.mcc081.3gppnetwork.org
From: sip:UA2@test.3gpp.com;tag=2222222222
This SIP message clip highlights the following parameters: Via, 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.
Feature-Caps: *;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";require;explicit
Privacy: none
User-Agent: Sharetechnote-VirtualUA/7e501f1
Content-Type: application/sdp
Content-Length: 727
Route: <sip:[2001:0:0:1::2]:28101;lr>
Contact: <sip:UA3@[2001:0:0:1::2]:58110;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
v=0
o=Sharetechnote 599 64599 IN IP6 2001:0:0:1::2
s=-
i=A VOIP Session
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 60002 RTP/AVP 96 97 98 99 100 8 0 101 102
This SIP message clip highlights the following parameters: Route, Contact, Content-Type, Content-Length, Accept-Contact, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
b=AS:153
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:240
a=rtpmap:96 EVS/16000/1
a=fmtp:96 max-red=220
a=rtpmap:97 AMR-WB/16000/1
a=fmtp:97 mode-change-capability=2
a=rtpmap:98 AMR-WB/16000/1
a=fmtp:98 octet-align=1; mode-change-capability=2
a=rtpmap:99 AMR/8000/1
a=fmtp:99 mode-change-capability=2
a=rtpmap:100 AMR/8000/1
a=fmtp:100 octet-align=1; mode-change-capability=2
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/16000
a=fmtp:101 0-15
a=rtpmap:102 telephone-event/8000
a=fmtp:102 0-15
a=mid:0
a=rtcp:60003
a=sendrecv
(C) SIP/2.0 486 Busy Here
Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bK73cbbac348344ef799e1ace1e004354486;rport;transport=udp
Via: SIP/2.0/TCP [2001:0:0:1::2]:58110;branch=z9hG4bK680245c87bed4ef089641f3f7cc62263f580f1da;transport=tcp
Max-Forwards: 70
This SIP message clip highlights the following parameters: Via, 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>
Contact: <sip:001010123456789@[2001:0:0:1::11]:5060>;+sip.instance="<urn:gsma:imei:35975507-290776-0>";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";+g.3gpp.mid-call;+g.3gpp.srvcc-alerting;+g.3gpp.ps2cs-srvcc-orig-pre-alerting;video
To: <sip:UA1@ims.mnc246.mcc081.3gppnetwork.org>;tag=7ce82475
From: <sip:UA3@test.3gpp.com>;tag=2222222222
Call-ID: c55a5d495a874c14bc886ec31edf3eef
CSeq: 18001 INVITE
Supported: timer, 100rel
User-Agent: T-Mobile VoLTE-ePDG-IR94 SEC/G930TUVU4Z 7.0
P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=0010100010000000
Content-Length: 0
This SIP message clip highlights the following parameters: Contact, CSeq, Call-ID, P-Access-Network-Info, From, To, Content-Length, Supported, 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.
(D) SIP/2.0 181 Call Is Being Forwarded
Max-Forwards: 70
Via: SIP/2.0/TCP [2001:0:0:1::2]:58110;branch=z9hG4bK680245c87bed4ef089641f3f7cc62263f580f1da;transport=tcp
From: sip:UA3@test.3gpp.com;tag=2222222222
To: sip:UA1@ims.mnc246.mcc081.3gppnetwork.org;tag=7ce82475
Call-ID: c55a5d495a874c14bc886ec31edf3eef
CSeq: 18001 INVITE
This SIP message clip highlights the following parameters: Via, 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.
History-Info: <sip:001010123456789@ims.mnc246.mcc081.3gppnetwork.org>; index=1
History-Info: <sip:001010123456789@ims.mnc246.mcc081.3gppnetwork.org>; index=1.1; NP=1
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.
(E) INVITE sip:UA4@[2001:0:0:1::2]:55899;transport=udp;cause=486 SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bK73cbbac348344ef799e1ace1e00435448b;rport;transport=udp
Via: SIP/2.0/TCP [2001:0:0:1::2]:58110;branch=z9hG4bK680245c87bed4ef089641f3f7cc62263f580f1da;transport=tcp
Max-Forwards: 69
Call-ID: c55a5d495a874c14bc886ec31edf3eef
CSeq: 18001 INVITE
To: sip:UA4@test.3gpp.com
From: sip:UA3@test.3gpp.com;tag=2222222222
This SIP message clip highlights the following parameters: Via, 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.
Feature-Caps: *;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";require;explicit
Privacy: none
User-Agent: Sharetechnote-VirtualUA/7e501f1
Content-Type: application/sdp
Content-Length: 727
Contact: <sip:UA3@[2001:0:0:1::2]:58110;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
This SIP message clip highlights the following parameters: Contact, Content-Type, Content-Length, Accept-Contact, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:VirtualUA_2nd@test.3gpp.com>
History-Info: <sip:001010123456789@ims.mnc246.mcc081.3gppnetwork.org>; index=1
History-Info: <sip:001010123456789@ims.mnc246.mcc081.3gppnetwork.org>; index=1.1; NP=1
History-Info: <sip:123456789@test.3gpp.com?cause=486>; index=1.2; MP=1.1
Record-Route: <sip:[2001:0:0:1::2]:5060;lr>
v=0
o=Sharetechnote 599 64599 IN IP6 2001:0:0:1::2
s=-
i=A VOIP Session
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 60002 RTP/AVP 96 97 98 99 100 8 0 101 102
b=AS:153
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:240
a=rtpmap:96 EVS/16000/1
a=fmtp:96 max-red=220
a=rtpmap:97 AMR-WB/16000/1
a=fmtp:97 mode-change-capability=2
a=rtpmap:98 AMR-WB/16000/1
a=fmtp:98 octet-align=1; mode-change-capability=2
a=rtpmap:99 AMR/8000/1
a=fmtp:99 mode-change-capability=2
a=rtpmap:100 AMR/8000/1
a=fmtp:100 octet-align=1; mode-change-capability=2
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/16000
a=fmtp:101 0-15
a=rtpmap:102 telephone-event/8000
a=fmtp:102 0-15
a=mid:0
a=rtcp:60003
a=sendrecv
< Communication Forwarding on no Reply (CFNR) >
NOTE : Following sequence is just a high level view of the overall flow for simplicity. For more detailed sequence diagram, A.1.3 “Communication forwarding on no reply” of TS 24.604 (I think/hope the sequence in my note would be easier to follow and grasp the big picture. I would suggest you to understand the big picture here first and then refer to 24.604)
(A) INVITE sip:UA1@ims.mnc246.mcc081.3gppnetwork.org SIP/2.0
Via: SIP/2.0/TCP [2001:0:0:1::2]:59417;branch=z9hG4bK62bc484e8cdd4ddc8e563c19815bf51aac5bd1e1;transport=tcp
Max-Forwards: 70
Call-ID: cf01b053c04a414ab24990140d4d2297
CSeq: 38001 INVITE
To: sip:UA1@ims.mnc246.mcc081.3gppnetwork.org
From: sip:UA2@ims.mnc246.mcc081.3gppnetwork.org;tag=1111111111
This SIP message clip highlights the following parameters: Via, 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.
Feature-Caps: *;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";require;explicit
Privacy: none
User-Agent: Sharetechnote-VirtualUA/7e501f1
Content-Type: application/sdp
Content-Length: 728
Route: <sip:[2001:0:0:1::2]:28101;lr>
Contact: <sip:UA2@[2001:0:0:1::2]:59417;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
v=0
o=Sharetechnote 583 102583 IN IP6 2001:0:0:1::2
s=-
i=A VOIP Session
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 60000 RTP/AVP 96 97 98 99 100 8 0 101 102
This SIP message clip highlights the following parameters: Route, Contact, Content-Type, Content-Length, Accept-Contact, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
b=AS:153
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:240
a=rtpmap:96 EVS/16000/1
a=fmtp:96 max-red=220
a=rtpmap:97 AMR-WB/16000/1
a=fmtp:97 mode-change-capability=2
a=rtpmap:98 AMR-WB/16000/1
a=fmtp:98 octet-align=1; mode-change-capability=2
a=rtpmap:99 AMR/8000/1
a=fmtp:99 mode-change-capability=2
a=rtpmap:100 AMR/8000/1
a=fmtp:100 octet-align=1; mode-change-capability=2
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/16000
a=fmtp:101 0-15
a=rtpmap:102 telephone-event/8000
a=fmtp:102 0-15
a=mid:0
a=rtcp:60001
a=sendrecv
(C) 180 Ringing
Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bKc7d5dede360c4bb5a88be02f843e7c4598;rport;transport=udp
Via: SIP/2.0/TCP [2001:0:0:1::2]:59417;branch=z9hG4bK62bc484e8cdd4ddc8e563c19815bf51aac5bd1e1;transport=tcp
Max-Forwards: 70
This SIP message clip highlights the following parameters: Via, 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>
Contact: <sip:UA1@[2001:0:0:1::11]:5060>;+sip.instance="<urn:gsma:imei:35975507-290776-0>";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";+g.3gpp.mid-call;+g.3gpp.srvcc-alerting;+g.3gpp.ps2cs-srvcc-orig-pre-alerting;video
To: <sip:UA1@ims.mnc246.mcc081.3gppnetwork.org>;tag=c0eff945
From: <sip:UA2@ims.mnc246.mcc081.3gppnetwork.org>;tag=1111111111
Call-ID: cf01b053c04a414ab24990140d4d2297
CSeq: 38001 INVITE
Supported: timer, 100rel
User-Agent: T-Mobile VoLTE-ePDG-IR94 SEC/G930TUVU4Z 7.0
P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=0010100010000000
Content-Length: 0
This SIP message clip highlights the following parameters: Contact, CSeq, Call-ID, P-Access-Network-Info, From, To, Content-Length, Supported, 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.
(D) 180 Ringing
Via: SIP/2.0/TCP [2001:0:0:1::2]:59417;branch=z9hG4bK62bc484e8cdd4ddc8e563c19815bf51aac5bd1e1;transport=tcp
Max-Forwards: 70
This SIP message clip highlights the following parameters: Via, 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]:28101;lr>
Contact: <sip:UA1@[2001:0:0:1::11]:5060>;+sip.instance="<urn:gsma:imei:35975507-290776-0>";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";+g.3gpp.mid-call;+g.3gpp.srvcc-alerting;+g.3gpp.ps2cs-srvcc-orig-pre-alerting;video
To: <sip:UA1@ims.mnc246.mcc081.3gppnetwork.org>;tag=c0eff945
From: <sip:UA2@ims.mnc246.mcc081.3gppnetwork.org>;tag=1111111111
Call-ID: cf01b053c04a414ab24990140d4d2297
CSeq: 38001 INVITE
Supported: timer, 100rel
User-Agent: T-Mobile VoLTE-ePDG-IR94 SEC/G930TUVU4Z 7.0
P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=0010100010000000
Content-Length: 0
This SIP message clip highlights the following parameters: Contact, CSeq, Call-ID, P-Access-Network-Info, From, To, Content-Length, Supported, 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.
(E) CANCEL sip:UA1@[2001:0:0:1::11]:5060 SIP/2.0
Max-Forwards: 70
Call-ID: cf01b053c04a414ab24990140d4d2297
CSeq: 38001 CANCEL
To: sip:UA1@ims.mnc246.mcc081.3gppnetwork.org
From: sip:UA2@ims.mnc246.mcc081.3gppnetwork.org;tag=1111111111
Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bKc7d5dede360c4bb5a88be02f843e7c4598;rport;transport=udp
Via: SIP/2.0/TCP [2001:0:0:1::2]:59417;branch=z9hG4bK62bc484e8cdd4ddc8e563c19815bf51aac5bd1e1;transport=tcp
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.
(F) 181 Call Is Being Forwarded
Max-Forwards: 70
Via: SIP/2.0/TCP [2001:0:0:1::2]:59417;branch=z9hG4bK62bc484e8cdd4ddc8e563c19815bf51aac5bd1e1;transport=tcp
From: sip:UA2@ims.mnc246.mcc081.3gppnetwork.org;tag=1111111111
To: sip:UA1@ims.mnc246.mcc081.3gppnetwork.org;tag=c0eff945
Call-ID: cf01b053c04a414ab24990140d4d2297
CSeq: 38001 INVITE
This SIP message clip highlights the following parameters: Via, 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.
History-Info: <sip:UA1@ims.mnc246.mcc081.3gppnetwork.org>; index=1
History-Info: <sip:UA1@ims.mnc246.mcc081.3gppnetwork.org>; index=1.1; NP=1
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.
(G) INVITE sip:UA3@[2001:0:0:1::2]:54990;transport=udp;cause=408 SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bKc7d5dede360c4bb5a88be02f843e7c459d;rport;transport=udp
Via: SIP/2.0/TCP [2001:0:0:1::2]:59417;branch=z9hG4bK62bc484e8cdd4ddc8e563c19815bf51aac5bd1e1;transport=tcp
Max-Forwards: 69
Call-ID: cf01b053c04a414ab24990140d4d2297
CSeq: 38001 INVITE
To: sip:UA3@test.3gpp.com
From: sip:UA2@ims.mnc246.mcc081.3gppnetwork.org;tag=1111111111
This SIP message clip highlights the following parameters: Via, 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.
Feature-Caps: *;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";require;explicit
User-Agent: Sharetechnote-VirtualUA/7e501f1
Content-Type: application/sdp
Content-Length: 728
Contact: <sip:UA2@[2001:0:0:1::2]:59417;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Privacy: none
This SIP message clip highlights the following parameters: Contact, Content-Type, Content-Length, Accept-Contact, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:UA2@ims.mnc246.mcc081.3gppnetwork.org>
History-Info: <sip:UA1@ims.mnc246.mcc081.3gppnetwork.org>; index=1
History-Info: <sip:UA1@ims.mnc246.mcc081.3gppnetwork.org>; index=1.1; NP=1
< Communication Forwarding on Subscriber Not Reachable (CFNRc) >
(A) INVITE sip:UA2@ims.mnc246.mcc081.3gppnetwork.org SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:56439;branch=z9hG4bK1161335930;rport
From: <sip:UA1@test.3gpp.com>;tag=1161341877
To: <sip:UA2@ims.mnc246.mcc081.3gppnetwork.org>
Contact: <sip:UA1@[2001:0:0:1::2]:56439;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Call-ID: bdc0cdba-3278-1303-7151-eada26d4de3a
CSeq: 21140 INVITE
Content-Type: application/sdp
Content-Length: 739
Max-Forwards: 70
Route: <sip:[2001:0:0:1::2]:5060;lr;transport=udp>
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
This SIP message clip highlights the following parameters: Via, Route, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Accept-Contact, 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.
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.112.744
This SIP message clip highlights the following parameters: P-Access-Network-Info, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Preferred-Identity: <sip:123456789@test.3gpp.com>
Supported: 100rel
v=0
o=doubango 1983 678901 IN IP6 2001:0:0:1::2
s=-
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 8048 RTP/AVP 112 111 3 8 0 9 97 98 99 101
a=ptime:20
a=rtpmap:112 AMR/8000/1
a=imageattr:112 octet-align=1
a=fmtp:112 octet-align=1
a=rtpmap:111 AMR/8000/1
a=imageattr:111 octet-align=0
a=fmtp:111 octet-align=0
a=rtpmap:3 GSM/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:9 G722/8000/1
a=rtpmap:97 SPEEX/8000/1
a=rtpmap:98 SPEEX/16000/1
a=rtpmap:99 SPEEX/32000/1
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15
a=tcap:1 RTP/AVPF
a=pcfg:1 t=1
a=sendrecv
a=rtcp-mux
a=ssrc:1311262921 cname:ldjWoB60jbyQlR6e
a=ssrc:1311262921 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2
a=ssrc:1311262921 label:Doubango
This SIP message clip highlights the following parameters: 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.
(B) 181 Call Is Being Forwarded
Max-Forwards: 70
Via: SIP/2.0/UDP [2001:0:0:1::2]:56439;branch=z9hG4bK1161335930;rport=56439
From: <sip:UA1@test.3gpp.com>;tag=1161341877
To: <sip:UA2@ims.mnc246.mcc081.3gppnetwork.org>;tag=987654321
Call-ID: bdc0cdba-3278-1303-7151-eada26d4de3a
CSeq: 21140 INVITE
This SIP message clip highlights the following parameters: Via, 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.
History-Info: <sip:001010123456789@ims.mnc246.mcc081.3gppnetwork.org>; index=1
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.
(C) INVITE sip:UA3@[2001:0:0:1::2]:49329;transport=udp;cause=503 SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:28101;branch=z9hG4bKbf2ece8e7f3e42539582fdba3875fe9d198;rport;transport=udp
Via: SIP/2.0/UDP [2001:0:0:1::2]:56439;branch=z9hG4bK1161335930;rport=56439
From: <sip:UA1@test.3gpp.com>;tag=1161341877
To: <sip:UA3@ims.mnc246.mcc081.3gppnetwork.org>
Contact: <sip:UA1@[2001:0:0:1::2]:56439;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Call-ID: bdc0cdba-3278-1303-7151-eada26d4de3a
CSeq: 21140 INVITE
Content-Type: application/sdp
Content-Length: 739
Max-Forwards: 69
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Accept-Contact, 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.
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.112.744
Supported: 100rel
This SIP message clip highlights the following parameters: P-Access-Network-Info, Supported, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:123456789@test.3gpp.com>
History-Info: <sip:UA2@ims.mnc246.mcc081.3gppnetwork.org>; index=1
History-Info: <sip:UA3@ims.mnc246.mcc081.3gppnetwork.org?cause=503>; index=1.1; MP=1
Record-Route: <sip:[2001:0:0:1::2]:28101;lr>
v=0
o=doubango 1983 678901 IN IP6 2001:0:0:1::2
s=-
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 8048 RTP/AVP 112 111 3 8 0 9 97 98 99 101
a=ptime:20
a=rtpmap:112 AMR/8000/1
a=imageattr:112 octet-align=1
a=fmtp:112 octet-align=1
a=rtpmap:111 AMR/8000/1
a=imageattr:111 octet-align=0
a=fmtp:111 octet-align=0
a=rtpmap:3 GSM/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:9 G722/8000/1
a=rtpmap:97 SPEEX/8000/1
a=rtpmap:98 SPEEX/16000/1
a=rtpmap:99 SPEEX/32000/1
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15
a=tcap:1 RTP/AVPF
a=pcfg:1 t=1
a=sendrecv
a=rtcp-mux
a=ssrc:1311262921 cname:ldjWoB60jbyQlR6e
a=ssrc:1311262921 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2
a=ssrc:1311262921 label:Doubango
< Communication Deflection (CD) >
< Communication Forwarding on Not Logged-in (CFNL) >
(A) INVITE sip:UA2@test.3gpp.com SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:50329;branch=z9hG4bK996978744;rport
From: <sip:UA1@test.3gpp.com>;tag=996990843
To: <sip:UA2@test.3gpp.com>
Contact: <sip:UA1@[2001:0:0:1::2]:50329;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Call-ID: 8c8faa31-bf9c-3adf-fb9e-1571d98e4073
CSeq: 8139 INVITE
Content-Type: application/sdp
Content-Length: 740
Max-Forwards: 70
Route: <sip:[2001:0:0:1::2]:5060;lr;transport=udp>
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
This SIP message clip highlights the following parameters: Via, Route, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Accept-Contact, 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.
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.112.744
This SIP message clip highlights the following parameters: P-Access-Network-Info, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Preferred-Identity: <sip:123456789@test.3gpp.com>
Supported: 100rel
v=0
o=doubango 1983 678901 IN IP6 2001:0:0:1::2
s=-
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 26306 RTP/AVP 112 111 3 8 0 9 97 98 99 101
a=ptime:20
a=rtpmap:112 AMR/8000/1
a=imageattr:112 octet-align=1
a=fmtp:112 octet-align=1
a=rtpmap:111 AMR/8000/1
a=imageattr:111 octet-align=0
a=fmtp:111 octet-align=0
a=rtpmap:3 GSM/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:9 G722/8000/1
a=rtpmap:97 SPEEX/8000/1
a=rtpmap:98 SPEEX/16000/1
a=rtpmap:99 SPEEX/32000/1
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15
a=tcap:1 RTP/AVPF
a=pcfg:1 t=1
a=sendrecv
a=rtcp-mux
a=ssrc:1146886926 cname:ldjWoB60jbyQlR6e
a=ssrc:1146886926 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2
a=ssrc:1146886926 label:Doubango
This SIP message clip highlights the following parameters: 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.
(B) 181 Call Is Being Forwarded
Max-Forwards: 70
Via: SIP/2.0/UDP [2001:0:0:1::2]:50329;branch=z9hG4bK996978744;rport=50329
From: <sip:UA1@test.3gpp.com>;tag=996990843
To: <sip:UA2@test.3gpp.com>;tag=987654321
Call-ID: 8c8faa31-bf9c-3adf-fb9e-1571d98e4073
CSeq: 8139 INVITE
This SIP message clip highlights the following parameters: Via, 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.
History-Info: <sip:223456789@test.3gpp.com>; index=1
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.
(C) INVITE sip:UA3@[2001:0:0:1::11]:5060;cause=404 SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bKe5a451b9d19443a79242368f24597c6111d;rport;transport=udp
Via: SIP/2.0/UDP [2001:0:0:1::2]:50329;branch=z9hG4bK996978744;rport=50329
From: <sip:UA1@test.3gpp.com>;tag=996990843
To: <sip:UA3@ims.mnc246.mcc081.3gppnetwork.org>
Contact: <sip:UA1@[2001:0:0:1::2]:50329;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Call-ID: 8c8faa31-bf9c-3adf-fb9e-1571d98e4073
CSeq: 8139 INVITE
Content-Type: application/sdp
Content-Length: 740
Max-Forwards: 69
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Accept-Contact, 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.
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.112.744
Supported: 100rel
This SIP message clip highlights the following parameters: P-Access-Network-Info, Supported, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:123456789@test.3gpp.com>
History-Info: <sip:223456789@test.3gpp.com>; index=1
History-Info: <sip:001010123456789@ims.mnc246.mcc081.3gppnetwork.org?cause=404>; index=1.1; MP=1
Record-Route: <sip:[2001:0:0:1::2]:5060;lr>
v=0
o=doubango 1983 678901 IN IP6 2001:0:0:1::2
s=-
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 26306 RTP/AVP 112 111 3 8 0 9 97 98 99 101
a=ptime:20
a=rtpmap:112 AMR/8000/1
a=imageattr:112 octet-align=1
a=fmtp:112 octet-align=1
a=rtpmap:111 AMR/8000/1
a=imageattr:111 octet-align=0
a=fmtp:111 octet-align=0
a=rtpmap:3 GSM/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:9 G722/8000/1
a=rtpmap:97 SPEEX/8000/1
a=rtpmap:98 SPEEX/16000/1
a=rtpmap:99 SPEEX/32000/1
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15
a=tcap:1 RTP/AVPF
a=pcfg:1 t=1
a=sendrecv
a=rtcp-mux
a=ssrc:1146886926 cname:ldjWoB60jbyQlR6e
a=ssrc:1146886926 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2
a=ssrc:1146886926 label:Doubango
This service enables a user to suspend the reception of media stream(s) of an established IP multimedia session, and resume the media stream(s) at a later time.
Following is a example of Call Forwarding Test using a test system (Anritsu MD8475A). Brief description on UA is described below.
- UA1 : Virtual UA embedded with the test system
- UA2 : A test mobile phone with IMSdroid installed on it
- UA3 : A software based IMS UA running on a separate PC (Boghe : http://code.google.com/p/boghe/)
(A) INVITE sip:UA2@192.168.1.11:51948;transport=udp | , with session description
Via: SIP/2.0/UDP 192.168.1.2:64941;branch=z9hG4bK07ec3b4acc4a4392a7bedaa6532051dfcf;rport;transport=udp
Via: SIP/2.0/UDP 192.168.1.2:64869;branch=z9hG4bK81f111044c244f838fab83c8fc8fc263b01b1496;rport=64873
Max-Forwards: 69
Call-ID: 64b52f7a86a64c25ba59ac07f01604e8
CSeq: 42001 INVITE
To: <sip:UA2@Sharetechnote-cscf.com>
From: <sip:UA1@Sharetechnote-cscf.com>;tag=1111111111
Allow: INVITE, PRACK, UPDATE, ACK, BYE, CANCEL
Supported: 100rel
Supported: precondition
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";require;explicit
User-Agent: Sharetechnote-VirtualUA/3834
Content-Type: application/sdp
Content-Length: 571
Contact: <sip:UA1@192.168.1.2:64869;transport=udp>
Privacy: none
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Accept-Contact, Max-Forwards, Supported, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:UA1@Sharetechnote-cscf.com>
Record-Route: <sip:192.168.1.2;lr>
v=0
o=Sharetechnote 420 856420 IN IP4 192.168.1.2
s=-
i=A VOIP Session
c=IN IP4 192.168.1.2
t=0 0
m=audio 60000 RTP/AVP 107 97 8 0 101
b=AS:64
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:20
a=rtpmap:107 AMR-WB/16000
a=fmtp:107 octet-align=1; mode-set=2
a=rtpmap:97 AMR/8000
a=fmtp:97 octet-align=1; mode-set=7
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=mid:0
a=sendrecv
a=rtcp:60001
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos optional remote sendrecv
(B) INVITE sip:UA2@192.168.1.11:51948;transport=udp SIP/2.0
INVITE sip:UA2@192.168.1.11:51948;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:64943;branch=z9hG4bK07ec3b4acc4a4392a7bedaa6532051dfd5;rport;transport=udp
Via: SIP/2.0/UDP 192.168.1.2:64869;branch=z9hG4bK81f111044c244f838fab83c8fc8fc263c24ec6e7;rport=64873
Max-Forwards: 69
Call-ID: 64b52f7a86a64c25ba59ac07f01604e8
CSeq: 42003 INVITE
To: <sip:UA2@Sharetechnote-cscf.com>;tag=340649356
From: <sip:UA1@Sharetechnote-cscf.com>;tag=1111111111
Allow: INVITE, PRACK, UPDATE, ACK, BYE, CANCEL
User-Agent: Sharetechnote-VirtualUA/3834
Content-Type: application/sdp
Content-Length: 321
Contact: <sip:UA1@192.168.1.2:64869;transport=udp>
Privacy: none
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Max-Forwards, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:UA1@Sharetechnote-cscf.com>
Record-Route: <sip:192.168.1.2;lr>
v=0
o=Sharetechnote 420 856422 IN IP4 192.168.1.2
s=-
i=A VOIP Session
c=IN IP4 192.168.1.2
t=0 0
m=audio 60000 RTP/AVP 8 0 101
b=AS:64
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:20
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=mid:0
a=sendonly
a=rtcp:60001
(C) INVITE sip:UA2@192.168.1.11:51948;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:64945;branch=z9hG4bK07ec3b4acc4a4392a7bedaa6532051dfd9;rport;transport=udp
Via: SIP/2.0/UDP 192.168.1.2:64869;branch=z9hG4bK81f111044c244f838fab83c8fc8fc263a57af679;rport=64873
Max-Forwards: 69
Call-ID: 64b52f7a86a64c25ba59ac07f01604e8
CSeq: 42004 INVITE
To: <sip:UA2@Sharetechnote-cscf.com>;tag=340649356
From: <sip:UA1@Sharetechnote-cscf.com>;tag=1111111111
Allow: INVITE, PRACK, UPDATE, ACK, BYE, CANCEL
User-Agent: Sharetechnote-VirtualUA/3834
Content-Type: application/sdp
Content-Length: 321
Contact: <sip:UA1@192.168.1.2:64869;transport=udp>
Privacy: none
This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Max-Forwards, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:UA1@Sharetechnote-cscf.com>
Record-Route: <sip:192.168.1.2;lr>
v=0
o=Sharetechnote 420 856424 IN IP4 192.168.1.2
s=-
i=A VOIP Session
c=IN IP4 192.168.1.2
t=0 0
m=audio 60000 RTP/AVP 8 0 101
b=AS:64
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:20
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=mid:0
a=sendrecv
a=rtcp:60001
This service enables a UE to be informed that no resources are available for an incoming communication. The user then has the choice of accepting, rejecting or ignoring the incoming communication.
(A) INVITE sip:001010123456789@[2001::1:d279:3516:72e6:fa46]:39047 SIP/2.0
INVITE sip:001010123456789@[2001::1:d279:3516:72e6:fa46]:39047 SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:65211;branch=z9hG4bK7274b6a822524ffa...;transport=udp
Via: SIP/2.0/TCP [2001:0:0:1::2]:50626;branch=z9hG4bKe16b0a51e196416...;transport=tcp
Max-Forwards: 69
Call-ID: 1e73797a14b14c7eb85e33e3e4b628ea
CSeq: 30001 INVITE
To: sip:001010123456789@ims.mnc01.mcc001.3gppnetwork.org
From: sip:0123456789@ims.mnc01.mcc001.3gppnetwork.org;tag=1111111111
This SIP message clip highlights the following parameters: Via, 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.
Feature-Caps: *;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";require;explicit
User-Agent: UA2/9dc040f
Content-Type: application/sdp
Content-Length: 727
Contact: <sip:0123456789@[2001:0:0:1::2]:50626;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Privacy: none
This SIP message clip highlights the following parameters: Contact, Content-Type, Content-Length, Accept-Contact, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:0123456789@ims.mnc01.mcc001.3gppnetwork.org>
Record-Route: <sip:[2001:0:0:1::2]:65211;lr>
v=0
o=Sharetechnote 164 63164 IN IP6 2001:0:0:1::2
s=-
i=A VOIP Session
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 60000 RTP/AVP 96 97 98 99 100 8 0 101 102
b=AS:153
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:240
a=rtpmap:96 EVS/16000/1
a=fmtp:96 max-red=220
a=rtpmap:97 AMR-WB/16000/1
a=fmtp:97 mode-change-capability=2
a=rtpmap:98 AMR-WB/16000/1
a=fmtp:98 octet-align=1; mode-change-capability=2
a=rtpmap:99 AMR/8000/1
a=fmtp:99 mode-change-capability=2
a=rtpmap:100 AMR/8000/1
a=fmtp:100 octet-align=1; mode-change-capability=2
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/16000
a=fmtp:101 0-15
a=rtpmap:102 telephone-event/8000
a=fmtp:102 0-15
a=mid:0
a=rtcp:60001
a=sendrecv
(B) INVITE sip:001010123456789@[2001::1:d279:3516:72e6:fa46]:39047 SIP/2.0
INVITE sip:001010123456789@[2001::1:d279:3516:72e6:fa46]:39047 SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:65211;branch=z9hG4bK7274b6a822524ffa838...;transport=udp
Via: SIP/2.0/TCP [2001:0:0:1::2]:50628;branch=z9hG4bK3234f01ce09b445aa5...;transport=tcp
Max-Forwards: 69
Call-ID: bf653744ce1d4b83ae0ccebdfad4e14d
CSeq: 52001 INVITE
To: sip:001010123456789@ims.mnc01.mcc001.3gppnetwork.org
From: sip:VirtualUA_2nd@test.3gpp.com;tag=2222222222
This SIP message clip highlights the following parameters: Via, 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.
Feature-Caps: *;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";require;explicit
Privacy: none
User-Agent: UA3/9dc040f
Content-Type: application/sdp
Content-Length: 728
Contact: <sip:VirtualUA_2nd@[2001:0:0:1::2]:50628;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
This SIP message clip highlights the following parameters: Contact, Content-Type, Content-Length, Accept-Contact, Allow, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:UA3@test.3gpp.com>
Record-Route: <sip:[2001:0:0:1::2]:65211;lr>
v=0
o=Sharetechnote 960 775960 IN IP6 2001:0:0:1::2
s=-
i=A VOIP Session
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 60002 RTP/AVP 96 97 98 99 100 8 0 101 102
b=AS:153
b=RS:800
b=RR:2400
a=ptime:20
a=maxptime:240
a=rtpmap:96 EVS/16000/1
a=fmtp:96 max-red=220
a=rtpmap:97 AMR-WB/16000/1
a=fmtp:97 mode-change-capability=2
a=rtpmap:98 AMR-WB/16000/1
a=fmtp:98 octet-align=1; mode-change-capability=2
a=rtpmap:99 AMR/8000/1
a=fmtp:99 mode-change-capability=2
a=rtpmap:100 AMR/8000/1
a=fmtp:100 octet-align=1; mode-change-capability=2
a=rtpmap:8 PCMA/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/16000
a=fmtp:101 0-15
a=rtpmap:102 telephone-event/8000
a=fmtp:102 0-15
a=mid:0
a=rtcp:60003
a=sendrecv
(C) INVITE sip:0123456789@[2001:0:0:1::2]:50626;transport=tcp SIP/2.0
INVITE sip:0123456789@[2001:0:0:1::2]:50626;transport=tcp SIP/2.0
Max-Forwards: 70
Route: <sip:[2001:0:0:1::2]:65211;lr>
Via: SIP/2.0/TCP [2001::1:d279:3516:72e6:fa46]:39047;branch=z9hG4bK150087668-37dae110
Call-ID: 1e73797a14b14c7eb85e33e3e4b628ea
CSeq: 1 INVITE
From: <sip:001010123456789@ims.mnc01.mcc001.3gppnetwork.org>;tag=5446714287d456-5e34ced8
To: <sip:0123456789@ims.mnc01.mcc001.3gppnetwork.org>;tag=1111111111
Contact: <sip:001010123456789@[2001::1:d279:3516:72e6:fa46]:39047>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+sip.instance="<urn:gsma:imei:35910506-000422-0>"
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video
Allow: INVITE,BYE,CANCEL,ACK,PRACK,UPDATE,INFO,REFER,NOTIFY,MESSAGE
This SIP message clip highlights the following parameters: Via, Route, Contact, CSeq, Call-ID, From, To, Accept-Contact, Max-Forwards, 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.
P-Preferred-Identity: <sip:001010123456789@ims.mnc01.mcc001.3gppnetwork.org>
P-Access-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=0010100010000000
This SIP message clip highlights the following parameters: P-Access-Network-Info. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
Security-Verify: ipsec-3gpp;q=0.1;alg=hmac-md5-96;prot=esp;mod=trans;ealg=null;spi-c=3854453982;spi-s=1494228412;port-c=65210;port-s=65211
Require: sec-agree
Supported: 100rel,timer
User-Agent: UA1
Proxy-Require: sec-agree
Content-Length: 648
Content-Type: application/sdp
v=0
o=sip:001010123456789@ims.mnc01.mcc001.3gppnetwork.org 3690753268 3690753269 IN IP6 2001:0:0:1::11
s=-
c=IN IP6 2001:0:0:1::11
t=0 0
m=audio 50010 RTP/AVP 97 98 99 100 101 102
This SIP message clip highlights the following parameters: Content-Type, Content-Length, Supported, User-Agent, Require, Proxy-Require. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
b=AS:49
b=RS:0
b=RR:1200
a=rtpmap:97 AMR-WB/16000/1
a=fmtp:97 mode-change-capability=2
a=rtpmap:98 AMR-WB/16000/1
a=fmtp:98 octet-align=1; mode-change-capability=2
a=rtpmap:99 telephone-event/16000
a=fmtp:99 0-15
a=rtpmap:100 AMR/8000/1
a=fmtp:100 mode-change-capability=2
a=rtpmap:101 AMR/8000/1
a=fmtp:101 octet-align=1; mode-change-capability=2
a=rtpmap:102 telephone-event/8000
a=fmtp:102 0-15
a=mid:0
a=sendonly
a=ptime:20
a=maxptime:240
(D) SIP/2.0 200 OK
SIP/2.0 200 OK
Max-Forwards: 70
Via: SIP/2.0/TCP [2001::1:d279:3516:72e6:fa46]:39047;branch=z9hG4bK150087668-37dae110
From: <sip:001010123456789@ims.mnc01.mcc001.3gppnetwork.org>;tag=5446714287d456-5e34ced8
To: <sip:0123456789@ims.mnc01.mcc001.3gppnetwork.org>;tag=1111111111
Call-ID: 1e73797a14b14c7eb85e33e3e4b628ea
CSeq: 1 INVITE
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
This SIP message clip highlights the following parameters: Via, CSeq, Call-ID, From, To, Max-Forwards, 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]:65211;lr>
User-Agent: UA2/9dc040f
Content-Type: application/sdp
Content-Length: 336
Contact: <sip:0123456789@[2001:0:0:1::2]:50626;transport=tcp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Privacy: none
This SIP message clip highlights the following parameters: Contact, Content-Type, Content-Length, User-Agent, Privacy. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
P-Asserted-Identity: <sip:0123456789@ims.mnc01.mcc001.3gppnetwork.org>
v=0
o=Sharetechnote 164 63166 IN IP6 2001:0:0:1::2
s=-
i=A VOIP Session
c=IN IP6 2001:0:0:1::2
t=0 0
m=audio 60000 RTP/AVP 97 99
b=AS:49
b=RS:0
b=RR:1200
a=rtpmap:97 AMR-WB/16000/1
a=fmtp:97 mode-change-capability=2
a=rtpmap:99 telephone-event/16000
a=fmtp:99 0-15
a=mid:0
a=ptime:20
a=maxptime:240
a=recvonly
a=rtcp:60001
(E) ACK sip:0123456789@[2001:0:0:1::2]:50626;transport=tcp SIP/2.0
ACK sip:0123456789@[2001:0:0:1::2]:50626;transport=tcp SIP/2.0
Max-Forwards: 70
Route: <sip:[2001:0:0:1::2]:65211;lr>
Via: SIP/2.0/UDP [2001::1:d279:3516:72e6:fa46]:39047;branch=z9hG4bK15009b44d-410bdd5b
Call-ID: 1e73797a14b14c7eb85e33e3e4b628ea
CSeq: 1 ACK
From: <sip:001010123456789@ims.mnc01.mcc001.3gppnetwork.org>;tag=5446714287d456-5e34ced8
To: <sip:0123456789@ims.mnc01.mcc001.3gppnetwork.org>;tag=1111111111
Allow: INVITE,BYE,CANCEL,ACK,PRACK,UPDATE,INFO,REFER,NOTIFY,MESSAGE
Require: sec-agree
User-Agent: UA1
Proxy-Require: sec-agree
Content-Length: 0
This SIP message clip highlights the following parameters: Via, Route, CSeq, Call-ID, From, To, Content-Length, Max-Forwards, Allow, User-Agent, Require, Proxy-Require. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.
This service enables a user to participate in and control a simultaneous communication involving a number of users.
When the CONF service is invoked, conference resources are allocated to the served user.
Once a conference is active, users can join and leave a conference, and remote users can be added to or removed from the conference.
Conference participants can request to be informed of these actions.
Message Waiting Indication (MWI)
With this service, NW can inform a subscriber that there is at least one waiting message. In order for the subscribe to use this service, it has to have subscription to MWI service.
Communication Barring (CB) is a service that can bar a certain call. This can be performed in several different context as described in 24.611.
- Incoming Communication Barring (ICB)
- Anonymous Communication Rejection (ACR)
- Outgoing Communication Barring (OCB)