[asterisk-bugs] [JIRA] (ASTERISK-15295) one way audio after call waiting

[Michael J Miller (JIRA)]

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

Michael J Miller commented on ASTERISK-15295:
---------------------------------------------

Also: since line numbers without a filename is not the most helpful thing ever.. I was referring to channels/sig_analog.c.

Thanks,
-mm
                
> one way audio after call waiting
> --------------------------------
>
>                 Key: ASTERISK-15295
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-15295
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_dahdi
>            Reporter: Erik Smith
>
> System is CentOS 5.3
> asterisk 1.6.1.11 
> addons 1.6.1.2
> dahdi 2.2.0.2
> TDM800P card w/ echo can, 1 quad FXO module chan 1-4 and 1 single FXS module chan 5
> 1. call comes into asterisk via SIP which then rings a ring group of devices
> Local/101
> Local/102
> Local/103 etc
> 2. call answered on chan dahdi/5
> 3. while on call a second call comes in calling the same ring group and call waiting beep is heard on dahdi/5 device and the dahdi/5 device can still hear the remote user. the remote user can no longer hear audio from dahdi/5.
> relative chan_dahdi.conf section
> group = 1
> context=from-inside
> signalling=fxo_ks
> callerid=House Phones<101>
> mailbox=102
> txgain=-4.0
> rxgain=-2.0
> callwaiting=no
> callreturn=yes
> callwaitingcallerid=no
> threewaycalling=no
> transfer=yes
> cancallforward=yes
> callreturn=yes
> pickupgroup=1
> callgroup=1
> channel => 5
> ****** ADDITIONAL INFORMATION ******
> This issue does not exist in 1.6.0 releases. I first encountered this problem when I went from 1.6.0 releases to 1.6.1.6 but reverted. Tried again to migrate to 1.6.1.11 to discover the problem still exists. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira