Hi, I have a line with extension 1001. CFA, CFB and CFNA for this line are set. I need to accomplish following task: When extension 1002 dials 1001, all forwarding settings must be ignored and call must not leave ext. 1001, when any other extension calls 1001, forwarding settings must be considered. Currently this behaviour is achieved using Hunt List with single member (Line 1001) and special CSS for line 1002, but this way is too complex and almost not scalable. I need to find more elegant solution, for example, to mark somehow the call, so forwarding settings are not considered. Thanks in advance, Denis
... View more
Thank you for the answer, in my case I only need to distribute LSCs to the phones for 802.1x authentication. As far as I understand, it is possible to just update the CTL file with Cisco CTL Client utility.
... View more
Hello, currently we are running CUCM 9.1.2 Unrestricted, it does not support SRTP, secure signalling etc. I would like to use LSCs issued by my own CA to authenticate our phones against RADIUS with EAP-TLS. As far as I understand how CAPF works, I need to enable mixed security mode in my cluster and create CTL (or I only need to choose "Update CTL file" option in Cisco CTL Client to create new CTL and upload it to CUCM?). Is it possible to do that if my cluster is unrestricted? Do I still need to buy bunch of USB Tokens to sign the CTL? Thank you.
... View more
Hi Setting "MTP required" option in Trunk or GW configuration also leads to the waste of MTP resources and multiplexes compexity of troubleshooting, but this option is recommended one. Are there another causes for not using IPv6 only addressing mode? Will Cisco TAC support such installation?
... View more
Thank you for supposition, but for IPv4 compatibility Cisco is using MTPs. For two devices (such as phones) that support mismatched addressing modes, an IP addressing version incompatibility exists when a device with an IPv4 address wants to establish a RTP voice stream with a device with an IPv6 address. To resolve this IP addressing incompatibility for media, Unified CM dynamically inserts a media termination point (MTP) to convert the media stream from IPv4 to IPv6, and vice versa.
... View more
Hi, according to this document, Cisco recommends IPv4 and IPv6 as the setting for the phone IP addressing mode. IPv6 Only is not recommended for production environments. Does anybody know, why using this mode should be avoided?
... View more
Hi! I am trying to jump upgrade from current 6.1.5 to 9.1.1 as stated in document "Jump Upgrade Procedure for Cisco Unified Communications Manager Release 4.1(3)–7.1(5) to 9.1(2)" I already have virtualized my installation and it successfully works in VM environment created with cucm_9.1_vmv8_v1.6.ova template file. I have installed ciscocm.refresh_upgrade_v1.2.cop.sgn file, but my installation fails during HW verification phase. I receive following error: 09/06/2013 11:45:50 refresh_upgrade|(CAPTURE) /common/refresh_upgrade/./.discinfo|<LVL::Debug> 09/06/2013 11:45:50 refresh_upgrade|(CAPTURE) 9557546 blocks|<LVL::Debug> 09/06/2013 11:45:50 refresh_upgrade|This hardware is no longer supported. Validation error on HSSI mode: VMware Validation Failure: Unable to validate VMware based server disk settings. Please check SCSI disks are at least 72 GB in size and are located at 0:0 (and 0:1 in a two disk config) in machine settings..|<LVL::Error> 09/06/2013 11:45:50 refresh_upgrade|Final exit processing with result 1|<LVL::Info> Is it possible to workaround this problem? Thanks
... View more
Hi! Currently we have two SIP trunks to different providers. These tunks reside in two Route Groups, which, in turn, are included into Route List. The problem is, when we receive 503 error from first trunk, the call routing stops and CUCM does not try to send failed call to the second trunk. As far as I uderstand, this is default behaviour of CUCM. Is it possible to override this? CUCM 6.1.2 Regards, Denis
... View more