Sv translation | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||
Pre-Requisites
JTAPI InstallationInstallationInstall the Cisco JTAPI Libraries on an appropriate server. This example assumes that the PRES role has been installed on a windows server. Installing simply requires clicking through the defaults, it is not necessary to change the paths. ConfigurationFrom the directory in which Cisco JTAPI is installed (on a windows server, usually C:\Program Files\Cisco\JTAPI64Tools), run jtprefs.bat. The following screens show the settings which can be made: DebuggingIf debugging and logging is desired, settings can be made on this page to specify the debug level: LoggingThese are the recommended logging settings: Cisco Unified CMAdd all available call manager servers on the next page: Further SettingsThe settings on the remaining pages can be left "as is", and do not need to be changed. Copy JTAPI.INIClick on OK, to create a JTAPI.INI file. This file will be stored in: C:\Program Files\Cisco\JTAPI64Tools Copy this file to the bin directory of the presence aggregator, for example: C:\presence-aggregator\bin Portal ConfigurationSystem Settings: Presence ConnectorsCisco Connector Portal Configuration Starting / Stopping ConnectorsConnectors can be started or stopped in the web interface, by clicking on the red / green dot next to the name: Trunk GroupsThe following settings are recommended for the creation / use of Trunks and Trunk Groups in the jtel System:
User ConfigurationUsers can be configured either:
The second method may be the best method to use on multi-site CUCM installations, if the numbering plan in the CUCM was never E.164 and has become "untidy" over time. Example |
...