How can i read the arabic SMS Submitted from the Log files | Search |
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through November 21, 2009 ⬆ |
◄ ► |
Author | Message | |||
Mexcano New member Username: Mexcano Post Number: 14 Registered: 02-2009 |
Dear All, i need your support to know how to read the submitted Arabic SMS from the log files as it appear at follow SMSCMsgId=2b5e9f2;Binary=1;DCS=F5;UDH=0B05040B8423F00003930301;Data=93062F1F2DB6 91819246414336394338313539364431344641344146394236393842424439364438333345353039 37323500030B6A1245746973616C617420574150004E41503200C54601C6560187070683000101C6 5501871106830D01870706830001871006AB018708060365746973616C61740001870906890101C6 5101 | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1235 Registered: 08-2008 |
Hi Mexcano, This was changed in NowSMS 2009, where we changed the log files and accounting callbacks to report all Unicode and long text messages using UTF-8 text encoding instead of the binary data. In earlier versions, you would need to decode it manually. -- Des NowSMS Support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1236 Registered: 08-2008 |
One more note Mexcano ... I just took another look at your log file entry and noticed that its DCS is not a Unicode DCS. That is a binary message DCS. From the looks of it, that is a WAP push message. Actually, it looks like some sort of OMA OTA message being sent over WAP push, as I can see that it is signed with a USERPIN. For WAP push and all OTA related messages, the log files only show the binary encoded data. -- Des NowSMS Support | |||
Mexcano New member Username: Mexcano Post Number: 15 Registered: 02-2009 |
Hi Des Thank you for your support but i need urgent solution to read the submitted Arabic SMS from the log files any solution if it possible | |||
Mexcano New member Username: Mexcano Post Number: 16 Registered: 02-2009 |
Hi Des i always face problem while using now sms 2008 or 2009 as i got always error SMS Failed and the error log is "ERROR: TCP/IP Error sending data to server -- SMPP" while another SMS sent successfully | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1240 Registered: 08-2008 |
Hi Mexcano,
The message you referenced above is a WAP Push SMS. It is NOT an Arabic SMS. NowSMS 2009 will display Arabic SMS in the SMSOUT-yyyymmdd.LOG with regular Arabic characters (encoded as text with UTF-8 character set).
This usually means that the SMPP server is closing its connection unexpectedly. The normal behaviour is that NowSMS reconnects and retries the message. If you are seeing this message a lot, then the most common cause is that your SMPP provider wants you to send "enquire link" messages more frequently. By default, NowSMS sends them every 58 seconds (a typical provider timeout is 60 seconds, so we send just a little more frequently than required). To change this frequency, edit the SMPP connection in the "SMSC" list, and under "Advanced Settings", change the "Keep Alive interval" number of seconds. If that doesn't solve the problem, then I need to know how frequently this error occurs. Is there a pattern to the error? -- Des NowSMS Support | |||
Mexcano New member Username: Mexcano Post Number: 17 Registered: 02-2009 |
Hi Des i make the Alive interval 10 sec and it got this error message "[SMS] SubmittedBy=10.10.10.10 PhoneNumber=XXXXXXXXXXXXXXXX Data=54062F1F2DB6918192464143363943383135393644313446413441463942363938424244393 6443833334535303937323500030B6A1245746973616C617420574150004E41503200C54601C6560 187070683000101C65501871106830D01870706830001871006AB018708060365746973616C61740 001870906890101C65101 UDH=0B05040B8423F00003540301 pid=00 dcs=F5 Binary=1 [ErrorDetail] RetryCount=5 LastRetryTime=20091108152218 LastErrorInfo=ERROR: Invalid Source address TON - ESME_RINVSRCTON (0x48) -- SMPP - 10.10.10.101:2020 " | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1414 Registered: 08-2008 |
Changing that setting would not affect this. Your provider is complaining that they do not like the source (sender) address that you are using. There is no sender explicitly specified in that message, so the "Default Sender Address" configured for your SMSC connection is what would be used. Change this setting to a source address that your provider will accept. One common problem...if you are specifying recipient addresses in international format (with +), do the same for the sender. Only your provider can tell you what they will accept. --Des | |||
Mexcano New member Username: Mexcano Post Number: 18 Registered: 02-2009 |
The provider alreay gave me the Default Sender Address And I put it into the settings | |||
Mexcano New member Username: Mexcano Post Number: 19 Registered: 02-2009 |
And regarding the international format (with +), I aleady used it | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1418 Registered: 08-2008 |
Ok. But your provider does not like the sender address that you are using. At least that is what they are indicating when they return the ESME_RINVSRCTON error. It is the provider that is generating this error, not NowSMS. Does this happen with every message that you send? Or only with messages to certain recipients? What is your default sender address? What is the recipient address that you are sending to? If you don't want to disclose actual numbers, that is fine ... just "XXXX" the last 4 or 5 digits so that we can get a better idea. -- Des NowSMS Support |