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 - Linux

The jtel STARFACE v62 Service must be installed on one of the telephony server machines.

Windows Firewall
sudo dnf install dotnet-sdk-8.0
mkdir -p /home/jtel/jtel-starface-listener
cd /home/jtel/jtel-starface-listener
cp -r /home/jtel/shared/JTELCarrierportal/WebServices/Install/Starface/StarfaceSoapService/* .
unzip bin.zip
sudo install.sh
mv bin/appsettings.json .

# change configuration as required
vi appsettings.json # normaly no changes required


sudo systemctl start jtel-starface-listener.service
sudo systemctl status jtel-starface-listener.service

# Testing
curl -k https://localhost:56745/jtelStarface6v2SOAPServiceLibrary?wsdl

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:

Windows Firewall
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.

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.

ParameterValue
NameFor example STARFACE
Country CodeSelect the correct country code
Outgoing Trunk SelectionTrunk Group for Internal NumbersSet to the same trunk group (explicitely)
Trunk Group for External NumbersSet to the same trunk group (explicitely)
Generall access for outbound callsOnly check this option, if this is a single customer installation.
Number TranslatorIncoming CallerE.164 with + incoming
Incoming CalledSTARFACE - remove converter parameter (usually 019900)
Converter Parameter019900
Outgoing CallerVOIP - 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 CalledVOIP - 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 LengthSet 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.

Configure SOAP User

Create the SOAP User as an agent in jtel and give the username and password to the starface provider for Module configuration


Old - Windows

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


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
  • No labels