Hello,
I am using the Kamailio SIP registrar described in
kb.logicmachine.net/integration/sip-server/ on an LM5M3. The device tree
reports "i.MX6UL LM5M3", ARMv7 Processor rev 5 (v7l), with genohm-scada
20251204. I installed it with the official resident-script method for the
i.MX6 target:
- kamailio3 3.3.7-1_imx6, plus the maxfwd, usrloc, registrar, rr, sl
and tm modules
- your default kamailio.cfg, unmodified
First, it works well and I want to be clear about that. With no
configuration changes I get multiple contacts registered against a single
AoR, parallel forking to all of them, first-answer-wins with CANCEL to the
losing branches, and RTP flowing directly between the endpoints -
including between different subnets - since no media relay module is
loaded. This is exactly the behaviour I need from a registrar for
door-entry intercoms.
I have run into three limits that all appear to need a rebuild rather than
a configuration change, so my main question is simply: is a rebuilt
package for the i.MX6 target something that can be provided? If not, the
individual items below are moot.
1. BRANCH LIMIT OF 12
I registered 15 contacts against one AoR. All 15 registered successfully,
but an incoming call forked to only 12 of them. I repeated the test and
got 12 again, with a different subset of 12 each time. The log shows:
ERROR: <core> [dset.c:306]: append_branch(): max nr of branches exceeded
ERROR: registrar [lookup.c:298]: lookup(): failed to append a branch
Since this is MAX_BRANCHES in the core rather than a module parameter, I
cannot raise it from kamailio.cfg. I need at least 16 branches on a single
AoR.
Could the package be rebuilt with a larger MAX_BRANCHES, or with the limit
exposed as a core parameter?
2. DIALOG MODULE
It is not in the package. I looked for a kamailio3-mod-dialog .ipk at the
distribution path, using the same naming pattern as the six modules that
are published, and got 404. Same result for auth, auth_db, xlog, textops
and nathelper, while all six published modules return 200.
Without dialog there is nothing to clean up a session left behind when an
endpoint disappears without sending BYE. Device-side call timers cover
some of this, but not the case where only one side is gone.
Is adding this module possible?
3. AUTH / AUTH_DB
Also absent, so any device can register with any credentials. This is fine
on a test bench but not something I can leave in place.
4. KAMAILIO VERSION
3.3.7 is from 2013 and no longer receives security fixes. Is a current
branch (5.x or 6.x) for i.MX6 on the roadmap? I understand the
configuration syntax differs and that this is the largest of the four
requests.
ONE MORE THING THAT MADE DIAGNOSIS HARDER
There is no mi_fifo or kamctl, so I have no way to inspect the location
table and see which devices are currently registered. If there is another
way to read usrloc on the LM, I would be glad to hear it.
I am happy to test any package and report results back here.
I am using the Kamailio SIP registrar described in
kb.logicmachine.net/integration/sip-server/ on an LM5M3. The device tree
reports "i.MX6UL LM5M3", ARMv7 Processor rev 5 (v7l), with genohm-scada
20251204. I installed it with the official resident-script method for the
i.MX6 target:
- kamailio3 3.3.7-1_imx6, plus the maxfwd, usrloc, registrar, rr, sl
and tm modules
- your default kamailio.cfg, unmodified
First, it works well and I want to be clear about that. With no
configuration changes I get multiple contacts registered against a single
AoR, parallel forking to all of them, first-answer-wins with CANCEL to the
losing branches, and RTP flowing directly between the endpoints -
including between different subnets - since no media relay module is
loaded. This is exactly the behaviour I need from a registrar for
door-entry intercoms.
I have run into three limits that all appear to need a rebuild rather than
a configuration change, so my main question is simply: is a rebuilt
package for the i.MX6 target something that can be provided? If not, the
individual items below are moot.
1. BRANCH LIMIT OF 12
I registered 15 contacts against one AoR. All 15 registered successfully,
but an incoming call forked to only 12 of them. I repeated the test and
got 12 again, with a different subset of 12 each time. The log shows:
ERROR: <core> [dset.c:306]: append_branch(): max nr of branches exceeded
ERROR: registrar [lookup.c:298]: lookup(): failed to append a branch
Since this is MAX_BRANCHES in the core rather than a module parameter, I
cannot raise it from kamailio.cfg. I need at least 16 branches on a single
AoR.
Could the package be rebuilt with a larger MAX_BRANCHES, or with the limit
exposed as a core parameter?
2. DIALOG MODULE
It is not in the package. I looked for a kamailio3-mod-dialog .ipk at the
distribution path, using the same naming pattern as the six modules that
are published, and got 404. Same result for auth, auth_db, xlog, textops
and nathelper, while all six published modules return 200.
Without dialog there is nothing to clean up a session left behind when an
endpoint disappears without sending BYE. Device-side call timers cover
some of this, but not the case where only one side is gone.
Is adding this module possible?
3. AUTH / AUTH_DB
Also absent, so any device can register with any credentials. This is fine
on a test bench but not something I can leave in place.
4. KAMAILIO VERSION
3.3.7 is from 2013 and no longer receives security fixes. Is a current
branch (5.x or 6.x) for i.MX6 on the roadmap? I understand the
configuration syntax differs and that this is the largest of the four
requests.
ONE MORE THING THAT MADE DIAGNOSIS HARDER
There is no mi_fifo or kamctl, so I have no way to inspect the location
table and see which devices are currently registered. If there is another
way to read usrloc on the LM, I would be glad to hear it.
I am happy to test any package and report results back here.
