Hi All,
I have managed to contact MTC they had to make amendments and we had to
split our TX and RX into seperate binds and set the message id type as
0x01 for both.
Thanks again
Jarratt
On 09/17/2010 10:45 AM, "Mads N. Vestergaard – CoolSMS A/S" wrote:
Hi Jarratt,
For me it looks like your provider isn't following the official protocol.
If we look at the message you are sending, they give it the msgid 31D44D55:
> 2010-09-17 10:26:34 [16954] [12] DEBUG: message_id: "31D44D55"
Later on you receive the DLR, but the ID is only given in the message_payload:
> 2010-09-17 10:26:37 [16954] [13] DEBUG: message_payload: "31D44D55 201"
And after the msgid, thay have, what for me looks like a return code: 201
This is out of standard, you provider might be able to solve this for you, if
not you might need to create a patch for kannel, to support your provider.
