provider spezifikation docsis 3 - unitymedia · um ts 411 2 von 65 02.05.2018 conventions...

UM TS 411 1 von 65 02.05.2018

passive NTP; Provider Specific Requirements

UM TS 411a

Provider Specific Requirements for a passive Network Termina-tion Point in DOCSIS 3.1 Environments

Version 1.0

UM TS 411 2 von 65 02.05.2018

Conventions

Throughout this document, the words that are used to define the significance of particular require-ments are capitalized. These words are:

"MUST, SHALL”

This word means that the item is an absolute requirement of this specification.

"MUST NOT" This phrase means that the item is an absolute prohibition of this specifica-tion.

"SHOULD" This word means that there may exist valid reasons in particular circumstanc-es to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course.

"SHOULD NOT"

This phrase means that there may exist valid reasons in particular circum-stances when the listed behavior is acceptable or even useful, but the full im-plications should be understood and the case carefully weighed before im-plementing any behavior described with this label.

"MAY" This word means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item.

UM TS 411 3 von 65 02.05.2018

Contact Unitymedia NRW GmbH Aachener Strasse 746 – 750 50933 Köln Unitymedia Hessen GmbH & Co. KG Aachener Strasse 746 – 750 50933 Köln Unitymedia BW GmbH Aachener Strasse 746 – 750 50933 Köln

UM TS 411 4 von 65 02.05.2018

PROVIDER SPECIFIC REQUIREMENTS FOR THE PASSIVE NETWORK TERMINATION POINT IN DOCSIS 3.0 ENVIRONMENT; 1

1 SCOPE 5

2 REFERENCES 5

2.1. NORMATIVE REFERENCES 5 2.2. INFORMATIVE REFERENCES 6

3 DEFINITIONS AND ABBREVIATIONS 6

3.1. DEFINITIONS 6 3.2. ABBREVIATIONS 7

4 RF INTERFACE CONNECTOR 8

5 NETWORK RF CHARACTERISTICS 8

6 CABLELABS SPECIFICATIONS CMCI/MULPI/OSSI/PHY/SEC 9

6.1. HARDWARE REQUIREMENTS 9 6.2. FIRMWARE UPDATES 9 6.3. CONSOLE ACCESS 9 6.4. CM PROVISIONING 10 6.5. MTA INITIALIZATION 11

7 VOICE SERVICES 11

7.1. RFCS TO SUPPORT 11 7.2. SUPPORTED SDP VALUES 11 7.3. QOS 11 7.4. METHODS AND CALL FEATURES 12 7.5. CALL FEATURES NOT SUPPORTED 12 7.6. SIP CLIENTS 12

7.6.1 . Packetcable 12 7.6.2 . IPv6 12 7.6.3 . Credentials 12

7.7. EMERGENCY CALLS 13 7.8. TONES 13

8 IP PROTOCOLS 13

8.1. SPECIFICS FOR DS LITE 13 8.2. ACCESS TO THE IPV4 13 8.3. VARIABLE AFTR ENDPOINT ADDRESSES 13

9 ADDITIONAL SECURITY RECOMMENDATIONS (STANDARD CONFIGURATION PARAMETERS) 13

APPENDIX I: TRACE EXAMPLE FOR REGISTRATION 14

APPENDIX II: TRACE EXAMPLE FOR BASIC OUTGOING CALL 16

APPENDIX III: TRACE EXAMPLE FOR CALL WAITING 20

APPENDIX IV: TRACE EXAMPLE FOR CALLER ID (CLIP) 25

APPENDIX V: TRACE EXAMPLE FOR CALLER ID DURING CALL WAITING 29

APPENDIX VI: TRACE EXAMPLE FOR PHONE NUMBER SUPPRESSION (CLIR) 38

APPENDIX VII: TRACE EXAMPLE FOR 3 WAY CONFERENCE 42

APPENDIX VIII: TRACE EXAMPLE FOR CALL HOLD 55

UM TS 411 5 von 65 02.05.2018

1 Scope

This interface specification describes and specifies the additional Unitymedia Specific Requirements and Deviations of the main characteristics of the dedicated data RF interface, laid down in the document [1], in the OPERATOR cable network at the user’s coaxial passive network termination point. The Unitymedia UM TS 411a and [1] are related and apply together. This interface specification describes the typical limits or values within which the RF characteristics can be expected to re-main for networks that are built according to OPERATOR specifications at installation time.

The interface specification does not apply under abnormal operating conditions such as:

- operating conditions arising as a result of operating services other than DOCSIS 3.0 over the dedicated data RF in-terface.

- operating conditions arising as a result of a fault, maintenance and construction work or to minimize the extend of interruption of service.

- operating conditions arising as a result of force majeure or third party interference. - operating conditions arising as a result of test signal injection governed by regulation. - In case of non-compliance of a network user’s installation or non-compliance of equipment with the relevant stand-

ards or non-compliance with the technical requirements for connection, established either by this interface specifi-cation or the public authorities including the relevant limits for electromagnetic compatibility.

The characteristics given in this interface specification are intended to be used to derive and specify requirements for equipment such as coaxial cables and cable modems to connect them to the dedicated data RF interface. The values in this interface specification take precedence over requirements in equipment product standards and in installation standards. The given characteristics are not intended to be used as electromagnetic compatibility levels or user emission limits in the OP-ERATOR network.

This interface specification may be changed at any time. The customer of this specification has to check the newest version at the OPERATOR support tools. This standard may be superseded in total or in part by the terms of a contract between the individual network user and the OPERATOR.

2 References

2.1. Normative references

[1] Specification for a passive Network Termination Point in DOCSIS 3.1 Environments; Net-work and Provisioning requirements v1.0

[2] ITU-T, G711A law: Pulse Code Modulation (PCM) of voice frequencies

[3] CableLabs “Data Over Cable Service Interface Specifications, DOCSIS 3.0 Operations Sup-port System Interface Specification CM-SP-OSSIv3.0-I28-151210”

[4] RFC 3261 - SIP: Session Initiation Protocol

[5] RFC 2833 - RTP Payload for DTMF Digits

[6] RFC 6333 Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion

[7] RFC 6334 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite

[8] TLV 202 – eRouter Operation Mode encoding

UM TS 411 6 von 65 02.05.2018

2.2. Informative references

[i.1] Deutsch Telekom 1 TR 110 -1

[i.2] ETSI ETS 300 001, Attachments to Public Switched Telephone Network (PSTN); General technical requirements for equipment connected to an analogue subscriber interface in the PSTN

[i.3] CableLabs “Data Over Cable Service Interface Specifications, DOCSIS 3.1 MAC and Upper Layer Protocols Interface Specification CM-SP-MULPIv3.1-I15-180509”

[i.4] CableLabs “Data Over Cable Service Interface Specifications, DOCSIS 3.1 Operations Sup-port System Interface Specification CM-SP-OSSIv3.1-I12-180509”

[i.5] CableLabs “Data Over Cable Service Interface Specifications, DOCSIS 3.1 Security Specifi-cation CM-SP-SECv3.1-I07-170111”

[i.6] Bundesamt für Sicherheit in der Informationstechnik: “Testkonzept für Breitbandrouter”; https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Cyber-Sicherheit/Themen/Testkonzept-Breitbandrouter.html

[i.7] WISI Werknorm WN744-747; Wiclick Buchse

[i.8] CableLabs “Data Over Cable Service Interface Specifications DOCSIS 3.1 Physical Layer Specification CM-SP-PHYv3.1-I14-180509

3 Definitions and abbreviations

3.1. Definitions

Service Flows A MAC layer transport service which provides unidirectional transport of packets from the upper layer service entity to the RF and shapes, polices, and prioritizes traffic according to QoS traffic parameters defined for the Flow. Bootfiles Docsis Config File which contains Classifiers for QoS and schedule, Baseline Privacy (BPI) etc. Console Access Console ports are meant to allow access to the router via a terminal interface. Connecting to the console port you can get remote access (to the root level of a router) without using the network that the router is connected to. Provisioning Provisioning Systems • The DHCP servers provide the CM with initial configuration information, including the de-vice IP address(es), when the CM boots. • The Configuration File server is used to down-load configuration files to CMs when they boot. Configuration files are in binary format and permit the configuration of the CM's parameters.

UM TS 411 7 von 65 02.05.2018

PacketCable PacketCable is a technology specification defined by the industry consortium CableLabs for using Internet Protocol (IP) networks to deliver multimedia services

3.2. Abbreviations

AFTR Address Family Transition Router BSI Bundesamt für Sicherheit in der Informationstechnik CFNR Call Forward No Reply CLIP Calling Line Identification Presentation CLIR Calling Line Identification Restriction CM Cable Modem CMTS Cable Modem Termination System CPE Customer Premise Equipment CVC Code Verification Certificate DNS Domain Name System DHCP Dynamic Host Configuration Protocol DS Downstream DS-Lite Dual Stack Lite eRouter embedded Router FQDN Fully Qualified Domain Name GUI Graphical User Interface HTTPS Hyper Text Transfer Protocoll Secure IPv6 Internet Protocol Version 6 ITU International Telecommunication Union MSS Clamping Maximum Segment Size Clamping MTA Multimedia Terminal Adapter PSTN Public Switched Telephone Network QoS Quality of Service RF Radio Frequency RFC Request For Comments SDP Session Description Protocol SIP Session Internet Protocol SNMP Simple Network Management Protocol TLV Type Length Value TR Technische Richtlinie TTL Time To Live UPnP Universal Plug&Play US Upstream UGS Unsolicited Grant Service WAN Wide Area Network

UM TS 411 8 von 65 02.05.2018

4 RF Interface Connector

According to [1], Chapter 4. Deviating to [1], Chapter 4.3 the mechanical interface may be [i.7] instead of f-type.

5 Network RF Characteristics

This clause describes and defines the RF parameters and requirements at the customer’s pNTP.

5.1. Downstream RF characteristics

5.1.1. Downstream Frequency Range

The channel spacing takes into account downstream path channel bandwidths 8 MHz.for digital TV and DOCSIS QAM channels in the frequency band from 110 to 1002 MHz. DOCSIS 3.0 channels are grouped into blocks of 4, 8 or more. DOCSIS 3.1 channels are OFDM channels of up to 192 MHz wide. The DOCSIS 3.1 downstream frequency range is 110 to 1218 MHz (edge frequency).

5.1.2. Downstream RF performance

Table 3 specifies the downstream performance characteristic at the pNTP.

Table 3: Network Downstream Performance Characteristics at the pNTP

Parameter Nominal ratings and characteristics Absolute maximum ratings and characteristics during normal operation

total input power < 93 dB(µV) ([10], B.6.3.2)

analogue carriers 68

analogue video carrier level 60 to 77 dB(µV) ([6], Chapter 5.4.1) 80 dB(µV)

signal tilt ≤ 12 dB ([6], Chapter 5.4.2)

channel signal tilt ≤ 8 dB

group delay ≤ 100 ns ([6], Chapter 5.6.2)

64 QAM signal level 47 to 67 dB(µV) (see [6], Chapter 5.4.1)

64 QAM BER (pre FEC) < 1 x 10-7

(typ. 1 x 10-8

) 1 x 10-4

(see [6], Chapter 5.8)

64 QAM MER ≥ 26 dB (typ. 30 dB, see [6], Chapter 5.8) ≥ 23 dB

256 QAM signal level 54 to 74 dB(µV) (see [6], Chapter 5.4.1)

256 QAM BER (pre FEC) < 1 x 10-6

(typ. 1 x 10-7

)

1 x 10-4

(see [6], Chapter 5.8)

256 QAM MER ≥ 32 dB (see [6], Chapter 5.8) ≥ 29 dB

OFDM signal level (per 8 MHz)

54 to 74 dB(µV)

OFDM MER See table [6] of [i.8] See note 1

Note 1: In DOCSIS 3.1 OFDM technology, a modulation might be present at the pNTP that does not need to be demodulated by the cable modem. A CMTS will address the cable modem with the most suitable modulation.

Table 4: Micro reflections at the pNTP

time nominal value1.

≤ 0,5 µs -10 dBc

≤ 1,0 µs -15 dBc

≤ 1,5 µs -20 dBc

> 1,5 µs -31.5 dBc 1.

see [10], B.5.2.1

UM TS 411 9 von 65 02.05.2018

5.2. Upstream RF characteristics

5.2.1. Upstream RF performance

The upstream spectrum used for DOCSIS operation is divided into 3.2 MHz and 6.4 MHz wide chan-nels and OFDMA channels in the frequency range from 5 MHz to 65 MHz.

5.2.2. Upstream RF performance

Table 5: Network Upstream Characteristics at the pNTP

Parameter Nominal ratings and charac-teristics at installation time

Absolute maximum ratings and characteristics

upstream level range Max total average output pow-er of 125 dB(µV)

4.

114 dB dB(µV)

C/(N+I)2. ≥ 71 dB

1.

BER2.

≤ 10-9

PER2.

≤ 10-8

amplitude ripple 0.5 dB/MHz3.

group delay ripple 200 ns/MHz3.

carrier hum modulation ≤ -23 dBc

1. OPERATOR specific

2. 16 QAM in 3.2 MHz channel

3. see [10], 5.2.2

4. Due to the used OFDMA modulation a range cannot be defined, only a total maximum output

power

The upstream spurious emissions shall meet table 11 of [i.8]

6 CableLabs specifications CMCI/MULPI/OSSI/PHY/SEC

6.1. Hardware Requirements

Minimum DOCSIS3.1 bonding capability must be in the downstream: 2 OFDM channel and 32 QAM channels, in the upstream 2 OFDMA channels and 8 Upstream Channels.

6.2. Firmware Updates

Unitymedia will not include CVC information in bootfile. Therefore, Unitymedia will not trigger Secure Software Download being referenced in [i.4] Chapter 8.2.3, [i.3] Chapter 12.1 and [i.5] Chapter 14. Updates for Docsis Cable Modem and / or eRouter MAY be installed via vendor-own solution, for ex-ample local GUI Upload / flash. Recommendation: It is recommended, that the general idea of validation of the trusted source for the software-image will still be in place for locally triggered software updates. This could be achieved by only providing manufacturer CVC certified software-images and adapt the process of validation described in [i.5] Chapter14 - to a local process.

6.3. Console Access

Requirement [3] Chapter 9.2 is mandatory.

UM TS 411 10 von 65 02.05.2018

6.4. CM Provisioning

Unitymedia will not include vendor specific TLVs in the CM Bootfiles. Settings included will be:

eRouter initialization Mode [8]; all possible values must be supported

US packet class + DS packet class with corresponding US Service Flows and DS Service Flows for separation of voice based traffic and best effort traffic

SNMP access communities

Please see section 7.3 QoS regarding dynamic service flows.

UM TS 411 11 von 65 02.05.2018

6.5. MTA Initialization

Unitymedia will not provide MTA-bootfiles and provisioning of any MTA as described in the Packetca-ble specification. Also MAX-CPE will always be value of 1 to allow one client to receive Public IP-address.

To indicate to the cable modem non-support of MTA, DHCP Server will always include DHCP Option 122 Sub-Option 1 with value “0.0.0.0” as described in Packetcable specification.

If the CM DHCP option code 122 suboption 1 contains a DHCP server of value of 0.0.0.0, then the MTA MUST not attempt to provision and MUST remain dormant.

7 Voice Services

7.1. RFCs to support

IAD/ Softclient must support the following RFCs. In order to avoid ambiguities, please refer to the oth-er sections showing more detailed information and live examples [4] and [5].

7.2. Supported SDP values

The following are the only supported values in UM Network. As mentioned above, please look at the traces for more guidance.

i) [2]

ii) A Packetisation period of 20ms

iii) Telephony Event 101

7.3. QoS

ICP DSCP Wert

ICP IP-Precedence Wert

46 5 Medienstrom (RTP)

26 3 Signalisierung (SIP)

The Docsis unit MUST NOT use “Unsolicited Grant Service” nor “Unsolicited Grant Service with Activ-ity Detection”. Unitymedia MAY choose to reject UGS Requests on CMTS side in the future. Unitymedia will provide static, well defined Service-Flows via the docsis bootfile, respecting the needs and recommendations for the different Unitymedia-supported services.

UM TS 411 12 von 65 02.05.2018

7.4. Methods and Call Features

Please note that all features mentioned below are not available in all Unitymedia networks.

i) Registration

a. Proxy Authentication is a requirement

b. Registration period MUST be a minimum of 1800 seconds, recommendation is 3600 sec

c. Example is shown in Appendix I

ii) Basic Call Example is shown in Appendix II

iii) Call waiting Example is shown in Appendix III

iv) Caller id (CLIP) Example is shown in Appendix IV

v) Caller id during Call waiting Example is shown in Appendix V

vi) Phone number suppression (CLIR) Example is shown in Appendix VI

vii) Call forward unconditional viii) Call forward busy ix) Call forward No Answer (CFNR) x) 3Way Conference

Example is shown in Appendix VII

xi) Call Hold Example is shown in Appendix VIII

7.5. Call Features not supported

i) Messages Waiting Indication

ii) Features not mentioned in the previous section

7.6. SIP Clients

SIP messages from clients will be accepted only on UDP port 5060

7.6.1. Packetcable

Packetcable for Voice services will not be supported.

7.6.2. IPv6

IPv6 must be supported on the voice clients

7.6.3. Credentials

Customer must be able to enter his credentials on the voice client; Username/Password/Registrar. Unitymedia will not provision those credentials.

UM TS 411 13 von 65 02.05.2018

7.7. Emergency Calls

CPE Emergency call features are not supported. Regarding the German Notruf TR, only the customer’s registered postal address in Unitymedia’s cus-tomer Care System, will be sent to the Emergency call centre.

7.8. Tones

The frequencies should abide to one of two standards: i) [i.2]

ii) [i.1]

8 IP Protocols

8.1. Specifics for DS Lite

8.2. Access to the IPv4 Internet

Access to the IPv4 Internet is being provided by means of DS-Lite [6], which is IPv4-in-IPv6 tunneling to carrier-grade IPv4-IPv4 NAT (the AFTR).The outside IPv4 address is shared between customers. The IP address of the AFTR is provided by DHCPv6 option 64 (OPTION_AFTR_NAME) [7].DS-Lite Fragmentation. Fragmentation and Reassembly MUST be supported. The MTU of the DOCSIS segment is 1500 Bytes and cannot be increased to accommodate with the additional IPv6 header for DS-Lite. Frag-mentation MUST happen after [RFC6333] encapsulation and reassembly MUST happen before de-capsulation. Measures SHOULD be taken to keep fragmentation to a minimum. One option for this is MSS clamping. The maximum TCP/IPv4 Segment Size for DS-Lite is 1420 Bytes.

8.3. Variable AFTR endpoint addresses

The AFTR can change during runtime of the B4. Therefore it is required to honor the DNS RRs TTL and changed information in DHCPv6 messages like Renew (see RFC6334 section 3).

9 Additional Security Recommendations (standard configuration parameters)

Reference to (i.6): please see the newest version. According to (i.6), there are exclusion criteria’s, and security relevant requirements which have to be met! For those, please consult the BSI homepage and look at the most recent “Testkonzept für Breit-bandrouter”. www.bsi.bund.de

http://www.bsi.bund.de/

UM TS 411 14 von 65 02.05.2018

Appendix I: Trace Example for Registration

REGISTER sip:ssl51-sbcv6.telefon.unitymedia.de SIP/2.0

Via: SIP/2.0/UDP [2a02:908:fff0:282:9dad:4800:eb95:a171]:5060;branch=z9hG4bK.YxxJmcxsT;rport

From: <sip:[email protected]>;tag=OUt02SslZ

To: sip:[email protected]

CSeq: 20 REGISTER

Call-ID: QGgyVGYp6s

Max-Forwards: 70

Supported: outbound

Accept: application/sdp

Accept: text/plain

Accept: application/vnd.gsma.rcs-ft-http+xml

Contact:

<sip:022734060893@[2a02:908:fff0:282:9dad:4800:eb95:a171]>;+sip.instance="<urn:uuid:5d82b57c-679f-479f-

b7dd-4b87cdfa9b58>"

Expires: 3600

User-Agent: Linphone/3.9.1 (belle-sip/1.4.2)

SIP/2.0 100 Trying

Via: SIP/2.0/UDP

[2a02:908:fff0:282:9dad:4800:eb95:a171]:5060;received=2a02:908:fff0:282:9dad:4800:eb95:a171;branch=z9hG

4bK.YxxJmcxsT;rport



CSeq: 20 REGISTER

Call-ID: QGgyVGYp6s

Content-Length: 0

SIP/2.0 407 Proxy Authentication Required

Via: SIP/2.0/UDP


4bK.YxxJmcxsT;rport


To: <sip:[email protected]>;tag=1216356682

CSeq: 20 REGISTER

Call-ID: QGgyVGYp6s

User-Agent: Nortel SESM 17.0.7.18

Supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join,x-nortel-sipvc,gin

Proxy-Authenticate: Digest

realm="Realm",nonce="MTQ2OTEwMzg5NDg3MmQxNzVkMTQ0YjdjZTM0ODY2NDc1NTFhNzI5ZThlMjhh",stale=false,algorith

m=MD5,qop="auth,auth-int"

Content-Length: 0

REGISTER sip:ssl51-sbcv6.telefon.unitymedia.de SIP/2.0

Via: SIP/2.0/UDP [2a02:908:fff0:282:9dad:4800:eb95:a171]:5060;branch=z9hG4bK.ezdpyZVX9;rport



CSeq: 21 REGISTER

Call-ID: QGgyVGYp6s

Max-Forwards: 70

Supported: outbound


Accept: text/plain


Contact:


b7dd-4b87cdfa9b58>"

Expires: 3600


Proxy-Authorization: Digest realm="Realm",

nonce="MTQ2OTEwMzg5NDg3MmQxNzVkMTQ0YjdjZTM0ODY2NDc1NTFhNzI5ZThlMjhh", algorithm=MD5,

username="022734060893", uri="sip:ssl51-sbcv6.telefon.unitymedia.de", response="270ca011d9ffc0278

SIP/2.0 100 Trying

Via: SIP/2.0/UDP


4bK.ezdpyZVX9;rport



UM TS 411 15 von 65 02.05.2018

CSeq: 21 REGISTER

Call-ID: QGgyVGYp6s

Content-Length: 0

SIP/2.0 200 Registration Successful

Via: SIP/2.0/UDP


4bK.ezdpyZVX9;rport



CSeq: 21 REGISTER

Call-ID: QGgyVGYp6s

Contact: <sip:022734060893@[2a02:908:fff0:282:9dad:4800:eb95:a171]>;expires=3514



Content-Length: 0

UM TS 411 16 von 65 02.05.2018

Appendix II: Trace Example for Basic outgoing call

Frame 27: 998 bytes on wire (7984 bits), 998 bytes captured (7984 bits) on interface 0

Ethernet II, Src: LiteonTe_e9:b7:f0 (30:10:b3:e9:b7:f0), Dst: AvmGmbh_67:0e:8b (bc:05:43:67:0e:8b)

Internet Protocol Version 6, Src: 2a02:908:399:1260:565:3999:4a8a:9502, Dst: 2a02:908:a:1000::4f

User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)

Session Initiation Protocol (INVITE)

Request-Line: INVITE sip:[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:399:1260:565:3999:4a8a:9502]:5060;branch=z9hG4bK.~pb65LJQZ;rport

From: <sip:[email protected]>;tag=hHy9pKnNU


CSeq: 20 INVITE

Call-ID: xvR2cGSumq

Max-Forwards: 70

Supported: outbound

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

Content-Type: application/sdp

Content-Length: 275

Contact:

<sip:93464269901@[2a02:908:399:1260:565:3999:4a8a:9502]>;+sip.instance="<urn:uuid:efd839ab-0e20-40f8-

9ca4-3f6de6f95248>"


Message Body

Session Description Protocol

Session Description Protocol Version (v): 0

Owner/Creator, Session Id (o): 93464269901 2550 1832 IN IP6

2a02:908:399:1260:565:3999:4a8a:9502

Session Name (s): Talk

Connection Information (c): IN IP6 2a02:908:399:1260:565:3999:4a8a:9502

Time Description, active time (t): 0 0

Session Attribute (a): rtcp-xr:rcvr-rtt=all:10000 stat-summary=loss,dup,jitt,TTL voip-

metrics

Media Description, name and address (m): audio 7078 RTP/AVP 0 8 101

Media Attribute (a): rtpmap:101 telephone-event/8000


Ethernet II, Src: AvmGmbh_67:0e:8b (bc:05:43:67:0e:8b), Dst: LiteonTe_e9:b7:f0 (30:10:b3:e9:b7:f0)

Internet Protocol Version 6, Src: 2a02:908:a:1000::4f, Dst: 2a02:908:399:1260:565:3999:4a8a:9502


Session Initiation Protocol (100)

Status-Line: SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP

[2a02:908:399:1260:565:3999:4a8a:9502]:5060;received=2a02:908:399:1260:565:3999:4a8a:9502;branch=z9hG4b

K.~pb65LJQZ;rport



CSeq: 20 INVITE

Call-ID: xvR2cGSumq






Status-Line: SIP/2.0 401 Unauthorized

Message Header

Via: SIP/2.0/UDP


K.~pb65LJQZ;rport


To: <sip:[email protected]>;tag=snl_0027122872

CSeq: 20 INVITE

Call-ID: xvR2cGSumq

WWW-Authenticate: Digest realm="srxadmin@localhost", nonce="4095637233-

8877b0c7a8a68eb83b060807d6c7bc1b", algorithm=MD5, qop="auth"

Content-Length: 0


UM TS 411 17 von 65 02.05.2018




Session Initiation Protocol (ACK)

Request-Line: ACK sip:[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:399:1260:565:3999:4a8a:9502]:5060;branch=z9hG4bK.~pb65LJQZ;rport

Call-ID: xvR2cGSumq



Contact:


9ca4-3f6de6f95248>"

Max-Forwards: 70

CSeq: 20 ACK







Message Header

Via: SIP/2.0/UDP [2a02:908:399:1260:565:3999:4a8a:9502]:5060;branch=z9hG4bK.ebpKWPYX-;rport



CSeq: 21 INVITE

Call-ID: xvR2cGSumq

Max-Forwards: 70

Supported: outbound



Content-Length: 275

Contact:


9ca4-3f6de6f95248>"


[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="4095637233-

8877b0c7a8a68eb83b060807d6c7bc1b", algorithm=MD5, username="93464269901", uri="sip:015112128603@hiq7a-

sbcv61a.kabelbw.de", response="ea9603ccfb6bcb4d05a37b44

Message Body




2a02:908:399:1260:565:3999:4a8a:9502


Connection Information (c): IN IP6 2a02:908:399:1260:565:3999:4a8a:9502



metrics









Message Header

Via: SIP/2.0/UDP


K.ebpKWPYX-;rport



CSeq: 21 INVITE

Call-ID: xvR2cGSumq




UM TS 411 18 von 65 02.05.2018



Status-Line: SIP/2.0 183 Session Progress

Message Header

Via: SIP/2.0/UDP


K.ebpKWPYX-;rport



CSeq: 21 INVITE

Call-ID: xvR2cGSumq

Contact: <sip:015112128603@[2a02:908:a:1000::4f]:5060;transport=udp>

Date: Mon, 25 Jul 2016 22:05:22 GMT


Content-Length: 221

Message Body



Owner/Creator, Session Id (o): PVG 1469484170960 1469484170960 IN IP6 2a02:908:a:1000::4f

Session Name (s): -

Phone Number (p): +1 6135555555

Connection Information (c): IN IP6 2a02:908:a:1000::4f




Media Attribute (a): fmtp:101 0-15

Media Attribute (a): ptime:20






Status-Line: SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


K.ebpKWPYX-;rport



CSeq: 21 INVITE

Call-ID: xvR2cGSumq


Accept-Language: en;q=0.0

Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER

Supported: timer

Session-Expires: 1800;refresher=uas

Date: Mon, 25 Jul 2016 22:05:26 GMT


Content-Length: 221

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555












Request-Line: ACK sip:015112128603@[2a02:908:a:1000::4f]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:399:1260:565:3999:4a8a:9502]:5060;rport;branch=z9hG4bK.jvPNIyaK1

UM TS 411 19 von 65 02.05.2018



CSeq: 21 ACK

Call-ID: xvR2cGSumq

Max-Forwards: 70


8877b0c7a8a68eb83b060807d6c7bc1b", algorithm=MD5, username="93464269901", uri="sip:015112128603@hiq7a-

sbcv61a.kabelbw.de", response="ea9603ccfb6bcb4d05a37b44





Session Initiation Protocol (BYE)

Request-Line: BYE sip:015112128603@[2a02:908:a:1000::4f]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:399:1260:565:3999:4a8a:9502]:5060;branch=z9hG4bK.f99JzJe8F;rport



CSeq: 22 BYE

Call-ID: xvR2cGSumq

Max-Forwards: 70



8877b0c7a8a68eb83b060807d6c7bc1b", algorithm=MD5, username="93464269901",

uri="sip:015112128603@[2a02:908:a:1000::4f]:5060;transport=udp", response="d74b8f78







Message Header

Via: SIP/2.0/UDP


K.f99JzJe8F;rport



CSeq: 22 BYE

Call-ID: xvR2cGSumq


Date: Mon, 25 Jul 2016 22:05:30 GMT

Content-Length: 0

UM TS 411 20 von 65 02.05.2018

Appendix III: Trace Example for call waiting INVITE sip:[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.PNLVr-2pB;rport

From: <sip:[email protected]>;tag=IjAnG6Nq-


CSeq: 20 INVITE

Call-ID: Pdl7nbwoBR

Max-Forwards: 70

Supported: outbound



Content-Length: 594

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:67bd92be-f1ec-40da-a985-

cbb5f1d81110>"


Message Body



Owner/Creator, Session Id (o): 93464269901 2450 2240 IN IP4 192.168.178.22


Connection Information (c): IN IP4 192.168.178.22



metrics

Media Description, name and address (m): audio 7078 RTP/AVP 96 97 98 99 0 8 101 100 102

Media Attribute (a): rtpmap:96 opus/48000/2

Media Attribute (a): fmtp:96 useinbandfec=1

Media Attribute (a): rtpmap:97 SILK/16000

Media Attribute (a): rtpmap:98 speex/16000

Media Attribute (a): fmtp:98 vbr=on






Media Description, name and address (m): video 9078 RTP/AVP 96 97

Media Attribute (a): rtpmap:96 VP8/90000

Media Attribute (a): rtpmap:97 H264/90000

Media Attribute (a): fmtp:97 profile-level-id=42801F

SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.PNLVr-

2pB;rport=5060



CSeq: 20 INVITE

Call-ID: Pdl7nbwoBR

SIP/2.0 401 Unauthorized

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.PNLVr-

2pB;rport=5060



CSeq: 20 INVITE

Call-ID: Pdl7nbwoBR


f5fd59483f4f37a62a411c6f7f4da5c5", algorithm=MD5, qop="auth"

Content-Length: 0

ACK sip:[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.PNLVr-2pB;rport

Call-ID: Pdl7nbwoBR



UM TS 411 21 von 65 02.05.2018


cbb5f1d81110>"

Max-Forwards: 70

CSeq: 20 ACK

INVITE sip:[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.BEl3TtA6Q;rport



CSeq: 21 INVITE

Call-ID: Pdl7nbwoBR

Max-Forwards: 70

Supported: outbound



Content-Length: 594


cbb5f1d81110>"



f5fd59483f4f37a62a411c6f7f4da5c5", algorithm=MD5, username="93464269901", uri="sip:015204466715@hiq7a-

sbcv41a.kabelbw.de", response="2fdcbd7459e793bfb993401d65

Message Body








metrics
















SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP

192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.BEl3TtA6Q;rport=5060



CSeq: 21 INVITE

Call-ID: Pdl7nbwoBR

SIP/2.0 183 Session Progress

Message Header

Via: SIP/2.0/UDP




CSeq: 21 INVITE

Call-ID: Pdl7nbwoBR

Contact: <sip:[email protected]:5060;transport=udp>

Date: Thu, 28 Jul 2016 08:49:22 GMT


Content-Length: 335

Message Body


UM TS 411 22 von 65 02.05.2018


Owner/Creator, Session Id (o): PVG 1469695310730 1469695310730 IN IP4 80.69.110.115

Session Name (s): -

Phone Number (p): +1 6135555555



Session Attribute (a): sqn: 0

Session Attribute (a): cdsc: 1 image udptl t38

Session Attribute (a): cpar: a=T38FaxVersion:0

Session Attribute (a): cpar: a=T38FaxUdpEC:t38UDPRedundancy





Media Description, name and address (m): video 0 RTP/AVP 96

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP




CSeq: 21 INVITE

Call-ID: Pdl7nbwoBR




Supported: timer


Date: Thu, 28 Jul 2016 08:49:24 GMT


Content-Length: 335

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555












ACK sip:[email protected]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;rport;branch=z9hG4bK.plx6NCs0k



CSeq: 21 ACK

Call-ID: Pdl7nbwoBR

Max-Forwards: 70


f5fd59483f4f37a62a411c6f7f4da5c5", algorithm=MD5, username="93464269901", uri="sip:015204466715@hiq7a-

sbcv41a.kabelbw.de", response="2fdcbd7459e793bfb993401d65

REGISTER sip:hiq7a-sbcv41a.kabelbw.de SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.K29t8fnCM;rport

From: <sip:[email protected]>;tag=f9B~wG-x4


CSeq: 35 REGISTER

Call-ID: JIKY0xFIar

Max-Forwards: 70

Supported: outbound

UM TS 411 23 von 65 02.05.2018


Accept: text/plain



cbb5f1d81110>"

Expires: 3600



f71661c9ee7162b03f1c3f84d9095968", algorithm=MD5, username="93464269901", uri="sip:hiq7a-

sbcv41a.kabelbw.de", response="507168062704321918f5781ebed66794", cnon

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP

192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.K29t8fnCM;rport=5060

From: <sip:[email protected]>;tag=f9B~wG-x4

To: <sip:[email protected]>;tag=aprq4ckic43-v3ri8h0000062

CSeq: 35 REGISTER

Call-ID: JIKY0xFIar

Contact: <sip:[email protected]>;expires=30


Message Header

Via: SIP/2.0/UDP 80.69.110.115:5060;branch=z9hG4bKem9a79007oqhln4gm2c1.1

To: <sip:[email protected]>

From: <sip:[email protected];user=phone>;tag=snl_0172310964_NSN_CLIENT

Call-ID: NSNSIP-ecbfa8c0-efbfa8c0-2-21-1469695773-167194-1469862967

CSeq: 1235 INVITE


Supported: 100rel

Supported: timer


Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO, PRACK

P-Service-Indication: CW

Session-Expires: 1800;refresher=uac

Min-SE: 1800

Date: Thu, 28 Jul 2016 08:49:33 GMT

Max-Forwards: 27


Content-Length: 151

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555



Media Description, name and address (m): audio 40418 RTP/AVP 8


SIP/2.0 100 Trying

Message Header





CSeq: 1235 INVITE

SIP/2.0 180 Ringing

Message Header



To: <sip:[email protected]>;tag=pnhx0~-


CSeq: 1235 INVITE


Supported: outbound

CANCEL sip:[email protected] SIP/2.0

Message Header

UM TS 411 24 von 65 02.05.2018


CSeq: 1235 CANCEL




Max-Forwards: 27

Content-Length: 0

Reason: Q.850;cause=31

SIP/2.0 200 Ok

Message Header



To: <sip:[email protected]>;tag=8iFWJ2T


CSeq: 1235 CANCEL


Supported: outbound

SIP/2.0 487 Request terminated

Message Header





CSeq: 1235 INVITE


Supported: outbound


Message Header


CSeq: 1235 ACK




Max-Forwards: 27

Content-Length: 0

BYE sip:[email protected]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.pkwnfZRUR;rport



CSeq: 22 BYE

Call-ID: Pdl7nbwoBR

Max-Forwards: 70



f5fd59483f4f37a62a411c6f7f4da5c5", algorithm=MD5, username="93464269901",

uri="sip:[email protected]:5060;transport=udp", response="9f857ba3758a18d289

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP

192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.pkwnfZRUR;rport=5060



CSeq: 22 BYE

Call-ID: Pdl7nbwoBR


Date: Thu, 28 Jul 2016 08:49:52 GMT

Content-Length: 0

UM TS 411 25 von 65 02.05.2018

Appendix IV: Trace Example for caller id (CLIP)


Via: SIP/2.0/UDP [2a02:908:fff0:282:9dad:4800:eb95:a171]:5060;branch=z9hG4bK.tBBCyryce;rport

From: <sip:[email protected]>;tag=-cSk4-zzA


CSeq: 20 INVITE

Call-ID: 8~PL5BagW-

Max-Forwards: 70

Supported: outbound



Content-Length: 640

Contact:


b7dd-4b87cdfa9b58>"


Message Body




2a02:908:fff0:282:9dad:4800:eb95:a171


Connection Information (c): IN IP6 2a02:908:fff0:282:9dad:4800:eb95:a171



metrics
















SIP/2.0 100 Trying

Via: SIP/2.0/UDP


4bK.tBBCyryce;rport



CSeq: 20 INVITE

Call-ID: 8~PL5BagW-

SIP/2.0 407 Proxy Authentication Required

Via: SIP/2.0/UDP


4bK.tBBCyryce;rport



CSeq: 20 INVITE

Call-ID: 8~PL5BagW-



Proxy-Authenticate: Digest

realm="Realm",nonce="MTQ2OTEwMzg5NDg3MmQxNzVkMTQ0YjdjZTM0ODY2NDc1NTFhNzI5ZThlMjhh",stale=false,algorith

m=MD5,qop="auth"

Content-Length: 0


Via: SIP/2.0/UDP [2a02:908:fff0:282:9dad:4800:eb95:a171]:5060;branch=z9hG4bK.tBBCyryce;rport

Call-ID: 8~PL5BagW-

UM TS 411 26 von 65 02.05.2018



Contact:


b7dd-4b87cdfa9b58>"

Max-Forwards: 70

CSeq: 20 ACK


Via: SIP/2.0/UDP [2a02:908:fff0:282:9dad:4800:eb95:a171]:5060;branch=z9hG4bK.f286Z04kq;rport



CSeq: 21 INVITE

Call-ID: 8~PL5BagW-

Max-Forwards: 70

Supported: outbound



Content-Length: 640

Contact:


b7dd-4b87cdfa9b58>"




username="022734060893", uri="sip:[email protected]", response="6cac

Message Body




2a02:908:fff0:282:9dad:4800:eb95:a171


Connection Information (c): IN IP6 2a02:908:fff0:282:9dad:4800:eb95:a171



metrics
















SIP/2.0 100 Trying

Via: SIP/2.0/UDP


4bK.f286Z04kq;rport



CSeq: 21 INVITE

Call-ID: 8~PL5BagW-

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP


4bK.f286Z04kq;rport



CSeq: 21 INVITE

Call-ID: 8~PL5BagW-

Contact: <sip:022734064551@[2a02:908:a:1000::31]:5060;transport=udp>


UM TS 411 27 von 65 02.05.2018


Content-Length: 0

SIP/2.0 183 Session Description

Via: SIP/2.0/UDP


4bK.f286Z04kq;rport



CSeq: 21 INVITE

Call-ID: 8~PL5BagW-





Content-Length: 493

Message Body



Owner/Creator, Session Id (o): unknown 3678092717 3678092717 IN IP6 2a02:908:a:1000::2a

Session Name (s): Default

E-mail Address (e): [email protected]

Connection Information (c): IN IP6 2a02:908:a:1000::2a




Media Attribute (a): mptime:20

Media Attribute (a): X-pc-csuites-rtp:60/50

Media Attribute (a): X-pc-csuites-rtcp:80/70

Media Attribute (a): sqn: 0

Media Attribute (a): cdsc: 1 audio RTP/AVP 0 8 15 96 18

Media Attribute (a): cpar: a=rtpmap:96 G729E/8000

Media Attribute (a): cdsc: 6 image udptl t38

Media Attribute (a): cpar: a=T38FaxVersion:0

Media Attribute (a): cpar: a=T38FaxRateManagement:transferredTCF

Media Attribute (a): cpar: a=T38FaxMaxDatagram:160

Media Attribute (a): cpar: a=T38FaxUdpEC:t38UDPRedundancy

SIP/2.0 200 OK

Via: SIP/2.0/UDP


4bK.f286Z04kq;rport



CSeq: 21 INVITE

Call-ID: 8~PL5BagW-




Supported: replaces

Allow: UPDATE,REFER

x-nt-location: -1

Content-Length: 493

Message Body



Owner/Creator, Session Id (o): unknown 3678092717 3678092717 IN IP6 2a02:908:a:1000::2a

Session Name (s): Default

E-mail Address (e): [email protected]

Connection Information (c): IN IP6 2a02:908:a:1000::2a




Media Attribute (a): mptime:20

Media Attribute (a): X-pc-csuites-rtp:60/50

Media Attribute (a): X-pc-csuites-rtcp:80/70

Media Attribute (a): sqn: 0

Media Attribute (a): cdsc: 1 audio RTP/AVP 0 8 15 96 18

Media Attribute (a): cpar: a=rtpmap:96 G729E/8000

Media Attribute (a): cdsc: 6 image udptl t38

UM TS 411 28 von 65 02.05.2018

Media Attribute (a): cpar: a=T38FaxVersion:0

Media Attribute (a): cpar: a=T38FaxRateManagement:transferredTCF

Media Attribute (a): cpar: a=T38FaxMaxDatagram:160

Media Attribute (a): cpar: a=T38FaxUdpEC:t38UDPRedundancy

ACK sip:022734064551@[2a02:908:a:1000::31]:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP [2a02:908:fff0:282:9dad:4800:eb95:a171]:5060;rport;branch=z9hG4bK.j8SaRoQV2



CSeq: 21 ACK

Call-ID: 8~PL5BagW-

Max-Forwards: 70



username="022734060893", uri="sip:[email protected]", response="6cac

BYE sip:022734060893@[2a02:908:fff0:282:9dad:4800:eb95:a171] SIP/2.0

Via: SIP/2.0/UDP [2a02:908:a:1000::31]:5060;branch=z9hG4bK74vq9t306oah0hkas301sd00000b0.1

From: <sip:[email protected]>;tag=63437

To: <sip:[email protected]>;tag=-cSk4-zzA

Call-ID: 8~PL5BagW-

CSeq: 22 BYE


Max-Forwards: 19


Content-Length: 0

SIP/2.0 200 Ok

Via: SIP/2.0/UDP [2a02:908:a:1000::31]:5060;branch=z9hG4bK74vq9t306oah0hkas301sd00000b0.1

From: <sip:[email protected]>;tag=63437

To: <sip:[email protected]>;tag=-cSk4-zzA

Call-ID: 8~PL5BagW-

CSeq: 22 BYE


Supported: outbound

UM TS 411 29 von 65 02.05.2018

Appendix V: Trace Example for caller id during call waiting

1 19:05:40.430102 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP/SDP 1287 Request: IN-

VITE sip:[email protected] |


Ethernet II, Src: Inventec_86:d2:7d (00:8c:fa:86:d2:7d), Dst: Cadant_23:fb:02 (00:01:5c:23:fb:02)

Internet Protocol Version 4, Src: 46.5.8.18, Dst: 192.88.99.1

Internet Protocol Version 6, Src: 2002:2e05:812::2e05:812, Dst: 2a02:908:a:1000::32


Source Port: 5060

Destination Port: 5060

Length: 1213

Checksum: 0x77a0 [validation disabled]

[Stream index: 0]



Message Header

Message Body



Owner/Creator, Session Id (o): 022734060893 658 3453 IN IP6 2002:2e05:812::2e05:812


Connection Information (c): IN IP6 2002:2e05:812::2e05:812



metrics














2 19:05:40.454542 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP 379 Status: 100

Trying |


Ethernet II, Src: Cadant_23:fb:02 (00:01:5c:23:fb:02), Dst: Inventec_86:d2:7d (00:8c:fa:86:d2:7d)


Internet Protocol Version 6, Src: 2a02:908:a:1000::32, Dst: 2002:2e05:812::2e05:812


Source Port: 5060


Length: 305

Checksum: 0x3bce [validation disabled]

[Stream index: 0]



Message Header

3 19:05:40.468380 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP 709 Status: 407

Proxy Authentication Required |






Source Port: 5060


Length: 635

Checksum: 0x2561 [validation disabled]

UM TS 411 30 von 65 02.05.2018

[Stream index: 0]


Status-Line: SIP/2.0 407 Proxy Authentication Required

Message Header

4 19:05:40.498568 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP 538 Request: ACK

sip:[email protected] |






Source Port: 5060


Length: 464

Checksum: 0xba32 [validation disabled]

[Stream index: 0]


Request-Line: ACK sip:[email protected] SIP/2.0

Message Header


VITE sip:[email protected] |






Source Port: 5060


Length: 1510

Checksum: 0x434d [validation disabled]

[Stream index: 0]



Message Header

Message Body








metrics














7 19:05:40.607748 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP 379 Status: 100

Trying |






Source Port: 5060


UM TS 411 31 von 65 02.05.2018

Length: 305

Checksum: 0xf5ca [validation disabled]

[Stream index: 0]



Message Header

8 19:05:41.481018 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP/SDP 884 Status: 183

Session Description |






Source Port: 5060


Length: 810

Checksum: 0xc3c2 [validation disabled]

[Stream index: 0]


Status-Line: SIP/2.0 183 Session Description

Message Header

Message Body



Owner/Creator, Session Id (o): PVG 701832518 701832518 IN IP6 2a02:908:a:1000::32

Session Name (s): -

Phone Number (p): +1 6135555555

Connection Information (c): IN IP6 2a02:908:a:1000::32







9 19:06:10.555186 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP/SDP 840 Status: 200 OK

|






Source Port: 5060


Length: 766

Checksum: 0x7db6 [validation disabled]

[Stream index: 0]



Message Header

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555









sip:093464269901@[2a02:908:a:1000::32]:5060;transport=udp |


UM TS 411 32 von 65 02.05.2018





Source Port: 5060


Length: 647

Checksum: 0x2ef4 [validation disabled]

[Stream index: 0]


Request-Line: ACK sip:093464269901@[2a02:908:a:1000::32]:5060;transport=udp SIP/2.0

Message Header


|






Source Port: 5060


Length: 766

Checksum: 0x7db6 [validation disabled]

[Stream index: 0]



Message Header

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555















Source Port: 5060


Length: 647

Checksum: 0xf72b [validation disabled]

[Stream index: 0]



Message Header

13 19:06:16.632981 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP/SDP 1193 Request: IN-

VITE sip:022734060893@[2002:2e05:812::2e05:812] |






Source Port: 5060


Length: 1119

UM TS 411 33 von 65 02.05.2018


[Stream index: 0]


Request-Line: INVITE sip:022734060893@[2002:2e05:812::2e05:812] SIP/2.0

Message Header

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555





14 19:06:16.649162 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP 398 Status: 100

Trying |






Source Port: 5060


Length: 324

Checksum: 0x9a43 [validation disabled]

[Stream index: 0]



Message Header

15 19:06:16.670608 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP 478 Status: 180

Ringing |






Source Port: 5060


Length: 404

Checksum: 0xaaf1 [validation disabled]

[Stream index: 0]


Status-Line: SIP/2.0 180 Ringing

Message Header


VITE sip:093464269901@[2a02:908:a:1000::32]:5060;transport=udp, in-dialog |






Source Port: 5060


Length: 1541

Checksum: 0xc06f [validation disabled]

[Stream index: 0]


Request-Line: INVITE sip:093464269901@[2a02:908:a:1000::32]:5060;transport=udp SIP/2.0

Message Header

Message Body





UM TS 411 34 von 65 02.05.2018




metrics












Media Attribute (a): sendonly


Media Attribute (a): inactive

18 19:06:23.640727 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP/SDP 870 Status: 200 Ok

|






Source Port: 5060


Length: 796

Checksum: 0x36ba [validation disabled]

[Stream index: 0]


Status-Line: SIP/2.0 200 Ok

Message Header

Message Body















Source Port: 5060


Length: 1541


[Stream index: 0]



Message Header

Message Body








metrics



UM TS 411 35 von 65 02.05.2018













21 19:06:24.148510 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP/SDP 870 Status: 200 Ok

|






Source Port: 5060


Length: 796

Checksum: 0x36ba [validation disabled]

[Stream index: 0]



Message Header

Message Body








22 19:06:24.214850 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP 596 Request: ACK

sip:022734060893@[2002:2e05:812::2e05:812] |






Source Port: 5060


Length: 522

Checksum: 0xfa83 [validation disabled]

[Stream index: 0]


Request-Line: ACK sip:022734060893@[2002:2e05:812::2e05:812] SIP/2.0

Message Header








Source Port: 5060


Length: 1541


[Stream index: 0]



Message Header

UM TS 411 36 von 65 02.05.2018

Message Body








metrics
















|






Source Port: 5060


Length: 823

Checksum: 0x43bc [validation disabled]

[Stream index: 0]



Message Header

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555







Media Attribute (a): recvonly









Source Port: 5060


Length: 657

Checksum: 0xc407 [validation disabled]

[Stream index: 0]



Message Header

UM TS 411 37 von 65 02.05.2018

27 19:06:30.207561 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP 612 Request: BYE

sip:022734060893@[2002:2e05:812::2e05:812] |






Source Port: 5060


Length: 538


[Stream index: 0]


Request-Line: BYE sip:022734060893@[2002:2e05:812::2e05:812] SIP/2.0

Message Header

28 19:06:30.226600 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP 479 Status: 200 Ok

|






Source Port: 5060


Length: 405

Checksum: 0x072a [validation disabled]

[Stream index: 0]



Message Header

29 19:06:34.847391 2002:2e05:812::2e05:812 2a02:908:a:1000::32 SIP 777 Request: BYE







Source Port: 5060


Length: 703

Checksum: 0x810c [validation disabled]

[Stream index: 0]


Request-Line: BYE sip:093464269901@[2a02:908:a:1000::32]:5060;transport=udp SIP/2.0

Message Header

30 19:06:34.885479 2a02:908:a:1000::32 2002:2e05:812::2e05:812 SIP 403 Status: 200 OK

|






Source Port: 5060


Length: 329


[Stream index: 0]



Message Header

UM TS 411 38 von 65 02.05.2018

Appendix VI: Trace Example for Phone number suppression (CLIR)

INVITE sip:*[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.ARcdm-JPc;rport

From: <sip:[email protected]>;tag=IkW2PZwRg

To: sip:*[email protected]

CSeq: 20 INVITE

Call-ID: sstavkgSAL

Max-Forwards: 70

Supported: outbound



Content-Length: 593


cbb5f1d81110>"


Message Body








metrics
















SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.ARcdm-

JPc;rport=5060



CSeq: 20 INVITE

Call-ID: sstavkgSAL


Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.ARcdm-

JPc;rport=5060


To: <sip:*[email protected]>;tag=snl_0031867329

CSeq: 20 INVITE

Call-ID: sstavkgSAL


4f3f2e3d4e59ba003eb7424982adb2bb", stale=true, algorithm=MD5, qop="auth"

Content-Length: 0

ACK sip:*[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.ARcdm-JPc;rport

Call-ID: sstavkgSAL


UM TS 411 39 von 65 02.05.2018



cbb5f1d81110>"

Max-Forwards: 70

CSeq: 20 ACK

INVITE sip:*[email protected] SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.zN1yb2WVs;rport



CSeq: 21 INVITE

Call-ID: sstavkgSAL

Max-Forwards: 70

Supported: outbound



Content-Length: 593


cbb5f1d81110>"



4f3f2e3d4e59ba003eb7424982adb2bb", algorithm=MD5, username="93464269901",

uri="sip:*[email protected]", response="8b1e0bdddeeb2ba34fb95d8

Message Body








metrics
















SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP

192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.zN1yb2WVs;rport=5060



CSeq: 21 INVITE

Call-ID: sstavkgSAL


Message Header

Via: SIP/2.0/UDP




CSeq: 21 INVITE

Call-ID: sstavkgSAL

Contact: <sip:*[email protected]:5060;transport=udp>

Date: Thu, 28 Jul 2016 11:46:02 GMT


Content-Length: 335

Message Body

UM TS 411 40 von 65 02.05.2018




Session Name (s): -

Phone Number (p): +1 6135555555












SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP




CSeq: 21 INVITE

Call-ID: sstavkgSAL




Supported: timer


Date: Thu, 28 Jul 2016 11:46:07 GMT


Content-Length: 335

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555












ACK sip:*[email protected]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;rport;branch=z9hG4bK.-Ah4paQ-P



CSeq: 21 ACK

Call-ID: sstavkgSAL

Max-Forwards: 70



uri="sip:*[email protected]", response="8b1e0bdddeeb2ba34fb95d8


Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.xto5sk-gK;rport

From: <sip:[email protected]>;tag=ULk64kWIb


CSeq: 35 REGISTER

Call-ID: YkQwXLv2pA

Max-Forwards: 70

UM TS 411 41 von 65 02.05.2018

Supported: outbound


Accept: text/plain



cbb5f1d81110>"

Expires: 3600



89e00fb5f640b95a64df29b27a7d398d", algorithm=MD5, username="93464269901", uri="sip:hiq7a-

sbcv41a.kabelbw.de", response="feaa1bce03302a2037c75542e6e0db87", cnon

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.xto5sk-

gK;rport=5060

From: <sip:[email protected]>;tag=ULk64kWIb

To: <sip:[email protected]>;tag=aprq4ckic43-0ra2qf2000062

CSeq: 35 REGISTER

Call-ID: YkQwXLv2pA

Contact: <sip:[email protected]>;expires=30

BYE sip:*[email protected]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP 192.168.178.22:5060;branch=z9hG4bK.LKtVI2ju3;rport



CSeq: 22 BYE

Call-ID: sstavkgSAL

Max-Forwards: 70




uri="sip:*[email protected]:5060;transport=udp", response="733e374b00a1e54

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP

192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.LKtVI2ju3;rport=5060



CSeq: 22 BYE

Call-ID: sstavkgSAL


Date: Thu, 28 Jul 2016 11:46:17 GMT

Content-Length: 0

UM TS 411 42 von 65 02.05.2018

Appendix VII: Trace Example for 3 way conference


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.NSxF828gy;rport

From: <sip:[email protected]>;tag=SKlOqo2CX


CSeq: 20 REGISTER

Call-ID: sciI9cBzH3

Max-Forwards: 70

Supported: outbound


Accept: text/plain


Contact:

<sip:93464269901@[2a02:908:fff0:282:c158:8513:fa43:50f8]>;+sip.instance="<urn:uuid:5d82b57c-679f-479f-

b7dd-4b87cdfa9b58>"

Expires: 3600


SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP

[2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;received=2a02:908:fff0:282:c158:8513:fa43:50f8;branch=z9hG

4bK.NSxF828gy;rport

From: <sip:[email protected]>;tag=SKlOqo2CX

To: <sip:[email protected]>;tag=aprq4ckic43-bl8snq1000081

CSeq: 20 REGISTER

Call-ID: sciI9cBzH3

Contact: <sip:93464269901@[2a02:908:fff0:282:c158:8513:fa43:50f8]>;expires=3307


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.4W0O1JSHE;rport

From: <sip:[email protected]>;tag=SQhF6t7xL


CSeq: 20 INVITE

Call-ID: OySlHknjOX

Max-Forwards: 70

Supported: outbound



Content-Length: 640

Contact:


b7dd-4b87cdfa9b58>"


Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8


Connection Information (c): IN IP6 2a02:908:fff0:282:c158:8513:fa43:50f8



metrics














UM TS 411 43 von 65 02.05.2018



SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP


4bK.4W0O1JSHE;rport



CSeq: 20 INVITE

Call-ID: OySlHknjOX


Message Header

Via: SIP/2.0/UDP


4bK.4W0O1JSHE;rport



CSeq: 20 INVITE

Call-ID: OySlHknjOX


14f7487e6a154c9228af67769a00c978", algorithm=MD5, qop="auth"

Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.4W0O1JSHE;rport

Call-ID: OySlHknjOX



Contact:


b7dd-4b87cdfa9b58>"

Max-Forwards: 70

CSeq: 20 ACK


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.-ociZfHka;rport



CSeq: 21 INVITE

Call-ID: OySlHknjOX

Max-Forwards: 70

Supported: outbound



Content-Length: 640

Contact:


b7dd-4b87cdfa9b58>"



14f7487e6a154c9228af67769a00c978", algorithm=MD5, username="93464269901", uri="sip:022734064551@hiq7a-

sbcv61a.kabelbw.de", response="715aad9df9ab2b5e212a3943

Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics





UM TS 411 44 von 65 02.05.2018












SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP


4bK.-ociZfHka;rport



CSeq: 21 INVITE

Call-ID: OySlHknjOX


Message Header

Via: SIP/2.0/UDP


4bK.-ociZfHka;rport



CSeq: 21 INVITE

Call-ID: OySlHknjOX


Date: Wed, 27 Jul 2016 11:50:36 GMT


Content-Length: 243

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555








SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.-ociZfHka;rport



CSeq: 21 INVITE

Call-ID: OySlHknjOX




Supported: timer


Date: Wed, 27 Jul 2016 11:50:40 GMT


Content-Length: 243

Message Body




Session Name (s): -

UM TS 411 45 von 65 02.05.2018

Phone Number (p): +1 6135555555








ACK sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;rport;branch=z9hG4bK.dBVOOHO-m



CSeq: 21 ACK

Call-ID: OySlHknjOX

Max-Forwards: 70



sbcv61a.kabelbw.de", response="715aad9df9ab2b5e212a3943

INVITE sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.T1y7q~xDV;rport



CSeq: 22 INVITE

Call-ID: OySlHknjOX

Max-Forwards: 70

Subject: Call on hold



Content-Length: 575

Contact:


b7dd-4b87cdfa9b58>"



14f7487e6a154c9228af67769a00c978", algorithm=MD5, username="93464269901",

uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="2e0910bb

Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics
















Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.inBCV3zgZ;rport

From: <sip:[email protected]>;tag=zVmWOm4gf


CSeq: 20 INVITE

UM TS 411 46 von 65 02.05.2018

Call-ID: fjBPx8WCd9

Max-Forwards: 70

Supported: outbound



Content-Length: 640

Contact:


b7dd-4b87cdfa9b58>"


Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics
















SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP


4bK.inBCV3zgZ;rport



CSeq: 20 INVITE

Call-ID: fjBPx8WCd9


Message Header

Via: SIP/2.0/UDP


4bK.inBCV3zgZ;rport



CSeq: 20 INVITE

Call-ID: fjBPx8WCd9


14f7487e6a154c9228af67769a00c978", algorithm=MD5, qop="auth"

Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.inBCV3zgZ;rport

Call-ID: fjBPx8WCd9



Contact:


b7dd-4b87cdfa9b58>"

Max-Forwards: 70

CSeq: 20 ACK

UM TS 411 47 von 65 02.05.2018


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.u4~mfV~4e;rport



CSeq: 21 INVITE

Call-ID: fjBPx8WCd9

Max-Forwards: 70

Supported: outbound



Content-Length: 640

Contact:


b7dd-4b87cdfa9b58>"




sbcv61a.kabelbw.de", response="26db3638549addd498721695

Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics
















SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.T1y7q~xDV;rport



CSeq: 22 INVITE

Call-ID: OySlHknjOX




Supported: timer


Date: Wed, 27 Jul 2016 11:50:58 GMT


Content-Length: 254

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555



UM TS 411 48 von 65 02.05.2018







SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP


4bK.u4~mfV~4e;rport



CSeq: 21 INVITE

Call-ID: fjBPx8WCd9


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;rport;branch=z9hG4bK.3I0mqnRZg



CSeq: 22 ACK

Call-ID: OySlHknjOX

Max-Forwards: 70



uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="2e0910bb


Message Header

Via: SIP/2.0/UDP


4bK.u4~mfV~4e;rport



CSeq: 21 INVITE

Call-ID: fjBPx8WCd9


Date: Wed, 27 Jul 2016 11:50:59 GMT


Content-Length: 243

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555








SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.u4~mfV~4e;rport



CSeq: 21 INVITE

Call-ID: fjBPx8WCd9




Supported: timer


Date: Wed, 27 Jul 2016 11:51:03 GMT

UM TS 411 49 von 65 02.05.2018


Content-Length: 243

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555









Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;rport;branch=z9hG4bK.mWnkC51Br



CSeq: 21 ACK

Call-ID: fjBPx8WCd9

Max-Forwards: 70



sbcv61a.kabelbw.de", response="26db3638549addd498721695


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.UBWNf2569;rport



CSeq: 22 INVITE

Call-ID: fjBPx8WCd9

Max-Forwards: 70




Content-Length: 575

Contact:


b7dd-4b87cdfa9b58>"




uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="ce178794

Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics















UM TS 411 50 von 65 02.05.2018


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.ofySxdwiE;rport



CSeq: 23 INVITE

Call-ID: OySlHknjOX

Max-Forwards: 70

Subject: Call resuming



Content-Length: 563

Contact:


b7dd-4b87cdfa9b58>"




uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="3bee6222

Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics














SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.UBWNf2569;rport



CSeq: 22 INVITE

Call-ID: fjBPx8WCd9




Supported: timer


Date: Wed, 27 Jul 2016 11:51:20 GMT


Content-Length: 254

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555





UM TS 411 51 von 65 02.05.2018





SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.ofySxdwiE;rport



CSeq: 23 INVITE

Call-ID: OySlHknjOX




Supported: timer


Date: Wed, 27 Jul 2016 11:51:20 GMT


Content-Length: 242

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555









Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;rport;branch=z9hG4bK.JpZN-qBTA



CSeq: 22 ACK

Call-ID: fjBPx8WCd9

Max-Forwards: 70



uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="ce178794


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;rport;branch=z9hG4bK.oJPlqfss8



CSeq: 23 ACK

Call-ID: OySlHknjOX

Max-Forwards: 70



uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="3bee6222


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.HLaLbGt~a;rport



CSeq: 24 INVITE

Call-ID: OySlHknjOX

Max-Forwards: 70

Subject: Conference



UM TS 411 52 von 65 02.05.2018

Content-Length: 563

Contact:

<sip:93464269901@[2a02:908:fff0:282:c158:8513:fa43:50f8]>;expires=3307;+sip.instance="<urn:uuid:5d82b57

c-679f-479f-b7dd-4b87cdfa9b58>"




uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="cb634df3

Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics















Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.X9Iyhoj3D;rport



CSeq: 23 INVITE

Call-ID: fjBPx8WCd9

Max-Forwards: 70

Subject: Conference



Content-Length: 563

Contact:


b7dd-4b87cdfa9b58>"




uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="bf8e7061

Message Body




2a02:908:fff0:282:c158:8513:fa43:50f8





metrics











UM TS 411 53 von 65 02.05.2018




SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.HLaLbGt~a;rport



CSeq: 24 INVITE

Call-ID: OySlHknjOX




Supported: timer


Date: Wed, 27 Jul 2016 11:51:31 GMT


Content-Length: 242

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555









Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;rport;branch=z9hG4bK.~otA61l1o



CSeq: 24 ACK

Call-ID: OySlHknjOX

Max-Forwards: 70



uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="cb634df3

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.X9Iyhoj3D;rport



CSeq: 23 INVITE

Call-ID: fjBPx8WCd9




Supported: timer


Date: Wed, 27 Jul 2016 11:51:31 GMT


Content-Length: 242

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555


UM TS 411 54 von 65 02.05.2018








Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;rport;branch=z9hG4bK.Xywo2f2qc



CSeq: 23 ACK

Call-ID: fjBPx8WCd9

Max-Forwards: 70



uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="bf8e7061

BYE sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.vOtKu8CU3;rport



CSeq: 25 BYE

Call-ID: OySlHknjOX

Max-Forwards: 70




uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="313b1210

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.vOtKu8CU3;rport



CSeq: 25 BYE

Call-ID: OySlHknjOX


Date: Wed, 27 Jul 2016 11:51:50 GMT

Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:c158:8513:fa43:50f8]:5060;branch=z9hG4bK.DtlL~w4na;rport



CSeq: 24 BYE

Call-ID: fjBPx8WCd9

Max-Forwards: 70




uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="7fc147d4

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.DtlL~w4na;rport



CSeq: 24 BYE

Call-ID: fjBPx8WCd9


Date: Wed, 27 Jul 2016 11:51:50 GMT

Content-Length: 0

UM TS 411 55 von 65 02.05.2018

Appendix VIII: Trace Example for call hold


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.yxTHSTSv5;rport

From: <sip:[email protected]>;tag=N0gMLxRDU


CSeq: 20 INVITE

Call-ID: np8Ek0zNdi

Max-Forwards: 70

Supported: outbound



Content-Length: 638

Contact:

<sip:93464269901@[2a02:908:fff0:282:d5c2:5640:f7d5:baef]>;+sip.instance="<urn:uuid:5d82b57c-679f-479f-

b7dd-4b87cdfa9b58>"


Message Body




2a02:908:fff0:282:d5c2:5640:f7d5:baef


Connection Information (c): IN IP6 2a02:908:fff0:282:d5c2:5640:f7d5:baef



metrics
















IP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP

[2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;received=2a02:908:fff0:282:d5c2:5640:f7d5:baef;branch=z9hG

4bK.yxTHSTSv5;rport



CSeq: 20 INVITE

Call-ID: np8Ek0zNdi


Message Header

Via: SIP/2.0/UDP


4bK.yxTHSTSv5;rport



CSeq: 20 INVITE

Call-ID: np8Ek0zNdi


a05573a300e13850c9b3e122f6415953", algorithm=MD5, qop="auth"

Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.yxTHSTSv5;rport

UM TS 411 56 von 65 02.05.2018

Call-ID: np8Ek0zNdi



Contact:


b7dd-4b87cdfa9b58>"

Max-Forwards: 70

CSeq: 20 ACK


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.Cn3bsDACO;rport



CSeq: 21 INVITE

Call-ID: np8Ek0zNdi

Max-Forwards: 70

Supported: outbound



Content-Length: 638

Contact:


b7dd-4b87cdfa9b58>"



a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="93464269901", uri="sip:022734064551@hiq7a-

sbcv61a.kabelbw.de", response="96d0f0c1084e1c07567f330f

Message Body




2a02:908:fff0:282:d5c2:5640:f7d5:baef





metrics
















SIP/2.0 100 Trying

Message Header

Via: SIP/2.0/UDP


4bK.Cn3bsDACO;rport



CSeq: 21 INVITE

Call-ID: np8Ek0zNdi


Message Header

Via: SIP/2.0/UDP


4bK.Cn3bsDACO;rport



UM TS 411 57 von 65 02.05.2018

CSeq: 21 INVITE

Call-ID: np8Ek0zNdi


Date: Wed, 27 Jul 2016 13:30:20 GMT


Content-Length: 347

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555












SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.Cn3bsDACO;rport



CSeq: 21 INVITE

Call-ID: np8Ek0zNdi




Supported: timer


Date: Wed, 27 Jul 2016 13:30:23 GMT


Content-Length: 347

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555













Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;rport;branch=z9hG4bK.eSvw3P3lv



CSeq: 21 ACK

Call-ID: np8Ek0zNdi

Max-Forwards: 70


a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="93464269901", uri="sip:022734064551@hiq7a-

sbcv61a.kabelbw.de", response="96d0f0c1084e1c07567f330f

UM TS 411 58 von 65 02.05.2018

INVITE sip:93464269901@[2a02:908:fff0:282:d5c2:5640:f7d5:baef] SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:a:1000::4f]:5060;branch=z9hG4bKjit0bj1080sg2h47t0a1.1




CSeq: 1235 INVITE


Supported: 100rel

Supported: timer


Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO, PRACK

P-Service-Indication: CW

Session-Expires: 1800;refresher=uac

Min-SE: 1800

Date: Wed, 27 Jul 2016 13:30:39 GMT

Max-Forwards: 27


Content-Length: 163

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555





SIP/2.0 100 Trying

Message Header





CSeq: 1235 INVITE

SIP/2.0 180 Ringing

Message Header



To: <sip:[email protected]>;tag=zs7lZ5j


CSeq: 1235 INVITE


Supported: outbound


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.nnH7OldpQ;rport



CSeq: 22 INVITE

Call-ID: np8Ek0zNdi

Max-Forwards: 70




Content-Length: 573

Contact:


b7dd-4b87cdfa9b58>"



a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="93464269901",

uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="a22bb4aa

Message Body



UM TS 411 59 von 65 02.05.2018


2a02:908:fff0:282:d5c2:5640:f7d5:baef





metrics















SIP/2.0 200 Ok

Message Header





CSeq: 1235 INVITE


Supported: outbound


Contact:


b7dd-4b87cdfa9b58>"


Content-Length: 161

Message Body




2a02:908:fff0:282:d5c2:5640:f7d5:baef





ACK sip:93464269901@[2a02:908:fff0:282:d5c2:5640:f7d5:baef] SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:a:1000::4f]:5060;branch=z9hG4bKnq4c7f30402h2hc2d3c0.1




CSeq: 1235 ACK



Date: Wed, 27 Jul 2016 13:30:51 GMT

Max-Forwards: 27

Content-Length: 0

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.nnH7OldpQ;rport



CSeq: 22 INVITE

Call-ID: np8Ek0zNdi



UM TS 411 60 von 65 02.05.2018


Supported: timer


Date: Wed, 27 Jul 2016 13:30:51 GMT


Content-Length: 358

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555














Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;rport;branch=z9hG4bK.lyQ-apqvg



CSeq: 22 ACK

Call-ID: np8Ek0zNdi

Max-Forwards: 70



uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="a22bb4aa


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.~lUFdNXg1;rport

From: <sip:[email protected]>;tag=zs7lZ5j

To: <sip:[email protected];user=phone>;tag=snl_0030172797_NSN_CLIENT

CSeq: 111 INVITE


Max-Forwards: 70




Content-Length: 541

Contact:


b7dd-4b87cdfa9b58>"


Message Body




2a02:908:fff0:282:d5c2:5640:f7d5:baef





metrics









UM TS 411 61 von 65 02.05.2018






Message Header

Via: SIP/2.0/UDP


4bK.~lUFdNXg1;rport



CSeq: 111 INVITE




Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.1hm0-eYXG;rport



CSeq: 23 INVITE

Call-ID: np8Ek0zNdi

Max-Forwards: 70

Subject: Call resuming



Content-Length: 561

Contact:


b7dd-4b87cdfa9b58>"




uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="4a3ffaa0

Message Body




2a02:908:fff0:282:d5c2:5640:f7d5:baef





metrics















Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.~lUFdNXg1;rport




Contact:


b7dd-4b87cdfa9b58>"

Max-Forwards: 70

UM TS 411 62 von 65 02.05.2018

CSeq: 111 ACK


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.JPV1Gi7D1;rport



CSeq: 112 INVITE


Max-Forwards: 70



Content-Length: 541

Contact:


b7dd-4b87cdfa9b58>"



a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="DD0793464269901",

uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="cbea

Message Body




2a02:908:fff0:282:d5c2:5640:f7d5:baef





metrics













SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.1hm0-eYXG;rport



CSeq: 23 INVITE

Call-ID: np8Ek0zNdi




Supported: timer


Date: Wed, 27 Jul 2016 13:31:03 GMT


Content-Length: 346

Message Body




Session Name (s): -

Phone Number (p): +1 6135555555






UM TS 411 63 von 65 02.05.2018








Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;rport;branch=z9hG4bK.L86M5WHwX



CSeq: 23 ACK

Call-ID: np8Ek0zNdi

Max-Forwards: 70



uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="4a3ffaa0


Message Header

Via: SIP/2.0/UDP


4bK.JPV1Gi7D1;rport



CSeq: 112 INVITE




Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.JPV1Gi7D1;rport




Contact:


b7dd-4b87cdfa9b58>"

Max-Forwards: 70

CSeq: 112 ACK


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.nkRQRURdX;rport



CSeq: 113 INVITE


Max-Forwards: 70



Content-Length: 541

Contact:


b7dd-4b87cdfa9b58>"



a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="DD0793464269901",

uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="0d9c

Message Body




2a02:908:fff0:282:d5c2:5640:f7d5:baef




UM TS 411 64 von 65 02.05.2018


metrics














Message Header

Via: SIP/2.0/UDP


4bK.nkRQRURdX;rport



CSeq: 113 INVITE




Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.nkRQRURdX;rport




Contact:


b7dd-4b87cdfa9b58>"

Max-Forwards: 70

CSeq: 113 ACK


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.y0X5-PCli;rport



CSeq: 24 BYE

Call-ID: np8Ek0zNdi

Max-Forwards: 70



Message Header

Via: SIP/2.0/UDP


4bK.y0X5-PCli;rport



CSeq: 24 BYE

Call-ID: np8Ek0zNdi



Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.WVtXZ6WEe;rport



CSeq: 25 BYE

Call-ID: np8Ek0zNdi

Max-Forwards: 70

UM TS 411 65 von 65 02.05.2018




uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="f7b5f743

SIP/2.0 200 OK

Message Header

Via: SIP/2.0/UDP


4bK.WVtXZ6WEe;rport



CSeq: 25 BYE

Call-ID: np8Ek0zNdi


Date: Wed, 27 Jul 2016 13:31:17 GMT

Content-Length: 0


Message Header

Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.zurMJdzqC;rport



CSeq: 114 BYE


Max-Forwards: 70



Message Header

Via: SIP/2.0/UDP


4bK.zurMJdzqC;rport



CSeq: 114 BYE




Content-Length: 0

BYE sip:93464269901@[2a02:908:fff0:282:d5c2:5640:f7d5:baef] SIP/2.0

Message Header

Via: SIP/2.0/UDP [2a02:908:a:1000::4f]:5060;branch=z9hG4bKnq4c7f30402h2hc2d3c0cd00080a3.1




CSeq: 1236 BYE



Date: Wed, 27 Jul 2016 13:31:38 GMT

Max-Forwards: 68

Content-Length: 0

SIP/2.0 481 Call/transaction does not exist

Message Header

Via: SIP/2.0/UDP [2a02:908:a:1000::4f]:5060;branch=z9hG4bKnq4c7f30402h2hc2d3c0cd00080a3.1




CSeq: 1236 BYE

provider spezifikation docsis 3 - unitymedia · um ts 411 2 von 65 02.05.2018 conventions...

Documents