hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.1 Introduction | This clause identifies the functional entities of the IMS-based PES architecture [3] that play a specific role in the implementation of PES services with regards to SIP processing. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2 Functional Entities | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2.1 User Equipment (UE) | Conventional IMS UEs do not exist in PES. In PES, the User Equipment comprises one or more analogue/ISDN terminals and may include the residential gateway to which they are connected. This residential gateway may be an H.248-controlled media gateway or a Voice over IP Gateway (VGW). Voice over IP Gateways (VGW) appear ... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2.2 Access Gateway Control Function (AGCF) | For the purpose of the PES, the AGCF shall implement the role of the PES access point as described in clause 5.3.2. The AGCF is part of the trust domain. The AGCF entity encompasses the functionality of an H.248 Media Gateway Controller (MGC) as defined in ITU-T Recommendation H.248.1 [22] and of a SIP User Agent as de... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2.3 Application Server (AS) | For the purpose of the PES, the AS shall implement the role of a PES application server, as described in clause 5.3.3. NOTE: The PES architecture does not require that all application servers involved in sessions initiated/addressed by/to PES users adhere to the procedures prescribed for the PES application server role... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2.4 Media Resource Function Controller (MRFC) | For the purpose of the PES, an MRFC shall implement the role of the PES announcement server as described in clause 5.3.4. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2.5 Media Gateway Controller Function (MGCF) | For the purpose of the PES, the MGCF shall implement the role of a PES interworking application as described in clause 5.3.5. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2.6 Interconnection Border Control Function (IBCF) | For the purpose of the PES, the IBCF shall implement the role of a PES Interconnection Application as described in clause 5.3.6. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.2.7 Voice over IP gateway (VGW) acting as Access Gateway | For the purpose of the PES, an access VGW, in line with the behaviour of all VGWs, shall implement the role of the PES end point as described in clause 5.3.1. The VGW entity encompasses the functionality of a Media Gateway Controller (MGC), Media Gateway (MG) and a SIP User Agent as defined in RFC 3261 [38]. Within the... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3 Role | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1 PES Endpoint | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.1 General | In addition to the procedures specified in the rest of clause 5.3.1, the PES endpoint shall support the procedures specified in ES 283 003 [4] and TS 183 028 [6] appropriate to an IMS UE. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.2 Subscription for profile delivery | The PES Endpoint shall subscribe to the "ua-profile" event defined in [15] and support the Profile document defined in annex A of the present document and optionally to the "message-summary" event defined in RFC 3842 [18]. The subscription may be implicit or explicit. If explicit subscription is required, the identity ... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.3 Registration procedures | The allocation of private and public user identities is left to each operator to decide. Two approaches are identified: • Group-based registration: One private user identity is assigned to a group of subscriber. A temporary public user identity is associated with this private user identity. Real public user identities ... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.4 Charging procedures | A PES Endpoint supporting advice of charge services shall support the INFO method and shall accept MIME bodies of type "application/vnd.etsi.aoc+xml" (see annex E). An INFO request that transports a body with AOC information shall identify the payload as MIME type "application/vnd.etsi.aoc+xml", the MIME type associate... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.5 Outgoing Call | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.5.1 General | Calls initiated by a PES user via a PES end point shall operate following the UE call origination procedures defined in ES 283 003 [4]. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.5.2 Procedures for analogue lines | On receipt of a non-empty Setup-Request the PES Endpoint shall send an INVITE request with the call destination in the Request-URI, an SDP Offer for a voice call. The INVITE may include a P-Preferred-Identity header field set to the default identity associated with the analogue termination where the off-hook event was ... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.5.3 Procedures for ISDN access | The procedures specified TS 183 036 [40] apply. If line-based registration is used, the PES Endpoint may set the P-Preferred-Identity header according to the calling party number received from the ISDN interface, as specified in TS 183 036 [40]. If the P-Preferred-Identity is not sent then the PES Endpoint shall ensure... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.6 Terminating Call | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.6.1 General | Calls to a PES user via a PES end point shall operate following the UE call termination procedures defined in ES 283 003 [4]. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.1.6.2 Use of Overlap Signalling (Optional) | If Overlap Signalling is supported between the PES Endpoint and the terminating PES Application Server the Overlap Signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annex F is dependent on national or network operator option. For ISDN Access the procedures specified... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2 PES Access Point | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.1 General | In addition to the procedures specified in the rest of clause 5.3.2, the behaviour of the PES access point shall be equivalent to the concatenation of the behaviour of a UE and a P-CSCF entity, as defined in ES 283.003 [4] and TS 183 028 [6]. NOTE: The above statement does not require AGCF implementations to execute UE... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.2 Subscription for profile delivery | On receipt of a NOTIFY request reporting the "message-summary" event with a "Messages-Waiting" field set to "yes", the PES access point shall: • Save the current dial tone value and set the current dial tone to the message waiting tone. • Send a Message Waiting Indicator message (see EN 200 659-3 [10]) using the proced... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.3 Registration Procedures | The following IMS parameters are assumed to available in a local data base: • a private user identity; • a public user identity; and • a home network domain name to which SIP REGISTER requests are addressed. The allocation of private and public user identities is left to each operator to decide. Two approaches are iden... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.4 Originating Call Control procedures | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.4.1 General | Calls initiated by a PES user via a PES access point shall operate following the concatenation of UE call origination and P-CSCF procedures as defined in ES 283 003 [4]. When the PES Access Point controls an A-MGW, the dsl-location parameter is set to a provisioned value associated to the line or to the media gateway i... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.4.2 Procedures for analogue lines | On receipt of a non-empty Setup-Request the PES access point shall send an INVITE request with the call destination in the Request-URI, an SDP Offer set according to the information received from the MGF and a P-Asserted-Identity header field set according to the default identity associated with the analogue terminatio... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.4.3 Procedures for ISDN access | The procedures specified TS 183 036 [40] apply. If line-based registration is used, the PES Access Point shall set the P-Asserted-Identity header according to the calling party number received from the ISDN interface, as specified in TS 183 036 [40]. The PES Endpoint should verify that this identity is included in the ... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.4.4 Use of Overlap Signalling (Optional) | If Overlap Signalling is supported between the PES Endpoint and the originating PES Application Server the Overlap Signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annex F is dependent on national or network operator option. For ISDN Access the procedures specified... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.5 Terminating Call Control procedures | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.5.1 General | Terminating calls received by a PES access point shall operate following the UE call termination procedures defined in ES 283 003 [4]. The P-Called-Party header value is used to fetch the termination to which the call shall be delivered. When the PES Access Point controls an A-MGW, the dsl-location parameter is set to ... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.5.2 Use of Overlap Signalling (Optional) | If Overlap Signalling is supported between the PES Access Point and the terminating PES Application Server the Overlap Signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annex F is dependent on national or network operator option. For ISDN Access the procedures speci... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.2.6 Charging procedures | A PES access point supporting advice of charge services shall support the INFO method and shall accept MIME bodies of type "application/vnd.etsi.aoc+xml". An INFO request that transports a body with AOC information shall identify the payload as MIME type "application/vnd.etsi.aoc+xml"", the MIME type associated with AO... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3 PES Application Server | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.1 General | In addition to the procedures specified in the rest of clause 5.3.3, the PES application server shall support the procedures specified in ES 283 003 [4] appropriate to an application server. ETSI ETSI TS 183 043 V2.3.1 (2009-03) 28 |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.2 Basic call procedures | A PES application server can act either as a proxy server or as a Back to Back User Agent (B2BUA) while processing calls. When acting as a B2BUA, the PES application server provides both originating UA and terminating UA functions as described in ES 283 003 [4]. As an originating UA that sends outbound INVITE requests,... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.3 Announcement procedures | The PES application server shall have the capability of requesting announcements during any phase of a session, according to the procedures described in TS 183 028 [6]. The PES application server shall use the ANNC URL syntax defined in [16] when requesting a PES announcement server to play an announcement. A PES appli... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.4 Profile Delivery | The PES application server shall act as a profile delivery server and manage Profile documents whose structure conforms to the XML schema defined in annex A and TS 183 023 [33]. The contents of the NOTIFY request shall be as follows: • The Event header shall be set to the "ua-profile" event package. • The "effective-by... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.5 Transport of ISUP information | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.5.1 General | Clause 5.3.3.5 describes the general behaviour of the PES application server in the case the PES application server is capable of exchanging ISUP information, as defined in ITU-T Recommendation Q.763 [29], carried within Narrowband Signalling Syntax (NSS) [31] message bodies with its SIP signalling peers to perform ser... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.5.2 Sending NSS message bodies to a peer SIP signalling entity | 5.3.3.5.2.1 General The PES application server shall send an NSS message body with encapsulated ISUP information in the appropriate SIP message to a peer SIP signalling entity according to the clauses 5.3.3.5.2.2 through 5.3.3.5.2.7, when all the following conditions are satisfied. • The PES application server is capab... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.5.3 Receiving an NSS message body from a peer SIP signalling entity | 5.3.3.5.3.1 General On receipt of a SIP message containing an NSS message body, a PES application server supporting services that require encapsulated ISUP information shall de-encapsulate the ISUP information from the NSS message body, perform the processing described in the clause 5.3.3.5.3.2, and trigger the relevan... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.3.6 Handling of charging information | When processing originating sessions, the PES application server shall be able to act as a Charging Generation Point (CGP) and send the appropriate charging information to the PES access point/endpoint. The PES application server shall accept charging information in the format defined in TS 183 058 [42], annex C and ma... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.4 PES Announcement Server | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.4.1 General | In addition to the procedures specified in the rest of clause 5.3.4, the PES announcement server shall support the procedures specified in ES 283 003 [4] appropriate to an MRFC. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.4.2 Announcement procedures | The PES announcement server shall support the ANNC URL syntax defined in [16] when providing announcements, prompt and collect functions, and multi-party conferencing. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5 PES Interworking Application | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.1 General | In addition to the procedures specified in the rest of clause 5.3.5, the PES interworking application shall support the procedures specified in ES 283 003 [4] and TS 183 028 [6] appropriate to an MGCF. ETSI ETSI TS 183 043 V2.3.1 (2009-03) 33 The PES interworking application shall support the P-Early-Media header. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.2 Routing procedures | In case of incoming calls from legacy networks, the PES interworking application determines the next hop in IP routing depending on received signalling information, based on configuration data and/or data base look up. The next hop may be an I-CSCF, a BGCF or an IBCF. Based on the destination and local policy rules, th... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.3 Handling of charging information | The PES interworking application shall be able to insert charging information in SIP messages sent in the upstream direction, based on charging information received from the PSTN. The PES interworking application shall use the format defined in TS 183 058 [42], annex C. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.4 Transport of ISUP information | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.4.1 General | The procedures in the clause 5.3.5.4 allow the PES interworking application to discover whether or not its peer SIP signalling entity is capable of supporting the encapsulation of ISUP information in Narrowband Signalling Syntax (NSS) [31] message bodies within SIP messages, and to successfully support the additional e... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.4.2 Sending ISUP information to a peer SIP signalling entity | 5.3.5.4.2.1 General The PES interworking application shall send an NSS message body with encapsulated ISUP information in the appropriate SIP message to a peer SIP signalling entity according to the clauses 5.3.5.4.2.2 through 5.3.5.4.2.7, when all the following conditions are satisfied. • Either the encapsulating mess... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.4.3 Receiving an NSS message body from a peer SIP signalling entity | 5.3.5.4.3.1 General On receipt of a SIP message containing an NSS message body, the PES interworking application supporting NSS shall de-encapsulate the ISUP information from the NSS message body, perform the processing described in clauses 5.3.5.4.3.2 and 5.3.5.4.3.3, and pass the ISUP information to the relevant ISUP... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.4.4 ISUP messages for special consideration | 5.3.5.4.4.1 General Table 3 lists the PES interworking application behaviour upon receipt of ISUP messages that have no counterparts in basic SIP call control messages. Table 3: ISUP messages for special consideration ISUP message Reference Subsequent address message 5.3.5.4.4.6 Reset circuit 5.3.5.4.4.2 Call progress ... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.5.5 Optional SIP/ISUP interworking procedures for PSTN Bridging | If the PES interworking application can determine that a call is for PSTN bridging (i.e. that the call will end up in an ISUP network) then the PES interworking application may, as a network option, use the interworking procedures defined in EN 383 001 [20] for Profile C. The way the PES interworking application detect... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.6 PES interconnection application | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.6.1 General | In addition to the procedures specified in the rest of clause 5.3.6, the PES interconnection application shall support the procedures specified in ES 283 003 [4] appropriate to an IBCF. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 5.3.6.2 Procedures related to NSS message bodies | Depending on local policy, the PES interconnection application in an IMS PES supporting NSS, acting as a B2BUA, may perform any reasonable combination of the following functions related to an NSS message body within a received SIP message, where the message is to be forwarded either into or outside of the IMS PES: • re... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6 Protocol using SIP/SDP for PES | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.1 Introduction | This clause identifies the functional entities of the IMS-based PES architecture [3] that play a specific role in the provision of PES services with regards to SDP processing in the context of SIP signalling. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.2 Functional Entities | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.2.1 User Equipment (UE) | Conventional SIP UEs do not exist in PES (see clause 5.2.1). For the purpose of the PES, the VGW shall implement the role of a PES endpoint as described in clause 6.3.1. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.2.2 Access Gateway Control Function (AGCF) | For the purpose of the PES, the AGCF shall implement the role of the PES access point as described in clause 6.3.2. The AGCF entity encompasses the functionality of a Media Gateway Controller (MGC) and of a SIP User Agent. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.2.3 Application Server (AS) | For the purpose of the PES, the AS shall implement the role of a PES application server, as described in clause 6.3.3. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.2.4 Media Resource Function Controller (MRFC) | For the purpose of the PES, an MRFC shall implement the role of the PES announcement server as described in clause 6.3.4. ETSI ETSI TS 183 043 V2.3.1 (2009-03) 39 |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.2.5 Voice over IP gateway (VGW) | For the purpose of the PES, the VGW shall implement the role of the PES end point as described in clause 6.3.1. The VGW entity encompasses the functionality of a Media Gateway Controller (MGC), Media Gateway (MG) and of SIP User Agent. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3 Roles | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.1 PES Endpoint | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.1.1 General | In addition to the procedures specified in the rest of clause 6.3.1, the PES endpoint shall support the procedures specified in ES 283 003 [4] appropriate to an IMS UE. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.1.2 Originating Calls | When sending an SDP payload in a SIP message, the PES endpoint shall not include the "i=", "u=", "e=", "p=", "r=", and "z=" lines in the SDP, and it shall ignore them when received in the SDP. For calls originating from an analogue access, PES endpoint shall build an SDP offer as follows: • Only one media description s... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.1.3 Terminating Calls | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.1.3.1 General | When sending an SDP payload in a SIP message, the PES endpoint shall not include the "i=", "u=", "e=", "p=", "r=", and "z=" lines in the SDP, and it shall ignore them when received in the SDP. When the PES endpoint sends a 183 (Session Progress) response with SDP payload, it shall only request confirmation for the resu... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.1.3.2 Analogue Access | For calls terminating on an analogue access, the PES endpoint shall: • Reject any media descriptions whose media type is different from audio, by setting the corresponding port to 0. NOTE: Support of T.38 is outside the scope of TISPAN NGN present Release. • check for codecs that match the requested SDP, which may incl... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.1.3.3 ISDN Access | Processing of media description for calls terminating on an ISDN access shall conform to TS 183 036 [40]. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.2 PES Access Point | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.2.1 General | In addition to the procedures specified in the rest of clause 6.3.2, the PES access point shall support the procedures specified in ES 283 003 [4] appropriate to an AGCF. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.2.2 Originating calls | When sending an SDP, the PES access point shall not include the "i=", "u=", "e=", "p=", "r=", and "z=" lines in the SDP, and it shall ignore them when received in the SDP. For calls originating from an analogue access, PES endpoint shall build an SDP offer as follows: • Only one media description shall be included (i.e... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.2.3 Terminating calls | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.2.3.1 General | When sending an SDP, the PES access point shall not include the "i=", "u=", "e=", "p=", "r=", and "z=" lines in the SDP, and it shall ignore them when received in the SDP. • When the PES access point sends a 183 (Session Progress) response with SDP payload, it shall only request confirmation for the result of the resou... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.2.4 Void | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.3 PES Application Server | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.3.1 General | In addition to the procedures specified in the rest of clause 6.3.3, the PES application server shall support the procedures specified in ES 283 003 [4] appropriate to an application server. When acting as a B2BUA, the PES application server must appropriately handle SDP received in responses received from a forking Pr... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.4 PES Announcement Server | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 6.3.4.1 General | In addition to the procedures specified in clause 6.3.4, the PES announcement server shall support the procedures specified in ES 283 003 [4] appropriate to an MRFC. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7 Protocol using H.248 for PES | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.1 Introduction | This clause identifies the functional entities of the IMS-based PES architecture [3] that play a specific role in the provision of PES services with regards to H.248 processing. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.2 Functional Entities | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.2.1 Access Gateway Control Function (AGCF) | For the purpose of the PES, the AGCF shall implement the role of the PES access point as described in clause 7.3.1. The AGCF entity encompasses the functionality of an H.248 Media Gateway Controller (MGC) and of a SIP User Agent. Within the AGCF, the MGC and SIP UA components are coordinated by a Feature Manager entity... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.2.2 Media Gateway Function (MGF) | For the purpose of the PES, the MGF shall implement the role of the PES media gateway as described in clause 7.3.2. |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3 Roles | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3.1 PES Access Point | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3.1.1 General | In addition to the procedures specified in the rest of clause 7.3.1, the PES access point shall support the procedures specified in ES 283 002 [5] appropriate to an MGC. ETSI ETSI TS 183 043 V2.3.1 (2009-03) 42 |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3.1.2 Registration | Registration is supported using the H.248 Service Change procedure. Registration can be performed on a group basis or on a per line/access basis. This event is passed to the Feature Manager. NOTE: A group may consist of all lines connected to a PES media gateway or to a subset of the media gateway. When the group basis... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3.1.3 Basic Session control procedures for analogue lines | |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3.1.3.1 Originating side procedures | 7.3.1.3.1.1 Call Initiation Step 0 On receipt of a notify command from the PES media gateway reporting the off-hook (al/of) event the PES access point shall: • Derive the user identity associated with the termination reporting the event. • Report the occurrence of the off-hook event to the Feature Manager using a Sessi... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3.1.3.2 Terminating side procedures | 7.3.1.3.2.1 Call Initiation Step 0 On receipt of a Setup-Request primitive from the internal SIP UA (via the Feature Manager), the PES access point shall: • Check that the required bearer service is compatible with analogue lines, otherwise return a Setup-Response to the Feature Manager, with a reject indication. • Det... |
7dd8c10c1a9b124ff7a27c3e74b13587 | 183 043 | 7.3.1.4 Procedures for fax/modems calls over analogue access | In order to be able to properly handle fax and modem calls, the PES access point requests the media gateway to monitor the ctyp/dtone event. On receipt of a notification of the ctyp/dtone event, the AGCF notifies the Feature Manager if the recognized tone corresponds to a supported fax/modem. Otherwise, the event is di... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.