Back in they day with the older 186 & 187s, there was this issue where the ATA would lose registration if the second/other port was not configured with a DN.
If that is the case, try and configure the other port and see if that improves your experience.
It looks like someone has reported a similar ATA issue for the ATA190, but not much detail included with this bug report: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk29369/?rfs=iqvred
Also, and I can’t recall the bug kit number, there used to be this issue with ATAs using the default Common Phone Profile setting; if you changed it to anything but whatever the default was, it improved the condition.
On Sep 19, 2018, at 04:38, Gary Parker <G.J.Parker@lboro.ac.uk<mailto:G.J.Parker@lboro.ac.uk>> wrote:
On 18 Sep 2018, at 20:27, Lisa Notarianni <firstname.lastname@example.org<mailto:email@example.com>> wrote:
Does anyone else out there ever have to do a hard reset on Cisco ATA devices because all of a sudden the ports are not registered in Call Manager? We have a few buildings this happens often in. We have to walk to the device and reset it. This happens for any type of ATA we use; 186, 187 or 190.
Yup, we’re running 186s and 187s and had this constantly until I put a scheduled job on on the callmanager to restart all of them every Sunday morning at 3am. The weekly restart sorted the problem.
/-Gary Parker----------------------------------f--\ | Unified Communications Service Manager |
n Loughborough University, IT Services | | tel:+441509635635 sip:firstname.lastname@example.org o
| https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.osx.ninja%2Fpubkey.txt&data=02%7C01%7C%7C90cd93946e1a4a80ad4408d61e0b4186%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729431018180903&sdata=SkkPb4INXXst72pj5pzQp%2FeQkwuAJhuxtHkUa1a%2BBvk%3D&reserved=0 |
cisco-voip mailing list