| SMS DCS=3 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Jorge L Soto P New member Username: Jsoto Post Number: 10 Registered: 09-2006 |
Bryce, I have some messages that arrive to my SMPPGateway correctly but when they are send get a Binary=1, DCS=3 configuration, and is not by my system. Example: SMPPDEBUG.LOG 13:55:34:875 (0000040C) <Incoming_IP_Address> --: WaitForResponseSMPP: SMPP Debug: received a submit message 13:55:34:875 (0000040C) <Incoming_IP_Address> <-: 82 byte packet 13:55:34:875 (0000040C) <Incoming_IP_Address> <-: 00 00 00 52 00 00 00 04 00 00 00 00 00 00 01 28 R ( 13:55:34:875 (0000040C) <Incoming_IP_Address> <-: 00 01 01 31 32 31 34 37 37 30 36 38 34 33 00 02 Originator_No. 13:55:34:875 (0000040C) <Incoming_IP_Address> <-: 01 38 30 39 34 34 35 34 31 36 39 00 00 00 00 00 Destination_No. 13:55:34:875 (0000040C) <Incoming_IP_Address> <-: 00 00 00 03 00 10 54 6F 64 6F 20 62 69 65 6E 2E Todo bien. 13:55:34:875 (0000040C) <Incoming_IP_Address> <-: 20 59 20 74 75 3F 02 0B 00 02 0A DB 02 0A 00 02 Y tu? 13:55:34:875 (0000040C) <Incoming_IP_Address> <-: 00 00 SMPPDEBUG.LOG 13:55:35:578 (000001EC) <Outgoing_IP_Address> ->: 00 00 00 4B 00 00 00 04 00 00 00 00 00 00 AB 06 K 13:55:35:578 (000001EC) <Outgoing_IP_Address> ->: 00 01 01 31 32 31 34 37 37 30 36 38 34 33 00 00 Originator_No. 13:55:35:578 (000001EC) <Outgoing_IP_Address> ->: 01 38 30 39 34 34 35 34 31 36 39 00 40 00 00 00 Destination_No. @ 13:55:35:578 (000001EC) <Outgoing_IP_Address> ->: 00 00 00 03 00 15 06 05 04 0A DB 00 00 D4 37 F9 7 13:55:35:578 (000001EC) <Outgoing_IP_Address> ->: 0D 12 A7 CB 6E 17 28 0B A2 D7 7F n ( 13:55:35:593 (000001EC) <Outgoing_IP_Address> --: SMPPSubmitMessage: Got an SMPP response 13:55:35:593 (000001EC) <Outgoing_IP_Address> <-: 23 byte packet How is send: 2007-02-19 13:55:35,45DA2739.req,<Incoming_IP_Address>,Destination_No.,OK -- SMPP - <Outgoing_IP_Address>:3705,SubmitUser=XXXXXX;Sender=+Originator_No.;SMSCMsgId=ec a0bf;Binary=1;DCS=3;UDH=0605040ADB0000;Data=D437F90D12A7CB6E17280BA2D77F | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6907 Registered: 10-2002 |
Hi Jorge, What version of NowSMS? (Older versions did not always understand that SMPP data_coding=3 on a received SMPP packet meant that the text was in ISO-8859-1 encoding.) The message is being converted to binary because the submission includes a TLV parameter to specify that the message should be directed to port 0ADB. NowSMS will convert this to UDH (user data header). And by default, when UDH is present, NowSMS will submit the text over SMPP in 7-bit packed format. If you uncheck "Encode long text messages with 7-bit packed encoding" in the "Advanced Settings" of the SMPP connection, then NowSMS will use standard 8-bit text format together with the UDH. (Although this setting refers specifically to long text messages, it will apply to any text messages that include UDH.) If you want NowSMS to use TLV parameters, just like the submitting SMPP client, check "Use TLV parameters for port numbers and segmentation" under the "Advanced Settings" for the SMPP connection. Changing one or both of those settings should work for you ... different SMPP providers have different ways of handling encoding variations. But there may be an issue if the outbound SMSC connection is using a protocol other than SMPP, because of the DCS=3 issue. There does seem to be a bug in the SMPP server component of NowSMS, which does not properly handle data_coding=3 when optional TLV parameters are specified in the message submission. If the above configuration changes do not resolve your problems, then we should have a patch to fix the data_coding=3 with TLV parameters problem early next week. -bn | |||
