Good day all,         I'm having quite the day today. Can anybody tell me if there is a way to access client created scripts and prompts from the CLI of a broken UCCX. The GUI is not an option, most services are stuck in "starting", the restore fails and cannot be used (long story). TAC basically told us that a miracle could not be provided, understandably, and we are reconfiguring from scratch.         Fetching the scripts and the prompts via CLI would be great. While waiting to re queue the TAC to ask them if it`s possible via the root account, I figured it could not hurt to ask here.   uccx version: 10.6.1.11002-15     Thanks, ... View more

I would appreciate to know in which release CSCuj44903 is fixed for Call Center Express. Accessing the bug ID is restricted for me. I was unable to find this bug in the open or resolved caveat for version 10.6 (1), we are running on this problem on version 10.5.1.11001-49 and would like a confirmation that 10.6(1) would fix it or if only a special ES would do the job (TAC).   link to information I found mentioning this reference: http://docwiki.cisco.com/wiki/Desktop:_Agents_experience_problems_signing_in_or_desktop_is_slow_to_respond   Thanks ... View more

Good afternoon,   I would appreciate if someone could help me understand how voice-class sip options-keepalive on a dial-peer behaves on a standby cube of a HA Cube setup. I was unable to find documentation that explained the behavior of both used together.   I have two HA cubes setup (four cubes in all), in two different sites, and they both behave differently in regards to the sip options-keepalive messages.   On SITE A: The standby CUBE puts all his dial-peer in busy out mode. Its SIP OPTION messages are sent to the SIP trunk provider using the HSRP ip address instead of local interface ip address (both on LAN toward cucm and WAN toward ISP) consequently the reply 200 ok comes back to the active CUBE instead of the standby. Or should I say, I see the OPTION leaving the WAN side interface with the HSRP address, and nothing comes back on the WAN side standby cube. (Network Trace)   On SITE B: The standby CUBE does not send any SIP OPTION messages, until he becomes the active cube . The keep alive field of the "show dial-peer voice summary" command shows no status while being the HSRP standby.   Wich way should be the designed way to behave ?If SIte A is correct, can I force the keepalives to be sent using the interface ip address instead of the HSRP address?   They are all running the same IOS. Both ISP providers are the same for both HA cubes. All connected to the same CUCM cluster on the LAN side.   The behavior of SITE B makes more sense according to me. In case of a cube fallback on SITE A, I would anticipate some delay before the option-keepalive changes the status of the dial-peer from busyout to active after he becomes primary cube and gets answers to his SIP OPTION messages, and that just smells bad.   Thanks, ... View more

Hi everyone, Is it possible to enable the wireless headset Hookswitch control for a 6945 on CUCM version 9.0.x (9.0.1.10000-37)? This document makes me believe it's possible: http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/6921_6941_6945_6961/9_0/english/admin_guide/P690_BK_4AB91FB_00_admin-6921-6941-6945-6961_chapter_011.html#IP95_TP_WFE19F9F_00 " Cisco Unified IP Phone 6921, 6941, 6945, and 6961 Administration Guide for Cisco Unified Communications Manager 9.0 (SCCP and SIP) Step 1   From the Cisco Unified   Communications Manager Administration, choose Device > Phone. Step 2   Scroll to the Wireless Headset   Hookswitch Control section. Step 3   To enable Electronic Hookswitch,   choose Enabled. Step 4   To disable Electronic Hookswitch,   choose Disabled." In practice, the option is not present on latest 9.0 , but does appear with latest 9.1 version after the latest device pack is installed. So back to my question, is it possible to have this option on 9.0 ? Or is the minor upgrade to latest 9.1 a must do ? Thanks ... View more

Hi , I am having some UTF-8 problems with French locale for  SPA-509/508/525 phones running 7.4.9C on UCXXX package 8.6. The directory sub menu and CME service sub menu on the phone display contains "@~C" instead of "é" everywhere. In all other menus in the phone the letters are displayed correctly. Problem is present only in the cme services sub menu for SPA525 Problem is not present on 79XX phones, I tried with fr_FR language pack 8.1.2.1, with fr_ca language pack 8.1.2.1. I tried removing "user-locale  U4 FR LOAD…. " commands put by CCA and forcing "user-locale FR LOAD …." directly in cli. I tried forcing the spa50x_30x_v746 dictionary directly in cli as well. Nothing fixes this.          A nybody has any other idea? (other then opening, yet another,  small businnes TAC of course) see attached pictures. ... View more

Hi all,      I have been provisioning a SPA525G2 as a remote phone using SSL-VPN with CCA 3.2 on 8.2 UC540 package and everything works perfectly fine as long as I have a static IP address setup on the WAN port of the UC towards my ISP . In the release notes of CCA 3.2, it cleary says that we can now setup a SSL-VPN full tunnel when the wan port is DHCP. Even includes  nice dynamic DNS options.Obvisously since I am posting, you guessed that as soon as I try to reconfigure my SPA525G2 as a remote phone with a DHCP configuration on the internet port of the UC with a Dynamic DNS setup (or without), it fails to connect to UC from remote site.      Before I open a STAC and gather more debugs, I figured I could ask the community see if anybody succeeded in this. Is the new CCA feature only for webvpn and not for remote phone configuration? thanks SPA525G2 is latest 7.4.9c. anyconnect ssl package is latest. IOS is latest of UC540.   notes from CCA 3.2 SSL VPN Configuration Provide an option to enter SSL VPN Port              Provides the option to configure SSL VPN port during SSL creation on UC500. Ability to accept the DHCP assigned IP address on the WAN for SSL VPN               Allows creation of SSL VPN using DHCP Wan IP and also warns the user of any changes to the WAN IP that will cause SSL VPN to not work. ... View more