General
Connection
The XPhone Call Controller (XCC) is a softswitch or media controller that is connected to telephone systems (PBX) or session controllers (SBC) via SIP gateways (SIP trunks). Please note that the ports of a possibly existing XCAPI controller do not collide with those of the XCC. Alternatively, you can also work with different IP addresses for XCAPI and XCC.
Hint
For the most common telephone systems and SBCs there are connection instructions. If your system is not included, you can connect the XCC via a Native SIP Trunk.
Variants
The XPhone Call Controller can be installed either together with the XPhone Connect Server or separately on a Linux Satellites:
The configuration of the features is done in the same way via the Web Administration.
Hint
In the case of integrated XCC, the resources of the XPhone Connect Server are shared by all services and programmes of the Windows Server. A CPU / main memory utilisation of more than 80% can cause impairments and quality losses of the XCC voice transmission (Conference, AnyDevice, Follow-Me). Remedy:
Allocation of additional CPU cores or main memory for the XPhone Connect Server.
Offloading the XCC to Linux satellites.
Features
The following features require XPhone Call Controller (XCC) and SIP Gateways:
Softphone Desktop
Softphone Mobile
AnyDevice
Meeting (dial-in conference)
TeamDesk
Requirements
The XPhone Call Controller and its functions, such as the softphone, depend on being used in a VoIP Ready network for smooth operation (good voice quality, no delays).
Please ensure that all components involved in VoIP (Windows Server, PBX, SBCs, Windows Clients …) use the same time server if possible. The Time synchronisation is a prerequisite for “VoIP Ready” and can be enabled via NTP (Network Time Protocol), for example.
Set Quality of Service for the XPhone Server and the XPhone Clients.
Hint
Also note already during planning that additional trunk channels as well as internal SIP channels of the telephone system used may be required for this feature. For example, an external telephone call with an external AnyDevice requires two trunk channels and for a consultation call to an external subscriber three.
In the case of the integrated XCC, the resources of the XPhone Connect Server are shared by all services and programmes of the Windows Server. A CPU / main memory utilisation of more than 80% can cause impairments and quality losses of the XCC voice transmission (conference, AnyDevice, Follow-Me). By allocating additional CPU cores or RAM for the XPhone Connect Server, impairments can be reduced and additional participants can be supported.
In order for a conference from an AnyDevice consultation call to work, the Office number must currently be stored in the master data in E164 format, e.g. +4989840798192.
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!