Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Disable the secondary dial-tone

Dear Team,

  When a user presses 6060 Translation pattern call routed on PSTN number 80XXXXXXXXXX with

secondary dial-tone

Is there a way to disable the secondary dial-tone in CallManager 8.x so that when a user presses 6060 Translation pattern will not  get an secondary outside line, CallManager simply continues to accept numbers until it finds a match, without playing the second tone?  I had disabled the "provide Outside Dial-Tone" box, but stillsecondary dial-tone present

.   I need to find a way to disable secondary dial-tone entirely.we are using MGCP gateway.


Regards,

Prafull

2 ACCEPTED SOLUTIONS

Accepted Solutions
VIP Super Bronze

Disable the secondary dial-tone

Praful,

This is most likely because you have overlapping patterns. There are other patterns begining with 6 that have the prvide outside dial tone on them..You need to disable it on those patterns too

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Disable the secondary dial-tone

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

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

3 REPLIES
VIP Super Bronze

Disable the secondary dial-tone

Praful,

This is most likely because you have overlapping patterns. There are other patterns begining with 6 that have the prvide outside dial tone on them..You need to disable it on those patterns too

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Disable the secondary dial-tone

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

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

Hall of Fame Super Red

Disable the secondary dial-tone

Nice answers from my two friends Bill & Deji here +5

Cheers!

Huff

"A smile relieves a heart that grieves" 

- Stones

406
Views
0
Helpful
3
Replies
CreatePlease to create content