| Problem with Huawei USSD Center |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 10, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| KKW New member Username: Kkw Post Number: 31 Registered: 01-2009 |
hi support, currently we using nowsms connecting to the mobile operator ussd gateway and they are going to migrate to new Huawei USSD Center, during the testing we found that nowsms cannot decode the smpp message from the new ussd gateway. below is the data logged in the smsin log 2011-05-31 19:15:42,85269730871,SMPP - 10.2.34.81:5019,Binary=1;DCS=4;Data=2A3138362300;Recip=*186 the ussd text should be *186*186# any idea what config should i change in nowsms ? thx kk | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3200 Registered: 08-2008 |
Hi kk, The problem is that the SMPP data_coding value is 4, which indicates that the data is in a binary format. 2A3138362300 is the raw ASCII code for *186# (followed by a null terminator). However, NowSMS is not decoding this as text because the SMPP data_coding value indicates that the content is binary. (Note: It is also possible that the SMPP data_coding value is 2, which NowSMS converts to 4, as both values indicate SMPP binary data.) Is there any way to change the USSD gateway so that it does not report a data_coding value indicating binary content? -- Des NowSMS Support | |||
| KKW New member Username: Kkw Post Number: 32 Registered: 01-2009 |
Hi Des, checked Huawei API Spec, for deliver_sm they need to use DCS=4 for plain text, for submit_sm they need to use DCS=0 for English, 7-bit coding, DCS=4 for plain text, 8 bit coding and DCS=8 for Chinese, 16-bit coding. is there any config can make nowsms to use those encoding thx kk | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3214 Registered: 08-2008 |
Hi kk, That is crazy. There is a configuration setting that would allow you to send text messages out using DCS=4. To enable this, under the [SMPP - server:port] header, add: TextDCS=4 Handling this on the receiving side is more difficult. I discussed this with our engineering team, and they agreed to provide a simple DCS override for received messages. With an updated version of NowSMS (2011.06.02 or later), under the [SMPP - server:port] header, add: BinaryDCSOverride=0 This means that any messages received via this connection that have an 8-bit binary encoding DCS value will be remapped to a DCS value of 0 for processing. So, they will be interpreted as text. A DCS value of 8 will continue to be interpreted as Unicode. The updated build of NowSMS with this additional parameter setting can be downloaded at http://www.nowsms.com/download/nowsms20110602.zip. -- Des NowSMS Support | |||
| KKW New member Username: Kkw Post Number: 33 Registered: 01-2009 |
Dear Des, thx a lot for yr help, however we tested this new setting seems problem. 1. in smsin log still same 2011-06-03 11:54:51,85269730871,SMPP - 10.2.34.81:5019,Binary=1;DCS=4;Data=2A3138362A3138362300;SMSCRouteName=CMP_USSD3 ;Recip=*186 2. when we enable 2-way to process this sms we get below is sample data logged in the exception log Exception occurred in thread #5 Thread Description: ThreadProcessInboundSMS Friday, June 03, 2011 @ 11:56 AM ------- below pls found the smpp config section in my smsgw.ini [SMPP - XXX.XXX.XXX.XXX:XXXX] BinaryDCSOverride=0 RouteName=XXXXXXXX SMPPVersion=v3.4 UserName=XXXX Password=XXXX SenderAddressOverride=Yes Receive=Yes ReceiveMMS=No UseSSL=No ReceiveSingleConnection=Yes LongSMSAlt=Yes SourceTON=1 SourceNPI=1 DestTON=1 DestNPI=1 SMSCCharset=iso-8859-1 ServiceType=USSD UnicodeDCS=8 TextDCS=4 pls help to check, thx kk | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3219 Registered: 08-2008 |
Hi kk, Something must be wrong in the implementation of this new setting. Can you send me some example messages from your SMS-IN directory? (Attach to reply here or e-mail to nowsms@nowsms.com with Attention: Des in the subject line.) -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3220 Registered: 08-2008 |
Could I also see a list of your 2-way commands? I am suspecting that there may be multiple issues. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3221 Registered: 08-2008 |
And while I'm at it ... an SMSDEBUG.LOG would also be helpful. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3223 Registered: 08-2008 |
Another follow-up ... We did discover that the uploaded version did not include the module with support for the BinaryDCSOverride setting. An update that includes this setting can be found here: http://www.nowsms.com/download/nowsms20110602a.zip However ... this should not have any relation to the 2-way command exception error that you are encountering. I would like to see the message files from the SMS-IN directory, list of 2-way commands, and SMSDEBUG.LOG so that we can understand what problem is occurring there. -- Des NowSMS Support | |||
| KKW New member Username: Kkw Post Number: 34 Registered: 01-2009 |
Dear Des, tested the updated version, the USSD text was decoded as expected, thx a lot however the 2-way problem still there, i have do some more checking found that even no sms incomming to the system, once i enable 2-way already have exception logged. like below Exception occurred in thread #7 Thread Description: ThreadProcessBulkQ Tuesday, June 07, 2011 @ 1:05 PM ------- Exception occurred in thread #6 Thread Description: ThreadProcessBulkQ Tuesday, June 07, 2011 @ 1:05 PM ------- Exception occurred in thread #6 Thread Description: ThreadProcessInboundMMS Tuesday, June 07, 2011 @ 1:07 PM ------- Exception occurred in thread #5 Thread Description: ThreadProcessInboundSMS Tuesday, June 07, 2011 @ 1:07 PM ------- Exception occurred in thread #6 Thread Description: ThreadProcessInboundMMS Tuesday, June 07, 2011 @ 1:07 PM ------- Exception occurred in thread #5 Thread Description: ThreadProcessInboundReceipts Tuesday, June 07, 2011 @ 1:07 PM ------- Exception occurred in thread #11 Thread Description: ThreadProcessBulkQ Tuesday, June 07, 2011 @ 1:07 PM ------- Exception occurred in thread #5 Thread Description: ThreadProcessBulkQ Tuesday, June 07, 2011 @ 1:08 PM ------- Exception occurred in thread #5 Thread Description: ThreadProcessInboundReceipts Tuesday, June 07, 2011 @ 1:08 PM ------- Exception occurred in thread #14 Thread Description: ThreadProcess2WayMMS Tuesday, June 07, 2011 @ 1:08 PM ------- Exception occurred in thread #9 Thread Description: ThreadProcessBulkQ Tuesday, June 07, 2011 @ 1:08 PM ------- my 2-way testing setting as below : ReceiveSMSCommand1=* c:\winnt\system32\cmd.exe /c echo @@FULLSMS@@ Yes * pls help to take a look, thx kk | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3238 Registered: 08-2008 |
Hi kk, That's why I want to see the message files that are in your SMS-IN directory. And an SMSDEBUG.LOG. I can't even begin to guess what the problem is that you are experiencing. (Attach as reply here or e-mail to nowsms@nowsms.com with Attention: Des in the subject line.) -- Des NowSMS Support | |||
| KKW New member Username: Kkw Post Number: 35 Registered: 01-2009 |
Hi Des, i emailed those file to nowsms@nowsms.com with Attention: Des in the subject line, there is only one file in the SMS-IN folder, pls help to take a look. thx kk | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3243 Registered: 08-2008 |
Hi kk, Oops. We broke some issues related to SMPPOptions handling in 2-way command processing beginning with the 2011.05.23 update. The following update fixes this problem: http://www.nowsms.com/download/nowsms20110608.zip -- Des NowSMS Support | |||
| KKW New member Username: Kkw Post Number: 36 Registered: 01-2009 |
Hi Des, tested the update and problem fixed, thx a lot kk | |||
