Versions Compared

Old Version 6

changes.mady.by.user jtel Support

Saved on

compared with

New Version 7

changes.mady.by.user jtel Support

Saved on

Key

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

...

If the numbers reported by the CUCM server via JTAPI are not fully qualified E.164, they can be translated.

This assumes the portal has been configured fully to E.164, and may not be necessary in all installations.

The address translator mechanism provides a way to normalise the numbers before they are used to update presence information in the jtel System.

A translator consists of two parts:

Match

A regular expression, which matches the number as reported by the CUCM.

For example, the following regex:

^1(..)$

Matches all 3 digit telephone numbers beginning with a 1. A grouping is used to isolate the last two digits of the number into group 1, referred to in the replacement as $1

Replace

The replacement to be made.

For example:

498946149501$1

This would cause the two digit matched group from the regex to be appended to the string 498946149501.

Example

Input: 123

Output: 49894614950123

Recommendations

Any number of translators can be used. They are all applied in sequence, so a little thought might be required to get the desired effect. It is recommended always to work with groupings and a specific length. Also, to prevent erroneous matches, the ^ (begin of string) and $ (end of string) regex operators should be used.

SettingValueComments

implementation jar base

jtel-system-presence-connectors-innovaphone

Currently, Cisco v10 or v12 Innovaphone v11 is supported. Configure the appropriate Cisco Innovaphone 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 Innovaphone versions).
parameters providerNameendpointIP_ADDRESSUse

Set <IP_ADDRESS_PBX> to the IP

Address or DNS Name

address of the

CUCM Server

PBX.

parameters userJTAPI
pbxUserName
Set <PBX_SOAP_USERUse the name of the configured user with JTAPI access in the CUCM Server_NAME_PBX> to the SOAP user name configured in the PBX.
parameters password
pbxUserPassword
Set <PBX_SOAPJTAPI_USER_PASSWORDUse PASSWORD> to the SOAP password of the configured user with JTAPI access in the CUCM Server.

Note: if special characters (not allowed in XML) are included in the password, these must be escaped inside a CDATA section as shown in the example configuration above.

addressTranslatorsXML Translator Definitionin the PBX.
addressExcludersXML Excluder Definition

Excluders are used to match number patterns which shall not be monitored.

For example, if trunks are passed to the jtel system, it does not make sense to monitor these entities.

An excluder consists of one part:

Match

A regular expression, which matches the number as reported by the CUCM.

For example, the following regex:

^9(..)$

Matches all 3 digit telephone numbers beginning with a 9, and will not setup monitor points to these numbers.

behaviour syncAcdUsers		0

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.

...

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

Anchor
Nfon Connector Portal Configuration
Nfon Connector Portal Configuration

Portal Configuration

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

SettingMeaningStandard Value
endpoint

The REST endpoint for the API for monitoring events.

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

Note: no final /

endpoint_namesThe REST endpoint for the API to retrieve the extension names.
https://nmonitoring-api.nfon.com/queues/extensions/

Note: Final /

userThe username for the API.Provided by NFON.
passwordPassword for the API.Provided by NFON.
syncAcdUsers

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

Note: this feature is currently not supported.

0
syncPbxUsersWhether the users from the PBX are automatically created as PBX users in the ACD1


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:

...