[cisco-voip] call manager publisher error

Jason Aarons (US) jason.aarons at us.didata.com
Tue Nov 23 18:53:31 EST 2010


It starts with a AN which means Analog, it’s registering to CallManager.

If this is a ATA there are two lines on a ATA, is the second port configured in CallManager?

If this is a VG224/SCCP are all 24 ports configured in CallManager, the ports will try to auto-register filling up the log file. There was a IOS bug, newer IOS version for VG224 might fix.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Countryman, Edward
Sent: Tuesday, November 23, 2010 2:41 PM
To: Arnold Lesar; VoIPgroup
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

[cid:image001.jpg at 01CB8B3F.B92F0CA0]


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






-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101123/f3d71432/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 9536 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101123/f3d71432/attachment.jpg>


More information about the cisco-voip mailing list