In the General Tab, you can change the Bind Port, which is the port used to register IAX2 devices and trunks. If you change this port, you also need to change it in the Firewall Services. You can also change the default Language for the voice prompts that IAX2 devices use. Additionally, you can set the Bandwidth which will determine the codec to use from the selected codec list.

Next, we have the Registration Tab. This tab holds settings used for different timings and counts.

Afterward, there’s the Codecs Tab. This tab allows you to choose who has the Codec Priority.
This can be one of the following options.

• Caller (Default) – This considers the caller’s preferred order over the host’s.
• Host – This considers the hosts’s preferred order over the caller’s.
• Disabled – This disables the consideration of codecs altogether. This is the original
  behavior prior to the addition of preferences being added.
• Reqonly – This is the same as Disabled. The call is only accepted if the requested
  format is available.

Below, you can choose the codecs to be used with IAX2 devices and trunks. In the left column,
you have the Available Codecs, and to the right the Selected Codecs.

Finally, we have the Security Tab for the IAX2 Settings. Here you will find various security
parameters that you can add to IAX2 devices.

First, let’s go to Settings > Technology Settings > PJSIP Settings. Here you will find general settings for the PJSIP protocol.

We visited this module when we looked into the NAT Settings. But aside from this, here you can define default Codecs PJSIP extensions and Trunks will use. You can also change the general Language that is used for voice prompts used with PJSIP endpoints. Here you can also change the Bind and TLS Bind ports. If you change these ports, you must also make the change in the Firewall so your devices can register with the new ports.

Other important aspects you will find here are the Certificate and SSL Method, but we will see more about this when we take a look into the security features with VitalPBX.

Most of the time, these features will be left with the default value, but if you make any changes here, you can Save and Apply Changes.

Now, let’s look into PJSIP Transports. These can be created under Settings > Technology Settings > PJSIP Transports.

PJSIP Transports are usually used when the server in which VitalPBX is installed has multiple network interfaces and you have SIP/PJSIP Trunks connected through these interfaces. When you configure the NAT settings, the IP address used for the SDP (Session Description Protocol) is the one defined in the NAT settings. Thus your Trunk Provider will reject the calls because you are not sending the IP Address assigned to you for their service.

Here is where PJSIP Transports come into play so you can create a transport where NAT settings are not used and can then be assigned to a Trunk. This way, the trunk at the moment of creating the SDP uses the IP assigned to the interface connected with the Trunk Provider.

This is a very particular case, and it is uncommon with internet-based VoIP providers. Default Transports for UDP, TCP, WebRTC, and Microsoft© Teams trunks are created automatically, so there is no need to create these and they cannot be modified or deleted. So creating PJSIP Transports is rare unless you need it for your use case.

Here you will see all of the active calls in your VitalPBX at that moment in real-time. If you place a call to another extension or a feature code, you will see the call appear and display information about that particular code.

Next, we will see modules specific to PJSIP, SIP, and IAX technologies. Within these modules, you will see information about the extensions, trunks, and outbound registrations in your VitalPBX.

We will only see the PJSIP module as this is basically the same for SIP and IAX devices. So we go to Reports > PBX Reports > PJSIP Endpoints.

The module will have three tabs. In the case of PJSIP, we first have the Endpoints tab these are the devices created for our extensions. You can see the extension number they are associated with, as well as the registration status for the devices. Since PJSIP can have multiple registrations for a single device, you may see multiple contacts in the contacts column. What is important to see here is that contacts have a status indicator. This indicator will shift from red to green depending on the registration status. All of this is updated in real-time. This way, you are able to monitor the registration of your devices. So if you turn off or de-register a device you will see it turn red or disappear from the table in real time.

The next tab is the Trunks tab.

In the trunks tab, you can see your trunks and the registered devices. Similarly to the extensions, you have a status indicator to see if your trunk is registered successfully. The green indicator would mean that the trunk is registered successfully.

Trunks can be extended to the Outbound Registrations tab if you are using registration authentication with your trunks. This means you have a username and secret to register your trunks.This tab will give you additional information about your registration status.

As mentioned before, this is the same idea for the SIP and IAX devices reports. With these reports, you can monitor in real-time the registration status of your extensions and trunks.