[asterisk-bugs] [JIRA] (ASTERISK-21008) falsly detecting CNG tones

[Tim Heath (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Heath updated ASTERISK-21008:
---------------------------------

    Attachment: inboundRTP.au
                00308278_digium-info_20130123.tar.gz
                00308278_digiuminfo.txt

Attaching: 
-digiuminfo from autosupport
-inboundRTP.au exported from wireshark

full pcap / cli capture / autosupport is large, and can be found here:

http://hsv-pdc.digium.internal/public/Technical_Support/cases/00308278/00308278_digium_20130123-0854.tar.gz

failing call is:
3166 => Asterisk
566e157b-498fc2e1-1c9358d6
Asterisk => 5052173166
42dc35ae274695627ecf71d571ea2a1b
                
> falsly detecting CNG tones
> --------------------------
>
>                 Key: ASTERISK-21008
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21008
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>         Environment: Asterisk 1.8.18.0
> Linux 2.6.18-308.11.1.el5
>            Reporter: Tim Heath
>         Attachments: 00308278_digium-info_20130123.tar.gz, 00308278_digiuminfo.txt, inboundRTP.au
>
>
> Customer is experiencing an issue with SIp calls being rerouted back to the inbound DID route in the middle of some calls.
> Turns out that Asterisk detects CNG tone from the sip providers side in the middle of the call and routes the call to the fax extension. (this leads back to their IVR, for what it's worth)
> The customer can workaround this issue by setting "faxdetect=no" BUT they are in an argument with their SIP provider, and they would like help discovering if this is a bug within asterisk, or if there is something being sent by the provider.
> I have attempted to analyze the RTP stream from an example call, and though there was some barely audible noise in the silence, I wasn't really able to make heads or tails of it. 

--
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