| Send Voice Mail Notifications problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| lge New member Username: Lge Post Number: 7 Registered: 02-2007 |
Test as follows in Now SMS2006 Send Voice Mail Notifications - Set or Clear Message Waiting Indicator : Set VoiceMail - Tex t : 1abcdefghijklmnopqrstuvwxyz (27 bytes) => reception : Whole character that break - Text : Test . Test . Test . (17 bytes) => reception : Whole character breaks SMSWEB LOG 2007-04-18 18:34:06,203.247.145.11,,4625DCEF.req,VoiceMail SMSOUT LOG 2007-04-18 18:34:07,4625DCEF.req,203.xxx.yyy.zz,22112259,OK -- SMPP - 203.xxx.yyy.zz:6204,Sender=+821029991114;SMSCMsgId=100ED23;Binary=1;DCS=D8;UDH=0 401020001;Data=C4C2E231B96C3EA3D3EA35BBED7EC3E3F239BD6EBFE3F37A Please answer me your solution. | |||
| lge New member Username: Lge Post Number: 8 Registered: 02-2007 |
Hi, I did 'Send Voice Mail Notifications' test in Now SMS 2006 again. - Phone Number → 22112259 - Set or Clear Message Waiting Indicator → Set VoiceMail - Message Waiting Count: (optional) → None - Text(Input) : → Text : Test. Test. Test. (17 bytes) => reception : Test. Test. Tes (15 byte) - Text(Input) : → 1abcdefghijklmnopqrstuvwxyz (27 bytes) => reception : 1abcdefghijklmnopqrs (20 byte) ▶ SMSOUT.LOG 2007-04-19 17:29:47,4625DF24.req,127.0.0.1,22112259,Retry Pending - Unknown Error 00000009 -- SMPP - 203.229.247.33:6208,Sender=+821029991115 2007-04-19 17:30:13,46271839.req,127.0.0.1,22112259,OK -- SMPP - 203.229.247.33:6208,Sender=+821029991115;SMSCMsgId=1007CE9;Binary=1;DCS=D8;UDH=0 401020001;Data=D0CB73BA0B442FCFE92E10BD3CA7BB00 ▶ SMSDEBUG.LOG 17:29:47:640 [3] ThreadProcessModem: Processing 4625DF24.req... 17:29:47:640 [3] ThreadProcessModem: Error: Unknown Error 00000009 17:30:12:671 [8] ThreadProcessConnection: Processing connection from 127.0.0.1... 17:30:12:671 [8] ThreadProcessConnection: Processing request /Send%20Voice%20Mail%20Notification.htm?PhoneNumber=22112259&VoiceMail=On&VoiceM ailMessageCount=&Text=test.+test.+test.&Submit=Submit 17:30:12:671 [8] Debug: 1 recipient entries 17:30:12:687 [8] ThreadProcessConnection: Request processing complete 17:30:12:703 [8] ThreadProcessConnection: Processing connection from 127.0.0.1... 17:30:12:703 [8] ThreadProcessConnection: Processing request /wait.js 17:30:12:703 [8] ThreadProcessConnection: Request processing complete 17:30:12:734 [8] ThreadProcessConnection: Processing connection from 127.0.0.1... 17:30:12:734 [8] ThreadProcessConnection: Processing request /progress_forward.html 17:30:12:734 [8] ThreadProcessConnection: Request processing complete 17:30:12:968 [8] ThreadProcessConnection: Processing connection from 127.0.0.1... 17:30:12:968 [8] ThreadProcessConnection: Processing request /progress.html 17:30:13:015 [8] ThreadProcessConnection: Request processing complete 17:30:13:671 [3] ThreadProcessModem: Processing 46271839.req... ▶ The following is 4625DF24.ERR in NOW SMS Q folder [SMS] SubmittedBy=127.0.0.1 PhoneNumber=22112259 Data=00A50065497400A5D96100A5CFE51825596D00A5796C003F00A55E2559FF002000A55BE5094 500A5BFE5396E00A5596000A55A7F002000A55D25896C003F00A559659FE000A5F96D00A5496500A 559FF002000A5397100A5196C00A5C96100A55BE5A96900A5297800A5F96F00A5EB21002D pid=00 dcs=08 Binary=1 ASAP | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7119 Registered: 10-2002 |
I do not encounter any problems sending the messages that you describe. Do you have problems sending other types of messages? There is a setting that might also make a difference. Under "Advanced Settings" when defining the SMPP connection in NowSMS, try different settings for "Send long text messages with 7-bit packed encoding". While you are not sending a long text message, this setting controls how NowSMS encodes the message for SMPP when the message includes UDH. Perhaps the current value for this setting is not what the SMSC expects. Do long text messages work alright? If changing this setting does not work, then I am suspicious that maybe because this is an unusual message encoding, that your SMSC is getting confused. I tried here with several different SMSC connections, and the message was delivered properly in my tests. -bn | |||
| lge New member Username: Lge Post Number: 9 Registered: 02-2007 |
I already setting "Send long text messages with 7 - bit packed encodings". Under "Advanced Settings" the SMPP connection in NOW SMS2006 and uniformity problem happens always ASAP | |||
| lge New member Username: Lge Post Number: 10 Registered: 02-2007 |
HI, I collected Packet Data at middle point of 'SMSC' path in 'NOW SMS'. 1. The following is 'Send Text Message' Test result Packet Data of Data Coding => SMPP Data Coding Scheme: UCS2 (ISO/IEC-10646) (0x08) 2. The following is 'Send Voice Mail Notification' Test result. ----Data------------------ Data coding: 0xd8 SMPP Data Coding Scheme: Unknown (0xd8) GSM SMS Data Coding 1101 .... = DCS Coding Group for SMS: SMS DCS: Message Waiting Indication - Store Message (GSM 7-bit default alphabet) (0x0d) ..0. .... = DCS Text compression: Uncompressed text ...1 .... = DCS Class present: Message class is present .... 10.. = DCS Character set: UCS-2 (16-bit) data (0x02) .... ..00 = DCS Message class: Class 0 (0x00) GSM CBS Data Coding 1101 .... = DCS Coding Group for CBS: CBS DCS: Reserved (0x0d) Predefined message: 0 Message length: 21 Message GSM Short Message Service User Data UDH Length: 4 IE Id: SMS - Special SMS Message Indication (0x01) Short Message body I am something want to know 'SMPP Data Coding Scheme'. ASSP | |||
| lge New member Username: Lge Post Number: 11 Registered: 02-2007 |
Please answer me your solution? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7170 Registered: 10-2002 |
I'm sorry ... I can't provide you an answer ... because I do not understand the question. If we go back to your original post, I do not understand what you mean by "Whole character that break". It is very possible that your SMSC does not understand this encoding. After all, I see that the software you are using to decode the packet also does not understand it. The GSM SMS Data Coding Scheme (DCS) is defined in ETSI GSM 03.38. For D8, the high bits 1101 (D) mean the following definition applies:
So, we are setting bit 3 = inidication active ... bit 2, 1 and 0 are all clear, indicating this is a voicemail message waiting. The message text is encoded in the default alphabet ... which is a little vague, but the specification continues:
It is very possible that your SMSC does not understand this DCS encoding value. I note that the decoding software that you are using thinks that because bit 3 is set, that the character set is UCS-2 (Unicode) ... and your SMSC might be making the same mistake. To test this theory, you could try including a Unicode character in the text of the notification. This will cause NowSMS to change the DCS to E8, which means the same type of voice mail notification, but that the text is in Unicode.
In summary ... I do not understand exactly what you are saying is not working properly. I believe NowSMS is performing the message encoding correctly. It is possible that your SMSC does not understand the encoding for this message, because it is unusual. All I can think to suggest is to try with "Send long text messages with 7 - bit packed encodings" checked, and with it UNchecked. The SMSC might understand one of these settings. -bn | |||
