Versions Compared

Old Version 3

changes.mady.by.user jtel Support

Saved on

compared with

New Version Current

changes.mady.by.user jtel Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed translated content for 'fr'
Sv translation
languageen


Info
title

Introduction

...

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

jtel STARFACE v6.2 Service

...

Service must be installed on one of the telephony server machines.

...

Translations Ignore


Code Block
titleWindows 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:

Translations Ignore


Code Block
titleWindows 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).

Image Added

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:

Image Added

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:

Translations Ignore


Code Block
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 - Starface Located In Local Network

Add a rule to allow http traffic into the web service.

...


Install as Service

Using a command window, as Administrator:

Translations Ignore


Code Block
titleWindows Firewall
netsh advfirewall firewall add rule name="jtelStarface6v2SOAPWindowsService" dir=in action=allow protocol=TCP localport=56745 edge=no

Configure Firewall - Starface Located At External Network

...

c:
cd \jtelStarface6v2SOAPWindowsService 
c:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe -install jtelStarface6v2SOAPWindowsService.exe



...

Sv translation
languagede


Code Block
titleVoraussetzungen
Der Anschluss der Starface v6 TK-Anlage erfordert die Lizenzierung des o-byte Anschlusses von o-byte und die Installation auf der Starface TK-Anlage.
Diese Anleitung behandelt die Konfiguration des jtel Systems.
jtel benötigt die IP-Adresse des Starface Endpunktes. Entweder die IP aus dem lokalen Netzwerk, oder eine öffentliche IP-Adresse, wenn sich das Starface an einem anderen Ort befindet.
jtel benötigt eine Rufnummer und einen Benutzer für den Test.
Weitere Anleitungen zur Konfiguration der Starface-Telefonanlage und des o-byte Connectors können bei o-byte angefordert werden.

jtel STARFACE v6.2 Dienst

Der jtel STARFACE v6.2 Service muss auf einem der Telefonie-Server-Maschinen installiert sein.

Dateien Kopieren

Kopieren Sie das folgende Verzeichnis auf den Telefonieserver:

Translations Ignore


Code Block
Source Directory:
\\acd-store\shared\JTELCarrierPortal\WebServices\Install\Starface\ServiceV62

Target Directory:
c:\jtelStarface6v2SOAPWindowsService


Konfiguration

Überprüfen Sie die Konfigurationsdatei jtelStarface6v2SOAPWindowsService.exe.config, ob Änderungen erforderlich sind.

Am wahrscheinlichsten sind Änderungen an den Abschnitten:

  • <connectionStrings>- für die Verbindung mit der Datenbank
    <appSettings> - für die Angabe des Rechners und des UDP-Ports des acd-Daemon-Prozesses
    <log4net> - für die Angabe des Speicherorts der Protokolldatei

Firewall Konfigurieren

Wenn die Windows-Firewall aktiv ist, fügen Sie eine Regel hinzu, die http-Verkehr für den Webdienst zulässt.

Verwenden Sie in einem cmd-Fenster als Administrator den folgenden Befehl:

Translations Ignore


Code Block
titleWindows Firewall
netsh advfirewall firewall add rule name="jtelStarface6v2SOAPWindowsService" dir=in action=allow protocol=TCP localport=56745 edge=no



Wenn sich das STARFACE in einem anderen Netzwerk befindet, müssen Sie auf edge=yes

Install as Service

umstellen und eine öffentliche Remote-IP-Adresse in den SIP- und RTP-Firewall-Regeln konfigurieren, um den Zugang zu ermöglichen.

Als Dienst installieren

Verwenden Sie ein Befehlsfenster als

Administrator:

Translations Ignore


Code Block
c:
cd \jtelStarface6v2SOAPWindowsService 
c:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe -install jtelStarface6v2SOAPWindowsService.exe



Trunk

...

Login as sysadmin to the jtel Portal.

Configure Trunks

Use System Settings ... Trunks to configure a trunk for each 8-Server machine.

...

und Trunk-Gruppen Konfiguration

Melden Sie sich als Systemadministrator am jtel Portal an.

Trunks Konfigurieren

Verwenden Sie Systemeinstellungen → Trunks, um eine Leitung für jeden 8-Server-Rechner zu konfigurieren.

Beachten Sie, dass die MachineID in der 8-Server-Konfiguration festgelegt wird (normalerweise der letzte Teil der IP-Adresse des Rechners).

Image Modified

Configure Trunk Groups

Create a new trunk group for each STARFACE PBX.

Legen Sie für jede STARFACE Telefonanlage eine neue Leitungsgruppe an.

Die folgenden Parameter sind erforderlich

...

.

Parameter

...

Wert
NameFor example STARFACE
Country Code

...

Wählen Sie die korrekte Ortsvorwahl
Outgoing Trunk SelectionTrunk

...

-Gruppe für interne ZieleAuf dieselbe Trunk-Gruppe einstellen
Trunk-Gruppe für externe ZieleAuf dieselbe Trunk-Gruppe einstellen
Frei verfügbar für ausgehende Anrufe

...

Only check this option, if this is a single customer installation.
Number Translator

...

Eingehend Anrufer NummerE.164 with + incoming

...

Eingehend Angerufene NummerSTARFACE - 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:

Image Modified

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.