Summary:	ASTERISK-18063: Flooding with [Jun 24 19:33:17] WARNING[6995]: chan_sip.c:6213 sip_write: Asked to transmit frame type g726, while native formats is 0x4 (ulaw) read/write = 0x4 (ulaw)/0x4 (ulaw)
Reporter:	Erik Smith (eeman)	Labels:
Date Opened:	2011-06-24 18:35:07	Date Closed:	2011-09-22 01:23:40
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/CodecHandling
Versions:	1.8.4	Frequency of Occurrence	Constant
Related Issues:	is a clone of ASTERISK-17502 Flooding with chan_sip.c:6047 sip_write: Asked to transmit frame type alaw, while native formats is 0x100 (g729) read/write = 0x is duplicated by ASTERISK-14384 Early media causes "Asked to transmit frame type 64, while native formats is 0x8 (alaw)(8)......" is duplicated by ASTERISK-17502 Flooding with chan_sip.c:6047 sip_write: Asked to transmit frame type alaw, while native formats is 0x100 (g729) read/write = 0x is duplicated by ASTERISK-18325 "Asked to transmit frame type" slows down all the calls is duplicated by ASTERISK-18422 Warning in CLI that seems wrong. (Asked to transmit frame type ulaw, while native formats is 0x100 (g729)) is related to ASTERISK-18325 "Asked to transmit frame type" slows down all the calls
Environment:		Attachments:	( 0) chan_fixup2.patch
Description:	Asterisk flooding with message : [Jun 24 19:33:17] WARNING[6995]: chan_sip.c:6213 sip_write: Asked to transmit frame type g726, while native formats is 0x4 (ulaw) read/write = 0x4 (ulaw)/0x4 (ulaw) PSTN PRI -> asteriskA -> SIP(g726) -> asteriskB -> SIP(ulaw) -> polycom handset sip.conf trunk on asteriskA [COLLINSKINGB] qualify=4000 nat=no secret=********* ;=description=Trunk to Kingbrook location host=123.123.123.123 username=COLLINSKINGB dtmfmode=rfc2833 context=from-inside type=friend canreinvite=no disallow=all allow=g726 sip.conf entry on asteriskB [COLLINSKINGB] qualify=4000 nat=no secret=******** ;=description=Trunk to Collins location host=124.124.124.124 username=COLLINSKINGB dtmfmode=rfc2833 context=from-collins type=friend canreinvite=no disallow=all allow=g726 [2103] qualify=yes nat=no pickupgroup=1 callerid=Mike <2103> context=from-inside call-limit=10 canreinvite=no vmexten=2103 secret=******** username=2103 host=dynamic subscribecontext=local-extensions callgroup=1 dtmfmode=rfc2833 type=friend mailbox=2103 disallow=all allow=ulaw
Comments:	By: Erik Smith (eeman) 2011-06-24 18:39:27.117-0500 I am getting the exact same results in 1.8.4.2 I have also tried g726 and other codecs. PSTN PRI -> asteriskA -> SIP(g726) -> asteriskB -> SIP(ulaw) -> polycom handset both asteriskA and asteriskB are 1.8.4.2 only asteriskB displays this insane barage of warnings. [Jun 24 19:33:17] WARNING[6995]: chan_sip.c:6213 sip_write: Asked to transmit frame type g726, while native formats is 0x4 (ulaw) read/write = 0x4 (ulaw)/0x4 (ulaw) By: Gregory Hinton Nietsky (irroot) 2011-06-25 07:13:17.673-0500 Put a "hack" in to sort this out ill post in a bit it basically "aligns" the formats by calling ast_set_write_format but it should be called in main/channel.c not chan_Sip ill work on it further. By: Gregory Hinton Nietsky (irroot) 2011-06-25 12:36:45.891-0500 This is a Simple solution to the problem i have seen this on DAHDI and SIP channels so i added this to the core. By: Gregory Hinton Nietsky (irroot) 2011-06-26 07:30:38.033-0500 This will only run when needed if the writeformat is ok but not nativeformat its been translated. By: Gregory Hinton Nietsky (irroot) 2011-09-06 13:55:14.391-0500 Has someone tested this patch have any feedback. By: Michael Gaudette (bluefox) 2011-09-06 22:17:53.639-0500 I applied it and can't find any problems with it.  My calls from ulaw to g729 work but I haven't the problematic warnings yet. By: Ian Jones (pmlco) 2011-11-04 13:05:25.937-0500 Works for me too - it got rid of these messages when translating from ulaw to g729 (thanks to Digium support for pointing me here.)