Prafull,
You can see the route patterns and translation patterns that have secondary dial tone enabled by using the following query from the command line:
run sql select dnorpattern,outsidedialtone from numplan
Since the above may give you more data than you care to process, you could also use:
run sql select dnorpattern,outsidedialtone from numplan where outsidedialtone='t'
The patterns presented by the second query have secondary dial tone enabled. You may want to look for patterns that would overlap or match 6060 (your translation) and start by disabling secondary dialtone on those patterns.
If you truly want to disable secondary dialtone "entirely" then you can do so with an update query. But you want to make sure you really want to disable secondary dialtone. The following query would do it. Disclaimer: use at your own risk because there is no going back. I'd recommend that you first log what patterns have secondary dialtone so you can undo manually.
run sql select pkid,dnorpattern,outsidedialtone from numplan where outsidedialtone='t'
Save the above output to a text file as a snap shot of what patterns had the secondary dialtone enabled. Then you can use the following to completely remove secondary dialtone:
admin:run sql update numplan set outsidedialtone='f' where (outsidedialtone='t') and (tkpatternusage=5 or tkpatternusage=6)
The above will set the outsidedialtone to 'f' (false or disabled) where:
(a) The outsidedialtone is 't' (true or enabled) AND
(b) The pattern is a route pattern or a translation pattern
Again, be careful when doing sql updates.
HTH.
-Bill (@ucguerrilla)
Remember to rate helpful posts
