hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1 Communication Hold (HOLD) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.1 Actions at the Incoming AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.1.1 Notification received from the network | Table 5.2.1.1.1-1: HOLD notification INVITE/UPDATE→ NOTIFY→ SDP: a=sendonly/inactive Notification indicator information element Notification description sendonly/inactive 111 1001 Remote hold sendreceive 111 1010 Remote retrieval |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.1.2 Invocation at coincident S and T reference point | Table 5.2.1.1.2-1: HOLD invocation ←INVITE/UPDATE ←Message received from the DSS 1 SDP: a=sendonly/inactive sendonly/inactive HOLD sendreceive RETRIEVE ETSI ETSI TS 183 036 V3.7.1 (2021-02) 43 |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.1.3 Notification received at T reference point | A HOLD notification may be received at T reference point in the active phase of the call. Table: 5.2.1.1.3-1: Receipt of a HOLD notification from a private network ←INVITE/UPDATE ←NOTIFY SDP: a=sendonly/inactive Notification indicator information element Notification description sendonly/inactive 111 1001 Remote hold s... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.2 Actions at the outgoing AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.2.1 Notification received from the network | Table 5.2.1.2.1-1: Receipt of HOLD notification from the network ←NOTIFY ←INVITE/UPDATE Notification indicator information element SDP: a=sendonly/inactive Notification description 111 1001 Remote hold sendonly/inactive 111 1010 Remote retrieval sendreceive |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.2.2 Invocation at coincident S and T reference point | Table 5.2.1.2.2-1: HOLD invocation INVITE/UPDATE→ Message received from the DSS 1 → SDP: a=sendonly/inactive HOLD sendonly/inactive RETRIEVE sendreceive |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.1.2.3 Notification received at T reference point | A HOLD notification may be received at T reference point in the active phase of the call. Table 5.2.1.2.3-1: Receipt of a HOLD notification from a private network NOTIFY→ INVITE/UPDATE→ Notification indicator information element SDP: a=sendonly/inactive Notification description 111 1001 Remote hold sendonly/inactive 11... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.2.1 Actions at the incoming AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.2.1.0 General statement to TIP | If the Initial INVITE is received and the Supported header contains the "from-change" tag, then the P-Asserted-Identity in the 200 OK INVITE or UPDATE request and the changed From header in the UPDATE are sent as described in tables 5.2.2.1.1-1 and 5.2.2.1.1-2. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.2.1.1 Connected Line Identification Presentation (COLP) | The AGCF/VGW shall sent first a 200 OK INVITE including an option tag "from-change" and after then an UPDATE request as shown in table 5.2.2.1.1-1 according the rules of IETF RFC 4916 [50]. 200 OK and UPDATE is sent on the Mw interface Table 5.2.2.1.1-1: Connected number interworking applies at Mw interface ←200 OK INV... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.2.1.2 Connected Line Identification Restriction (COLR) | Table 5.2.2.1.2-1: Coding of the Privacy header field ←200 OK INVITE ←CONNECT Privacy header field Connected number information element Presentation indicator "id", "header", "user" Presentation restricted No Privacy header Absent "none" Presentation allowed ETSI ETSI TS 183 036 V3.7.1 (2021-02) 47 |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.2.2 Actions at the outgoing AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.2.2.1 Connected Line Identification Presentation (COLP) | NOTE: Depending on national regulations, some networks may define categories of subscribers that have the ability to override the presentation restriction and have the connected party's ISDN number, and subaddress information (if any) presented (e.g. the police). The ability to override the presentation restriction and... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.2.2.2 Connected line identification restriction (COLR) | See table 5.2.2.2.1-1. 5.2.3 Calling line Identification Presentation (CLIP)/Calling line Identification Restriction (CLIR) |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.3.1 Actions at the incoming AGCF/VGW | Table 5.2.3.1-1: Mapping of SIP From/P-Asserted-Identity/ Privacy header fields to CLI parameters INVITE→ SETUP→ P-Asserted-Identity From header Privacy Coding of the calling party number information element Absent Value not significant (see note) No Privacy header No Calling number IE Absent "Anonymous" <sip:anonymous... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.3.2 Actions at the outgoing AGCF/VGW | Actions at the Gm interface Table 5.2.3.2-1: Mapping CLI parameters to SIP header fields - Gm interface SETUP→ INVITE→ Presentation Restriction Indicator P-Preferred-Identity header field From header field: Privacy header field Privacy value Presentation restricted Addr-spec is derived from Calling Party Number paramet... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.4 Conference calling (CONF) | This service is for further study. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 57 |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.5 Communication Diversion Services (CDIV) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.5.0 General information regarding the service | As a network option the Activation, Deactivation and Interrogation of call forwarding services is performed using service code commands as described in ETSI EN 300 207-1 [34] (ISDN; Diversion supplementary services) and ETSI EN 300 196-1 [25] (ISDN; Generic functional protocol for the support of supplementary services)... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.5.1 Actions at the Outgoing AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.5.1.1 Reception of a "call is diverting" notification | 5.2.5.1.1.0 General clarification According to ETSI TS 124 604 [8], the 181 Being Forwarded may be received. 5.2.5.1.1.1 First diversion The latest history-entry, representing the diverted-to-number, contained in the History-Info header is stored. A notification of diversion is sent to the calling user as shown in tabl... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.5.1.2 Evaluation of History-Info header | If a backward message (provisional response or 200 OK) is received containing a History-Info header and there is no privacy header is included in the URI of the latest history-entry: • it has been determined, according to ETSI TS 124 604 [8], that the notification of diverted-to number is allowed, a redirection number ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.5.1.3 Procedures at the T reference point | When the AGCF/VGW receives a SETUP containing a Facility information element including a DivertingLegInformation2 invoke component (ETSI EN 300 207-1 [34], clause 10.4.1), an INVITE is sent containing a History-Info header. Table 5.2.5.1.3-1: Mapping of the DivertingLegInformation2 invoke component into the History-Inf... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.5.2 Actions at the incoming AGCF/VGW | 5.2.5.2.1 Interworking at the AGCF/VGW where a call is diverted within or beyond the private ISDN (T reference point) When the AGCF/VGW receives a DSS1 PROGRESS or ALERTING message, a Provisional Response is sent. When a FACILITY message is received containing a DivertingLegInformation1 invoke component, a 181 Provisio... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.6 MCID | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.6.1 Actions at the Outgoing AGCF/VGW | There is no interworking requirement relating to the Malicious Call Identification (MCID) supplementary service. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.6.2 Actions at the incoming AGCF/VGW | There is no interworking requirement relating to the Malicious Call Identification (MCID) supplementary service. Invocation of the service To invoke the MCID supplementary service, the called user shall send a McidRequest invoke component carried by a Facility information element in a FACILITY message. This invocation ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7 Explicit Communication Transfer (ECT) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.1 Actions at the Outgoing AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.1.0 General information regarding the service | For this service, the separation "incoming call" and "outgoing call" does not apply. This clause describes the interworking at the AGCF/VGW (i.e. the exchange where the served user is connected to). To simulate ECT in the IMS, the Consultative Transfer is applicable. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.1.1 Coincident S and T reference point | 5.2.7.1.1.1 Service invocation The invocation of ECT in the alerting state should be rejected by the AGCF/VGW. Table 5.2.7.1.1.1-1: ECT invocation Message received from the served user (user A) REFER FACILITY→ Facility information element EctExecute invoke component or ExplicitEctExecute invoke component The request UR... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.1.2 T reference point | 5.2.7.1.2.1 Service invocation Receipt of a notification from the access: Table 5.2.7.1.2.1-1: Receipt of a notification from the access Message received from the access Message sent to the network FACILITY→ Facility information element REFER → EctInform invoke component Alerting No mapping FACILITY→ Facility informati... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.2 Actions at the incoming AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.2.0 General information regarding the service | For this service, the separation "outgoing call" and "incoming call" does not apply. This clause describes the interworking at the O/I-AGCF/VGW (i.e. the AGCF/VGW where the remote user(s) is(are) connected to). |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.2.1 Coincident S and T reference point | 5.2.7.2.1.1 Messages received from the network 5.2.7.2.1.1.1 Receipt of an INVITE/UPDATE message The ECT simulation service is performed as described in ETSI TS 183 029 [36] with the additions and clarifications described in ETSI TS 183 028 [32] in special REFER handling procedures. Upon receipt of an INVITE or UPDATE:... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.7.2.2 T reference point | 5.2.7.2.2.1 Service invocation: Messages received from the network 5.2.7.2.2.1.1 Receipt of an INVITE/UPDATE Upon receipt of an INVITE or UPDATE, two cases are possible: a) INVITE the corresponding remote ECT user is in alerting state NOTE 1: This interworking is applicable to the user in "active call state, call held ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.8 Subaddressing (SUB) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.8.0 General information regarding the service | The Sub-address (SUB) service allows the called (served) user to expand the addressing capacity beyond the one given by the E.164 user number. Subaddressing (SUB). The coding rules according IETF RFC 3966 [47] are not supporting the Type of subaddress (NSAP and user specified) as defined in ISDN (Recommendation ITU-T Q... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.8.1 Actions at the Outgoing AGCF/VGW | Table 5.2.8.1-1: SIP Header information for subaddressing mapping at the I-AGCF/VGW contained in the INVITE SETUP→ INVITE→ Called party sub-address To header Source component value Type of subaddress Octet 4 AFI Source SIP header field and component Derived value of parameter field NSAP 000 AFI x50 IA5 To header isub p... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.8.2 Actions at the incoming AGCF/VGW | The called party subaddress information element received in the isub parameter of the To header of the INVITE (see IETF RFC 3966 [47]) is transferred transparently in the SETUP message. The number type value is a network option, NSAP is recommended. Table 5.2.8.2-1: Sending of the called party subaddress (SUB) SETUP ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.9 Closed User Group (CUG) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.9.0 General information regarding the service | An XML element containing the identification of the closed user group transferred in the INVITE between two AS is described in ETSI TS 124 654 [62]. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.9.1 Actions at the Outgoing AGCF/VGW | CUG checks at the originating Application Server and determination of the type of call request in correlation with the CUG information received from the calling user in the SETUP message and the CUG attributes of the calling user are described in table 4 of ETSI EN 300 138-1 [21] or for IMS implementations ETSI TS 124 ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.9.2 Actions at the incoming AGCF/VGW | CUG checks at the destination Application Server and determination of the type of call request in correlation with the CUG information received in the Initial INVITE message and the CUG attributes of the called user are described in ETSI TS 124 654 [62]. The mapping of the CUG information in the call setup sent to the ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10 User to User Service (UUS) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.0 General information regarding the service | The coding of the User-user information element is described within ETSI EN 300 286-1 [38]. The User-to-User header is defined within draft-johnston- sipping-cc-uui-02.txt [i.1]. The content of the uuidata field of the User-to-User header shall start with the first octet being the protocol discriminator and followed by... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.1 Actions at the Outgoing AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.1.1 Service 1 (UUS1) implicit | Service 1 may be requested implicitly by the presence of the user-user information element in the SETUP message which is mapped into the user-to-user information parameter of the initial INVITE. Table 5.2.10.1.1-1: Implicit UUS1 transfer DSS 1 messages SIP messages SETUP→ INVITE→ User-user information element Protocol ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.1.2 Service 1 (UUS1) explicit | Table 5.2.10.1.2-1: Explicit UUS1 invocation SETUP→ Content Facility information element UserUserService invoke component Service 1 preferred User-user information element Facility information element UserUserService invoke component Service 1 required User-user information element A service 1 explicit request preferre... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.1.3 Service 2 | Table 5.2.10.1.3-1: UUS2 invocation SETUP→ SIP messages Content Facility information element UserUserService invoke component Service 2 preferred Facility information element UserUserService invoke component Service 2 required A service 2 is rejected as described below: Service 2 rejection Rejection initiated by the O-... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.1.4 Service 3 | Table 5.2.10.1.4-1: UUS3 invocation SETUP→ SIP messages Content Facility information element UserUserService invoke component Service 3 preferred Facility information element UserUserService invoke component Service 3 required A service 3 request during call setup is rejected as described below. Table 5.2.10.1.4-2: UUS... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.2 Actions at the incoming AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.10.2.1 Service 1 (UUS1) implicit | Service 1 may be requested implicitly by the presence of the User-to-User header field of the Initial INVITE which is mapped into the user-user information element in the SETUP message. If service 1 is requested: Table 5.2.10.2.1-1: Implicit UUS1 transfer SIP messages DSS 1 messages INVITE→ SETUP→ User-to-User header u... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.11 Call Waiting (CW) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.11.1 Actions at the Outgoing AGCF/VGW | Table 5.2.11.1-1: Mapping of 18x provisional responses for CW procedure in ISDN access ←ALERTING/PROGRESS/NOTIFY (see note) ←18x Notification indicator information element Alert-Info: <urn:alert:service:call-waiting> Notification description 110 0000 Call is a waiting call NOTE: The criteria of sending of ALERTING or P... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.11.2 Actions at the incoming AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.11.2.1 Procedure at coincident S and T reference point | CW indication indicates the call waiting service is activated against the user. AGCF/VGW uses this CW indication in conjunction with the B-channel busy condition, and if both apply, AGCF/VGW shall send SETUP with "no channel" in the information channel selection field of the Channel identification information element. ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.11.2.2 Notification received at T reference point | A CW notification may be received at T reference point in the ALERTING message. Table 5.2.11.2.2-1: Receipt of a CW notification from a private network ←18x (see note) ←ALERTING/PROGRESS/NOTIFY Notification indicator information element Notification description Alert-Info: <urn:alert:service:call-waiting> 110 0000 Call... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.12 Terminal Portability (TP) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.12.1 Actions at the outgoing AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.12.1.1 Invocation at coincident S and T reference point | Table 5.2.12.1.1-1: TP invocation Message received from the DSS 1→ INVITE/UPDATE→ SUSPEND SDP: a=sendonly RESUME SDP: a=sendrecv The action taken on the access side upon receipt of SUSPEND and RESUME messages are described in clause 5.6 and figure A.6 of Recommendation ITU-T Q.931 [54]. Upon the T307 expiry, a Release ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.12.1.2 Notification received at T reference point | A TP notification may be received at T reference point from a point-to-point data link in the active phase of the call. Table 5.2.12.1.2-1: Receipt of a TP notification from a private network NOTIFY→ INVITE/UPDATE→ Notification indicator information element Notification description 000 0000 User suspended SDP: a=sendon... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.12.2 Actions at the incoming AGCF/VGW | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.12.2.1 Invocation at coincident S and T reference point | Table 5.2.12.2.1-1: TP invocation ←INVITE /UPDATE ←Message received from the DSS 1 SDP: a=sendonly SUSPEND SDP: a=sendrecv RESUME The actions taken on the access side upon receipt of the SUSPEND and RESUME messages are described in clause 5.2.6 and figure A.6 of Recommendation ITU-T Q.931 [54]. ETSI ETSI TS 183 036 V3.... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.12.2.2 Notification received at T reference point | A TP notification may be received at T reference point in the active phase of the call. Table 5.2.12.2.2-1: Receipt of a TP notification from a private network ←INVITE/UPDATE ←NOTIFY Notification indicator information element Notification description SDP: a=sendonly 000 0000 User suspended SDP: a=sendrecv 000 0001 User... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.13 Three-party (3PTY) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.13.0 General information regarding the service | Based on local policy, the AGCF may subscribe for the conference event package on behalf of the ISDN participant after being added to a three party. When the conference event package option is implemented, and one of the following events occurs at the AGCF/VGW: • a 200 OK is received as a response to an initial INVITE ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.13.1 Notification received from the network | Table 5.2.13.1-1: 3PTY notification ←NOTIFY ←INVITE Notification indicator information element <conference-info> Notification description <conference-state> 100 0010 Conference established <active>true< active/> 100 0011 Conference disconnected <active>false< active/> 111 1001 Remote hold SDP a=sendonly |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.13.2 Invocation at coincident S and T reference point | Before a three way conversation can be established, one of two existing sessions is set on hold by sending a reINVITE with an a attribute set to sendonly in the SDP. To invoke a three party communication after receipt of the Begin3PTY invoke component, the AGCF/VGW shall send an INVITE request with the conference facto... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.13.3 Notification received at T reference point | Table 5.2.13.3-1: Receipt of a 3PTY notification from a private network NOTIFY→ UPDATE/INVITE → Notification indicator information element <conference-info> Notification description <conference-state> 100 0010 Conference established <active>true< active/> 100 0011 Conference disconnected <active>false< active/> 111 100... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.13.4 Notification received at T reference point | Table 5.2.13.4-1: Receipt of a 3PTY notification from a private network ←INVITE/UPDATE ←NOTIFY <conference-info> Notification indicator information element <conference-state> Notification description <active>true< active/> 100 0010 Conference established <active>false< active/> 100 0011 Conference disconnected SDP a=se... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.14 Completion of Call to Busy Subscriber (CCBS) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.14.1 Actions at the outgoing AGCF/VGW | CCBS Invocation In case the terminating user is busy, a 183 Session Progress is received. The activation of the CCBS service is possible after the announcement is applied by the AS. The user provides the activation by performing in-band dialogue or by sending the proper service code via keypad protocol. The service cod... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.14.2 Actions at the incoming AGCF/VGW | No special requirements. Procedures as described in clause 5.1.2.1 apply. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 93 |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.15 Completion of Calls on No Reply (CCNR) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.15.1 Actions at the outgoing AGCF/VGW | CCNR Invocation In case the terminating user is not busy, a 180 Ringing is received. The activation of the CCNR service is possible after the announcement is applied by the AS. The user provides the activation by performing in-band dialogue or by sending the proper service code via keypad protocol. The service code rec... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.15.2 Actions at the incoming AGCF/VGW | No special requirements. Procedures as described in clause 5.1.2.1 apply. NOTE: Information received from the served user in the recall phase will not be transported to the terminating user. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 94 |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.16 Advice Of Charge AOC | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.16.0 General information regarding the service | As described in ETSI TS 183 047 [31], three AOC supplementary services exist: a) Charging information at communication set-up time (AOC-S): - The AOC-S service enables a user to receive information about the charging rates at communication set-uptime and also to receive further information during the communication if t... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.16.1 Actions at the outgoing AGCF/VGW | Transfer of AOC-S charging information The AOC-S charging information is transported during the call establishment, during the call (change in rates). During the call establishment, the AOC-S information shall be carried in SIP 1xx provisional response or a 200 OK response to an INVITE message, in a MIME body type "app... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.2.17 Message Waiting Indication (MWI) | Upon receipt of a NOTIFY request containing the following headers: • Event: message-summary. • Subscription-State: active. • Content-Type: application/simple-message-summary. • Messages-Waiting: yes. A DSS1 FACILITY message is sent to the DSS1 user equipment. The mapping of the Facility I.E is described in table 5.2.17... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.3 DSS1 layer 2 failure | 5.3.1 DSS 1 data link reset and data link failure procedures in the outgoing AGCF/VGW The data link reset and data link failure procedures are respectively described in clauses 5.2.8.8 and 5.2.8.9 of Recommendation ITU-T Q.931 [54]. Table 5.3.1-1: DSS 1 data link reset and data link failure procedures ←DISCONNECT Trigg... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.3.3 Release by the outgoing AGCF/VGW | Table 5.3.3-1: Release from the originating AGCF/VGW ←DISCONNECT Trigger event BYE/CANCEL→ Cause information element (see note 3) Reason header Cause value No. 28 Invalid number format (address incomplete) Determination that the called number information received is incomplete, after an INVITE message has already been ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.3.4 Release by the AGCF/VGW | Table 5.3.4-1: Release from the terminating AGCF/VGW ←Message sent to the SIP Trigger event Message sent to the DSS 1→ (see note 3) Point-to-point data link Broadcast data link 480 Cause value No. 18 No user responding No response to the SETUP message (T303 expiry) DISCONNECT Cause value No. 102 Recovery on timer expir... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4 Service operation | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.1 Call related service operation | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.1.1 Malicious Call Identification (MCID) | The invocation of Malicious Call Identification is described in clause 5.2.6. When a 200 OK INVITE is received as the final response to the reINVITE containing the MCID request, a mCIDRequest return result component is sent to the served user equipment. If an unsuccessful final response is received, a mCIDRequest retur... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.1.2 Explicit Communication Transfer (ECT) | The mapping of Explicit Communication Transfer related Facility components is described in clause 5.2.7. When a 202 Accepted is received, and the NOTIFY message/sipfrag part for both communications indicates the successful communication between Transfer target and Transferee, an eCTExecute return result component is se... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.1.3 Closed User Group (CUG) | The mapping of the CUG request and the handling of unsuccessful final responses is described in clause 5.2.9. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.1.4 Three Party Service (3PTY) | The mapping of Three Party Service related Facility components is described in clause 5.2.13. When for the INVITE sent to the conference focus to get a "conference URI" the 200 OK is received and the 202 Accepted for both REFER sent to the remote participants is received, a Begin3PTY return result component is sent to ... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.1.5 Completion of Call to Busy Subscriber (CCBS) | For further studies. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.1.6 Completion of Calls on No Reply (CCNR) | For further studies. |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2 Call independent service configuration | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.0 General requirements | Call independent service can be achieved using either the Gm reference point or the Ut reference point. In case of the Gm reference point the MESSAGE method is used to convey the service related information to the relevant target. In general the information to configure a service is embedded in an XML instance document... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.1 Communication Diversion Services (CDIV) | |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.1.1 Communication Diversion activation | On receipt of a DSS1 FACILITY message containing the ActivationDiversion invoke component, a SIP MESSAGE request or a HTTP request is sent that contains an XML "communication-diversion" instance to the Application Server. The attribute of the communication-diversion element is "true". The mapping of the Facility I.E is... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.1.2 Communication Diversion deactivation | On receipt of a DSS1 FACILITY message containing the DeactivationDiversion invoke component, a SIP MESSAGE request or a HTTP Request is sent that contains an XML "communication-diversion" instance to the Application Server. The attribute of the communication-diversion element is "false". The mapping of the Facility I.E... |
0ff9322d6516f1180b1095b0fba94533 | 183 036 | 5.4.2.1.3 Communication Diversion interrogation | On receipt of a DSS1 FACILITY message containing the InterrogationDiversion invoke component, a SIP MESSAGE or HTTP request is sent that contains an XML "communication-diversion" instance to the Application Server. The mapping of the Facility I.E is described below. Table 5.4.2.1.3-1: Mapping of InterrogationDiversion ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.