I have one CSS that's behaving oddly. We require 9 to reach an external line. In my normal device pool/CSS, when I dial 9, I get a dialtone, then I continue with 1800xxxxxxx. However another phone with a different device pool/CSS, I don't hear the dailtone till later. I dial 918 (then I hear the dialtone), then I continue with 00xxxxxxx and the call completes.
Where would I look to find this problem? What determines when it transmits the dialtone sound?
You will hear outside dial tone only when all potentially matching patterns have the "outside dial tone" option checked or enabled on them. If you have a pattern that still may be matched in your CSS/partition list that does not have outside dial tone set on it, then you will not hear outside dial tone until that pattern is elimitated from the potential list of matches.
Here's a SQL query to locate what pattern is causing the problem. This will print all patterns starting with 9 that do not have outside dial tone set and what partitions they are in.
run sql select n.dnorpattern,r.name as partition,n.outsidedialtone from numplan n, routepartition r where n.dnorpattern like '9%' and r.pkid = n.fkroutepartition
There's the dialed number analyzer tool, but that tool checks the number as an "enbloc" number meaning all digits are sent at once rather than digit by digit. You could use that tool to do an analysis on 9 first to see what alternative matches there are, then enter 9x as the dialed number and do another analysis, etc. Another approach would be to use the phone that is having the problem and go off hook and dial 9 then 1. If you hear outside dial tone, you know the pattern does not start with 91. Hang up, and go off hook and dial 92, if you do not get secondary dial tone, the pattern starts with 92. You can keep doing this process with 921, 922, 923, to isolate it down to the problem pattern.
Interesting ideas. I tried the DNA, but when I just enter 9, the Alternate Matches shows:
Note: Information Not Available
So trying via the problem phone, I can confirm that 9[0,2-9] provide dialtone. Only 91 waits. Then again 91[0,2-9] provides dialtone. So I assume the problem has something to do with 911. But my 911 translation pattern looks consistant for this CSS and my working ones.
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...