Your reference to “dispatcher is not considering registrations as load at all and only counts INVITES as load.” leads me to believe that you are trying to use algorithm 10 since that’s the only mechanism that cares about call loading.

Working from that assumption, the documentation clearly states “This algorithm can be used only for dispatching INVITE requests as it is the only SIP method creating a SIP call.”

http://kamailio.org/docs/modules/stable/modules/dispatcher.html#dispatcher.f.ds_select_dst

Brooks Bridges | Sr. Voice Services Engineer

O¹ Communications

5190 Golden Foothill Pkwy

El Dorado Hills, CA 95762

office: 916.235.2097 | main: 888.444.1111, Option 2

email: bbridges@o1.com | web: www.o1.com

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of SamyGo
Sent: Thursday, March 24, 2016 10:17 AM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List
Subject: [SR-Users] Dispatching Registrations to Weight based servers

Hi All,

I'm having a wee little bit of difficulty in trying to load-balance registrations to multiple servers based on their weights. 

Kind of similar scenario as discussed in this thread: http://lists.sip-router.org/pipermail/sr-users/2014-December/086235.html

The problem I'm facing is that dispatcher is always choosing the first destination from the group.

I do suspect that dispatcher is not considering registrations as load at all and only counts INVITES as load.

If above is correct then is there a way to use dispatcher to count registrations as load ?

Thanks,

Sammy