[cisco-voip] VG202/204 registration errors

[Ed Leatherman]

Ahh thanks for clearing that up.

It's CCM 6.1.4, and they are SCCP setup with autoconfiguration. the
tech set them in in CCM admin as gateway devices.

I do see this in the database using the run sql cmd. shouldn't it just
register then or did we miss something?

On Thu, Oct 29, 2009 at 12:36 PM, Nick Matthews <matthnick at gmail.com> wrote:
> The FFF port is the SCCP auto-registration 'port'.  This is the device
> that gets reset that resets the whole device and is responsible for
> the SCCP autoconfiguration. If you don't want this port, you can
> remove the ccm sccp configuration.  It's on by default on the
> VG202/204 routers, which is probably the only reason you haven't seen
> it before.
>
> -nick
>
> On Thu, Oct 29, 2009 at 12:06 PM, Ed Leatherman <ealeatherman at gmail.com> 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
>>
>



-- 
Ed Leatherman