[cisco-voip] VG202/204 registration errors

[Ed Leatherman]

Yes it returns a row with that device name.

Looking in the trace, it appears that the DB query cm is doing returns
all this information (I didnt paste it to the list for brevity). It
returns the deviceID etc. It gets down to:
CCM|<--DB: Int[deviceUserHoldMOHAudioSource]=[0]
and then the next line is the 'fail to get callmanagerGroupEntry template' error

IOS config looks OK.. I don't think anything was changed in it from
default other than to put a password on the console port. debug showed
dbconfig error when it tried to register the autoconfig interface.

On Fri, Oct 30, 2009 at 10:34 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
> And you found the device in db when doing the CLI command?
> run sql select * from device where name='AN1DA2EA3B63FFF'
>
> -Ryan
>
> On Oct 30, 2009, at 10:19 AM, Ed Leatherman wrote:
>
> Have never looked at traces related to device registration before -
> lots of messages here.
>
> 10/30/2009 08:58:47.273 CCM|Processing StationReg. regCount: 1
> DeviceName=AN1DA2EA3B63FFF, TCPPid = [2.100.7.970508],
> IPAddr=10.182.62.246, Port=54532, Device Controller=[2,66,24774]
> 10/30/2009 08:58:47.273 CCM|dBProcs - device AN1DA2EA3B63FFF is not
> found. real time access database
>
> Looks like after it can't find it in the real time database it does
> several SQL lookups, then:
>
> - 10/30/2009 08:58:47.412 CCM|dBProcs::fail to get
> callmanagerGroupEntry template, GUID =
> - 10/30/2009 08:58:47.412 CCM|dBProcs - Fail to station registration
> profile by device name, deviceName=AN1DA2EA3B63FFF
>
> So here I tried changing the CM Group in CCM to something else and
> then also back to the original setting, neither operation helped. Not
> sure what else to do from that error.
>
> I'm going to make a visit over to the gateway and review the config
> and see if there is anything I can gather from debugs. Wish I had
> remote access configured on it now :)
>
>
>
> On Thu, Oct 29, 2009 at 2:19 PM, Ryan Ratliff <rratliff at cisco.com> wrote:
>>
>> A device not being in the database is only one reason why it won't
>> register.
>>  That TSP error is basically a transient device connection, so I'd
>> recommend
>> getting detailed CCM traces that cover one of the errors and see what is
>> going on related to that device.
>>
>> -Ryan
>>
>
>



-- 
Ed Leatherman