Hi All.
I've got a question about the new LCR module that Juha commited to CVS.
We're located in the US so this question may pertain only to ser installations that follow the North American Numbering Plan.
For us to _really_ perform LCR decisions we need to look at the NPA and NXX (ie, the first 6 digits of a 10-digit phone number) of the origination and termination numbers. This this we would decide where to route the call.
The reason is that it matters here we get DIDs from (sometimes they're provided by 3rd party PSTN gateway operators) and where our softswitch(s) are physically located.
So at a high level the matrix of routing decisions would look something like this:
Orig NPANXX Term NPANXX PSTN Gateway --------------------- ----------------------- ----------------------- 407566 321251 10.10.0.40 814332 202442 67.93.11.31
So can the LCR module accomodate something like this?
Regards, Paul
Java Rockx writes:
For us to _really_ perform LCR decisions we need to look at the NPA and NXX (ie, the first 6 digits of a 10-digit phone number) of the origination and termination numbers. This this we would decide where to route the call.
it should work "out of the box" it NPA and NXX are found in request uri and from field.
-- juha
Thanks!
Also, I'm using ser-0.9 rather than ser-10.99-devX
Are there any dependencies in the core that I need to backport in order to use the LCR module with ser-0.9?
Regards, Paul
On Thu, 17 Feb 2005 23:18:15 +0200, Juha Heinanen jh@lohi.tutpro.com wrote:
Java Rockx writes:
For us to _really_ perform LCR decisions we need to look at the NPA and NXX (ie, the first 6 digits of a 10-digit phone number) of the origination and termination numbers. This this we would decide where to route the call.
it should work "out of the box" it NPA and NXX are found in request uri and from field.
-- juha
-
Java Rockx -
Juha Heinanen