hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.2.3 Media Setup Procedure | On sending a SETUP request, the UE shall populate the header fields as follows: - RTSP URL header shall be set to the a=control parameter if present in the answer to the DESCRIBE sent by the MCF. If not present, RTSP URL shall be set to the corresponding media RTSP URL which has been obtained from the SSF data, or from... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.2.4 Media Playback Initiation Procedure | After SETUP request has been acknowledged as successful, UE shall start the playback of the content by sending an RTSP PLAY request. The UE shall populate the header fields as follows: - RTSP URL header shall be set to the a=control parameter if present in the answer to the DESCRIBE sent by the MCF. If not present, RTS... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.2.5 Media Playback Modification Procedure | Upon a request to modify playback the UE shall send an RTSP PLAY message with a request to modify the position, speed and/or direction of playback. The UE changes the direction and/or speed of playback by including a Scale header or change the position of playback by including a Range header. ETSI ETSI TS 183 063 V2.1.... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.2.6 Media Teardown Procedure | On sending TEARDOWN request, the UE shall populate the header fields as follows: - RTSP URL header shall be set to the a=control parameter if present in the answer to the DESCRIBE sent by the MCF. If not present, RTSP URL shall be set to the corresponding media RTSP URL which has been obtained from the SSF data, or fro... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.2.7 Handling of Media Events | Upon the reception of the RTSP ANNOUNCE with indication of end-of-stream the UE may take relevant actions to handle the end of stream event (e.g. Terminating session, rewinding the media stream etc.). The UE shall respond with a 200 OK. In case of BC sessions with trick-play, if the UE receives an RTSP ANNOUNCE request... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2 Media Control Function (MCF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.1 Procedures for RTSP playback control (Method 1) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.1.1 Introduction | The MCF shall support the following RTSP methods for RTSP playback control: • PLAY (UE to MCF). • PAUSE (UE to MCF). • GET_PARAMETER (UE to MCF). ETSI ETSI TS 183 063 V2.1.0 (2008-06) 58 • SET_PARAMETER (UE to MCF). • ANNOUNCE (MCF to UE). • OPTION (UE to MCF). All other methods that the MCF does not support will resul... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.1.2 Media Playback Initiation Procedure | Upon successful RTSP PLAY request the MCF responds with a 200 OK message except for the cases as follows: • If the requested content is not ready for playing, the MCF shall reply with an RTSP error code 404 Not Found. The contents of the 200 OK response shall be as follows: - CSeq shall be set to the same value as that... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.1.3 Media Playback Modification Procedure | Upon successful RTSP PLAY or PAUSE request the MCF responds with a 200 OK message. The contents of the 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated. - RTP-... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.1.4 Media Playback Information Retrieval and Setting Procedure | Upon successful RTSP GET_PARAMETER or SET_PARAMETER request the MCF responds with a 200 OK message with the requested values or with the successful setting of a parameter. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.1.5 Handling of Media Events | Upon receipt of the end-of-stream indication from MDF, MCF may send an RTSP ANNOUNCE to the UE with an indication that the end-of-stream has been reached. The "Notice" header shall be included with the notice code value set to "2101 End-of-Stream Reached". NOTE: The header and code are based draft-stiemerling-rtsp-anno... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2 Procedure for content control (Method 2) | The MCF shall act as a media server as defined in RFC 2326 [8]. RTSP header fields shall conform to TS 102 034 [3], clause 6.3.2. The MCF shall not redirect the RTSP methods using either the REDIRECT method or Redirection status code (3xx). NOTE: It is recommended that the MCF does not perform redirection to avoid misa... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2.1 Introduction | After CoD session setup, RTSP as defined in RFC 2326 [8] is used to control media delivery. It includes media setup, media control and media teardown. RTSP header fields shall conform to TS 102 034 [3], clause 6.3.2. The MCF shall support the following RTSP methods: • DESCRIBE (UE to MCF). • SETUP (UE to MCF). • PLAY (... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2.2 Media Description Procedure | Upon successful RTSP DESCRIBE request the MCF responds with a 200 OK message. The DESCRIBE response sent by the MCF shall have: • Content-type header set to "application/sdp"; or • Content-type header set to "text/xml" and Content-encoding set to "utf8", conforming to TS 102 034 [3], clause 6.3.1.2. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2.3 Media Setup Procedure | Upon successful RTSP SETUP request the MCF responds with a 200 OK message. The contents of 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the SETUP request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated. - Session he... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2.4 Media Playback InitiationControl Procedure | Upon successful RTSP PLAY request the MCF responds with a 200 OK message. The contents of the 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated. - RTP-Info head... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2.5 Media Playback Modification Procedure | Upon successful RTSP control (PLAY, PAUSE) request the MCF responds with a 200 OK message. The contents of the 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2.6 Media Teardown Procedure | Upon successful RTSP TEARDOWN request the MCF responds with a 200 OK message. The contents of 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the TEARDOWN request. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.2.2.7 Handling of Media Events | Upon receipt of the end-of-stream indication from MDF, MCF shall send an RTSP ANNOUNCE to the UE with an indication that the end-of-stream has been reached. The "Notice" header shall be included with the notice code value set to "2101 End-of-Stream Reached". NOTE: The header and code are based draft-stiemerling-rtsp-an... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8 Procedures using IGMP/MLD for IMS-based IPTV | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.1 User Equipment (UE) | If IPv4 is used for the transport, the UE shall support IGMPv3 as described in RFC 3376 [28]. If IPv6 is used for the transport, the UE shall support MLDv2 as described in RFC 3810 [29]. ETSI ETSI TS 183 063 V2.1.0 (2008-06) 61 Backward compatibility rules between the UE and the Transport Function have to be done confo... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.1.1 Procedure for Service Selection | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.1.1.1 Procedure to start receiving service selection information | When the UE wishes to receive service selection information from the SSF in multicast mode, it shall send an IGMPv3 unsolicited Membership Report or a MLDv2 Multicast Listener Report Message to the Access Node as specified in RFC 3376 [28] and RFC 3810 [29]. The IGMPv3/MLDv2 request shall be populated as follows: • the... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.1.1.2 Procedure to stop receiving service selection information | When the UE wants to stop receiving service selection information from an SSF in multicast mode, it shall send an IGMP v3 Membership Report Message or MLD v2 Multicast Listener Report Message for leaving a multicast group. The IGMPv3/MLDv2 request shall be populated as follows: • the type shall be set to 0x22 "v3 Membe... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.1.2 Procedure for BC service | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.1.2.1 Procedure for joining a BC service | After the BC session initiation procedure, when the UE wishes to join a particular BC service, an IGMP unsolicited v3 Membership Report or a MLD v2 Multicast Listener Report Message to the Access Node as specified in RFC 3376 [28] and RFC 3810 [29]. The IGMPv3/MLDv2 request shall be populated as follows: • the type sha... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.1.2.2 Procedure for leaving BC service | When the UE wants to stops receiving content delivery data from the previously selected BC service, it shall send an IGMPv3 Membership Report Message or MLDv2 Multicast Listener Report Message for leaving a multicast group. The IGMPv3/MLDv2 request shall be populated as follows: • the type shall be set to 0x22 "v3 Memb... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.2 Transport Functions | For IPv4 multicast IPTV service distribution, the network transport functions shall support minimally IGMPv2 or higher. The use of IGMPv3 is recommended, in which case the backwards compatibility rules of RFC 3376 [28], clause 7 shall apply. For IPv6 multicast IPTV service distribution, the network transport functions ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.2.1 Receiving IGMP/MLD request corresponding to a join operation | When receiving an IGMP/MLD request corresponding to a join, the ECF/EFF shall check, based on traffic policies, whether the sender of the request is allowed to join the targeted multicast group. If the multicast group is not allowed the ECF/EFF shall ignore the UE request. If the multicast group is allowed, the ECF/EFF... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 8.2.2 Receiving IGMP/MLD request corresponding to a leave operation | When Receiving IGMP/MLD request corresponding to a leave operation, the ECF/EFF shall stop forwarding data to the UE corresponding to the multicast group indicated in the Leave operation and delete the subscription of the UE IP address to this group. If pull model is used, the ECF/EFF shall inform the RACS of the Leave... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9 Procedures using DVBSTP for IMS-based IPTV | This clause applies when using DVB-IPTV multicast delivery for service and content guide discovery. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.1 User Equipment (UE) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.1.1 Procedure for Service Selection | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.1.1.1 Request of DVB Service Discovery & Selection data | In the DVB push model of multicast delivery of DVB SD&S data, the UE shall subscribe to the multicast DVBSTP streams identified within the response from the SDF. Refer to clause 8 for multicast connection mechanism. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.1.1.2 Request of DVB Broadband Content Guide | In the DVB push model of multicast delivery of a DVB BCG data, the UE shall subscribe to the multicast DVBSTP streams identified within the response from the SDF or within the Service Selection information returned by the SSF. Refer to clause 8 for multicast connection mechanism. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.1.1.3 Use of Service Selection information | The UE uses service selection information as defined in clause 6.1.1.5. ETSI ETSI TS 183 063 V2.1.0 (2008-06) 65 |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.2 Service Selection Function (SSF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.2.1 Procedure for Service Selection | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.2.1.1 Delivery of DVB Service Discovery and Selection data | In the DVB push model of multicast delivery of DVB SD&S data, the DVBSTP protocol shall be used conforming to TS 102 034 [3], clause 5.4.1. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 9.2.1.2 Delivery of DVB Broadband Content Guide | In the DVB push model of multicast delivery of a DVB BCG data, the DVBSTP protocol shall be used conforming to TS 102 539 [13], clause 4.1.2.2.1. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10 Procedures using FLUTE for IMS-based IPTV | NOTE: This clause applies when using OMA BCAST multicast delivery for service provider and guide discovery. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.1 User Equipment (UE) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.1.1 Procedure for Service Selection | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.1.1.1 Request of OMA BCAST service discovery and selection data | In the OMA BCAST push model of multicast delivery of OMA BCAST ESG provider discovery data, the UE shall subscribe to the FLUTE streams identified within the response from the SDF, conforming to clause 9.2 in TS 102 471 [4] and clause 6 of TS 102 472 [5]. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.1.1.2 Request of OMA BCAST Service Guide | In the OMA BCAST push model of multicast delivery of an OMA BCAST ESG, the UE shall subscribe to the FLUTE streams identified within the response from SDF or within the Service Selection information returned by the SSF, conforming to TS 102 471 [4], clause 8.1, OMA-TS BCAST_DVB_Adaptation-V1_0 [6], clause 6.3.5 and OMA... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.1.1.3 Use of Service Selection information | The UE uses service selection information as defined in clause 6.1.1.5. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.2 Service Selection Function (SSF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.2.1 Procedure for Service Selection | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.2.1.1 Delivery of OMA BCAST service discovery and selection data | In the OMA BCAST push model of multicast delivery of OMA BCAST ESG provider discovery data, the FLUTE protocol shall be used, conforming to TS 102 471 [4], clause 9.2 and OMA-TS-BCAST_DVB_Adaptation-V1_0, clause 6.3.5 [6]. ETSI ETSI TS 183 063 V2.1.0 (2008-06) 66 |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 10.2.1.2 Delivery of OMA BCAST Service Guide | In the OMA BCAST push model of multicast delivery of an OMA BCAST ESG, the FLUTE protocol shall be used, conforming to TS 102 471 [4], clause 8.1, OMA-TS-BCAST_DVB_Adaptation-V1_0 [6], clause 6.3.5 and OMA-TS-BCAST_Service_Guide-V1_0 [5], clause 5.4. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11 Procedures using UDP/RTP for IMS-based IPTV | The IPTV content is transported over the IP network. In order to do so, several encapsulation are possible: • MPEG2TS: the content is encapsulated into MPEG2TS packets: - MPEG2TS over UDP: the MPEG2TS packets are directly transported over the UDP layer. - MPEG2TS over RTP: the MPEG2TS packets are transported over the R... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.1 User Equipment (UE) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.1.1 Procedure for Real-Time Transport | The UE shall support at least one of the following transport technologies: • MPEG2TS encapsulation. • Direct RTP transport. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.1.1.1 Transport using MPEG2TS | The UE may be able to receive the content encapsulated in MPEG2TS packets. When using the MPEG2TS encapsulation technology, the UE shall support both: • MPEG2TS over UDP conforming to TS 102 034 [3], clause 7.1.2. • MPEG2TS over RTP conforming to TS 102 034 [3], clause 7.1.1 excluding clause 7.1.1.1. - As specified in ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.1.1.2 Transport using direct RTP encapsulation | The UE may be able to receive the content directly over the RTP layer (e.g. H264 over RTP). As specified in ES 283 003 [20], it is possible to negotiate RTCP bandwidth - and thus to control UE receiver report generation - for unicast IPTV services during SIP session setup. NOTE 1: Handling of RTCP Receiver reports for ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.1.2 Procedure for Real-Time Transport Error Correction | The UE may support a transport error correction mechanism. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.1.2.1 Unidirectional Transport Error Correction | When unidirectional transport error correction is used, the UE shall be able to receive an application Layer FEC, conforming to TS 102 034 [3], annex E. NOTE: Only the base layer of the DVB-IP AL-FEC is supported in the present document, the enhancement layer support is out of scope. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.2 Media Delivery Function (MDF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.2.1 Procedure for Real-Time Transport | The MDF shall send the content using one of the following transport technologies: • MPEG2TS encapsulation. • Direct RTP transport. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.2.1.1 Transport using MPEG2TS | The MDF may be able to send the content encapsulated into MPEG2-TS.In that case, one of the following shall be used: • The transport of the IPTV content within MPEG2TS layer over RTP shall be done conforming to TS 102 034 [3], clause 7.1.1. • The transport of the IPTV content within MPEG2TS layer over UDP shall be done... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.2.1.2 Transport using direct RTP encapsulation | The MDF may be able to send the content directly over the RTP layer (e.g. H264 over RTP). |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.2.2 Procedure for Real-Time Transport Error Correction | The MDF may support a transport error correction mechanism. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 11.2.2.1 Unidirectional Transport Error Correction | For unidirectional transport error correction the MDF shall use an application Layer FEC mechanism, conforming to TS 102 034 [3], annex E. NOTE: Only the base layer of the DVB-IP AL-FEC is supported in the present document, the enhancement layer support is out of scope. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 12 IPTV user profile schema | The IPTV user profile is described by an XML document. This XML document complies with the XML schema defined in annex C. Although it is not explicit in the XML schema described in annex C, the IPTV user profile must comprise at least one BC profile or CoD profile. ETSI ETSI TS 183 063 V2.1.0 (2008-06) 68 The "Global S... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 13 IPTV service action data schema | For convenience purposes, each object class of the IPTV service action data is described by a separate XML documents. Those XML document comply with the XML schema defined in annex D. Although they are defined as optional in the XML schema described for "NPVR items" in annex D, the "BCServiceId", "RecordStartDate" and ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 1 Scope | The present document specifies the stage three protocol description of the signalling interworking between ISDN DSS1 protocol and SIP based on the concatenation of ETSI TS 129 163 [1], ETSI TS 124 229 [5] with ETSI EN 300 899-1 [2]. The concatenation method describes only the SIP/ISDN parameter mapping without ISUP pro... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 2 References | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 3 Definition of terms, symbols and abbreviations | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 3.1 Terms | For the purposes of the present document, the following terms apply: en bloc receiving: procedure, used in call establishment of an incoming call, to enable the network to send called party number digits to the user in a single message NOTE: See ETSI EN 300 403-1 [29]. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 13 en bloc s... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 3.2 Symbols | Void. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement ACR Anonymous Call Rejection AFI Authority and Format Identifier AGCF Access Gateway Control Function AGW Access GateWay AOC Advice Of Charge AOC-D Advice Of Charge During the call AOC-E Advice Of Charge at the End of the c... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 4 General | The present document describes the requirements for implementing commonly deployed Integrated Service Data Network (ISDN) basic call and supplementary services using the IP Multimedia Subsystem (IMS) and IMS-based PSTN/ISDN Emulation Subsystem (PES) architecture: • ISDN terminals are connected to Voice over IP GateWay ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5 Interworking for IMS simulation/emulation services | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1 Basic Call | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1 Actions at the Outgoing AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.1 Sending of the Initial INVITE | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.1.0 Interworking of DSS1 SETUP or INFO into SIP INVITE request | After initiating the normal incoming call establishment procedures, determining the end of address signalling and selecting to route the call to the IMS domain, the originating VGW/AGCF shall send the initial INVITE. As a network option, the originating VGW/AGCF may send INVITE requests without determining the end of a... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.1.1 En-bloc sending according to ETSI EN 300 403-1, clause 5.1.1 | If en-bloc sending is used, the SETUP message contains the complete called number information. The called party number information is included in the called party number information element possibly completed by the called party subaddress information element. The network shall send a CALL PROCEEDING message to the use... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.1.2 Bearer capability mapping | The "information transfer capability" code point of the bearer capability information element in the SETUP message shall be mapped to the SDP in SIP according to table 5.1.1.1.2-1. Table 5.1.1.1.2-1: Coding of the BC received SETUP→ INVITE→ Bearer capability information element Coding of SDP media description lines fro... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.1.4 Request URI/To header field | Table 5.1.1.1.4-1: Mapping DSS1 called party number to SIP Request-URI and To header field SETUP INVITE Called party Number Request-URI and To header field Type of number Unknown Dialled strings E. 164 Number format LN (local number) Option a) sip: dialled digits@homehostportion (see note 2) Option b) sip: dialled digi... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.2 Receipt of a Provisional Response 18x | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.2.0 General statement to provisional responses | The SDP answer is described in annex B. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.2.1 180 Ringing response | 5.1.1.2.1.0 Basic procedure Depending on the following three cases, the AGCF/VGW shall send an ALERTING message across the user-network interface to the calling user, as described in table 5.1.1.2.1.0-1. The reception of the first 180 Ringing response without a P-Early-Media header (authorizing early media); or the rec... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.2.2 Receipt of the 183 (Session Progress) response | 5.1.1.2.2.0 General description Once all the following sub-conditions have been met: • if the AGCF/VGW has received the first 183 Session Progress that includes a P-Early-Media header (indicating authorization of early media); and • SDP preconditions are not used or applicable SDP preconditions have been met. The AGCF/... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.3 Receipt of the 200 OK INVITE | Upon receipt of a 200 OK INVITE and the 200 OK INVITE does not contain the from-change tag in the supported header, the AGCF/VGW shall send a CONNECT message across the user-network interface to the calling user. If the from-change tag in the supported header is contained in the 200 OK INVITE, the applicable procedures... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.4 Receipt of (BYE or Final Response) | Table 5.1.1.4-1: Receipt (BYE or Final Response) ←DISCONNECT ←BYE/3xx/4xx/5xx/6xx Cause information element Reason header Cause value No. X (see notes 1 and 2) cause value No. X Progress indicator No. 8 (see note 3) (In-band information or appropriate pattern now available) NOTE 1: If the cause value received in the Re... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.5 Sending of (BYE or CANCEL) | Table 5.1.1.5-1: Call clearing from the user DISCONNECT, RELEASE RELEASE COMPLETE→ BYE/CANCEL→ Cause information element Reason header Cause value No. X cause value No. X (see notes 1 and 2) NOTE 1: If the cause value received in the DSS 1 message is unknown in ISUP, the unspecified cause value of the class is sent. NO... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.1.6 Use of Overlap signalling (Optional) | If overlap signalling is supported between the AGCF/VGW and the originating PES Application Server the overlap signalling method used, either the multiples INVITES method or the IN-Dialog method as described within annexes G and H is dependent on national or network operator option. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.2 Actions at the Incoming AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.2.1 Sending of the SETUP message | On reception of a SIP INVITE, the AGCF/VGW shall send a SETUP message. An AGCF/VGW shall support both incoming INVITE requests containing SIP preconditions and 100rel extensions in the SIP Supported or Require headers, and INVITE requests not containing these extensions. If the SDP in the received INVITE request contai... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.2.2 Sending of the 18x from the destination VGW/AGCF | Table 5.1.2.2-1: Interworking of CALL PROCEEDING/PROGRESS ←Message on the SIP ←Message sent to the DSS 1 183 Session Progress CALL PROCEEDING/PROGRESS Progress indicator information element PSTN XML with ProgressIndicator Value of PI and PSTN XML ProgressIndicator No. 7 (see note 2) Number Value of PI PSTN XML Progress... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.2.3 Sending of the 200 OK INVITE | Upon receipt of the CONNECT message, the destination AGCF/VGW shall: • stop the sending of the awaiting answer indication (if any); • send the 200 OK INVITE to the preceding entity. NOTE: Tones and announcements can as well be provided by the MRFC. The 200 OK INVITE is coded as follows: OPTIONAL PARAMETERS P-Asserted-I... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.2.4 Receipt of BYE/CANCEL | Table 5.1.2.4-1: Receipt of BYE/CANCEL BYE/CANCEL→ DISCONNECT → Reason header Cause information element Cause No. X Cause value No. X (see notes 1 and 2) NOTE 1: If the Reason value received in the Release message (BYE/CANCEL) is unknown in DSS 1, the unspecified cause value of the class is sent. NOTE 2: Some supplemen... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.2.5 Sending of BYE/4xx/5xx | If a DISCONNECT, RELEASE or RELEASE COMPLETE message is received and a final response (i.e. 200 OK (INVITE)) has already been sent, the I-AGCF/VGW shall send a BYE message. "The Cause value sub-field received in the DISCONNECT, RELEASE or RELEASE COMPLETE message shall be mapped to the cause value of the Reason header ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.1.2.6 Sending of the DSS1 INFO (Optional) | If overlap signalling is supported between the AGCF/VGW and the terminating PES Application Server the overlap signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annexes D and E is dependent on national or network operator option. ETSI ETSI TS 183 036 V3.7.1 (2021-02... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2 Supplementary services | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.0 General statement to supplementary service interworking | This clause discusses the impact of supplementary services on the AGCF/VGW. Table 5.2.0-1 lists the supplementary services covered and the corresponding references to the PES simulation service specifications. Table 5.2.0-1: PES Simulation Supplementary Services Supplementary Service Reference Communication Hold (HOLD)... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.