One of the standard capabilities of NowSMS is the automatic mapping of receipt message IDs when routing messages to an upstream SMSC connection.
The reasoning/logic is simple. When NowSMS accepts a message from a client, NowSMS needs to assign an ID to the message.
When the message gets routed to an upstream SMSC, that SMSC will assign a new message ID.
NowSMS saves the message ID assigned by the upstream SMSC, so that if a delivery receipt message is received, NowSMS can translate the upstream message ID back to the NowSMS assigned message ID before it is delivered back to the client that submitted the message to NowSMS.
Message IDs are not globally unique. NowSMS maintains a separate receipt message ID tracking database for each SMSC connection. For situations where there are multiple connections to the same SMSC (same host name or IP address and port number), NowSMS automatically shares the same message ID tracking database over all matching connections. This is because it is possible that the SMSC might return a delivery receipt over any of the connections to that SMSC.
A problem can occur if multliple connections to the same SMSC exist, but with a different host name, IP address or port number.
There is a way to configure NowSMS to use the same receipt message ID database for multiple connections. This should only be done when you are connecting to an SMSC via multiple IP addresses where you are certain that the SMSC shares a message ID space across the IP addresses.
To enable this, it is necessary to edit the SMSGW.INI file.
Under the [SMPP - server:port] section header for each connection that shares the same receipt message ID namespace, add TrackSMPPReceipts=somename
“somename” can be any text that makes sense to you. NowSMS will group together receipt message ID tracking for all connections that share the same TrackSMPPReceipts value.
Related pages:
- Multiple SMPP Connections to One SMSC Although it is possible for SMPP Asynchronous connections to process hundreds of SMS messages per second, sometimes there are performance gains by...
- Using NowSMS as an SMPP Server for Another Application One of the more unusual features of NowSMS is its ability to operate as an SMPP server. NowSMS can relay...
- NowSMS Update – Interim Release 2010.05.07 An interim update release of NowSMS is available for download at http://www.nowsms.com/download/nowsmsupdate.zip. The most interesting updated features/capabilities include: Major SMS...
- Configuring SMSC Connections The Now SMS & MMS Gateway requires a connection to an SMSC (Short Messaging Service Centre) to interface with SMS...
- International Prefix Conversion for SMS There are many situations where end users submit messages using local number formats, but the upstream SMSC connection requires that...
- Dynamic SMS Message Routing with HTTP Callbacks If you need control over routing to particular SMSC connections, the logic that NowSMS uses for SMS message routing is...
- SMS Routing Logic For the sake of clarity, this section will define the routing logic that NowSMS uses to determine which connection should...
- MMSC MM4 Interconnection Basics MM4 is the standard protocol that is defined for connecting together two or more MMSCs. MM4 is an SMTP based...
- Routing Options The “Routing Options” dialog for a modem connection contains a field to set the Phone Number of the GSM modem...
- Routing SMS messages to a Specifc SMSC Route If you need control over routing to particular SMSC connections, the logic in NowSMS works like this: When NowSMS routes...
Topic Category: delivery receipts, SMPP
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...
Click here to download a free trial version of NowSMS & MMS Gateway, NowSMS Lite or NowWAP Gateway.
Learn more about NowSMS Lite.