hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
64055e89333e00dcb957f3ac03995556 | 102 179 | 4 Protocol architecture | The protocol architectures for PT and FT are shown in figures 1 and 2. Application 1 DTE1 AT IWU NWK DLC MAC PT PHY Figure 1: Protocol architecture PT ETSI ETSI TR 102 179 V1.1.1 (2003-03) 7 Application 2 DTE2/DCE2 AT IWU NWK DLC MAC FT PHY Figure 2: Protocol architecture FT |
64055e89333e00dcb957f3ac03995556 | 102 179 | 5 Configurations | |
64055e89333e00dcb957f3ac03995556 | 102 179 | 5.1 NULL MODEM configuration | A NULL MODEM configuration is shown in figure 3. DTE1 (an application of the PC1) controls with the AT command set the PT. The PT establishes a connection to the FT. DTE2 (an application of the PC2) controls with the AT command set the FT. Once the connection is established, data can be conveyed between DTE1 and DTE2. ... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 5.2 ACCESS configuration | An ACCESS configuration is shown in figure 4. DTE1 (an application of the PC) controls with the AT command set the PT. The PT establishes a connection to the FT. The FT establishes a connection via the Modem (M) to an Internet Service Provider (ISP). Once the connection is established, data can be conveyed between DTE1... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6 Interworking procedures | |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.1 General AT commands | Tables 1 to 5 list the general AT commands which should be implemented by the IWF of the PT and the FT. The PT is the DCE in the NULL MODEM configuration and in the ACCESS configuration. The FT is the DCE in the NULL MODEM configuration and the FT is the DTE in the ACCESS configuration. Table 1: Generic DCE control com... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.2 DECT specific AT commands | Tables 6 to 11 list the DECT specific AT commands which should be implemented by the IWF of the PT and the FT. Table 6: AT commands for configuration Command DTE to DCE Command description Reference DCE action Response DCE to DTE AT&F0 Set to factory- defined configuration 6.1.2 [18] Select NULL MODEM configuration OK,... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.3 PT subscription | If the PT is switched on for the first time, then the PT should execute the following procedures: • Obtain access rights. • Location registration. Then the FT should execute: • Authentication of PT. If the PT is switched on after having executed the subscription, then the PT should execute the following procedure: • Lo... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.3.1 Obtain access rights | The Obtain Access Rights procedure is shown in figure 5, the related AT commands are listed in table 7. If the P-IWU receives an AT+COAR=1 command, then the P-IWU should issue a MM_ACCESS_RIGHTS.req primitive resulting in an ACCESS-RIGHTS-REQUEST message (see 8.30 [6]) being sent to the FT. Access accept: Upon receipt ... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.3.2 Location registration | The Location Registration procedure is shown in figure 6, the related AT commands are listed in table 8. If the P-IWU receives an AT+CGATT=1 command, then the P-IWU should issue a MM_LOCATE.req primitive resulting in a LOCATE-REQUEST message (see 8.28 [6]) being sent to the FT. Locate accept: Upon receipt of the LOCATE... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.3.3 Authentication | |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.3.3.1 Authentication of the user | The Authentication of the user procedure is shown in figure 7, the related AT commands are listed in table 9. If PC1 receives an AT+CPIN command, then PC1 should send the AT+CPIN=UPI command to the PT. The PT should store the UPI and send an OK command to PC1. If PC1 wants to notify the PT directly with the UPI, then P... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.3.3.2 NULL MODEM authentication of a PT | The NULL MODEM Authentication of a PT procedure is shown in figure 8, the related AT commands are listed in table 9. If the F-IWU receives an AT+CPIN command, then the F-IWU should issue a MM_AUTHENTICATE.req primitive resulting in an AUTHENTICATION-REQUEST message (see 8.24 [6]) being sent to the PT. Authentication ac... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.3.3.3 Authentication of a FT | The Authentication of a FT procedure is shown in figure 9, the related AT commands are listed in table 9. If the P-IWU receives an AT+CPIN command, then the P-IWU should issue a MM_AUTHENTICATE.req primitive resulting in an AUTHENTICATION-REQUEST message (see 8.24 [6]) being sent to the FT. Authentication accept: Upon ... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.4 Call control | Upon receipt of a CC-SETUP message the PT/FT sends: • in the case of the NULL MODEM configuration a RING command; and • in the case of the ACCESS configuration an ATD command. The IWF of the PT/FT has to have information about the current configuration in order to send the correct AT command. The information about the ... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.4.1 NULL MODEM call establishment | The NULL MODEM call establishment is shown in figure 10. The default configuration could be the NULL MODEM configuration. The NULL MODEM call establishment initiated by DTE1 is symmetric to the NULL MODEM call establishment initiated by DTE2 (except for the CC_CONNECT_ACK). Therefore only the NULL MODEM call establishm... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.4.2 ACCESS DTE-initiated call establishment | The DTE-initiated call establishment is shown in figure 11. The default configuration could be the NULL MODEM configuration. In order to change into ACCESS configuration the AT&F255 command should be used. If the P-IWU receives an AT&F255 command, then the P-IWU should switch to ACCESS configuration and return an OK me... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.4.3 ACCESS DCE-initiated call establishment | The DCE-initiated call establishment is shown in figure 12. If the F-IWU receives a RING command, then the F-IWU should issue a MNCC_SETUP.req primitive resulting in a CC-SETUP message being sent to the PT. Upon receipt of a MNCC_SETUP.ind primitive the P-IWU should send a RING command to DTE1. PT and FT may perform th... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.5 Bandwidth negotiation | |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.5.1 NULL MODEM bandwidth negotiation | The NULL MODEM bandwidth negotiation is shown in figure 13. The NULL MODEM bandwidth negotiation initiated by DTE1 is symmetric to the NULL MODEM bandwidth negotiation initiated by DTE2 (except for the CC_CONNECT_ACK). Therefore only the NULL MODEM bandwidth negotiation initiated by DTE1 is described. DTE1 defines the ... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.5.2 ACCESS DTE bandwidth negotiation | The ACCESS DTE bandwidth negotiation is shown in figure 14. DTE1 defines the data rate of the next call by sending an AT+CBST=<speed> command to the PT. At the next call attempt the PT maps the <speed > parameter to the Data rate field of the IWU-attributes element. The FT maps the Data rate field of the IWU-attributes... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.5.3 ACCESS DCE bandwidth negotiation | The ACCESS DCE bandwidth negotiation is shown in figure 15. DCE2 defines the data rate of the next call by sending an AT+MRR:<speed> command to the FT. At the next call attempt the FT maps the <speed > parameter to the Data rate field of the IWU-attributes element. The PT maps the Data rate field of the IWU-attributes ... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.6 Ciphering | |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.6.1 NULL MODEM ciphering by FT | The NULL MODEM ciphering by FT is shown in figure 16. If the F-IWU receives an AT+CCF command, then the F-IWU should either send a CIPHER-REQUEST message or execute the key allocation procedure. Ciphering accept: The FT sends an OK command. Ciphering reject: The FT sends the appropriate D-ERROR-RESULT command. ETSI ETS... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.7 Error handling | The definition of the +CMEE command and +CME ERROR command should apply as described in TS 127 007, clauses 9.1 and 9.2 [11] with the following modifications. |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.7.1 +CMEE | Defined values <n>: 3 enable +CME ERROR: <err> result code and use hex <err> values |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.7.2 +CME ERROR | The id parameter (decimal value of the element header) is introduced in order to distinguish between Reject reasons and Release reasons which have the same decimal value. Defined values <id, err>: id (decimal): 96 Reject reason 226 Release reason ETSI ETSI TR 102 179 V1.1.1 (2003-03) 29 err: copy from the DECT values |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.8 Multiplexing | The +CMUX command should enable/disable the multiplexer protocol, as specified in TS 127 010 [12]. The multiplexing protocol allows a number of virtual channels to be established between DTE1 and a the PT, and DTE2 and the FT respectively. In the following clauses possible appliances are described. |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.8.1 Bandwidth change | Once a connection is established, the bandwidth can be changed. |
64055e89333e00dcb957f3ac03995556 | 102 179 | 6.8.1.1 NULL MODEM bandwidth change | The NULL MODEM bandwidth change is shown in figure 23. The NULL MODEM bandwidth change initiated by DTE1 is symmetric to the NULL MODEM bandwidth change initiated by DTE2. Therefore only the NULL MODEM bandwidth change initiated by DTE1 is described. DTE1 changes the data rate of the call by sending an AT+CBST=<speed> ... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 7 Message mappings | |
64055e89333e00dcb957f3ac03995556 | 102 179 | 7.1 AT to DECT | Table 24: List of mapped messages, AT to DECT Item No AT command DECT message Mapping status 1 AT+COAR ACCESS-RIGHTS-REQUEST o 2 AT+CGATT=1 LOCATE-REQUEST o 3 AT+CPIN AUTHENTICATION-REQUEST o 4 ATD <dial-string> CC-SETUP o 5 ATA CC-CONNECT o 6 CONNECT <text> CC-CONNECT o 7 RING CC-SETUP o 8 AT+CBST=<data rate> CC-SERVI... |
64055e89333e00dcb957f3ac03995556 | 102 179 | 7.2 DECT to AT | Table 25: List of mapped messages, DECT to AT Item No DECT message AT command Mapping status 1 ACCESS-RIGHTS-ACCEPT OK o 2 ACCESS-RIGHTS-REJECT AT+CME ERROR o 3 LOCATE-ACCEPT OK o 4 LOCATE-REJECT AT+CME ERROR o 5 AUTHENTICATION-REPLY OK o 6 AUTHENTICATION-REJECT AT+CME ERROR o 7 CC-SETUP(1) RING o 8 CC-SETUP(2) ATD o 9... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 1 Scope | The present document applies to measurements of the symmetry behaviour and the attenuation in Low Voltage Distribution Networks (LVDN) within premises. It also covers measurements for magnetic near fields within and in close vicinity of premises resulting from feeding HF-signals into LVDN. The measurements are intended... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ITU-T Recommendation G.117: "Transmission aspects of unbalance about earth". [2] CISPR 16-1: "Specification for radio disturbance and immunity measuring apparatus and methods- Part 1: Radio disturbance and immunity measuring apparatus". ... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 3 Abbreviations and symbols | |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 3.1 Abbreviations | For the purposes of the present document, the following abbreviations apply: EL Electromagnetic force (EMF)of the asymmetric feeding voltage EMF ElectroMagnetic Force HF High Frequency L Line LCL Longitudinal Conversion Loss LCTL Longitudinal Conversion Transfer Loss LTL Longitudinal Transfer Loss LVDN Low voltage dist... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 3.2 Symbols | kasy Coupling factor for asymmetric feed ksym Coupling factor for symmetric feed Zasy Asymmetric impedance Zsym Symmetric impedance ETSI ETSI TR 102 175 V1.1.1 (2003-03) 6 |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 4 Terminology guide | The used terminology has been clarified by means of figures 1 to 9. LVDN ZLCL ZLCL/4 UA.1 2UA.2 × × = 2. 1. 2 log 20 A A U U LCL Figure 1: Longitudinal Conversion Loss (LCL) LVDN ZLCL ZLCL/4 UA.1 UA.3 ZLCL/4 ZLCL × = 3. 1. log 20 A A U U LTL Figure 2: Longitudinal Transfer Loss (LTL) LVDN ZL... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 5 Measurement set-up | In contrast to other specifications or standards the present document defines a common measurement set-up for the collection of raw data, which is used for deriving quantities relevant for the operation of PLT. The main measurement concept is to use two independent subsystems, one for signal feeding and one for signal ... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 5.1 LCL measurement | The following impedance definitions are used: LVDN Z LCL Z LCL /4 E L U T L N PE Figure 10: LCL measurement set-up LCL is not only a function of the symmetric - and the asymmetric - impedance and the unbalance characteristic of the LVDN to be measured, but it is also a rather strong function of ZLCL Thus it is essentia... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 5.2 Field strength measurement | The magnetic field strength is measured with a loop antenna. Measurements shall be performed with three orthogonal orientations of the antenna. The raw data file shall contain the three readings. ETSI ETSI TR 102 175 V1.1.1 (2003-03) 9 |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 5.3 Measurements with asymmetric feeding | For asymmetric feeding the LCL-measurement adapter shall be used. Therefore an asymmetric impedance of 25 Ω is applied. The signal feeding subsystem consists of a comb generator, producing narrowband signals in 1 MHz spacing. An amplifier with an output power of minimum 1 W may be required for the measurement of the ma... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 5.4 Measurements with symmetric feeding | For symmetric feeding a simple BALUN (impedance ratio 1:4) shall be used. Therefore a symmetric impedance of 100 Ω applies in conjunction with the circuit shown in the figures below. The signal feeding subsystem consists of a comb generator, producing narrowband signals in 1 MHz spacing. An amplifier with an output pow... |
ffc8eae5185a71c8279bb1d30801ffad | 102 175 | 5.5 Summary of necessary measurement equipment | • Comb generator, spikes in 1 MHz steps. • Broadband amplifier (class A) minimum 1 W for field strength measurements. • Measurement receiver, AV-detector, 10 kHz bandwidth, preselector. • Power terminator 50 Ω (suitable for the amplifier). • 6 terminator 50 Ω. • 2 measurement adapters according to Macfarlane [3](with v... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 1 Scope | Services for Computer Supported Telecommunications Applications are defined by Standard ECMA-269 and the XML Protocol for those services is defined by Standard ECMA-323. In many cases, applications require only a small subset of the features standardized in CSTA. In a voice browser environment, processing speech (not c... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 2 References | The present document provides informative examples of how to use ECMA-323 in a Voice Browser environment. The following ECMA Standards should be used as the definitive references for CSTA. ECMA-269: "Services for Computer Supported Telecommunications Applications (CSTA) Phase III". ECMA-323: "XMLProtocol for Computer S... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 3 Brief Overview of ECMA-323 | ECMA-323 consists of a set of XML Schemas based upon the W3C XML Schema Language Recommendation. The Standard includes schemas for many categories of services defined in ECMA-269. Call control is just one category of services in ECMA-323. Examples of other categories of services are: capability exchange (feature discov... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 4 Fundamental Concepts | This clause introduces some informative modelling concepts that are useful to illustrate how ECMA-323 enabled voice browsers can use ECMA-323 messages. The actual ECMA CSTA standards should be used for the definitive descriptions. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 4.1 CSTA Connection | CSTA call control services are applied to CSTA connections. A CSTA connection refers to a relationship between a call and a telephony endpoint. A CSTA connection is referenced via a CSTA connection identifier. A CSTA connection identifier consists of a call identifier and a device (endpoint) identifier. In a typical 1s... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 4.2 CSTA Connection State Model | A ECMA-323 enabled voice browser application is informed of connection state transitions (via ECMA-323 call control events) by placing a monitor on a telephony endpoint via an associated address (e.g. this is how an application "listens" for incoming calls). Each CSTA connection in a call is associated with a connectio... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 4.3 Connection State Transitions for CSTA Calls | |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 4.3.1 Incoming Call | The following figure illustrates the CSTA events for an incoming call. The connection state of endpoint on the voice browser platform (called connection) is indicated in parenthesis. • Delivered Event (Alerting): Indicates call is alerting. Calls that are "auto-answered" do not sent this event. A CSTA Answer Call servi... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 4.3.2 Outgoing Call | The following figure illustrates the CSTA events for an outgoing call. The connection state of the endpoint on the Voice Browser platform (originating connection) is indicated in parenthesis. This sequence could be the result of a CSTA Make Call service. • Originated Event (Connected): Indicates that the originating co... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5 CSTA Profiles | Since many CSTA features are optional, and to enhance application portability across different CSTA implementations, CSTA standards require a minimal subset of functionality as conformance criteria. ECMA-269 specifies a set of Profiles. At least one profile is required to be supported. The following profiles most close... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.1 Level 1a Voice Browser Profile | |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.1.1 Services | The following CSTA services are included in the Level 1a Voice Browser Profile: • Answer call: Answers an alerting call. In a voice browser, the answering device is an endpoint on the platform. • Clear Connection: Clears a connection. In a voice browser environment, the clearing device is an endpoint on the voice brows... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.1.2 Events | The following CSTA events are included in the Level 1a Voice Browser Profile: • Connection Cleared: Indicates that an endpoint has disconnected from a call. • Delivered: Indicates that a call is alerting an endpoint. • Established: Indicates that an endpoint has answered or been connected to a call. • Failed: Indicates... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.2 Level 1b Voice Browser Profile | |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.2.1 Services | The following CSTA services are included in the Level 1b Voice Browser Profile: • Answer call: Answers an alerting call. In a voice browser, the answering device is an endpoint on the platform. • Clear Connection: Clears a connection. In a voice browser environment, the clearing device is an endpoint on the voice brows... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.2.2 Events | The following CSTA events are included in the Level 1b Voice Browser Profile: • Connection Cleared: Indicates that an endpoint has disconnected from a call. • Delivered: Indicates that a call is alerting an endpoint. • Diverted: Indicates that the endpoint (on the voice browser platform) has redirected a call to anothe... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.3 Level 2 Voice Browser Profile | |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.3.1 Services | In this profile, a CSTA implementation is required to provide its capabilities to applications via the ECMA-323 Get Switching Function Capabilities service. The capabilities include the list of ECMA-323 services and events supported by a telephony platform and the various types of behaviour options supported by an impl... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.3.2 Events | The following CSTA events are included in the Level 2 Voice Browser Profile: • Connection Cleared: Indicates that an endpoint has disconnected from a call. • Delivered: Indicates that a call is alerting an endpoint. • Established: Indicates that an endpoint has answered or been connected to a call. ETSI ETSI TR 102 171... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.4 Basic Telephony Profile | |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.4.1 Services | In this profile, the CSTA implementation is required to provide its capabilities to applications via the ECMA-323 Get Switching Function Capabilities service. The capabilities include the list of ECMA-323 services and events supported by a telephony platform and the various types of behaviour options supported by an im... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.4.2 Events | The following CSTA events are included in the Basic Telephony Profile: • Connection Cleared: Indicates that an endpoint has disconnected from a call. • Delivered: Indicates that a call is alerting an endpoint. • Established: Indicates that an endpoint has answered or been connected to a call. • Failed: Indicates that a... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 5.5 Other Features | The services defined in these profiles are a very small subset of the call control features standardized in CSTA. A telephony platform may provide any number of additional ECMA-323 services and may even provide features that have not been standardized in ECMA-323 by using the ECMA-323 extension mechanism. The following... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6 ECMA-323 Illustrative Examples | This clause provides some examples of ECMA-323 XML messages (W3C Instance Documents) in the context of voice browser usage scenarios. Examples include: • discovering the features supported by a telephony platform; • establishing a monitor on a device (i.e. listen for incoming calls); • notification of an inbound alerti... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.1 Discovering the Capabilities of a Telephony Platform | The ECMA-323 Get Switching Function Capabilities service can be used by a voice browser application to determine the features (services and events) that a telephony platform supports. See ECMA-323, clause 11.1.3, for the format of the information provided. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.2 Starting a Monitor (i.e. listening for incoming calls) | In order to receive ECMA-323 call control events, a CSTA monitor must be placed on a telephony endpoint via the ECMA-323 Monitor Start service. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.2.1 Monitor Start - Service Request example | This example shows how a voice browser application places a monitor on an endpoint that is associated with the identifier 22343. Note that by omitting the ECMA-323 optional parameters, the most relevant type of monitoring (a device-type monitor on a device) is requested. ETSI ETSI TR 102 171 V1.1.1 (2003-02) 13 The man... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.2.2 Monitor Start - Service Response example | This example shows the response to the Monitor Start request. The monitorCrossRefID of 99 will be provided in all ECMA-323 events associated with this monitor request. The mandatory Service Response parameters are: • monitorCrossRefIdentifier: this parameter provides a handle to correlate subsequent ECMA-323 events wit... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.3 Notification of an Inbound Call | When an inbound call arrives at a monitored endpoint, an ECMA-323 Delivered event is provided by the telephony platform. The Delivered event contains information about the call such as ANI and DNIS information provided by the network for example. This information enables a voice browser application to determine if it s... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.3.1 Delivered Event example | The event contains the following parameters: • monitorCrossRefID: This parameter represents the handle provided in the Monitor Start response. • connection: This parameter contains connection identifier that is used in CSTA services that are to be applied to this connection (e.g. Answer Call). • alertingDevice: This pa... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.4 Answering an Inbound Call | After the voice browser application is notified of the incoming call it uses the ECMA-323 Answer Call service to answer the call. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.4.1 Answer Call - Service Request example | The mandatory Service Request parameters are: • callToBeAnswered: The connection identifier of the alerting connection. The application uses the contents of the connection parameter provided in the Delivered event. <?xml version="1.0" encoding="UTF-8"?> <AnswerCall xmlns="http://www.ecma.ch/standards/ecma-323/csta/ed2"... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.4.2 Answer Call - Service Response example | The telephony platform provides a positive response to the Answer Call service request. There are no mandatory Service Request parameters. <?xml version="1.0" encoding="UTF-8"?> <AnswerCallResponse xmlns="http://www.ecma.ch/standards/ecma-323/csta/ed2"/> |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.5 Notification of a Connected Call | As the result of the Answer Call service, an ECMA-323 Established event is provided by the telephony platform to indicate that the connection is now in the connected state. If the telephony platform was configured to "auto-answer" the call, the Established event would be the first event sent to the voice browser applic... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.5.1 Established Event example | Since the Established event contains similar information as in Delivered event example, the parameter description sections is omitted. <?xml version="1.0" encoding="UTF-8"?> <EstablishedEvent xmlns="http://www.ecma.ch/standards/ecma-323/csta/ed2"> <monitorCrossRefID>99</monitorCrossRefID> <establishedConnection> <callI... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.6 Clearing a Connection | Once the voice browser application is finished with the call, it sends an ECMA-323 Clear Connection service to the telephony platform. ETSI ETSI TR 102 171 V1.1.1 (2003-02) 16 |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.6.1 Clear Connection - Service Request example | The mandatory Service Request parameters are: • connectionToBeCleared: the connection identifier of the connection to be cleared. The application uses the connection identifier provided by the telephony platform in previous events. <?xml version="1.0" encoding="UTF-8"?> <ClearConnection xmlns="http://www.ecma.ch/standa... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.6.2 Clear Connection - Service Response example | The telephony platform provides a positive response to the Clear Connection service request. There are no mandatory Service Request parameters. <?xml version="1.0" encoding="UTF-8"?> <ClearConnectionResponse xmlns="http://www.ecma.ch/standards/ecma-323/csta/ed2"/> |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.7 Notification of a Cleared Connection | As the result of the Clear Connection service, an ECMA-323 Connection Cleared event is provided by the telephony platform to indicate that the connection is now cleared. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.7.1 Connection Cleared Event example | The event contains the following parameters: • monitorCrossRefID: this parameter represents the handle provided in the Monitor Start response. • droppedConnection: this parameter contains connection identifier of the connection that has been cleared. • releasingDevice: this parameter provides the endpoint identifier of... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.8 Initiating an Outbound Call | A voice browser application can initiate an outbound call by using the ECMA-323 Make Call Service. Before it initiates an outbound call, the application should place a monitor on the originating device, in order to monitor the progress of the call. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.8.1 Make Call - Service Request example (refer to Profile) | In this example, the application wants to establish a call from the device identifier 22343 (on the voice browser platform) to an external device associated with the telephone number 18001234567. The mandatory Service Request parameters are: • callingDevice: the device identifier associated with the calling device on t... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.8.2 Make Call - Service Response example | This example shows the response to the Make Call request. The mandatory Service Response parameters are: • callingDevice connection identifier: this parameter provides the connection identifier that is used to reference the connection in subsequent services. It is also provided in future events associated with the conn... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.9 Outbound Call Event Sequence | This example shows the sequence of events generated as the result of the Make Call service request. The event sequence includes the following events: Originated, Network Reached, Delivered, and Established. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.9.1 Originated Event Example | The Originated event indicates that the calling device (associated with the voice browser platform) is connected to the call. The event contains the following parameters: • monitorCrossRefID: this parameter represents the handle provided in the Monitor Start response. • originatedConnection: this parameter contains con... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.9.2 Network Reached Event | The Network Reached event indicates that the call has encountered a network interface device (CO line, trunk, etc.). The event contains the following parameters: • monitorCrossRefID: this parameter represents the handle provided in the Monitor Start response. • outboundConnection: this parameter contains connection ide... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.9.3 Delivered Event | If the underlying signalling can detect that the called device is alerting, the telephony platform provides a Delivered event. The event contains the following parameters: • monitorCrossRefID: this parameter represents the handle provided in the Monitor Start response. • connection: this parameter contains connection i... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.9.4 Established Event | The Established event is provided by the telephony platform when it detects that the called party has answered the call. The ability to detect that the call device has answered is dependent upon the underlying signalling capabilities. Since the Established event is very similar to the Delivered event, it is not shown i... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.10 Single Step Transfer | A voice browser application can use the ECMA-323 Single Step Transfer service to transfer the caller away from the voice browser platform to another endpoint. In the process of transferring the call, the transferring connection at the voice browser platform is disconnected from the call. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.10.1 Single Step Transfer - Service Request example | The mandatory Service Request parameters are: • activeCall connection: the connection identifier of the transferring connection (connection at the voice browser platform). • transferredTo: the device identifier associated with the transferred to endpoint. <?xml version="1.0" encoding="UTF-8"?> <SingleStepTransferCall x... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.10.2 Single Step Transfer - Service Response example | The telephony platform provides a positive response to the Single Step Transfer service request. The mandatory Service Response parameters are: • transferredCall connection: the connection identifier at the transferredTo connection. <?xml version="1.0" encoding="UTF-8"?> <SingleStepTransferCallResponse xmlns="http://ww... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.11 Notification of a Transferred Connection | As the result of the Single Step Transfer service, an ECMA-323 Transferred event is provided by the telephony platform to indicate that the transferring connection is now cleared and the transferred device is now connected to the transferred-to device. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.11.1 Transferred Event example | The event contains the following parameters: • monitorCrossRefID: this parameter represents the handle provided in the Monitor Start response. • primaryOldCall connection: this parameter contains connection identifier of the connection of the transferring endpoint in the voice browser platform. ETSI ETSI TR 102 171 V1.... |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.12 Deflect | A voice browser application can use the ECMA-323 Deflect service to move a call away from the voice browser platform to another endpoint. |
4bffed8fe31ed1fc1f71e628b4395743 | 102 171 | 6.12.1 Deflect - Service Request example | The mandatory Service Request parameters are: • callToBeDiverted connection: the connection identifier that is to be moved (connection at the voice browser platform). • newDestination: the device identifier associated with the new destination. <?xml version="1.0" encoding="UTF-8"?> <DeflectCall xmlns="http://www.ecma.c... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.