How can I adjust the configuration for unsupported VOIP providers or gateways?

How can I adjust the configuration for unsupported VOIP providers or gateways?

3CX performs extended tests with a number of VoIP Providers and Gateways. This allows us to create optimized templates for use with these tested Providers and Gateways, based on the information collected during the course of these tests.

It is STRONGLY RECOMMENDED that if at all possible, you use a VoIP Provider or Gateway from within the list of pre-configured templates, because these templates are known to work, and have been extensively tested, and in many cases including the collaboration of the respective service or hardware vendor.

Why is manual configuration sometimes necessary?

Since the number of VoIP Providers and Gateway manufacturers are very large, and their numbers are still on the rise, it is obviously impossible to prepare templates for all of them.

Because of this, 3CX  supplies Generic Templates which contain the most common set of parameters in use as observed during tests.

Most Providers and Gateways build (when sending) or interpret (when receiving) signals using a standard set of parameters. So if a new Gateway device appears on the market, or a new VoIP Provider starts offering services, these Generic Templates provide a reasonable set of configuration options to work with the Provider or Gateway “out of the box”.

However some VoIP Providers or Gateways may be designed to send the information in some non-standard, or at least, not common, configuration, making it difficult for the 3CX Phone System to correctly identify or even interpret the information.

In these situations, an advanced user may create a custom configuration to create a working set of parameters for his Provider or Gateway.

Advanced Custom Gateway and VoIP Provider Configuration

In order to enable much improved interoperability with a much wider range of Gateways and Providers, 3CX Phone System provides the possibility to customise parameters with which an incoming call is identified, and how to recognise the information relevant to the call.

Source Identification

This is the section where we can tell 3CX Phone System how to identify the source of an incoming call.

It is typically necessary to adjust this section when the entity sending the incoming request (INVITE) specifies an unknown contact.

You can specify a maximum of three Field and Value combinations to identify the source of the call. You can also specify whether ALL of the specified combinations or ANY ONE of the combinations are necessary to provide a match.

If a provider requires customisation to allow source identification, and since this provider sends the External Line Number assigned to the VoIP Account in the “User” part of the “Request Line URI” field, we can configure this section as follows

  • For the “Matching Strategy” field, select “Match Any Fields”.
  • In the “SIP Field” column, set the top-most field to “Request Line URI : User Part”.
  • In the “Value” column, set the top-most field to “Line Number”.

Outbound Parameters

This is the section where we can tell the 3CX Phone System how to build the request when effecting an outbound call.

These settings may be changed in situations where the VoIP Provider or Gateway is expecting some information in some non-standard format. So if for example, the VoIP Provider expects to see the CallerID (our number, in this case, since it is an outgoing call) in the User part of the “Remote Party ID – Calling Party” field, we can configure this section as follows:

  • In the “SIP Field” column, identify the row for “Remote Party ID – Calling Party : User Part”
  • In the “Value” column, set the field to “CallerName” – which is retrieved from the “Outbound Caller ID” field in the “Edit Extension” page in the “Other Options” section.

Inbound Parameters

This is the section where we can tell 3CX Phone System how to interpret the request when receiving an inbound call.

These settings may be changes in situations where the VoIP Provider or Gateway is sending some information in some non-standard format. So if for example, the VoIP Provider sends the CallerID (the remote person’s number, in this case, since it is an incoming call) in the User part of the “Remote Party ID – Calling Party” field, we can configure this section as follows:

  • In the “SIP Field” column, identify the row for “Remote Party ID – Calling Party : User Part”.
  • In the “Value” column, set the field to “CallerName” – which is how the 3CX Phone System refers to the Caller ID.

Liked this article?


Get notified of new articles
or share
You might also be interested in: