I have an IPMA setup that has had a lot of problems. Currently, there are problems again with disabling/enabling the DivAll function to divert all calls to an assistant.
CallManager version is 4.1.3sr3a, IPMA is configured using proxy line and is running on 2 servers.
Sometimes, all functions well. However, last week there have been a lot of problems (error messages once and a while like "Call Filtering down" and afterwards Call Filtering works fine again, managers disappearing from IPMA Assistant Consoles and reappearing afterwards,...). Today, I restarted IPMA, but without succes. Managers appear correctly now, but Call Filtering is down and stays down now...
I restarted all Tomcat-services, but still no change...
Is there anyone who has experienced the same problem and what was the solution/cause?
Do you want to disable the Imm.Divert softkey on the IPMA phones.?If so,you need to edit the softkey template on the device settings option.Call control must be up always,if not just restart your services and ensure that you have given the CCM IP address in IPMA service under enterprise service option.
Softkey is obviously present, with disable I mean we cannot deactivate it. If we push the softkey, it doesn't do anything. If we do the same thing on the IPMA Assistant Console, we get "Failed to set DivAll".
Already opened a TAC case and hoping they provide a solution soon.
Two design considerations we should have in place are IPMA/EM should be running on the same node for IPMA Divert All to function properly.Note one thing that complicates here is that IPMA user actually has EM profile here. Hence conditions complicate with IPMA/EM service restarts, threads and DB dependencies.
Failover conditions for EM App/Service and IPMA/EM Divert all and Pub DB overload needs to be looked into in details. We could not find an 4.x SRND which documents above. However including URL which similar flavour discussions:
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...