[cisco-voip] CM 4.1 Call Forward All to Voicemail problem

[Jonathan Charles]

Just some more details...

It is 4.1(3)SR8a

Unassigned DNs are all deleted... no change (and there were no matches anyway).

Cust has no TAC support....



Jonathan



On Mon, Dec 14, 2009 at 10:02 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> Dan, you might be hitting the bug where a number is forwarded, then deleted
> before being unforwarded.
>
> Check out this thread to see if it helps.
>
> http://cisco-voip.markmail.org/search/?q=unassigned+DN+bug+with+4.1(3)
>
> The only other thing I can suggest is rebooting the cluster, pub first, then
> tftp, then subscribers.
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "Bad grammar makes me [sic]" - Tshirt
>
>
> ----- Original Message -----
> From: "Dan Schmitt" <customade806 at hotmail.com>
> To: cisco-voip at puck.nether.net
> Sent: Monday, December 14, 2009 10:04:16 PM GMT -05:00 US/Canada Eastern
> Subject: [cisco-voip] CM 4.1 Call Forward All to Voicemail problem
>
> Hello,
>
> We are having an issue where calls coming in to a couple particular DNs are
> going straight to voice mail even though the device profile says otherwise.
>
> A brief history: About a month ago we added a new subscriber to the cluster
> and got sub and pub syncronized.
>
> Troubleshooting already performed:
>
> We have already made sure that Call Forward All under the DN is not checked
> and that calls are not hitting Unity first.
> We ran a DBHelper and had to do a re-initialization of the cluster.
> We then created a new entry on the publisher and everything came back OK and
> two servers were syncronizing OK. The problem still occurs and the phone is
> still labeled as Forwarding Calls to VM. However the settings in the server
> says otherwise.
> As another step of troubleshooting we stopped the CCM service on the
> subscriber. All devices did register back to the Publisher and the problem
> still existed. This leads us to believe that the problem existed before
> we added the new subscriber into the cluster.
>
>
> We are stuck and do not know what to look for next. If anybody can shed some
> light or give some advice that would be much appreciated. Attached is a
> trace log containing the errors. Thank You!
>
> Dan Schmitt
>
> customade806 at hotmail.com
>
>
>
>
> ________________________________
> Hotmail: Free, trusted and rich email service. Get it now.
> _______________________________________________ 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
>
>