Summary:	ASTERISK-16941: Dropping incompatible voice frame on Local/ on multiple atxfer a->b->c...->d...
Reporter:	Carlos Diego Russo Medeiros (cdiego)	Labels:
Date Opened:	2010-11-10 12:55:05.000-0600	Date Closed:	2013-01-15 11:01:21.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Multiple warning messages on Asterisk 1.4.36: Dropping incompatible voice frame on Local/.... when receiving calls with codec A and doing multiple attended transfers to codec B The first atxfer is ok. Reproduced with the following channel combinations SIP -> SIP -> SIP... IAX -> SIP -> SIP... DAHDI -> SIP -> SIP.. Tested in different systems witch I've upgraded from 1.4.22 to 1.4.36, tested with different codecs. g729 -> alaw ilbc -> alaw alaw -> ilbc alaw -> g729 ... Tried to set transcode_via_sln=no and restarting *, it has no effect. moh files in wav format, also tried moh files in multiple formats to avoid transcoding.. =============== Test Multiple call transfer =============== A with codec X calls  B with codec Y B answers the call B attended Transfer to C -> Ok C attended Transfer to D -> Multiple warning messages 139.... 150 Dropping incompatible voice frame on Local/ D attended Transfer to E -> Multiple warning messages 139.... 150 Dropping incompatible voice frame on Local/ ... [Nov 10 16:12:38] NOTICE[4463] channel.c: Dropping incompatible voice frame on Local/413@ramais-administrativo-81ea,2 of format slin since our native format has changed to 0x8 (alaw) ... [Nov 10 16:12:38] NOTICE[4463] channel.c: Dropping incompatible voice frame on Local/413@ramais-administrativo-81ea,2 of format slin since our native format has changed to 0x8 (alaw) Can it cause a problem to asterisk? I have about 7K to 10K of this warning messages per day in all my systems with 1.4.36 version.
Comments:	By: Leif Madsen (lmadsen) 2010-11-18 15:28:58.000-0600 Please test with 1.4.38-rc1 or later as many changes to Local changes were made that could potentially affect how this works. By: Carlos Diego Russo Medeiros (cdiego) 2010-11-22 18:26:47.000-0600 Hi, Tested with 1.4.38-rc1 and the issue still happens as the same with 1.4.36 tux*CLI> show version Asterisk 1.4.38-rc1 built by root @ tux.itflex.com.br on a i686 running Linux on 2010-11-22 15:08:01 UTC cat /var/log/asterisk/messages | grep -i voice ... ... [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) [2010-11-22 15:51:49] NOTICE[19535] channel.c: Dropping incompatible voice frame on Local/630@discagem-ramais-3631,2 of format slin since our native format has changed to 0x8 (alaw) ... ... ... Please, Let me know if you need any other information... By: Leif Madsen (lmadsen) 2011-01-18 09:53:15.000-0600 Please provide the debugging information from the console, along with the configuration files you're using, and the SIP trace for the SIP scnearios (along with SIP history enabled). We'll need this information in order to reproduce the issue and see what is going on. By: Matt Jordan (mjordan) 2013-01-15 11:01:16.214-0600 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions.  After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8.