| Couple of questions: SMSC and Econding |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Saud Abdul Unregistered guest |
Hi, I am testing NowSMS gateway, and have couple of questions that I would like to get an answer from: (1) Since it is possible to configure NowSMS to use different SMSC connections, is it possible to know which SMSC (via SMPP) was used "originally" to send the received SMS? (2) When sending SMS text "dynamically" using a script, how do NowSMS distinguish between normal SMS messages and unicode messages? Do we have to do a programmed check on the text, then use one of the commands provided by NowSMS, or do the Gateway automatically distinguish between the two? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3107 Registered: 10-2002 |
Hi, 1.) I'm not sure if you are asking about how to specify which SMSC is to be used to send an outbound message ... or how to determine which SMSC a received message originated with. So, I will briefly explain both. First the sending: When NowSMS routes a message, it first looks to see if a sender address has been specified for the message submission (normally there is not a sender address specified, unless you submitted the message via HTTP and specified a "Sender=" parameter, or a forced sender address is associated with a particular "SMS Users" account). If a sender address was specified, then NowSMS checks to see if the sender address matches the "Default Sender Address" that is configured for any of the SMSC links (or the "Phone Number" associated with a GSM modem). If NowSMS finds a match, then it will route the message only via an SMSC connection with a matching sender address. If NowSMS did not find a match on the sender address, then it evaluates the recipient address, and it will look to see if it finds a match in the "Preferred SMSC Connection for" recipient address masks associated with any of the SMSC connections. (These recipient address masks can be wildcards such as "+44*" to match any phone number that starts with "+44".) If NowSMS finds a match, then it looks for the longest mask that provides a match, and routes the message via the connection with the longest matching mask. (For example, if you were sending to +441624999999, and you had one connection with a mask of "+44*", and another with "+441624*", then the connection with the mask of "+441624*" would be used as it is a longer match than "+44*".) If there is no match on the recipient address mask, then the message will be routed via any connection that has "Support any outbound message traffic" checked. Second, the receiving: The SMSC should pass through the recipient address as part of the message. (Not just the sender, but also the recipient, which should correspond to your phone number or short code.) We maintain the recipient address as part of the request. In 2-way commands, the recipient is passed as the @@RECIP@@ replaceable parameter. You can even assoicate different 2-way commands with different recipient values. Note: If you are using a GSM modem as the SMSC, NowSMS wants you to specify the phone number of the modem under the "Properties" for the modem on the "SMSC" page. NowSMS then records that phone number as the recipient for messages received over a GSM modem. 2.) The gateway detects it automatically. -bn | |||
