Every few days I have a dozen callers in teh Example Interview. I have gone through and checked, and I CAN NOT find out how they are getting there. Is there a utility I cna use to look to see what is linked to that and fix it?
You can set a link to the interview handler in question in the ATM and when you then click on the interviewer in the lower right it will list all the subscriber and call handlers that link to that interview handler... the one you just created for it to show up will be there, of course, but there should be at least one other I would imagine...
Just pick a one key link off the opening greeting that's not being used, right click on it and select "Send to Interviewer". In the dialog that pops up, hit the "select existing" tab and pick your example interviewer. The interviewer then shows up in the tree control and you can click on it.
check the after greeting and after message actions on the opening greeting and the operator call handler - be sure to check ALL the greetings for after greeting action - I don't think ATM is filtering for those - it's just looking for one key links, I'll have to walk the code.
so far, all handlers look okay. I have about 340 subscribers at the moment. I will take a look a few at time. Could hte live record default route be messing things up and is that even possible with a CCM integration?
OK... I whipped up some SQL queries that should help you run this guy down and tested them out locally here... I'll actually add similiar queries into the next version of ATM to populate the "links from" tables in the lower right.
You can just copy and paste these into the SQL Query Analyzer tool - if you don't have that handy you can do this in the OSQL interface by typing "osql -E" at a command prompt and using the same query strings.
This first query will dump ou the alias of the call handler and the name of the message rule (greeting) that has an after greeting action set to go to the example administrator. this will pick up call handlers and subscribers, the subscriber alias will be something like "ch_lindborg" or the like:
from CallHandler, MenuEntry inner join InterviewHandler
There's very few other ways folks can end up in the interview handler - if you have an ID associated with it (which is optional) users could be dialing it from the opening greeting. There could be a routing rule set to go to it but you'd see that in the SA routing rules tables (no, there's no chance the live record has anything at all to do with this).
I strongly suspect it something simple like the operator call handler's off hour greeting having an after greeting action set to go to the example interview handler or the like.
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...