Have you tried setting the interface-version ? -- Oded Arbel m-Wise mobile solutions [EMAIL PROTECTED]
+972-9-9581711 (116) +972-67-340014 ::.. Linux - The STABLE and FUN way to operate > -----Original Message----- > From: Troy Kelly [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 02, 2002 4:37 AM > To: [EMAIL PROTECTED] > Subject: RE: Information concerning Message Payload field > Importance: Low > > > Hi, > > Our carrier has told me that they are using a SEMA SMSC/SMPP gateway. > Has anybody else had problems like we are experiencing with it? > > Our carrier is quite unhelpful when it comes to trouble shooting, it > took them 2 months just to admit they were not delivering message_text > and only message_payload had the content. > > Regards, > Troy Kelly > WebCentral > http://www.webcentral.com/ > > > -----Original Message----- > From: Oded Arbel [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, 1 October 2002 6:06 PM > To: Troy Kelly; [EMAIL PROTECTED] > Subject: RE: Information concerning Message Payload field > > We had that same problem with a provider that uses the CMG > SMSC with an > SMPP protocol. if the protocol version is set to 3.4, then > the SMSC will > send out the content of the message in message_payload. setting the > interface version to 3.3 will for the SMSC to send only 3.3 compatible > fields which Kannel can handle. this shouldn't cause any problems as > Kannel does not implement any v3.4 extension anyway. > > We need to fix the SMPP module, or write a new one, that will support > the optional fields of v3.4 - but as the describeed solution works, we > are not in any hurry. > > -- > Oded Arbel > m-Wise mobile solutions > [EMAIL PROTECTED] > > +972-9-9581711 (116) > +972-67-340014 > > ::.. > Famous Last Words 018-"He hit me for HOW MUCH?????" > > > > > > -----Original Message----- > > From: Troy Kelly [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, October 01, 2002 3:53 AM > > To: '[EMAIL PROTECTED]' > > Subject: FW: Information concerning Message Payload field > > Importance: Low > > > > > > 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 > > > > >
