Admin Level

The Vodia PBX uses the notion of a tenant to describe a group of users that are able to distribute and transfer calls within that group, see the status of other users, reassign mailbox messages and generally collaborate on voice calls. They can also access the same address book and share features, such as call monitoring and call park/pickup. Tenants are generally not aware of the presence of other tenents on the same PBX instance.

📄️ Admin Email

Sending out emails is an important mechanism for the system to stay in touch with administrators and users. Emails can be used to set up welcome and password reset emails, they can be used to send voicemail messages, messages about missed calls and other status emails to extensions and send reports about the call queues and other accounts to managers.

📄️ Template Parameter

When the PBX generates the provisioning files for VoIP phones, it uses

📄️ Certificate Management

The PBX uses TLS in secure communication, e.g. for HTTP and SIP traffic. This works only if the system has a pair of private keys and certificates. Depending on the direction of the communication, it needs to either present a certificate (e.g. web server) or trust certificates from other parties (e.g. when the PBX pulls information from other sites).

📄️ Monthly Billing

In hosted PBX environments, clients need to be billed monthly. The PBX can automatically generate invoices at the beginning of a month, based on the usage of the previous month.

📄️ Music on Hold Sources

Music on hold (MoH) is recorded music that callers listen to while waiting on hold. It is used to avoid silence on the line and is used in several places of the system file, wave input, and RTP stream. These sources serve different purposes and are detailed below. The sources can be used in parallel in different locations on the same system. They can be assigned to different domains or all domains so that they can appear as moh options in those domains.

📄️ Network Port Settings

The ports page allows you to control which networking resources the system will utilize when communicating with the outside IP world. When specifying ports, list the ports that you may bind to, either specifying a port number or explicitly specifying the IP address and the port, separated by a colon (e.g., 192.168.1.2db8:5060). If you are only specifying the port number, the system will bind to all IPv4 and IPv6 addresses on the system. If you want to bind only to IPv4 sockets, use the form 0.0.0.05060. In general, you may bind to more than one socket; just separate the addresses by spaces. If you do not want to use the service, leave the field empty. If you change a port binding, you will need to restart the Vodia PBX service. We support the default SIP port.

📄️ IP Access Control

It is important for the stability of the system to control who has access to the network ports. This is controlled in the Settings → Security → Access page. There are several reasons why a system administrator might want to define who has access to the system:

📄️ System Security

Security Settings

📄️ Administrator Login

📄️ Administrators

Administrators

📄️ Admin Security

This page has been split up into five different pages:

📄️ Admin SIP and Audio (RTP) Settings

SIP Settings

📄️ User Page Control

The User Page Control feature allows administrators to preconfigure settings for the Vodia web app and provides granular control over what users can see and access. Administrators can hide specific settings, such as mailbox configurations, to simplify the user interface or restrict access to certain features.

📄️ Audio Files

Adding files

📄️ Number Management

Calls

📄️ Event Notification

The system sends notifications to users and administrators when certain events occur. This can be done by email or by text messages (SMS). Those messages are usually just warnings, however the administrator should check if there is a serious issue causing the problem that needs attention.

📄️ Admin Settings

📄️ Tenant Management