5.10. TERM_NACK_BLK

When using DM3 boards, the TERM_NACK_BLK data structure is not supported.

When using Springware boards, the TERM_NACK_BLK data structure is used to cast terminal initialization event data after a CCEV_RCVTERMREG_NACK event is received. TERM_NACK_BLK contains the cause value for the event, indicating why the terminal initialization request was rejected by the network.

The data structure is defined as follows:

/* 
 * Structure for CCEV_RCVTERMREG_NACK Event.
 */   
typedef struct
{
   DLINK data_link;
   byte  cause_value;
} TERM_NACK_BLK; 

Table 50. TERM_NACK_BLK Field Descriptions

Field	Description
data_link	The DLINK data structure; see Section 5.5, DLINK.
cause_value	The Cause Value defined in isdncmd.h. (For a listing of Cause Values associated with a CCEV_RCTERMREG_NACK event. See Table 51 below.

The following table lists the possible cause values that may be returned in the TERM_NACK_BLK data structure after receiving a CCEV_RCVTERMREG_NACK event. Any values provided by the Network that are not listed in the table will also be passed up to the application.

Table 51. Cause Values Associated with CCEV_RCVTERMREG_NACK

Cause Value	Q.850 Description	Meaning
0x26	Network out of order	Used when the network has removed the TEI, causing the data link to go down.
0x63	Information element/parameter non-existent or not implemented	Switch does not support endpoint initialization.
0x64	Invalid information element contents	SPID was most likely coded incorrectly.
0x66	Recovery on timer expiry	Application tried two attempts at initialization with no response from the network.
0x6F	Protocol error, unspecified	Used when no cause was given for the rejection.

Click here to contact Telecom Support Resources