KamoCRM

The platform main line survives a boot, and 8200 is the team line

FixKlusterServices
Shipped
29 செப்டம்பர், 2026 அன்று 1:40 AM UTC
Author
Kamo
Commit
c37e8e4

Luna's go-live (2026-09-28) wrote [kamo-main-luna] into extensions_custom.conf and KAMO_LUNA_EXT / KAMO_LUNA_MAX_RING into globals_custom.conf by hand on the hostPath. startup.sh rewrites globals_custom.conf on every boot, so a pod restart dropped both globals from the file and, at the next Asterisk start, from memory: the main line then dialled an empty extension and Luna silently stopped answering (SP95 spec 3.6). - globals: KAMO_LUNA_EXT = 8123 and KAMO_LUNA_MAX_RING = 30, written on every boot. - [kamo-main-luna] appended once under its own grep guard, the context byte for byte as live, so a rebuilt node gets the main line too; the live node keeps its copy. - [kamo-ai-xfer]: exten 8200 -> kamo-inbound-attendant,s,queue, the team line an AI's unnamed transfer rings (the kamo-main queue, Sage + Erik; SP95 D11). Existing nodes get it by hand (SP95 Task 24). - test_sp95_main_line runs the dialplan-writing part of startup.sh against a temporary /etc/asterisk (fresh node, and the go-live node) and pins the main-line routing; the SP13 host-patch test now compares against the attendant block without SP95's lines. Takes effect at the next boot; no reload needed.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing