Are you using an external conference bridge or the BIB on the phone? Also, what is the model phone you are using and what firmware version is it runing? Also, what is the CUCM version? ... View more

Hi Stephanie, I may need you to ask more specific questions but I will give it a shot. Unity Connection leverages EWS to constantly synchronize messages and message state between Unity Connection and Exchange. The throttling parameters basically make sure that a specific user does not overload an Exchange server. However, the default values don't allow Unity Connection to synchronize in a timely manner, perhaps you have encounters slow sychronization before? It would more than likely be cased by these throttling thresholds being hit and the synchronization terminated. In order for Unity Connection sychronize the messages, subscribes to events that it "cares" about in regards to the messages. The processing on these subscriptions and other requests counts against the thresholds that you see above. There can be many simoultaneous connections between a CUC and an Exchange server which is determined by the number of users and the latency between CUC and the Exchange server. A signle user request can use one or more of these simultaneously and this why in Exchange 2010 SP2 RU4, moving the throttling calculations to the ddestination user caused an issue, because before, the throttling was calculated against the source user, which would have been the UM service account (so disabling throttling for this one user allowed us to sychronize as needed without opening the Exchange server up to potential resource issues from the users). Basically, in Exchange 2010 SP2 RU4, the voice message activity and size of the Exchange mailbox dictate how the the throttle parameters need to be set to ensure that messages and their status synchronize in a timely manner. If you have more specific queries, just let me know and I will try and get you an answer. ... View more

Stephanie, Here is the write-up I will be providing to other customers/partners as they inquire until we can get the official documentation updated. Let me know if you have any lingering questions. Exchange 2010 SP2 Rollup Update 4 and later now calculates usage based on the destination account rather than the source account which is the UM Service Account. Because of the change in where usage is calculated, removing the throttling limits from the UM Service Account no longer affect Unity Connection’s usage of EWS in Single Inbox integrations. Exchange 2013 and Office 365 Wave 15 use different metrics for throttling and are more relaxed when compared to Exchange 2010 SP2 RU4. As such, the throttling values presented here are not relevant to Exchange 2013 and Office 365 Wave 15 deployments. However, the fix for CSCtz20281 (read further down) improves Unity Connection’s ability to synchronize with larger mailboxes and applies to all versions of Exchange including 2010, 2013, and Office 365 Wave 15. The following represent the throttling parameters that can affect Unity Connection’s Single Inbox Integration: EWSPercentTimeInAD - This parameter specifies the maximum amount of time that can be spent by a Client Access server when accessing Active Directory resources on behalf of a client account, per minute. EWSPercentTimeInCAS - This parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing the client access server code (PercentTimeInCAS). EWSPercentTimeInMailboxRPC - This parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing mailbox remote procedure call (RPC) requests (PercentTimeInMailboxRPC) EWSFindCountLimit - Defines the maximum number of items from a FindItem or FindFolder operation that can exist in memory on the Client Access server at one time for one user. Testing has been performed to help identify proper values for the 4 EWS Throttling parameters that need to be applied to all Single Inbox users within Exchange: EWSPercentTimeInAD - 100 EWSPercentTimeInCAS - 300 EWSPercentTimeInMailboxRPC - 200 EWSFindCountLimit – 10,000 ***Please be aware that these are guidelines for mailboxes with up to 10,000 items in them. Should a mailbox contain more than 10,000 items, then these settings may be insufficient to avoid throttling. The use of Exchange performance counters can be used to help administrators adjust these numbers as required. During this testing, the development team identified 2 enhancements that could be made to help avoid hitting throttling limits: CSCtz20281 - Allows Unity Connection to page (group) multiple request together to receive a single response. It also eliminates the need to modify the EWSFindCountLimit parameter which defaults to 1,000. Patched in 10.0(1), 9.1(2)ES02, 8.6(2)ES, 8.5(1)ES/SU Exact versions for 8.5(1) and 8.6(2) are not available yet and will be provided ASAP CSCui39504 - Filters out calendar events from EWS request to reduce responses to Unity Connection. Fix is not yet available and will be provided ASAP With the application of these EWS Throttle parameters and versions of CUC that have fixes for the previously mentioned defects, Unity Connection should operate correctly with Exchange 2010 SP2 RU4 and later without completely disabling throttling on user accounts. ... View more

Hi Stephanie, We are in the process of documenting some more specific throttling values rather than out-right turning them off. We also have some improvements (code fixes) for CUC which will help eliminate the need to change/remove some throttling limits. We just received a draft of this last week and are working on finalizing and publishing. I have another customer that is also looking for all of the specifics so give me a couple days to round up all the data and versions and I can post back here with what we will be recommending going forward before it offically gets published. Chris ... View more

Hi Sergey, Thank you for your question. The upgrade process from 8.6.1 to 8.6.2 is described in detail in the HCS 8.6.2 documentation. Here is a basical outline of the order of operations for such an upgrade: 1. Cisco HCS Management Components—Service Fulfillment and Service Assurance 2. Cisco HCS Data Center and Service Provider Network Infrastructure Components 3. Cisco HCS Aggregation Layer Components and Cisco Unified Communications Domain Manager Models. After you upgrade Cisco HCS Management, DC Infrastructure, and Aggregation Layer components to the compatible Cisco HCS versions, you can continue to manage individual Cisco HCS customers that are running the previous Cisco HCS Solution versions of Cisco Unified Communications applications since the upgraded components are backward compatible. 4. Customer-Specific Unified Communications Applications and Services. This can be accomplished using the Platform Manager component of HCM-F which allows administratotrs to schedule and automate the upgrades of the all the UC applications. I hope this helps Sergey! Chris ... View more

Hi Mohamad, I think you may have posted in the wrong section. My expertise is in the Hosted Collaboration Solution and other Unified Communication topics. Perhaps you intended to post this elsewhere? Chris Ward ... View more

Hi Lisa, Thanks for your question. Yes, you would be allowed to integrate your conferencing solution into your HCS offering. In cases like this where the HCS team has not validated the configuration or tested it in our labs, this type of integration would need to be tested and supported by you, the HCS provider/partner. The HCS SP/Partner would need to own this itegration but it would be allowed. So while Cisco can't validate or support the integration, the partner is allowed to add this to their offering with the previously mentioned caveats. Hope that helps. Thanks Lisa! ... View more

Hi Tenaro, Thank you for your question. At current, we do not setup CUCM in a multi-tenant configuration. Each HCS end-customer gets their own unique CUCM cluster, the same goes for Unity Connection and Unified Presence. There are a few pieces of software that are unique to HCS 1) HCM - F - This component is used to automate the upgrades of the UC applications, produce bundle-based billing reports from the configuration domain, and also automatically provision/configure the Service Assurance architecture so as you deploy HCS to end customers, the monitoring of those configurations is automatically done for you. 2) Prime Central for HCS Assurance - This component is responsible for provides lots of functionality in regards to monitoring the HCS solution. It aggregates data from CUOM, CUSM, DCNM, and vCenter and can display all the events/errors/alarms that those components are reporting. It also has the ability to normalize these errors and forward them to an exisitng alarm management or ticketing system via SNMP traps. It also includes a reatures like fault correlation (root cause analysis) and service impact analysis which allows you to see what services are affected based on the error information that is being reported. 3) This last item is not really a piece of software, but more an advantage over using UC on UCS as opposed to HCS. Within HCS we allow the over subscription of your UCS resources for some of the smaller OVAs where in UC on UCS you would be required to map a vCPU to an entire core. This allows for much greater denisty. Also, the HCS licensing scheme allows for the SP to pool licenses and transfer between the customers as needed where in UC on UCS, these licenses are bound to customers, once purchased. To answer your last question, we sell HCS to service providers and partners. Partners may need to have customers bring their own PSTN connectivity or partner with an SP to provide PSTN access, but either way, partners are just as capable of providing this service. Hope that helps. Thanks again Tenaro! ... View more

Hi J, The process of creating a new customer is not yet fully automated, but we are working on vCenter integration that may eventually automate this process. With HCS, you would build a "golden template" of the UC apps that your customers would be consuming. The golden template is essentially an image of the UC App (UCM Pub, UCM Sub, UCxN, and CUP) that has parameters and configurations that you think every customer will be using. There are some caveats to what you configure since the provisioning tool, Cisco Unified Communications Domain Manager (UCDM), will be provisioning the system for you after you create the customer instances. Once you have your golden templates, you are ready to start rolling out customers. You would clone the golden templates to create your new customer instance. Then you run what are called the "new identity" scripts on the cloned VMs. This new Identity script is built into the UC application (From 8.0 and later). It essentially involves you using the Answer File Generator on cisco.com to create an answer file for the application of interest and then you mount this answer file via a floppy image to your newly cloned VM. Once the floppy is mounted, you can go ahead and run the new identity script "utils import config" from the CLI of the UC app. It will rename, re-IP, change DNS servers, and lots of other platform information about the system that you can configure. Finally, it will reboot the system. Some of this process can also be automated using VMware's vMA toolset using scripts that the HCS team can provide. Once the new identity script has been run, you have a new install for your new customer. Then you would input the new address information into UCDM and begin the bulk provisioning of the system. The UCDM would be bulk creating users, phones, VM accounts, partitions, CSS's, and just about everything else for the UC environment. Once again, stay tuned for some future automation enhancements in this area, but at current (HCS 8.0.2 and soon to be 8.6.1) this is the method for provisioning a new customer from scratch in VMware. ... View more

Hi, I don't fully understand the problem, but will help where I can and hopefully ask the right questions to help fully grasp the issue at hand. The part I can answer is that to make sure end users can't dial the ELIN patterns is to make sure the inbound CSS on the GW is the only CSS that can reach those ELIN translation patterns. Now for the questions: 1) How many digits is CUCM receiving from the Telco? 4 or 10? 2) Can you provide some examples of the problem you feel you are going to face? (feel free to use some X's so you don't advertise your DIDs and DNs) ... View more

We sometimes see strange delay and ringing issues like this when the call to the cell phone from CUCM (SNR call) is sent over an unsupported link: "Mobile Connect features do not get supported for T1 CAS, FXO, FXS and BRI." http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmfeat/fsmobmgr.html#wp1245955 Please make sure you are using a PRI, H323 GW, or SIP trunk from CUCM to the cell phone. Using a different type of trunk will cause unexpected behavior. ... View more

Let me answer what I can: 1) 7.1.2bSU1 probably doesn't have the fix you are looking for from a 6.1.4ES. So you should ask TAC to provide the full install of the 7.1.2ES that you need. So you can upgrade directly from 6.1.2 to 7.1.2ES. That way you can still back out easily should something with 7.1.2ES not be the way you want. What is the Bug ID? 2) The Jump from 6.X to 7.X is much less dramatic in SCCP versions than the jump from 4.X to 6.X so there is less of a chance of issue with this. Out of curiosity though, what IOS are you using on these devices? 3) AC should continue to function in 7.X (if you are upgrading), but will be totally removed in 8.0 so get ready to find a new solution. That's what I can answer. Hope it helps some. Thanks! ... View more

RTMT has the functionality to automatically and continuously collect logs. http://www.cisco.com/en/US/docs/voice_ip_comm/cups/6_0_1/Serviceability/administration/guide/sartmttc.html#wp1090215 HTH -Chris ... View more

The reason the phone is looking for the non-NAT'd CUCM IP address is because the firewall is not inspecting the TFTP traffic that is used to send the config to the phone from CUCM. The XML file contains these IP addresses. You can either see if there is a TFTP inspect you can run on the firewall to rewrite this, or use DNS names instead which a DNS server outside you NAT could use to resolve to the NAT'd IP. Also, I think the officially supported method to accomplish what you are trying here is the PhoneProxy feature set on the ASA. HTH ... View more