Re: [asterisk-users] DAHDI DTMF problem?

2012-07-06 Thread Bill Dunn - VCI Internet Services
   I used the dahdi_monitor to record the audio on the T1 channel of the 
working server and the new server. The audio stream of the working server 
allowed me to hear the audio I heard over the phone call plus the DTMF at 
the very beginning. The audio of the new server was completely messed up. I 
could barely make out the where the DTMF and the audio were in the file. If 
I didn't have a working sample I wouldn't know what it was. And, the 
beginning of the new server sample always contains a hum or tone in it 
whereas the working server does not have that.


What does this tell me?


Bill Dunn



- Original Message - 
From: Shaun Ruffell

To: Asterisk Users Mailing List - Non-Commercial Discussion
Sent: Friday, July 06, 2012 12:16 PM
Subject: Re: [asterisk-users] DAHDI DTMF problem?


On Fri, Jul 06, 2012 at 11:10:43AM -0500, Tim Nelson wrote:

- Original Message -
>
> It has a Digium Wildcard TE122

If it has an onboard echo canceler, try disabling it and retrying.
Just a shot in the dark, going from my experience with other cards
and same symptoms. If the card is new(ish) I would think Digium
could provide support to you for determining the DTMF problems.


Bill,

To repeat what Tim said, if you're eligible I would recommend
contacting Digium's support department. There are many variables
with a new install and Digium support would be happy to help you
troubleshoot.

Some other things to try in order to isolate the drivers / hardware
change from the Asterisk change. You could:

a) Install the exact same versions of Asterisk / DAHDI that you used
previously on the new server with Centos 5.8.

b) Run a local pattern test to verify the host <-> card
communication is valid. If you have problems here there may be a
framebuffer configured or a disk controller running in combined mode
preventing the cards interrupt handler from running in a timely
fashion.

c) Use dahdi_monitor to record the audio on the channel you're
testing with and open it up with audacity and verify that the DTMF
looks correct. If it does, then most likely there is a problem with
chan_dahdi reading the audio from the drivers quickly enough.

d) Ensure that you are only loading the Asterisk modules you need in
case you're running on a system with limited memory and the asterisk
process is dropping audio while paging in code. (See DAHLIN-241 [1])

[1] https://issues.asterisk.org/jira/browse/DAHLIN-241

Cheers,
Shaun

--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users 



--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] DAHDI DTMF problem?

2012-07-06 Thread Bill Dunn - VCI Internet Services
Thanks Ron. I have had my chan_dahdi.conf file set as follows with the same 
result.


[trunkgroups]
[channels]
switchtype=national
usecallerid=yes
callerid=asreceived
cidsignalling=smdi
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
usesmdi=yes
smdiport=/dev/ttyS0
signalling = em_w
immediate = no
group = 1
channel => 1-3



Bill Dunn



- Original Message - 
From: Ron Bergin

To: Asterisk Users Mailing List - Non-Commercial Discussion
Sent: Friday, July 06, 2012 12:34 PM
Subject: Re: [asterisk-users] DAHDI DTMF problem?


Bill Dunn - VCI Internet Services wrote:

I have an Asterisk server configured to run as voicemail with a T1 and
SMDI.
It has 1.6.1.6 (dahdi 2.1.0.4) and Centos 5.6 and has worked great for a
few
years. I am configuring a new server with Asterisk 1.8.13 (dahdi 2.6.1) on
Centos 5.8

The problem I am having appears to be related to DTMF detection. When the
test phone number is called (2704083000) Asterisk only receives a portion
of
the dialed number. It varies as to what numbers are detected. Sometimes it
sees a single digit, sometimes 3 or 4 of the digits of the dialed number.

When I compare this to the old server the debug below is similar but there
isn't any mention of the "sig_analog.c" lines shown below.

I am told the T1's on the old server and the new server are configured the
same. I can make outgoing calls on the T1 from Asterisk.

Can someone give me a clue as to what could be causing this?


Bill Dunn



Try setting:
relaxdtmf=yes

We used to have that same problem on most of our servers.  Setting
relaxdtmf to yes solved the problem for us.

--
Ron Bergin
Network Operations Administrator
Fry's Electronics, Inc.




--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users 



--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] DAHDI DTMF problem?

2012-07-06 Thread Bill Dunn - VCI Internet Services

Sorry, forgot to include that.

It has a Digium Wildcard TE122

I've asked Digium about the card below. They say the -1 in the bipolar and 
CRC errors is ok. They don't change.


Description  AlarmsIRQbpviol CRCFra 
Codi Options  LBO
Wildcard TE122 Card 0 OK1  -1 -1   ESF 
B8ZS0 db (CSU)/0-133 feet (DSX-1)



Bill Dunn



- Original Message - 
From: Tim Nelson

To: Asterisk Users Mailing List - Non-Commercial Discussion
Sent: Friday, July 06, 2012 11:01 AM
Subject: Re: [asterisk-users] DAHDI DTMF problem?


- Original Message -

I have an Asterisk server configured to run as voicemail with a T1
and SMDI.
It has 1.6.1.6 (dahdi 2.1.0.4) and Centos 5.6 and has worked great
for a few
years. I am configuring a new server with Asterisk 1.8.13 (dahdi
2.6.1) on
Centos 5.8

The problem I am having appears to be related to DTMF detection. When
the
test phone number is called (2704083000) Asterisk only receives a
portion of
the dialed number. It varies as to what numbers are detected.
Sometimes it
sees a single digit, sometimes 3 or 4 of the digits of the dialed
number.

When I compare this to the old server the debug below is similar but
there
isn't any mention of the "sig_analog.c" lines shown below.

I am told the T1's on the old server and the new server are
configured the
same. I can make outgoing calls on the T1 from Asterisk.

Can someone give me a clue as to what could be causing this?



What kind of hardware are you using to interface with the T1? Is there any 
chance a HWEC or other DSP is interfering with DTMF?


--Tim


--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] DAHDI DTMF problem?

2012-07-06 Thread Bill Dunn - VCI Internet Services
I have an Asterisk server configured to run as voicemail with a T1 and SMDI. 
It has 1.6.1.6 (dahdi 2.1.0.4) and Centos 5.6 and has worked great for a few 
years. I am configuring a new server with Asterisk 1.8.13 (dahdi 2.6.1) on 
Centos 5.8


The problem I am having appears to be related to DTMF detection. When the 
test phone number is called (2704083000) Asterisk only receives a portion of 
the dialed number. It varies as to what numbers are detected. Sometimes it 
sees a single digit, sometimes 3 or 4 of the digits of the dialed number.


When I compare this to the old server the debug below is similar but there 
isn't any mention of the "sig_analog.c" lines shown below.


I am told the T1's on the old server and the new server are configured the 
same. I can make outgoing calls on the T1 from Asterisk.


Can someone give me a clue as to what could be causing this?


Bill Dunn



[Jul  6 10:28:40] DEBUG[15045]: chan_dahdi.c:11895 do_monitor: Monitor 
doohicky got event Ring/Answered on channel 1
[Jul  6 10:28:40] DEBUG[15045]: sig_analog.c:3621 analog_handle_init_event: 
channel (1) - signaling (7) - event (ANALOG_EVENT_RINGOFFHOOK)
[Jul  6 10:28:40] DEBUG[15045]: dsp.c:471 ast_tone_detect_init: Setup tone 
1100 Hz, 500 ms, block_size=160, hits_required=21
[Jul  6 10:28:40] DEBUG[15045]: dsp.c:471 ast_tone_detect_init: Setup tone 
2100 Hz, 2600 ms, block_size=160, hits_required=116
[Jul  6 10:28:40] DEBUG[15036]: devicestate.c:458 do_state_change: Changing 
state for DAHDI/1 - state 2 (In use)
[Jul  6 10:28:40] DEBUG[15081]: sig_analog.c:1769 __analog_ss_thread: 
__analog_ss_thread 1

   -- Starting simple switch on 'DAHDI/1-1'
[Jul  6 10:28:40] DEBUG[15036]: devicestate.c:438 devstate_event: device 
'DAHDI/1' state '2'
[Jul  6 10:28:40] DEBUG[15053]: app_queue.c:1487 handle_statechange: Device 
'DAHDI/1' changed to state '2' (In use) but we don't care because they're 
not a member of any queue.
[Jul  6 10:28:40] DEBUG[15081]: sig_analog.c:1602 analog_handle_dtmf: Begin 
DTMF digit: 0x32 '2' on DAHDI/1-1
[Jul  6 10:28:40] DEBUG[15081]: chan_dahdi.c:2026 my_handle_dtmf: Begin DTMF 
digit: 0x32 '2' on DAHDI/1-1
[Jul  6 10:28:40] DEBUG[15081]: sig_analog.c:1602 analog_handle_dtmf: End 
DTMF digit: 0x32 '2' on DAHDI/1-1
[Jul  6 10:28:40] DEBUG[15081]: chan_dahdi.c:2026 my_handle_dtmf: End DTMF 
digit: 0x32 '2' on DAHDI/1-1
[Jul  6 10:28:40] DEBUG[15081]: sig_analog.c:1602 analog_handle_dtmf: Begin 
DTMF digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:28:40] DEBUG[15081]: chan_dahdi.c:2026 my_handle_dtmf: Begin DTMF 
digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:28:40] DEBUG[15081]: sig_analog.c:1602 analog_handle_dtmf: End 
DTMF digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:28:40] DEBUG[15081]: chan_dahdi.c:2026 my_handle_dtmf: End DTMF 
digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:28:41] DEBUG[15081]: sig_analog.c:1602 analog_handle_dtmf: Begin 
DTMF digit: 0x38 '8' on DAHDI/1-1
[Jul  6 10:28:41] DEBUG[15081]: chan_dahdi.c:2026 my_handle_dtmf: Begin DTMF 
digit: 0x38 '8' on DAHDI/1-1
[Jul  6 10:28:41] DEBUG[15081]: sig_analog.c:1602 analog_handle_dtmf: End 
DTMF digit: 0x38 '8' on DAHDI/1-1
[Jul  6 10:28:41] DEBUG[15081]: chan_dahdi.c:2026 my_handle_dtmf: End DTMF 
digit: 0x38 '8' on DAHDI/1-1
[Jul  6 10:28:41] DEBUG[15081]: chan_dahdi.c:4927 dahdi_enable_ec: Enabled 
echo cancellation on channel 1

   -- Unknown extension '278' in context 'default' requested




Here is another call.

[Jul  6 10:48:34] DEBUG[15138]: chan_dahdi.c:11895 do_monitor: Monitor 
doohicky got event Ring/Answered on channel 1
[Jul  6 10:48:34] DEBUG[15138]: sig_analog.c:3621 analog_handle_init_event: 
channel (1) - signaling (7) - event (ANALOG_EVENT_RINGOFFHOOK)
[Jul  6 10:48:34] DEBUG[15138]: dsp.c:471 ast_tone_detect_init: Setup tone 
1100 Hz, 500 ms, block_size=160, hits_required=21
[Jul  6 10:48:34] DEBUG[15138]: dsp.c:471 ast_tone_detect_init: Setup tone 
2100 Hz, 2600 ms, block_size=160, hits_required=116
[Jul  6 10:48:34] DEBUG[15150]: sig_analog.c:1769 __analog_ss_thread: 
__analog_ss_thread 1
[Jul  6 10:48:34] DEBUG[15129]: devicestate.c:458 do_state_change: Changing 
state for DAHDI/1 - state 2 (In use)
[Jul  6 10:48:34] DEBUG[15129]: devicestate.c:438 devstate_event: device 
'DAHDI/1' state '2'

   -- Starting simple switch on 'DAHDI/1-1'
[Jul  6 10:48:34] DEBUG[15145]: app_queue.c:1487 handle_statechange: Device 
'DAHDI/1' changed to state '2' (In use) but we don't care because they're 
not a member of any queue.
[Jul  6 10:48:34] DEBUG[15150]: sig_analog.c:1602 analog_handle_dtmf: Begin 
DTMF digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:48:34] DEBUG[15150]: chan_dahdi.c:2026 my_handle_dtmf: Begin DTMF 
digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:48:35] DEBUG[15150]: sig_analog.c:1602 analog_handle_dtmf: End 
DTMF digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:48:35] DEBUG[15150]: chan_dahdi.c:2026 my_handle_dtmf: End DTMF 
digit: 0x37 '7' on DAHDI/1-1
[Jul  6 10:48:35] DEBUG[15150]: chan_dahdi.c:4927 dahdi_enable_ec: Enabled 
echo cancellation on channel