search for: gsmtolin_framein

...below the line)? Machine P2 w/512MB RAM Debian (testing) ; kernel 2.6.12-1-386 asterisk 1.2.1-n-all incl. astcc For many months now I went through * 1.07, 1.09 and never saw something like that. Even with 1.2.0, a month now, at the beginning everything was fine, and suddenly "codec_gsm.c:194 gsmtolin_framein: Invalid GSM data" thing started. It happens with astcc (but not immediatelly) as you can see after being interogated about the card (after astcc-accountnum2). When there is no card check (silent level 4) sometimes there is no problem, but some times it happens when the callee party answers....

Hi I have created meetme with 3 user. When i going to mute user it gives following error.. *Asterisk Version : 1.6.2.6* -- <SIP/52987-00000040> Playing 'conf-muted.gsm' (language 'en') [Jul 2 22:46:51] WARNING[10823]: codec_gsm.c:103 gsmtolin_framein: Invalid GSM data (1) [Jul 2 22:46:51] WARNING[10823]: translate.c:204 framein: gsmtolin did not update samples 0 [Jul 2 22:46:51] WARNING[10823]: codec_gsm.c:103 gsmtolin_framein: Invalid GSM data (1) [Jul 2 22:46:51] WARNING[10823]: translate.c:204 framein: gsmtolin did not update samples 0 [J...

I park a call and instead of the parked extension being returned, I get silence and the log shows a bunch of the following messages WARNING[26220]: codec_gsm.c:135 gsmtolin_framein: Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from (null) (320)? what does this mean? BTW these messages are intermittant. sometimes it works fine other times i get the above message Regards Greg Cirino ___________________________________

Hi, I got ast. 1.6.0.10 working for a few weeks without a problem. A few mins ago..I got the following msgs on ast-cli and asterisk service crashed. I coudlnt find anything that might cause this problem. Any ideas?? [Aug 7 13:54:34] WARNING[10102]: codec_gsm.c:133 gsmtolin_framein: Invalid GSM data (1) [Aug 7 13:54:34] WARNING[10102]: translate.c:204 framein: gsmtolin did not update samples 0 [Aug 7 13:54:34] WARNING[10102]: codec_gsm.c:133 gsmtolin_framein: Invalid GSM data (1) [Aug 7 13:54:34] WARNING[10102]: translate.c:204 framein: gsmtolin did not update samples 0 [A...

...nable to find a path from gsm to g729 Jan 4 10:06:42 NOTICE[23409]: channel.c:1791 ast_set_read_format: Unable to find a path from g729 to slin Jan 4 10:06:42 NOTICE[23409]: channel.c:1791 ast_set_read_format: Unable to find a path from g729 to slin Jan 4 10:06:42 WARNING[23409]: codec_gsm.c:135 gsmtolin_framein: Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from IAX2 (20)? Jan 4 10:06:42 WARNING[23409]: codec_gsm.c:135 gsmtolin_framein: Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from IAX2 (20)? ... Gerald

...aking progress passing it to SIP/1010-8b60 NOTICE[311316]: File channel.c, Line 1476 (ast_set_read_format): Unable to find a path from G729A to ALAW NOTICE[311316]: File channel.c, Line 1446 (ast_set_write_format): Unable to find a path from GSM to G729A WARNING[311316]: File codec_gsm.c, Line 136 (gsmtolin_framein): Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from RTP (20)? WARNING[311316]: File codec_gsm.c, Line 136 (gsmtolin_framein): Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from RTP (20)? WARNING[311316]: File codec_gsm.c, Line 136 (gsmtolin_framein): Huh?...

...\371\222\327&X\244\357\221$J\332^A\233\372\331\343$^L+L\362\333\204D\234\243Tt\325\227F\375\221\223\243G^_\211-\213\335\243I=,\354\\225d\263'\212I"\341#\207oj\272\352\325^T\206\275D\343$\214\363\262KQ\233^D^K#u\334\225\352\242\355\\227\346[Feb 24 16:07:20] WARNING[777]: codec_gsm.c:140 gsmtolin_framein: Invalid GSM data (1) [Feb 24 16:07:20] WARNING[777]: translate.c:197 framein: gsmtolin did not update samples 0 [Feb 24 16:07:20] WARNING[777]: codec_gsm.c:140 gsmtolin_framein: Invalid GSM data (1) [Feb 24 16:07:20] WARNING[777]: translate.c:197 framein: gsmtolin did not update samples 0 <sni...

...too short Nov 23 16:27:33 WARNING[1061908]: rtp.c:428 ast_rtp_read: RTP Read too short Nov 23 16:27:33 WARNING[1061908]: rtp.c:428 ast_rtp_read: RTP Read too short Nov 23 16:27:35 NOTICE[1061908]: rtp.c:489 ast_rtp_read: Unknown RTP codec 1 received Nov 23 16:27:35 WARNING[1061908]: codec_gsm.c:135 gsmtolin_framein: Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from RTP (15)? Nov 23 16:27:35 NOTICE[1061908]: channel.c:1724 ast_set_read_format: Unable to find a path from G723 to ALAW Nov 23 16:27:35 NOTICE[1061908]: channel.c:1691 ast_set_write_format: Unable to find a path from GSM to G72...

I am getting thousand of these messages in asterisk console Jun 27 12:35:55 WARNING[16496]: codec_gsm.c:194 gsmtolin_framein: Invalid GSM data And after some time the system crashes. Does anyone know why? I running Asterisk SVN-trunk-r7522 built Does it help to upgrade the system? Regards, Fredrik Jensen

...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 containing "allow=gsm" and still kept the line "allow=g729" because as I've said already incoming...

Hello, We have updated the Wiki page for Polycom phones: http://www.voip-info.org/tiki-index.php?page=Polycom+Phones We posted several configuration specs as well as a link to an admin guide for the phone. We also posted a link on there to two firmware versions for download. The official Asterisk-Polycom support website should be up and live sometime in January. If anyone has anything to add

Hi List, I am facing the reverse problem as stated here.I am using ATA 186 to make and recieve call to * through OH323 driver. When I use G711 codec in the ATA to make call then then as soon as i dial an extension the * crashes with 'segmentation fault'. But the same scenerio works fine when i use 723 codec in the ATA .I can dial the number and extension very well/(I have 723 support in

...1236360496]: File indications.c, Line 62 (playtones_release): playtones_release Jun 5 01:55:39 DEBUG[1236360496]: File channel.c, Line 1381 (ast_set_write_format): Set channel SIP/5010-d3c4 to write format 2 After that, the console is filled with: WARNING[1236360496]: File codec_gsm.c, Line 136 (gsmtolin_framein): Huh? A GSM frame that isn't a multiple of 33 or 65 bytes long from mp3_exec (320) I attempted to dig into this thing, if I used another call to <Background> (even with another format) the problem didn't show up since ast_openstream takes care of calling ast_deactivate_generator,...

...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 containing "allow=gsm" and still kept the line "allow=g729" because as I've said already incoming...