Sv translation | |||||
---|---|---|---|---|---|
| |||||
BackgroundThis 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. ScenarioThe 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.
First step: Add Trunk Group for jtel ACDAdd new trunk group
Go to next stepSpecify a trunk group name and a descriptionTrunk Group Type
SIP Settings
SIP Settings
Stun Server Settings
Encryption Settings
Definition of Routing
Location Profile
Second step: Add Trunk for jtel ACDAdd new trunkGo to next stepTrunk 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 tableThis 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 SystemTrunk Group
Trunk
For debugging purposesThe 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. |
Sv translation | |||||
---|---|---|---|---|---|
| |||||
BackgroundThis 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. ScenarioThe 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.
First step: Add Trunk Group for jtel ACDAdd new trunk group
Go to next stepSpecify a trunk group name and a descriptionTrunk Group Type
SIP Settings
SIP Settings
Stun Server Settings
Encryption Settings
Definition of Routing
Location Profile
Second step: Add Trunk for jtel ACDAdd new trunkGo to next stepTrunk 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 tableThis 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 SystemTrunk Group
Trunk
For debugging purposesThe 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. |