McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 488

↗ View in doc context
page
488
source
cucm/v15/feature-config-guide/feature-config-guide.md
chunk_id
cucm::v15::feature-config-guide::feature-config-guide::436

EMCC Login Result loginType in Visiting Cluster EM URL* Home Cluster Version Visiting Cluster Version Success UID, SP, or DN *** 12.0 11.5 and below • * Following are the loginType parameter options: • UID—Users login using User ID and PIN • SP—Users login using Self-Service User ID and PIN • DN—Users login using Primary Extension and PIN • ** Fail with error code - 1 — (When EMService could not parse the XML request from EMApp/EMService) • *** loginType will be ignored and the User ID / PIN login prompt gets populated on the phone. Note Extension Mobility Cross Cluster and Security Mode for Different Cluster Versions Phone configuration files can be encrypted only if both the home cluster and visiting cluster versions are 9.x or later, and when the TFTP encryption configuration flag is enabled. Note During EMCC login, if both the visiting cluster and home cluster versions are in 9.x or later, the phone will behave in various modes as shown in the following table. Table 40: Supported Security Modes When Both Visiting Cluster and Home Cluster Are In 9.x or later Versions EMCC Status Visiting Phone Mode Visiting Cluster Mode Visiting Cluster Version Home Cluster Mode Home Cluster Version Secure EMCC Secure Mixed 9.x or later Mixed 9.x or later Non-secure EMCC Non-secure Mixed 9.x or later Mixed 9.x or later Non-secure EMCC Non-secure Non-secure 9.x or later Mixed 9.x or later Login fails Secure Mixed 9.x or later Non-secure 9.x or later Non-secure EMCC Non-secure Non-secure 9.x or later Non-secure 9.x or later Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 446 Receiving Calls Extension Mobility Cross Cluster and Security Mode for Different Cluster Versions

Image 1 from page 488