...

Our system supports the following presence connectors:

Innovaphone

Connecting the Innovaphone PBX to the jtel System is described here: http://wiki.innovaphone.com/index.php?title=Howto:Jtel_ACD_-_jtel_GmbH_-_3rd_Party_Product

Portal Configuration

The new presence connector is created as sysadmin in the jtel Web Portal.

Give the connector a good name, and select Innovaphone PBX SOAP API (Version) as the connector type.

The Configuration of the connector uses XML. The following example XML is used in the table below, to explain the settings.

...

<?xml version="1.0" encoding="UTF-8"?>
<config>
	<implementation>
		<jar>
			<base>tel-system-presence-connectors-innovaphone</base>
			<version>1.0</version>
		</jar>
		<class>de.jtel.system.presence.connectors.innovaphone.v11.InnovaphonePBX</class>
	</implementation>
	<parameters>
		<endpoint>https://<pbx-ip>/PBX0/user.soap</endpoint>
		<user></user>
		<password></password>
	</parameters>
	<behavior>
		<syncAcdUsers>0</syncAcdUsers>
		<syncPbxUsers>1</syncPbxUsers>
	</behavior>
</config>

Settings

...

implementation jar base

...

jtel-system-presence-connectors-innovaphone

Currently, Innovaphone v11 is supported. Configure the appropriate Innovaphone version.

...

1.0

...

Set <IP_ADDRESS_PBX> to the IP address of the PBX.

...

pbxUserName

...

pbxUserPassword

...

Causes all reported extensions to be created as an ACD user. Setting this to 1 is not recommended.

Note: even if this is set to 0, the ACD users presence status will still be set according to the current Tel1 field in the user record, and TelActive (the active telephone number).

...

Nfon

The NFON Connector supports the following functions:

• Monitoring of the configured extensions in the respective PBX 
  
  • Not registered
  • Idle
  • Occupied
  • Ringing

...

Portal Configuration

The new presence connector is created as sysadmin in the jtel Web Portal.

Give the connector a good name, and select Nfon ExtensionsEvents API (Version) as the connector type.

The connector settings are specified as XML.

Example:

...

<?xml version="1.0" encoding="UTF-8"?>
<config>
	<implementation>
		<jar>
			<base>jtel-system-presence-connectors-nfon</base>
			<version>1.0</version>
		</jar>
		<class>de.jtel.system.presence.connectors.nfon.v1.NFONExtensionsEvents</class>
	</implementation>
	<parameters>
		<endpoint>https://nmonitoring-api.nfon.com/queues/extensions/events</endpoint>
		<endpoint_names>https://nmonitoring-api.nfon.com/queues/extensions/</endpoint_names>
		<user>KXXXX</user>
		<password>AAAAABBBBBCCCCCDDDDDEEEEEFFFFFGGGGG</password>
	</parameters>
	<behavior>
		<syncAcdUsers>0</syncAcdUsers>
		<syncPbxUsers>1</syncPbxUsers>
	</behavior>
</config>

Settings

Only the settings in the areas parameters and behaviour may be adjusted:

...

The REST endpoint for the API for monitoring events.

...

https://nmonitoring-api.nfon.com/queues/extensions/events

Note: no final /

...

https://nmonitoring-api.nfon.com/queues/extensions/

Note: Final /

...

Whether the users from the PBX are automatically created as users in the ACD

Note: this feature is currently not supported.

...

Microsoft Teams

MS Teams Connector allow the retrieval of presence from MS Teams, to provide a display of presence in the jtel system in various views such as:

• Agent Home
• Supervisor
• MiniClient
• Main Page

Portal Configuration

The new presence connector is created as sysadmin in the jtel Web Portal.

Give the connector a good name, and select TEAMS Presence Rest API (Version) as the connector type.

The connector settings are specified as XML.

Example:

...

<?xml version="1.0" encoding="UTF-8"?>
<config>
	<implementation>
		<jar>
			<base>jtel-system-presence-connectors-teams</base>
			<version>1.0</version>
		</jar>
		<class>de.jtel.system.presence.connectors.teams.v1.TEAMSPresenceRestApi</class>
	</implementation>
	<parameters>
		<tenant_id></tenant_id>
		<client_id></client_id>
		<client_secret></client_secret>
        <scope></scope>
        <user></user>
        <password></password>
        <execution_period></execution_period>
	</parameters>
	<behavior>
		<syncAcdUsers>0</syncAcdUsers>
		<syncPbxUsers>1</syncPbxUsers>
	</behavior>
</config>

Settings

Only the settings in the areas parameters and behaviour may be adjusted:

...

implementation jar base

...

jtel-system-presence-connectors-teams

Currently, teams v1.0 is supported. Configure the appropriate Teams version.

...

1.0

...

The Directory (tenant) ID from Azure Active Directory - registered App

...

client_id

...

teams_user

...

Causes all reported extensions to be created as an ACD user. Setting this to 1 is not recommended.

Note: even if this is set to 0, the ACD users presence status will still be set according to the current Tel1 field in the user record, and TelActive (the active telephone number).

...