Hi At 12:20 PM 8/11/03 +0200, you wrote:
Main question is: How much of the specific implementations do we want to add to Kannel?
Ideally this would look like the SMSCConn abstraction layer itself for the resolving of the network.
A first scratch may be an simple HTTP lookup to an "resolving server" which then answers with a given smsc-id we simply inject to the Msg struct and then route via this smsc-id.
Any ideas and comments please?!
I would rather be able to ask Kannel about an MSISDN - simply routing it to another smsc-id can have disasterous effects esp. with respect to charging. Eg say a user wants to restrict the charge to X creds in Country Y. Now via one SMSC we can get to telco A in Country Y and via another SMSC telco B - but with different costs - eg O2 and Vodaphone in the UK. If bearerbox simply rewrites at this point all apps doing intelligent routing pre SMSbox will get things totally wrong.
I would prefer to see some sort of lookup interface.. Something like a "HLR" box.
Of more importance is how to implement the lookup and when (as this will incur a msg cost)? Use some third party? Do some SS7 integration? Booktrout have some nice APIs with their SS7 cards.
Also of course if we keep the numbers in a hash table, when does one refresh?
Nisan
Stipe
[EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf
Tel: +49-211-74845-0 Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
