Douglas Garstang writes:
Ok, can someone please tell me why 4999 LCR entries is too many? What's the limit? Is it hard coded in the OpenSER source? Why?
there is a constant in lcr_mod.h that tells how many lcr entries cached lcr table can hold:
#define MAX_QUERY_SIZE 512
you can increase its value, but as i have said, lcr module was not designed for the kind of inter-operator application that you have.
Ok... what about carrierroute? Are there are docs or examples available besides the very limited module specs at openser.org? It seems like if you want to change carriers you have to hard code it in cr_tree_rewrite_uri(). Wouldn't a next_carrier() type function make more sense?
Doug.
____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
On Tuesday 25 March 2008, Douglas Garstang wrote:
#define MAX_QUERY_SIZE 512
you can increase its value, but as i have said, lcr module was not designed for the kind of inter-operator application that you have.
Ok... what about carrierroute? Are there are docs or examples available besides the very limited module specs at openser.org? It seems like if you want to change carriers you have to hard code it in cr_tree_rewrite_uri(). Wouldn't a next_carrier() type function make more sense?
Hi Douglas,
as i said in a previous mail, this is not necessary, you can load the carrier from a database, with cr_user_rewrite. If you don't like this function, you can still load the carrier from an AVP, e.g. from another DB table. As a side note, i can understand your frustration regardings the documentation, i still feel the same with some parts of the server.. I'll later add a few more sentences about this to the docs, trying to explain it better.
But please allow me to remind you that this is an open source project. Many month months of engineering time (from my collegues and me) went into the design, test and maintenance of carrierroute. You get a quite capable piece of code to implement carrier-grade LCR infrastructures for free. But if you want to use this, then you should (as with any open source project) invest some time to learn and understand how to use this, and also implement some QA infrastructure to make sure that this code does _really_ what you need.
If you don't have time for this, then perhaps you need to hire someone to create such a solution for you. I'm more than happy to apply any improvement patches for the documentation from you, and will of course try to fix any bug you encounter. If you have any specific questions about this module i will also try to answer them.
Cheers,
Henning
-
Douglas Garstang -
Henning Westerholt