Hello list, as many countries deploy MSISDN number portability in their GSM networks, which means you as a end-customer can take your MSISDN to an other operator when you switch, makes things a bit more complicated on the SMS gateway side.
Mainly Kannel uses MSISDN number prefixes to route messages to specific SMSCs (that may be the operators SMSC). Taking number portability as a given fact, either the external calling application (which calls smsbox's sendsms interface) has to take care that the message is routed to the appripriate smsc-id via the smsc cgi variable or Kannel may do this. Therefore I'd like to add a feature in bearerbox that allows to resolve the smsc-id where a specific MT receiver will have to be routed to find it's way into the "new" home network. As many implementation of the number portability lookup differ we need to abstract this in bearerbox as much as possible. 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?! 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
