I have a CUCM cluster running 8.6.2a Here in Ontario Canada,. It connects to a UCCE in US . When we have a wan failure the customer is asking that we create a DR model where the survivablity.TCL willl step in and send calls to a callhandler in Unity Connection the to a hunt group. The issue is how many diffeerent numbers will the survivablity tcl script support,. I have over a 100 inbound numbers and well over 25 different UCCE starting points for inbound calls ie: one group is sales, then support etc etc.
what are my limitations of the survivability script,. From reading looks like I can do time of day and a few other options however I cannot tell how many numbers it will handle or does survivablity tcl only works with a single number
There are no limitations on number of numbers, you simply apply it to dial-peers that point to UCCE, and it gets invoked when communication to CVP is lost. So, for every dial-peer that sends the call to CVP/CUSP/CUPS apply the survivability service to it.
Chris, I got you confused as Iam ,., What I need is all my inbound numbers like 1-888-555-1212 and the other 100+ numbers that got to different scripts, during a wan failure I need calls to go to callhandlers and huntgroups which right now is over 30, well I need the survivabilty.tcl to work like CVP and route calls to specific handlers etc
Survivability in its own I dont believe can do this can be done with survivabilty alone.
I have done it with BACD but not with this many hunt groups.
Chris thanks for quick reply.. I had read the CVP SRND guide and the Admin guide and I knew I was screwed.
I got messed up as some of the docs are ify at best..The bigger issue of this deployment is we have a CUCM cluster here in Ontario and all the UCCE is in Richmond Virgina (I think) My calls come into a local gateway and I send the UCCE to a US CUSP.
If I loose the wan link I am in trouble, For some reason we thouht we could use the survivability to send calls to 30+ callhandlers and I knew it wasn't that simple.,
The last time I hit this type of scenario I had to use BACD / CME and it was messy.,
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.