RE: [RFC] mcc and mnc

> -----Original Message-----
> From: Stipe Tolj [mailto:[email protected]]
> 
> Angel Fradejas wrote:
> > 
> > >>Not true in multi-operator links.
> > >
> > >if your multi-operator incoming link tells you the 
> original SMSC the
> > >message comes from (passing the %i) then youre back in business. If
> > >you implement mnc and mcc and the multi-operator link 
> doesnt tell you
> > >this, you're back to square one, hence the original smsc name is as
> > >good as mnc and mcc.
> > 
> > Better a practical (and simplified) example:
> > 
> > you have only one link
> > 
> >         group = smsc
> >         smsc-id = custom_driver_whatever
> >         smsc = custom_type
> > 
> > The protocol of this link tells you (in one way or another) 
> the operator
> > originating the MO. Your %i will be "custom_driver_whatever".
> > 
> > Hope this clarifies.
> 
> yep, if you do receive messages from different networks over one link,
> which is what you think of, the %i only tells the sms-service that it
> has arrived from this smsc.
> 
> In this case I suggest you're backend system should know the prefix of
> the MO message, hence your backend system has to figure out from which
> network the request is coming by parsing the prefix number value.

Since the smsc_id in the MO is set by the driver, and this only applies to custom/proprietery or future drivers, I think that setting the smsc_id of the MO to something that represents the mcc/mnc will suffice (maybe a concatenation of their values), and is a good solution. 
Otherwise, adding another two members for msg->sms structure and allowing for options in the get/post/xmlrpc sms-service query to use them wouldn't be such a hurdle IMO - it won't be useful for most people, but there are other things there which aren't useful for most people, and still in Kannel. Adding these members will also allow to pass more message information into the module - for example, if you need to connect to an SMSC where you can set the MCC/MNC values in some fields independent of the UDH (just a speculation, haven't seem something which allows/requires that, but with all the XML messaging going on around, it's likely something like this will come up sooner or later).

So my opinion is that if the implementation is clean - it will do no harm and potentioally can do good.

just my € 0.02

--
Oded Arbel
m-Wise Inc.
[email protected]
(972)-67-340014
(972)-9-9581711 (ext: 116)

::..
"The C Programming Language -- A language which combines the
 flexibility of assembly language with the power of assembly language."