Quick Reference for VoLTE over IMS

LTE Quick Reference - VoLTE over IMS Go Back To Index Home : www.
sharetechnote

VoLTE literally stands for "Voice over LTE". But when people say "VoLTE" (in abbreviation) it usually me
LTE utilizing IMS". (You would need to read the context to figure out what they say. Are they talking ab
voice technology implementation over LTE' or "Voice over LTE utilizing IMS" ?)

Theoretically you can use the IP/SIP based application for voice call on LTE as you do with your PC and
Then what would be the difference between VoLTE and generic IP based voice call. The simple answer is
IMS can be specially optimized for voice traffic not only in terms of core network but also in terms of rad
whereas generic IP based voice call is just 'best effort' type of application which can hardly be optimized
and no guaranteed quality of service.

When we are thinking about VoLTE, we have to look into two layers. One is about Application Layer (SIP
the other one is about Access Network Layer (Radio Layer).

Following is the topics that I will talk about in this page.
 SIP/IMS Transaction - Overall SIP/IMS Sequence
 Radio Layer Configuration
 NAS Messages - Related to IMS/VoLTE
 Example 1 : Overal Procedure for VoLTE (Both Radio Signaling and IMS Signaling)

SIP/IMS Transaction - Overall SIP/IMS Sequence

One common transaction for VoLTE at SIP/IMS layer would be as shown below, but the detailed implem
vary on the requirement from Carriers.

Following is a very basic SIP sequence from IMS Registration through VoLTE. This log were captured un
conditon. (With VoLTE in real network, you would not see this kind of simplified log since most of live ne
enable Authentication and require Precondition)
 Authentication = OFF
 Precondition = OFF

Actually each of the SIP message shown above has a lot of details and desribed acorss multiple specifica
interested in more details of each of these messages and parameters, refer to following links
 No Precondition (including IMS Registration with Authentication) : MO Call/MO Release-Plain Tex
 Precondition /Full Sequence Example 1 : MO VoLTE with PreCondition
 SDP

Radio Layer Configuration

There can be almost inifinite number of variations in terms of radio stack configurations for VoLTE over.
would be the most common configuration in very high level view.

Case 1 :

Case 2 :

Case 3 :

NAS Messages - Related to IMS/VoLTE

Attach request ::= DIVISION
....
| +-Octet6 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-1xSRVCC ::= CHOICE [SRVCC from E-UTRAN to cdma2000 1xCS not supported]
| | +-spare ::= FIX [0]
| +-Octet7-14 ::= DIVISION
| +-Spare ::= OCTETARRAY SIZE(0..8) [00]
....
+-MS network capability ::= TLV OPTIONAL:Exist
....
| +-SRVCC to GERAN/UTRAN capability ::= CHOICE [SRVCC from UTRAN HSPA or E-UTRAN
GERAN/UTRAN not supported]
+-Voice domain preference and UE's usage setting ::= TLV OPTIONAL:Exist
+-Octet1 ::= DIVISION
| +-Voice domain preference and UE's usage setting IEI ::= IEI [5D]
| +-Length of Voice domain preference and UE's usage setting contents ::= LEN (0..2
+-Spare ::= FIX [0]
+-UE's usage setting ::= CHOICE [Voice centric]
// This IE has following choices
// : Voice Centric,
Data Centric,
+-Voice domain preference for E-UTRAN ::= CHOICE [CS Voice only]
// : CS Voice Only,
IMS PS Voice Only,
CS Voice Prefered IMS PS Voice as Secondary
IMS PS Voice Prefered CS Voice as Secondary

Attach accept ::= DIVISION
.....
+-EPS network feature support ::= TLV OPTIONAL:Exist
| | +-EPS network feature support IEI ::= IEI [64]
| | +-Length of EPS network feature support contents ::= LEN (0..255) [1]
| +-Spare ::= FIX [0]
| +-IMS VoPS ::= CHOICE [IMS voice over PS session in S1 mode supported]
// IMS voice over PS session in S1 mode supported
// IMS voice over PS session in S1 mode not supported
+-Additional update result ::= TV OPTIONAL:Omit
+-Additional update result IEI ::= IEI [F-]
+-Spare ::= FIX [0]
+-Additional update result value ::= CHOICE [no additional information]

Example 1 : Overal Procedure for VoLTE (Both Radio Signaling and IMS Signaling)

Following is the very simplified procedure of protocol sequence from UE Power On to VoLTE Call Setup.
link if you want to get the detailed sequence.
1) [ UE <--> NW ] < Initial RRC Connection Establishment >
2) [ UE <--> NW ] < RRC Connection Reconfiguration : Attach Accept, Default EPS Bearer for In
3) [ UE --> NW ] < PDN Connectivity Request : for ims APN >
4) [ UE <--> NW ] < RRC Connection Reconfiguration : Default EPS Bearer for ims APN >
5) [ UE <--> NW ] < UE Perform IMS Registration >
6) [ UE <--> NW ] < Initiate a VoLTE Call >
7) [ UE <--> NW ] < Initial SIP Signaling for VoLTE Setup >
8) [ UE <--> NW ] < RRC Connection Reconfiguration : Dedicated EPS Bearer for ims APN >
9) [ UE <--> NW ] < RTP Traffic >

2) < RRC Connection Reconfiguration : Attach Accept, Default EPS Bearer for Internet APN >

rrcConnectionReconfiguration-r8
dedicatedInfoNASList: 1 item
Item 0
DedicatedInfoNAS: 2732c69fbd02074202e0060000f110000000365226c10109...
Non-Access-Stratum (NAS)PDU
...
ESM message container
Length: 54
ESM message container contents: ...
0101 .... = EPS bearer identity: EPS bearer identity value
.... 0010 = Protocol discriminator:
EPS session management messages (0x02)
Procedure transaction identity: 38
NAS EPS session management messages:
Activate default EPS bearer context request (0
EPS quality of service
Length: 1
Quality of Service Class Identifier (QCI): QCI 9 (9)
Access Point Name
Length: 8
APN: internet
PDN address
Length: 5
0000 0... = Spare bit(s): 0x00
PDN type: IPv4 (1)
PDN IPv4: 192.168.1.1 (192.168.1.1)
Protocol Configuration Options
Element ID: 0x27
Length: 27
[Link direction: Network to MS (1)]
1... .... = Extension: True
Configuration Protocol: ...
Protocol or Container ID:
Internet Protocol Control Protocol (
Length: 0x10 (16)
PPP IP Control Protocol
Code: Configuration Nak (3)
Identifier: 0 (0x00)
Length: 16
Options: (12 bytes), ...
Primary DNS Server IP Address: 192.168.1.2
Type: Primary DNS Server IP Address (12
Length: 6
Primary DNS Address: 192.168.1.2 (192.1
Secondary DNS Server IP Address: 192.168.1.
Type: Secondary DNS Server IP Address (
Length: 6
Secondary DNS Address: 192.168.1.3 (192
Protocol or Container ID: DNS Server IPv4 Address (0x00
Length: 0x04 (4)
IPv4: 192.168.1.2
EPS mobile identity - GUTI
...
Location area identification
...
Mobile identity - MS identity - TMSI/P-TMSI (0x0001)
...
GPRS Timer - T3402 value
...
GPRS Timer - T3423 value
...
EPS network feature support
Element ID: 0x64
Length: 1
00.. .... = Spare bit(s): 0x00
..0. .... = ESRPS: ...
...0 0... = CS-LCS: ...
.... .0.. = EPC-LCS: location services via EPC not supported
.... ..1. = EMC BS: emergency bearer services in S1 mode suppor
.... ...1 = IMS VoPS: IMS voice over PS session in S1 mode supp
radioResourceConfigDedicated
srb-ToAddModList: 1 item
...
drb-ToAddModList: 1 item
Item 0
DRB-ToAddMod
eps-BearerIdentity: 5
drb-Identity: 1
pdcp-Config
...
rlc-Config: am (0)
...
logicalChannelIdentity: 3
logicalChannelConfig
ul-SpecificParameters
priority: 13
prioritisedBitRate: kBps8 (1)
bucketSizeDuration: ms100 (1)
logicalChannelGroup: 2
mac-MainConfig: explicitValue (0)
explicitValue
ul-SCH-Config
...
drx-Config: setup (1)
...
timeAlignmentTimerDedicated: infinity (7)
phr-Config: setup (1)
...
mac-MainConfig-v1020
physicalConfigDedicated
tpc-PDCCH-ConfigPUCCH: setup (1)
setup
...
tpc-PDCCH-ConfigPUSCH: setup (1)
setup
...
antennaInfo: defaultValue (1)

ulInformationTransfer-r8
dedicatedInfoType: dedicatedInfoNAS (0)
dedicatedInfoNAS: 279489aabb02074300035200c2
0010 .... = Security header type: Integrity protected and ciphered (2)
.... 0111 = Protocol discriminator: EPS mobility management messages (0
Message authentication code: 0x9489aabb
Sequence number: 2
0000 .... = Security header type: Plain NAS message, not security prote
NAS EPS Mobility Management Message Type: Attach complete (0x43)
ESM message container
Length: 3
ESM message container contents: 5200c2
0101 .... = EPS bearer identity: EPS bearer identity value 5 (5
.... 0010 = Protocol discriminator: EPS session management mess
Activate default EPS bearer context accept (0
defaultValue: NULL

3) < PDN Connectivity Request : for ims APN >

ulInformationTransfer-r8
dedicatedInfoType: dedicatedInfoNAS (0)
dedicatedInfoNAS: 27ff2b2869030227d021280403696d732710800003000001...
0010 .... = Security header type: Integrity protected and ciphered (2)
Message authentication code: 0xff2b2869
Sequence number: 3
0000 .... = EPS bearer identity: No EPS bearer identity assigned (0)
.... 0010 = Protocol discriminator: EPS session management messages (0x
NAS EPS session management messages: PDN connectivity request (0xd0)
0010 .... = PDN type: IPv6 (2)
.... 0001 = Request type: initial request (1)
Access Point Name
Element ID: 0x28
Length: 4
APN: ims
Element ID: 0x27
Length: 16
[Link direction: MS to network (0)]
Configuration Protocol: PPP for use with IP PDP type or IP PDN type
Protocol or Container ID: DNS Server IPv6 Address Request (0x0003)
Length: 0x00 (0)
Protocol or Container ID: P-CSCF IPv6 Address Request (0x0001)
Length: 0x00 (0)
Protocol or Container ID: IP address allocation via NAS signalling
Length: 0x00 (0)
Protocol or Container ID:
MS Support of Network Requested Bearer Control indicator
Length: 0x00 (0)
Protocol or Container ID: IPv4 Link MTU Request (0x0010)
Length: 0x00 (0)

4) < RRC Connection Reconfiguration : Default EPS Bearer for ims APN >

Item 0
DedicatedInfoNAS: 279e2205e3046227c101090403696d730902000000000000...
0010 .... = Security header type: Integrity protected and ciphered
.... 0111 = Protocol discriminator: EPS mobility management message
Message authentication code: 0x9e2205e3
Sequence number: 4
0110 .... = EPS bearer identity: EPS bearer identity value 6 (6)
.... 0010 = Protocol discriminator: EPS session management messages
Activate default EPS bearer context request (0xc1)
Length: 1
Access Point Name
Length: 4
APN: ims
PDN address
Length: 9
0000 0... = Spare bit(s): 0x00
PDN type: IPv6 (2)
PDN IPv6 if id: 0000000000000011
Element ID: 0x27
Length: 39
[Link direction: Network to MS (1)]
Configuration Protocol: PPP for use with IP PDP type or IP PDN
Protocol or Container ID: DNS Server IPv6 Address (0x0003)
Length: 0x10 (16)
IPv6: 2001:0:0:1::2
Protocol or Container ID: P-CSCF IPv6 Address (0x0001)
Length: 0x10 (16)
IPv6: 2001:0:0:1::2
...
priority: 13
explicitValue
ul-SCH-Config
...
...
...
...
...

8) < RRC Connection Reconfiguration : Dedicated EPS Bearer for ims APN >

Item 0
DedicatedInfoNAS: 27b6fac978057200c506050131313131172230100840c35a...
0010 .... = Security header type: Integrity protected and ciphered
.... 0111 = Protocol discriminator: EPS mobility management message
Message authentication code: 0xb6fac978
Sequence number: 5
0111 .... = EPS bearer identity: EPS bearer identity value 7 (7)
.... 0010 = Protocol discriminator: EPS session management messages
Activate dedicated EPS bearer context request (0xc5)
0000 .... = Spare half octet: 0
.... 0110 = Linked EPS bearer identity: EPS bearer identity value 6
Length: 5
Maximum bit rate for uplink: 49 kbps
Maximum bit rate for downlink: 49 kbps
Guaranteed bit rate for uplink: 49 kbps
Guaranteed bit rate for downlink: 49 kbps
Traffic Flow Template
Length: 23
001. .... = TFT operation code: Create new TFT (1)
...0 .... = E bit: Parameters list is not included
.... 0010 = Number of packet filters: 2
Packet filter 0
00.. .... = Spare bit(s): 0
..11 .... = Packet filter direction: Bidirectional (3)
.... 0000 = Packet filter identifier: 1 (0)
Packet evaluation precedence: 0x10 (16)
Packet filter length: 0x08 (8)
Packet filter component type identifier: Single local port
Port: 50010
Packet filter component type identifier: Single remote port
Port: 60000
Packet filter component type identifier:
Protocol identifier/Next header
Protocol/header: UDP (0x11)
Packet filter 1
00.. .... = Spare bit(s): 0
..11 .... = Packet filter direction: Bidirectional (3)
.... 0001 = Packet filter identifier: 2 (1)
Packet evaluation precedence: 0x11 (17)
Packet filter length: 0x08 (8)
Packet filter component type identifier: Single local port
Port: 50011
Packet filter component type identifier: Single remote port
Port: 60001
Packet filter component type identifier:
Protocol identifier/Next header type (48)
Protocol/header: UDP (0x11)
Item 0
DRB-ToAddMod
eps-BearerIdentity: 7
drb-Identity: 3
pdcp-Config
discardTimer: ms100 (1)
rlc-UM
pdcp-SN-Size: len12bits (1)
headerCompression: rohc (1)
rohc
maxCID: 15
profiles
1... .... profile0x0001: True
.1.. .... profile0x0002: True
..0. .... profile0x0003: False
...0 .... profile0x0004: False
.... 0... profile0x0006: False
.... .0.. profile0x0101: False
.... ..0. profile0x0102: False
.... ...0 profile0x0103: False
0... .... profile0x0104: False
rlc-Config: um-Bi-Directional (1)
um-Bi-Directional
ul-UM-RLC
sn-FieldLength: size10 (1)
dl-UM-RLC
sn-FieldLength: size10 (1)
t-Reordering: ms50 (10)
priority: 6
explicitValue
ul-SCH-Config
...
...
...
...
...
defaultValue: NULL
IMS/SIP - SMS over IMS Home : www.sharetechnote.com

Overall sequence of SMS over IMS is very simple. Just send a message and wait for delivery report (this
is optional).

Comments from the initial post (Just to give you an idea on how the technology evolve) :
But when you are going into details especially for troubleshooting, there are a lot of small things you ha
came across many troubleshooting case, but I haven't found any general rules that would clear out all o
problems. (It may be becauseIMS service is still in early phase as of now (Oct 2013), specification (RFC
clear and the interpretation of those specification by the IMS stack developers seems to vary a lot.)
So my approach on this topic is to introduce various cases as much as possible so that you can absorbe
pattern.

Comments as of Feb 2017 :
Now pretty much everything is cleary defined in 3GPP specification 24.341 (Refer to the latest version o

Followings are the list of example, I will go through in this page.
 SIP Specification on SMS
o Capability indcation in REGISTER
o MO SMS Signal Flow
 MO SMS - Example 1
o MT SMS Signal Flow
 MT SMS - Example 1

SIP Specification on SMS

< Capability indcation in REGISTER >

IR 92 2.2.1 SIP Registration Procedures says :
If a UE support SMS over IP, it should include a tag to indicate the capablity of SMS over IP as stated in
as below.

On sending a REGISTER request, the SM-over-IP receiver shall indicate its capability to receive tradition
messages over IMS network by including a "+g.3gpp.smsip" parameter into the Contact header accordi

In RFC 3840, 5. Computing Capabilities
 in order to identify them as feature parameters (as opposed to parameters for another SIP exten
encoded with a leading "+" sign in the Contact header field

Example :
REGISTER sip:test.3gpp.com SIP/2.0
Expires: 600000
Authorization: Digest ....
CSeq: 1 REGISTER
Max-Forwards: 70
Route: <sip:[2001:0:0:2::2]:5060;lr>
f: <sip:310410123456789@test.3gpp.com>;tag=1148585218
i: 229717043
k: pathsec-agree
l: 0
m: <sip:310410123456789@[2001:0:0:2::1]:5060>;+g.3gpp.icsi-ref="urn%3Aurn-7%3
service.ims.icsi.mmtel";+g.3gpp.smsip;+sip.instance="<urn:gsma:imei:35858205-00176
t: <sip:310410123456789@test.3gpp.com>
v: SIP/2.0/TCP [2001:0:0:2::1]:5060;branch=z9hG4bK1447958797smg;transport=TCP

< MO SMS Signal Flow >

< 24.341 B.5 Signalling flows demonstrating successful UE originated SM submit procedure ov

< MT SMS Signal Flow >

< 24.341 B.6 Signalling flows demonstrating successful UE terminated SM deliver procedure ov

MO SMS - Example 1

Following is an example of MO SMS over IMS. If you want to get the detailed description of the specifica
to 34.229 18.1 Mobile Originating SMS

Message
Direction
UA --> NW Request : MESSAGE <URI> | (RP) RP-DATA (MS to Network)
UA <-- NW 202 Accepted
UA <-- NW Request : MESSAGE <URI> | (RP) RP-ACK (Network to MS)
UA --> NW 200 OK

Request: MESSAGE tel:19037029920;phone-context=TestIMS.com | (RP) RP-DATA (MS to Network)
MESSAGE tel:19037029920;phone-context=TestIMS.com SIP/2.0
f: "Test" <sip:+11234567890@test.3gpp.com>;tag=834037901
t: <tel:19037029920;phone-context=TestIMS.com>
CSeq: 834037887 MESSAGE
i: 834037887_2367153256@2001:0:0:1::1
v: SIP/2.0/UDP [2001:0:0:1::1]:5060;branch=z9hG4bK253093091
Max-Forwards: 70
Route: <sip:[2001:0:0:1::2]:5060;lr>
c: application/vnd.3gpp.sms
Allow: MESSAGE
Request-Disposition: no-fork
User-Agent: Test User Agent
l: 28

Route: <sip:[2001:0:0:1::2]:5060;lr>
Allow: MESSAGE

Message Body
GSM A-I/F RP - RP-DATA (MS to Network)
RP-Message Reference
RP-Message Reference: 0x05 (5)
RP-Origination Address
Length: 0
RP-Destination Address - (19037029920)
0... .... = TP-RP: TP Reply Path parameter is not set in this SMS SUBMIT/DELIVER
.0.. .... = TP-UDHI: The TP UD field contains only the short message
..0. .... = TP-SRR: A status report is not requested
...1 0... = TP-VPF: TP-VP field present - relative format (2)
.... .0.. = TP-RD: Instruct SC to accept duplicates
.... ..01 = TP-MTI: SMS-SUBMIT (1) // This is indication of MO-SMS
TP-MR: 88
TP-Destination-Address - (555)
Length: 3 address digits
1... .... : No extension
.000 .... : Type of number: (0) Unknown
.... 0001 : Numbering plan: (1) ISDN/telephone (E.164/E.163)
TP-DA Digits: 555
TP-PID: 0
00.. .... : defines formatting for subsequent bits
..0. .... : no telematic interworking, but SME-to-SME protocol
...0 0000 : the SM-AL protocol being used between the SME and the MS (0)
TP-DCS: 0
00.. .... = Coding Group Bits: General Data Coding indication (0)
Special case, GSM 7 bit default alphabet
TP-Validity-Period: 24 hours 0 minutes
TP-User-Data-Length: (12) depends on Data-Coding-Scheme
TP-User-Data
SMS text: MO SMS Test

Request: MESSAGE sip:+11234567890@test.3gpp.com | (RP) RP-ACK (Network to MS)
MESSAGE sip:+11234567890@test.3gpp.com SIP/2.0
Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bK-b6999e582ee8a42f22e8aafe5f68f47b
Via: SIP/2.0/UDP [2001:0:0:1::2]:60393;branch=z9hG4bK00476613
Max-Forwards: 69
From: <sip:1111@test.3gpp.com>;tag=00476613
To: <sip:+11234567890@test.3gpp.com>
Call-ID: 20131016-151124@[2001:0:0:1::2]:60393
CSeq: 1 MESSAGE
Request-Disposition: fork, parallel
Accept-Contact: *;+g.3gpp.smsip;require;explicit // This indicate that this SIP message is a SMS
Content-Type: application/vnd.3gpp.sms // This indicates that the SMS is in 3GPP format (not 3
In-Reply-To: 834037887_2367153256@2001:0:0:1::1
P-Called-Party-ID: <sip:+11234567890@test.3gpp.com>
Content-Length: 13
Record-Route: <sip:[2001:0:0:1::2];lr>

Message Body
GSM A-I/F RP - RP-ACK (Network to MS)
RP-User Data
Element ID: 0x41
Length: 9
TPDU (not displayed)
GSM SMS TPDU (GSM 03.40) SMS-SUBMIT REPORT
.... ..01 = TP-MTI: SMS-SUBMIT REPORT (1)
TP-Parameter-Indicator
.000 0... : Reserved
.... .0.. : TP-UDL not present
.... ..0. : TP-DCS not present
.... ...0 : TP-PID not present
TP-Service-Centre-Time-Stamp
Year 33, Month 13, Day 03
Hour 13, Minutes 63, Seconds 13
Timezone: GMT + 13 hours 15 minutes

MT SMS - Example 1

Following is an example of MT SMS over IMS. If you want to get the detailed description of the specifica
to 34.229 18.2 Mobile Terminating SMS

Message
Direction
UA <-- NW Request : MESSAGE <URI> | (RP) RP-DATA (Network to MS)
UA --> NW 200 OK
UA --> NW Request : MESSAGE <URI> | (RP) RP-ACK (MS to Network)
UA <-- NW 202 Accepted

Request: MESSAGE sip:+11234567890@test.3gpp.com | (RP) RP-DATA (Network to MS)
MESSAGE sip:+11234567890@test.3gpp.com SIP/2.0

Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bK-ad54683f54403f46ff8d8b553521e588
Via: SIP/2.0/UDP [2001:0:0:1::2]:60393;branch=z9hG4bK0047D4EC
Max-Forwards: 69
From: <sip:1111@test.3gpp.com>;tag=0047D4EC
To: <sip:+11234567890@test.3gpp.com>
Call-ID: 20131016-151152@[2001:0:0:1::2]:60393
CSeq: 1 MESSAGE
Accept-Contact: *;+g.3gpp.smsip;require;explicit // This indicate that this SIP message is a SMS
Content-Type: application/vnd.3gpp.sms // This indicates that the SMS is in 3GPP format (not 3G
Content-Transfer-Encoding: binary
P-Called-Party-ID: <sip:+11234567890@test.3gpp.com>
Content-Length: 41
Record-Route: <sip:[2001:0:0:1::2];lr>

Message Body
GSM A-I/F RP - RP-DATA (Network to MS)
RP-Origination Address - (999999)
Length: 4
1... .... = Extension: No Extension
.000 .... = Type of number: unknown (0x00)
.... 0001 = Numbering plan identification: ISDN/Telephony Numbering (Rec ITU-T
BCD Digits: 999999
RP-Destination Address
RP-User Data

GSM SMS TPDU (GSM 03.40) SMS-DELIVER
0... .... = TP-RP: TP Reply Path parameter is not set in this SMS SUBMIT/DELIVER
..0. .... = TP-SRI: A status report shall not be returned to the SME
.... .1.. = TP-MMS: No more messages are waiting for the MS in this SC
.... ..00 = TP-MTI: SMS-DELIVER (0) // This is indication of MT-SMS
TP-Originating-Address - (1234567890)
Length: 10 address digits
.000 .... : Type of number: (0) Unknown
.... 0001 : Numbering plan: (1) ISDN/telephone (E.164/E.163)
TP-OA Digits: 1234567890
TP-PID: 0
00.. .... : defines formatting for subsequent bits
..0. .... : no telematic interworking, but SME-to-SME protocol
...0 0000 : the SM-AL protocol being used between the SME and the MS (0)
TP-DCS: 0
00.. .... = Coding Group Bits: General Data Coding indication (0)
Special case, GSM 7 bit default alphabet
TP-Service-Centre-Time-Stamp
Year 13, Month 10, Day 16
Hour 15, Minutes 11, Seconds 29
Timezone: GMT + 5 hours 0 minutes
TP-User-Data
SMS text: this is a mt sms test message

Request: MESSAGE sip:1111@test.3gpp.com;phone-context=TestIMS.com | (RP) RP-ACK (MS to Netwo
MESSAGE sip:1111@test.3gpp.com;phone-context=TestIMS.com SIP/2.0
f: "Test" <sip:+11234567890@test.3gpp.com>;tag=834066458
t: <sip:1111@test.3gpp.com;phone-context=TestIMS.com>
CSeq: 834066445 MESSAGE
i: 834066446_2367161720@2001:0:0:1::1
Max-Forwards: 70
Route: <sip:[2001:0:0:1::2]:5060;lr>
Allow: MESSAGE
l: 6

Message Body
GSM A-I/F RP - RP-ACK (MS to Network)
RP-User Data
Element ID: 0x41
Length: 2
TPDU (not displayed)
GSM SMS TPDU (GSM 03.40) SMS-DELIVER REPORT
.... .0.. = TP-MMS: More messages are waiting for the MS in this SC
.... ..00 = TP-MTI: SMS-DELIVER REPORT (0)
TP-Parameter-Indicator
.000 0... : Reserved
.... .0.. : TP-UDL not present
.... ..0. : TP-DCS not present
.... ...0 : TP-PID not present

Quick Reference for VoLTE over IMS

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Quick Reference for VoLTE over IMS

Hochgeladen von

Copyright:

Verfügbare Formate

LTE Quick Reference - VoLTE over IMS Go Back To Index Home : www.

Request: MESSAGE sip:+11234567890@test.3gpp.com | (RP) RP-DATA (Network to MS)

MESSAGE sip:+11234567890@test.3gpp.com SIP/2.0

Das könnte Ihnen auch gefallen