Previous PageTable Of Contents../index.htmlIndexNext Page

cc_TermRegisterResponse( )

Description | Cautions | Example | Errors | See Also

Name:

int cc_TermRegisterResponse(linedev, data_blk_ptr)

Inputs:

LINEDEV linedev

  board device handle

 

TERM_BLK data_blk_ptr

  pointer to the terminal initialization block data to be sent to the firmware

Returns:

0 on success
< 0 on failure

Includes:

isdncmd.h

Category:

System tools

Mode:

asynchronous

Technology:

BRI/SC

Top Of PageDescription

The cc_TermRegisterResponse( ) function sends a response for CCEV_TERM_REGISTER events. The application, when used as the Network side, receives this event as notification of a TE registration request. On receiving the CCEV_TERM_REGISTER 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 cc_TermRegisterResponse( ) function to send either the CCEV_RCVTERMREG_ACK event, if the request is accepted, or the CCEV_RCVTERMREG_NACK event, if the request is rejected. If the request is accepted, the terminal is then fully initialized.

Refer to the Call Scenarios in Appendix A for the sequence of events and function calls required for BRI North American terminal initialization. For additional information, refer to the North American BRI Terminal Initialization with Dialogic Products application note; the note can be downloaded from the Application Notes section of the Dialogic FirstCall Info Server website: http://support.dialogic.com

Parameter

Description

linedev:

The line device handle of the D channel Board.

data_blk_ptr:

Pointer to the data block TERM_BLK to be sent to the firmware. For a description of the TERM_BLK structure, see Section 6.12. TERM_BLK.

The data associated with the terminal initialization events can be retrieved using sr_getevtdatap( ) and casting the value to data types associated with the received event. The types of data structures that are used to cast the event-associated data are provided in Table 28 below.


Table 28. Terminal Initialization Events and Data Structures

Event

Type of Data Structure

CCEV_TERM_REGISTER

SPID_BLK
(See Section 6.11. SPID_BLK for a description of this structure.)

CCEV_RCVTERMREG_ACK

USPID_BLK
(See Section 6.15. USPID_BLK for a description of this structure.)

CCEV_RCVTERMREG_NACK

TERM_NACK_BLK
(See Section 6.13. TERM_NACK_BLK for a description of this structure.)

NOTE:
The North American terminal initialization events all occur on a board level device, not a channel device. The handlers for these events must be registered on the board level device. Refer to the Voice Software Reference -- Standard Runtime Library for information on the sr_enblhdlr( ) function.

Top Of PageCautions

Top Of PageExample

Top Of PageErrors

If the function returns a value < 0 to indicate failure, use the cc_CauseValue( ) function to retrieve the reason code for the failure. The cc_ResultMsg( ) function can be used to interpret the reason code. Error codes are defined in the files ccerr.h, isdnerr.h, and isdncmd.h.

Error codes from the cc_TermRegisterResponse( ) function include the following:

Error Code

Description

ERR_ISDN_LIB | E_ISBADIF

Bad interface number

ERR_ISDN_LIB | E_ISNOMEM

Cannot map or allocate memory

Top Of PageSee Also


Previous PageTable Of ContentsTop Of PageIndexNext Page

Click here to contact Dialogic Customer Engineering

Copyright 2001, Dialogic Corporation
All rights reserved
This page generated December, 2001