What causes a system to just stop providing secondary dial tone right after hitting the 9?
If you dial 9 and any other number it gives secondary dial-tone.
Verified the route pattern to provide secondary dial-tone is checked.
What else causes this?
The only other thing I can think of is in the translation pattern, I built a few:
#01 - speed dial function
*001 - Speed dial function
*002 - Speed dial function
Solved! Go to Solution.
This is exactly what I did.
I created a test phone as 9999 and 9998 and removed them, but forgot that cm likes to store the numbers in the directory number section and you need to delete it again there too.
Thank you very much Chris!
Do I need to do anything special to get this to start working again?
I removed the DN 9999 and 9998 and it still does not give me my secondary dialtone as it did before?
The only thing that I can think of is that something that begins with 9 has been added in the Route Plan. Can you check the Route Plan Report to verify.
Chris had a few things to check too and I forgot how Cisco likes to keep track of things even after you delete it. You need to delete it a second time!
Found out what I did.
Created a test phone as 9999 with a secondary as 9998 and deleted the phones, but then needed to delete it from the directory number, under call routing too.
Yes, my Baboon like typing skills and inability to form thoughts on a Monday Morning let me down again ;-)
Did you go to the Route Plan Report>Delete Unassigned DN's and remove everything that begins with 9?
The way secondary dial-tone works is this,
If you have 2 RP:
90794XXX (you checked play outside dialtone)
90788xxx (no play outside dialtone checked)
Callmanager will wait until the 4th digit which is 8 here before playing the outside dial tone.
Your translation patterns begin with 9, so no secondary dial tone will be played until callmanager eliminates all the digits that do not have the provide outside dial tone.
What you need to do is to check the provide outside dial tone for all your translation pattrens that starts with 9...
I get second dial tone no matter what the second digit is every time. It never waits till I get to an unrecognized digit that does not meat any of the other matches.
I hit 91 dial tone
I hit 98 dial tone
I hit 92 dial tone
no matter what the second digit is.
I am a bit lost.
When you hit 9, do you get a second dial tone....???
I get the secondary dial tone once I hit another number after the 9
Everything worked until I built a test phone and assigned it 9999.
I removed the phone, then removed the DN.
I assumed everything would go back to normal once I removed this, but it has not.
To resolve this, you will need to look carefully within your route plan report...
So Suggest you do the following:
Run a route plan report on all others begining with 9, then check any pattern(s) that exist without the provide outside dial tone check box.
This has happened to me before, so I know the problem is that some numbers still exist begining with 9 that do not have the porvide outside dial tone....
I ran into the problem recently and it was a call pickup group that begin with 9. Change it to another number snd secondsry dial tone after dialing 9 came back.