[cisco-voip] VG202/204 registration errors

[Ryan Ratliff]

Confirmed in CUCM 7.12.10000-16 that when the SCCP VG202 is created  
the virtual port is added to the db.

If your VG is not SCCP then I'd highly recommend removing any sccp  
related commands that are configured on it.

-Ryan

On Oct 29, 2009, at 12:18 PM, Ryan Ratliff wrote:

That's the virtual port used for resetting the device, and should be  
in the database (run sql select name from device where name like  
'%FFF').

On the VG224s you can disable this port by removing the 'ccm-manager  
sccp' command (I think).

What version of CUCM are you running and what protocol are you using  
for the VG202?

-Ryan

On Oct 29, 2009, at 12:06 PM, Ed Leatherman wrote:

Hello all,

Curious if anyone has some of the new VG202's in production.. i'm
seeing registration attempts from these devices that doesn't make
sense to me.

example:
%CCM_CALLMANAGER-CALLMANAGER-3-TspError: Error in TSP. Port
IsoEthPort:0 Port DSL:0 Name of Device:AN1DA2EA3B63FFF App ID:Cisco
CallManager Cluster ID:OWP-PUB-Cluster Node ID:OWP-SUB-A

The device name here is AN1DA2EA3B63FFF ... I have in call manager
AN1DA2EA3B63000 and 001 for the two ports on the VG (which register as
normal), but no FFF. What is it trying to register here, there are
only 2 ports?

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

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