1.16. Overlap Send

When using Springware boards, to activate the overlap send feature that prevents the automatic sending of a Sending Complete IE within the SETUP message, parameter 0024 in the firmware PRM file must be set to a value that includes the bit represented by the value 08H. See Table 55, Modifiable Protocol Parameters for more information.

When using DM3 boards, to activate the overlap send feature that prevents the automatic sending of a Sending Complete IE within the SETUP message, the following modifications should be made to the CONFIG file for the desired outbound protocol variant requiring overlap send support. The CalledNumberCount parameter, which has a default value of zero, should be set to a large positive value. For example, in the ISDN Protocol Variant Definitions section of the CONFIG file being used, change:

    Variant CalledNumberCount 99 

Note: You can have more than one CalledNumberCount setting per board, in order to do so, create a new Variant Define and apply that define using the defineBSet command in the respective TSC section.

See the configuration information for DM3 products provided with the system release software for more information on how to perform the changes outlined above.

A gc_MakeCall( ) function call that specifies fewer digits than the CalledNumberCount results in the sending of a SETUP message that does not contain a Sending Complete IE. If more digits are specified, the Sending Complete IE is included in the SETUP message.

The gc_SendMoreInfo( ) function is not supported, so to send extra digits, the application should wait for the GCEV_SETUP_ACK event, which indicates the inbound side acknowledges the SETUP message, construct an IE block containing the digits to be sent, and then call gc_SndMsg(GlobalCallDeviceHandle, CRN, SndMsg_Information, &IEBlock) to send the digits. Even after sending a number of digits greater than CalledNumberCount, the Sending Complete IE is not sent automatically.

The following is an example of how to send extra digits using overlap send:

void mdfSendOverlap(CH_INFO_PTR chanInfop, char* digits)
{
    IE_BLK info;
    GC_IE_BLK gcInfo;
    char length;
    unsigned char type = 0x00;
    unsigned char plan = 0x00;
    for(length = 0; ; length++, digits++)
    {
        if(*digits)
        {
            info.data[3 + length]= *digits & 0x7F; // Bit 8 set to 0
        }
        else
        {
            break;
        }
    }
    info.data[2] = 0x80|plan|(type<<4); // Octet 3: Number Type + Numbering Plan
    info.data[1] = length + 1; // Octet 2: Element Length
    info.data[0] = 0x70; // Octet 1: Called Number ID
    info.length = length + 3; // Information block
    gcInfo.gclib = NULL;
    gcInfo.cclib = &info;
    if(gc_SndMsg(chanInfop->hGC, chanInfop->crn, SndMsg_Information, &gcInfo)< 0)
    {
        mdfError(EGCALL, chanInfop, "gc_SndMsg (SndMsg_Information) failed "
                 "CRN: 0x%X", chanInfop->crn);
    }
} 

Note: Any changes to the CONFIG file for a particular protocol requires the regeneration of the FCD file and the subsequent downloading of the firmware to the boards. The FCDGEN tool, available in the dialogic\bin directory, is used to convert a CONFIG file to an FCD file.

Click here to contact Telecom Support Resources