The Tag column size is 64. If I make this larger in the database, will
it be truncated once it is loaded into memory?
According to modules source code Tag's max size is hardcoded and will be
truncated. But this is not a bit problem. You can keep capabilities list
in htable and only put a key
t
of both methods.
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Vitaliy Aleksandrov
Sent: Wednesday, April 29, 2015 12:27 PM
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] LCR with gateway capabilities
On 29/04/15 12:34, Grant Bagdasarian wrote:
That s
r.org
*Subject:* Re: [SR-Users] LCR with gateway capabilities
What about configuring two LCR instances with different "lcr_id".
The first one can use only gateways with requested capabilities and
the second one all gateways.
Then you can make a decision about which instance to use durin
d g711ulaw codec? Etc.
Wouldn't this cause the data to grow exponentially?
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Vitaliy Aleksandrov
Sent: Wednesday, April 29, 2015 10:36 AM
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] LCR with gateway cap
What about configuring two LCR instances with different "lcr_id".
The first one can use only gateways with requested capabilities and the
second one all gateways.
Then you can make a decision about which instance to use during call
routing process providing this lcr_id to load_gws() function.
Hello,
>From what I understand about the LCR module is that the rules have to be
>prioritized by the admin, be it manually or automatically by an application.
Let's say the LCR database has 10 gateways, each with their own rules etc.
4 of these gateways support caller id spoofing and the others
