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 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, not really an issue even if it is not enforced. 

Thanks,

On Thu, Aug 27, 2015 at 9:07 AM, Ding Ma <mading087@gmail.com> wrote:

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.cfg is the same as included in the previous email in this thread.

Hope I didn't make any mistake in kamailio.cfg. 

Thanks

On Fri, Jun 12, 2015 at 12:34 AM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:

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, Daniel-Constantin Mierla <miconda@gmail.com> wrote:

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, report here and I will look at it with the first chance.

Cheers,
Daniel

On 10/06/15 16:50, Ding Ma wrote:

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_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES

ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB

poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.

id: 5596bd

compiled on 09:32:37 May  6 2015 with gcc 4.4.7

On Wed, Jun 10, 2015 at 7:01 AM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:

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 the last destination entry in the dispatcher table even if I have set the maxload attributes. I'm using algorithm 10 for load distribution. The number of calls sent to one asterisk is well above the maxload. Hope someone more experienced in dispatcher can review my config and give me some recommendations. Thanks in advance.

Here is the content of dispatcher table in postgresql db.

select * from dispatcher;

 id | setid |    destination     | flags | priority |           attrs           | description

----+-------+--------------------+-------+----------+---------------------------+-------------

  1 |     1 | sip:10.0.1.31:5061 |     0 |        0 | duid=asterisk1;maxload=25 | Asterisk1

  2 |     1 | sip:10.0.1.33:5061 |     0 |        0 | duid=asterisk2;maxload=25 | Asterisk2

(2 rows)

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat