Advanced Search
Search Results
13 total results found
Verifying DTMF Output Switching Functionality
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...
Verifying Script Functionality
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 ...
Verifying Tag Functionality
[ DRAFT EDITION ]
MOXA ioLogik Output control via Script
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: ...
How-to configure DTMF action
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...
Verifying Trigger Functionality
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. ...
Calls That Stay Open After Intercom Hang-Up
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....
Troubleshooting TLS Transport Registration Issues in Intercom
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...
SIP Intercom Appears Registered But Is Not Available in CoCoS
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...
Analyzing and Resolving Call Failures
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...
How-to configure outgoing call routes
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...
Troubleshooting Call Recording Not Started Or Shown
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...
MOXA ioLogik Output control
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...