Background

This guide describes one way of connecting the jtel ACD to the Swyx PBX system and routing calls to the jtel System.

The following principle applies to connecting the jtel System to the Swyx PBX:

The jtel System hence operates as a back to back user agent, the Swyx PBX is not aware that Leg 2 calls are associated with Leg 1.

Scenario

The following configuration scenario was performed after the following steps had been performed on the Swyx System:

After these steps, a basic PBX is configured with some users, internal calls working, and functionality to call inbound or outbound to / from the outside world.

This is not intended to be an expert guide on configuring the Swyx PBX system or a recommendation that "this is the one and only way" of doing things.

You should know your Swyx PBX well, and any configuration therein which is relevant.

You should also be familiar with the procedures involved here, particularly in the Swyx PBX.

You should also be capable of identifying steps which may be critical to your PBX installation, it's configuration or any routing involved, before you proceed.

The scenario below may need modifying to suit your needs!

First step: Add Trunk Group for jtel ACD

Add new trunk group

Go to next step

Specify a trunk group name and a description

Trunk Group Type

SIP Settings

SIP Settings

Stun Server Settings

Encryption Settings

Definition of Routing

Location Profile


Second step: Add Trunk for jtel ACD

Add new trunk

Go to next step

Trunk Name

Trunk Group Selection

SIP Trunk Provider / User Data

Subscriber Numbers

SIP URI

Codecs

Number of Channels


Computer Name

Trunk - Trunk Group Settings

Trunk - Rights

Third step: Modify the routing table

This is where you define which calls should be routed to the jtel ACD. In this case, we are specifying calls from an outside number, +49198112233* (* is a wildcard).

Add a new routing record

Trunk Group Selection

Routing

Fourth Step: Create a trunk group in the jtel System

Trunk Group

Trunk

For debugging purposes

The usual call logging applies from the jtel side. It may be necessary to run a wireshark trace to see if calls are being routed to the jtel system at all.

You can access the swyx trace logs via: C:\ProgramData\Swyx\Traces on the Swyx machine which may give insight as to why things are not working.