Great, appreciating the feedback to know that all is ok.
Cheers,
Daniel
On 03/10/15 17:02, Ding Ma wrote:
> Happy to to report the max_load worked in our testing. Thanks,
>
> On Tue, Sep 15, 2015 at 3:04 AM, Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> Hello,
>
> good
Happy to to report the max_load worked in our testing. Thanks,
On Tue, Sep 15, 2015 at 3:04 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
> good to know that you found the issue and it was in the config file. Would
> be appreciated if you can report the results on testing maxload, to know if
>
Hello,
good to know that you found the issue and it was in the config file.
Would be appreciated if you can report the results on testing maxload,
to know if there is anything to fix there.
Cheers,
Daniel
On 14/09/15 21:52, Ding Ma wrote:
> Hi,
>
> Figured this out. Seems I had made a mistake in
Hi,
Figured this out. Seems I had made a mistake in the names of AVPs. Changed
the AVP names as the exact names used in the example contained in
dispatcher doc. Dispatcher started to work, I can see even distribution of
loads to 2 Asterisk servers. Will verify if maxload is being enforced or
not,
Hi, Daniel
I just tested the dispatcher in 4.3.1. It showed the same behavior as
4.2.3. All the calls are sent to one Asterisk (the last one in the
dispatcher list), the maxload setting in dispatcher table is ignored.
We use db dispatcher table instead of dispatcher list file, and the
kamailio.cf
Yes, 4.3 should have all fixes in 4.2.
Cheers,
Daniel
On 12/06/15 06:06, Ding Ma wrote:
> OK, we’ll try to update and report back. Wonder if the latest 4.3 has
> all the fixes went into the latest 4.2.x. We already have plan to
> upgrade to 4.3.
> Thanks.
>
>> On Jun 10, 2015, at 10:01 AM, Dani
OK, we’ll try to update and report back. Wonder if the latest 4.3 has all the
fixes went into the latest 4.2.x. We already have plan to upgrade to 4.3.
Thanks.
> On Jun 10, 2015, at 10:01 AM, Daniel-Constantin Mierla
> wrote:
>
> It was a fix for maxload during 4.2.x, but don't recall exactl
It was a fix for maxload during 4.2.x, but don't recall exactly when was
backported. Can you upgrade to latest 4.2.x and see the results? Your
config file and database don't require any change, only deploy the
binaries for latest 4.2.x and restart.
If the issue is still there with latest 4.2.x, re
We're running kamailio 4.2.3. Are there any changes to dispatcher in 4.2.x?
Thanks,
# kamailio -V
version: kamailio 4.2.3 (x86_64/linux) 5596bd
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
F_MALLOC, DBG_F_MALLO
Hello,
what version of kamailio are you using?
Cheers,
Daniel
On 09/06/15 20:51, Ding Ma wrote:
> I'm trying to set up kamailio dispatcher to distribute calls to 2
> asterisk servers. So far, the failover case seems ok, but I cannot get
> the dispatcher to distribute load. All calls are going to
I'm trying to set up kamailio dispatcher to distribute calls to 2 asterisk
servers. So far, the failover case seems ok, but I cannot get the
dispatcher to distribute load. All calls are going to the last destination
entry in the dispatcher table even if I have set the maxload attributes.
I'm using
11 matches
Mail list logo
