Introduction
The following page describes the required configuration to connect the jtel ACD to Starface.
Pre-Requisites
Installation of the Starface v6 BPX requires licensing the o-byte connector from o-byte and installation on the Starface PBX.
This guide covers the configuration of the jtel System. Additional instructions regarding the configuration of the Starface PBX and the o-byte Connector can be obtained from o-byte.
Before installation may begin, jtel requires the following:
- IP-Adress of the Starface endpoint - Either the IP from the local network, or a public IP-Adress if the Starface is located elsewhere
- Test number (Will be configured as a Test-Servicenumber in jtel)
- Test user (Will be configured as a Testuser in jtel)
jtel STARFACE v6.2 Service
The jtel STARFACE v6.2 Service must be installed on one of the telephony server machines. The following describes the required steps for installation.
Copy Files
Copy the following directory to the telephony server:
Translations Ignore | ||
---|---|---|
|
Check Configuration
Check the configuration file jtelStarface6v2SOAPWindowsService.exe.config if any changes are required.
The most likely changes would be to the sections:
- <connectionStrings>- for connecting to the database
- <appSettings> - for specifying the machine and UDP port of the acd Daemon Process
- <log4net> - for specifying the location of the log file
Configure Firewall - Starface Located In Local Network
Add a rule to allow http traffic into the web service.
Use the following in a cmd window as administrator:
Translations Ignore | |||||
---|---|---|---|---|---|
|
Configure Firewall - Starface Located At External Network
If the STARFACE is in a different network, you will need to change to edge=yes and configure a public remote IP-Adress in the SIP and RTP firewall rules to provide access.
Translations Ignore | |||||
---|---|---|---|---|---|
|
Install as Service
Using a command window, as Administrator:
Translations Ignore | ||
---|---|---|
|
Trunk and Trunk Group Configuration
Login as sysadmin to the jtel Portal.
Configure Trunks
Use System Settings ... Trunks to configure a trunk for each 8-Server machine.
Note, the machine ID is set in the 8-Server configuration (usually the last part of the IP address of the machine).
Configure Trunk Groups
Create a new trunk group for each STARFACE PBX.
The following parameters are required.
Parameter | Value | |
---|---|---|
Name | For example STARFACE | |
Country Code | Select the correct country code | |
Outgoing Trunk Selection | Trunk Group for Internal Numbers | Set to the same trunk group (explicitely) |
Trunk Group for External Numbers | Set to the same trunk group (explicitely) | |
Generall access for outbound calls | Only check this option, if this is a single customer installation. | |
Number Translator | Incoming Caller | E.164 with + incoming |
Incoming Called | STARFACE - remove converter parameter (usually 019900) | |
Converter Parameter | 019900 | |
Outgoing Caller | VOIP - Add prefix "sip:+", then E.164 number and postfix "@<Converter Parameter> | |
Converter Parameter | <IP_Address_8-Server>:5060 For example: 192.168.1.1:5060 | |
Outgoing Called | VOIP - Add prefix "sip:", then E.164 number and postfix "@<Converter Parameter>" | |
Converter Parameter | <IP_Address_STARFACE>:5060 For example: 192.168.1.100:5060 | |
Internal Number Length | Set to the maximum length of internal PBX extension numbers, for example 3 |
Add the trunk created above for the PBX to the Trunks page. DO NOT FORGET THIS, OR IT WILL NOT WORK!
See the screenshot below for an example configuration:
Configure Service Numbers
Service-Numbers are configured as fully qualified E.164 numbers.
Agent Telephone Numbers / PBX Internal Destinations
Agent telephone numbers are configured only with the number of the internal extension, not as fully qualified E.164 numbers.