Search Results

Use PJSIP technology for res_pjsip provider trunks. MiRTA PBX maintains related ps_endpoints, ps_aors, ps_auths, and ps_endpoint_id_ips rows when realtime is enabled. PJSIP realtime account settings with fictional res_pjsip trunk values. Common Realtime Fi...

Use IAX2 technology for IAX trunks and legacy interconnects. IAX2 uses fewer signaling fields than SIP/PJSIP and stores its realtime account in iaxfriends. IAX2 realtime account settings with fictional gateway values. IAX2 Fields Field Applies to Purpose Fict...

Use DAHDI technology for analog, PRI, or hardware channel-group resources that are managed by the telephony node outside SIP/PJSIP realtime. DAHDI providers do not show the realtime account block. DAHDI provider fields with fictional analog gateway values. DAH...

Use LOCAL technology when a PBX-local route should be selected by routing profiles like a provider. LOCAL providers do not create SIP, PJSIP, or IAX realtime rows. LOCAL provider fields with fictional local route values. LOCAL Field Details Field Applies to Pu...

Use SMS technology for outbound text-message delivery. SMS providers reuse provider identity, status, outbound digit manipulation, additional headers, channel limits, and penalty fields, then expose protocol-specific delivery fields. SMS Field Details Field Ap...

Special Destinations Special destinations are built-in PBX actions that can be selected from destination fields in extensions, DIDs, IVRs, queues, flows, and other routing objects. They do not route to a normal endpoint; instead, they execute a predefined dial...

You can use Google Drive as a Recording Storage only inside a Shared Drive created in Google Workplace. A normal, personal, GMail account cannot use the Google Drive as Recording Storage. Access the Google Cloud Console Access your Gmail account then connect t...

The Campaign Numbers page manages the destination numbers attached to a selected voice, SMS, or fax campaign. Open it from Configuration > Call/SMS/FAX Campaigns by selecting Manage numbers for the campaign. The page uses the tenant selected in the top bar. Th...

The AI Analysis endpoint returns transcript, AI summary, and sentimental analysis data for recorded calls. It is a read-only OpenAPI endpoint and supports GET only. Use this endpoint when an integration already has an Asterisk uniqueid from CDR, Simple CDR, ...

In a client configuration I noticed he was using 127.0.0.1 as DNS in /etc/resolv.conf and asked about an explaination. This is his answer: The 127.0.0.1 loopback configuration is intentional. We were experiencing intermittent issues because Asterisk relies so ...

The Phone Book object is supported by the MiRTA PBX OpenAPI endpoint. This object is tenant-scoped. Tenant API keys must include tenant=CANISTRACCI; writes require a writable API key. Object Summary Property Value Object phonebook Primary path /phonebooks ID ...

The Phone Book Entry object is supported by the MiRTA PBX OpenAPI endpoint. This object is tenant-scoped. Tenant API keys must include tenant=CANISTRACCI; writes require a writable API key. Object Summary Property Value Object phonebookentry Primary path /pho...

The Extension State endpoint returns live call-state information for one extension. It is a read-only OpenAPI endpoint and supports GET only. This endpoint checks the extension registration server and queries Asterisk manager for the active channel, matching ...

The Dial endpoint originates a call between a source extension and a destination number. It is the OpenAPI equivalent of proxyapi.php?reqtype=DIAL and uses the same PBX dialplan contexts. The endpoint requires a tenant context and a full API key. Read-only AP...