Microsoft KB Archive/308663

= SMPP Commands That Must Be Implemented for Interoperability with Mobile Information Server Carrier Edition =

Article ID: 308663

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Mobile Information Server 2001 Enterprise Edition

-



This article was previously published under Q308663



SUMMARY
The Short Message Service (SMS) Connector module is a component of Mobile Information Server Carrier Edition and communicates with the SMS Center (SMSC) at the carrier. One of the SMSC protocols that Carrier Edition supports is Short Message Peer to Peer (SMPP) v3.3. This article describes the subset of SMPP v3.3 commands that must be implemented by an SMSC so that Carrier Edition can interoperate with the SMSC.

For each SMSC account, the SMPP protocol uses two TCP/IP connections, both initiated by Carrier Edition. When the SMPP session starts, Carrier Edition opens two TCP/IP connections to the SMSC. One connection is used to transmit data, the other one to receive data.



Commands from Mobile Information Server Carrier Edition to SMSC
This section describes the commands Mobile Information Server Carrier Edition sends to the SMSC.  bind_receiver: All bind_receiver parameters are configurable from the Mobile Information Server System Manager user interface (UI). bind_transmitter: Same as for bind_receiver. unbind: When Carrier Edition logs out from an SMSC account, it sends an unbind command on the RX channel. Carrier Edition will not send an unbind on the TX channel. submit_sm

 submit_multi: Not implemented deliver_sm_resp: Message ID is &quot;\0&quot; query_sm: Not implemented</li> query_last_msgs: Not implemented</li> query_msg_details: Not implemented</li> cancel_sm: Not implemented</li> replace_sm: Not implemented</li> enquire_link: Carrier Edition sends enquire_link periodically on both TX and RX connections. Carrier Edition expects enquire_link_resp as response. The interval is configurable through the UI. Note that the enquire link interval always is a multiple of the timeout interval.</li> enquire_link_resp: Sent back when Carrier Edition gets an enquire_link request from the SMSC. Carrier Edition does not require this.</li> generic_nak: Implemented</li></ul>

Commands from SMSC to Mobile Information Server Carrier Edition
This section describes how Mobile Information Server Carrier Edition reacts on commands sent from the SMSC.
 * bind_transmitter_resp: Must be returned as response to bind transmitter. System_id is logged, but ignored.
 * bind_receiver_resp: Must be returned as response to bind transmitter. System_id is logged, but ignored.
 * unbind_resp: Must be returned as a response to an unbind.
 * submit_sm_resp: Carrier Edition does not use status report and will not use the ID sent in the submit_sm_resp command.
 * submit_multi_resp: Not implemented
 * deliver_sm
 * query_sm_resp: Not implemented
 * query_last_msgs_resp: Not implemented
 * query_msg_details_resp: Not implemented
 * cancel_sm_resp: Not implemented
 * replace_sm_resp: Not implemented
 * enquire_link: Carrier Edition will handle an enquire_link command. Carrier Edition does not require the SMSC to send enquire_link commands to work.
 * enquire_link_resp: When the SMSC gets an enquire_link command from Carrier Edition, the SMSC must respond with an enquire_link_resp as response.
 * generic_nak: Handled by Carrier Edition if the command header is invalid.

Sequence numbers in the command header must be implemented according to specification.

Keywords: kbinfo KB308663

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.