implementation jar base

jtel-system-presence-connectors-cisco

1.0

Use the 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.

In some CUCM, the numbers reported by the CUCM server via JTAPI are not fully qualified E.164.

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.

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