hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.4 Surveillance Procedures at a CMS Proxy | Electronic surveillance does not impose any special requirements on CMS tandem-proxies that act as dedicated routing proxies. Tandem-proxies will pass the P-DCS-Laes header transparently and will not communicate with the DF. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 49 |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.2.5 Interworking with CSCFs | CSCFs do not generate CCCIDs even when intercepting call content, but populate the CCCID with a null value. Therefore, a CMS that receives a P-DCS-LAES from a CSCF that requires call content intercept will need to generate a CCCID value on behalf of the CSCF. If the CMST receives a SIP message containing a P-DCS-LAES h... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.3 P-DCS-Billing-Info | The P-DCS-Billing-Info header is used to pass accounting information between CMS nodes. clauses 7.7.3.1 through 7.7.3.3 augment the P-DCS-Billing header-Info requirements in [16] by clarifying how the JIP-param procedures are applied based on the role of the CMS. Clause 7.7.3.4 describes special procedures that are use... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.3.1 Procedures at an Originating CMS | An originating CMS that passes a REFER or initial INVITE request to a proxy or a terminating CMS shall include the JIP-param in the P-DCS-Billing-Info header indicating the NPA-NNX of the originating CMS. In the case of a REFER request, the JIP-param shall be included in the P-DCS-Billing header in the Refer-To header.... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.3.2 Procedures at a Terminating CMS | A terminating CMS that returns a 3xx-Redirect response to an originating CMS shall include the JIP-param in the P-DCS-Billing-Info header indicating the NPA-NNX of the "forwarded from" party. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.3.3 Procedures at a Proxy | No specific procedures are defined. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.3.4 Interaction with CSCF Signaling Nodes | IPCablecom 2.0 [i.9] does not support the P-DCS-Billing header. Instead, accounting information is shared between CMS and Call Session Control Functions (CSCFs) using the P-Charging-Vector and P-Charging-Function-Address headers as defined in [38] and [39] and the P-Charge-Info header as defined in [52]. The informatio... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.3.4.1 Sessions initiated from a CSCF to a CMS or MGC | Incoming sessions from a CSCF will contain charging information in a P-Charging-Vector and possibly a P-Charging- Function-Address header. A P-Charge-Info header [52] may also be present. If the incoming request is from within the same trust domain as the CMS or MGC, the P-Charging-Vector header will be guaranteed to c... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.3.4.2 Sessions initiated from a CMS or MGC to a CSCF | Outgoing sessions to a CSCF will contain charging information in a P-Charging-Vector and possibly a P-Charging- Function-Address header. A P-Charge-Info header [52] can also be present. If the outgoing request is for a CSCF within the same trust domain as the CMS or MGC, the P-Charging-Vector header needs to be populat... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.7.4 P-DCS Option Tag | The extensions defined in [16] do not define any option tags; however the CMSS specification defines the option tag "P-DCS" to indicate support of the extension headers P-DCS-Billing-Info, P-DCS-Laes and P-DCS-Redirect as specified in [16]. CMSS compliant implementations may use the option tag "P-DCS" in the Supported ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.8 The SIP "Replaces" Header | CMSS compliant implementations shall support the extensions defined in [18]. 7.9 Private Extensions to the SIP Protocol for Asserted Identity within Trusted Networks CMSS compliant implementations shall support the asserted identity extensions defined in [13] except as defined in this clause. NOTE 1: Support of the ass... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.11 Globally Routable User Agent URI (GRUU) | A CMSS compliant implementation shall provide a GRUU referring to itself in the contact address of dialog-initiating SIP messages, as specified in [36]; such a GRUU conforms to the definition of a self-made GRUU. A CMSS compliant implementation shall handle requests received outside of the dialog in which the contact w... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.12 The Early Session Disposition Type for SIP | CMSS compliant implementations shall support the early session disposition type as specified in RFC 3959 [40]. The detection and prevention of fraud issues associated with the use of the early session disposition type is considered outside the scope of the present document. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 53 7... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.15 The Session Initiation Protocol (SIP) Join Header | CMSS compliant implementations shall support the Join header as described in RFC 3911 [44]. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 7.16 SUBSCRIBE to Dialog Event Package | In order to allow a CMS to determine the line status of an endpoint, CMSS compliant implementations shall support the functionality described in RFC 4235 [46] except as indicated in this clause. CMSS compliant implementations shall ignore newly introduced message headers in the Notify message body that are not recogniz... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8 CMS-CMS SIGNALING | In this clause, the CMS to CMS signalling that takes place between CMSs within a domain and the signalling that takes place between domains is presented. The primary difference between intra-domain signalling and inter-domain signalling is the use of External Border Proxies, which are described in clause 5.4. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1 CMS Interfaces | Signaling between two CMSs is simply referred to as CMS-CMS signalling or CMSS signalling. From a CMS-CMS signalling perspective, the Media Gateway Controller (MGC), Bridge Server, Announcement Server and other media service nodes are analogous to the CMS, although they do not interface with a Gate Controller. In the f... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1 Overview of CMS Behaviour | The CMS contains a trusted SIP User Agent Client (UAC) and User Agent Server (UAS). It maintains call state during the life of the call and monitors the endpoint device for state changes that affect the call. The interface between the CMS and the endpoint device is outside the scope of the present document, but the par... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.1 CMS Behaviour in Support of Call Originator | Through a mechanism outside the scope of the present document, the CMS becomes aware that the endpoint device desires to initiate a call and determines the destination address of that desired call. This may be done, for example, through a Notify message in NCS, where the MTA detected the off-hook condition and collecte... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.2 CMS Behaviour in Support of Call Destination | CMSO sends an INVITE request to CMST, where the dialled number is translated into the address of the terminating endpoint. Through negotiation with the terminating endpoint, CMST determines the media stream properties and authorizes the QoS resources needed. CMST responds to the INVITE request with a provisional 183-Se... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.3 CMS Behaviour in Support of Mid-call Changes | For the duration of the call, CMSO and CMST are available to their respective endpoints and they respond to any mid-call changes requested by the endpoints. Examples of such changes are: hold/resume; codec change; call transfer; three-way-calling; busy-line verification; and emergency interrupt. CMSO and CMST initiate ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.4 CMS Behaviour in Support of Event Messaging | The IPCablecom Event Messaging specification [23] requires a stream of events to be generated on behalf of each endpoint involved in a call, i.e. for each half of the call (originating and terminating). Each of the originating and terminating event streams is identified by its own Billing-Correlation-ID and is further ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.5 CMS Behaviour in Support of Call Forwarding | Requirements for event generation for the Call Forwarding services are based on the billing model of the PSTN. A forwarded call is considered to consist of several call-segments, each of which is billed to the party that initiated that call-segment. For instance, a call from party A to party B that is forwarded to part... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.6 CMS Behaviour in Support of Inter-Domain Call Forwarding | When calling and forwarding is performed between IPCablecom domains (or within a domain when the parties are served by different Record Keeping Servers), it is required that all event messages related to a call segment be recorded by the Record Keeping Server within the domain of the party being charged for that call s... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.7 CMS Behaviour in Support of REFER | Requirements for event generation for the REFER-based services (e.g. Call Transfer, Three-Way Calling) are based on the billing model of the PSTN. Consider the case in which party A calls party B and party B REFERs the call to party C. Assume that all three parties are in the same IPCablecom domain and served by the sa... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.1.8 CMS Behaviour in Support of Inter-Domain REFER | When REFER operations are performed between IPCablecom domains, it is required that all event messages related to a call segment be recorded within the domain of the party being charged for that call segment. It is therefore necessary for a CMS in each IPCablecom domain to remain on the signalling path for the duration... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.1.2 Overview of Tandem Proxy | In theory, all CMSs may communicate with each other, both within a given domain, as well as between different domains. In practice, the need for scalable and manageable security and routing implies that one or more levels of indirection may be needed. The tandem proxy provides this indirection. Tandem proxies, which ma... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.2 CMS Retransmission, Reliability and Recovery Strategies | SIP [6] defines a retransmission scheme based on two timer values, T1 and T2. The retransmission interval starts at T1 seconds and is doubled, with each attempt (up to a limit of T2 seconds), up to some maximum number of retransmissions. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 60 The CMS shall implement an additional ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.3 CMS to CMS Routing | CMS to CMS routing is concerned with routing requests to their destination. CMSS supports routing of general SIP(s) URIs as well as telephone numbers in the form of tel-URIs as defined in clause 7.1. Routing of general SIP(s) URIs simply follows the procedures in clause 6.8.1. Routing of telephone numbers follows the p... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.3.1 Forming a SIP-URI from a tel-URI | The FQDN ("hostport") part of a SIP(s) URI identifies the intended recipient of the request. The recipient may or may not be the final destination for the request. The method by which the CMS determines the FQDN part of a SIP(s) URI formed from a tel-URI is outside the scope of the present document. For example, the CM... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.3.2 Routing a SIP(s) URI at Tandem CMSs | If a CMS receives a request with a SIP(s) URI in the Request-URI that identifies a destination other than the CMS, the CMS considers itself a tandem and attempts to send the request to its intended destination. The CMS may now operate as a stateless proxy as defined in clause 6.16. The Request-URI of the forwarded requ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.3.3 Routing based on tel-URI | Routing based on tel-URIs is performed hop-by-hop. The Request-URI may be rewritten as a result of Local Number Portability lookup, Freephone Number translation, etc. as described in clause 8.3.1. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4 CMS Procedures | The following subclauses contain sample procedures for a basic call from an originating CMS to a terminating CMS and for various mid-call changes that may be initiated by either endpoint. The procedures assume that the participating CMSs have been configured to require support of all CMSS extensions. The call flow diag... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1 CMS Messages and Procedures for Basic Call Setup | The basic INVITE message sequence for a CMSS call setup includes the INVITE/183-Session-Progress/18x/200- OK/ACK exchange, an UPDATE/200-OK exchange and one or two PRACK/200-OK message exchanges. These are shown in figure 4 (clause 5.6) and discussed in the following subclauses. When it is known that the far-end is bei... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.1 CMSO initiating Invite | CMSO becomes aware of a call origination attempt when it receives a Notify message from the MTA. A Media Gateway Controller (MGC) becomes aware of a call origination attempt when it receives a Notify message from the media gateway, or an IP-IAM message from the signalling gateway. A CMS also becomes aware of a call ori... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.1.1 CMSO Authentication and Authorization of Originator | Two different cases are considered here: • a call originating on-net; and • a call originating off-net. Except as specified below, if the call originates on-net, CMSO shall provide a validated originating phone number for the active line on MTAO in the P-Asserted-Identity header. CMSO shall also provide a validated ori... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.1.2 Address Translation | CMSO shall resolve the destination number into either: • the address of a destination endpoint served by this CMS; or • the address of another CMS or proxy (subsequent routing procedures are described in clause 8.3). If it cannot resolve the destination number, it shall consider the request to be in error. ETSI ETSI TS... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.1.3 IP Address Privacy Support | If the caller requested IP Address Privacy, then CMSO shall provide IP address Privacy through the use of an anonymizer as described in clause 9. Since there is no CMSS signalling support for IP address Privacy, CMSO shall either provide the IP address Privacy itself or route the request to an anonymizer. The anonymize... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.1.4 INVITE message generation | If the destination endpoint is not served by CMSO, CMSO generates a SIP INVITE message and sends it to CMST, the CMS that manages the terminating endpoint. Please refer to clause 7.7.2.2 for electronic surveillance procedures at the originating CMS. CMSO shall add the P-DCS-Billing-Info header, which is defined in clau... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.2 Invite from CMSO arrives at CMST | CMST shall resolve the destination number from the Request-URI into either: • the address of a destination endpoint served by this CMS; or • the address of another CMS (subsequent routing procedures are described in clause 8.3). If it cannot resolve the destination number, it shall consider the request to be in error a... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.2.1 CMST Sending 183-Session-Progress Status Response | If the destination endpoint is able to accept the call, CMST sends the 183-Session-Progress provisional response reliably (see clause 7.2) to CMSO. The following call characteristics are determined by CMST and are used to generate the 183-Session-Progress response: • Contact address for direct CMS-CMS signalling messag... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.2.2 CMST Sending 3xx REDIRECT Status Response | Procedures in this clause are invoked when CMST determines (by methods beyond the scope of the present document) that the incoming call is to be forwarded. CMST shall verify that the called party is a subscriber to the Call Forwarding service. If not, CMST shall send a 480 Temporarily Unavailable error response to CMSO... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.2.3 CMST Sending INVITE Request to CMSF | Procedures in this clause are invoked when CMST determines (by methods beyond the scope of the present document) that the incoming call is to be forwarded. CMST shall verify that the called party is a subscriber to the Call Forwarding service. If not, CMST shall send a 480 Temporarily Unavailable error response to CMSO... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.2.4 CMST Sending Other Status Response to INVITE request | A final error response (4xx, 5xx, or 6xx) shall be sent per clause 6. This includes, but is not limited to, 486-Busy Here. The error response shall be formatted as follows. Error (CMST -> CMSO) Header: Requirements On CMST for Message Generation Requirements On CMSO for Message Checking SIP/2.0 xxx Status line header s... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.3 CMSO Receives Initial Status Response | In response to the initial INVITE request, CMSO shall be prepared to receive a 183-Session-Progress provisional response (in a normal call establishment), a 3xx-Redirect response (if the call was forwarded), or a 4xx, 5xx, or 6xx error response (error cases, such as busy). Final responses, including 4xx, 5xx and 6xx, a... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.3.1 CMSO handling of 183-Session-Progress Response | The 183-Session-Progress provisional response received by CMSO shall be checked to ensure that it conforms to the following format: 183-Session-Progress (CMST -> CMSO) Header: Requirements On CMSO for Message Checking SIP/2.0 183 Session Progress Status line with status code 183 shall be present. Via: As described in c... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.3.2 302-Redirect Status Response Handling at CMSO | NOTE 1: The procedures defined in this clause are identical to the procedures defined in clause 8.4.1.8.2. CMSO shall check that the headers of a received 302-Redirect response are as follows. 302-Redirect (CMST -> CMSO) Header: Requirements On CMSO for Message Checking SIP/2.0 302 Moved Temporarily Status line header ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.4 CMST Receiving Acknowledgement of 183-Session-Progress | After sending the 183-Session-Progress response to the INVITE, CMST shall wait for the PRACK message acknowledging the Session-Progress. The PRACK message headers shall be checked as follows. PRACK (CMSO -> CMST) Header: Requirements On CMST for Message Checking PRACK URI SIP/2.0 As described in clause 7.2. Via: As des... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.5 CMST sends 180-Ringing or 183-Session-Progress | Once CMST receives the UPDATE message and any applicable resource reservation for the terminating endpoint has completed successfully, CMST shall send a provisional or final response to CMSO, through the proxy path taken by the initial INVITE request. When the terminating endpoint is on-net, CMST determines, by mechani... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.6 CMSO receives 180-Ringing or 183-Session-Progress | After the originating endpoint has completed the resource reservation and CMSO has sent the UPDATE message to the destination CMS, CMSO will receive one of: 1) a provisional response of 180-Ringing or 183-Session-Progress; 2) a final response of 200-OK; or 3) an error. This clause covers the procedures for the provisio... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.7 CMST Sending final Response | After the destination endpoint has successfully reserved resources, CMST has received the UPDATE message from CMSO (indicating it had also successfully reserved resources) and the destination endpoint has completed whatever alerting procedures were required, CMST sends a final response. For a typical telephony service,... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.7.1 CMST sending 200-OK Final Response | Once CMST determines that the destination endpoint accepts the incoming call (e.g. off-hook, or hook-flash, or by other methods beyond the scope of the present document), it shall send a 200-OK final response to the originating CMS. The message sent by CMST to CMSO shall be formatted as follows. 200-OK (CMST -> CMSO) H... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.7.2 CMST sending 3xx-Redirect Final Response | If the terminating endpoint wishes to forward the call (e.g. if call-forwarding-no-answer is enabled), a final 3xx-Redirect status response shall be sent by CMST, the contact header contains the new URI of the forwarded to destination. CMST determines this by means beyond the scope of the present document. Please refer... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.7.3 Other Status Response to INVITE Request | A final error response (4xx, 5xx, or 6xx) shall be sent as per [6]. This includes, but is not limited to, 480-Temporarily- Unavailable. The error response shall be formatted as follows. Error (CMST -> CMSO) Header: Requirements On CMST for Message Generation SIP/2.0 xxx As described in clause 6.13. Via: From: To: Call-... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.8 CMSO Receives Final Response from CMST | |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.8.1 CMSO Receiving 200-OK | Once the terminating endpoint accepts the incoming call (e.g. off-hook or hook-flash), it sends a 200-OK status message to the originating CMSO. The message sent by CMST to CMSO shall be formatted as follows. 200-OK (CMST -> CMSO) Header: Requirements On CMSO for Message Checking SIP/2.0 200 OK Status line with status ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.8.2 CMSO receiving 302-Redirect | NOTE: The procedures defined in this clause are identical to the procedures defined in clause 8.4.1.3.2. If the terminating device wished to forward the call (e.g. if call-forwarding-no-answer was enabled at the destination), a 302-Redirect status response with the forwarded-to destination URI in the contact header is ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.8.3 CMSO receiving other error response | A final error response (4xx, 5xx, or 6xx) may be sent as per 6.13. This includes, but is not limited to, 480-Temporarily- Unavailable. The error response shall be verified as follows. Error (CMST -> CMSO) Header: Requirements On CMSO for Message Checking SIP/2.0 As described in clause 6.13. Via: From: To: Call-ID: Cseq... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.1.9 Session Timer expiration at CMSO | On expiration of timer T3, CMSO shall send a CANCEL request to CMST and shall release all resources reserved for this connection. The CANCEL request shall be as described below. CMSO shall also be prepared to send a BYE message in the case that it receives a final response after sending the CANCEL. CANCEL (CMSO -> CMST... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2 Emergency Call Procedures | A call for emergency services, e.g. 121 or 911, shall follow the procedures given for a basic call, as given in clause 8.4.1, with the following exceptions. As described in clause 7.1, the emergency services telephone number is not an international number and hence cannot be supplied as a global-number. Instead, the lo... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.1 Network Hold Support | Network Hold is an optional capability that provides the PSAP operator with the ability to control when the emergency call is released. If Network Hold is supported, then when the originating party hangs up during an emergency call, the call is not released. Instead, the call is maintained and Network Hold is applied b... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.2 PSAP Operator Ringback | Operator Ringback is a feature that allows the PSAP to alert the originating party in an established emergency call. The type of alerting depends on whether Network Hold is applied or not (i.e. whether the originating party is on-hook or off- hook). If Network Hold is not applied (caller is off-hook), the caller can be... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.2.1 PSAP Operator Ringback while Network Hold not Applied (Caller Off-Hook) | When the PSAP indicates that the caller should be alerted and Network Hold is not in effect, the in-band audible alerting signal can be applied in one of several ways. For example, the PSAP could instruct the MG endpoint to send the audible in-band alerting signal toward the originating party via the established bearer... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.2.2 PSAP Operator Ringback while Network Hold Applied (Caller On-Hook) | When the PSAP indicates that the caller should be alerted while Network Hold is applied, the MGC shall send a re-INVITE request containing an Alert-Info header specifying the type of alerting to be applied and a Priority header containing the value "emergency". On receiving the re-INVITE, CMSO shall process the request... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.3 PSAP CallBack (PSAP Originated Emergency Call) | After an emergency call has ended (due to a caller-initiated disconnect before 200 OK, PSAP forced disconnect, or Network Hold timer timeout), the PSAP operator may wish to re-establish a connection with the emergency caller. In this case, the PSAP initiates a new call towards the original emergency calling party based... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.4 MGC Procedures | |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.4.1 Invite processing | The MGC procedures to support emergency calls differ depending on whether the trunk interface to the PSTN Selective Router is via SS7 ISUP or Multi-Frequency (MF) Trunks. SS7 ISUP Trunks: Both shared and non-shared ISUP trunks may be used to the selective router. When shared facilities are used the MGC shall limit thos... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.4.2 Network Hold processing | The MGC processing of a Network Hold event depends on whether the trunk interface to the PSTN Selective Router is via SS7 ISUP or Multi-Frequency (MF) Trunks. SS7 ISUP Trunks: The MGC shall process Network Hold disconnect requests in accordance with Telcordia GR 1277 [49] (Operator SS7) including the following mappings... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.4.3 PSAP Ringback processing | The MGC processing of a PSAP Ringback event depends on whether the trunk interface to the PSTN Selective Router is via SS7 ISUP or Multi-Frequency (MF) Trunks. SS7 ISUP Trunks: The MGC shall process the operator ringback request in accordance with Telcordia GR 1277 [49] (Operator SS7). On receiving an indication from t... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.2.4.4 PSAP Callback (PSAP Originated Emergency Call) | The MGC shall indicate in the SIP signalling that the PSAP callback call as an emergency call by including a Priority header in the INVITE containing the value "emergency". The method of determining that the call is a PSAP callback call is as follows. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 94 SS7 ISUP Trunks: If an i... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3 CMS Procedures for REFER | The SIP REFER method is described in clause 7.6, with further specification text in clause 7.5. This clause details the procedures that a CMS follows in generating and responding to a REFER request. In the following clauses, CMSI is the CMS that initiated the REFER request, CMSO is the target of the REFER (who also ini... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.1 CMSI Initiates REFER Request | When the REFER is generated within an established call-leg, the call-leg identification (From tag, To tag and Call-ID) shall match those of the call-leg between CMSI and CMSO. The CSeq shall be higher than the value of the last-transmitted request (e.g. the ACK). The Request-URI of the REFER shall be the value of the m... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.2 CMSO Receives REFER | CMSO receives the REFER request and verifies the requirements shown in the previous subclause. If acceptable, it returns a 202 Accepted final response and goes on to send an INVITE to the Refer-To party (see clause 8.4.1.1). If the request is not acceptable, CMSO returns an appropriate 4xx response; 406-Not-Acceptable ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.3 CMSI Receives Final Response to REFER | CMSI stops the transaction timer T3. If the response is 202-Accepted, CMSI waits for notification of the final result of the request. As described below, other events may precede receipt of this notification, in which case CMSI will act on those other events. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.4 CMSI Receives Initial NOTIFY for REFER | Upon receiving the initial NOTIFY for the REFER, CMSI sends a 200-OK to CMSO. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 97 200-OK (CMSI -> CMSO) Header: Requirements On CMSI for Message Generation SIP/2.0 200 OK As described in clause 7.6. Via: From: To: Call-ID: Cseq: Content-Length: Shall be present if the transport p... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.5 CMSO Sends INVITE to Target | CMSO creates an INVITE request based on the contents of the REFER. The Request-URI and To header are populated with the URI from the Refer-To header. Additional headers appended to the Refer-To URI (e.g. Replaces) are copied to the INVITE. If the Refer-To URL did not contain a P-DCS-Billing-Info header, then CMSO shall... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.6 CMSO Sends Final NOTIFY To CMSI | CMSO shall send a NOTIFY request to CMSI when it receives the final response to the INVITE. The NOTIFY request is described in clause 7.5. The format of the message is shown below. NOTIFY (CMSI -> CMSO) Header: Requirements on CMSI for Message Generation NOTIFY URL SIP/2.0 Shall be present. Method shall be NOTIFY. The ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.7 CMSI Receives NOTIFY | When CMSI receives a NOTIFY it matches the From, To and Call-ID headers to an existing call-leg, checks to see that the call-leg has at least one outstanding REFER and verifies that the value of the Cseq parameter in the Event header of the NOTIFY matches the Cseq header of an outstanding REFER. If all of these checks ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.3.8 CMSO Receives Final Response To NOTIFY | CMSO terminates the retransmission timer for the NOTIFY. It takes no other action based on the final response. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.4 CMS handling of Mid-Call Changes | Mid-call changes include call-hold, call-resume, call replacement, operator services and dynamic codec changes. The initiator of a mid-call change in this clause is referred to as CMSI and the recipient of a mid-call change is referred to as CMSR. Another type of mid-call change involves changing the endpoints of sessi... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.4.1 CMSI Initiating Call Hold: re-INVITE/UPDATE(hold) | To place a call on hold, a re-INVITE(hold) or an UPDATE(hold) message is sent on the signalling channel to the party that is to be put on hold. This is a standard SIP re-INVITE or UPDATE request, with an additional "a=sendonly" or "a=inactive" attribute for the media stream in the SDP. The format of the UPDATE message ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.4.2 CMSI Resuming a held call: UPDATE(resume) | The party that placed the call on hold shall be the one to take it off hold. To take a call off hold, a re-INVITE(resume) or an UPDATE(resume) is sent. A re-INVITE/UPDATE(resume) is a re-INVITE/UPDATE(hold) message with the SDP description of the call being reinstated. NOTE 1: If this SDP has changed from the pre-hold ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.4.3 CMSR Receiving Call Hold: UPDATE(hold) and UPDATE(resume) | On receiving an UPDATE(hold), CMSR sends a 200-OK with SDP description to the party requesting the hold and instructs the endpoint to stop sending bearer channel packets. On receiving an UPDATE(resume), which is an UPDATE message with the SDP description of the call being reinstated, the CMS sends the party requesting ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.4.4 SIP Messages for Codec Changes - INVITE/UPDATE(Codec-change) | A codec change can occur automatically when two or more codecs are negotiated in the SDP "m=" line. This does not involve any SIP signalling and hence it is not addressed here. However, changing to one or more codecs that were not negotiated in the SDP requires SIP signalling described below. A signalling message may b... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.4.4.1 Codec Change within Previous Authorization | If the new codec(s) that CMSI wishes to adopt not require additional network resources compared to the codecs included in the SDP of the initial INVITE transaction (or authorized by a subsequent INVITE(codec-change) request), the codec(s) are considered authorized by the network. In this case, CMSI initiating the codec... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.4.4.2 Codec Change Requiring New Authorization | The format of the INVITE message sent by CMSI and the requirements on the header fields checked at the receiving CMS (CMSR) are shown below. INVITE(codec-change) (CMSI->CMSR) Header: Requirements on CMSI for message generation Requirements on CMSR for message checking INVITE URI SIP/2.0 As described in clause 6.12. The... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.5 CMS handling of Call Teardown | To terminate a call, the CMS shall send a BYE message on the signalling channel to instruct the endpoint to stop transmitting bearer data to the other endpoint. It shall also instruct the endpoint to release network resources used for the call. The endpoint that has detected local hangup is denoted by CMSI; the other e... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.6 Sample Implementation of Call Transfer | The user interface to initiate call transfer and ad hoc conferencing is fundamentally different for NCS MTAs as opposed to intelligent MTAs. The procedures in the present document assume NCS-controlled MTAs; intelligent MTAs are outside the scope of the present document. In the procedural description that follows, the ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.7 Sample Implementation of Ad-hoc Conference | An ad-hoc conference is formed when the Initiator has two simultaneous active calls, one to Party B and one to Party C and desires to connect them together. The beginning of an ad-hoc conference is as described in steps 1 to 5 and figures 15 to 18 in clause 8.4.6. The difference comes in the next step: 6) The Initiator... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.8 Automatic Recall and Callback | In support of Automatic Recall and Callback, CMSS supports the extensions defined in clauses 7.16 and 6.20.9. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.8.1 CMSO Sends INVITE to Target | When a user invokes an AR or AC call, CMSO shall follow the procedures given for a basic call, as given in clause 8.4.1, with the following exceptions. CMSO shall populate the request URI of the INVITE request based on the stored last dialled address for Auto Callback, or the stored address for the last call received f... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.8.2 CMSO Sends SUBSCRIBE to Target | On receiving a 486-Busy-Here or 600-Busy-Everywhere response to an AC/AR INVITE request (defined in clause 8.4.8.1), CMSO shall initiate a timer that limits the overall duration of the AC/AR campon attempt. CMSO shall then establish a subscription to the dialog event package of the target endpoint, by sending a SUBSCRI... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.8.3 CMST Sends NOTIFY to CMSO | Upon receiving a valid SUBSCRIBE request, CMST shall send an immediate NOTIFY with the dialog state of the target subscriber. Whenever the dialog state of the target subscriber changes, CMST shall send an updated NOTIFY with the new dialog state. The NOTIFY request is described in clauses 7.5 and 7.16. CMST shall encod... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.8.4 INVITE from IPCablecom to PSTN | If MGCT receives an INVITE from CMSO with a Call-Info header declaring "purpose=answer_if_not_busy", then MGCT shall take the following actions: • Send a TCAP Initial Query message to the PSTN network, requesting the busy/idle status of the target, according to the Originating SPCS procedures defined in GR 227 [47]. • ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.8.5 Initial Query Request from PSTN to IPCablecom | When the MGC receives a TCAP Initial Query message according to the terminating SPCS procedures specified in GR 227 [47] and functioning as CMSO as specified in clauses 8.4.8.2 and 8.4.8.3, it shall send: • A SUBSCRIBE request to the target's dialog event package as specified in clause 8.4.8.2. In this case, the reques... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.9 Message Waiting Indicator | In support of message waiting indicator, CMSS supports the extensions defined in clause 7.10. If a subscriber's MTA is controlled by a CMS that is different from the one controlling the subscriber's messaging system (e.g. voice-mail), then CMS-to-CMS interaction is required in order to communicate the message waiting i... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.9.1 CMSI Sends SUBSCRIBE to CMSR | To subscribe to the message waiting status of a subscriber, a SUBSCRIBE message is sent to the CMS of the subscriber's messaging system. This is a standard SIP SUBSCRIBE [9] request using the "message-summary" event package defined in clause 7.10. The format of the SUBSCRIBE message sent by the initiating CMSI and the ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.9.2 CMSR Sends NOTIFY to CMSI | CMSR then sends an immediate NOTIFY with the message-waiting status of the subscriber. Whenever the message-waiting status of the subscriber changes, CMSR sends an updated NOTIFY with the message-waiting status. The NOTIFY request is described in clauses 7.5 and 7.10. The format of the message is shown below. ETSI ETSI... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.10 SDP Interworking | CMSS compliant implementations need to support rules and procedures to allow for interworking between E-MTAs, MGs and UEs. This is due to the protocol differences between NCS/TGCP and SIP and the use of different SDP attributes. Specifically: • NCS/TGCP and SIP - NCS and TGCP are master/slave protocols that do not use ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.10.1 Offer/Answer Requirements for Call Hold | Call hold can be invoked by either the local or remote endpoint. When invoked at the local endpoint, the CMS can choose whether it wants to update the session and inform the remote endpoint of the hold invocation. When invoked at the remote endpoint, the local CMS needs to be prepared to receive a re-INVITE with a numb... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.