Sometimes people just key up for no reason, others key up if they are on a repeater that has that TG as a PTT TG and not static.

Also try another browser other than IE. The OS2 does not care much for it. I use Brave, FF or Chrome and it works. Sometimes a page refresh wakes it up too.

Hmmm, if you have the proper NTP server name and valid DNS addresses...other than the gateway address (which I believe must be your router), your OS2 should be on the internet just fine and your OS2 should get time and hitting the sync now should work.

If you go to the OS2 settings tab you can do a manual sync. I use us.pool.ntp.org and it works fine. If it cant resolve the URL then I would suspect you may not have the proper DNS server listed in the OS2 as well. Do you have your DNS set to something like 8.8.8.8??

Makes it somewhat confusing to see UTC from the OS2 and the rest of my devices show local time.

Will have to make do with that small inconvenience. Would be nice to see an option in a future release to allow the user to decide though

The OS2 local logs show EDT as they should and the time is properly set via NTP So why is my syslog server showing EDT+4 (UTC) timestamps? I dont see a way to change what the OS2 sends to the server as far as timestamping goes BTW all my other logs from my routers and raspberry pi's show local time ...

Good luck with that one. I sent the word out on FB and also email. Either they know about it and wont say and maybe working on it or...just ignoring it.

I dont have any problems with the OS2 on TGIF or XLX.

What is annoying as well is that since there is a private and a group call...there are times where my Anytone shows up with the "missed call" pop up.

That has me wondering why changing the SSID password would cause the OS2 to not connect. Provided of course you did change the PW on the OS2, it should still connect. By any chance do you have any special characters in your password? Not that this could be the reason but its been brought up that iph...

OK. Have been working with some of the BM folks to see why they are sending more than one message for the caller ID information. Seems they are fragmenting the data into 3 messages instead of one. I am using the OS2 now in static mode and it appears to be ok. Just the web session disconnects periodi...