1.10. Service Request (BRI Only)

Note: The following information applies when using Springware boards only. DM3 boards do not support the service request feature.

In BRI North American terminal initialization, the terminal equipment (TE) registration request goes to the network side. The firmware sends the information on its own. The application, when used as the Network side, receives a GCEV_SERVICEREQ event as notification of a TE registration request. On receiving this event, the application evaluates the Service Profile Interface ID (SPID) received and either rejects or accepts the registration request. The application then conveys its result to the network using the gc_RespService() function to send a GCEV_SERVICERESP event to indicate whether the request is accepted or rejected. If the request is accepted, the terminal is then fully initialized.

Note: The gc_RespService( ) function can be called on a board device handle only.

Global Call also defines the gc_ReqService( ) function which is not used for ISDN protocols. The device registration is automatically generated when the device is initialized, so the Service Request feature is essentially used in a response-only manner by the network side.

The following sections describe the gc_RespService() function as it relates to ISDN and the corresponding events. The set and parameter IDs are described in Chapter 4, ISDN-Specific Parameter Set Reference.

Click here to contact Telecom Support Resources