扩展移动交叉集群（EMCC）

Cisco Unified Communications Manger（CUCM）8.0引入了一个新功能，即许多分布式多群呼叫处理部署已经等待......。跨群集的扩展移动性。除非有缩写，否则有什么技术特征是值得的???新功能称为扩展移动交叉集群（EMCC）。CUCM 8.0还添加了对安全扩展移动登录的支持。扩展移动性是能够登录未使用您的电话号码，服务类和我们称呼功能的其他书呆子旋钮编程的电话。想象一下，贵公司是思科系统，您在曼哈顿市中心（纽约市）的一家宾馆广场有办公室。由于房地产在纽约市和思科是一个虚拟化的公司，大多数工程师和帐户经理（销售）没有NYC的任何常规办公空间。思科员工可以借用当天的隔间空间，并使用扩展移动性登录思科电话。扩展移动性允许某人在临时工作空间中允许他们的电话号码跟随它们到临时电话。 The phone configuration is also updated with various other configuration parameters based on the configuration of the device profile(s) that are associated to the end user. Extension Mobility was originally a feature of IPCC Express (re-branded to Unified Contact Center Express or UCCX) which required the purchase, maintenance, and configuration of the Cisco Customer Response Server (CRS) platform. Cisco integrated Extension Mobility functionality into CUCM 3.1, but extension mobility requires a standalone or centralized call processing model if using a CUCM version before 8.0. CUCM 7.0 introduced a new option in the publishing of Phone Services that allows extension mobility to be published as a global subscription. The global subscription nerd knob (check box) on the phone services configuration page of CUCM automatically subscribes every phone and device profile to the extension mobility service. Have you ever subscribed a Cisco IP Phone to the extension mobility service, but forgotten to subscribe the user’s device profile to the service? Been there… done that! If the Extension Mobility service parameter doesn’t allow multiple logins (default), the user will not be able to logout of the phone or login to any other phones. Configuring extension mobility cross cluster (EMCC) is nothing you should take lightly. EMCC requires a lot of configuration parameters including the exporting and importing of each neighbor cluster’s X.509v3 digital certificates. EMCC is supported over SIP trunks only. Presence is another feature that’s only supported over SIP trunks. If you want to be able to perform scalable Call Admission Control (CAC) in a distributed multi-cluster call processing model, you will need to point an H.225 or Gatekeeper controlled trunk to an H.323 Gatekeeper for CAC… but if you want to support presence and EMCC between clusters and maintain CAC… Houston! We have a problem here! Here are two potential solutions to the problem… but they’re both not scalable: 1)Assign the SIP trunks to a location and perform CAC in CUCM 2)Use Resource Reservation Protocol (RSVP) to provide CAC between clusters Option #1 above will require a lot of configuration in large environments that have dozens of CUCM clusters…. Option #2 above will seriously tax the CPU of your router because RSVP signaling requires a lot of processing. Service providers will never run RSVP with you either, but they will do pass-through RSVP where they can provide per-hop behavior (PHB) quality of service (QoS) based on the differentiated services code point (DSCP) markings of the IP packets. Here’s a link to the information you will need to be able to configure Extension Mobility Cross Cluster (EMCC): http://www.ciscosystems.ch/en/US/docs/voice_ip_comm/cucm/admin/8_0_2/ccmfeat/fsemcc.pdf