| Sending long messages via SMPP to Nokia 3650 - Fails |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I am trying to send a long sms to a 3650 using the csoft gateway via SMPP (SMPP by: Aldiscon 3.3). I send: http://127.0.0.1:8800/?PhoneNumber=xxxxxxxx&Text=abc+def+ghi+jkl+mno+pqr+stu+vwx yz+abc+def+ghi+jkl+mno+pqr+stu+vwxyz+abc+def+ghi+jkl+mno+pqr+stu+vwxyz+abc+def+g hi+jkl+mno+pqr+stu+vwxyz+abc+def+ghi+jkl+mno+pqr+stu+vwxyz+abc+def+ghi+jkl+mno+p qr+stu+vwxyz+abc+def+ghi+jkl+mno+pqr+stu+vwxyz+abc+def+ghi+jkl+mno+pqr+stu+vw271 &charset=iso-8859-1 (I also get the same problem sending from your web page, and sending with and without the "&charset=iso-8859-1" added) the Nokia 3650 recieves two messages with gibberish: msg1:??1??6???4H?f???7??????:???????x?"???3: R????? ????9?????y=(,???e3??N??k6?????q9hN???w??? ?? r??:?? ?? j?? x????? ???????1??6???4H?f?? msg2: ?o?<.???u?????Aa??D.?Agt????Am????Asz?d???zPX If i try to turn of the 7-bit encoding for long messages, the first message nowsms sends is rejected by the network, the 2nd part is accepted. I am using v5.51 (b20040823) | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3346 Registered: 10-2002 |
If the SMSC only supports SMPP v3.3, then it is possible that it might not understand long messages. Basically, SMPP v3.3 did not have a flag for specifying that a message contains UDH (user data header). However, UDH needs to be used to used for sending long text messages. UDH also needs to be used for practically all types of binary SMS messages like WAP Push, EMS or Nokia Smart Messaging. (Siemens SEO is the only binary message type that comes to mind that doesn't use UDH, although there are probably a few other more obscure formats as well.) When configured for an SMPP 3.3 environment, NowSMS still sets the flag for specifying that UDH is present ... even though this definition was not added until SMPP 3.4. (Many SMSCs that say they support SMPP 3.3 do support this flag, they just don't claim SMPP 3.4 support because they do not support SMPP 3.4's TLV parameters.) Since I'm in the "too much information zone", let's get back to your problem, and I'll make some suggestions. First, are you able to send WAP push messages through this SMSC? Give that a try, sending a simple push message, including some text and any URL. If that works, then this suggests that the SMSC does understand the UDH flag, even if it is an SMPP 3.3 implementation ... so that is good. If the WAP push message does not work, and is received as gibberish, then this suggests that the SMSC does not support UDH, and I would not expect it to be able to handle long messages. You would have to ask your SMSC provider for guidance in this instance. If the WAP push message did work, then try toggling the setting "Encode long text messages with 7-bit packed encoding". And restart the service after changing this setting. If it is still gibberish, do you see a difference in the gibberish? You should also ask your provider if they have guidance for how to send long text messages through their service. -bn | |||
