KamoCRM

Resolve the Kamailio question — SIP registration works end to end

Docskamo-login
Ya
27 Agosti 2026, 16:23 UTC
Mwandishi
Kamo
Ahadi ya
5a2bbf1

Section 16 recommended a purpose-built config on stock Kamailio and recorded that "2600hz/kamailio does not exist". Both are corrected by evidence. Two further patched-only constructs turned up, and routes() is decisive: default.cfg:235 is routes("KZ_$(rm)_START_ROUTE"), a route name computed at RUNTIME, which stock route() cannot express. A preprocessor for the other three was written, got the tree to parse, and was then discarded — ~60 call sites cannot follow. The fork does exist but its 5.7 branch is a plain upstream mirror. The patches ship as RPMs at **************** which also carry db_kazoo.so, KazooDB and KazooDB-diff. On that base the vendored config parses unmodified, so the SBC layer is kept and nothing is forked. The interim "SIP via FreeSWITCH first" decision is superseded the same day: it was tried and does not work. Kazoo's sipinterface_1 answers REGISTER with 405 and omits it from Allow: by design, and a hand-rolled public profile authenticated against FreeSWITCH's LOCAL directory rather than Kazoo. Records five more traps found during bring-up, including the RabbitMQ consistent-hash plugin — its absence makes every REGISTER hang after "100 checking your credentials" while every component still reports healthy.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei