| Ray Burkholder 2007-02-28, 1:11 pm |
| I agree. It has become standard practice for me to connect new phones to a
dedicated voice vlan port to get them upgraded to the latest and greatest.
Then they seem to work properly on regular ports after that.
_____
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Jonathan Charles
Sent: Wednesday, February 28, 2007 09:29
To: Paul Choi
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Consensus for troubleshooting CCM IP
phoneregistration when connectivity is confirmed...
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...
Jonathan
On 2/28/07, Paul Choi <asobihoudai@yahoo.com> wrote:
Is there a decent methodology to troubleshoot IP phone
CCM registration when end-to-end connectivity has
already been confirmed?
My thoughts are the first clues would be shown under
'debug sccp all' on the local gateway. Does anyone
have any other hints besides what I have already? I
honestly don't remember the order of tasks on the CCM
cluster to register telephones. I would greatly
appreciate it if someone would please provide a
general summary of what needs to be finished on the
CCM cluster before registering IP phones on a remote
gateway.
Cheers
________________________________________
____________________________________
________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Scanned for viruses & dangerous content at One Unified
<http://www.oneunified.net> and is believed to be clean.
--
Scanned for viruses and dangerous content at
http://www.oneunified.net and is believed to be clean.
|