Pre-Requisites
Connecting the Starface v6 PBX requires licensing the o-byte connector from o-byte and installation on the Starface PBX.
This guide covers the configuration of the jtel System.
jtel requires the IP-Adress of the Starface endpoint. Either the IP from the local network, or a public IP-Adress if the Starface is located elsewhere.
jtel requires a phone number and user for testing.
Additional instructions on configuration of the Starface PBX and the o-byte Connector can be obtained from o-byte.
jtel STARFACE v62 Service
The jtel STARFACE v62 Service must be installed on one of the telephony server machines.
Copy Files
Copy the following directory to the telephony server:
Source Directory: \\acd-store\shared\JTELCarrierPortal\WebServices\Install\Starface\ServiceV62 Target Directory: c:\jtelStarface6v2SOAPWindowsService
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
If the windows firewall is active, add a rule to allow http traffic into the web service.
Use the following in a cmd window as administrator:
netsh advfirewall firewall add rule name="jtelStarface6v2SOAPWindowsService" dir=in action=allow protocol=TCP localport=56745 edge=no
Note, 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.
Install as Service
Using a command window, as Administrator:
c: cd \jtelStarface6v2SOAPWindowsService c:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe -install jtelStarface6v2SOAPWindowsService.exe
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.