|
Home > Archive > Voice over IP Cisco > January 2008 > secondary dial tone problems
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
secondary dial tone problems
|
|
| Peter Ejmont 2007-12-29, 1:11 pm |
| Hi all,
I need your expert advice here.
Our campus voip is based on ccm (currently 4.1(3)) and it has been working
great for years.
Approx. a week ago, something has changed that secondary dial tone is played
in different places.
Our dial plan requires to dial 8 for outside calls and normally, after
pressing 8 you get
the socondary dial tone right away, regardless if call is for local (7
digit), national (10 digit) or
international. Well, things got interesting lately. Dialing local calls, I
get secondary dial tone after pressing
2 digits, one 8 and any number from 2-9. Long distance, secondary dial tone
is heard after pressing
81(2-9), so after 3 digits. International calls are similar to local calls.
Secondary dial tone is played after 80.
Nothing has changed in route patterns, gateways, route lists, etc. The only
few changes I found was someone
added one voip phone starting with a temporary 8XXXX number. I deleted it
but still have problems. Also,
2 ATA-188 were added but they have problems registering with call manager.
I ran the route pattern report and could not find anymore instances of
anything starting with 8 (except defined
dial plan). I used DNA for verification and the secondary dial tone should
be heard after pressing 8.
Any thoughts?
Thanks,
Peter
| |
| Paul Choi 2007-12-29, 1:11 pm |
| We've also had this very odd problem with no real
understanding of why it occurs. It creates great
confusion with users and they assume the phone isn't
working. I have yet to hear a clear explanation of why
this occurs. Our users would experience secondary
dialtone after about seven digits.
Paul
--- Peter Ejmont <pejmont@gmail.com> wrote:
> Hi all,
> I need your expert advice here.
> Our campus voip is based on ccm (currently 4.1(3))
> and it has been working
> great for years.
> Approx. a week ago, something has changed that
> secondary dial tone is played
> in different places.
> Our dial plan requires to dial 8 for outside calls
> and normally, after
> pressing 8 you get
> the socondary dial tone right away, regardless if
> call is for local (7
> digit), national (10 digit) or
> international. Well, things got interesting lately.
> Dialing local calls, I
> get secondary dial tone after pressing
> 2 digits, one 8 and any number from 2-9. Long
> distance, secondary dial tone
> is heard after pressing
> 81(2-9), so after 3 digits. International calls are
> similar to local calls.
> Secondary dial tone is played after 80.
>
> Nothing has changed in route patterns, gateways,
> route lists, etc. The only
> few changes I found was someone
> added one voip phone starting with a temporary 8XXXX
> number. I deleted it
> but still have problems. Also,
> 2 ATA-188 were added but they have problems
> registering with call manager.
> I ran the route pattern report and could not find
> anymore instances of
> anything starting with 8 (except defined
> dial plan). I used DNA for verification and the
> secondary dial tone should
> be heard after pressing 8.
>
> Any thoughts?
>
> Thanks,
> Peter
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
________________________________________
____
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
| |
| Joel P 2007-12-29, 1:11 pm |
| I had this same issue occur to me at one of our customers site about 8
months ago. At first we thought it was user error because it was a random
occurrence. Eventually we were able to duplicate it. We looked everywhere
for what could cause this and found nothing.
On a whim we disabled secondary dial tone for about a week while we tried to
Troubleshoot it, but of course found nothing wrong. We then re-enabled it
and the problem just went away on its own and hasn't happened again since.
No real resolution from Tac either.
Joel P
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Paul Choi
Sent: Saturday, December 29, 2007 11:16 AM
To: Peter Ejmont; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] secondary dial tone problems
We've also had this very odd problem with no real
understanding of why it occurs. It creates great
confusion with users and they assume the phone isn't
working. I have yet to hear a clear explanation of why
this occurs. Our users would experience secondary
dialtone after about seven digits.
Paul
--- Peter Ejmont <pejmont@gmail.com> wrote:
> Hi all,
> I need your expert advice here.
> Our campus voip is based on ccm (currently 4.1(3))
> and it has been working
> great for years.
> Approx. a week ago, something has changed that
> secondary dial tone is played
> in different places.
> Our dial plan requires to dial 8 for outside calls
> and normally, after
> pressing 8 you get
> the socondary dial tone right away, regardless if
> call is for local (7
> digit), national (10 digit) or
> international. Well, things got interesting lately.
> Dialing local calls, I
> get secondary dial tone after pressing
> 2 digits, one 8 and any number from 2-9. Long
> distance, secondary dial tone
> is heard after pressing
> 81(2-9), so after 3 digits. International calls are
> similar to local calls.
> Secondary dial tone is played after 80.
>
> Nothing has changed in route patterns, gateways,
> route lists, etc. The only
> few changes I found was someone
> added one voip phone starting with a temporary 8XXXX
> number. I deleted it
> but still have problems. Also,
> 2 ATA-188 were added but they have problems
> registering with call manager.
> I ran the route pattern report and could not find
> anymore instances of
> anything starting with 8 (except defined
> dial plan). I used DNA for verification and the
> secondary dial tone should
> be heard after pressing 8.
>
> Any thoughts?
>
> Thanks,
> Peter
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
____________________________________
________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Lelio Fulgenzi 2007-12-29, 1:11 pm |
| you found the root of the problem,i.e. a number beginning with 8, and that should have fixed it, but you probably need a restart of the cluster.
fifty bucks that is what the tac will tell you.
----- Original Message -----
From: Peter Ejmont
To: cisco-voip@puck.nether.net
Sent: Saturday, December 29, 2007 9:05 AM
Subject: [cisco-voip] secondary dial tone problems
Hi all,
I need your expert advice here.
Our campus voip is based on ccm (currently 4.1(3)) and it has been working great for years.
Approx. a week ago, something has changed that secondary dial tone is played in different places.
Our dial plan requires to dial 8 for outside calls and normally, after pressing 8 you get
the socondary dial tone right away, regardless if call is for local (7 digit), national (10 digit) or
international. Well, things got interesting lately. Dialing local calls, I get secondary dial tone after pressing
2 digits, one 8 and any number from 2-9. Long distance, secondary dial tone is heard after pressing
81(2-9), so after 3 digits. International calls are similar to local calls. Secondary dial tone is played after 80.
Nothing has changed in route patterns, gateways, route lists, etc. The only few changes I found was someone
added one voip phone starting with a temporary 8XXXX number. I deleted it but still have problems. Also,
2 ATA-188 were added but they have problems registering with call manager.
I ran the route pattern report and could not find anymore instances of anything starting with 8 (except defined
dial plan). I used DNA for verification and the secondary dial tone should be heard after pressing 8.
Any thoughts?
Thanks,
Peter
------------------------------------------------------------------------------
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Avner Izhar 2007-12-29, 1:11 pm |
| Hi,
You are looking in the right direction, prob that 8xxxx phone number or similar.
If you didn't restart ccm service after doing the changes then it might help.
It is something in that number range which doesn't have the secondary dial tone checked.
HTH,
-------------------------------------------
thanks,
Avner Izhar
CCIE#15999 (Voice), CCVP, CCSI# 31623
Technical Instructor
CCBOOTCAMP - A cisco Sponsored Organization (SO)
Email: aizhar@ccbootcamp.com
Toll Free: 877-654-2243
Direct: +1-702-968-5100 = Outside the USA
FAX: +1-702-446-8012
YES! We take cisco Learning Credits!
Training And Remote Racks: http://www.ccbootcamp.com
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Peter Ejmont
Sent: Saturday, December 29, 2007 06:05
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] secondary dial tone problems [bcc][faked-from][html-rem]
Hi all,
I need your expert advice here.
Our campus voip is based on ccm (currently 4.1(3)) and it has been working
great for years.
Approx. a week ago, something has changed that secondary dial tone is played
in different places.
Our dial plan requires to dial 8 for outside calls and normally, after
pressing 8 you get
the socondary dial tone right away, regardless if call is for local (7
digit), national (10 digit) or
international. Well, things got interesting lately. Dialing local calls, I
get secondary dial tone after pressing
2 digits, one 8 and any number from 2-9. Long distance, secondary dial tone
is heard after pressing
81(2-9), so after 3 digits. International calls are similar to local calls.
Secondary dial tone is played after 80.
Nothing has changed in route patterns, gateways, route lists, etc. The only
few changes I found was someone
added one voip phone starting with a temporary 8XXXX number. I deleted it
but still have problems. Also,
2 ATA-188 were added but they have problems registering with call manager.
I ran the route pattern report and could not find anymore instances of
anything starting with 8 (except defined
dial plan). I used DNA for verification and the secondary dial tone should
be heard after pressing 8.
Any thoughts?
Thanks,
Peter
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.12/1202 - Release Date: 12/29/2007 13:27
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.12/1202 - Release Date: 12/29/2007 13:27
| |
| Peter Ejmont 2007-12-29, 7:11 pm |
| The problem is that I already restarted it twice. Still, problem exists.
I'll try Joel's suggestion to disable a secondary dial tone on all route
patterns.
One more discovery to make it even more interesting. We have quite few
numbers
in 4xxxx range for call center agents. I have 3 phones where 4xxxx are
primary numbers,
2 used for testing and 1 for CER emergency notifications. 2 of them work
fine. You hear
a secondary dial tone as soon as you press 8. Thrid, happens to be CER's
phone, has the
same problem as the rest of the campus.
Thanks,
Peter
On Dec 29, 2007 11:32 AM, Lelio Fulgenzi < lelio@uoguelph.ca> wrote:
> you found the root of the problem,i.e. a number beginning with 8, and
> that should have fixed it, but you probably need a restart of the cluster.
>
> fifty bucks that is what the tac will tell you.
>
> ----- Original Message -----
> *From:* Peter Ejmont <pejmont@gmail.com>
> *To:* cisco-voip@puck.nether.net
> *Sent:* Saturday, December 29, 2007 9:05 AM
> *Subject:* [cisco-voip] secondary dial tone problems
>
> Hi all,
> I need your expert advice here.
> Our campus voip is based on ccm (currently 4.1(3)) and it has been working
> great for years.
> Approx. a week ago, something has changed that secondary dial tone is
> played in different places.
> Our dial plan requires to dial 8 for outside calls and normally, after
> pressing 8 you get
> the socondary dial tone right away, regardless if call is for local (7
> digit), national (10 digit) or
> international. Well, things got interesting lately. Dialing local calls, I
> get secondary dial tone after pressing
> 2 digits, one 8 and any number from 2-9. Long distance, secondary dial
> tone is heard after pressing
> 81(2-9), so after 3 digits. International calls are similar to local
> calls. Secondary dial tone is played after 80.
>
> Nothing has changed in route patterns, gateways, route lists, etc. The
> only few changes I found was someone
> added one voip phone starting with a temporary 8XXXX number. I deleted it
> but still have problems. Also,
> 2 ATA-188 were added but they have problems registering with call manager.
> I ran the route pattern report and could not find anymore instances of
> anything starting with 8 (except defined
> dial plan). I used DNA for verification and the secondary dial tone should
> be heard after pressing 8.
>
> Any thoughts?
>
> Thanks,
> Peter
>
> ------------------------------
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
| |
| Lelio Fulgenzi 2007-12-30, 1:12 am |
| oh boy. interesting to say the least.
have you tried deleting the number from the "unused" numbers?
in route plan report select unused DNs and delete it from there.
that might help. ???
----- Original Message -----
From: Peter Ejmont
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Sent: Saturday, December 29, 2007 7:52 PM
Subject: Re: [cisco-voip] secondary dial tone problems
The problem is that I already restarted it twice. Still, problem exists.
I'll try Joel's suggestion to disable a secondary dial tone on all route patterns.
One more discovery to make it even more interesting. We have quite few numbers
in 4xxxx range for call center agents. I have 3 phones where 4xxxx are primary numbers,
2 used for testing and 1 for CER emergency notifications. 2 of them work fine. You hear
a secondary dial tone as soon as you press 8. Thrid, happens to be CER's phone, has the
same problem as the rest of the campus.
Thanks,
Peter
On Dec 29, 2007 11:32 AM, Lelio Fulgenzi < lelio@uoguelph.ca> wrote:
you found the root of the problem,i.e. a number beginning with 8, and that should have fixed it, but you probably need a restart of the cluster.
fifty bucks that is what the tac will tell you.
----- Original Message -----
From: Peter Ejmont
To: cisco-voip@puck.nether.net
Sent: Saturday, December 29, 2007 9:05 AM
Subject: [cisco-voip] secondary dial tone problems
Hi all,
I need your expert advice here.
Our campus voip is based on ccm (currently 4.1(3)) and it has been working great for years.
Approx. a week ago, something has changed that secondary dial tone is played in different places.
Our dial plan requires to dial 8 for outside calls and normally, after pressing 8 you get
the socondary dial tone right away, regardless if call is for local (7 digit), national (10 digit) or
international. Well, things got interesting lately. Dialing local calls, I get secondary dial tone after pressing
2 digits, one 8 and any number from 2-9. Long distance, secondary dial tone is heard after pressing
81(2-9), so after 3 digits. International calls are similar to local calls. Secondary dial tone is played after 80.
Nothing has changed in route patterns, gateways, route lists, etc. The only few changes I found was someone
added one voip phone starting with a temporary 8XXXX number. I deleted it but still have problems. Also,
2 ATA-188 were added but they have problems registering with call manager.
I ran the route pattern report and could not find anymore instances of anything starting with 8 (except defined
dial plan). I used DNA for verification and the secondary dial tone should be heard after pressing 8.
Any thoughts?
Thanks,
Peter
--------------------------------------------------------------------------
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Peter Ejmont 2007-12-30, 7:12 am |
| All unused numbers starting with 8 were deleted to begin with.
Then, the entire cluster was restarted.
Thanks,
Peter
On Dec 29, 2007 11:11 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:
> oh boy. interesting to say the least.
>
> have you tried deleting the number from the "unused" numbers?
>
> in route plan report select unused DNs and delete it from there.
>
> that might help. ???
>
>
| |
| Lelio Fulgenzi 2007-12-30, 1:12 pm |
| By 'unused' I meant 'unassigned'.
Route Plan > Route Plan Report > Find Unassigned DN (from drop down).
This will give you a list of DNs you have deleted, but not purged from the system.
Just wanted to be clear, some people miss this step.
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Life expectancy would grow by leaps and bounds if green vegetables smelled as good as bacon."
Doug Larson
----- Original Message -----
From: Peter Ejmont
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Sent: Sunday, December 30, 2007 5:34 AM
Subject: Re: [cisco-voip] secondary dial tone problems
All unused numbers starting with 8 were deleted to begin with.
Then, the entire cluster was restarted.
Thanks,
Peter
On Dec 29, 2007 11:11 PM, Lelio Fulgenzi < lelio@uoguelph.ca> wrote:
oh boy. interesting to say the least.
have you tried deleting the number from the "unused" numbers?
in route plan report select unused DNs and delete it from there.
that might help. ???
| |
| Ryan Ratliff 2007-12-31, 1:11 pm |
| Looks like you are on the right track so far in identifying the
numbers conflicting with the route pattern. Secondary (outside) dial
tone is played only when all potential matches for a dialed string
have the flag set to play outside dialtone. Since you were
receiving it after dialing 8[2-9] and 81[2-9] this would tell me you
have a pattern beginning with 81 that does not have the flag set to
play outside dialtone.
-Ryan
On Dec 30, 2007, at 11:58 AM, Lelio Fulgenzi wrote:
By 'unused' I meant 'unassigned'.
Route Plan > Route Plan Report > Find Unassigned DN (from drop down).
This will give you a list of DNs you have deleted, but not purged
from the system.
Just wanted to be clear, some people miss this step.
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
“Life expectancy would grow by leaps and bounds if green vegetables
smelled as good as bacon.”
Doug Larson
----- Original Message -----
From: Peter Ejmont
To: Lelio Fulgenzi
Cc: cisco-voip@puck.nether.net
Sent: Sunday, December 30, 2007 5:34 AM
Subject: Re: [cisco-voip] secondary dial tone problems
All unused numbers starting with 8 were deleted to begin with.
Then, the entire cluster was restarted.
Thanks,
Peter
On Dec 29, 2007 11:11 PM, Lelio Fulgenzi < lelio@uoguelph.ca> wrote:
oh boy. interesting to say the least.
have you tried deleting the number from the "unused" numbers?
in route plan report select unused DNs and delete it from there.
that might help. ???
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Paul Choi 2007-12-31, 1:11 pm |
| Did this completely resolve your problems?
Paul
--- Peter Ejmont <pejmont@gmail.com> wrote:
> All unused numbers starting with 8 were deleted to
> begin with.
> Then, the entire cluster was restarted.
>
> Thanks,
> Peter
>
>
> On Dec 29, 2007 11:11 PM, Lelio Fulgenzi
> <lelio@uoguelph.ca> wrote:
>
> "unused" numbers?
> it from there.
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
________________________________________
____
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
| |
| Jason Burns 2007-12-31, 1:11 pm |
| To add a bit to Ryan's email:
I always use the following query in 4.X (either query analyzer or =
enterprise manager with your highest numbered CCM030X DB selected) to =
see what might not have "Provide Outside Dialtone" checked.
select dnorpattern, outsidedialtone
from numplan
where dnorpattern like '8%' and outsidedialtone =3D '0'
If that doesn't work...
It's also possible that the forwarding intercept for that 8XXXX is still =
stuck in the database and is causing CCM to hold off on providing the =
outside dialtone because CCM thinks the number still exists.
This wouldn't be visible in the previous query, but could be identified =
in the CCM traces.
CSCsj30852 - CM 4.x - Inactive or Unassigned DN with CFA still forwards =
calls
Which was fixed in an Engineering Special (no SR released for it yet)
It's more likely an overlapping pattern somewhere without the checkbox, =
but if after more searching you can't find the offending pattern you =
might want to turn to the traces / TAC.
Thanks,
Jason Burns
On 12/31/2007 10:27 AM, Ryan Ratliff wrote:
> Looks like you are on the right track so far in identifying the numbers =
> conflicting with the route pattern. Secondary (outside) dial tone is =
> played only when all potential matches for a dialed string have the flag =
> set to play outside dialtone. Since you were receiving it after =
> dialing 8[2-9] and 81[2-9] this would tell me you have a pattern =
> beginning with 81 that does not have the flag set to play outside dialton=
e. =
> =
> -Ryan
> =
> =
> On Dec 30, 2007, at 11:58 AM, Lelio Fulgenzi wrote:
> =
> By 'unused' I meant 'unassigned'.
> =
> Route Plan > Route Plan Report > Find Unassigned DN (from drop down).
> =
> This will give you a list of DNs you have deleted, but not purged from =
> the system.
> =
> Just wanted to be clear, some people miss this step.
> =
> -------------------------------------------------------------------------=
-------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> =93Life expectancy would grow by leaps and bounds if green vegetables =
> smelled as good as bacon.=94
> Doug Larson
> =
> =
> =
> ----- Original Message -----
> *From:* Peter Ejmont <mailto:pejmont@gmail.com>
> *To:* Lelio Fulgenzi <mailto:lelio@uoguelph.ca>
> *Cc:* cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> *Sent:* Sunday, December 30, 2007 5:34 AM
> *Subject:* Re: [cisco-voip] secondary dial tone problems
> =
> All unused numbers starting with 8 were deleted to begin with.
> Then, the entire cluster was restarted.
> =
> Thanks,
> Peter
> =
> =
> On Dec 29, 2007 11:11 PM, Lelio Fulgenzi < lelio@uoguelph.ca
> <mailto:lelio@uoguelph.ca>> wrote:
> =
> oh boy. interesting to say the least.
> =
> have you tried deleting the number from the "unused" numbers?
> =
> in route plan report select unused DNs and delete it from there.
> =
> that might help. ???
> =
> =
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
> =
> =
> ------------------------------------------------------------------------
> =
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Ryan Ratliff 2007-12-31, 1:11 pm |
| 4.1(3)SR6 should be out and does have the fix.
-Ryan
On Dec 31, 2007, at 11:33 AM, Jason Burns wrote:
To add a bit to Ryan's email:
I always use the following query in 4.X (either query analyzer or =
enterprise manager with your highest numbered CCM030X DB selected) to =
see what might not have "Provide Outside Dialtone" checked.
select dnorpattern, outsidedialtone
from numplan
where dnorpattern like '8%' and outsidedialtone =3D '0'
If that doesn't work...
It's also possible that the forwarding intercept for that 8XXXX is =
still stuck in the database and is causing CCM to hold off on =
providing the outside dialtone because CCM thinks the number still =
exists.
This wouldn't be visible in the previous query, but could be =
identified in the CCM traces.
CSCsj30852 - CM 4.x - Inactive or Unassigned DN with CFA still =
forwards calls
Which was fixed in an Engineering Special (no SR released for it yet)
It's more likely an overlapping pattern somewhere without the =
checkbox, but if after more searching you can't find the offending =
pattern you might want to turn to the traces / TAC.
Thanks,
Jason Burns
On 12/31/2007 10:27 AM, Ryan Ratliff wrote:
> Looks like you are on the right track so far in identifying the =
> numbers conflicting with the route pattern. Secondary (outside) =
> dial tone is played only when all potential matches for a dialed =
> string have the flag set to play outside dialtone. Since you were =
> receiving it after dialing 8[2-9] and 81[2-9] this would tell me =
> you have a pattern beginning with 81 that does not have the flag =
> set to play outside dialtone. -Ryan
> On Dec 30, 2007, at 11:58 AM, Lelio Fulgenzi wrote:
> By 'unused' I meant 'unassigned'.
> Route Plan > Route Plan Report > Find Unassigned DN (from drop down).
> This will give you a list of DNs you have deleted, but not purged =
> from the system.
> Just wanted to be clear, some people miss this step.
> =
> ---------------------------------------------------------------------- =
> ----------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> =93Life expectancy would grow by leaps and bounds if green vegetables =
> smelled as good as bacon.=94
> Doug Larson
> ----- Original Message -----
> *From:* Peter Ejmont <mailto:pejmont@gmail.com>
> *To:* Lelio Fulgenzi <mailto:lelio@uoguelph.ca>
> *Cc:* cisco-voip@puck.nether.net <mailto:cisco- =
> voip@puck.nether.net>
> *Sent:* Sunday, December 30, 2007 5:34 AM
> *Subject:* Re: [cisco-voip] secondary dial tone problems
> All unused numbers starting with 8 were deleted to begin with.
> Then, the entire cluster was restarted.
> Thanks,
> Peter
> On Dec 29, 2007 11:11 PM, Lelio Fulgenzi < lelio@uoguelph.ca
> <mailto:lelio@uoguelph.ca>> wrote:
> oh boy. interesting to say the least.
> have you tried deleting the number from the =
> "unused" numbers?
> in route plan report select unused DNs and delete =
> it from there.
> that might help. ???
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ---------------------------------------------------------------------- =
> --
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Peter Ejmont 2008-01-02, 1:12 am |
| I did uncheck all "provide dial tone" on all route patterns starting with 8.
Worked like a charm -> no secondary dial tone. Restarted the entire cluster
then, checked all boxes again and restarted the cluster again. Still,
secondary dial tone was in the wrong place.
Then ran a query:
select dnorpattern, outsidedialtone
from numplan
where dnorpattern like '8%' and outsidedialtone = '0'
As I suspected, no results.
1 day later, I am about to download the newest release (4.1(3)sr6)
and start upgrading but guess what, the secondary dial tone is in the right
place. Very odd.
I am not sure what to think of it.
Cisco folks, is it an isolated incident (besides Paul's and Joel's) or is it
a common occurence? Maybe I should disable the secondary dial tone all
together so users won't be confused as much next time? I am just looking for
some suggestions.
Thank you all for help. You guys are great!
On Dec 31, 2007 11:52 AM, Ryan Ratliff <rratliff@cisco.com> wrote:
> 4.1(3)SR6 should be out and does have the fix.
>
> -Ryan
>
> On Dec 31, 2007, at 11:33 AM, Jason Burns wrote:
>
> To add a bit to Ryan's email:
>
> I always use the following query in 4.X (either query analyzer or
> enterprise manager with your highest numbered CCM030X DB selected) to
> see what might not have "Provide Outside Dialtone" checked.
>
> select dnorpattern, outsidedialtone
> from numplan
> where dnorpattern like '8%' and outsidedialtone = '0'
>
>
> If that doesn't work...
>
> It's also possible that the forwarding intercept for that 8XXXX is
> still stuck in the database and is causing CCM to hold off on
> providing the outside dialtone because CCM thinks the number still
> exists.
>
> This wouldn't be visible in the previous query, but could be
> identified in the CCM traces.
>
> CSCsj30852 - CM 4.x - Inactive or Unassigned DN with CFA still
> forwards calls
>
> Which was fixed in an Engineering Special (no SR released for it yet)
>
> It's more likely an overlapping pattern somewhere without the
> checkbox, but if after more searching you can't find the offending
> pattern you might want to turn to the traces / TAC.
>
> Thanks,
> Jason Burns
>
>
> On 12/31/2007 10:27 AM, Ryan Ratliff wrote:
>
| |
| Jason Wydra 2008-01-02, 1:12 am |
| I would have to quess that the temp 8XXXX is what caused the problem. Double
check the route plan report. It could also be that SQL still has the temp
8XXXX number in the database, even though you don't see it in CCM admin. If
you know how to run SQL queries, you could try looking there. Be very
careful when poking around in SQL.
On Dec 29, 2007 8:05 AM, Peter Ejmont <pejmont@gmail.com> wrote:
> Hi all,
> I need your expert advice here.
> Our campus voip is based on ccm (currently 4.1(3)) and it has been working
> great for years.
> Approx. a week ago, something has changed that secondary dial tone is
> played in different places.
> Our dial plan requires to dial 8 for outside calls and normally, after
> pressing 8 you get
> the socondary dial tone right away, regardless if call is for local (7
> digit), national (10 digit) or
> international. Well, things got interesting lately. Dialing local calls, I
> get secondary dial tone after pressing
> 2 digits, one 8 and any number from 2-9. Long distance, secondary dial
> tone is heard after pressing
> 81(2-9), so after 3 digits. International calls are similar to local
> calls. Secondary dial tone is played after 80.
>
> Nothing has changed in route patterns, gateways, route lists, etc. The
> only few changes I found was someone
> added one voip phone starting with a temporary 8XXXX number. I deleted it
> but still have problems. Also,
> 2 ATA-188 were added but they have problems registering with call manager.
> I ran the route pattern report and could not find anymore instances of
> anything starting with 8 (except defined
> dial plan). I used DNA for verification and the secondary dial tone should
> be heard after pressing 8.
>
> Any thoughts?
>
> Thanks,
> Peter
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
|
|
|
|
|