Versions Compared

Old Version 7

changes.mady.by.user jtel Support

Saved on

compared with

New Version 8

changes.mady.by.user jtel Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
Cisco Connector Portal Configuration
Cisco Connector Portal Configuration

Portal Configuration

To use the connector, and The new presence connector is created as sysadmin in the jtel Web Portal.

...

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

To use the connector, and The new presence connector is created as sysadmin in the jtel Web Portal.

...

Anchor
Nfon Connector Portal Configuration
Nfon Connector Portal Configuration

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.

...

Translations Ignore


Code Block
titleNFON ExtensionsEvents API Presence Connector XML Settings
<?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>


...

  • 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:

Translations Ignore


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

SettingValueComments

implementation jar base

jtel-system-presence-connectors-teams

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


implementation jar version
1.0
This version pertains to the jtel version of the connector implementation. Currently version 1.0 is required (for all Teams versions).
parameters tenant_idtenant_id


parameters client_id
client_id

parameters client_secret client_secret
parameters scope https://graph.microsoft.com/.default
parameters user 
teams_user
Set the email for the Teams Administrator.
parameters passwordteams_passwordSet the password for the Teams Administrator.
parameters execution_period5This define the periode of updating the status of MS Teams users.
behaviour syncAcdUsers0

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).

behavious syncPbxUsers1Causes all reported extensions to be created as PBX Users. Setting this to 1 is recommended.