Search Results

Symptomes During a call, pressing the 1 key (or any other configured key) on the receiving phone or intercom does not result in the expected behaviour, such as opening a door or gate. Details The issue occurs when using a DTMF action to switch outputs (such...

Symptoms A script fails to execute if there are syntax errors or runtime issues, such as missing variables or incorrect logic. It can also fail if the script is not properly triggered (e.g., a failure in a preceding action like a trigger or DTMF input), the ...

Please use the custom device type "Moxa ioLogik" instead. Introduction This use case describes how to configure a (CoCoS) script for controlling outputs on a MOXA ioLogik device. Step by step implementation To configure this use case, follow these steps: ...

Description This guide describes how to configure a DTMF (Dual-Tone Multi-Frequency) action on an intercom station. A DTMF action allows the system to respond to specific keypad input from the called party—for example, to trigger a script such as opening a do...

Symptoms Triggers are used to automate actions like opening a door or sending a notification — when they don’t work, it’s often due to incorrect conditions or misconfigurations. A trigger does not activate even when the expected conditions are met. ...

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 or disconnected (on requist) Related symptoms The call history in CoCoS still shows an active conversation....

Symptoms The intercom is correctly configured but fails to register with the server. Related symptoms The intercom displays an error indicating it is unable to register. (In the intercom and in CoCoS) Calls to the intercom fail for the following re...

Symptoms Your intercom looks like it’s working and says it’s registered, but in CoCoS it still shows as error, disconnected, or no status. Related symptoms You try to call the intercom, but the call fails. Calls to the intercom fail for the following...

Symptoms Calls made from an intercom (or a group of intercoms) consistently fail, or a call that should have succeeded is marked as "Not Answered," "Failed," or "Aborted." Related symptoms Call status is not marked as "Answered." Call fails or is n...

Question or Case description To make outbound (external) calls through your PBX system, you need to configure outgoing call rules. These rules define which calls should go out (for example, calls to 10-digit numbers) and which trunk (connection to the outside...

Symptoms Call recordings are enabled, but they do not appear in the call history. Related symptoms Call recordings not started. Call recordings started, but they do not show up in the call history after the call ends. Details This issue occurs when c...

Question or Case description This article describes how to configure and control outputs on Moxa ioLogik devices using the new device connector in CoCoS.The connector replaces the previous script-based method, providing a more user-friendly and reliable way t...

Symptoms When starting a call, especially from a button, the call appears to connect, but: The person who receives the call hears nothing from the person who started it. The person who initiates the call hears nothing at all. The conversation w...

Description This article explains how to start, stop, and download a packet capture within the CoCoS platform.A packet capture allows you to record network traffic so you can analyze protocols such as SIP and RTP. Packet captures are often used to diagnose ca...