McDewey

Unicode Support Unicode Display Name Scenario Events Delivered to JTAPI Applications Scenario Call info should contain: getCurrentCalledPartyDisplayName = asciiNameB getCurrentCalledPartyUnicodeDisplayName = null getCurrentCallingPartyDisplayName = null getCurrentCallingPartyUnicodeDisplayName = japaneseNameA A line is configured on IP phone A with no ASCII name and a Unicode name in Japanese. IP phone B is configured with ASCII name and no Unicode name. A calls B. Only B is observed. DisplayName does not apply. Applications should consider “conference” as the called party. A, B and C are in conference. Calling party Unicode display name can change between A and B. Shared lines – A and B are shared lines with different locales. A calls C. C is unobserved. GetLocale and UniCodeCapabilities of Terminal Events delivered to JTAPI applications Scenario CiscoTerminalInServiceEv contains getLocale = JAPANESE getSupportedEncoding = UCS2UNICODE_ENCODING CiscoTerminal.getLocale = JAPANESE CiscoTerminal. getSupportedEncoding = UCS2UNICODE_ENCODING A line is configured on IP phone A with no ASCII name and Unicode name in Japanese. Application adds TerminalObserver on the Device. Application queries the following using CiscoTerminal. Unrestricted Unified CM Use Case One The application tries to register with an insecure CTI Port to the unrestricted Cisco Unified Communications Manager. Call information Result Action [Term A] CiscoTermOutOfService[A] CiscoAddrOutOfServiceEv[Term A] CiscoTermInServiceEv[A] CiscoAddrInServiceEv Application opens a provider with the unrestricted Cisco Unified Communications Manager and tries to register with an insecure phone CTI Port 'A'. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1541 Message Sequence Charts Unicode Support