RE: [RFC] mcc and mnc

>smsc-id is almost as good, but not completely. mcc and mnc are 
>normalized values, and when you have for example 20 connections to 
>the same operator (as I do, one emi2 link for each short code), if 
>you use smsc-id you'll have to translate this value in every 
>application behind kannel, wich is error prone.

Well frankly I dont think it makes sense to do it in kannel but 
simple mechanisms can be used in your app like a SMSC naming scheme 
"provider-shortid".

>I know kannel doesn't have a way to know mcc and mnc, that's why i 
>suggest smsc directives.

Frankly what will you do if you have an SMSC which deals with 
multiple MNC and MCCs?

>But for extensibility (i mean custom drivers) it would be a good 
>thing: for example, a custom NetSize driver we have developed, gets 
>mcc and mnc information directly from the provider, as you can have 
>any mcc and mnc through this link. In this situation, neither using 
>%i or appendind &mcc=xx&mnc=xx would work.

in this situation kannel will simply not know it and even a directive 
wouldnt work.

-- 

Andreas Fink
Fink-Consulting

------------------------------------------------------------------
Tel: +41-61-6932730 Fax: +41-61-6932729  Mobile: +41-79-2457333
Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland
E-Mail:  [email protected]  Homepage: http://www.finkconsulting.com
------------------------------------------------------------------
Something urgent? Try http://www.smsrelay.com/  Nickname afink