search for: sip_writ

...e. I am testing using cisco 7902 phones and using cisco 2800 router. Codec is g711ulaw regards, -- Executing ParkedCall("SIP/192.168.50.2-09cbd610", "366") -- Channel SIP/192.168.50.2-09cbd610 connected to parked call 366 Mar 29 17:59:16 WARNING[13774]: chan_sip.c:2692 sip_write: Asked to transmit frame type 64, while native formats is 4 (read/write = 4/4) Mar 29 17:59:16 WARNING[13774]: chan_sip.c:2692 sip_write: Asked to transmit frame type 64, while native formats is 4 (read/write = 4/4) Mar 29 17:59:16 WARNING[13774]: chan_sip.c:2692 sip_write: Asked to transmit frame...

We are getting the following on 1.8.3 and 1.8.4-rc2, HELP! Why is Asterisk unable to transcode to/from ulaw and g722? [2011-04-21 09:51:34] WARNING[22067]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722) [2011-04-21 09:51:34] WARNING[22067]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722) [201...

...sue when I ma trying to place a call through my voip provider, I am using an asterisk 1.2.21.1, do you have an idea what could fix this issue (as you can see when the other party answered, the call get dropped because of probably sip incompatibility) Nov 12 14:31:30 WARNING[21432]: chan_sip.c:2587 sip_write: Asked to transmit frame type 256, while native formats is 4 (read/write = 4/4) Nov 12 14:31:30 WARNING[21432]: chan_sip.c:2587 sip_write: Asked to transmit frame type 4, while native formats is 256 (read/write = 256/256) Nov 12 14:31:30 WARNING[21432]: chan_sip.c:2587 sip_write: Asked to transmit...

...Codec mismatch on channel SIP/00493514977290-000001d1 setting write format to g729 from alaw native formats 0x8 (alaw) [Jul 15 18:59:55] WARNING[8752]: channel.c:5254 set_format: Unable to find a codec translation path from 0x8 (alaw) to 0x100 (g729) [Jul 15 18:59:55] WARNING[8752]: chan_sip.c:6773 sip_write: Asked to transmit frame type g729, while native formats is 0x8 (alaw) read/write = 0x8 (alaw)/0x8 (alaw) [Jul 15 18:59:55] WARNING[8752]: chan_sip.c:6773 sip_write: Asked to transmit frame type alaw, while native formats is 0x100 (g729) read/write = 0x8 (alaw)/0x8 (alaw) [Jul 15 18:59:55] WARNING...

...IP/Trunk-out/***************,180,tTr") in new stack == Using SIP RTP CoS mark 5 -- Called Trunk-out/****************** -- SIP/Trunk-out-00000777 is ringing -- SIP/Trunk-out-00000777 is making progress passing it to SIP/ua1-00000776 [Nov 19 17:08:37] WARNING[8377]: chan_sip.c:6027 sip_write: Asked to transmit frame type ulaw, while native formats is 0x2 (gsm) read/write = 0x2 (gsm)/0x2 (gsm) [Nov 19 17:08:37] WARNING[8377]: chan_sip.c:6027 sip_write: Asked to transmit frame type ulaw, while native formats is 0x2 (gsm) read/write = 0x2 (gsm)/0x2 (gsm) [Nov 19 17:08:37] WARNING[8377]:...

...176,18,rtT") in new stack == Using UDPTL TOS bits 184 == Using UDPTL CoS mark 5 == Using SIP RTP TOS bits 184 == Using SIP RTP CoS mark 5 -- Called SIP/176 -- SIP/176-0000001d is ringing -- SIP/176-0000001d is ringing [Nov 11 12:04:08] WARNING[24072]: chan_sip.c:6433 sip_write: Can't send 10 type frames with SIP write [Nov 11 12:04:08] WARNING[23780]: chan_sip.c:8740 process_sdp: Unsupported SDP media type in offer: video 0 RTP/AVP 26 31 34 98 99 104 -- SIP/176-0000001d answered SIP/teliax-00000019 [Nov 11 12:04:09] WARNING[24072]: chan_sip.c:6433 sip_write:...

...el.c:1884 set_format: Unable to find a path from g729 to gsm Jun 8 18:48:41 NOTICE[6073]: channel.c:1884 set_format: Unable to find a path from g729 to gsm Jun 8 18:48:42 NOTICE[6073]: channel.c:1884 set_format: Unable to find a path from g729 to gsm Jun 8 18:48:42 WARNING[6405]: chan_sip.c:2170 sip_write: Asked to transmit frame type 256, while native formats is 2 (read/write = 2/2) Jun 8 18:48:42 WARNING[6405]: chan_sip.c:2170 sip_write: Asked to transmit frame type 256, while native formats is 2 (read/write = 2/2) Jun 8 18:48:42 WARNING[6405]: chan_sip.c:2170 sip_write: Asked to transmit frame...

...ISDN line (it's BT ISDN2e on a pair of Eicon Diva BRI-2M cards) The Pickup(783743) works (the phone across the room stops ringing), but the calling party gets a nasty distorted noise back down the phone, and I get dozens of these messages: Dec 5 11:37:50 WARNING[26972]: chan_sip.c:2561 sip_write: Asked to transmit frame type 64, while native formats is 4 (read/write = 64/64) Any ideas what I'm doing wrong? Asterisk is 1.2.11 on Debian with 2.6.8-2-686 kernel. Thanks Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.d...

Starting with Asterisk 13.1 we are seeing this WARNING messages a lot in our logs and console: WARNING[25164][C-0004865e]: chan_sip.c:7364 sip_write: Can't send 10 type frames with SIP write) We found that line in function "sip_write" inside "chan_sip.c". In our previous version (11.2.1) we did not see those messages being printed (same verbosity level). We compared both versions of the functions and see no differenc...

...3227]: channel.c:1724 ast_set_write_format: Unable to find a path from ulaw to g723 -- SIP/SIP_PROVIDER-77e1 is making progress passing it to Zap/3-1 May 26 09:49:05 DEBUG[3242]: chan_zap.c:4479 zt_indicate: Received AST_CONTROL_PROGRESS on Zap/3-1 May 26 09:49:05 WARNING[3242]: chan_sip.c:1829 sip_write: Asked to transmit frame type 4, while native formats is 1 (read/write = 4/4) May 26 09:49:05 WARNING[3242]: chan_sip.c:1829 sip_write: Asked to transmit frame type 4, while native formats is 1 (read/write = 4/4) May 26 09:49:05 WARNING[3242]: chan_sip.c:1829 sip_write: Asked to transmit frame typ...

...p: No compatible codecs! 2005-07-13 10:20:48 NOTICE[23280]: channel.c:1736 ast_set_read_format: Unable to find a path from g729 to ulaw 2005-07-13 10:20:48 NOTICE[23280]: channel.c:1703 ast_set_write_format: Unable to find a path from alaw to g729 2005-07-13 10:20:48 WARNING[23280]: chan_sip.c:1836 sip_write: Asked to transmit frame type 8, while native formats is 256 (read/write = 4/8) 2005-07-13 10:20:48 WARNING[23280]: chan_sip.c:1836 sip_write: Asked to transmit frame type 8, while native formats is 256 (read/write = 4/8) 2005-07-13 10:20:49 WARNING[23280]: chan_sip.c:1836 sip_write: Asked to tran...

...0777-000001cc [2011-03-28 18:22:27] DEBUG[22502]: channel.c:6092 ast_set_owners_and_peers: setting peeraccount to 123456 for SIP/0010777-000001cc from data on channel SIP/zzz-000001cd -- Locally bridging SIP/0010777-000001cc and SIP/zzz-000001cd [2011-03-28 18:22:27] WARNING[22502]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x8 (alaw) read/write = 0x8 (alaw)/0x8 (alaw) [2011-03-28 18:22:27] WARNING[22502]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x8 (alaw) read/write = 0x8 (alaw)/0x8 (alaw) [2011-03-28 18:22:27]...

...annel.c:1736 ast_set_read_format: Unable to find a path from g723 to g729 Aug 11 10:15:02 NOTICE[11260]: channel.c:1703 ast_set_write_format: Unable to find a path from g729 to g723 -- SIP/isphone-8213 is making progress passing it to SIP/200-1264 Aug 11 10:15:02 WARNING[11260]: chan_sip.c:1836 sip_write: Asked to transmit frame type 4, while native formats is 1 (read/write = 256/256) Aug 11 10:15:02 WARNING[11260]: chan_sip.c:1836 sip_write: Asked to transmit frame type 4, while native formats is 1 (read/write = 256/256) Aug 11 10:15:02 WARNING[11260]: chan_sip.c:1836 sip_write: Asked to transmit...

...he client and the client listens to me normally. The problem is when I will transfer this connection, the call is mute for the extension I have transfered. Only the client hears normally. In the console of Asterisk generates the following warning: [Jul 19 14:46:24] WARNING [9220]: chan_sip.c: 5340 sip_write: Asked to transmit frame type 64, while native formats is 0x2 (gsm) (2) read / write = 0x40 (slin) (64) / 0x2 (gsm) (2) [Jul 19 14:46:24] WARNING [9220]: chan_sip.c: 5340 sip_write: Asked to transmit frame type 64, while native formats is 0x2 (gsm) (2) read / write = 0x40 (slin) (64) / 0x2 (gsm) (...

...n my sip conf I specified allow=g729. I called my PSTN geographic number again and was delighted when the incoming calls worked. However when I next went to make an outgoing call (after having added in the "allow=g729" line), I got an infinite loop of warnings: WARNING: chan_sip.c: 2520 sip_write: Asked to transmit frame type 256, while native formats is 8 (read/write = 8/8) WARNING: codec_gsm.c165 gsmtolin_framein: Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from RTP After those warnings I thought there might be a problem with the gsm codec so I commented the lines...

...the problem is somewhere in SpanDSP. From my logs, I get: -- Goto (macro-faxreceive,s,7) -- Executing RxFAX("SIP/<faxnumber removed>-ff83", "/var/spool/asterisk/fax/fax/asterisk-8558-1149842081.2.tif") in new stack Jun 9 10:34:56 WARNING[8558]: chan_sip.c:1829 sip_write: Asked to transmit frame type 64, while native formats is 4 (read/write = 64/4) Jun 9 10:34:56 WARNING[8558]: chan_sip.c:1829 sip_write: Asked to transmit frame type 64, while native formats is 4 (read/write = 64/4) Jun 9 10:34:56 WARNING[8558]: chan_sip.c:1829 sip_write: Asked to transmit fr...

...oice-dialout:1] Dial("DAHDI/18-1", "SIP/524|30|tT") in new stack -- Called 524 [May 3 21:47:41] WARNING[21746]: channel.c:3782 ast_channel_make_compatible: No path to translate from SIP/524-00000001(4096) to DAHDI/18-1(4) [May 3 21:47:41] WARNING[21746]: chan_sip.c:3890 sip_write: Asked to transmit frame type 4, while native formats is 0x1000 (g722)(4096) read/write = 0x1000 (g722)(4096)/0x1000 (g722)(4096) [May 3 21:47:41] WARNING[21746]: chan_sip.c:3890 sip_write: Asked to transmit frame type 4, while native formats is 0x1000 (g722)(4096) read/write = 0x1000 (g722)(...

...y already there, have got different HT behavior: 1. When HT use GSM codec => it connects to conference room, but hear nothing (just dead ear). 2. When HT use G729 codec => it gets busy signal and I could see such output on asterisk console ( Jul 1 07:26:14 WARNING[737298]: chan_sip.c:1611 sip_write: Asked to transmit frame type 4, while native formats is 256 (read/write = 4/256) Jul 1 07:26:14 WARNING[737298]: app_meetme.c:896 conf_run: Unable to write frame to channel: No child processes Jul 1 07:26:14 WARNING[737298]: app_meetme.c:896 conf_run: Unable to write frame to channel: No child...

When dialling in and dialling my extension, when answered I get " Read_channel ## vpb/1-3: Setting record mode, bridge = 0 WARNING[20499]: File chan_sip.c, Line 1111 (sip_write): Asked to transmit frame type 8, while native formats is 4 (read/write = 4/4) == Spawn extension (default, 1004, 1) exited non-zero on 'vpb/1-3' -- hangup on vpb (vpb/1-3) -- Hungup on vpb/1-3 complete -- Event [12=>[02] Loop Drop " And it hangs up the line any ideas ??? Regard...

...ent with ulaw), but not in the other (SIP client with GSM). The client used for this is X-Lite behind NAT while both servers have a public IP (I playback an anouncement before trying to connect to the second *). Error on the originating * server: WARNING[27670]: File chan_sip.c, Line 1148 (sip_write): Asked to transmit frame type 64, while native formats is 2 (read/write = 2/2) I really _really_ have no clue why codec "16 bit Signed Linear PCM" is n the game here, to my knowledge that is not supported by X-Lite, and it is certainly not enabled anyware in the conf files either...