Rasperry Pi stuck on login-screen / not booting
Symptoms
When making a call between intercoms (usually from a substation to a main station), the call remains open after one intercom has hung up.
Related symptoms
-
The call history in CoCoS still shows an active conversation.
-
The other intercom displays an "in conversation" screen, or its LED remains active after the call ends.
Details
The issue can be recognized when, after a call is hung up, the second intercom continues to show an "in conversation" screen and/or icon. The LED indicator may also remain lit. Additionally, the call history in CoCoS will show the conversation as still active, even though the call was already ended from one end.
Cause
This issue is caused by a misconfiguration of NAT (Network Address Translation). Specifically, the "External IP-Address / Hostname" field is incorrectly set on the intercom server, causing the intercoms to attempt to communicate with an invalid or nonexistent endpoint. This leads to the call being left open after hang-up.
Solution / Resolution / How To
Describe how to fix it, how to validate an observation or describe how to configure a specific case. Only use one title, solution, resolution or HowTo
|
Navigate to "system / devices" |
|
|
Find and open the intercom server device where the intercom(s) in question are located. |
|
|
Under the "Connectivity" section, check if the "External IP-Address / Hostname" is specified.
If an address is listed:
|
|
|
If the intercom is behind NAT, disable the "Device behind NAT" option, unless NAT should be used.
(This ensures proper communication between intercoms and prevents the call from staying open after hang-up.) |