cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
568
Views
0
Helpful
4
Replies

Secondary Dial tone on UCM 8.6.2

slade
Level 1
Level 1

When we migrated out of version 6.x to 8.6, dial tone behavior changed.  Prior to the migration, there was no secondary dial tone.  After the migration, secondary dial tone occured after you dialed a 9 for an outside line.  So, [press speaker button] -> dial tone [press 9] -> secondary dial tone.  Suddenly, the behavior has changed.  Now, its like this:  [press speaker button] -> dial tone [press 9] -> silence -> [press 1] -> secondary dial tone.

Any ideas as to why this is happening?

3 Accepted Solutions

Accepted Solutions

yahsiel2004
Level 7
Level 7

You have to uncheck the "Provide Outside Dial Tone" from your Route Patterns and or Translation Patterns.

Regards,

Yosh

HTH Regards, Yosh

View solution in original post

This is commonly asked question, you can search the forum for solutions, but as Yosh stated it comes down to not having one route pattern/translation pattern that begins with the off-net access code checked with provide outside dial tone, or having DN starting with off-net access code creating an overlap.

Under Route Plan report review all patterns/DN starting with 9, or X or [2-9], etc.

HTH,

Chris

View solution in original post

Jaime Valencia
Cisco Employee
Cisco Employee

That has nothing to do with upgrades, thats a configuration issue.
Check that theres no overlapping in your dial plan, if all your TPs and RPs have the secondary dial tone checked, theres something else in hour dial plan that doesn't have the option and its overlapping.
Use the route plan report to identify whats causing this

Sent from Cisco Technical Support iPad App

HTH

java

if this helps, please rate

View solution in original post

4 Replies 4

yahsiel2004
Level 7
Level 7

You have to uncheck the "Provide Outside Dial Tone" from your Route Patterns and or Translation Patterns.

Regards,

Yosh

HTH Regards, Yosh

This is commonly asked question, you can search the forum for solutions, but as Yosh stated it comes down to not having one route pattern/translation pattern that begins with the off-net access code checked with provide outside dial tone, or having DN starting with off-net access code creating an overlap.

Under Route Plan report review all patterns/DN starting with 9, or X or [2-9], etc.

HTH,

Chris

Jaime Valencia
Cisco Employee
Cisco Employee

That has nothing to do with upgrades, thats a configuration issue.
Check that theres no overlapping in your dial plan, if all your TPs and RPs have the secondary dial tone checked, theres something else in hour dial plan that doesn't have the option and its overlapping.
Use the route plan report to identify whats causing this

Sent from Cisco Technical Support iPad App

HTH

java

if this helps, please rate

slade
Level 1
Level 1

Thanks much guys, good to go.