Skip to main content

Verifying DTMF Output Switching Functionality

Symptomes

The issue occurs when using a DTMF action to switch outputs (for switching doors, barriers, etc.) during a call. The expected output switching does not happen, or it happens inconsistently.

The output switch may fail if the intercoms are unavailable or busy, the called number is blacklisted, the specific action (calling a script, setting a tag, etc.) configured to be executed after the DTMF action may have failed, and/or network instability may also contribute to the problem.

How to Reproduce

(Optional section)

StapStep 1:
Go
Opento the CoCoSdashboard Loggingand add a control panel for intercom stations if there is not yet one present.

image.pngimage.png
StapStep 1:2:
Enter
Openthe Opennumber you want to make a logbooktest itemcall to, and click the "dial" button.

image.pngStep 3:

During the conversation press the DTMF digit that should preform the configured action.


The configured DTMF action should now be executed.

Application

(Optional section)

Describe in which application / in what way the problem occurred. The issue was noticed when a script was created to open a door using an IO device controlled by webhooks.

Cause

Issues with DTMF actions are likely caused by one or more of the following:

  • Intercom unavailability: If the intercom(s) involved in the action are unavailable or busy, the output switching may not occur since a call from this intercom can not be made.

  • Called number is blacklisted: If an allow list is specified for the DTMF action, the called number may not be allowed to preform the action when they press the DTMF digit.
  • Script, tag, or other action failed: If an action is configured for the DTMF action, this action may have failed.

Solution / How To

    1.
  1. Check the call history:history

    2. Verifythat
    Navigate to "Intercom / Call History"

    image.png

    Here you can see a list of all calls are being started from intercom(s), and are successfull.

  2. Checkon the callsystem.

    logs:

     

    If your issue is with a specific intercom or location, you might want to filter on this specific location or intercom (number).

    		3.

    image.png

    Open one or more of the calls towhere checkyou might suspect the logsissue foris anypresent.
    In issues,this and opencase the valueconfigured historyDTMF does not work when calling a specific number.

     

     

    image.png

    First to check if the required DTMF digitaction was send by the called partynumber /we caller.will (See also article ...)

  3. Monitoropen the intercomvalue status:history Seeand articlesearch for a message like the following: "event(press).digit(1)"

     

    When this message is not present, this would mean that the user (the called number) did not press a DTMF digit during the call, or the DTMF was pressed but not received due to a network issue.

    		4.

    image.png

    After that we will check the logbook for any logs that would indicate an issue.

     

    In this case I was able to find a log message that indicated that the DTMF action was denied for the called number

    (meaning the called number was not found in the configured allow list for the DTMF action)..

    		5.

    image.png

    2. Check the configured action:action

    1. For
      2. scripttag

      Navigate to "System / Devices" or "Intercom / Intercom Stations" and open the intercom station where the DTMF action checkshould articlebe ...configured.

    2. For
      		3.

      image.png

      Open the DTMF action checkconfigured articlefor ...this intercom station.

      image.png

      image.png

      References

      Describe where to find external answers or extra informations

    Back to top