Actually, the biggest thing I have found that generally always works, is to hard code the port for the voice vlan... after that, even the most pesky phone registers...<br><br><br>Jonathan<br><br><div><span class="gmail_quote">
On 2/28/07, <b class="gmail_sendername">Paul Choi</b> <<a href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is there a decent methodology to troubleshoot IP phone<br>CCM registration when end-to-end connectivity has<br>already been confirmed?<br><br>My thoughts are the first clues would be shown under<br>'debug sccp all' on the local gateway. Does anyone
<br>have any other hints besides what I have already? I<br>honestly don't remember the order of tasks on the CCM<br>cluster to register telephones. I would greatly<br>appreciate it if someone would please provide a<br>
general summary of what needs to be finished on the<br>CCM cluster before registering IP phones on a remote<br>gateway.<br><br>Cheers<br><br><br><br>____________________________________________________________________________________
<br>Cheap talk?<br>Check out Yahoo! Messenger's low PC-to-Phone call rates.<br><a href="http://voice.yahoo.com">http://voice.yahoo.com</a><br>_______________________________________________<br>cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br>