was wondering if anyone knows a solution for this, what i'm thinking about is; we have our remote sites set up for their own Device Pool and Region as a general rule. What i'd like to be able to do, is in the event of a problem at that site, divert all incoming calls meant for extensions based there, to another site, or annoucement etc. As the main common factor for extensions on a per site basis is Device Pool or region, can anyone think of a way of globally diverting based on this?
I don't know of any way to route calls based on device pool or region. If you have distinct DN ranges at these sites, you could use a translation pattern. For example, if site A has DNs 5001-5099, you could create a translation pattern of 50XX and translate any call to that range to another DN. This could also be done with a translation rule on an H.323 gateway.
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.