Provider Specific Requirements for the passive NTP in

Transcription

passive NTP; Provider Specific Requirements
UM TS 411
Provider Specific Requirements for the passive Network
Termination Point in
DOCSIS 3.0 Environment;
Version 1.0
28.07.2016
UM TS 411
1 von 63
29.07.2016
Conventions
Throughout this document, the words that are used to define the significance of particular
requirements 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
specification.
"SHOULD"
This word means that there may exist valid reasons in particular
circumstances 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
circumstances when the listed behavior is acceptable or even useful, but the
full implications should be understood and the case carefully weighed before
implementing 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
2 von 63
29.07.2016
Contact
Unitymedia NRW GmbH
Aachener Strasse 746 – 750
50933 Köln
Unitymedia Hessen GmbH & Co. KG
50933 Köln
Unitymedia BW GmbH
50933 Köln
UM TS 411
3 von 63
29.07.2016
PROVIDERSPECIFICREQUIREMENTSFORTHEPASSIVENETWORKTERMINATIONPOINTINDOCSIS3.0ENVIRONMENT;
1
1
SCOPE
5
2
REFERENCES
5
2.1.
2.2.
3
5
6
NORMATIVEREFERENCES
INFORMATIVEREFERENCES
6
DEFINITIONSANDABBREVIATIONS
3.1.
3.2.
6
7
DEFINITIONS
ABBREVIATIONS
4
RFINTERFACECONNECTOR
8
5
NETWORKRFCHARACTERISTICS
8
6
CABLELABSSPECIFICATIONSCMCI/MULPI/OSSI/PHY/SEC
8
6.1.
6.2.
6.3.
6.4.
6.5.
7
8
8
8
8
9
HARDWAREREQUIREMENTS
FIRMWAREUPDATES
CONSOLEACCESS
CMPROVISIONING
MTAINITIALIZATION
9
VOICESERVICES
7 . 1 . RFCSTOSUPPORT
7 . 2 . SUPPORTEDSDPVALUES
7 . 3 . QOS
7 . 4 . METHODSANDCALLFEATURES
7 . 5 . CALLFEATURESNOTSUPPORTED
7 . 6 . SIPCLIENTS
7 . 6 . 1 . Packetcable
7 . 6 . 2 . IPv6
7 . 6 . 3 . Credentials
7 . 7 . EMERGENCYCALLS
7 . 8 . TONES
8
11
IPPROTOCOLS
8.1.
8.2.
8.3.
9
9
9
9
10
10
10
10
10
10
11
11
11
11
11
SPECIFICSFORDSLITE
ACCESSTOTHEIPV4
VARIABLEAFTRENDPOINTADDRESSES
11
ADDITIONALSECURITYRECOMMENDATIONS(STANDARDCONFIGURATIONPARAMETERS)
APPENDIXI:TRACEEXAMPLEFORREGISTRATION
12
APPENDIXII:TRACEEXAMPLEFORBASICOUTGOINGCALL
14
APPENDIXIII:TRACEEXAMPLEFORCALLWAITING
18
APPENDIXIV:TRACEEXAMPLEFORCALLERID(CLIP)
23
APPENDIXV:TRACEEXAMPLEFORCALLERIDDURINGCALLWAITING
27
APPENDIXVI:TRACEEXAMPLEFOR PHONENUMBERSUPPRESSION(CLIR)
36
APPENDIXVII:TRACEEXAMPLEFOR3WAYCONFERENCE
40
APPENDIXVIII:TRACEEXAMPLEFORCALLHOLD
53
UM TS 411
4 von 63
29.07.2016
1 Scope
This interface specification describes and specifies the additional Unitymedia Specific Requirements and Deviations of the
ANGA 100 001 main characteristics of the dedicated data RF interface in the OPERATOR cable network at the user’s
coaxial passive network termination point. The Unitymedia UM TS 411 and the ANGA 100 001 are related and apply
together. This interface specification describes the typical limits or values within which the RF characteristics can be
expected to remain 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
interface.
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
standards or non-compliance with the technical requirements for connection, established either by this interface
specification 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
OPERATOR 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]
ANGA 100 001 v1.0, Specification for the passive Network Termination Point in DOCSIS 3.0
Environment; Network and Provisioning requirements
[2]
ITU-T, G711A law: Pulse Code Modulation (PCM) of voice frequencies
[3]
CableLabs “Data Over Cable Service Interface Specifications, DOCSIS 3.0 Operations
Support 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
Lite
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack
[8]
TLV 202 – eRouter Operation Mode encoding
UM TS 411
5 von 63
29.07.2016
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.0 MAC and Upper
Layer Protocols Interface Specification CM-SP-MULPIv3.0-I29-151210”
[i.4]
CableLabs “Data Over Cable Service Interface Specifications, DOCSIS 3.0 Operations
Support System Interface Specification CM-SP-OSSIv3.0-I28-151210”
[i.5]
CableLabs “Data Over Cable Service Interface Specifications, DOCSIS 3.0 Security
Specification CM-SP-SECv3.0-I15-130808”
[i.6]
Bundesamt für Sicherheit in der Informationstechnik: “Testkonzept für Breitbandrouter”;
https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/CyberSicherheit/Themen/Testkonzept-Breitbandrouter.html
[i.7]
WISI Werknorm WN744-747; Wiclick Buchse
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
device IP address(es), when the CM boots. • The Configuration File server is used to
download configuration files to CMs when they boot. Configuration files are in binary format
and permit the configuration of the CM's parameters.
PacketCable
PacketCable is a technology specification defined by the industry consortium CableLabs for
using Internet Protocol (IP) networks to deliver multimedia services
UM TS 411
6 von 63
29.07.2016
3.2.
Abbreviations
AFTR
BSI
CFNR
CLIP
CLIR
CM
CMTS
CPE
CVC
DNS
DHCP
DS
DS-Lite
eRouter
FQDN
GUI
HTTPS
IPv6
ITU
MSS Clamping
MTA
PSTN
QoS
RF
RFC
SDP
SIP
SNMP
TLV
TR
TTL
UPnP
US
UGS
WAN
UM TS 411
Address Family Transition Router
Bundesamt für Sicherheit in der Informationstechnik
Call Forward No Reply
Calling Line Identification Presentation
Calling Line Identification Restriction
Cable Modem
Cable Modem Termination System
Customer Premise Equipment
Code Verification Certificate
Domain Name System
Dynamic Host Configuration Protocol
Downstream
Dual Stack Lite
embedded Router
Fully Qualified Domain Name
Graphical User Interface
Hyper Text Transfer Protocoll Secure
Internet Protocol Version 6
International Telecommunication Union
Maximum Segment Size Clamping
Multimedia Terminal Adapter
Public Switched Telephone Network
Quality of Service
Radio Frequency
Request For Comments
Session Description Protocol
Session Internet Protocol
Simple Network Management Protocoll
Type Length Value
Technische Richtlinie
Time To Live
Universal Plug&Play
Upstream
Unsolicited Grant Service
Wide Area Network
7 von 63
29.07.2016
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
According to [1], Chapter 5.
6 CableLabs specifications CMCI/MULPI/OSSI/PHY/SEC
6.1.
Hardware Requirements
Minimum Docsis 3.0 bonding capability must be 24 Downstream 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
example 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
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
8 von 63
29.07.2016
6.5.
MTA Initialization
Unitymedia will not provide MTA-bootfiles and provisioning of any MTA as described in the
Packetcable 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
other 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)
ii)
iii)
7.3.
[2]
A Packetisation period of 20ms
Telephony Event 101
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
Activity 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
9 von 63
29.07.2016
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
Basic Call
Example is shown in Appendix II
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)
viii)
ix)
x)
Call forward unconditional
Call forward busy
Call forward No Answer (CFNR)
3Way Conference
Example is shown in Appendix VII
xi)
Call Hold
Example is shown in Appendix VIII
7.5.
Call Features not supported
i)
ii)
7.6.
Messages Waiting Indication
Features not mentioned in the previous section
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
10 von 63
29.07.2016
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
customer Care System, will be sent to the Emergency call center.
7.8.
Tones
The frequencies should abide to one of two standards:
i)
ii)
[i.2]
[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.
Fragmentation MUST happen after [RFC6333] encapsulation and reassembly MUST happen before
decapsulation. Meassures 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
Breitbandrouter”.
www.bsi.bund.de
UM TS 411
11 von 63
29.07.2016
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-479fb7dd-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:
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
12 von 63
29.07.2016
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
13 von 63
29.07.2016
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-40f89ca4-3f6de6f95248>"
Message Body
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 voipmetrics
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="40956372338877b0c7a8a68eb83b060807d6c7bc1b", algorithm=MD5, qop="auth"
Content-Length: 0
UM TS 411
14 von 63
29.07.2016
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:
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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="40956372338877b0c7a8a68eb83b060807d6c7bc1b", algorithm=MD5, username="93464269901", uri="sip:[email protected]", 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
Message Header
Via: SIP/2.0/UDP
K.ebpKWPYX-;rport
CSeq: 21 INVITE
Call-ID: xvR2cGSumq
UM TS 411
15 von 63
29.07.2016
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
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
16 von 63
29.07.2016
CSeq: 21 ACK
Call-ID: xvR2cGSumq
Max-Forwards: 70
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="40956372338877b0c7a8a68eb83b060807d6c7bc1b", algorithm=MD5, username="93464269901", uri="sip:[email protected]", 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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="40956372338877b0c7a8a68eb83b060807d6c7bc1b", 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
17 von 63
29.07.2016
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=IjAnG6NqTo: sip:[email protected]
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-a985cbb5f1d81110>"
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
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.PNLVr2pB;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.PNLVr2pB;rport=5060
From: <sip:[email protected]>;tag=IjAnG6NqTo: <sip:[email protected]>;tag=snl_0031449157
CSeq: 20 INVITE
Call-ID: Pdl7nbwoBR
WWW-Authenticate: Digest realm="srxadmin@localhost", nonce="11879665f5fd59483f4f37a62a411c6f7f4da5c5", 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
18 von 63
29.07.2016
Max-Forwards: 70
CSeq: 20 ACK
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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="11879665f5fd59483f4f37a62a411c6f7f4da5c5", algorithm=MD5, username="93464269901", uri="sip:[email protected]", response="2fdcbd7459e793bfb993401d65
Message Body
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
19 von 63
29.07.2016
Owner/Creator, Session Id (o): PVG 1469695310730 1469695310730 IN IP4 80.69.110.115
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
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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="11879665f5fd59483f4f37a62a411c6f7f4da5c5", algorithm=MD5, username="93464269901", uri="sip:[email protected]", 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
20 von 63
29.07.2016
Accept: text/plain
Expires: 3600
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="12063116f71661c9ee7162b03f1c3f84d9095968", algorithm=MD5, username="93464269901", uri="sip:hiq7asbcv41a.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
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~Call-ID: NSNSIP-ecbfa8c0-efbfa8c0-2-21-1469695773-167194-1469862967
CSeq: 1235 INVITE
Supported: outbound
CANCEL sip:[email protected] SIP/2.0
Message Header
UM TS 411
21 von 63
29.07.2016
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
To: <sip:[email protected]>;tag=pnhx0~Call-ID: NSNSIP-ecbfa8c0-efbfa8c0-2-21-1469695773-167194-1469862967
CSeq: 1235 INVITE
Supported: outbound
Message Header
CSeq: 1235 ACK
To: <sip:[email protected]>;tag=pnhx0~From: <sip:[email protected];user=phone>;tag=snl_0172310964_NSN_CLIENT
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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="11879665f5fd59483f4f37a62a411c6f7f4da5c5", 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
22 von 63
29.07.2016
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~PL5BagWMax-Forwards: 70
Supported: outbound
Content-Length: 640
Contact:
Message Body
2a02:908:fff0:282:9dad:4800:eb95:a171
Connection Information (c): IN IP6 2a02:908:fff0:282:9dad:4800:eb95:a171
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
4bK.tBBCyryce;rport
CSeq: 20 INVITE
Call-ID: 8~PL5BagWSIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
4bK.tBBCyryce;rport
CSeq: 20 INVITE
Call-ID: 8~PL5BagWUser-Agent: Nortel SESM 17.0.7.18
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
23 von 63
29.07.2016
Contact:
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
Supported: outbound
Content-Length: 640
Contact:
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
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
4bK.f286Z04kq;rport
CSeq: 21 INVITE
Call-ID: 8~PL5BagWSIP/2.0 180 Ringing
Via: SIP/2.0/UDP
4bK.f286Z04kq;rport
CSeq: 21 INVITE
Call-ID: 8~PL5BagWContact: <sip:022734064551@[2a02:908:a:1000::31]:5060;transport=udp>
UM TS 411
24 von 63
29.07.2016
Content-Length: 0
SIP/2.0 183 Session Description
Via: SIP/2.0/UDP
4bK.f286Z04kq;rport
CSeq: 21 INVITE
Call-ID: 8~PL5BagWContent-Type: application/sdp
Contact: <sip:022734064551@[2a02:908:a:1000::31]:5060;transport=udp>
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~PL5BagWContent-Type: application/sdp
Contact: <sip:022734064551@[2a02:908:a:1000::31]:5060;transport=udp>
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
25 von 63
29.07.2016
Media
Media
Media
Media
Attribute
Attribute
Attribute
Attribute
(a):
(a):
(a):
(a):
cpar:
cpar:
cpar:
cpar:
a=T38FaxVersion:0
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxDatagram:160
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
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~PL5BagWCSeq: 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~PL5BagWCSeq: 22 BYE
Supported: outbound
UM TS 411
26 von 63
29.07.2016
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
INVITE sip:[email protected] |
SIP/SDP
1287
Request:
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
2 19:05:40.454542
Trying |
2a02:908:a:1000::32
2002:2e05:812::2e05:812 SIP
379
Status: 100
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
Proxy Authentication Required |
2002:2e05:812::2e05:812 SIP
709
Status: 407
Source Port: 5060
Length: 635
Checksum: 0x2561 [validation disabled]
UM TS 411
27 von 63
29.07.2016
[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:[email protected] |
SIP
538
Request: ACK
Source Port: 5060
Length: 464
Checksum: 0xba32 [validation disabled]
[Stream index: 0]
Request-Line: ACK sip:[email protected] SIP/2.0
Message Header
6 19:05:40.498782
2002:2e05:812::2e05:812 2a02:908:a:1000::32
INVITE sip:[email protected] |
SIP/SDP
360
Request:
Source Port: 5060
Length: 1510
Checksum: 0x434d [validation disabled]
[Stream index: 0]
Message Header
Message Body
7 19:05:40.607748
Trying |
2a02:908:a:1000::32
2002:2e05:812::2e05:812 SIP
379
Status: 100
Source Port: 5060
UM TS 411
28 von 63
29.07.2016
Length: 305
Checksum: 0xf5ca [validation disabled]
[Stream index: 0]
Message Header
8 19:05:41.481018
Session Description |
2a02:908:a:1000::32
2002:2e05:812::2e05:812 SIP/SDP
884
Status: 183
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
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
10 19:06:10.568197
2002:2e05:812::2e05:812 2a02:908:a:1000::32
sip:093464269901@[2a02:908:a:1000::32]:5060;transport=udp |
SIP
721
Request: ACK
UM TS 411
29 von 63
29.07.2016
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
11 19:06:14.549714
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
12 19:06:14.557811
2002:2e05:812::2e05:812 2a02:908:a:1000::32
SIP
721
Request: ACK
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
INVITE sip:022734060893@[2002:2e05:812::2e05:812] |
1193
Request:
Source Port: 5060
Length: 1119
UM TS 411
30 von 63
29.07.2016
[Stream index: 0]
Request-Line: INVITE sip:022734060893@[2002:2e05:812::2e05:812] SIP/2.0
Message Header
Message Body
14 19:06:16.649162
Trying |
2002:2e05:812::2e05:812 2a02:908:a:1000::32
SIP
398
Status: 100
Source Port: 5060
Length: 324
Checksum: 0x9a43 [validation disabled]
[Stream index: 0]
Message Header
15 19:06:16.670608
Ringing |
2002:2e05:812::2e05:812 2a02:908:a:1000::32
SIP
478
Status: 180
Source Port: 5060
Length: 404
Checksum: 0xaaf1 [validation disabled]
[Stream index: 0]
Status-Line: SIP/2.0 180 Ringing
Message Header
17 19:06:23.623845
2002:2e05:812::2e05:812 2a02:908:a:1000::32
SIP/SDP
INVITE sip:093464269901@[2a02:908:a:1000::32]:5060;transport=udp, in-dialog |
391
Request:
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
31 von 63
29.07.2016
|
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Description, name and address (m): audio 7078 RTP/AVP 96 97 98 99 0 8 101 100 102
Attribute (a): rtpmap:96 opus/48000/2
Attribute (a): fmtp:96 useinbandfec=1
Attribute (a): rtpmap:97 SILK/16000
Attribute (a): rtpmap:98 speex/16000
Attribute (a): fmtp:98 vbr=on
Attribute (a): rtpmap:101 telephone-event/48000
Attribute (a): sendonly
Description, name and address (m): video 0 RTP/AVP 0
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
20 19:06:24.118539
2002:2e05:812::2e05:812 2a02:908:a:1000::32
SIP/SDP
391
Request:
Source Port: 5060
Length: 1541
[Stream index: 0]
Message Header
Message Body
UM TS 411
32 von 63
29.07.2016
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Attribute (a): inactive
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
sip:022734060893@[2002:2e05:812::2e05:812] |
2002:2e05:812::2e05:812 SIP
596
Request: ACK
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
24 19:06:25.138690
2002:2e05:812::2e05:812 2a02:908:a:1000::32
SIP/SDP
391
Request:
Source Port: 5060
Length: 1541
[Stream index: 0]
Message Header
UM TS 411
33 von 63
29.07.2016
Message Body
Media Attribute (a): sendonly
Media Attribute (a): inactive
|
25 19:06:25.234841
2a02:908:a:1000::32
2002:2e05:812::2e05:812 SIP/SDP
897
Status: 200 OK
Source Port: 5060
Length: 823
Checksum: 0x43bc [validation disabled]
[Stream index: 0]
Message Header
Message Body
Media Attribute (a): recvonly
26 19:06:25.268651
2002:2e05:812::2e05:812 2a02:908:a:1000::32
SIP
731
Request: ACK
Source Port: 5060
Length: 657
Checksum: 0xc407 [validation disabled]
[Stream index: 0]
Message Header
UM TS 411
34 von 63
29.07.2016
27 19:06:30.207561
2a02:908:a:1000::32
sip:022734060893@[2002:2e05:812::2e05:812] |
2002:2e05:812::2e05:812 SIP
612
Request: BYE
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
35 von 63
29.07.2016
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
Message Body
SIP/2.0 100 Trying
Message Header
Via: SIP/2.0/UDP 192.168.178.22:5060;received=62.143.252.132;branch=z9hG4bK.ARcdmJPc;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.ARcdmJPc;rport=5060
To: <sip:*[email protected]>;tag=snl_0031867329
CSeq: 20 INVITE
Call-ID: sstavkgSAL
WWW-Authenticate: Digest realm="srxadmin@localhost", nonce="227071564f3f2e3d4e59ba003eb7424982adb2bb", 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
36 von 63
29.07.2016
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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="227071564f3f2e3d4e59ba003eb7424982adb2bb", algorithm=MD5, username="93464269901",
uri="sip:*[email protected]", response="8b1e0bdddeeb2ba34fb95d8
Message Body
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
37 von 63
29.07.2016
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
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
38 von 63
29.07.2016
Supported: outbound
Accept: text/plain
Expires: 3600
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="2233344689e00fb5f640b95a64df29b27a7d398d", algorithm=MD5, username="93464269901", uri="sip:hiq7asbcv41a.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.xto5skgK;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
39 von 63
29.07.2016
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-479fb7dd-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:
Message Body
2a02:908:fff0:282:c158:8513:fa43:50f8
Connection Information (c): IN IP6 2a02:908:fff0:282:c158:8513:fa43:50f8
UM TS 411
40 von 63
29.07.2016
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
WWW-Authenticate: Digest realm="srxadmin@localhost", nonce="423155222214f7487e6a154c9228af67769a00c978", 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:
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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="423155222214f7487e6a154c9228af67769a00c978", algorithm=MD5, username="93464269901", uri="sip:[email protected]", response="715aad9df9ab2b5e212a3943
Message Body
2a02:908:fff0:282:c158:8513:fa43:50f8
UM TS 411
41 von 63
29.07.2016
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Description, name and address (m): video 9078 RTP/AVP 96 97
Attribute (a): rtpmap:96 VP8/90000
Attribute (a): rtpmap:97 H264/90000
Attribute (a): fmtp:97 profile-level-id=42801F
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
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
42 von 63
29.07.2016
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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="423155222214f7487e6a154c9228af67769a00c978", algorithm=MD5, username="93464269901", uri="sip:[email protected]", 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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="423155222214f7487e6a154c9228af67769a00c978", 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
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
43 von 63
29.07.2016
Call-ID: fjBPx8WCd9
Max-Forwards: 70
Supported: outbound
Content-Length: 640
Contact:
Message Body
2a02:908:fff0:282:c158:8513:fa43:50f8
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
WWW-Authenticate: Digest realm="srxadmin@localhost", nonce="423155222214f7487e6a154c9228af67769a00c978", 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:
Max-Forwards: 70
CSeq: 20 ACK
UM TS 411
44 von 63
29.07.2016
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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="423155222214f7487e6a154c9228af67769a00c978", algorithm=MD5, username="93464269901", uri="sip:[email protected]", response="26db3638549addd498721695
Message Body
2a02:908:fff0:282:c158:8513:fa43:50f8
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
UM TS 411
45 von 63
29.07.2016
Media
Media
Media
Media
Media
Media
Description, name and address (m): audio 40992 RTP/AVP 0 8 102
Attribute (a): fmtp:102 0-15
Attribute (a): ptime:20
Attribute (a): recvonly
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
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
46 von 63
29.07.2016
Content-Length: 243
Message Body
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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="423155222214f7487e6a154c9228af67769a00c978", algorithm=MD5, username="93464269901", uri="sip:[email protected]", 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:
uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="ce178794
Message Body
2a02:908:fff0:282:c158:8513:fa43:50f8
UM TS 411
47 von 63
29.07.2016
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:
uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="3bee6222
Message Body
2a02:908:fff0:282:c158:8513:fa43:50f8
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
UM TS 411
48 von 63
29.07.2016
Media
Media
Media
Media
Attribute (a): fmtp:102 0-15
Attribute (a): ptime:20
Attribute (a): recvonly
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
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
49 von 63
29.07.2016
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
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:
uri="sip:022753809999@[2a02:908:a:1000::4f]:5060;transport=udp", response="bf8e7061
Message Body
2a02:908:fff0:282:c158:8513:fa43:50f8
UM TS 411
50 von 63
29.07.2016
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
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
UM TS 411
51 von 63
29.07.2016
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
52 von 63
29.07.2016
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-479fb7dd-4b87cdfa9b58>"
Message Body
2a02:908:fff0:282:d5c2:5640:f7d5:baef
Connection Information (c): IN IP6 2a02:908:fff0:282:d5c2:5640:f7d5:baef
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
WWW-Authenticate: Digest realm="srxadmin@localhost", nonce="4237519055a05573a300e13850c9b3e122f6415953", 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
53 von 63
29.07.2016
Call-ID: np8Ek0zNdi
Contact:
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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="4237519055a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="93464269901", uri="sip:[email protected]", response="96d0f0c1084e1c07567f330f
Message Body
2a02:908:fff0:282:d5c2:5640:f7d5:baef
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
54 von 63
29.07.2016
CSeq: 21 INVITE
Call-ID: np8Ek0zNdi
Date: Wed, 27 Jul 2016 13:30:20 GMT
Content-Length: 347
Message Body
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
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
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="4237519055a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="93464269901", uri="sip:[email protected]", response="96d0f0c1084e1c07567f330f
UM TS 411
55 von 63
29.07.2016
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
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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="4237519055a05573a300e13850c9b3e122f6415953", algorithm=MD5, username="93464269901",
uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="a22bb4aa
Message Body
UM TS 411
56 von 63
29.07.2016
2a02:908:fff0:282:d5c2:5640:f7d5:baef
SIP/2.0 200 Ok
Message Header
CSeq: 1235 INVITE
Supported: outbound
Contact:
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
57 von 63
29.07.2016
Supported: timer
Date: Wed, 27 Jul 2016 13:30:51 GMT
Content-Length: 358
Message Body
Media Attribute (a): recvonly
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:
Message Body
2a02:908:fff0:282:d5c2:5640:f7d5:baef
UM TS 411
58 von 63
29.07.2016
Media
Media
Media
Media
Attribute
Attribute
Attribute
Attribute
(a):
(a):
(a):
(a):
rtpmap:101 telephone-event/48000
sendonly
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:
uri="sip:022734064551@[2a02:908:a:1000::4f]:5060;transport=udp", response="4a3ffaa0
Message Body
2a02:908:fff0:282:d5c2:5640:f7d5:baef
Message Header
Via: SIP/2.0/UDP [2a02:908:fff0:282:d5c2:5640:f7d5:baef]:5060;branch=z9hG4bK.~lUFdNXg1;rport
Contact:
Max-Forwards: 70
UM TS 411
59 von 63
29.07.2016
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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="4237519055a05573a300e13850c9b3e122f6415953", 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
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
UM TS 411
60 von 63
29.07.2016
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:
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:
[truncated]Authorization: Digest realm="srxadmin@localhost", nonce="4237519055a05573a300e13850c9b3e122f6415953", 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
61 von 63
29.07.2016
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Media
Description, name and address (m): audio 7080 RTP/AVP 96 97 98 99 0 8 101 100 102
Attribute (a): rtpmap:96 opus/48000/2
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:
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
62 von 63
29.07.2016
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
UM TS 411
63 von 63
29.07.2016

Provider Specific Requirements for the passive NTP in

Transcription

Similar documents

Bestellen Sie jetzt!