Up until recently our switchboard operators were diverting any calls to the attendant console to another office extension, by hitting the CFwdall button on the extension associated to the console This has been working fine up until last week
Now if the CFwdall is on ,any callers either receive busy or the system on hold music and just sit there for eternity!
Has anyone any pointers as to why this may be happening please?
Are you using the Attendant Console as an application (i.e. with Pilot Point and users going online and offline) or just for call control? Not that that makes a real difference, I'm just curious.
Have you checked the Calling Search Space on CFwdAll on the Attendant's phone within CUCM? Next step is to take a look at the CDR data for that user's phone and see to where it is trying to forward the call.
Is there any pattern on when calls get fast busy vs. lost in MoH Limbo?
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...