| SMS got stuck in 2way |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 22, 2012 ⬆ |
◄ ► |
| Author | Message | |||||||
| Erzhan Checkmarket New member Username: Checkmarket Post Number: 3 Registered: 06-2012 |
Hello. Please help me. The subscriber sent SMS, the coding is specified by dcs=4. For clarity, I enclosed the file from 2way queue, a part of smppdebag and smsdebag. 1) Why this SMS got stuck in 2way queue? 2) Why it is distinguished as binary? after all the subscriber sent simply the text "78838917"
| |||||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4035 Registered: 08-2008 |
Hi, I don't know why this message would be received by you as a binary message. However, the SMPP message that you are receiving has an SMPP data_coding value of 4, which indicates that the message content is binary. As such, NowSMS is treating it as a binary message. By default, we do not route binary messages to a 2-way command, because the 2-way command is most likely not prepared to process it. I don't know why your SMS provider would be flagging a message as binary when it is not. If you want to route binary SMS messages to your 2-way command, include an @@BINARY@@ placeholder somewhere in the 2-way command. @@BINARY@@ will be replaced with “1″ if the message is in binary format, “0″ otherwise. If the message is binary, @@FULLSMS@@ will be the message content in hex format, and you would need to convert it to ASCII. I'm curious ... does this happen consistently if the message content is numeric only? It sounds like an odd bug at your SMS provider. -- Des NowSMS Support | |||||||
