Re: [RFC] Number portability hooks

 > 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 
connections go to the operators directly, and not over a service aggregator.

In this case, the MO will only come from the operator who "owns" the 
handset, i.e. owns the GSM network in which the handset is present. If 
that handset gets ported, the MO will come from the new network's SMSC.

By remembering the smsc-id from whence an MO came, you will almost never 
go wrong sending it back to the same smsc-id for the MT replies. No 
nasty HLR lookups!

It's no good for strongly asynchronous MT-centric services 
(subscriptions, e-mail notifications, etc) but it will work like a charm 
for most other cases.

David WHITE
ONE GmbH

P.S. Sorry Nisan! I pressed "send" there before remembering the 
dev-list's handling of replies. Not enough coffee...