RE: Optional parameters in smpp pdu's?

Sema have an SMPP gateway to their SMSC. The version of the SMPP
the gateway uses depends on what is sent in the bind request. If the
version uses 3.3 then it will send the message body in the short message
field, if it is 3.4 then it uses the optional parameter message_payload
field. This is SMPP 3.4 compliant. Optional parameters are something
that will be needed in Kannel as delivery reports use them
in SMSCs that implement SMPP 3.4.

It is necessary to set the version in the bind receive and the bind transmit
PDUs to be 0x33 in order for this to work with Kannel. We have had this
working here so maybe the version of the gateway you are connecting to
is different? Perhaps you could send in the log file.

Kindest Regards,
Michael Mulcahy.

ANAM Wireless Internet Solutions
http://www.anam.com mailto:[email protected]
+353 1 284 7555
Castle Yard, Saint Patrick's Road, Dalkey, County Dublin, Ireland

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Alexei Pashkovsky
> Sent: Friday, February 22, 2002 5:58 AM
> To: [email protected]
> Subject: Re: Optional parameters in smpp pdu's?
>
>
> Well,
> according to sema spec's , it only supports Sema2000
> protocol, which is
> implemented in OIS module, and you use SMPP.
> Afaik, your operator has written some propriatory translator for SMPP
> protocol, or has made changes to the original smsc.
> Kannel SMPP module supports only the standard SMPP
> functionality, thus if
> you need anything beyond, you will have to make it yourself.
> Should not be too much difficult if you know the exact
> structure of packets
> you get and have them documented.
> I suggest you adding the new packets support and probably new
> functions for
> treating those packets in a new kannel module, call it
> smpp-[your-operator-name] and try adjusting.
> If there will be more than one user for this module, it might
> be included in
> Kannel mainstream.
> Those are my 2 cents ..
>
> ----- Original Message -----
> From: "Wartan Hachaturow" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, February 21, 2002 12:36 PM
> Subject: Re: Optional parameters in smpp pdu's?
>
>
> > On Thu, Feb 21, 2002 at 10:33:33AM -0000, Ronan Derby wrote:
> >
> > > Are you connecting to a SEMA  SMSC?
> >
> > Hmm. No idea, to be honest :) I've been just said it supports
> > SMPP v3.4. But I'll ask.
> >
> > > If so, I would suggest trying to set the SMPP version to 0x33
> > > (SMPP v3.3) in smsc_smpp.c and rebuilding Kannel.
> >
> > That didn't helped, unfortunately :(
> >
> > > The SMPP spec is a little vague about the use
> > > of the message payload functionality, it says to use it
> for messages
> > > over a certain length, but it doesn't say that it can't be used
> > > for smaller messages. The SEMA SMSC uses it for all
> messages (I think).
> >
> > Yeah, my smsc also use it for all messages (even those that are <160
> > octets).
> > So the problem is still in question: are there any patches
> for optional
> > smpp parameters support (e.g., message payloading, for example)?
> > If not, will you be interested in adding such a support, and, maybe,
> > give me some recommendations? (I have to write the patch
> this weekend,
> > so it should be out shortly :).
> >
> > --
> > Regards, Wartan.
> > echo "Your stdio isn't very std."
> > -- Larry Wall in Configure from the perl distribution
> >
> >
> >
>