Re: mBlox SMPP optional parameters

Hi Ian

part of the problem here is that  each vendor will then have their own 
proprietary settings,
now most of us who use kannel for high volume messaging and have many links 
running and external applications that handle the routing - this would then 
mean that the routing apps would need to have specific knowledge of the 
optional/proprietary settings for each gateway. Part of the idea of Kannel 
is to abstract the links so external apps do not need to know anything 
about the various protocols and connections.  Then the next issue is how to 
pass these through from smsbox.

so -1 for this going to CVS,

nisan
  - At 11:30 AM 2004/07/14, you wrote:
>Alexander Malysh wrote:
> > Hi Ian,
> >
> > please no vendor specific things in kannel (vote -0 ;))...
>
>Understood.
>
>But perhaps if someone could think of a way for users to submit any optional
>parameter in the range 0x1400 to 0x3fff without the tag being named
>specifically mBlox? (See SMPP v3.4 section 5.3.1)
>
> > p.s. you should post your changes and they should be of interest for
> > other users... and may be will be commited to cvs or at least part of
> > those...
>
>I've got a few people testing it a bit more first.
>
>--
>Ian Cass
>
> >
> > Thanks in advance!
> >
> > Ian Cass wrote:
> >
> >> Hi guys,
> >>
> >> I spent a few hours at the end of last week making Kannel work with
> >> our SMPP vendor specific optional parameters that we (mBlox) have
> >> implemented for our PSMS solution. Should I submit the patch or
> >> would you rather not have vendor specific stuff in the Kannel?
> >>
> >> --
> >> Ian Cass (mBlox)


--------------------------------
www.clickatell.com
Any message, anywhere
Phone: +27 21 9487150