Mailing List Archive

Cisco ATA Devices need reset
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.

Thanks in advance. Call Manager version 11.5.

Lisa


[Lisa Notarianni Telecom Engineer]
Re: Cisco ATA Devices need reset [ In reply to ]
Yep have seen the same thing over the years over many versions and all ATAs. Wish they were PoE!


Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch@heliontechnologies.com
From: cisco-voip <cisco-voip-bounces@puck.nether.net> On Behalf Of Lisa Notarianni
Sent: Tuesday, September 18, 2018 3:28 PM
To: cisco-voip voyp list <cisco-voip@puck.nether.net>
Subject: [cisco-voip] Cisco ATA Devices need reset

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.

Thanks in advance. Call Manager version 11.5.

Lisa


[Lisa Notarianni Telecom Engineer]
Re: Cisco ATA Devices need reset [ In reply to ]
> On 18 Sep 2018, at 20:27, Lisa Notarianni <lisa.notarianni@scranton.edu> 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:gary@lboro.ac.uk o
| https://www.osx.ninja/pubkey.txt |
\r----------------------------------------------d-/
Re: Cisco ATA Devices need reset [ In reply to ]
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.

Thanks,

Ryan

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 <lisa.notarianni@scranton.edu<mailto:lisa.notarianni@scranton.edu>> 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:gary@lboro.ac.uk o
| https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.osx.ninja%2Fpubkey.txt&amp;data=02%7C01%7C%7C90cd93946e1a4a80ad4408d61e0b4186%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729431018180903&amp;sdata=SkkPb4INXXst72pj5pzQp%2FeQkwuAJhuxtHkUa1a%2BBvk%3D&amp;reserved=0 |
\r----------------------------------------------d-/

_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7C90cd93946e1a4a80ad4408d61e0b4186%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729431018180903&amp;sdata=C8uQuX%2FMX%2Bk1aZ%2F7floI7dn9eVzE6yTE3wgxhWsKPAM%3D&amp;reserved=0
Re: Cisco ATA Devices need reset [ In reply to ]
On the ATA-186, any time we did maintenance work on the UCM or CM service. They are pretty weak sauce and seem to just give up trying to operate.

You don't have to physically go to these though, I just go to the admin page and touch something like the TFTP config line or whatever and it will eventually come back to life and re-register itself.

Have not had this problem with the ATA-187 or ATA-190.

We DO have this problem with the VG320 and VG340, SCCP- they'll fall off due to a network outage and then never bother to come back and re-register no matter how I configure the "retry" parameter.

Adam Pawlowski
SUNAB
Re: Cisco ATA Devices need reset [ In reply to ]
For our VG202 and VG204s we are using 802.3at to 12V adapters (
https://www.amazon.com/GAT-USBC-Convert-802-3at-Macbook-Converts/dp/B07D7HYWQF/ref=sr_1_14?ie=UTF8&qid=1537393314&sr=8-14&keywords=802.3at%2B12V&th=1)
to convert them to PoE. This problem happens pretty infrequently but now we
have an easy solution. Unfortunately the barrel jack is the wrong pitch so
we have to hack the cables apart and solder the right barrel together. But
at least that's only painful one time.

On Wed, Sep 19, 2018 at 2:13 PM Pawlowski, Adam <ajp26@buffalo.edu> wrote:

> On the ATA-186, any time we did maintenance work on the UCM or CM service.
> They are pretty weak sauce and seem to just give up trying to operate.
>
>
>
> You don’t have to physically go to these though, I just go to the admin
> page and touch something like the TFTP config line or whatever and it will
> eventually come back to life and re-register itself.
>
>
>
> Have not had this problem with the ATA-187 or ATA-190.
>
>
>
> We DO have this problem with the VG320 and VG340, SCCP- they’ll fall off
> due to a network outage and then never bother to come back and re-register
> no matter how I configure the “retry” parameter.
>
>
>
> Adam Pawlowski
>
> SUNAB
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
--

--
Hunter Fuller
Network Engineer
VBH Annex B-5
+1 256 824 5331

Office of Information Technology
The University of Alabama in Huntsville
Systems and Infrastructure
Re: Cisco ATA Devices need reset [ In reply to ]
Hey Ryan - sorry to grave dig.

Can you remember the reference for the common phone profile by chance? We
have 50 or so ATA's that we will need to replace with 191's in the meantime
i'd like to try the common phone profile change.

Was it just the name of the common profile or is it should I change the
name along with some irrelevant setting?

Cheers

Nick





On Wed, Sep 19, 2018 at 2:10 AM Ryan Huff <ryanhuff@outlook.com> wrote:

> 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.
>
> Thanks,
>
> Ryan
>
> On Sep 19, 2018, at 04:38, Gary Parker <G.J.Parker@lboro.ac.uk> wrote:
>
>
>
> On 18 Sep 2018, at 20:27, Lisa Notarianni <lisa.notarianni@scranton.edu>
> 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 <+441509635635> sip:gary@lboro.ac.uk o
> |
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.osx.ninja%2Fpubkey.txt&amp;data=02%7C01%7C%7C90cd93946e1a4a80ad4408d61e0b4186%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729431018180903&amp;sdata=SkkPb4INXXst72pj5pzQp%2FeQkwuAJhuxtHkUa1a%2BBvk%3D&amp;reserved=0
> |
> \r----------------------------------------------d-/
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7C90cd93946e1a4a80ad4408d61e0b4186%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729431018180903&amp;sdata=C8uQuX%2FMX%2Bk1aZ%2F7floI7dn9eVzE6yTE3wgxhWsKPAM%3D&amp;reserved=0
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>


--
- Nick