[asterisk-bugs] [JIRA] (DAHTOOL-66) Congestion tone for Australia not correct in zonedata.c

[armeniki (JIRA)]

     [ https://issues.asterisk.org/jira/browse/DAHTOOL-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

armeniki updated DAHTOOL-66:
----------------------------

    Description: 
Hi there,

At approximately Line 66 of the zonedata.c file, the Congestion tone specifications for Australia have the correct cadence in place however the frequencies and levels are incorrect.  The Congestion tone in Australia must be reduced by 10 to 15 dB at every other cadence and the frequencies are always the same for both at 425.  Otherwise, it is very similar to the engaged/busy signal and it is very difficult/impossible to distinguish when a line is busy/engaged or out of service, etc.

  was:
Hi there,

At approximately Line 66 of the zonedata.c file, the Congestion tone specifications for Australia have the correct frequencies and cadence in place however the levels are incorrect.  The Congestion tone in Australia must be reduced by 10 to 15 dB at every other cadence.  Otherwise, it is very similar to the engaged/busy signal.

As such, it very difficult/impossible to distinguish when a line is busy/engaged or out of service, etc.


> Congestion tone for Australia not correct in zonedata.c
> -------------------------------------------------------
>
>                 Key: DAHTOOL-66
>                 URL: https://issues.asterisk.org/jira/browse/DAHTOOL-66
>             Project: DAHDI-Tools
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 2.6.2
>            Reporter: armeniki
>            Assignee: Russ Meyerriecks
>
> Hi there,
> At approximately Line 66 of the zonedata.c file, the Congestion tone specifications for Australia have the correct cadence in place however the frequencies and levels are incorrect.  The Congestion tone in Australia must be reduced by 10 to 15 dB at every other cadence and the frequencies are always the same for both at 425.  Otherwise, it is very similar to the engaged/busy signal and it is very difficult/impossible to distinguish when a line is busy/engaged or out of service, etc.



--
This message was sent by Atlassian JIRA
(v6.2#6252)