We have a project with several sites in different cities and countries. We have implemented CME/CUE in all remote sites and CCM/Unity in the central site. We have done the internal inter-site calls and the calls from any offices to other city's local PSTN.
Now the customer has a new requeirment. They want to dail to other cities through their IPT network when not being in office. For example, in one city, they dail a local number which is configured in CME/CUE, get dial tone, dial the other city's local number. This can be done with Unity. But how can we implement it with CME/CUE? Is there a way to configure this or we need CUE script? Thanks.
if you can have this setup to work w/o authentication (not recommended), just configure a pots DP with "incoming called-number XXX" where XXX is a free DID that you have. You will get dialtone and can dial freely.
Else, it's more complicated. Do "show call application voice | begin app_clid_authen_collect.tcl". You will see the script to use and how configure it.
You will then configure "aaa authentication local" and "username XXX password YYY" with the number that you use for authentication. You also need to download the package that contains the voice prompts from CCO, I can point you to the exact location if you need to. Then configure again a pots DP on free DID, with "incoming called-number" and "service app_clid_authen_collect". This may take some time to setup correctly.
I configure a DP with a free DID, so the default application "session" should work when the DID is dialed. In debug, I can see the call hits the pots port, but it looks like the application doesn't work on the DP? How can I correct this?
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.