[cisco-voip] VG202/204 registration errors

[Fuermann, Jason]

I doubt you need to visit the device if everything else is working properly and you're just getting this transient connection from the FFF port. Have you tried removing it from CM and re-adding it? My thought is that the GW insertion somehow messed up. We experienced a similar issue caused by bug CSCsw43113 because we inserted our GW's via BAT, although that should be resolved in your version. Just something to check.


-----Original Message----- 
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Friday, October 30, 2009 9:35 AM
To: Ed Leatherman
Cc: Cisco VOIP
Subject: Re: [cisco-voip] VG202/204 registration errors

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
>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip