| Send long sms without segmentation doesn't work |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through November 21, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Hany New member Username: Honeywell Post Number: 1 Registered: 07-2009 |
Hi All this is top urgent issue how can i send long sms without segmentation(customer receive long message in multi separated messages) send long message without segmentation checkbox doesn't work. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1055 Registered: 08-2008 |
Hi, I need more information about your configuration. What type of SMSC connection are you using? Are you using an HTTP SMSC connection? (I am guessing that you are because the configuration option that you reference is only in the HTTP SMSC configuration.) If so, who is the provider? For other types of SMSC connections, there are troubleshooting steps that we can take. But HTTP SMSC interfaces are far more limited. You should realise that long SMS messages must always be segmented when actually being sent over the air. What NowSMS does is insert the headers that allow the receiving device to reassemble the message so it appears as one long message. These headers are in the UDH (user data header), so if you are using an HTTP SMSC, your template needs to include an @@UDH@@ parameter. (Or, if you are using an HTTP SMSC interface with "Send long messages without segmentation" checked, then NowSMS sends the whole message to the SMSC in one submission, and the SMSC then has to segment the message and put in these headers in order to send it over the air.) -- Des NowSMS Support | |||
| Hany New member Username: Honeywell Post Number: 3 Registered: 07-2009 |
Hi Des thanks for ur reply i turned to smpp connection now the big problem i face is to send text message to a specific port number UDH like UDH=060504C3500000 in previous nowsms 2006 i receive strange characters eccode problem in nowsms 2008 & 2009 i receive empty mesaage thank you | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1079 Registered: 08-2008 |
Hi Hany, For SMPP connections, there are different encodings expected by different providers ... because the SMPP standard is not specific enough. What you need to do is try some different options under "Advanced Settings" for the SMPP connection in NowSMS, in order to determine which format works best with your provider. Here are the different combinations that you should try: 1.) Use WDP Adaptation - NOT checked Encode long text messages with 7-bit packing - checked Use TLV parameters - NOT checked 2.) Use WDP Adaptation - NOT checked Encode long text messages with 7-bit packing - NOT checked Use TLV parameters - NOT checked 3.) Use WDP Adaptation - NOT checked Encode long text messages with 7-bit packing - NOT checked Use TLV parameters - checked 4.) Use WDP Adaptation - checked Encode long text messages with 7-bit packing - NOT checked Use TLV parameters - NOT checked Unless your SMPP provider has problems handling messages that contain UDH, one of the above should work. For testing each combination of settings, you must press Ok/Ok/Apply in order to save the setting in NowSMS. Then restart the service with the changed settings, and try another message. I have listed the different combinations in the order of which is the most likely to work. (1 is most likely, 2 is next most likely, etc.) -- Des NowSMS Support | |||
