After a little delay of a few months, I'm moving forward slowly but
surely with this. We now have our own internal setup to query an
MSISDN for MCC/MNC, it's just a case of interfacing it to the outside
world.
As such a query is a two stage process, I would imagine it would go
something like
As such a query is a two stage process, I would imagine it would go
something like this:
1. Client makes request with MSISDN and return URL
2. Server posts result (as HTTP GET or POST) back to client as soon as
the necessary information is received back from the remote operator.
As this is such
Hi Ben,
I think the protocol you use will be dependent somewhat on the
average length of time for the lookup. There is more overhead in
having to have 2 connection setups (1 outbound and 1 inbound) than in
just the one. But it probably comes down to volumes as well, and if
the calling
Blocking is an idea, but as you're basically doing a an SS7 query to
the remote operators HLR it's possible the HLR may not respond or
take a little while to respond. That's where caching comes into play.
Indeed. I think if you are planning on caching at your end, then you
need to provide
On 11/9/06, Ben Suffolk [EMAIL PROTECTED] wrote:
Blocking is an idea, but as you're basically doing a an SS7 query to
the remote operators HLR it's possible the HLR may not respond or
take a little while to respond. That's where caching comes into play.
Indeed. I think if you are planning
we built something fairly similar for a MNP solution.
wecached the result in memcached for 24 hours.
works a treat.
however, the overheard of all those http requests was too much for some
applications, so we also made a LDAP interface.
On Friday 10 November 2006 07:37, Alex Kinch wrote:
On
Hello,
Just putting together a proposal for a new service, would there be any
interest from people here for a service that will do an HLR lookup
against an MSISDN and return a MCC/MNC?
I know there was talk about an HLR box or plugin for Kannel, but not
sure it ever went much further forward
