Re: [RFC] Number portability hooks

2003-08-14 Thread Stipe Tolj
An HTTP 'callback' sounds good as an initial implementation. Generic and flexible. yep. I'm also in a favor of this. Where API should be very simplified like: earerbox calls http://www.foob.com/?msisdn=msisdn and that HTTP server replies with either an smsc-id as body/header(?!) or nothing

Re: [RFC] Number portability hooks

2003-08-14 Thread Steve Kennedy
On Mon, Aug 11, 2003 at 12:20:38PM +0200, Stipe Tolj wrote: 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.

Re: [RFC] Number portability hooks

2003-08-14 Thread Steve Kennedy
On Mon, Aug 11, 2003 at 05:01:50PM +0200, Nisan Bloch wrote: 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

RE: [RFC] Number portability hooks

2003-08-14 Thread Paul Keogh
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

RE: [RFC] Number portability hooks

2003-08-14 Thread Paul Keogh
now, in Germany we have an access to an centralized database which holds all ported numbers. So actually if you want to route messages to Operator SMSCs, you must resolve the MSISDN at that database to know if it has been ported to an other operator and hence route it to the new one instead

Re: [RFC] Number portability hooks

2003-08-14 Thread Alex Kinch
We'd be interested - +1 from me. Alex - Original Message - From: Alexei [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 11, 2003 4:41 PM Subject: Re: [RFC] Number portability hooks Sounds illegal to me to make this information public. But anyone with SS7 access can do

Re: [RFC] Number portability hooks

2003-08-14 Thread Dave White
At 12:20 PM 8/11/03 +0200, you wrote: Any ideas and comments please?! Yeah. For interactive services, where an app responds to an MO SM with an MT SM within a timeframe of at most a few minutes, you can do most NP work very simply under certain conditions, namely when all bearerbox

Re: [RFC] Number portability hooks

2003-08-14 Thread Alexei
- Original Message - From: Steve Kennedy [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 11, 2003 4:15 PM Subject: Re: [RFC] Number portability hooks On Mon, Aug 11, 2003 at 05:01:50PM +0200, Nisan Bloch wrote: I would prefer to see some sort of lookup interface

Re: [RFC] Number portability hooks

2003-08-14 Thread Steve Kennedy
On Mon, Aug 11, 2003 at 12:51:16PM +0200, Stipe Tolj wrote: The question is would we do some kind of internal caching for this? This would speed up things drastically. Maybe using a *huge* Dict hash? Has anyone used huge Dict hashs? Look at cdb, good for multiple reads, not so good for

Re: [RFC] Number portability hooks

2003-08-14 Thread Alex Kinch
- From: Steve Kennedy [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 11, 2003 4:15 PM Subject: Re: [RFC] Number portability hooks On Mon, Aug 11, 2003 at 05:01:50PM +0200, Nisan Bloch wrote: I would prefer to see some sort of lookup interface.. Something like a HLR box

Re: [RFC] Number portability hooks

2003-08-14 Thread Andreas Fink
On Montag, August 11, 2003, at 05:15 Uhr, Steve Kennedy wrote: On Mon, Aug 11, 2003 at 05:01:50PM +0200, Nisan Bloch wrote: 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