Operate the offsite PBX

This runbook checks the offsite PBX. That Asterisk takes every call voip.ms delivers to the sub-account 168847_elevenlabs and hands it to the troll agent at ElevenLabs. Use it when PBXDown or PBXTrunkNotRegistered fires on offsite, or when a troll call fails.

Before you start#

• Get kubectl access to offsite (Get cluster admin access).
• Get access to offsite's VictoriaLogs.

The config is clusters/offsite/apps/pbx/. A merge under that directory or clusters/base/apps/pbx/ restarts the pod, and so does a change to its pbx-secrets.

Check the registration#

1. Show the registration.

   kubectl --context offsite -n pbx exec deploy/pbx -c asterisk -- \
     /bin/asterisk -C /etc/asterisk/asterisk.conf -rx 'pjsip show registrations'

   Result: vms-elevenlabs shows Registered, over TLS to the numbered server that pbx-env names.

2. Show the identifies.

   kubectl --context offsite -n pbx exec deploy/pbx -c asterisk -- \
     /bin/asterisk -C /etc/asterisk/asterisk.conf -rx 'pjsip show identifies'

   Result: One identify for vms-elevenlabs, on X-Dest-User: 168847_elevenlabs.

Read a call#

1. In offsite's VictoriaLogs, query the call events.

   {namespace="pbx", container="asterisk"} "pbx-event"

   Result: Each call logs kind=inbound. Then it logs kind=troll and kind=held with its length, or kind=troll-miss with a why.

2. Remove "pbx-event" from the query to read the SIP of the call.

   Result: voip.ms sends the INVITE down the registration's TLS connection. It addresses s with a line parameter, or digits with X-Dest-User: 168847_elevenlabs.

If something goes wrong#

Offsite refuses every call the agent does not take before it answers, so voip.ms sees that call fail.

Related#

• PBX
• ElevenLabs
• Operate the office phone: the folly PBX, and how to read its SIP