MSPP Unsolicited Event Structures

Fusion NbUP Endpoint uses two MSPP unsolicited event structures:

• MSPEVN_NBUP_INIT

• MSPEVN_NBUP_ERROR

MSPEVN_NBUP_INIT

typedef struct tag_msp_NBUP_INIT
{
    DWORD FilterId; /* NbUP Filter ID (MSP_ENDPOINT_RTPFDX_NBUP)*/
    DWORD status;   /* Success or error condition */
} msp_NBUP_INIT;

MSPEVN_NBUP_ERROR

typedef struct tag_msp_NBUP_ERROR
{
    DWORD FilterId; /* NbUP Filter ID (MSP_ENDPOINT_RTPFDX_NBUP)*/
    DWORD error;    /* Error condition */
} msp_NBUP_ERROR;

MSPP State Machine

For more information, refer to the Dialogic® NaturalAccess™ Media Stream Protocol Processing API Developer’s Manual.

NbUP State Machine

The following illustration shows the NbUP state machine and all the possible transitions:

Note: NbUP states and MSPP states are independent of each other.

NbUP Endpoint Status Query

An application can query the status of the endpoint when it is in Active State (both the RTP and NbUP states must be in Active State). The query returns filter status information in a buffer. For more information, refer to the Dialogic® NaturalAccess™ Media Stream Protocol Processing API Developer’s Manual.

The buffer received with the query response is of type msp_ENDPOINT_RTPFDX_NBUP_STATUS:

typedef struct tag_msp_ENDPOINT_RTPFDX_STATUS {
msp_ENDPOINT_RTPFDX_STATUS rtpfdxstats;  // RTP status
msp_ENDPOINT_NBUP_STATUS          nbupstats;    // NbUP status
} msp_ENDPOINT_RTPFDX_NBUP_STATUS;

typedef struct tag_msp_ENDPOINT_NBUP_STATUS {
    DWORD         mode;
    DWORD         state;
    DWORD         rtptype;
    DWORD         rxPduFrame;
    DWORD         rxCtrlFrame;
    DWORD         txPduFrame;
    DWORD         txCtrlFrame;
    DWORD         rateCtrlError;
    DWORD         timeAlignmentError;
    DWORD         frameLossError;
    DWORD         unexpectedFrameError;
    DWORD         unexpectedPduError;
    DWORD         unknownProcError;
    DWORD         unknownPduError;
    DWORD         crcHeaderError;
    DWORD         crcPayloadError;
} msp_ENDPOINT_NBUP_STATUS;

For more information about the msp_ENDPOINT_RTPFDX_STATUS structure, refer to the Dialogic® NaturalAccess™ Media Stream Protocol Processing API Developer’s Manual.

The following NbUP-related information is returned as part of msp_ENDPOINT_NBUP_STATUS: