[asterisk-bugs] [Asterisk 0011354]: Can not change Call-Waiting tone duration and frequency
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Apr 2 18:27:49 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11354
======================================================================
Reported By: cahen
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11354
Category: Channels/chan_zap
Reproducibility: always
Severity: minor
Priority: normal
Status: confirmed
Asterisk Version: 1.4.15
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 11-22-2007 20:09 CST
Last Modified: 04-02-2008 18:27 CDT
======================================================================
Summary: Can not change Call-Waiting tone duration and
frequency
Description:
Our users reports that the call-waiting tone on analog phones connected to
Zaptel hardware (TDM400 & TDM2400) is too disturbing.
I tryed to change it's duration in indications.conf AND in zonedata.c
(recompiled, etc...), but it doesn't change anything (changing other tones,
ie dialtone works fine!).
Basically, whatever is configured in those 2 files, the CWT is 300ms long
at 440Hz, and is repeated every 3 or 4 seconds! (it seems that a CWT is
emitted at the beginning of each ring-back tone sent to the caller)
Another issue is that when a call is bridged between 2 local extensions,
both parties hear the CWT, so no one knows who is concerned
======================================================================
----------------------------------------------------------------------
qwell - 04-02-08 18:27
----------------------------------------------------------------------
Here is an ugly hack that will shorten the beep, and also delay longer (in
theory) between beeps.
Note the 2400 (now 1200) - this is (simplified) beep ms * 8, and the 10000
(now 20000) at the top is the delay between beeps...in theory.
It's going to take a great deal of effort to rework how this all is
generated, and to be honest, I don't see that being done in the near term.
I think it might be appropriate to suspend this issue (and of course leave
the patch and this explanation up). Thoughts?
Issue History
Date Modified Username Field Change
======================================================================
04-02-08 18:27 qwell Note Added: 0084969
======================================================================
More information about the asterisk-bugs
mailing list