RE: [RFC] mcc and mnc

>Angel, what you want to do is to allow to forward mcc and mnc values
>that have to be entered by the system admin by hand to each smsc
>group, which means Kannel is only storing and forwarding still
>statical information. This blows only unnecessary the code of Kannel
>up.
>
>You can distunguish in each called sms-service from which smsc group
>the request came in, hence your backend system should deal with the
>translation from smsc-id to mnc, mcc pairs IMO.

Not true in multi-operator links.

This is mainly the kind of situation I was triyng to deal with.  As I said
before, fixed directives for direct operator links, copying theses
attributes to msg->sms.mcc/mnc members. And then, if a link deals with
several mcc and mncs, the driver could get (if possible) the values from the
provider and set them in msg->sms.*
I'm doing it with success. And I see no reason to think I'm a extremely rare
case if SMS bussiness.

(Btw, the solution of having one sms-service for each service/operator
combination is simply impractical. We have as much as 5000+ services - we
are a content developer and provider - so figure yourself).

We have a working and practical kannel for a small number of services and
smscs. Let's work towards a practical kannel for a huge number of them.

(note when I say "let's work" I mean "i would contribute my working solution
if anybody is interested").

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