[asterisk-bugs] [JIRA] (ASTERISK-20773) fake DTMF or talkoff

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201241#comment-201241 ] 

Rusty Newton edited comment on ASTERISK-20773 at 1/8/13 5:12 PM:
-----------------------------------------------------------------

Marlon, can you use [dahdi_monitor|http://docs.tzafrir.org.il/dahdi-tools/man/dahdi_monitor.8.html] to record the input (RX) audio stream before it gets to Asterisk? This will help out any developers who want to analyze the audio stream.

How does your T1 connect to Asterisk? Is it coming straight from a service provider or is there another PBX in front of your Asterisk system (providing the T1) ?
                
      was (Author: rnewton):
    Marlon, can you use [dahdi_monitor|http://docs.tzafrir.org.il/dahdi-tools/man/dahdi_monitor.8.html] to record the input (RX) audio stream before it gets to Asterisk? This will help out any developers who want to analyze the audio stream.
                  
> fake DTMF or talkoff
> --------------------
>
>                 Key: ASTERISK-20773
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20773
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>         Environment: DAHDI Version: 2.6.1 Echo Canceller: HWEC, OSLEC
> Asterisk 1.8.18.0 i686 running Linux CentOS release 5.8
> pci:0000:02:06.0     wct4xxp+     d161:0410 Wildcard TE410P (3rd Gen)
>            Reporter: Marlon Costa
>            Assignee: Marlon Costa
>         Attachments: beep_log_filtered.cap, beep_log_filtered.log, chan_dahdi_additional.conf, chan_dahdi.conf, dahdi-channels.conf, init.conf, modules, system.conf, xpp.conf
>
>
> Hi,
> Many of our customers claims a beep when making or receiving calls.
> Our tech team enabled debug in our Asterisk and found that this beeps are DTMF tones.
> In asterisk logs it's possible see this things many times:
> {noformat}
> [Dec  5 12:40:13] DEBUG[5764] chan_dahdi.c: Begin DTMF digit: 0x41 'A' on DAHDI/i1/21499100-fab
> [Dec  5 12:40:13] DTMF[5764] channel.c: DTMF begin 'A' received on DAHDI/i1/21499100-fab
> [Dec  5 12:40:13] DTMF[5764] channel.c: DTMF begin passthrough 'A' on DAHDI/i1/21499100-fab
> [Dec  5 12:40:13] DEBUG[5764] chan_dahdi.c: End DTMF digit: 0x41 'A' on DAHDI/i1/21499100-fab
> [Dec  5 12:40:13] DTMF[5764] channel.c: DTMF end 'A' received on DAHDI/i1/21499100-fab, duration 51 ms
> [Dec  5 12:40:13] DTMF[5764] channel.c: DTMF end accepted with begin 'A' on DAHDI/i1/21499100-fab
> [Dec  5 12:40:13] DTMF[5764] channel.c: DTMF end 'A' detected to have actual duration 60 on the wire, emulation will be triggered on DAHDI/i1/21499100-fab
> [Dec  5 12:40:13] DTMF[5764] channel.c: DTMF end 'A' has duration 60 but want minimum 80, emulating on DAHDI/i1/21499100-fab
> [Dec  5 12:40:13] DTMF[5764] channel.c: DTMF end emulation of 'A' queued on DAHDI/i1/21499100-fab
> {noformat}
> We done a wireshark capture to find out what is happening and it's possible see an RTP EVENT during these beeps see file attached.
> Could you please, help us to solve this issue?
> Thanks,
> Marlon

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira