|
Hi,
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.
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.
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.
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!
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?
Alex
|
- Re: Least cost routing Alex Kinch
- Re: Least cost routing Andreas Fink
- Re: Least cost routing Alex Kinch
- Re: Least cost routing Steve Kennedy
