| Email to SMS , with Dynamic Sender ID |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 22, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| DJXLoRd New member Username: Djxlord Post Number: 24 Registered: 01-2004 |
Hi , I was wondering how is it possible to define a Dynamic Sender ID when Sending Email to SMS. On a different note , all Email to SMS being Sent via "Authorized Domains" and not from defined SMS/MMS user list are being submitted Via "localsystem-mmsc" User , how is it possible to track the usage of such built in User as this may lead to issues in Accounting of SMS Usage. regards. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 103 Registered: 08-2008 |
Hi, The SMSOUT-yyyymmdd.LOG does seem to record SMTP sender information. But, this information not in any of the HTTP accounting callbacks. Are you using the HTTP accounting callbacks or the log files? -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 104 Registered: 08-2008 |
Sorry, I missed the first part of your question. You can associate different sender addresses with different authorized users/domains. When you define an address on the authorized list, you can optionally follow the address with a comma (,) and the SMS sender address that should be used for messages sent by this e-mail address. For example: *@nowsms.com,11111 -- Des NowSMS Support | |||
| Pratik Chauhan |
Hi Team, I explored email to sms option of Nowsms. Email is sent in the form of sms and nowsms gateway sends multiple sms as defined if email length is more than 160 bytes but data coding of email is binary so although sms is received by smsc/handset they can not read it as it is not in readable format. Is there any way so email will be sent in plain text without any binary coding?? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 221 Registered: 08-2008 |
Hi, Long text messages need to be sent out with binary information to indicate message concatenation so that the receiving handset can reassemble the message. That said, different SMSCs have different ways of dealing with this type of binary message. Forget about e-mail for a minute. For testing, send messages from the NowSMS web interface. If you are using an SMPP connection to your SMSC, go into "Properties" for the SMPP connection from the "SMSC" list in NowSMS. Under "Advanced Settings", change the setting for "Encode long messages with 7-bit packed encoding". Some SMSCs want long messages 7-bit packed, some don't. You basically need to experiment to see which setting your SMS provider wants you to use. If you are using an HTTP SMSC connection ... under "Properties" for the SMSC connection, there are two relevant options. Checking "Send long messages without segmentation" tells NowSMS not to segment the message when submitting to the SMSC. So the long message will go out as a text message without any segmentation. Or if "Use 7-bit binary encoding for long messages" is UNchecked, the message will go out as text, but it will include the necessary UDH for segmentation, if your text template includes a @@UDH@@ variable (and if your provider supports it). For other types of SMSCs, there are other relevant configuration settings. But as other SMSC types are less common, chances are that one of the above recommendations will address your issue. If not, please explain your SMSC connection. -- Des NowSMS Support | |||
