Hometronics-SF Posted April 30, 2019 Author Share Posted April 30, 2019 Sorry such a late reply to this, it ended up being an update that fixed it from Control4. everything has been working fine since, thanks for all the help Quote Link to comment Share on other sites More sharing options...
Peter69 Posted October 20, 2019 Share Posted October 20, 2019 On 12/3/2018 at 8:11 AM, Gary Leeds UK said: Just Check our Intercom App and Our DS2 (Mini) is also off line Too. All TS and Mobile Devices are working Tried the Reset on Gateway - Nothing Just did a Restart on DS2 from HE - Back online How do you restart the DS2 from HE? Quote Link to comment Share on other sites More sharing options...
Gary Leeds UK Posted October 21, 2019 Share Posted October 21, 2019 Go into Action Tab and press Restart Quote Link to comment Share on other sites More sharing options...
C4TTRS Posted March 19, 2020 Share Posted March 19, 2020 On 12/5/2018 at 6:10 PM, thegreatheed said: Identifying them by IP address certainly wasn't the fix, so, since you haven't found the culprit, you can't rule anything out. The FACT remains that issues with SDDP are usually caused by the network. FACT. I'm not troubleshooting your network or your system, it's a FACT that issues with SDDP (which is a multicast-dependent protocol) are usually caused by the network. If you knew that, you would have known that identifying a device by IP address isn't a fix, it's a bandaid for network issues. And just because your Pakedge gear didn't change, that doesn't rule out a network issue. So, keep ruling out things you haven't ruled out. I don't care, it's not my project. Or, you could take someone's comment and try to use it and not dismiss it. Reset your POE switch and everything will work. Yes its a symptom of a network error at the POE switch Quote Link to comment Share on other sites More sharing options...
kraney Posted September 9, 2021 Share Posted September 9, 2021 I had a similar problem where often the intercoms were not ready, but then sometimes they would just magically work. What I found is that the sipproxy service was enabled on my director. Sipproxy and freeswitch both try to listen on the same TCP & UDP port number. Whichever one grabs it first at boot time works, and the other is broken. For the new communications agent, you want freeswitch, so make sure sipproxy is disabled. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.