[Home]

Summary:ASTERISK-09377: [patch]Asterisk can't establish dialtone after brief hangup
Reporter:Mark MacVicar (mmacvicar)Labels:
Date Opened:2007-05-03 14:08:33Date Closed:2008-06-07 13:54:03
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_zap
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) 20070926__bug9660.diff.txt
( 1) 9660.patch.txt
( 2) zap_zt_set_hook_bug.diff
( 3) zaptel-base-c_patch_1_4_rev3121
Description:Asterisk can't establish dialtone after brief hangup

When I press the hook-switch (i.e., receiver button) and then let go to make a new call, the phone doesn't establish dialtone unless I hold it down for for 4-5 seconds.

Reproducible Steps:
1. Pick up handset and establish dialtone.
2. Press the hook-switch for 1-3 seconds and let go

After letting go of the hookswitch, the sound on the line is silent for a moment then a computerized squeal is heard briefly and silence continues. The asterisk console displays the following messages when "core set verbose 10":
--------------------
   -- Starting simple switch on 'Zap/7-1'
   -- Hungup 'Zap/7-1'
[May  3 11:31:45] WARNING[2241]: chan_zap.c:1616 zt_set_hook: zt hook failed: Device or resource busy
--------------------

We are using analog Astra Telecom 480e phones connected through internal wiring to TDM400P cards in our asterisk server.



****** ADDITIONAL INFORMATION ******

This is just an irritation more than anything else.  Please let me know if I can provide more information.
Comments:By: Jason Parker (jparker) 2007-05-03 15:05:16

What version of zaptel is this with?
By: Mark MacVicar (mmacvicar) 2007-05-03 15:19:47

The latest release Zaptel 1.4.2.1, and this has happened with zaptel 1.4.0
By: Olle Johansson (oej) 2007-05-04 08:26:18

...why is this reported in the SIP category? :-)
By: Mark MacVicar (mmacvicar) 2007-05-07 12:35:32

I reported it as SIP because I noticed the problem when we switched over to SIP from IAX. We also upgraded from Asterisk ~1.2(exact version unknown) to 1.4. If it's more of a zaptel driver problem I apologize for the confusion.
By: marco (marco) 2007-07-06 09:29:49

I can confirme:
Card: TDM 400P
Asterisk version : 1.4.0
Zaptel version: 1.4.1

the same problem here,but the probelm seems to randomly reproducible:
   -- Starting simple switch on 'Zap/2-1'
   -- Hungup 'Zap/2-1'
   -- Starting simple switch on 'Zap/2-1'
   -- Hungup 'Zap/2-1'
   -- Starting simple switch on 'Zap/2-1'
   -- Hungup 'Zap/2-1'
[Jul  6 16:17:06] WARNING[8649]: chan_zap.c:1642 zt_set_hook: zt hook failed: Device or resource busy
   -- Starting simple switch on 'Zap/2-1'
   -- Hungup 'Zap/2-1'

For me it is reproducible when i press the hook very quickly after hanging up.
It's like if asterisk detect the hangup hook with a small delay and then had some problem to establish dialtone until you give it the time to do so(holding it down for for 4-5 seconds).
Sometimes really boring.
By: Arcadiy Ivanov (arcivanov) 2007-07-06 09:56:27

I can attest to having the same thing. The workaround is to hang up, wait to 1 - 1.5 sec or more and then pickup. Basically it might be related to flash functionality (i think you need to pickup within .4 s from the hangup for flash to  occur as opposed to hangup). I'm running stable 1.4 both asterisk and zaptel, updated weekly on Saturday (basically almost most recent stable).


By: Jonathan Hunter (jmhunter) 2007-07-06 16:38:47

Same here.

I'm using a TDM400P with Asterisk 1.4.4.
Zaptel is either 1.4.1 or 1.4.2 (I have both sets of source code around - how can I tell which is running?)

If I pick up the telephone handset, and then hang up & pick the handset up again too quickly, I get the following:

   -- Starting simple switch on 'Zap/3-1'
   -- Hungup 'Zap/3-1'
[Jul  6 22:47:02] WARNING[5398]: chan_zap.c:1616 zt_set_hook: zt hook failed: Device or resource busy
[Jul  6 22:47:05] WARNING[5398]: chan_zap.c:6897 do_monitor: Read failed with -1: Unknown error 500

If I listen straight after picking the handset up again, there are a few seconds of silence and then a 1-second noise I can best describe as similar to a modem trying to train with the other end. At that point it goes silent again, and next time I hang up / pick up it is fine.

Other info of note:

I am using 'UK' tones/zones with my Asterisk setup. Not sure if that affects anything?

I have experimented with the following in zapata.conf (in a failed bid to reduce the time Asterisk needs to differentiate between a hookflash and hangup - the UK standard timings for these are considerably shorter than the USA ones) but this hasn't helped:

debounce=300
flash=200
rxflash=200

(If there is a guide to what these timings actually mean, I'd appreciate being pointed in the right direction - I wasn't sure which settings to actually set in order to achieve my goal.)
By: Brett Bryant (bbryant) 2007-07-11 11:38:53

I uploaded a patch that fixed the issue for me, I'd like to get some feedback from other people as well before I commit it.
By: Mark MacVicar (mmacvicar) 2007-07-11 14:35:45

I added your new code to 1.4.4 chan_zap.c and recompiled, but it didn't seem to have any effect.
By: Jonathan Hunter (jmhunter) 2007-07-11 18:06:16

Thanks bbryant - but I patched my (now 1.4.7.1) installation and it didn't help. I still get an error and no dialtone if I pick up too quickly after hanging up:

[Jul 12 00:19:43] WARNING[2676]: chan_zap.c:1632 zt_set_hook: zt hook failed: Device or resource busy

For the benefit of the archives, to tell what version of zaptel you are running, the following command will do the trick:

# modinfo zaptel | grep ^version
version:        1.4.1
By: Russell Bryant (russell) 2007-07-11 18:45:18

I have attached a second patch which attempts to do the same thing that bbryant was going for.  Give it a try.
By: Mark MacVicar (mmacvicar) 2007-07-11 19:12:04

The second patch seems to do the trick.  I haven't tested it thoroughly, but hangup works well even if only pressed down for an instant. Flash still works good too. I'll let you know if any issues come up.
By: Jonathan Hunter (jmhunter) 2007-07-11 19:19:30

Thanks Russell, the second patch seems to be working for me as well. I'll let you know if I notice any oddities - but it has definitely fixed the reported problem, thank you very much!!
By: Frank Waller (explidous) 2007-07-12 20:29:45

We tried the patch and it at least seems to work to the point that we do not see the "zt hook failed" error message anymore. And phones do not seem to get in an undetermined state that easily anymore. For me this should be included in the next release.
By: Digium Subversion (svnbot) 2007-07-13 13:53:10

Repository: asterisk
Revision: 75052

------------------------------------------------------------------------
r75052 | russell | 2007-07-13 13:53:08 -0500 (Fri, 13 Jul 2007) | 12 lines

(closes issue ASTERISK-9377)
Reported by: mmacvicar
Patches submitted by: bbryant, russell
Tested by: mmacvicar, marco, arcivanov, jmhunter, explidous

When using a TDM400P (and probably other analog cards) there was a chance that
you could hang up and pick the phone back up where it has been long enough to
be not considered a flash hook, but too soon such that the device reports that
it is busy and the person on the phone will only hear silence.  This patch
makes chan_zap more tolerant of this and gives the device a couple of seconds
to succeed so the person on the phone happily gets their dialtone.

------------------------------------------------------------------------
By: Digium Subversion (svnbot) 2007-07-13 13:54:34

Repository: asterisk
Revision: 75053

------------------------------------------------------------------------
r75053 | russell | 2007-07-13 13:54:34 -0500 (Fri, 13 Jul 2007) | 20 lines

Merged revisions 75052 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.2

........
r75052 | russell | 2007-07-13 14:10:00 -0500 (Fri, 13 Jul 2007) | 12 lines

(closes issue ASTERISK-9377)
Reported by: mmacvicar
Patches submitted by: bbryant, russell
Tested by: mmacvicar, marco, arcivanov, jmhunter, explidous

When using a TDM400P (and probably other analog cards) there was a chance that
you could hang up and pick the phone back up where it has been long enough to
be not considered a flash hook, but too soon such that the device reports that
it is busy and the person on the phone will only hear silence.  This patch
makes chan_zap more tolerant of this and gives the device a couple of seconds
to succeed so the person on the phone happily gets their dialtone.

........

------------------------------------------------------------------------
By: Digium Subversion (svnbot) 2007-07-13 14:03:00

Repository: asterisk
Revision: 75054

------------------------------------------------------------------------
r75054 | russell | 2007-07-13 14:02:59 -0500 (Fri, 13 Jul 2007) | 28 lines

Merged revisions 75053 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4

................
r75053 | russell | 2007-07-13 14:11:26 -0500 (Fri, 13 Jul 2007) | 20 lines

Merged revisions 75052 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.2

........
r75052 | russell | 2007-07-13 14:10:00 -0500 (Fri, 13 Jul 2007) | 12 lines

(closes issue ASTERISK-9377)
Reported by: mmacvicar
Patches submitted by: bbryant, russell
Tested by: mmacvicar, marco, arcivanov, jmhunter, explidous

When using a TDM400P (and probably other analog cards) there was a chance that
you could hang up and pick the phone back up where it has been long enough to
be not considered a flash hook, but too soon such that the device reports that
it is busy and the person on the phone will only hear silence.  This patch
makes chan_zap more tolerant of this and gives the device a couple of seconds
to succeed so the person on the phone happily gets their dialtone.

........

................

------------------------------------------------------------------------
By: Russell Bryant (russell) 2007-08-07 12:24:43

The patch that was committed for this broke E&M trunks, so it has been reverted.
By: Digium Subversion (svnbot) 2007-08-07 12:26:32

Repository: asterisk
Revision: 78370

------------------------------------------------------------------------
r78370 | russell | 2007-08-07 12:26:30 -0500 (Tue, 07 Aug 2007) | 4 lines

Revert patch committed for issue ASTERISK-9377.  It broke E&M trunks.
(closes issue ASTERISK-10005)
(closes issue ASTERISK-10009)

------------------------------------------------------------------------
By: Digium Subversion (svnbot) 2007-08-07 12:27:57

Repository: asterisk
Revision: 78371

------------------------------------------------------------------------
r78371 | russell | 2007-08-07 12:27:56 -0500 (Tue, 07 Aug 2007) | 12 lines

Merged revisions 78370 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.2

........
r78370 | russell | 2007-08-07 12:44:04 -0500 (Tue, 07 Aug 2007) | 4 lines

Revert patch committed for issue ASTERISK-9377.  It broke E&M trunks.
(closes issue ASTERISK-10005)
(closes issue ASTERISK-10009)

........

------------------------------------------------------------------------
By: Digium Subversion (svnbot) 2007-08-07 12:28:37

Repository: asterisk
Revision: 78372

------------------------------------------------------------------------
r78372 | russell | 2007-08-07 12:28:36 -0500 (Tue, 07 Aug 2007) | 20 lines

Merged revisions 78371 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4

................
r78371 | russell | 2007-08-07 12:45:30 -0500 (Tue, 07 Aug 2007) | 12 lines

Merged revisions 78370 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.2

........
r78370 | russell | 2007-08-07 12:44:04 -0500 (Tue, 07 Aug 2007) | 4 lines

Revert patch committed for issue ASTERISK-9377.  It broke E&M trunks.
(closes issue ASTERISK-10005)
(closes issue ASTERISK-10009)

........

................

------------------------------------------------------------------------
By: Tilghman Lesher (tilghman) 2007-09-26 14:04:36

New patch uploaded that should fix this issue without causing problems for e&m trunks.
By: Whit Thiele (sirwhit) 2007-10-09 11:41:39

I've been having trouble with e&m lines which could be related to this bug.

Make about 500 outgoing calls then (using ZapBarge) I hear the telco saying that not enough digits have been dialed.

Next and all future calls goes into a fast busy and the e&m trunks are useless until asterisk is restarted.

No errors reported from asterisk.
By: Tilghman Lesher (tilghman) 2007-10-09 11:45:42

SirWhit:  Please report that as a new issue, not attached to this one.
By: meneault (meneault) 2007-11-05 09:07:12.000-0600

If I could have my say... I don't suffer this problem but I may be of some help.
Apparently the problem is only related to zaptel and not asterisk.
I guess you are all using kewlstart signalling on your FXS channels, aren't you?

Ok so the problem lies in two things:
- the flash mechanism which by default is 1250 ms (so an onhook event would go unoticed by zaptel if you switch off-hook on-hook off-hook too fast), you can override this setting under zapata.conf with rxflash.
So unless you change this setting you would have to wait for more than 1 sec before attempting a new off-hook sequence.

- And if you are using kewlstart signalling you would have to wait 800 msec more. And this is due to a bug of zaptel... When asterisk makes its ioctl (ZT_HOOK ZT_ONHOOK) the driver is told to drop the battery on the line during 500ms at least and then wait 300ms more to be idle...And even when your TE is already on-hook (this is the bug).

So we have something like that:
- take off-hook (wait debounce= 600 ms)
- goes back on-hook (wait rxflash = 1250ms)
=> gets noticed by asterisk (some more ms)
=> zt_hangup called => ioctl ZT_HOOK ZT_ONHOOK
=> kewl start is made (800ms to wait)
                          (kewlstart shouldn't be made here....)
if you try to go off-hook when in kewlstart you get the busy message!

So two things:
- try to lower the value of rxflash if you want to (otherwise don't expect to do your off-hook on-hook off-hook too fast).
- apply my patch zaptel-base-c_patch_1_4_rev3121 on revision 3121 branch 1.4 (this is one of the latest available).
If you don't want to apply the patch you probably could try loop start signalling instead of kewlstart.

Now you shouldn't have to make an asterisk patch anymore.

Note:
I haven't tested my patch because I don't use kewlstart on my FXS lines. So please try it and give feedback -- it could avoid to patch asterisk and it may also avoid other race conditions because of kewlstart mishandling.


By: Tilghman Lesher (tilghman) 2007-11-05 11:33:15.000-0600

If we don't get some feedback soon, I'm going to close this issue, as I suspect everybody has lost interest.
By: Jonathan Hunter (jmhunter) 2007-11-05 16:39:16.000-0600

meneault - thank you for your advice.

I have decreased the rxflash time (although this was not the issue - I waited for the console to show "Hungup 'Zap/3-1' before picking up the handset again), and this works as described.

The big change, though, came when I switched from fxs_ks to fxs_ls signalling. This has completely eliminated the buggy behaviour.

To a lay person, what is the difference between Kewlstart and Loopstart? Why would somebody choose one over the other? I seem to remember the documentation recommends Kewlstart.

I will try your patch now and let you know if it works as well.
By: Jonathan Hunter (jmhunter) 2007-11-05 16:46:37.000-0600

I have just tried zaptel-base-c_patch_1_4_rev3121 (Zaptel SVN-branch-1.4-r2972M) and it works perfectly with my zap channels in fxo_ks mode.

I can now pick up the handset directly after hanging up, and instantly get a dialtone.

Thanks meneault - it's a simple patch and seems to work well.
By: meneault (meneault) 2007-11-08 02:24:55.000-0600

jmhunter:
Basically loopstart signalling and kewlstart signalling are almost the same.
Choosing one or another is usually a question of hardware i.e your phones for FXS channels.

kewlstart is an add-on of loopstart, with loopstart you can't know when other party has hanged up, you are obliged to detect a congestion tone and then hangup. Usually on your asterisk configuration for your FXO channels you would have something like busydetect=yes (or call progress detection or hangup on polarity switch).

With kewlstart signalling on an FXO channel, the telco provider drop the battery when other party has hanged up, thus your asterisk automatically knows that the conversation is over and can hangup the channel automatically, without trying to detect the congestion tone.
So for FXO channels the difference is really important.

For FXS channels it does not really matter to know when the communication is over because on FXS channels you usually connect regular phones which are taken off-hook by humans (i.e not computers). And when the channel is hanged up asterisk plays a congestion tone on the channel, thus you know that the communication is over and you hang-up.
In kewlstart mode, asterisk (actually zaptel) also drops the battery when the communication is over and your phones may detect this and hang-up automatically.
So for FXS channels it doesn't hurt as much as for FXO channels and loopstart could be a good choice if you don't need the automatic hangup detection by your phones.

FYI, in zaptel the kewlstart handling is buggy (IMHO) because when your phones are already on-hook zaptel indicates hangup anyway by dropping battery during 800ms which is simply non-sense because nobody is listening on the channel.
So my patch only remove the battery drop when nobody is listening, that avoid you to wait 800ms before taking the phone off-hook again.
By: Digium Subversion (svnbot) 2008-03-04 17:54:43.000-0600

Repository: zaptel
Revision: 3932

U   branches/1.4/kernel/zaptel-base.c

------------------------------------------------------------------------
r3932 | kpfleming | 2008-03-04 17:54:41 -0600 (Tue, 04 Mar 2008) | 9 lines

don't add an unnecessary delayed battery transition on FXS ports when we know the other end is already on-hook

(closes issue ASTERISK-9377)
Reported by: mmacvicar
Patches:
     zaptel-base-c_patch_1_4_rev3121 uploaded by meneault (license 260)
Tested by: jmhunter


------------------------------------------------------------------------

http://svn.digium.com/view/zaptel?view=rev&revision=3932
By: Digium Subversion (svnbot) 2008-03-05 16:21:11.000-0600

Repository: zaptel
Revision: 3944

_U  team/mattf/zaptel-1.4-vpmadt032fwupdate/
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/Makefile
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/README
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/build_tools/test_kernel_git
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/hdlcstress.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/hdlctest.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/GNUmakefile
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/tor2.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/torisa.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/xpp/utils/zconf/Zaptel/Span.pm
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/zaptel-base.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/tonezone.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/zaptel.conf.sample
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/zonedata.c

------------------------------------------------------------------------
r3944 | mattf | 2008-03-05 16:21:09 -0600 (Wed, 05 Mar 2008) | 98 lines

Merged revisions 3881,3883,3885,3888,3892,3899,3904,3916,3919-3921,3932,3939 via svnmerge from
https://origsvn.digium.com/svn/zaptel/branches/1.4

................
r3881 | kpfleming | 2008-02-26 17:43:29 -0600 (Tue, 26 Feb 2008) | 2 lines

properly initialize the buffer used for holding generated tone samples... this should fix issue ZAP-283 and solve problems with DTMF generation

................
r3883 | sruffell | 2008-02-26 19:13:05 -0600 (Tue, 26 Feb 2008) | 3 lines

Increase the battery debounce from 64ms to 1 second.


................
r3885 | sruffell | 2008-02-27 12:30:56 -0600 (Wed, 27 Feb 2008) | 4 lines

Set the default tone zone to to the first loaded zone by default.

Should prevent the crash reported in issue  0012053.

................
r3888 | tzafrir | 2008-02-27 15:57:44 -0600 (Wed, 27 Feb 2008) | 3 lines

* torisa.c: Report the correct E1/T1 .
* tor2.c: fix a typo in the span description string.

................
r3892 | sruffell | 2008-02-28 00:01:47 -0600 (Thu, 28 Feb 2008) | 6 lines

Undoing the change in revision 3883 until there can be more thought about the
best place to configure the battery debounce time.  Too short and erroneous
alarms are generated.  Too long, and asterisk won't detect when the remote
side disconnects.


................
r3899 | dbailey | 2008-02-28 08:37:26 -0600 (Thu, 28 Feb 2008) | 2 lines

Change DTMF and MF level parameters to match country specs

................
r3904 | tzafrir | 2008-02-28 10:12:08 -0600 (Thu, 28 Feb 2008) | 2 lines

Remove some unused variables.

................
r3916 | tzafrir | 2008-03-03 04:57:00 -0600 (Mon, 03 Mar 2008) | 3 lines

* Document 'mulaw', 'alaw' and 'deflaw' in the sample config file.
* Fix spacing in the README.

................
r3919 | tzafrir | 2008-03-03 15:01:34 -0600 (Mon, 03 Mar 2008) | 2 lines

Fix setting versions in test_kernel_git.

................
r3920 | tzafrir | 2008-03-03 15:33:16 -0600 (Mon, 03 Mar 2008) | 11 lines

Blocked revisions 3917 via svnmerge

........
r3917 | tzafrir | 2008-03-03 22:44:01 +0200 (Mon, 03 Mar 2008) | 4 lines

No need for userspace 'make clean' here. Kbuild takes care of it.

Closes issue ZAP-294 .

........

................
r3921 | tzafrir | 2008-03-03 16:04:02 -0600 (Mon, 03 Mar 2008) | 5 lines

* Pass some extra variables explicitly in the 2.4 build.
* Clean up the 2.4 kernel GNUMakefile.

Should hopefully fix issue ZAP-291.

................
r3932 | kpfleming | 2008-03-04 17:58:35 -0600 (Tue, 04 Mar 2008) | 9 lines

don't add an unnecessary delayed battery transition on FXS ports when we know the other end is already on-hook

(closes issue ASTERISK-9377)
Reported by: mmacvicar
Patches:
     zaptel-base-c_patch_1_4_rev3121 uploaded by meneault (license 260)
Tested by: jmhunter


................
r3939 | tzafrir | 2008-03-05 15:16:47 -0600 (Wed, 05 Mar 2008) | 2 lines

Hopefully a fix for issue ZAP-296 .

................

------------------------------------------------------------------------

http://svn.digium.com/view/zaptel?view=rev&revision=3944
By: Digium Subversion (svnbot) 2008-06-07 13:53:39

Repository: dahdi
Revision: 3932

U   branches/1.4/kernel/zaptel-base.c

------------------------------------------------------------------------
r3932 | kpfleming | 2008-06-07 13:53:39 -0500 (Sat, 07 Jun 2008) | 9 lines

don't add an unnecessary delayed battery transition on FXS ports when we know the other end is already on-hook

(closes issue ASTERISK-9377)
Reported by: mmacvicar
Patches:
     zaptel-base-c_patch_1_4_rev3121 uploaded by meneault (license 260)
Tested by: jmhunter


------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=3932
By: Digium Subversion (svnbot) 2008-06-07 13:54:03

Repository: dahdi
Revision: 3944

_U  team/mattf/zaptel-1.4-vpmadt032fwupdate/
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/Makefile
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/README
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/build_tools/test_kernel_git
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/hdlcstress.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/hdlctest.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/GNUmakefile
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/tor2.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/torisa.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/xpp/utils/zconf/Zaptel/Span.pm
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/kernel/zaptel-base.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/tonezone.c
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/zaptel.conf.sample
U   team/mattf/zaptel-1.4-vpmadt032fwupdate/zonedata.c

------------------------------------------------------------------------
r3944 | mattf | 2008-06-07 13:53:56 -0500 (Sat, 07 Jun 2008) | 98 lines

Merged revisions 3881,3883,3885,3888,3892,3899,3904,3916,3919-3921,3932,3939 via svnmerge from
https://origsvn.digium.com/svn/zaptel/branches/1.4

................
r3881 | kpfleming | 2008-02-26 17:43:29 -0600 (Tue, 26 Feb 2008) | 2 lines

properly initialize the buffer used for holding generated tone samples... this should fix issue ZAP-283 and solve problems with DTMF generation

................
r3883 | sruffell | 2008-02-26 19:13:05 -0600 (Tue, 26 Feb 2008) | 3 lines

Increase the battery debounce from 64ms to 1 second.


................
r3885 | sruffell | 2008-02-27 12:30:56 -0600 (Wed, 27 Feb 2008) | 4 lines

Set the default tone zone to to the first loaded zone by default.

Should prevent the crash reported in issue  0012053.

................
r3888 | tzafrir | 2008-02-27 15:57:44 -0600 (Wed, 27 Feb 2008) | 3 lines

* torisa.c: Report the correct E1/T1 .
* tor2.c: fix a typo in the span description string.

................
r3892 | sruffell | 2008-02-28 00:01:47 -0600 (Thu, 28 Feb 2008) | 6 lines

Undoing the change in revision 3883 until there can be more thought about the
best place to configure the battery debounce time.  Too short and erroneous
alarms are generated.  Too long, and asterisk won't detect when the remote
side disconnects.


................
r3899 | dbailey | 2008-02-28 08:37:26 -0600 (Thu, 28 Feb 2008) | 2 lines

Change DTMF and MF level parameters to match country specs

................
r3904 | tzafrir | 2008-02-28 10:12:08 -0600 (Thu, 28 Feb 2008) | 2 lines

Remove some unused variables.

................
r3916 | tzafrir | 2008-03-03 04:57:00 -0600 (Mon, 03 Mar 2008) | 3 lines

* Document 'mulaw', 'alaw' and 'deflaw' in the sample config file.
* Fix spacing in the README.

................
r3919 | tzafrir | 2008-03-03 15:01:34 -0600 (Mon, 03 Mar 2008) | 2 lines

Fix setting versions in test_kernel_git.

................
r3920 | tzafrir | 2008-03-03 15:33:16 -0600 (Mon, 03 Mar 2008) | 11 lines

Blocked revisions 3917 via svnmerge

........
r3917 | tzafrir | 2008-03-03 22:44:01 +0200 (Mon, 03 Mar 2008) | 4 lines

No need for userspace 'make clean' here. Kbuild takes care of it.

Closes issue ZAP-294 .

........

................
r3921 | tzafrir | 2008-03-03 16:04:02 -0600 (Mon, 03 Mar 2008) | 5 lines

* Pass some extra variables explicitly in the 2.4 build.
* Clean up the 2.4 kernel GNUMakefile.

Should hopefully fix issue ZAP-291.

................
r3932 | kpfleming | 2008-03-04 17:58:35 -0600 (Tue, 04 Mar 2008) | 9 lines

don't add an unnecessary delayed battery transition on FXS ports when we know the other end is already on-hook

(closes issue ASTERISK-9377)
Reported by: mmacvicar
Patches:
     zaptel-base-c_patch_1_4_rev3121 uploaded by meneault (license 260)
Tested by: jmhunter


................
r3939 | tzafrir | 2008-03-05 15:16:47 -0600 (Wed, 05 Mar 2008) | 2 lines

Hopefully a fix for issue ZAP-296 .

................

------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=3944