Summary: | ASTERISK-18993: CLONE - Flooding with chan_sip.c:6047 sip_write: Asked to transmit frame type alaw, while native formats is 0x100 (g729) read/write = 0x | ||||
Reporter: | David O Reilly (trendboy) | Labels: | |||
Date Opened: | 2011-12-08 07:36:58.000-0600 | Date Closed: | 2012-02-09 16:59:07.000-0600 | ||
Priority: | Minor | Regression? | No | ||
Status: | Closed/Complete | Components: | Channels/chan_sip/CodecHandling | ||
Versions: | 1.8.7.1 | Frequency of Occurrence | |||
Related Issues: |
| ||||
Environment: | Attachments: | ||||
Description: | Astersik flooding with message : chan_sip.c:6047 sip_write: Asked to transmit frame type alaw, while native formats is 0x100 (g729) read/write = 0x100 (g729)/0x100 (g729) When user test dial at outtrunk: Dial(SIP/somenumberhere@outtrunk,40,m); i got many warninig messages like above. When we remove m(music on hold) parameter everything works fine: Dial(SIP/somenumberhere@outtrunk,40); We have installed moh files in alaw and g729 formats, and we using g729 codec from: <link removed by lmadsen> ****** ADDITIONAL INFORMATION ****** part of sip.conf: [test] type=friend callerid="test" username=test host=dynamic secret=test dtmfmode=info canreinvite=yes nat=yes qualify=yes context=outgoing disallow=all allow=alaw [outtrunk] type=peer host=21.21.12.45 canreinvite=no nat=yes sendrpid=yes disallow=all allow=g729 | ||||
Comments: | By: David O Reilly (trendboy) 2011-12-08 07:38:15.226-0600 I have this exact problem also - my console is flooded with it. I use the Digium G729 codec and my sip.conf is set to disallow=all and allow=g729 By: David O Reilly (trendboy) 2011-12-08 07:39:01.621-0600 I also use: diva*CLI> core show version Asterisk 1.8.7.1 built by root @ (hidden for safety for the bug report) on a i686 running Linux on 2011-11-29 23:28:58 UTC By: Matt Jordan (mjordan) 2011-12-28 15:34:44.017-0600 What format is the MOH being played in? How many licenses of the G729 codec do you have? By: Matt Jordan (mjordan) 2012-02-09 16:59:02.054-0600 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines |