Configure the connection to your Phone System
Add Extensions to an existing Phone System
SIP Caller connects to your phone system as a remote extension. You could think of SIP Caller as a phone that connects to the PBX to make calls.
SIP Caller operates from the cloud. This means that it will connect to your Phone System from a public IP address (which might change depending on your location), and this might require some configurations depending on the location of your Phone System.
This is the most common case nowadays, and the simplest scenario to integrate SIP Caller with your Phone System. In this case, both endpoints (SIP Caller and the Phone System) are in the cloud, and that means that there are no firewalls between them, except by the firewall running in the Phone System itself. The connection in this case is straight forward. You will just need to configure SIP Caller with the public IP address or Host Name of your Phone System, and eventually add the SIP Caller IP addresses white listed in your Phone System firewall. No additional configuration is needed.
The global trend is that users are moving their Phone Systems to the cloud, so this scenario is becoming less common every day. However, some companies still prefer to have their Phone Systems on-premise. If this is your case, your Phone System will be behind a firewall, and you will need to configure this firewall to allow the incoming SIP and RTP traffic from the cloud to your Phone System server. You probably already have this inbound rule traffic open for your SIP Trunk, but you might need to enable the IP addresses of SIP Caller as well.
In order to create or edit a Phone System, the user needs one of the following roles:
In order to view a Phone System, the user needs one of the following roles:
SIP Caller connects to your Phone System as a remote extension. Therefore, in order to use SIP Caller with your Phone System you will need to create an extension for it, and then obtain the SIP credentials.
To set up the connection to your Phone System:
Tip: if your Phone System is using a port number for the SIP protocol different than 5060, you can configure this using the colon (:) separator, for example: mypbx.example.com:5061
The number of Phone Systems you can register in your SIP Caller account is limited according to the plan you choose. However, you can add as many extensions as you need to a single Phone System.
You might want to configure SIP Caller with multiple extensions in your Phone System. This could be useful for example to run some campaigns using an extension, and other campaigns using a different extension. This could provide the following benefits:
To add extensions to your Phone System, go to the “Phone Systems” section in the management console, and click the Phone System you want to edit. Then add the extension by clicking “Create” in the “Extensions” section.
When you need to run campaigns in “Predictive Dialer” mode, queue monitoring must be enabled. This requires that you install the “SIP Caller Proxy” module in your phone system server. This module will report the status of the queues in real time.
In order to install the “SIP Caller Proxy” module, click on the “Show details” link to expand this section, and then follow the step by step instructions provided. As part of this procedure, you will need to create an API Key which then needs to be configured for the module.
Once the “SIP Caller Proxy” module is installed and running, this section will list the queues that have been detected in your phone system. Once these queues are reported, you will be able to select a queue for predictive dialing when creating your campaign.
Any Phone System supporting the SIP & RTP standards can be integrated with SIP Caller. We have deeply tested SIP Caller with the following systems, and we provide step by step guides to make the integration a breeze:
* All trademarks mentioned are not affiliated with Easy Caller LLC, its products, or its websites. The owners of these trademarks are not the source of, and do not sponsor or endorse, the products/services promoted here. All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.