We have recently merged with another company. There is a need for a single support line to ring in multiple locations simutaneously, NY,NJ,CH London and Singapore. Each of these locations are using an different version of call manager with the exception of NY and Chicago which are on the same cluster.I have made NJ the main location for the support # and configured all others as remote destinations. The signaling issues are a major drawback. If a remote destination answers the line all other sites lose signaling except the main one(NJ).The remote site needs to dial *81 for NJ to be able to pick up the line on hold. Also if a remote destination answers the call and hangs up the call is placed on hold in JC which leads to false holds. Is there a better way to do this?
You can't truely share a DN across multiple clusters. The only "better way" that I can think of would be Contact Center Enterprise which can have a PG for each CUCM cluster. AFAIK it doesn't support CME though. Call pickup across clusters isn't going to happen either.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...