Advanced Search
Search Results
488 total results found
Agent Average Talk Time
The Agent Average Talk Time statsboard report adds a reusable card for Agent average talk time. Use it inside Status > Statsboards when the selected tenant needs this metric on a custom operations board. Agent Average Talk Time example with fictional data. Con...
Provider
The Provider object is supported by the MiRTA PBX OpenAPI endpoint. This object is managed at system scope and requires a global API key. Object Summary Property Value Object provider Primary path /providers ID field pr_id Label field pr_name Primary source ta...
Auth Token
The Auth Token endpoint generates or resets temporary login tokens for web users and extension web identities. The generated token can be used in place of the user password on the MiRTA PBX login page. Authentication Scope This endpoint always requires the glo...
Shared Provider Fields
These fields appear on the provider page before technology-specific realtime options. Some fields are hidden when they do not apply to the selected provider technology. Information Provider Information fields filled with fictional SIP values. Field Applies to ...
SIP Provider
Use SIP technology for chan_sip provider trunks. SIP providers can create and maintain a global sipfriends realtime row when Use Realtime Account is enabled. SIP realtime account settings with fictional chan_sip trunk values. Common Realtime Fields Field Appl...
PJSIP Provider
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...
IAX2 Provider
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...
DAHDI Provider
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...
LOCAL Provider
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...
SMS Provider
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
Built-in destination actions available in tenant call routing.
Overview
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...
Configuring Google Drive as Recording Storage
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...
Campaign Numbers
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...
AI Analysis
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, ...
Dealing with Amazon AWS DNS limits
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 ...
Phone Book
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 ...
Phone Book Entry
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...