[cisco-voip] untraceable connection attempt?

[Lelio Fulgenzi]

First time I think I've ever seen this. Especially with no MAC or IP addr.

Only one alert.

But we've recently started allowing Jabber connections from our data VLANS.

I'd hate for it to be the beginning of something larger.

Sent from my iPhone

On Dec 19, 2017, at 11:35 PM, Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:

Could also be network connectivity among a lot of things but more often than not, bouncing CM service seems to fix if this is a recurring alarm. If it’s a one time alarm you’ve not seen before; likely legitimately referring to a device.

If you’ve recently added any new devices, check network connectivity / verify they are all registered. Could also be a bad device that is no longer working but still attempting a registration ... sort of.

-Ryan

On Dec 19, 2017, at 11:22 PM, Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>> wrote:

Sounds like you should schedule a bounce of the CM service for this node.

Have a read here for more detail: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/8_x/ccmalarms851.html

Thanks,

Ryan

On Dec 19, 2017, at 11:11 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

An endpoint attempted to register but did not complete registration
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171220/2a846adc/attachment.html>