search for: debounce

I get the following message on a Centos 5 system (really a Trixbox 2.4 build on Centos 5): Jan 14 00:12:28 sip2 kernel: hub 1-0:1.0: connect-debounce failed, port 1 disabled What does this mean? This message occurs about 30 times/sec for about 45 sec. Then my Bluetooth token starts up. Jan 14 00:12:28 sip2 kernel: hub 1-0:1.0: connect-debounce failed, port 1 disabled Jan 14 00:13:00 sip2 last message repeated 18 times Jan 14 00:14:01 sip...

...0ms) ; preflash: Pre-flash time (default 50ms) ; wink: Wink time (default 150ms) ; flash: Flash time (default 750ms) ; start: Start time (default 1500ms) ; rxwink: Receiver wink time (default 300ms) ; rxflash: Receiver flashtime (default 1250ms) ; debounce: Debounce timing (default 600ms)

...0000:00:02.0: GetStatus roothub.portstatus [1] = 0x00030300 PESC CSC LSDA PPS hub 2-0:1.0: port 2, status 0300, change 0003, 1.5 Mb/s usb 2-2: USB disconnect, address 87 usb 2-2: unregistering device usb 2-2: usb_disable_device nuking all URBs usb 2-2: unregistering interface 2-2:1.0 hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x300 hub 1-0:1.0: state 7 ports 10 chg 0000 evt 0004 ehci_hcd 0000:00:02.1: GetStatus port 2 status 001403 POWER sig=k CSC CONNECT hub 1-0:1.0: port 2, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501...

Hi, I'm having problems with a TE420P card, in which I cannot make calls using spans 2 through 4. After a couple of days of working correctly, spans 2, 3 and 4 start failing (can not make calls). The system is configured to work with SS7. After the ACM message goes out, immediately a REL message is returned. I searched for error messages in /var/log/messages and could not find a clue

...ese settings in zapata.conf to fix my problem? *prewink*: Sets the pre-wink timing. *preflash*: Sets the pre-flash timing. *wink*: Sets the wink timing. *rxwink*: Sets the receive wink timing. *rxflash*: Sets the receive flash timing. *flash*: Sets the flash timing. *start*: Sets the start timing. *debounce*: Sets the debounce timing. "The debounce settings in the Asterisk configuration affects how Asterisk handles hookswitch transitions on its FXO/FXS interfaces." --

...automated testing going on all the time. Now granted the real problem is the zhone itself being oversensitive, but I take the view that you can always fix shit hardware with the right software. After writing off the telco (Bell Canada) as morons, I attempt to find a solution in asterisk - ring debounce looks right so I investigate the zaptel libs. Mark chimes in about how could this be possible yada yada. After investigation I find the debounce set to 500ms, but basically ignored and treated as an on/off value - implementation of which still seems pretty strange, but I am convinced it is not...

...as a flash instead of a hangup?). A 'soft hangup zap/27-1' will not do anything (though it makes an attempt). Does shortening the rxflash time sound like it may help this? (Does anyone have a good explanation, or link to one, of the prewink, wink, preflash, flash, start, rxwink, rxflash, debounce timing functions?) Thanks, as always... Steve

Hello there, I tried to found documentation about openloop disconnect on Asterisk/Zaptel. And up to now, I didn't find anything. Is openloop disconnect supported by zaptel/wcfxo drivers? Other question: maxsilence and silencethreshold don't seem to have any effect on voicemail. Could it be possible that in certain situation it just wont work? I tried adding some verbose in

...is converted and routed to Asterisk. The lines are configured as follows: /etc/asterisk/zapata.conf ; Channels 1-24 service MainStreet 3624 channel bank context=infrom-did group=1 immediate=yes signalling = fxo_ls busydetect=no callprogress=no echocancel=yes echotrain=no echocancelwhenbridged=yes debounce=50 channel => 1-4 /etc/asterisk/extensions.conf [infrom-did] exten => s,1,DigitTimeout,3 ; Gather keypresses, 2 second pause is 'completed dialing' exten => s,3,ResponseTimeout,10 ; 10 seconds without any digits is a problem... include => ou...

...wctdm24xxp: Name the shadow registers for each modules. wctdm24xxp: Change intcount to framecount. wctdm24xxp: Use fact that handle_transmit/receive are called in hard-irq wctdm24xxp: Protect creation / destruction of VPM instance. wctdm24xxp: Reset the polarity debounce setting when battery is lost. wctdm24xxp: Probe for and configure modules in parallel. wctdm24xxp: Introduce bg_create/bg_join. wcte12xp: Abort driver bind if read/write test fails. The DAHDI-Linux diffstat from the 2.5.0.2 release: README...

...wctdm24xxp: Name the shadow registers for each modules. wctdm24xxp: Change intcount to framecount. wctdm24xxp: Use fact that handle_transmit/receive are called in hard-irq wctdm24xxp: Protect creation / destruction of VPM instance. wctdm24xxp: Reset the polarity debounce setting when battery is lost. wctdm24xxp: Probe for and configure modules in parallel. wctdm24xxp: Introduce bg_create/bg_join. wcte12xp: Abort driver bind if read/write test fails. The DAHDI-Linux diffstat from the 2.5.0.2 release: README...

Hello all- So I have * up and running and connected to a legacy system via em_w lines and have no trouble dialing from * through the tie line but from the PBX across the tie line I am having intermittant receipt of the DTMF. T-Berd testing is showing that the digits are coming across but * is either missing the first digit consistantly. This seems to me to have something to do with start timers

...nge, but a switching power supply might still be able to coast through it-- especially if the supply is oversized for the load at the time of the abnormality. Since both "outages" (really, the on-battery states) were exactly 10 seconds long means that the UPS was probably trying to "debounce" the voltage fluctuation by not switching back to line power immediately after the voltage went back to normal. For APCs and MGEs, I think it is typically 5 seconds. Several people have rigged up longer timers with upssched to not send the wall message until it has been on battery for, say,...

...loaded they won't be on at all. They do not change if a phone is plugged in or not. root@asterisk:~# cat /etc/asterisk/zapata.conf |grep -v "^;" [channels] context=default switchtype=national signalling=em_w rxwink=2500 ; Atlas seems to use long (250ms) winks start=250 debounce=333 usecallerid=yes hidecallerid=yes callwaiting=no usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes relaxdtmf=yes #rxgain=-10.1 #txgain=-10.1 group=1 callgroup=1 pickupgroup=1 immediate=no musico...

Hello, I'm a little confused on DTMF. A sip peer is registered on two Asterisk servers. No dtmfmode is set for them, the sip peer is 999 on Asterisk 1 and 999 on Asterisk 2. They both register on each other. A call comes in on Asterisk server 1, provider 1, dtmf=inband. Then the call is transferred to Asterisk 2: RetryDial(/var/lib/asterisk/sounds/connecting,15,10,SIP/12351 at

...able length). No difference. My next angle of attack was the software - I dug around in the dahdi source code to try and find timeouts to adjust, so that it wouldn't be quite so quick to think that I had picked up the phone. However I didn't have any luck with that, either. There is a 'debounce' parameter which is great in theory, but only worked when I hung up the phone - it had no impact on picking it up in the first place. So I'm throwing the question open to the amassed wisdom of [asterisk-users]. Can anybody perhaps point me in the right direction of what I can try next? Th...

Something new to me. Recently installed a 1.4.30 box for a small office with four POTS lines in a hunt (Digium TDM410P). Had the telco put a "call forward" option on the main line of the hunt. They dial a feature code from their desk phones (Polycom IP450) that results in forwarding the main number to our VoIP service. This is all to let them "try out" our dialtone

...wered immediately or ; if the simple switch should provide dialtone, read digits, etc. ; immediate=yes ; For fax detection, uncomment one of the following lines. The default is *OFF* ; ;faxdetect=both ;faxdetect=incoming ;faxdetect=outgoing ;faxdetect=no rxgain=0 txgain=0 signalling=em wink=200 debounce=100 flash=300 ;context=zap-incoming context=gv-incoming group = 1 channel => 1-17 signalling=em_w context=zap-incoming group = 2 channel => 21-24

0 listeners is fine. Just no sense in pulling of a feed when no one is listening. ----- Original Message ----- From: "Karl Heyes" <karl@xiph.org> To: <Jason@Weatherserver.net> Cc: "icecast" <> Sent: Friday, May 13, 2005 7:09 AM Subject: Re: [Icecast] On-Demand Relay > On Fri, 2005-05-13 at 05:56, Jason wrote: >> Is on-demand relay currently

The Asterisk Development Team is pleased to announce the release of DAHDI-Linux and DAHDI-Tools version 2.2.1. DAHDI-Linux 2.2.1, DAHDI-Tools 2.2.1, and DAHDI-Linux-Complete are available for immediate download at http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete These