Hi All,
>ray wrote:
> if you could use this for least cost routing based on rate table in the
> database then this would be a dream.
I agree. However, after a somewhat stormy night over here, and the fact that
I couldn't sleep a wink, I managed to think of something which can really useful.
Here is my idea:
We know that if we define several "permanentEndpoints" that have the same prefix
assigned to them, GnuGK will round-robin all endpoints.
Why not create something like an E164 re-write table with priorities, something
that looks similar to this:
9119#011=1;00
9119#011=2;01
9119#011=3;02
The selection of which re-write to use is based upon the priority number of the
re-write rule. The lower the number, the higher the priority. If the call to the
first re-write rule fails, the GK will try the second one, and so one. This way
we can make a pseudo-LCR by defining which re-write rule has precedence to which.
What do you think ?
_________________________________________________________________
Nir Simionovich
IT Manager
m-Wise Ltd.
e-Mail: nirs@m-wise.com
cell: +972-54-482826
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
