Hi Folks, I am having some problems with our carrier, it seems that Kannel doesn't support the message_payload field but out carrier only delivers the content of the message in this optional field.
We currently have a hastily developed 'hack' in place to make it work at the moment, but was curious to see if anybody had a better solution for all of the optional fields? Regards, Troy Kelly WebCentral Pty Ltd http://www.webcentral.com/ -----Original Message----- From: XXXXXXX, XXXXXXX [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 17 September 2002 10:15 AM To: Troy Kelly Subject: Information concerning Message Payload field Hi Troy, It has been confirmed from the testing that I have undertaken that the "message payload" field is used for the user data when the interface version of the SMPP client is 3.4 or later. An interface version of 3.4 uses message payload, otherwise message text is used. The advantage of applications using 3.4 binds is that it saves the client from performing length checks before setting up the text. I now regard this issue as closed. Please call me if you wish to discuss further. Regards, XXXXXX XXXXXXX Technology - Planning XXXXXXXX Australia Phone: +61 2 XXXX XXXX Mobile: +61 XXX XX XXXX Fax: 02 XXXX XXXX
smime.p7s
Description: application/pkcs7-signature
