# RTCM Remote Clients Stopped Working **URL:** \ **Category:** AllStarLink\ **Created:** [January 30, 2021, 4:38pm UTC](https://community.allstarlink.org/t/rtcm-remote-clients-stopped-working/18199 "2021-01-30T16:38:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Kc7mrq1](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kc7mrq1/32/471_2.png) [@Kc7mrq1](https://community.allstarlink.org/u/Kc7mrq1)\ **Post date:** [January 30, 2021, 4:38pm UTC](https://community.allstarlink.org/t/rtcm-remote-clients-stopped-working/18199/1 "2021-01-30T16:38:30Z")
A voter system recently stopped stopped working and no changes to the master server occurred. The system has been up for a couple years. Here’s the steps I’ve taken so far and am looking for any assistance on what to check next. Background: Three through-hole RTCM system. All three boards have a Garmin 18 GPS. Two boards are at remote locations using locally provided internet. Recently, the internet provider changed out gear, but the nothing changed with static IP assigned to the remote sites. Troubleshooting steps taken: 1. logged into the master server and ran “asterisk -r” . I verified I can voter ping each remote board. latency has not changed and are low numbers. 2. Ran voter display and only audio shows up on the master when a radio is keyed down. Both boards are showing up with the master during the voter display cycle. 3. Verified port 667 is open in the router. 4. Telenet into both remote boards and confirmed connect is 1 and gps lock is 1 via status 98. 5. Tried different debug levels (1, 32) to see if there were any errors with GPS or in general. 6. Ran option 97 and confirmed each board is receiving a signal when a radio is keyed down. 7. A local ham went to one of the sites and confirmed the RX led on the RTCM sees a signal. (flashing without CTCSS and solid with CTCSS). The CTCSS appears to be working. I am not sure what to check at this point and am hoping someone can recommend the next steps. Thank you, Corey KC7MRQ ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [January 30, 2021, 5:07pm UTC](https://community.allstarlink.org/t/rtcm-remote-clients-stopped-working/18199/2 "2021-01-30T17:07:30Z")
Take a look at this topic. > [@Your VOTER/RTCM May Have Broken Itself on 01/01/21 00:01](https://community.allstarlink.org/t/your-voter-rtcm-may-have-broken-itself-on-01-01-21-00-01/18031): > > Well, I found this (by accident) about a month ago, which scared the hell out of me: [https://www.microchip.com/forums/m653169.aspx](https://www.microchip.com/forums/m653169.aspx) So, I did some testing/compiling to fast-forward time, and watch how it behaved when time rolled over. Apparently, my testing wasn’t very good, because in my tests time rolled over fine from 12/31/2020 to 01/01/2021. If you go look at the time in your VOTER/RTCM right now, it is going to be a mess (98 - status or debug 32), and if you do a voter debug level 3 in … There is new firmware available from > **[RTCMFWShare](https://www.dropbox.com/sh/hkfjf25emlg69y1/AAB2fwh63QtYDu7YbuCglCwla?dl=0)** > > Shared with Dropbox ---
**Author:** ![Kc7mrq1](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kc7mrq1/32/471_2.png) [@Kc7mrq1](https://community.allstarlink.org/u/Kc7mrq1)\ **Post date:** [January 31, 2021, 2:49am UTC](https://community.allstarlink.org/t/rtcm-remote-clients-stopped-working/18199/3 "2021-01-31T02:49:38Z")
Tim, Thank you for pointing me in the right direction. I will implement the new firmware shortly. Have a great day, Corey ---
**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\ **Post date:** [February 3, 2021, 2:49am UTC](https://community.allstarlink.org/t/rtcm-remote-clients-stopped-working/18199/4 "2021-02-03T02:49:42Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.