RE: Service description parameters in CIMD2

Hi Dziugas,

As always, each operator does different things: one may include param 069 in
the MOs, others may not. 
And talking about billing, that is really a mess: although cimd2 spec has a
explicit param to pass billing information (param 064 TARIFF CLASS), my
experience is that each operator uses whatever he feels.

For example, we have all these cases:

1) operator wants billing info for MTs on param 064 (wow, spec compliant!!)
2) operator wants billing info for MTs with something like <sender><binfo>
on param 023 (ORIGINATING ADDRESS)
3) operator wants billing info for MTs with something like
<PREFIX><sender><binfo><SUFFIX> on param 023 (ORIGINATING ADDRESS)

As you see, this is quite a mess. We're working on a flexible way to inform
the driver where to put binfo in the MTs, and have come with the following
aproach: smsc config directivs as follows

Case 1)
binfo-mt-param = 064
binfo-mt-pattern = %B 

Case 2)
binfo-mt-param = 023
binfo-mt-pattern = %p%B

Case 3)
binfo-mt-param = 023
binfo-mt-pattern = whateverprefix%p%Bwhateversuffix


And maybe if some has to use param 065 (service description) to put the
billing information

binfo-mt-param = 065
binfo-mt-pattern = %B

What do you thing about this approach? Anyone interested in seeing that
going into cvs?

With this kind of flexibility, a lot of users could use kannel
out-of-the-box with more cimd2 links.

Angel Fradejas
Mediafusión España, S.A.
[email protected]
www.mediafusion.es
Tel +34 91 252 32 00
Fax +34 91 252 59 69


> -----Mensaje original-----
> De: [email protected] [mailto:[email protected]] En 
> nombre de Dziugas Baltrunas
> Enviado el: martes 25 de noviembre de 2003 14:37
> Para: [email protected]
> Asunto: RE: Service description parameters in CIMD2
> 
> Hi list,
> 
> could also somebody report, are these features supported at 
> operator by
> default (i.e. every packet is appended with that 
> information), or it's up
> to the operator to "add" that feature (sure, according to 
> CIMD2 spec), for
> example, binfo, service center address, etc.
> 
> regards,
> Dziugas Baltrunas
> 
> On Tue, 25 Nov 2003, Angel Fradejas wrote:
> 
> >
> > >> I'll work on it.  I've also made some patches for my own
> > >> needs, and need
> > >> to filter those out first.
> >
> > We're already working to add standard &binfo= capabilities 
> to the cimd2
> > driver. Maybe if you tell me what you we can take it into 
> consideration. For
> > example, we don't need to use param 065 in any way with our 
> operators, but
> > it seems you need it.
> >
> > >> I've also noticed that parameter 69 (which the CIMD spec says is
> > >> "Service Center Address") is not recognized by Kannel, and I keep
> > >> getting warnings about it.  I'll try to add this in the patch
> > >> I'll make.
> >
> > Current cvs kannel does not give any warning for param 069 
> (just ignores it
> > silently), I made a patch for that months ago that went into cvs.
> > What version are you using?
> >
> > Angel Fradejas
> > Mediafusión Espa?a, S.A.
> > [email protected]
> > www.mediafusion.es
> > Tel +34 91 252 32 00
> > Fax +34 91 252 59 69
> >
> >
>