[cisco-voip] call manager publisher error

[Arnold Lesar]

dear edward,

thanks for your advice, i will check on my voice gateway, 
maybe some of my VG not configured completely.
 
GBU


Regards,


Arnold Samuel Lesar


------------------------------------------------------
Note: This message was created by ARNOLD SAMUEL LESAR.
------------------------------------------------------


--------------------------------------------------------------------------
--------------------------------------------------------------------------
PT. PELITA RELIANCE INTERNATIONAL
Eka Hospital BSD City, Tangerang 
Address : CBD Lot IX, BSD City, Tangerang 
Phone : (+62-21) 256 555 55 
Fax : (+62-21) 256 555 44 
--------------------------------------------------------------------------
--------------------------------------------------------------------------




________________________________
From: "Countryman, Edward" <Edward.Countryman at provena.org>
To: Arnold Lesar <arnoldlesar at yahoo.co.uk>; VoIPgroup 
<cisco-voip at puck.nether.net>
Sent: Wed, 24 November, 2010 2:40:41
Subject: RE: [cisco-voip] call manager publisher error


This is caused because you have a device that is looking to register with your 
CCM that is not configured in your CCM.  It appears to be an analog device so it 
could either be an ATA or possibly an SCCP configured port on a VG224.  Either 
configure CCM to add the device or shut it down and the messages will stop.  

 
From:cisco-voip-bounces at puck.nether.net 
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Arnold Lesar
Sent: Monday, November 22, 2010 10:16 PM
To: VoIPgroup
Subject: [cisco-voip] call manager publisher error
 
 
 
dear all,

i have a problem with this error,

Error: DeviceTransientConnection - Transient connection attempt.
  Connecting Port: 2000
  Device name [Optional].: AN23335F0031411
  Device IP address.: 172.31.38.22
  Device type. [Optional]: 30027
  Reason Code [Optional].: 1
  App ID: Cisco CallManager
  Cluster ID: StandAloneCluster
  Node ID: 172.31.10.2
Explanation: A connection was established and 
immediately dropped before completing registration. 
Incomplete registration may indicate a device is 
rehoming in the middle of registration. 
The alarm could also indicate a device 
misconfiguration, database error, 
or an illegal/unknown device trying to attempt a 
connection.
Recommended Action: 
No action is required if this event was 
issued as a result of a normal device rehome.. 

does anyone knows why this issued happened?and how to resolved this problem?

thanks.

Regards,
 
Arnold Samuel Lesar 


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101128/ee2f90e4/attachment.html>