<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Dan, you might be hitting the bug where a number is forwarded, then deleted before being unforwarded.<br><br>Check out this thread to see if it helps.<br><br>http://cisco-voip.markmail.org/search/?q=unassigned+DN+bug+with+4.1(3)<br><br>The only other thing I can suggest is rebooting the cluster, pub first, then tftp, then subscribers.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Dan Schmitt" <customade806@hotmail.com><br>To: cisco-voip@puck.nether.net<br>Sent: Monday, December 14, 2009 10:04:16 PM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] CM 4.1 Call Forward All to Voicemail problem<br><br>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
Hello,<br>
<br>
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. <br>
<br>
<strong>A brief history:</strong> About a month ago we added a new subscriber to the cluster and got sub and pub syncronized.<br>
<br>
<strong>Troubleshooting already performed:</strong><br>
<ul>
<li>We have already made sure that Call Forward All under the DN is not checked and that calls are not hitting Unity first.</li>
<li>We ran a DBHelper and had to do a re-initialization of the cluster. </li>
<li>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.</li>
<li>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.</li></ul>
<br>
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! <br>
<br>Dan Schmitt<br><br><a href="mailto:customade806@hotmail.com" target="_blank">customade806@hotmail.com</a><br><br><br><br> <br><hr>Hotmail: Free, trusted and rich email service. <a href="http://clk.atdmt.com/GBL/go/171222984/direct/01/" target="_blank">Get it now.</a><br>_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
</div></body></html>