VoNR is very similar to VoLTE. They are all based on Voice call over IMS. The main difference is that the IMS is established by and go through 5G Core network in VoNR whereas it is established by and go through 4G core network. Even in terms of 3GPP, the details of VoNR procedure is described in 23.228 which is mainly for IMS for LTE and 5G specific details are provided as an appendix (Annex Y). So if you are already familiar with VoLTE, you would catch up VoNR very quickly and most of the contents listed in my IMS notes would applies to VoNR as well. In this page, I would mostly focus on the differences in VoNR.
- Overall Call Flow
- PDU session establishment request
- PDU session establishment accept
- PDU session modification command
- PDU session modification complete
- QoS Flow
- S1 mode vs N1 mode
- Key Informations in Signaling Message
- Overall SIP Procedure
- Reference
Overall Call Flow
Following is the overall call flow of NR. You would see a little bit of differences in terms of signaling message name comparing to VoLTE setup, but those differences are due to signaling difference between LTE and NR, not specifically due to IMS side difference. I wouldn't put all the details of NR signaling procedure here. I would only put those steps related to VoNR.
|
Step |
Direction |
Message |
Memo |
|
1 |
UE <- NW |
SIB1 |
SIB1 should indicate that the NW supports IMS (ims-EmergencySupport,eCallOverIMS-Support) and it is not barred(uac-BarringInfo). |
|
2 |
UE <-> NW |
N/A |
All the necessary UAC condition should be met for allowing IMS call. |
|
3 |
UE -> NW |
Registration Request |
Usage setting = voice centric, GMM capability S1 mode = true |
|
.... |
|||
|
4 |
UE <- NW |
UE Capability Enquiry |
|
|
5 |
UE -> NW |
UE Capability Information |
UE should notify the IMS related capabilities (IMS-Parameters) |
|
6 |
UE <- NW |
Registration Accept |
|
|
7 |
UE -> NW |
Registration Complete |
|
|
8 |
UE -> NW |
PDU Session Establishment Request |
internet DNN, 5QI = (Usually) 6 |
|
9 |
UE <- NW |
PDU Session Establishment Accept |
|
|
10 |
UE -> NW |
ims DNN |
|
|
11 |
UE <- NW |
5QI = 5 (mainly for SIP signaling) |
|
|
12 |
UE <-> NW |
|
|
|
13 |
UE |
Initiate Voice Call |
|
|
14 |
UE <-> NW |
|
|
|
15 |
UE <- NW |
Add QoS Flow for SIP traffic, 5QI = 1 |
|
|
16 |
UE -> NW |
|
|
|
17 |
UE <-> NW |
SIP Traffic |
|
PDU session establishment request (Log shared by Amarisoft)
This is the message from UE that initiate setting up the configuration which are required to do IMS registration. I would like you to note that this message is requesting a PDU setup with DNN="ims" and requesting the IP address for P-CSCF. If you are familiar with VoLTE process, you would notice that the role of this message is similar to PDN Connectivity Request in VoLTE.
Decoded signalling message from a live capture. Field values are what one network actually sent, not specification text.
Protocol discriminator = 0x7e (5GS Mobility Management)
Security header = 0x2 (Integrity protected and ciphered)
Auth code = 0xff096300
Sequence number = 0x02
Protocol discriminator = 0x7e (5GS Mobility Management)
Security header = 0x0 (Plain 5GS NAS message, not security protected)
Message type = 0x67 (UL NAS transport)
Payload container type = 1 (N1 SM information)
Payload container:
Protocol discriminator = 0x2e (5GS Session Management)
PDU session identity = 5
Procedure transaction identity = 9
Message type = 0xc1 (PDU session establishment request )
Integrity protection maximum data data:
Maximum data rate per UE for user-plane integrity protection for uplink
= 0xff (Full data rate)
Maximum data rate per UE for user-plane integrity protection for downlink
= 0xff (Full data rate)
PDU session type = 0x3 (IPv4v6)
SSC mode = 0x1 (1)
Extended protocol configuration options:
Ext = 1
Configuration protocol = 0
Protocol ID = 0x000a (IP address allocation via NAS signalling)
Data =
Protocol ID = 0x0002 (IM CN Subsystem Signaling Flag)
Data =
Protocol ID = 0x0001 (P-CSCF IPv6 Address Request)
Data =
Protocol ID = 0x000c (P-CSCF IPv4 Address Request)
Data =
Protocol ID = 0x0003 (DNS Server IPv6 Address Request)
Data =
Protocol ID = 0x000d (DNS Server IPv4 Address Request)
Data =
PDU session ID = 5
Request type = 0x1 (initial request)
DNN = "ims"
PDU session establishment accept (Log shared by Amarisoft).
Once network recieves the PDU session establishment request message from UE, Network informs the UE of the requested information (P-CSCF) and creates a QoS pipe that is necessary for the traffic. This is similar to Activate default EPS bearer context request in VoLTE.
Decoded signalling message from a live capture. Field values are what one network actually sent, not specification text.
Protocol discriminator = 0x7e (5GS Mobility Management) Security header = 0x2 (Integrity protected and ciphered) Auth code = 0x66f143b0 Sequence number = 0x03 Protocol discriminator = 0x7e (5GS Mobility Management) Security header = 0x0 (Plain 5GS NAS message, not security protected) Message type = 0x68 (DL NAS transport) Payload container type = 1 (N1 SM information) Payload container: Protocol discriminator = 0x2e (5GS Session Management) PDU session identity = 5 Procedure transaction identity = 9 Message type = 0xc2 (PDU session establishment accept ) Selected PDU session type = 0x3 (IPv4v6) Selected SSC mode = 0x1 (1) Authorized QoS rules: QoS rule 1: QoS rule identifier = 1 Rule operation code = 1 (create new QoS rule) DQR = 1 (the QoS rule is the default QoS rule) Number of packet filters = 1 Packet filter identifier = 15 Packet filter direction = 3 (bidirectional) Match-all QoS rule precedence = 255 QFI = 1 Session AMBR: Session-AMBR for downlink = 3000000 kbps Session-AMBR for uplink = 1000000 kbps PDU address: PDU session type = 3 (IPv4v6) IPv6 = ::2001:468:3000:1 IPv4 = 192.168.4.2 Authorized QoS flow descriptions: QoS flow description 1: QFI = 1 Operation code = 1 (create new QoS flow description) E = 1 (parameters list is included) Number of parameters = 15QI = 5 Extended protocol configuration options: Ext = 1 Configuration protocol = 0 Protocol ID = 0x000d (DNS Server IPv4 Address) Data = 8.8.8.8 Protocol ID = 0x0003 (DNS Server IPv6 Address) Data = 2001:4860:4860:0:0:0:0:8888Protocol ID = 0x000c (P-CSCF IPv4 Address) Data = 192.168.4.1 Protocol ID = 0x0001 (P-CSCF IPv6 Address) Data = 2001:468:3000:1:0:0:0:0 Protocol ID = 0x0002 (IM CN Subsystem Signaling Flag) Data =DNN = "ims.mnc001.mcc001.gprs" PDU session ID = 5
PDU session modification command (Log shared by Amarisoft)
Once IMS registration is done and the user trigger IMS call, it would reach a certain point where another data pipe for IMS data traffic (i.e, Voice traffic). For setting up the data only traffic (not IMS signaling), usually NW sets up another data pipe (QoS flow) dedicated for the data traffic. This process is initiated by NW via PDU session modification command (
Decoded signalling message from a live capture. Field values are what one network actually sent, not specification text.
Protocol discriminator = 0x7e (5GS Mobility Management)
Security header = 0x2 (Integrity protected and ciphered)
Auth code = 0x1a236417
Sequence number = 0x05
Protocol discriminator = 0x7e (5GS Mobility Management)
Security header = 0x0 (Plain 5GS NAS message, not security protected)
Message type = 0x68 (DL NAS transport)
Payload container type = 1 (N1 SM information)
Payload container:
Protocol discriminator = 0x2e (5GS Session Management)
PDU session identity = 5
Procedure transaction identity = 0
Message type = 0xcb (PDU session modification command )
Authorized QoS rules:
QoS rule 1:
QoS rule identifier = 2
Rule operation code = 1 (create new QoS rule)
DQR = 0 (the QoS rule is not the default QoS rule)
Number of packet filters = 2
Packet filter identifier = 0
Packet filter direction = 3 (bidirectional)
Packet filter component 0x20 = 0x20010468300000010000000000000000 ...
ffffffffffffffffffffffffffffffff3011502710407918
Packet filter identifier = 1
Packet filter direction = 3 (bidirectional)
Packet filter component 0x20 = 0x20010468300000010000000000000000 ...
ffffffffffffffffffffffffffffffff3011502711407919
QoS rule precedence = 0
QFI = 2
Authorized QoS flow descriptions:
QoS flow description 1:
QFI = 2
Operation code = 1 (create new QoS flow description)
E = 1 (parameters list is included)
Number of parameters = 5
5QI = 1
GFBR uplink = 49 kbps
GFBR downlink = 49 kbps
MFBR uplink = 51 kbps
MFBR downlink = 51 kbps
Extended protocol configuration options:
Ext = 1
Configuration protocol = 0
Protocol ID = 0x000d (DNS Server IPv4 Address)
Data = 8.8.8.8
Protocol ID = 0x0003 (DNS Server IPv6 Address)
Data = 2001:4860:4860:0:0:0:0:8888
Protocol ID = 0x000c (P-CSCF IPv4 Address)
Data = 192.168.4.1
Protocol ID = 0x0001 (P-CSCF IPv6 Address)
Data = 2001:468:3000:1:0:0:0:0
Protocol ID = 0x0002 (IM CN Subsystem Signaling Flag)
Data =
PDU session ID = 5
PDU session modification complete (Log shared by Amarisoft)
The exchange closes here, and the message is short because it carries no new parameters. What it does carry is confirmation that the UE accepted the QoS flow the command above created. One failure mode is worth recognising in a log. When the complete never arrives, the voice flow stays configured on the core side and unusable on the radio side.
Decoded signalling message from a live capture. Field values are what one network actually sent, not specification text.
Protocol discriminator = 0x7e (5GS Mobility Management)
Security header = 0x2 (Integrity protected and ciphered)
Auth code = 0x81da3da5
Sequence number = 0x04
Protocol discriminator = 0x7e (5GS Mobility Management)
Security header = 0x0 (Plain 5GS NAS message, not security protected)
Message type = 0x67 (UL NAS transport)
Payload container type = 1 (N1 SM information)
Payload container:
Protocol discriminator = 0x2e (5GS Session Management)
PDU session identity = 5
Procedure transaction identity = 0
Message type = 0xcc (PDU session modification complete )
PDU session ID = 5
QoS Flow
In VoNR, two different data flows get involved and in most case these two flows are mapped to two different types of QoS pipe. Following is a typical example of the two QoS pipe being used in VoNR based on the log shared by Amarisoft. If you are not familiar with 5G QoS Structure, it would be worth reading my notes on 5G QoS first.
The first QoS Pipe is involved mostly in setting up the data flow for IMS signaling message as shown in the following example. Usually, this QoS setup is triggered by UE via PDU Session Establishment Request and Network creates a core network side of the QoS flow via PDU Session Establishment Accept message. This core network side of QoS pipe (QoS Flow) is mapped to RAN(Radio Access Network) pipe through SDAP configuration in Rrc Message as shown in Figure 1.
Figure 1 puts the two messages side by side, the NAS message on the left and the RRC message on the right. The yellow arrows link the values that have to match. PDU session ID 5 becomes pdu-Session 5 in the SDAP configuration, and QFI 1 becomes the single entry in mappedQoS-FlowsToAdd.
Figure 1. The flow is created once and named twice. The core network calls it a QFI and the radio network calls it a mapped flow on a DRB, and the SDAP configuration is where the two names meet.
5QI = 5 : the standardised non-GBR profile for IMS signalling. This flow carries SIP, not speech.DQR = 1 with a Match-all filter at precedence 255 : the rule is the default for the session, so anything no later rule claims arrives here.defaultDRB TRUE : the radio side agrees, and this bearer takes whatever maps to no other flow.sdap-HeaderUL present, sdap-HeaderDL absent : the UE marks its uplink packets with the QFI, and the network does not need to mark the downlink.Number of parameters = 1 : the flow description carries 5QI and nothing else, which is what a non-GBR flow needs.
The second QoS Pipe is involved mostly in setting up the data flow for IMS traffic (Voice data) as shown in the following example. This QoS setup is triggered by Network via PDU Session Modification Command and Network creates another QoS pipe on core network side. This core network side of QoS pipe (QoS Flow) is mapped to RAN(Radio Access Network) pipe through SDAP configuration in Rrc Message as shown in Figure 2.
Figure 2 repeats the layout for the second flow, and what differs is the interesting part. The message on the left is a PDU session modification command rather than an accept, so the network is adding a flow to a session that already exists. PDU session ID 5 is the same session as in Figure 1.
Figure 2. One session, two flows, and only the second one carries speech. The guaranteed bit rate parameters are what separate a voice flow from the signalling flow that set it up.
5QI = 1 : the standardised GBR profile for conversational voice.GFBR 49 kbps and MFBR 51 kbps, both directions : a guaranteed rate and a ceiling. The 5QI 5 flow in Figure 1 has neither.DQR = 0 with two packet filters at precedence 0 : this rule is not the default, and its precedence puts it ahead of the Match-all rule from Figure 1.defaultDRB FALSE, drb-Identity 2 : a second radio bearer, so the speech gets a bearer of its own.sdap-HeaderUL and sdap-HeaderDL both absent : one flow on the bearer needs no QFI marking, because the bearer already identifies the flow.Number of parameters = 5 : 5QI plus the four rate values, against the single parameter in Figure 1.
S1 mode vs N1 mode
Two names sit side by side in a registration log, and a reader new to 5G NAS often takes them for options the UE picked. They are better read as two separate attachment paths. S1 is the interface to the EPC and N1 is the interface to the 5GC, so the mode names say which core network the UE went through.
- S1 mode : indicates successful EPS Attach
- N1 mode : indicates successful 5GC(5G Core) Attach
For voice the distinction decides where a call can be carried. A UE registered through N1 can be offered VoNR, because its IMS session terminates in the 5G core. S1 support gives the network a second route, and that route is EPS fallback. The call begins in 5G signalling and moves to LTE before the media starts.
The network does not choose that route without information. The capability listing in Key Informations in Signaling Message carries voiceFallbackIndicationEPS-r16 inside IMS-ParametersCommon, and a UE supporting it says in advance that it expects to be redirected. Read the two together and a registration log becomes useful. The mode says which core the UE is on now, and the capability says where it can be sent when a call arrives.
In a log the two appear during registration rather than during call setup, so the answer is settled before any INVITE is sent. That is why a voice problem is often diagnosed from the registration exchange rather than from the SIP trace further down this page. If the UE never registered through N1, reading the INVITE will not explain why the call avoided NR.
S1 and N1 name interfaces, not radio technologies : the mode tells you which core network the UE registered with, and says nothing about whether the radio is LTE or NR.VoNR needs N1 : the IMS session has to terminate in the 5G core, so a UE registered only through S1 gets VoLTE instead.EPS fallback needs both : the network moves the call to LTE, so the UE has to be able to use S1 as well as N1.Read the registration before the SIP trace : the mode is settled there, and the call setup only inherits what registration decided.Check the capability beside the mode : voiceFallbackIndicationEPS-r16 tells the network whether the UE expects that redirection at all.
Key Informations in Signaling Message
There are many different types of message with various information elements related to VoNR service and I am trying to list up those messages and information elements in this section. But I wouldn't say all of these information elements are mandatory. Depending on Network implementation or UE protocol stack implementation it may work without some of these informations.
SIB1
Two flags in SIB1 tell a UE whether IMS voice is worth attempting on this cell, before it has registered anywhere. Both are optional, so their absence is the ordinary case rather than a fault. Read them as permission to try, not as a promise that a call will succeed.
Following is based on
SIB1 ::= SEQUENCE {
-- ... fields unrelated to IMS are omitted ...
ims-EmergencySupport ENUMERATED {true} OPTIONAL, -- Need R
eCallOverIMS-Support ENUMERATED {true} OPTIONAL, -- Need R
-- ...
}
UE Capability Information
SIB1 says what the cell offers. This says what the UE can do, and a voice call needs both to agree. Note where voiceOverNR sits : it is under the FRX-Diff branch rather than under Common, because support can differ between FR1 and FR2.
Following is based on
IMS-Parameters ::= SEQUENCE {
ims-ParametersCommon IMS-ParametersCommon OPTIONAL,
ims-ParametersFRX-Diff IMS-ParametersFRX-Diff OPTIONAL,
...
}
IMS-Parameters-v1700 ::= SEQUENCE {
ims-ParametersFR2-2-r17 IMS-ParametersFR2-2-r17 OPTIONAL
}
IMS-ParametersCommon ::= SEQUENCE {
voiceOverEUTRA-5GC ENUMERATED {supported} OPTIONAL,
...,
[[
voiceOverSCG-BearerEUTRA-5GC ENUMERATED {supported} OPTIONAL
]],
[[
voiceFallbackIndicationEPS-r16 ENUMERATED {supported} OPTIONAL
]]
}
IMS-ParametersFRX-Diff ::= SEQUENCE {
voiceOverNR ENUMERATED {supported} OPTIONAL,
...
}
IMS-ParametersFR2-2-r17 ::= SEQUENCE {
voiceOverNR-r17 ENUMERATED {supported} OPTIONAL,
...
}
Two things moved when this listing was checked against 38.331 v19.3.0. In SIB1, eCallOverIMS-Support now reads
That extension is IMS-Parameters-v1700, and its only content is ims-ParametersFR2-2-r17. Inside it sits voiceOverNR-r17, a second voice flag. FR2-2 is the 52.6 to 71 GHz range added in Release 17, and it needs a flag of its own because the FRX-Diff branch above it does not reach that far. A UE supporting voice on FR2-2 therefore reports it twice, once per structure.
PDU session establishment request
This is the message that asks for the IMS session, and two fields carry the whole intent. The DNN names the network the UE wants, and the protocol configuration options ask for the P-CSCF address it will register with. Everything else in the message is ordinary session setup.
Decoded signalling message from a live capture. Field values are what one network actually sent, not specification text.
...
PDU session type = 0x3 (IPv4v6)
SSC mode = 0x1 (1)
Extended protocol configuration options:
Ext = 1
...
Protocol ID = 0x0001 (P-CSCF IPv6 Address Request)
Data =
Protocol ID = 0x000c (P-CSCF IPv4 Address Request)
Data =
...
PDU session ID = 5
Request type = 0x1 (initial request)
DNN = "ims"
PDU session establishment accept
The network answers with the QoS it has authorised, and this is where a voice call becomes possible or does not. Read the QoS rule and the QoS flow description together. The rule says which packets belong to the flow, and the description says how the flow is treated.
Decoded signalling message from a live capture. Field values are what one network actually sent, not specification text.
Authorized QoS rules : QoS rule 1: QoS rule identifier = 1 Rule operation code = 1 (create new QoS rule) DQR = 1 (the QoS rule is the default QoS rule) Number of packet filters = 1 Packet filter identifier = 15 Packet filter direction = 3 (bidirectional) Match-all QoS rule precedence = 255 QFI = 1Session AMBR : Session-AMBR for downlink = 3000000 kbps Session-AMBR for uplink = 1000000 kbps PDU address: PDU session type = 3 (IPv4v6) IPv6 = ::2001:468:3000:1 IPv4 = 192.168.4.2Authorized QoS flow descriptions : QoS flow description 1: QFI = 1 Operation code = 1 (create new QoS flow description) E = 1 (parameters list is included) Number of parameters = 15QI = 5 Extended protocol configuration options: Ext = 1... Protocol ID = 0x000c (P-CSCF IPv4 Address) Data = 192.168.4.1 Protocol ID = 0x0001 (P-CSCF IPv6 Address) Data = 2001:468:3000:1:0:0:0:0 ... DNN = "ims.mnc001.mcc001.gprs" PDU session ID = 5
Overall SIP Procedure
Everything above this point builds the pipe. This section carries what travels through it. The table lists the sixteen messages in order, and each one is captured in full below the table, so a step can be read against the packet that carried it. Registration runs first, and the call setup follows it.
|
Step |
Direction |
Message |
|
UE --> CSCF |
Request: REGISTER sip:msg.testdomain.com |
|
|
UE <-- CSCF |
Status: 200 OK (REGISTER) |
|
|
UE --> CSCF |
Request: SUBSCRIBE sip:+98765432100@test.3gpp.com |
|
|
UE <-- CSCF |
Status: 200 OK (SUBSCRIBE) |
|
|
UE <-- CSCF |
Request: NOTIFY sip:+98765432100@[2001:0:0:2::1]:5060 |
|
|
UE <-- CSCF |
Request: NOTIFY sip:+98765432100@[2001:0:0:2::1]:5060 |
|
|
UE --> CSCF |
Status: 200 OK (NOTIFY) |
|
|
UE <-- CSCF |
Request: INVITE sip:+98765432100@[2001:0:0:2::1]:5060 |
|
|
UE --> CSCF |
Status: 183 Session Progress |
|
|
UE <-- CSCF |
Request: PRACK sip:+98765432100@[2001:0:0:2::1]:5060 |
|
|
UE --> CSCF |
Status: 200 OK (PRACK) |
|
|
UE <-- CSCF |
Request: UPDATE sip:+98765432100@[2001:0:0:2::1]:5060 |
|
|
UE --> CSCF |
Status: 200 OK (UPDATE |
|
|
UE --> CSCF |
Status: 180 Ringing |
|
|
UE --> CSCF |
EVS 107 PT=EVS, SSRC=0x33050, Seq=1, Time=277680, Mark, EVS Primary 13.2 |
|
|
UE <-- CSCF |
EVS 107 PT=EVS, SSRC=0x33051, Seq=1, Time=277680, Mark, EVS Primary 13.2 |
|
|
|
|
|
[1] Request: REGISTER sip:msg.testdomain.com |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
Transmission Control Protocol, Src Port: 33841, Dst Port: 5060, Seq: 1001, Ack: 1, Len: 641
Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:msg.testdomain.com SIP/2.0
Method: REGISTER
Request-URI: sip:msg.lab.t-mobile.com
Request-URI Host Part: msg.testdomain.com
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP [2001:0:0:2::1]:5060;branch=z9hG4bK-524287-1---d2129e94b5f02ee5;rport;transport=TCP
Max-Forwards: 70
Proxy-Require: sec-agree
Require: sec-agree
Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-0>";q=1.0;
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+g.3gpp.smsip;text
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: q=1.0
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: video
Contact parameter: +g.3gpp.smsip
Contact parameter: text
To: <sip:+98765432100@test.3gpp.com>
SIP to address: sip:+98765432100@test.3gpp.com
From: <sip:+98765432100@test.3gpp.com>;tag=0896d778
SIP from address: sip:+98765432100@test.3gpp.com
SIP from tag: 0896d778
Call-ID: j62XAO7FQuoiNGYpvV_3UA..@2001:0:0:2::1
[Generated Call-ID: j62XAO7FQuoiNGYpvV_3UA..@2001:0:0:2::1]
CSeq: 1 REGISTER
Expires: 600000
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, INFO, REFER, NOTIFY, MESSAGE, PRACK
Supported: path, gruu, sec-agree
User-Agent: T-Mobile VONR-RCSUP-ePDG-IR94-RTT-ussd-VVM SEC/SM-G998U G998USQU4AUG8
Authorization: Digest username="001010987654321@test.3gpp.com",
realm="msg.testdomain.com",
uri="sip:msg.testdomain.com",nonce="",response="",algorithm=AKAv1-MD5
Authentication Scheme: Digest
Username: "001010987654321@test.3gpp.com"
Realm: "msg.testdomain.com
Authentication URI: "sip:msg.testdomain.com"
Nonce Value: ""
Digest Authentication Response: ""
Algorithm: AKAv1-MD5
[truncated]Security-Client: ipsec-3gpp;prot=esp;mod=trans;spi-c=31598;spi-s=31599;port-c=6101;
port-s=6100;alg=hmac-md5-96;ealg=des-ede3-cbc, ipsec-3gpp;prot=esp;mod=trans;
spi-c=31598;spi-s=31599;port-c=6101;port-s=6100;alg=hmac-md5-96;ea
Content-Length: 0
|
[2] Status: 200 OK (REGISTER) |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
Transmission Control Protocol, Src Port: 5060, Dst Port: 33841, Seq: 1, Ack: 1642, Len: 683
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
Message Header
Max-Forwards: 70
Via: SIP/2.0/TCP [2001:0:0:2::1]:5060;branch=z9hG4bK-524287-1-- d2129e94b5f02ee5;
rport=33841;transport=TCP
From: <sip:+98765432100@test.3gpp.com>;tag=0896d778
SIP from address: sip:+98765432100@test.3gpp.com
SIP from tag: 0896d778
To: <sip:+98765432100@test.3gpp.com>;tag=0896d778
SIP to address: sip:+98765432100@test.3gpp.com
SIP to tag: 0896d778
Call-ID: j62XAO7FQuoiNGYpvV_3UA..@2001:0:0:2::1
[Generated Call-ID: j62XAO7FQuoiNGYpvV_3UA..@2001:0:0:2::1]
CSeq: 1 REGISTER
Date: Sat, 27 Aug 2022 14:22:43 GMT
Require: sec-agree
P-Associated-URI: <sip:+98765432100@test.3gpp.com>
Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-0>";q=1.0;
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;
+g.3gpp.smsip;text;expires=600000
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: q=1.0
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: video
Contact parameter: +g.3gpp.smsip
Contact parameter: text
Contact parameter: expires=600000
Content-Length: 0
Path: <sip:[2001:0:0:11::2];lr>
|
[3] Request: SUBSCRIBE sip:+98765432100@test.3gpp.com |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
Transmission Control Protocol, Src Port: 33841, Dst Port: 5060, Seq: 2642, Ack: 684, Len: 85
[2 Reassembled TCP Segments (1085 bytes): #42(1000), #43(85)]
Session Initiation Protocol (SUBSCRIBE)
Request-Line: SUBSCRIBE sip:+98765432100@test.3gpp.com SIP/2.0
Method: SUBSCRIBE
Request-URI: sip:+98765432100@test.3gpp.com
Request-URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Request-URI Host Part: test.3gpp.com
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP [2001:0:0:2::1]:5060;branch=z9hG4bK-524287-1---4b779d7664c314d5;rport;transport=TCP
Max-Forwards: 70
Route: <sip:[2001:0:0:11::2]:5060;lr>
Proxy-Require: sec-agree
Require: sec-agree
[truncated]Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-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-p
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: +g.3gpp.mid-call
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.ps2cs-srvcc-orig-pre-alerting
Contact parameter: video
Contact parameter: +g.3gpp.smsip
Contact parameter: text
To: <sip:+98765432100@test.3gpp.com>
SIP to address: sip:+98765432100@test.3gpp.com
From: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP from address: sip:+98765432100@test.3gpp.com
SIP from tag: 6382823e
Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1
[Generated Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1]
CSeq: 1 SUBSCRIBE
Expires: 600000
Accept: application/reginfo+xml
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, INFO, REFER, NOTIFY, MESSAGE, PRACK
Supported: sec-agree
User-Agent: Test VONR-RCSUP-ePDG-IR94-RTT-ussd-VVM SEC/SM-G998U G998USQU4AUG8
Event: reg
P-Preferred-Identity: <sip:+98765432100@test.3gpp.com>
SIP PPI Address: sip:+98765432100@test.3gpp.com
P-Access-Network-Info: 3GPP-NR-FDD;utran-cell-id-3gpp=00101000001000000000
Content-Length: 0
|
[4] Status: 200 OK (SUBSCRIBE) |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
Transmission Control Protocol, Src Port: 5060, Dst Port: 33841, Seq: 684, Ack: 2727, Len: 450
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
Message Header
Max-Forwards: 70
Via: SIP/2.0/TCP [2001:0:0:2::1]:5060;branch=z9hG4bK-524287-1---4b779d7664c314d5;
rport=33841;transport=TCP
From: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP from address: sip:+98765432100@test.3gpp.com
SIP from tag: 6382823e
To: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP to address: sip:+98765432100@test.3gpp.com
SIP to tag: 6382823e
Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1
[Generated Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1]
CSeq: 1 SUBSCRIBE
Expires: 600000
Contact: <sip:[2001:0:0:11::2]:5060;transport=tcp>
Contact URI: sip:[2001:0:0:11::2]:5060;transport=tcp
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Content-Length: 0
|
[5] Request: NOTIFY sip:+98765432100@[2001:0:0:2::1]:5060 |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (NOTIFY)
Request-Line: NOTIFY sip:+98765432100@[2001:0:0:2::1]:5060 SIP/2.0
Method: NOTIFY
Request-URI: sip:+98765432100@[2001:0:0:2::1]:5060
Request-URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Request-URI Host Part: [2001:0:0:2::1]
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP [2001:0:0:11::2]:5060;
branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6404;rport;transport=udp
Transport: UDP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 5060
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6404
RPort: rport
transport=udp
Max-Forwards: 69
Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1
[Generated Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1]
CSeq: 1 NOTIFY
Sequence Number: 1
Method: NOTIFY
To: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6382823e
From: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP from address: sip:+98765432100@test.3gpp.com
SIP from address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP from address Host Part: test.3gpp.com
SIP from tag: 6382823e
Contact: <sip:[2001:0:0:11::2]:5060;transport=tcp>
Contact URI: sip:[2001:0:0:11::2]:5060;transport=tcp
Contact URI Host Part: [2001:0:0:11::2]
Contact URI Host Port: 5060
Contact URI parameter: transport=tcp
Event: reg
Subscription-State: active;expires=600000
Content-Type: application/reginfo+xml
Content-Length: 678
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
Message Body
eXtensible Markup Language
<?xml
version="1.0"
encoding="UTF-8"
?>
<reginfo
version="0"
state="full"
xmlns="urn:ietf:params:xml:ns:reginfo">
<registration
aor="sip:+98765432100@test.3gpp.com"
id="a1"
state="active">
<contact
id="1"
state="active"
event="registered">
<uri>
sip:+98765432100@[2001:0:0:2::1]:5060
</uri>
<unknown-param
name="+sip.instance">
"<urn:gsma:imei:35012167-001225-0>"
</unknown-param>
<unknown-param
name="+g.3gpp.icsi-ref">
"urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
</unknown-param>
<unknown-param
name="video"/>
<unknown-param
name="+g.3gpp.smsip"/>
<unknown-param
name="text"/>
</contact>
</registration>
</reginfo>
|
[6] Request: NOTIFY sip:+98765432100@[2001:0:0:2::1]:5060 |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (NOTIFY)
Request-Line: NOTIFY sip:+98765432100@[2001:0:0:2::1]:5060 SIP/2.0
Method: NOTIFY
Request-URI: sip:+98765432100@[2001:0:0:2::1]:5060
Request-URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Request-URI Host Part: [2001:0:0:2::1]
Request-URI Host Port: 5060
[Resent Packet: True]
[Suspected resend of frame: 49]
Message Header
Via: SIP/2.0/UDP [2001:0:0:11::2]:5060;
branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6404;rport;transport=udp
Transport: UDP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 5060
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6404
RPort: rport
transport=udp
Max-Forwards: 69
Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1
[Generated Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1]
CSeq: 1 NOTIFY
Sequence Number: 1
Method: NOTIFY
To: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6382823e
From: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP from address: sip:+98765432100@test.3gpp.com
SIP from address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP from address Host Part: test.3gpp.com
SIP from tag: 6382823e
Contact: <sip:[2001:0:0:11::2]:5060;transport=tcp>
Contact URI: sip:[2001:0:0:11::2]:5060;transport=tcp
Contact URI Host Part: [2001:0:0:11::2]
Contact URI Host Port: 5060
Contact URI parameter: transport=tcp
Event: reg
Subscription-State: active;expires=600000
Content-Type: application/reginfo+xml
Content-Length: 678
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
Message Body
eXtensible Markup Language
<?xml
version="1.0"
encoding="UTF-8"
?>
<reginfo
version="0"
state="full"
xmlns="urn:ietf:params:xml:ns:reginfo">
<registration
aor="sip:+98765432100@test.3gpp.com"
id="a1"
state="active">
<contact
id="1"
state="active"
event="registered">
<uri>
sip:+98765432100@[2001:0:0:2::1]:5060
</uri>
<unknown-param
name="+sip.instance">
"<urn:gsma:imei:35012167-001225-0>"
</unknown-param>
<unknown-param
name="+g.3gpp.icsi-ref">
"urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
</unknown-param>
<unknown-param
name="video"/>
<unknown-param
name="+g.3gpp.smsip"/>
<unknown-param
name="text"/>
</contact>
</registration>
</reginfo>
|
[7] Status: 200 OK (NOTIFY) |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
[Request Frame: 49]
[Response Time (ms): 28]
Message Header
Via: SIP/2.0/UDP [2001:0:0:11::2]:5060;
branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6404;rport;transport=udp
Transport: UDP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 5060
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6404
RPort: rport
transport=udp
Max-Forwards: 70
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
[truncated]Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-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-p
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Contact URI Host Part: [2001:0:0:2::1]
Contact URI Host Port: 5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: +g.3gpp.mid-call
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.ps2cs-srvcc-orig-pre-alerting
Contact parameter: video
Contact parameter: +g.3gpp.smsip
Contact parameter: text
To: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6382823e
From: <sip:+98765432100@test.3gpp.com>;tag=6382823e
SIP from address: sip:+98765432100@test.3gpp.com
SIP from address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP from address Host Part: test.3gpp.com
SIP from tag: 6382823e
Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1
[Generated Call-ID: SUnkKfWjftMfBtyk4UTOhw..@2001:0:0:2::1]
CSeq: 1 NOTIFY
Sequence Number: 1
Method: NOTIFY
User-Agent: Test VONR-RCSUP-ePDG-IR94-RTT-ussd-VVM SEC/SM-G998U G998USQU4AUG8
P-Access-Network-Info: 3GPP-NR-FDD;utran-cell-id-3gpp=00101000001000000000
access-type: 3GPP-NR-FDD
utran-cell-id-3gpp: 00101000001000000000
Content-Length: 0
|
[8] Request: INVITE sip:+98765432100@[2001:0:0:2::1]:5060 |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
Transmission Control Protocol, Src Port: 58024, Dst Port: 5060, Seq: 1, Ack: 1, Len: 2069
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:+98765432100@[2001:0:0:2::1]:5060 SIP/2.0
Method: INVITE
Request-URI: sip:+98765432100@[2001:0:0:2::1]:5060
Request-URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Request-URI Host Part: [2001:0:0:2::1]
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP [2001:0:0:11::2]:58024;branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6407;
rport;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 58024
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6407
RPort: rport
transport=tcp
Via: SIP/2.0/TCP [2001:0:0:11::2]:57994;
branch=z9hG4bK9216066c0d2b4e51b61f22f36db61549c6782a09;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 57994
Branch: z9hG4bK9216066c0d2b4e51b61f22f36db61549c6782a09
transport=tcp
Max-Forwards: 69
Call-ID: 80a0494490184dc1b46f8994e9e4efc7
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
CSeq: 57001 INVITE
Sequence Number: 57001
Method: INVITE
To: sip:+98765432100@test.3gpp.com
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
From: sip:0123456789@test.3gpp.com;tag=1111111111
SIP from address: sip:0123456789@test.3gpp.com
SIP from address User Part: 0123456789
SIP from address Host Part: test.3gpp.com
SIP from tag: 1111111111
Feature-Caps: *;+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Feature Cap: *
Feature Cap: g.3gpp.srvcc-alerting
Feature Cap: g.3gpp.mid-call
Allow: ACK, BYE, CANCEL, INVITE, PRACK, UPDATE
Supported: 100rel
Supported: precondition
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";audio;require;explicit
Accept: application/sdp
P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
User-Agent: Anritsu-VirtualUA/ec175bc7c
Content-Type: application/sdp
Content-Length: 848
Contact: <sip:0123456789@[2001:0:0:11::2]:57994;transport=tcp>;
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";audio;video;text;
+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Contact URI: sip:0123456789@[2001:0:0:11::2]:57994;transport=tcp
Contact URI User Part: 0123456789
Contact URI Host Part: [2001:0:0:11::2]
Contact URI Host Port: 57994
Contact URI parameter: transport=tcp
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: audio
Contact parameter: video
Contact parameter: text
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.mid-call
Privacy: none
P-Asserted-Identity: <sip:0123456789@test.3gpp.com>
SIP PAI Address: sip:0123456789@test.3gpp.com
SIP PAI User Part: 0123456789
SIP PAI Host Part: test.3gpp.com
P-Called-Party-ID: <sip:+98765432100@test.3gpp.com>
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): anritsu 733 90488 IN IP6 2001:0:0:11::2
Owner Username: anritsu
Session ID: 733
Session Version: 90488
Owner Network Type: IN
Owner Address Type: IP6
Owner Address: 2001:0:0:11::2
Session Name (s): -
Session Information (i): A VOIP Session
Connection Information (c): IN IP6 2001:0:0:11::2
Connection Network Type: IN
Connection Address Type: IP6
Connection Address: 2001:0:0:11::2
Time Description, active time (t): 0 0
Session Start Time: 0
Session Stop Time: 0
Media Description, name and address (m): audio 32000 RTP/AVP 96 97 98 99 100 8 0 101 102
Media Type: audio
Media Port: 32000
Media Protocol: RTP/AVP
Media Format: DynamicRTP-Type-96
Media Format: DynamicRTP-Type-97
Media Format: DynamicRTP-Type-98
Media Format: DynamicRTP-Type-99
Media Format: DynamicRTP-Type-100
Media Format: ITU-T G.711 PCMA
Media Format: ITU-T G.711 PCMU
Media Format: DynamicRTP-Type-101
Media Format: DynamicRTP-Type-102
Bandwidth Information (b): AS:153
Bandwidth Modifier: AS [Application Specific (RTP session bandwidth)]
Bandwidth Value: 153 kb/s
Bandwidth Information (b): RS:800
Bandwidth Modifier: RS
Bandwidth Value: 800
Bandwidth Information (b): RR:2400
Bandwidth Modifier: RR
Bandwidth Value: 2400
Media Attribute (a): ptime:20
Media Attribute Fieldname: ptime
Media Attribute Value: 20
Media Attribute (a): maxptime:240
Media Attribute Fieldname: maxptime
Media Attribute Value: 240
Media Attribute (a): rtpmap:96 EVS/16000/1
Media Attribute Fieldname: rtpmap
Media Format: 96
MIME Type: EVS
Sample Rate: 16000
Media Attribute (a): fmtp:96 max-red=220
Media Attribute Fieldname: fmtp
Media Format: 96 [EVS]
Media format specific parameters: max-red=220
Media Attribute (a): rtpmap:97 AMR-WB/16000/1
Media Attribute Fieldname: rtpmap
Media Format: 97
MIME Type: AMR-WB
Sample Rate: 16000
Media Attribute (a): fmtp:97 mode-change-capability=2
Media Attribute Fieldname: fmtp
Media Format: 97 [AMR-WB]
Media format specific parameters: mode-change-capability=2
Media Attribute (a): rtpmap:98 AMR-WB/16000/1
Media Attribute Fieldname: rtpmap
Media Format: 98
MIME Type: AMR-WB
Sample Rate: 16000
Media Attribute (a): fmtp:98 octet-align=1; mode-change-capability=2
Media Attribute Fieldname: fmtp
Media Format: 98 [AMR-WB]
Media format specific parameters: octet-align=1
Media format specific parameters: mode-change-capability=2
Media Attribute (a): rtpmap:99 AMR/8000/1
Media Attribute Fieldname: rtpmap
Media Format: 99
MIME Type: AMR
Sample Rate: 8000
Media Attribute (a): fmtp:99 mode-change-capability=2
Media Attribute Fieldname: fmtp
Media Format: 99 [AMR]
Media format specific parameters: mode-change-capability=2
Media Attribute (a): rtpmap:100 AMR/8000/1
Media Attribute Fieldname: rtpmap
Media Format: 100
MIME Type: AMR
Sample Rate: 8000
Media Attribute (a): fmtp:100 octet-align=1; mode-change-capability=2
Media Attribute Fieldname: fmtp
Media Format: 100 [AMR]
Media format specific parameters: octet-align=1
Media format specific parameters: mode-change-capability=2
Media Attribute (a): rtpmap:8 PCMA/8000/1
Media Attribute Fieldname: rtpmap
Media Format: 8
MIME Type: PCMA
Sample Rate: 8000
Media Attribute (a): rtpmap:0 PCMU/8000/1
Media Attribute Fieldname: rtpmap
Media Format: 0
MIME Type: PCMU
Sample Rate: 8000
Media Attribute (a): rtpmap:101 telephone-event/16000
Media Attribute Fieldname: rtpmap
Media Format: 101
MIME Type: telephone-event
Sample Rate: 16000
Media Attribute (a): fmtp:101 0-15
Media Attribute Fieldname: fmtp
Media Format: 101 [telephone-event]
Media format specific parameters: 0-15
Media Attribute (a): rtpmap:102 telephone-event/8000
Media Attribute Fieldname: rtpmap
Media Format: 102
MIME Type: telephone-event
Sample Rate: 8000
Media Attribute (a): fmtp:102 0-15
Media Attribute Fieldname: fmtp
Media Format: 102 [telephone-event]
Media format specific parameters: 0-15
Media Attribute (a): mid:0
Media Attribute Fieldname: mid
Media Attribute Value: 0
Media Attribute (a): rtcp:32001
Media Attribute Fieldname: rtcp
Media Attribute Value: 32001
Media Attribute (a): curr:qos local none
Media Attribute Fieldname: curr
Media Attribute Value: qos local none
Media Attribute (a): curr:qos remote none
Media Attribute Fieldname: curr
Media Attribute Value: qos remote none
Media Attribute (a): des:qos mandatory local sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos mandatory local sendrecv
Media Attribute (a): des:qos optional remote sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos optional remote sendrecv
Media Attribute (a): sendrecv
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
|
[9] Status: 183 Session Progress |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
Transmission Control Protocol, Src Port: 5060, Dst Port: 58024, Seq: 1001, Ack: 2070, Len: 574
Session Initiation Protocol (183)
Status-Line: SIP/2.0 183 Session Progress
Status-Code: 183
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP [2001:0:0:11::2]:58024;branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6407;rport;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 58024
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6407
RPort: rport
transport=tcp
Via: SIP/2.0/TCP [2001:0:0:11::2]:57994;branch=z9hG4bK9216066c0d2b4e51b61f22f36db61549c6782a09;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 57994
Branch: z9hG4bK9216066c0d2b4e51b61f22f36db61549c6782a09
transport=tcp
Max-Forwards: 70
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
Require: precondition, 100rel
[truncated]Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-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-p
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Contact URI Host Part: [2001:0:0:2::1]
Contact URI Host Port: 5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: +g.3gpp.mid-call
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.ps2cs-srvcc-orig-pre-alerting
Contact parameter: video
Contact parameter: text
To: <sip:+98765432100@test.3gpp.com>;tag=6c0f9425
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6c0f9425
From: <sip:0123456789@test.3gpp.com>;tag=1111111111
SIP from address: sip:0123456789@test.3gpp.com
SIP from address User Part: 0123456789
SIP from address Host Part: test.3gpp.com
SIP from tag: 1111111111
Call-ID: 80a0494490184dc1b46f8994e9e4efc7
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
CSeq: 57001 INVITE
Sequence Number: 57001
Method: INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, INFO, REFER, NOTIFY, MESSAGE, PRACK
Content-Type: application/sdp
Supported: timer, 100rel, precondition
User-Agent: T-Mobile VONR-RCSUP-ePDG-IR94-RTT-ussd-VVM SEC/SM-G998U G998USQU4AUG8
RSeq: 1
P-Access-Network-Info: 3GPP-NR-FDD;utran-cell-id-3gpp=00101000001000000000
access-type: 3GPP-NR-FDD
utran-cell-id-3gpp: 00101000001000000000
Content-Length: 464
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): SAMSUNG-IMS-UE 175962184 0 IN IP6 2001:0:0:2::1
Owner Username: SAMSUNG-IMS-UE
Session ID: 175962184
Session Version: 0
Owner Network Type: IN
Owner Address Type: IP6
Owner Address: 2001:0:0:2::1
Session Name (s): SS VOIP
Connection Information (c): IN IP6 2001:0:0:2::1
Connection Network Type: IN
Connection Address Type: IP6
Connection Address: 2001:0:0:2::1
Time Description, active time (t): 0 0
Session Start Time: 0
Session Stop Time: 0
Media Description, name and address (m): audio 1234 RTP/AVP 96 101
Media Type: audio
Media Port: 1234
Media Protocol: RTP/AVP
Media Format: DynamicRTP-Type-96
Media Format: DynamicRTP-Type-101
Bandwidth Information (b): AS:38
Bandwidth Modifier: AS [Application Specific (RTP session bandwidth)]
Bandwidth Value: 38 kb/s
Bandwidth Information (b): RS:0
Bandwidth Modifier: RS
Bandwidth Value: 0
Bandwidth Information (b): RR:2500
Bandwidth Modifier: RR
Bandwidth Value: 2500
Media Attribute (a): rtpmap:96 EVS/16000
Media Attribute Fieldname: rtpmap
Media Format: 96
MIME Type: EVS
Sample Rate: 16000
Media Attribute (a): fmtp:96 bw=nb-swb;br=5.9-13.2;max-red=220
Media Attribute Fieldname: fmtp
Media Format: 96 [EVS]
Media format specific parameters: bw=nb-swb
Media format specific parameters: br=5.9-13.2
Media format specific parameters: max-red=220
Media Attribute (a): rtpmap:101 telephone-event/16000
Media Attribute Fieldname: rtpmap
Media Format: 101
MIME Type: telephone-event
Sample Rate: 16000
Media Attribute (a): fmtp:101 0-15
Media Attribute Fieldname: fmtp
Media Format: 101 [telephone-event]
Media format specific parameters: 0-15
Media Attribute (a): ptime:20
Media Attribute Fieldname: ptime
Media Attribute Value: 20
Media Attribute (a): maxptime:240
Media Attribute Fieldname: maxptime
Media Attribute Value: 240
Media Attribute (a): sendrecv
Media Attribute (a): curr:qos local none
Media Attribute Fieldname: curr
Media Attribute Value: qos local none
Media Attribute (a): curr:qos remote none
Media Attribute Fieldname: curr
Media Attribute Value: qos remote none
Media Attribute (a): des:qos mandatory local sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos mandatory local sendrecv
Media Attribute (a): des:qos mandatory remote sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos mandatory remote sendrecv
Media Attribute (a): conf:qos remote sendrecv
Media Attribute Fieldname: conf
Media Attribute Value: qos remote sendrecv
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
|
[10] Request: PRACK sip:+98765432100@[2001:0:0:2::1]:5060 |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (PRACK)
Request-Line: PRACK sip:+98765432100@[2001:0:0:2::1]:5060 SIP/2.0
Method: PRACK
Request-URI: sip:+98765432100@[2001:0:0:2::1]:5060
Request-URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Request-URI Host Part: [2001:0:0:2::1]
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP [2001:0:0:11::2]:5060;branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6409;rport;transport=udp
Transport: UDP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 5060
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6409
RPort: rport
transport=udp
Via: SIP/2.0/UDP [2001:0:0:11::2]:64066;branch=z9hG4bK9216066c0d2b4e51b61f22f36db61549dc00911e
Transport: UDP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 64066
Branch: z9hG4bK9216066c0d2b4e51b61f22f36db61549dc00911e
Max-Forwards: 69
Call-ID: 80a0494490184dc1b46f8994e9e4efc7
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
CSeq: 57002 PRACK
Sequence Number: 57002
Method: PRACK
To: <sip:+98765432100@test.3gpp.com>;tag=6c0f9425
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6c0f9425
From: <sip:0123456789@test.3gpp.com>;tag=1111111111
SIP from address: sip:0123456789@test.3gpp.com
SIP from address User Part: 0123456789
SIP from address Host Part: test.3gpp.com
SIP from tag: 1111111111
RAck: 1 57001 INVITE
RSeq Sequence Number: 1
CSeq Sequence Number: 57001
CSeq Method: INVITE
Require: precondition
Require: 100rel
Supported: precondition
Supported: 100rel
User-Agent: Anritsu-VirtualUA/ec175bc7c
Content-Length: 0
Privacy: none
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
|
[11] Status: 200 OK (PRACK) |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
[Request Frame: 182]
[Response Time (ms): 40]
Message Header
Via: SIP/2.0/UDP [2001:0:0:11::2]:5060;branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6409;rport;transport=udp
Transport: UDP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 5060
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6409
RPort: rport
transport=udp
Via: SIP/2.0/UDP [2001:0:0:11::2]:64066;branch=z9hG4bK9216066c0d2b4e51b61f22f36db61549dc00911e
Transport: UDP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 64066
Branch: z9hG4bK9216066c0d2b4e51b61f22f36db61549dc00911e
Max-Forwards: 70
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
[truncated]Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-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-p
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Contact URI Host Part: [2001:0:0:2::1]
Contact URI Host Port: 5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: +g.3gpp.mid-call
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.ps2cs-srvcc-orig-pre-alerting
Contact parameter: video
Contact parameter: text
To: <sip:+98765432100@test.3gpp.com>;tag=6c0f9425
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6c0f9425
From: <sip:0123456789@test.3gpp.com>;tag=1111111111
SIP from address: sip:0123456789@test.3gpp.com
SIP from address User Part: 0123456789
SIP from address Host Part: test.3gpp.com
SIP from tag: 1111111111
Call-ID: 80a0494490184dc1b46f8994e9e4efc7
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
CSeq: 57002 PRACK
Sequence Number: 57002
Method: PRACK
User-Agent: T-Mobile VONR-RCSUP-ePDG-IR94-RTT-ussd-VVM SEC/SM-G998U G998USQU4AUG8
P-Access-Network-Info: 3GPP-NR-FDD;utran-cell-id-3gpp=00101000001000000000
access-type: 3GPP-NR-FDD
utran-cell-id-3gpp: 00101000001000000000
Content-Length: 0
|
[12] Request: UPDATE sip:+98765432100@[2001:0:0:2::1]:5060 |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
Transmission Control Protocol, Src Port: 58024, Dst Port: 5060, Seq: 2070, Ack: 1575, Len: 1481
Session Initiation Protocol (UPDATE)
Request-Line: UPDATE sip:+98765432100@[2001:0:0:2::1]:5060 SIP/2.0
Method: UPDATE
Request-URI: sip:+98765432100@[2001:0:0:2::1]:5060
Request-URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Request-URI Host Part: [2001:0:0:2::1]
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP [2001:0:0:11::2]:58024;
branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a640c;rport;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 58024
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a640c
RPort: rport
transport=tcp
Via: SIP/2.0/TCP [2001:0:0:11::2]:57994;
branch=z9hG4bK9216066c0d2b4e51b61f22f36db6154999fc9d3b;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 57994
Branch: z9hG4bK9216066c0d2b4e51b61f22f36db6154999fc9d3b
transport=tcp
Max-Forwards: 69
Call-ID: 80a0494490184dc1b46f8994e9e4efc7
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
CSeq: 57003 UPDATE
Sequence Number: 57003
Method: UPDATE
To: <sip:+98765432100@test.3gpp.com>;tag=6c0f9425
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6c0f9425
From: <sip:0123456789@test.3gpp.com>;tag=1111111111
SIP from address: sip:0123456789@test.3gpp.com
SIP from address User Part: 0123456789
SIP from address Host Part: test.3gpp.com
SIP from tag: 1111111111
Supported: 100rel
Supported: precondition
Require: precondition
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: Anritsu-VirtualUA/ec175bc7c
Content-Type: application/sdp
Content-Length: 473
Contact: <sip:0123456789@[2001:0:0:11::2]:57994;transport=tcp>;
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";audio;video;text;
+g.3gpp.srvcc-alerting;+g.3gpp.mid-call
Contact URI: sip:0123456789@[2001:0:0:11::2]:57994;transport=tcp
Contact URI User Part: 0123456789
Contact URI Host Part: [2001:0:0:11::2]
Contact URI Host Port: 57994
Contact URI parameter: transport=tcp
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: audio
Contact parameter: video
Contact parameter: text
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.mid-call
Privacy: none
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): anritsu 733 90489 IN IP6 2001:0:0:11::2
Owner Username: anritsu
Session ID: 733
Session Version: 90489
Owner Network Type: IN
Owner Address Type: IP6
Owner Address: 2001:0:0:11::2
Session Name (s): -
Session Information (i): A VOIP Session
Connection Information (c): IN IP6 2001:0:0:11::2
Connection Network Type: IN
Connection Address Type: IP6
Connection Address: 2001:0:0:11::2
Time Description, active time (t): 0 0
Session Start Time: 0
Session Stop Time: 0
Media Description, name and address (m): audio 32000 RTP/AVP 96 101
Media Type: audio
Media Port: 32000
Media Protocol: RTP/AVP
Media Format: DynamicRTP-Type-96
Media Format: DynamicRTP-Type-101
Bandwidth Information (b): AS:38
Bandwidth Modifier: AS [Application Specific (RTP session bandwidth)]
Bandwidth Value: 38 kb/s
Bandwidth Information (b): RS:0
Bandwidth Modifier: RS
Bandwidth Value: 0
Bandwidth Information (b): RR:2500
Bandwidth Modifier: RR
Bandwidth Value: 2500
Media Attribute (a): ptime:20
Media Attribute Fieldname: ptime
Media Attribute Value: 20
Media Attribute (a): maxptime:240
Media Attribute Fieldname: maxptime
Media Attribute Value: 240
Media Attribute (a): rtpmap:96 EVS/16000/1
Media Attribute Fieldname: rtpmap
Media Format: 96
MIME Type: EVS
Sample Rate: 16000
Media Attribute (a): fmtp:96 bw=nb-swb; br=5.9-13.2; max-red=220
Media Attribute Fieldname: fmtp
Media Format: 96 [EVS]
Media format specific parameters: bw=nb-swb
Media format specific parameters: br=5.9-13.2
Media format specific parameters: max-red=220
Media Attribute (a): rtpmap:101 telephone-event/16000
Media Attribute Fieldname: rtpmap
Media Format: 101
MIME Type: telephone-event
Sample Rate: 16000
Media Attribute (a): fmtp:101 0-15
Media Attribute Fieldname: fmtp
Media Format: 101 [telephone-event]
Media format specific parameters: 0-15
Media Attribute (a): mid:0
Media Attribute Fieldname: mid
Media Attribute Value: 0
Media Attribute (a): rtcp:32001
Media Attribute Fieldname: rtcp
Media Attribute Value: 32001
Media Attribute (a): curr:qos local sendrecv
Media Attribute Fieldname: curr
Media Attribute Value: qos local sendrecv
Media Attribute (a): curr:qos remote none
Media Attribute Fieldname: curr
Media Attribute Value: qos remote none
Media Attribute (a): des:qos mandatory local sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos mandatory local sendrecv
Media Attribute (a): des:qos mandatory remote sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos mandatory remote sendrecv
Media Attribute (a): sendrecv
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
|
[13] Status: 200 OK (UPDATE) |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
Transmission Control Protocol, Src Port: 5060, Dst Port: 58024, Seq: 2575, Ack: 3551, Len: 556
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP [2001:0:0:11::2]:58024;branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a640c;rport;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 58024
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a640c
RPort: rport
transport=tcp
Via: SIP/2.0/TCP [2001:0:0:11::2]:57994;branch=z9hG4bK9216066c0d2b4e51b61f22f36db6154999fc9d3b;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 57994
Branch: z9hG4bK9216066c0d2b4e51b61f22f36db6154999fc9d3b
transport=tcp
Max-Forwards: 70
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
Require: precondition
[truncated]Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-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-p
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Contact URI Host Part: [2001:0:0:2::1]
Contact URI Host Port: 5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: +g.3gpp.mid-call
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.ps2cs-srvcc-orig-pre-alerting
Contact parameter: video
Contact parameter: text
To: <sip:+98765432100@test.3gpp.com>;tag=6c0f9425
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6c0f9425
From: <sip:0123456789@test.3gpp.com>;tag=1111111111
SIP from address: sip:0123456789@test.3gpp.com
SIP from address User Part: 0123456789
SIP from address Host Part: test.3gpp.com
SIP from tag: 1111111111
Call-ID: 80a0494490184dc1b46f8994e9e4efc7
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
CSeq: 57003 UPDATE
Sequence Number: 57003
Method: UPDATE
Session-Expires: 1800;refresher=uas
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, INFO, REFER, NOTIFY, MESSAGE, PRACK
Content-Type: application/sdp
Supported: timer, 100rel, precondition
User-Agent: T-Mobile VONR-RCSUP-ePDG-IR94-RTT-ussd-VVM SEC/SM-G998U G998USQU4AUG8
P-Access-Network-Info: 3GPP-NR-FDD;utran-cell-id-3gpp=00101000001000000000
access-type: 3GPP-NR-FDD
utran-cell-id-3gpp: 00101000001000000000
Content-Length: 440
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): SAMSUNG-IMS-UE 175962184 1 IN IP6 2001:0:0:2::1
Owner Username: SAMSUNG-IMS-UE
Session ID: 175962184
Session Version: 1
Owner Network Type: IN
Owner Address Type: IP6
Owner Address: 2001:0:0:2::1
Session Name (s): SS VOIP
Connection Information (c): IN IP6 2001:0:0:2::1
Connection Network Type: IN
Connection Address Type: IP6
Connection Address: 2001:0:0:2::1
Time Description, active time (t): 0 0
Session Start Time: 0
Session Stop Time: 0
Media Description, name and address (m): audio 1234 RTP/AVP 96 101
Media Type: audio
Media Port: 1234
Media Protocol: RTP/AVP
Media Format: DynamicRTP-Type-96
Media Format: DynamicRTP-Type-101
Bandwidth Information (b): AS:38
Bandwidth Modifier: AS [Application Specific (RTP session bandwidth)]
Bandwidth Value: 38 kb/s
Bandwidth Information (b): RS:0
Bandwidth Modifier: RS
Bandwidth Value: 0
Bandwidth Information (b): RR:2500
Bandwidth Modifier: RR
Bandwidth Value: 2500
Media Attribute (a): rtpmap:96 EVS/16000
Media Attribute Fieldname: rtpmap
Media Format: 96
MIME Type: EVS
Sample Rate: 16000
Media Attribute (a): fmtp:96 bw=nb-swb;br=5.9-13.2;max-red=220
Media Attribute Fieldname: fmtp
Media Format: 96 [EVS]
Media format specific parameters: bw=nb-swb
Media format specific parameters: br=5.9-13.2
Media format specific parameters: max-red=220
Media Attribute (a): rtpmap:101 telephone-event/16000
Media Attribute Fieldname: rtpmap
Media Format: 101
MIME Type: telephone-event
Sample Rate: 16000
Media Attribute (a): fmtp:101 0-15
Media Attribute Fieldname: fmtp
Media Format: 101 [telephone-event]
Media format specific parameters: 0-15
Media Attribute (a): ptime:20
Media Attribute Fieldname: ptime
Media Attribute Value: 20
Media Attribute (a): maxptime:240
Media Attribute Fieldname: maxptime
Media Attribute Value: 240
Media Attribute (a): sendrecv
Media Attribute (a): curr:qos local none
Media Attribute Fieldname: curr
Media Attribute Value: qos local none
Media Attribute (a): curr:qos remote sendrecv
Media Attribute Fieldname: curr
Media Attribute Value: qos remote sendrecv
Media Attribute (a): des:qos mandatory local sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos mandatory local sendrecv
Media Attribute (a): des:qos mandatory remote sendrecv
Media Attribute Fieldname: des
Media Attribute Value: qos mandatory remote sendrecv
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
|
[14] Status: 180 Ringing |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
Transmission Control Protocol, Src Port: 5060, Dst Port: 58024, Seq: 3131, Ack: 3551, Len: 941
Session Initiation Protocol (180)
Status-Line: SIP/2.0 180 Ringing
Status-Code: 180
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP [2001:0:0:11::2]:58024;
branch=z9hG4bKb0149d1122e24dd6a49f63b786d0a6407;rport;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 58024
Branch: z9hG4bKb0149d1122e24dd6a49f63b786d0a6407
RPort: rport
transport=tcp
Via: SIP/2.0/TCP [2001:0:0:11::2]:57994;
branch=z9hG4bK9216066c0d2b4e51b61f22f36db61549c6782a09;transport=tcp
Transport: TCP
Sent-by Address: 2001:0:0:11::2
Sent-by port: 57994
Branch: z9hG4bK9216066c0d2b4e51b61f22f36db61549c6782a09
transport=tcp
Max-Forwards: 70
Record-Route: <sip:[2001:0:0:11::2]:5060;lr>
Record-Route URI: sip:[2001:0:0:11::2]:5060;lr
Record-Route Host Part: [2001:0:0:11::2]
Record-Route Host Port: 5060
Record-Route URI parameter: lr
[truncated]Contact: <sip:+98765432100@[2001:0:0:2::1]:5060>;
+sip.instance="<urn:gsma:imei:35012167-001225-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-p
Contact URI: sip:+98765432100@[2001:0:0:2::1]:5060
Contact URI User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
Contact URI Host Part: [2001:0:0:2::1]
Contact URI Host Port: 5060
Contact parameter: +sip.instance="<urn:gsma:imei:35012167-001225-0>"
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact parameter: +g.3gpp.mid-call
Contact parameter: +g.3gpp.srvcc-alerting
Contact parameter: +g.3gpp.ps2cs-srvcc-orig-pre-alerting
Contact parameter: video
Contact parameter: text
To: <sip:+98765432100@test.3gpp.com>;tag=6c0f9425
SIP to address: sip:+98765432100@test.3gpp.com
SIP to address User Part: +98765432100
E.164 number (MSISDN): 98765432100
Country Code: Iran (Islamic Republic of) (98)
SIP to address Host Part: test.3gpp.com
SIP to tag: 6c0f9425
From: <sip:0123456789@test.3gpp.com>;tag=1111111111
SIP from address: sip:0123456789@test.3gpp.com
SIP from address User Part: 0123456789
SIP from address Host Part: test.3gpp.com
SIP from tag: 1111111111
Call-ID: 80a0494490184dc1b46f8994e9e4efc7
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
CSeq: 57001 INVITE
Sequence Number: 57001
Method: INVITE
Supported: timer, 100rel, precondition
User-Agent: T-Mobile VONR-RCSUP-ePDG-IR94-RTT-ussd-VVM SEC/SM-G998U G998USQU4AUG8
P-Access-Network-Info: 3GPP-NR-FDD;utran-cell-id-3gpp=00101000001000000000
access-type: 3GPP-NR-FDD
utran-cell-id-3gpp: 00101000001000000000
Content-Length: 0
|
[15] EVS 107 PT=EVS, SSRC=0x33050, Seq=1, Time=277680, Mark, EVS Primary 13.2 |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:2::1, Dst: 2001:0:0:11::2
User Datagram Protocol, Src Port: 1234, Dst Port: 32000
Real-Time Transport Protocol
[Stream setup by SDP (frame 185)]
[Setup frame: 185]
[Setup Method: SDP]
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
10.. .... = Version: RFC 1889 Version (2)
..0. .... = Padding: False
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0
1... .... = Marker: True
Payload type: EVS (96)
Sequence number: 1
[Extended sequence number: 65537]
Timestamp: 277680
Synchronization Source identifier: 0x00033050 (208976)
Enhanced Voice Services
[Framing Mode: Compact]
EVS Primary 13.2, packet_len 264 bits
Voice Data
0111 0... = BW CT RF Index: SWB inactive (14)
|
[16] EVS 107 PT=EVS, SSRC=0x33051, Seq=1, Time=277680, Mark, EVS Primary 13.2 |
SIP message from a packet capture. The text is what was on the wire, not specification text.
Internet Protocol Version 6, Src: 2001:0:0:11::2, Dst: 2001:0:0:2::1
User Datagram Protocol, Src Port: 32000, Dst Port: 1234
Real-Time Transport Protocol
[Stream setup by SDP (frame 190)]
[Setup frame: 190]
[Setup Method: SDP]
[Generated Call-ID: 80a0494490184dc1b46f8994e9e4efc7]
10.. .... = Version: RFC 1889 Version (2)
..0. .... = Padding: False
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0
1... .... = Marker: True
Payload type: EVS (96)
Sequence number: 1
[Extended sequence number: 65537]
Timestamp: 277680
Synchronization Source identifier: 0x00033051 (208977)
Enhanced Voice Services
[Framing Mode: Compact]
EVS Primary 13.2, packet_len 264 bits
Voice Data
0111 0... = BW CT RF Index: SWB inactive (14)
Reference
- 5G VOICE OVER NEW RADIO(VoNR) - Rhode & SCHWARZ WhitePaper
- Voice Over NR (VoNR Call Flow)
- 3GPP 23.501 - System architecture for the 5G System (5GS)
- 3GPP 23.228 - IP Multimedia Subsystem (IMS)