# Sending commands to TPKT endpoints

Applications can change settings specified in the msp_TPKT_ENDPOINT_CONFIG structure by using mspSendCommand. When invoking mspSendCommand for TPKT endpoints, application specify an MSPP handle associated with a TPKT endpoint, the endpoint ID (the MSP_ENDPOINT_TPKT parameter for TPKT endpoints), and an endpoint command ID (MSP_CMD_TPKT_CONFIG for TPKT endpoint commands). Applications then use the mspBuildCommand macro to concatenate the endpoint ID and command ID, while specifying the location of a buffer that includes the parameter values to set for the endpoint.

When an application wants to re-configure an TPKT endpoint, it must disable the endpoint before sending it new configuration information.

Applications specify the TPKT parameter values in a msp_TPKT_ENDPOINT_CONFIG structure that contains the following information:

Name | Description
localSessionID | Local session ID.
localSessionSeq | Sequence number for detecting session overlap (0 | 1).
remoteSessionID | Remote session ID.
remoteSessionSeq | Sequence number for detecting session overlap (0 | 1).
deliveryMethod | Session delivery method (simple or complex).
remoteGatewayIP | Destination gateway for this session.
coderType | TPKT endpoint vocoder type.

For more information about sending commands to MSPP endpoints, refer to the Dialogic® NaturalAccess™ Media Stream Protocol Processing API Developer's Manual.