hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 10 Messaging | |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 10.1 Overview | The PCSP interface follows a Web Service paradigm. The interface employs SOAP 1.1 messages to transfer XML encoded entities (from the PCSP data model) between client and server. Messages are transported between client and server using the HTTP 1.1 protocol. For a complete discussion of the transport considerations, see... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 10.2 CMS and PS Messaging Role Requirements | In general, both CMS and PS may be implemented to fully support client and server messaging roles. However, within the scope of IPCablecom CMS provisioning, the CMS and PS assume the role requirements specified in table 1. Table 1: CMS and PS Messaging Roles Message CMS as client CMS as server PS as client PS as server... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 10.3 WSDL Document | The PCSP interface is specified using Web Service Description Language 1.1. Just as with a Corba IDL, the WSDL interface definition specifies the remote methods on the interface, the arguments the methods accepts, the return values from the methods, and any interface specific data types that must be defined. Additional... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 11 Security | The PCSP interface is secured using the IPSec ESP protocol in transport mode. Key management is implemented using IKE with pre-shared keys. This security infrastructure is already used at the CMS for various interfaces. See [3] for full details. ETSI ETSI TS 103 161-17 V1.1.1 (2011-04) 20 Annex A (normative): PCSP XML ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 1 Scope | The present document describes the IPCablecom Call Management Server (CMS) to CMS Signalling protocol intended for use by a CMS to communicate with another CMS in order to support packet-based voice and other real-time multimedia applications. The protocol exchanges between a CMS and a Media Gateway Controller (MGC) ar... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Void. [2] Void. [3] IETF RFC 4566 (July 2006): "SDP: Session Description Protocol". [4] IETF RFC 2396 (August 1998): "Uniform Resource Identifiers (URI): Generic Syntax". [5] IETF RFC 2397 (August 1998): "The "data" URL Sc... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 3398 (2002): "ISUP to SIP Mapping, December". ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 13 [i.2] Void. [i.3] PacketCable 1.5 Architecture Fram... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 3 Definitions and abbreviations | |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: active: service flow is said to be "active" when it is permitted to forward data packets NOTE: A service flow must first be admitted before it is active. admitted: service flow is said to be "admitted" when the CMTS has reserved resour... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: BCID Billing Correlation ID BLV Busy Line Verification CA Call Agent CFNA Call Forwarding No Answer CLASS Custom Local Area Signalling Services CMTS Cable Modem Termination System CNAM Calling Name DCS Distributed Call Signalling EI Emergency ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 4 Void | |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5 Background and motivation | The design of the Call Management Server Signaling (CMSS) architecture recognizes the trend towards use of packet networks as the underlying framework for communications. These networks will provide a broad range of services, including traditional best-effort data service, as well as enhanced value-added services such ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5.1 Requirements and Design Principles | This clause briefly describes the application requirements that led to the set of CMSS design principles. The need to support primary line telephony service requires enhanced bearer channel and signalling performance, including: • Low delay - end-to-end packet delay must be sufficiently small that it does not interfere... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5.2 IPCablecom Architecture | The CMS to CMS Signaling (CMSS) Architecture follows the principles outlined above to support a robust multimedia service. Figure 1 introduces the key components in the architecture. Multimedia Terminal Adapters (MTAs) may either be embedded into the Cable Modem (CM) or they may be stand-alone. The cable access network... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5.3 CMSS Trust Model | CMSS defines a trust boundary around the various systems and servers that are within a single domain. These trusted systems include the Internal and External Border Proxies(more generally referred to as tandem proxies or simply proxies), CMSs, CMTSs of the cable access network and various servers such as bridge servers... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5.4 CMS to CMS Architectural Model | The Call Management Server (CMS) is an architectural entity that performs those services necessary to enable endpoints to establish IP multimedia sessions. The CMS is a complex of server functions that support session signalling, number translation and feature support. In addition to processing signalling messages, the... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5.5 Overview of CMS Behaviour | IPCablecom defines the Call Management Server (CMS) as a complex of server functions which support call signalling, number translation, call routing, feature support and admission control. Within the CMS complex, the IPCablecom architecture allocates many of these responsibilities to the Proxy/CA/MGC and the Gate Contr... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5.6 Basic Telephony Call Flow | Figure 4 presents a high-level overview of an example basic call that uses the CMSS protocol between the CMSs through a proxy while the end-points (MTAs) are using the NCS protocol. In this example, when the MTA goes off-hook and the user dials a telephone number, the originating MTA (MTAO) collects the dialled digits ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 5.7 CMS-MGC Basic Telephony Call Flow | This clause presents a high level overview of a basic call that uses the CMSS protocol between a CMS and an MGC to make an on-net to off-net call. The procedure shown follows the SIP to ISUP mapping recommendations provided in [i.1]. NOTE: CMSS in general is intended to be compatible with the interworking recommendatio... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6 SIP PROFILE | This clause defines a SIP [6] profile for usage in CMSS compliant systems. This clause is structured to mirror the SIP document and its clause numbering. The subclauses of this clause are numbered such that the second digit tracks the SIP section numbers of the SIP specification [6] and section titles at all header lev... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.1 Introduction | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 1. Since there are no requirements in SIP/2.0 [6] clause 1, CMSS implementations are automatically compliant with it. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.2 Overview of SIP Functionality | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 2. Since there are no requirements in SIP/2.0 [6] clause 2, CMSS implementations are automatically compliant with it. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.3 Terminology | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 3. Since there are no requirements in SIP/2.0 [6] clause 3, CMSS implementations are automatically compliant with it. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.4 Overview of Operation | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 4. Since there are no requirements in SIP/2.0 [6], clause 4, CMSS implementations are automatically compliant with it. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.5 Structure of the Protocol | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 5. Since there are no requirements in SIP/2.0 [6], clause 5, CMSS implementations are automatically compliant with it. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.6 Definitions | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 6. NOTE: The term "client" in this clause covers both UAs and proxies. Since there are no requirements in SIP/2.0 [6], clause 6, CMSS implementations are automatically compliant with it. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7 SIP Messages | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 7, except as noted below. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 27 |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7.1 Requests | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 7.1, except as defined in this clause. The INVITE, ACK, CANCEL, BYE and OPTIONS methods shall be supported. The REGISTER method may be supported. The SIP URI as defined in [6] and tel URI as defined in clause 7.1 shall be supported in the Reque... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7.2 Responses | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 7.2. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7.3 Header Fields | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 7.3 and its subclauses. Furthermore, CMSS compliant applications shall be able to both generate and accept short and long form header field names as defined in [6], clause 7.3.3. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7.4 Bodies | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 7.4 and its subclauses except as defined in this clause. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7.4.1 Message Body Types | CMSS compliant applications shall support the message body type "application/sdp". The message body type "application/sdp" shall be supported with the INVITE, UPDATE and PRACK methods as well as any non-failure response to these methods. Furthermore, the message body type "application/sdp" shall be supported in success... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7.4.2 Message Body Length | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 7.4.2. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.7.5 Framing SIP Messages | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 7.5. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.8 General User Agent Behaviour | Behaviour of CMSS User Agents (UA) shall be in accordance with clause 8 and with [6] except as noted in this clause. NOTE: The behaviour defined in this clause applies only to requests and responses outside of a dialog. Behaviour within a dialog is defined in clause 6.12. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.8.1 UAC Behaviour | Support for the REGISTER method is OPTIONAL, however, if supported, it shall be as specified in [6], clause 8.1. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 28 When a request is forked, multiple responses may be received, each of which results in the creation of an early dialog. Furthermore, each response may contain an a... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.8.1.1 Generating the Request | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 8.1.1, except as noted below. Request-URI in the request contains the address of the callee. This will normally be a telephone-number, but it may also be a general SIP URI. This can, for example, be used when forwarding to a an Interactive Voic... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.8.1.2 Processing Responses | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 8.1.3 except as noted in this clause. When receiving a 401 (Unauthorized) or 407 (Proxy Authentication Required) response, the SIP authorization procedure should only be followed if the UAC has credentials for the realm in question. When receiv... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.8.2 UAS Behaviour | The CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 8.2 and its subclauses. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.8.3 Redirect Servers | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 8.3. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.9 Cancelling a Request | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 9 and its subclauses. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.10 Registrations | Proxies shall and UACs may, support the SIP REGISTER method in accordance with [6], clause 10. Support for registrars is OPTIONAL; however if supported, it shall be as specified in [6], clause 10. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.11 Querying for Capabilities | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 11. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.12 Dialogs | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 12 and its subclauses. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.13 Initiating a Session | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 13 and its subclauses, except as noted in this clause. CMSS compliant implementations should include a message body of type "application/sdp" with the initial INVITE. When an initial INVITE is received with an offer SDP, an answer SDP should be... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.14 Modifying an Existing Session | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 14 and its subclauses, except as noted in this clause. When a CMSS compliant implementation sends a re-INVITE, it should include a message body of type "application/sdp" with a new offer. Furthermore, CMSS compliant implementations shall suppor... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.15 Terminating a Session | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 15 and its subclauses. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.16 Proxy Behaviour | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 16 and its subclauses, except as noted in this clause. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 30 Support for multiple simultaneous media streams for a single call is OPTIONAL for an MTA. Since parallel forking may result in multiple simultane... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.17 Transactions | CMSS compliant applications shall be in accordance with SIP/2.0 [6] clause 17 and its subclauses except as noted in this clause. Behaviour of CMSS servers (proxies) shall be in accordance with clause 8, which takes precedence over [6], clause 17 in case of any conflicts. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.18 Transport | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 18 and its subclauses. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.19 Common Message Components | |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.19.1 SIP URI Component | The definition of a SIP URI is as given in [6] clause 19.1.1 and extended in clause 7.1.1 in the present document. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20 Header Fields | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 20 and its subclauses, except as defined in this clause. In addition to the extensions listed in clause 7, the following SIP headers shall be supported by CMSS compliant applications. 1) Accept 2) Accept-Encoding 3) Accept-Language 4) Allow 5) ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.1 Accept | The Accept header shall be supported as specified in [6], clause 20.1. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.2 Accept-Encoding | The Accept-Encoding header shall be supported as specified in [6], clause 20.2, except as noted below. The Accept-Encoding header may be used by CMSS compliant implementations. The "identity" encoding value shall be supported; other encodings may be supported. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.3 Accept-Language | The Accept-Language header shall be supported as specified in [6], clause 20.3, except as noted below. CMSS compliant implementations should include the "Accept-Language" header in requests or responses as defined in [6]. The value "en" for English shall be supported, other values may be supported based on configuratio... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.4 Alert-Info | The Alert-Info header shall be supported for emergency calls (see clause 8.4.2); otherwise, it may be supported. When included, it shall be as specified in [6], clause 20.4. It is noted that there are security risks associated with acting on the Alert-Info header as described in [6], clause 20.4. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.5 Allow | The Allow header field shall be supported as specified in [6], clause 20.5. CMSS compliant implementations shall include the "Allow" header in the initial INVITE and the 200-OK response to the initial INVITE. When an Allow header is not received, the set of supported methods is unknown. Refer to annex B for a list of s... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.6 Authentication-Info | Support for the Authentication-Info is OPTIONAL; however, if supported, it shall be as specified in [6], clause 20.6. See also clause 6.22. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 32 |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.7 Authorization | Support for the Authorization header field is OPTIONAL; however, if supported, it shall be as specified in [6], clause 20.7. See also clause 6.22. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.8 Call-ID | The Call-ID header shall be supported as specified in [6], clause 20.8, except as noted below. CMSS restricts contents of the Call-ID header in order to support user Privacy. When Privacy is requested by the session originator, the Call-ID shall not contain the "@" sign and hence consists of a single "word" as defined ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.20.9 Call-Info | The Call-Info header shall be supported as specified in [6], clause 20.9 except as noted below. The Call-Info header "purpose" parameter value of "answer_if_not_busy" shall be supported; other encodings may be supported. It is noted that there are security risks associated with acting on the Call-Info header as describ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.21 Response Codes | CMSS compliant applications shall be in accordance with SIP/2.0 [6], clause 21 and its subclauses, except as specified below. CMSS compliant applications should not issue a 401 or a 407 response; however, they shall process any such received responses in accordance with clause 6.8.1.2. CMSS compliant implementations sh... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.22 Usage of HTTP Authentication | Support of HTTP Authentication is OPTIONAL; however, if used, it shall be as specified in [26] and [6], clause 22. Where these documents conflict, [26] takes precedence. See also clause 6.21. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.23 S/MIME | Support of S/MIME is OPTIONAL; however, if used, it shall be as specified in [26] and [6], clause 23. Where these documents conflict, [26] takes precedence. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.24 Examples | The examples provided in [6], clause 24 do not apply to CMSS compliant implementations. For equivalent examples, refer to clause 8. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.25 Augmented BNF for the SIP Protocol | CMSS compliant applications shall comply with SIP/2.0 [6], clause 25. 6.26 Security Considerations: Threat Model and Security Usage Recommendations CMSS complaint applications shall comply with the IPCablecom Security specification [26]. Support for the SIP Security Considerations specified in [6], clause 26 is conside... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 6.27 Table of Timer Values | CMSS compliant applications shall comply with SIP/2.0 [6], Appendix A. CMSS compliant applications shall also support the timer values defined in annex A according to the procedures specified in clause 8.4. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 38 |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7 SIP Extensions | SIP [6] has a flexible mechanism for adding extensions and new fields to the protocol for support of additional capabilities. This clause defines a set of SIP extensions that enables IPCablecom CMSS-compliant systems to provide a robust multimedia service platform supporting basic telephony, CLASS and custom calling fe... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.1 URIs for Telephone Calls | CMSS compliant implementations shall support URIs for telephone calls as specified in RFC 3966 [28], except as noted in this clause. 7.1.1 Routing Number, Number Portability, Carrier Identification Code and Dial Around Indication Number CMSS compliant implementations shall support extensions to the tel URI that relate ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.1.2 Procedures at an Originating CMS | If the Request-URI of an initial INVITE requires routing via an equal access carrier in the PSTN and is either a tel-URI or a Sip URI with user=phone, a carrier-id-code parameter shall be included in the telephone-subscriber part with a value corresponding to the identity of the carrier preferred by the party paying fo... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.1.3 Procedures at a Terminating CMS | No specific procedures are defined. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.1.4 Procedures at Proxy | A Tel or SIP(s) URI containing a "npdi" in the telephone-subscriber part shall not appear other than in an initial INVITE Request-URI or the URI of a Refer-To header in a REFER request sent to another proxy or CMST. A proxy that performs the local-number-portability lookup and passes the REFER or initial INVITE request... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.2 Reliability of Provisional Responses | CMSS compliant implementations shall support the extensions defined in [7], except as noted in this clause. CMSS compliant implementations shall by default include a Supported header containing the value "100rel" in the initial INVITE request. Alternatively, if a CMS is configured to require use of reliable provisional... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.3 SIP UPDATE Method | CMSS compliant implementations shall support the extensions defined in [10] except as noted in this clause. CMSs shall include the method "UPDATE" in the Allow header field in the relevant requests and responses as described in clause 6. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 41 |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4 Integration of Resource Management and SIP | CMSS compliant implementations shall support the extensions defined in [11] except as noted in the subclauses below. In particular, CMSS compliant implementations shall support segmented QoS preconditions. CMSS compliant implementations may support end-to-end QoS preconditions, although the procedures are not specified... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4.1 Procedures at an Originating CMS | CMSS compliant implementations shall support use of segmented QoS preconditions as defined in the following subclauses, however if a given deployment does not want to use QoS preconditions, the session originator (CMSO) shall not include any QoS precondition attributes in the SDP and the procedures below do not apply. ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4.1.1 Default Operation Using QoS Preconditions Strength "Optional" | Unless configured otherwise, the session originator (CMSO) shall include a Supported header containing the value "precondition". For each media flow in the SDP sent with the INVITE, the precondition-type shall be "qos" and the status-type shall be segmented, i.e. there needs to be separate attributes for the local and ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4.1.2 QoS Preconditions Strength "None" | If a given deployment has no preference about the use of QoS preconditions, the session originator (CMSO) should include a Supported header containing the value "precondition". For each QoS precondition it includes in the SDP, the precondition-type shall then be "qos" and the status-type shall be segmented, i.e. there ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4.1.3 QoS Preconditions Strength "Mandatory" | If a given deployment requires use of QoS preconditions, the session originator (CMSO) shall include a Require header containing the value "precondition". For each media flow in the SDP sent with the INVITE, the precondition-type shall be "qos" and the status-type shall be segmented, i.e. there needs to be separate att... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4.2 Procedures at a Terminating CMS | When an INVITE is received without any QoS preconditions, the procedures in this clause do not apply; instead normal SIP processing of the call occurs. When an INVITE with QoS preconditions is received, three sets of procedures are defined in the following clauses. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4.2.1 QoS Preconditions Strength "None" or "Optional" | Unless configured otherwise, on receipt of an INVITE request containing "optional" or "none" QoS preconditions using a segmented status-type, a terminating CMS (CMST) shall generate a 183-Session-Progress response with an SDP containing mandatory preconditions. For each media flow with QoS precondition in the answer SD... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.4.2.2 QoS Preconditions Strength "Mandatory" | On receipt of an INVITE request containing mandatory QoS preconditions using a segmented status-type, a terminating CMS (CMST) shall generate a 183-Session-Progress response with an SDP. For each media flow with QoS precondition in the answer SDP sent, the precondition-type shall be "qos" and the status-type shall be s... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.5 SIP-Specific Event Notification | CMSS compliant implementations shall support the extensions defined in [9]. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.6 The REFER Method | CMSS compliant implementations shall support the extensions defined in [17] except as noted in this clause. NOTE: This method makes use of the Notify mechanism defined in clause 7.5. In CMSS, the use of the REFER method is specified both within an existing dialog and outside of a dialog as a dialog creating request. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.6.1 Procedures at an Originating CMS | The CMS originating a REFER shall include additional header parameters in the Refer-To header for a nested P-DCS-Billing-Info header and should include the additional header parameters for nested P-DCS-Laes and P-DCS- Redirect headers, as specified in clause 7.7. NOTE: Please refer to clause 7.7.2 for additional guidan... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.6.2 Procedures at a Terminating CMS | If the action requested by the REFER is a SIP INVITE, then the NOTIFY sent when it completes shall include the call-leg identification for the newly established session (i.e. the From, To and Call-ID headers). ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 43 The uri-parameters in a SIP or tel URI in a Refer-To header shall ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7 SIP Proxy to Proxy Extensions for Supporting DCS | CMSS compliant implementations shall support the extensions defined in [16] except as defined in this clause. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.1 P-DCS-Trace-Party-ID | Support for the P-DCS-TRACE-PARTY-ID header is not required. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2 P-DCS-LAES and P-DCS-REDIRECT | For the purposes of the present document, the 4th paragraph in clause 8 of [16] is intended to require that CMSS compliant devices fully implement the P-DCS-LAES and P-DCS-REDIRECT headers as defined in [16] (with the exceptions noted in the present document) and also implement a mechanism that allows the service provi... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.1 P-DCS-LAES Header | The P-DCS-LAES-Header is used to pass the responsibility for performing electronic surveillance on a call from one CMS to another. For example, if a call terminates to a line that is marked for surveillance and the line also has call-forwarding activated, then the terminating CMS can include the P-DCS-LAES header in th... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.2 Surveillance Procedures at Originating CMS | An originating CMS (CMSO) is required to perform electronic surveillance functions for an originating call if the originating line has an outstanding lawfully authorized electronic surveillance order. An originating CMS may also choose to perform electronic surveillance functions on behalf of a terminating CMS for cert... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.2.1 CMSO Receives REFER Request or Redirect Response | When CMSO receives a 3XX Redirect response containing a P-DCS-Laes header in response to an INVITE, or receives a REFER request containing a P-DCS-Laes header in the Refer-To header for an active dialog, then it shall copy the received P-DCS-Laes header into the subsequent INVITE that is generated as a result of the RE... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.3 Surveillance Procedures at Terminating CMS | A terminating CMS is required to perform surveillance functions for an incoming call for two cases; when the terminating line has an outstanding lawfully authorized electronic surveillance order and when the received INVITE request contains a P-DCS-Laes header requesting the terminating CMS to perform surveillance for ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.3.1 Terminating Line is Able to Accept the Call | If the terminating line is able to accept the call and either a local outstanding lawfully authorized electronic surveillance order exists for the line, or a P-DCS-Laes header is received in the INVITE, then CMST shall send a SignalingStart message to the local DF containing the identity of the terminating line and the... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.3.2 Terminating Line is Unable to Accept the Call | If CMST receives an INVITE request containing a P-DCS-Laes header and the terminating endpoint is not able to accept the call for some reason (e.g. line is busy, line is unknown) and CMST does not need to otherwise initiate a surveillance session, then CMST shall send a SurveillanceStop message containing the following... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.3.3 Terminating CMS is Unable to Perform Call-Content Surveillance | If CMST receives an INVITE containing a P-DCS-Laes header requesting call-data and call-content surveillance and CMST is unable to perform the call-content surveillance for some reason (e.g. call routed to voice mail server), then CMST must continue to perform the call-data surveillance as specified in clause 7.7.2.3.1... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.3.4 Terminating CMS Redirects or Transfers the Call | If CMST is required to perform surveillance on a call (either as a result of terminating to a subscriber with a lawfully authorized surveillance order, or as specified in the P-DCS-Laes header of the INVITE message from the CMSO), but the call is redirected or transferred to a new terminating line, then CMST shall send... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.