Networked PBX systems

Hint

These instructions are based on experience gained from connecting various systems. Depending on the existing environment, there may be variations in the implementation.

Problem:

You use a telephone system that serves several locations or manages several external connections (ITSP) with different external numbers. A connection with only one SIP trunk for the XPhone Call Controller (XCC) to the PBX is desired because the server and main system are connected in a central data centre.

Explanation:

The XCC is connected to the PBX via a SIP trunk. The configuration on the XPhone Connect Server as well as the user configuration is simplified by this setup. The configuration is simplified overall because a separate SIP trunk is not required for each gateway.

Preparation

Example scenario

vernetzungsszenario

Requirements

  • The PBX must be networked with the various locations so that SIP messages are transmitted from the master node to the connected XCC SIP Trunk.

  • The network must have QoS policies so that the RTP packets are prioritised.

  • The routing from the sub-locations (gateway & extension) must allow a direct connection to the XPhone Connect server. Here, it must be taken into account how the PBX handles RTP streams and whether centralised or decentralised streaming is used.

  • The transmission of call numbers from the PBX master to the XCC SIP Trunk must be in E.164 format to ensure unique call number identification. This ensures that the correct AnyDevice user can be determined.

Configuration XPhone Connect Server

Dialling parameter

For the networked system, a separate dialling parameter should be created for each location or exchange connection. It is also advisable to differentiate between SIP and CTI dialling parameters. Thus, different dialling parameters or special configurations can be implemented.

wahlparameter

Setting up the XCC SIP Trunk on the XPhone Connect Server

The SIP trunk on the XPhone Connect server is set up with the corresponding connection data:

  • The IP address of the XPhone Connect Server is used for the local gateway.

  • The IP address of the master PBX system is entered in the field of the remote gateway.

Important

The AnyDevice phone number must be stored in E.164 format. In this example, the phone number +498912345815 is used. For the conference server, only the extension number (816) may still be used!

sip-trunk

Adding dialling parameters in the SIP Trunk

In order to provide users with AnyDevice lines, the correct dialling parameter must be stored on the SIP Trunk.

  • Select the SIP Trunk.

  • Click Create Lines to add more dialing parameters.

leitungen1

Click Add to create a new area.

leitungen2

Set the value * for the From and To fields to include any phone number of the location.

A corresponding SIP dialling parameter of the other locations must be selected as dialling parameter.

leitungen3

Save the phone number range and add more if necessary.

Important

Once all the dialing parameters of the locations have been added, end the recording via Close! The line generation must NOT be executed!

leitungen4

Add AnyDevice line of users

In the user administration, users receive an AnyDevice line via AnyDevice Wizard. The distinction is whether the user also uses a CTI line or not (AnyDevice Only).

The corresponding SIP trunk is used as the trunk.

Dialing parameters / Special configuration CSTA

For other locations (e.g. Berlin and Hamburg) special configurations must be carried out in the dialling parameters. The AnyDevice call number from the XCC SIP Trunk must be edited for the CSTA dialling parameter. Call forwarding is usually only performed on the extension number, therefore a PhoneToDisplay rule must be created which adapts the extension number to the E.164 format.

  • Open the dialling parameters/special configuration via the XPhone Connect Server Manager (Tools).

  • Log in with the administrator access of the XPhone Connect Server (default: admin/admin , but you should change this login data!).

  • Select the corresponding dialling parameter for the CTI connection (here: Berlin location).

  • Add a new entry via the New item.

wapasoko_0

  • For Name, use the item PhoneToDisplay.

  • For Value 1, set your values for the extension of the AnyDevice number.

  • For value 2, set the AnyDevice call number of the main location in E.164 format.

  • Click OK.

wapasoko_2

  • Finally, set the DefaultPhoneToDisplay settings via the dialing parameter.

  • To do this, use the E.164 format so that the previously set dialing parameter takes effect.

  • Click OK.

These steps must be carried out for all further election parameters (e.g. Hamburg). For the locations Berlin and Hamburg, the configuration then looks like this, for example:

wapasoko_5

wapasoko_6

Other dial parameter settings

If the PBX expects all call numbers via the SIP trunk - even with an internal dialling - in E.164 format, the following values must be set.

Dialing parameters for SIP connection

In the dialling parameter for the SIP connection (e.g.: Berlin_SIP or Hamburg_SIP) the attribute Flags must be set with the value 304. The value results from the addition of the value 48 (external call number in the format +49…) and the value 256 (internal call number in the format +49….). Thus, for outgoing calls from the XCC SIP trunk to the PBX, the To header is signalled in the E.164. This step must then be carried out for all other SIP dialling parameters of the connected locations, including the main location.

sip_wapa_1

Adaptation of the atlas.xml

If the attribute Flags is set with the value 304 in the dialling parameters, the check of the internal call number must be deactivated via the atlas.xml when generating lines for AnyDevice lines.

Therefore, the following value must be added in the atlas.xml under Configuration:

<Telephony PBXAutoConfig="64"/>

atlas

Caution

For the change in the atlas.xml to take effect, a restart of the server services is required.

Dialling parameters / Special configuration SIP

For dialling parameters of the SIP Trunk, the attributes DefaultPhoneToDisplayFormat should also be set to the value 64. This will display all phone numbers in E.164 format. This adjustment should be made to all dialling parameters that are required for the AnyDevice connection.

Have you found a mistake on this page?

Or is something not formulated well or too vague? Then we look forward to receiving an e-mail, preferably with a suggestion for improvement, to doku@c4b.de. Thank you very much!