| Long messages in particular smsc give wrong broken text on receive |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through November 21, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| medium kuriboh New member Username: Mediumkuriboh Post Number: 7 Registered: 04-2008 |
We are connected to differents smsc, i have a problem with sending long messages on one of them. using the nowsms webinterface, i sent a long message (267 caracters/2 msgs), that doesn't include any special caracter, i got broken message on receive, while sending the same message on the other smsc (different provider) will give the good results. Actually nowsms has the same config for both smsc, what could be wrong. If i use DCS=8 and send encoded text (original text = arabic), the limit of message appears like if it is 250 caracters (of original arabic text), so the text is sent right but it is cut. So what can i do to fix the problem? Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 282 Registered: 08-2008 |
Hi, Are these SMPP connections? For the first instance, I assume you are sending regular English/Latin text, correct? Because of ambiguity in the SMPP specfication, different SMSCs may have different expectations of how the message should be encoded. Under "Advanced Settings" for the SMPP SMSC connection in NowSMS, there is an option titled "Encode long text messages with 7-bit packed encoding". If long text messages arrive as "garbage", then try changing the value of this setting. There is no right or wrong choice for this setting, you just have to pick checked or not checked, depending on what works with your provider. If you are having problems with long messages using Arabic (or other Unicode) text, then this option would have an effect. However, there is another setting, "Use TLV parameters for port numbers and segmentation", which some providers might want to use. (When "Use TLV" is NOT checked, NowSMS builds the GSM UDH for segmentation and includes it in the message. When "Use TLV" is checked, NowSMS uses SMPP TLV parameters to indicate segmentation.) With most providers, "Use TLV" NOT checked is the preferred solution ... but some providers may want you to use the TLV parameters instead of using GSM UDH headers. Another setting that is relevant to long text messages in some environments is "Use WDP Adaptation for WAP Push and MMS notifications (required for CDMA)". While this setting primarily applies for WAP Push message, it also has a side effect for long text messages. If this setting is checked, then NowSMS will not segment the message before submitting it to the SMSC. Instead, NowSMS will submit the entire long message to the SMSC in one submission, using the SMPP TLV message_payload parameter. It is then expected that the SMSC will perform the segmentation. Unfotunately, there is no right choice for any of these parameters. The defaults are right for the majority of SMPP providers. However, some providers may have different preferences, and only "trial and error" can determine which settings are right for a particular provider. If you have a long Arabic text message that is truncated at 250 characters, then your provider might have a limit on the number of message segments that they support. For a Unicode message, you can fit 70 characters in a single message, or 67 characters per segment in a multipart message. There is some more detail on limits here: http://blog.nowsms.com/2007/06/long-sms-text-messages-and-160.html -- Des NowSMS Support | |||
