|
Hi Andreas
Yes I figured 0.024$ was a bit expensive for a
lookup - and that's based on 500k lookups a month (about $12k!). I looked into
the service, and they don't even return MCC/MNC - just the name of the network.
Even worse, they only provide information for Germany, Ireland, Netherlands,
Switzerland and the UK!
Our VOIP provider also wants to do network lookups
to make their LCR for mobile calls 100% reliable. I'm sure I can find you some
more customers..
When will you be able to offer this service? I kind
of need it by yesterday!
Alex
----- Original Message -----
Sent: Sunday, October 19, 2003 5:22
PM
Subject: Re: Least cost routing
On 19.10.2003, at 17:30, Alex Kinch wrote:
Hi,/smaller>/fontfamily> I'm
currently getting to grips with least cost routing of messages. As we don't
currently have any reliable MCC/MNC lookup facilities, we're having to do
this by country prefix./smaller>/fontfamily> As
far as I can see there's two ways I can do this: 1. implement
preferred-prefix on each SMSC, or 2. put prefix matching in our application
to select the SMSC using the smsc variable on the HTTP GET call to Kannel./smaller>/fontfamily> There
were discussions previously about building an HLR box for Kannel, to
retrieve MCC/MNC from a number using SS7. I've looked at a couple of third
parties that offer an HTTP-based lookup of MCC/MNC for approx $0.024 per
lookup - but when you're on tight margins as it is that's quite an overhead
on the delivery costs./smaller>/fontfamily>
0.024$
Sounds very expensive for a lookup. We are able to do this but we wouldn't
charge that much. I once posted such a idea to the kannel list and asked if
anyone is interested but we had no reply whatsoever so we didn't develop the
idea any further at that time. It's still easy to do for us however.
I remember when we
discussing this before, Nisan made a valid point that if there was a hash
table in Kannel, how often would it need to be refreshed.. We were thinking
on a monthly basis, but then if someone ports their number to another
network and one of our users just happens to text them 10-15 times a day,
we'd potentially end up losing a large chunk of money until their network
information is refreshed!/smaller>/fontfamily>
I don't
think this is appropriate. The cache should expire within hours in my eyes. If
you use the location info too (the MSC number) then changing the location
(going to roam) already makes the routing info inappropriate in some cases.
For example, if you want to send an SMS to my swiss number and I am in france,
then you can send it to me over Swisscom SMSC but not from other SMSC's while
as when I am in switzerland, many foreign SMSC's work fine. So knowing that my
number is a swisscom number is good for 24h but which SMSC link to use to
deliver the message might change many times during the day.
Anyone like to share
some thoughts on this whole thing? Stipe you must have experience of this as
I imagine you're doing some sort of destination routing for Centrium?/smaller>/fontfamily> Alex/smaller>/fontfamily>
Andreas
Fink Global Networks Switzerland
AG
------------------------------------------------------------------ Tel:
+41-61-6666333 Fax: +41-61-6666334 Mobile: +41-79-2457333 Global Networks,
Inc. Clarastrasse 3, 4058 Basel, Switzerland Web:
http://www.global-networks.ch/
[EMAIL PROTECTED] ------------------------------------------------------------------
/x-tad-smaller>/fontfamily>
|