[cisco-voip] Problem Directing all calls to VM

Wed Sep 12 18:17:25 EDT 2007

That was it.  TAC had just started pouring over my trace files, when we noticed the problem stemmed from the modified CTI ports.  They all had CFA enabled.  We were resyncing the database and were planning on rebooting the cluster when your fix came through.

Thanks for your help.

Eddie Klaczko

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, September 12, 2007 3:00 PM
To: Lelio Fulgenzi
Cc: Ted Nugent; Erick Bergquist; Klaczko, Edwin; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Problem Directing all calls to VM

Most likely this was CSCsj30852, fixed in ES119 for 4.1(3).
Basically if you delete a dn or change the partition on a dn that has
ANY type of forwarding set, the forward entry stays in the intercept
table and blocks all calls t that dn if it happens to be the highest
partition in the calling device's CSS.

Even deleting the unassigned DN does not fix it, you have to re-add
the "bad" dn to a device, clear all forwards, then delete it.

-Ryan

On Sep 12, 2007, at 3:55 PM, Lelio Fulgenzi wrote:

at least they didn't tell you to upgrade. ;)

----- Original Message -----
From: Ted Nugent
To: Erick Bergquist
Cc: Klaczko, Edwin ; cisco-voip at puck.nether.net
Sent: Wednesday, September 12, 2007 3:44 PM
Subject: Re: [cisco-voip] Problem Directing all calls to VM

I just got confirmation from our SE working with TAC that thier
recommendation after reviewing the traces was to reboot the cluster,
shocker! We can't get a maintenance window until sunday though so
I'll report back then.

On 9/12/07, Erick Bergquist <erickbee at gmail.com> wrote: I had a
similar problem a few weeks ago, forgot the exact 4.1(3) SR
they had offhand, but calls to VM were busy , and even calling VM
ports directly were busy. If you had removed them from the hunt group
they then rang the first time when you called them but then were busy
on second and third calls. We had to reset the hunt list for the
voicemail and that cleared it up.

On 9/12/07, Ted Nugent <tednugent73 at gmail.com> wrote:
 >
 >
 > Yes we had a very similar experience just a couple days ago!
Something with
 > CCM 4.1(3)sr5b is VERY screwy!
 >
 > Our problem is that deleted patterns/dns are still being held onto
by CM
 > someplace??? They are no longer listed in the route plan report
and they are
 > not showing up in the numplan table in SQL on the pub or Sub so
that leaves
 > RAM. At any rate, we spent a couple hours toying with it and this
I what was
 > occurring
 >
 >
 >
 > Someone accidentally added a phones extension (4001) to the wrong
partition
 > (Partition-A) which is ordered first in all CSSes. The DN was then
move to
 > the proper partition (PartitionB) order 3 rd in all CSS (deleted?
Moved? I'm
 > not sure I was not engaged at that point).
 >
 > After the move we got fast busy when dialing 4001
 >
 > We deleted the unused 4001 from the route plan report thinking
that this was
 > giving us grief although it should NOT.
 >
 > Fast Busy
 >
 > Cursed Loudly for a few hours!!
 >
 > Reorder a CSS so that PartitionB is order in front of PartitionA
 >
 > RING!
 >
 > Move it back
 >
 > Fast busy!
 >
 > Repeat with same results multiple times
 >
 > Check routeplan report
 >
 > 4001 is only in partitionB
 >
 > Check SQL on SUB and PUB, single DN for 4001 (also DBLHelper looks
clean)
 >
 > The interesting piece is that if I run DNA it matches the correct DN
 > everytime no mater the order in the CSS
 >
 >
 >
 > We've temporarily reordered the CSS so that this extension can be
dialed and
 > I think we have a maintenance window scheduled to kick the CM
service and/or
 > bounce the servers to see if either resolves the issue. I'll let
you know
 > how it turns out.
 >
 >
 >
 >
 > On 9/12/07, Klaczko, Edwin <EdwinKlaczko at sd54.k12.il.us> wrote:
 > >
 > >
 > >
 > >
 > >
 > > I just got done moving over 50 users to new extensions.  I
placed their
 > old extensions as Alternate Extensions in Unity so anyone dialing
their old
 > numbers would get their voicemail.  I found the instructions to
setup a CTI
 > port to direct all calls to VM.  We use this for time of day
routing so I am
 > familiar with it.  Setup the first user and tested worked great.
Tried the
 > next user and fast busy.  Tried a couple more and fast busy.  I
ran the
 > dialed number analyzer and the numbers are be matched to
voicemail.  I can't
 > understand why the first one works and the rest don't.  At first I
thought I
 > could list a bunch of numbers and create one CTI port when the
second number
 > didn't work I created separate CTI ports for each number, still
didn't work.
 >  We use *XXXX to go right to voicemail and when I dial the
extensions with
 > an * it goes right into the voicemailbox like it should.  Has
anyone run up
 > against this?
 > >
 > >
 > >
 > > CCM 4.1(3)sr5b
 > >
 > > Unity 5.0(1)
 > >
 > >
 > >
 > >
 > >
 > > Eddie Klaczko
 > >
 > >
 > > _______________________________________________
 > > cisco-voip mailing list
 > > cisco-voip at puck.nether.net
 > > https://puck.nether.net/mailman/listinfo/cisco-voip
 > >
 >
 >
 > _______________________________________________
 > cisco-voip mailing list
 > cisco-voip at puck.nether.net
 > https://puck.nether.net/mailman/listinfo/cisco-voip
 >

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip