Re: [Asterisk-Users] RE: MeetMe freezes machine with Junghanns

2006-03-24 Thread Henning Holtschneider
On Thursday 23 March 2006 22:14, BJ Weschke wrote:

>  There's been two very recent commits (one less than an hour ago) that
> may very well correct your issues.

The patch at http://bugs.digium.com/view.php?id=5884 fixes the problem!

Cheers,
Henning Holtschneider
--
LocaNet oHG - http://www.loca.net
Lindemannstrasse 81, D-44137 Dortmund
tel +49 231 91596-25, fax +49 231 91596-55


pgpoDln7bEb6t.pgp
Description: PGP signature
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] RE: MeetMe freezes machine with Junghanns

2006-03-23 Thread BJ Weschke
On 3/23/06, Brent Torrenga <[EMAIL PROTECTED]> wrote:
> Dollars to donuts it is related to these two posts, but no one seems to know
> where or why it happens - this issue doesn't seem to be related to one
> specific piece of hardware:
>
> Post 1)
>
> *
> Anyone ever seen MeetMe cause * to crash? Specifically, it happens
> consistantly if someone begins to enter a conference and then decides to
> hangup while Allison is introducing them - like playing back
> "conf-onlyperson". This has been seen with the MeetMe participant connecting
> via IAX and SIP (not saying it doesn't happen with Zap, just that I haven't
> seen it).
>
> The box is * 1.2.5, Zaptel 1.2.4, a TDM400P loaded with 3xFXO cards,
> Mandriva 2006 Free.
>
> Symptoms of the crash: once the participant hangs up, the CLI seems to
> freeze. One more call instance can be initiated, and the system will seize
> within seconds (for instance, an audio prompt will deteriorate and then stop
> dead). This behavior reminds me of the memory leak issue and time bomb bug,
> perhaps they do the same damage as this.
>
> Solution right now is to disable MeetMe, which isn't a solution as much as
> an amputation. Anyways, here is the CLI output, note the WARNING:
>
> alpha*CLI>
> -- Executing Goto("SIP/Brent_ring-4473", "conferences|900|1") in new stack
> -- Goto (conferences,900,1)
> -- Executing MeetMe("SIP/Brent_ring-4473", "900|sMi|1234") in new stack ==
> Parsing '/etc/asterisk/meetme.conf': Found
> -- Created MeetMe conference 1023 for conference '900'
> -- Recording
> -- Playing 'vm-rec-name' (language 'en') Mar 15 16:44:38 WARNING[24014]:
> file.cL584 ast_readaudio_callback: Failed to write frame
> -- Playing 'conf-onlyperson' (language 'en') Alpha*CLI>
> *
>
> Post 2)
>
> *
> Thank you for the hint. Now finaly I can 100% reproduce the problem. Yes, if
> I hang up during Playing 'conf-onlyperson' my machine freezes. It's not a
> GSM Enconding problem as I suspected first, this happens with every
> encoding.
>
> magma*CLI>
>-- Executing Answer("SIP/11-9d7c", "") in new stack
>-- Executing MeetMe("SIP/11-9d7c", "555") in new stack
>-- Created MeetMe conference 1023 for conference '555'
>-- Playing 'conf-onlyperson' (language 'de') magma*CLI>
>
> Freeze!
>

 There's been two very recent commits (one less than an hour ago) that
may very well correct your issues.

--
Bird's The Word Technologies, Inc.
http://www.btwtech.com/
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[Asterisk-Users] RE: MeetMe freezes machine with Junghanns

2006-03-23 Thread Brent Torrenga
Dollars to donuts it is related to these two posts, but no one seems to know
where or why it happens - this issue doesn't seem to be related to one
specific piece of hardware:

Post 1)

*
Anyone ever seen MeetMe cause * to crash? Specifically, it happens
consistantly if someone begins to enter a conference and then decides to
hangup while Allison is introducing them - like playing back
"conf-onlyperson". This has been seen with the MeetMe participant connecting
via IAX and SIP (not saying it doesn't happen with Zap, just that I haven't
seen it).

The box is * 1.2.5, Zaptel 1.2.4, a TDM400P loaded with 3xFXO cards,
Mandriva 2006 Free.

Symptoms of the crash: once the participant hangs up, the CLI seems to
freeze. One more call instance can be initiated, and the system will seize
within seconds (for instance, an audio prompt will deteriorate and then stop
dead). This behavior reminds me of the memory leak issue and time bomb bug,
perhaps they do the same damage as this.

Solution right now is to disable MeetMe, which isn't a solution as much as
an amputation. Anyways, here is the CLI output, note the WARNING:

alpha*CLI>
-- Executing Goto("SIP/Brent_ring-4473", "conferences|900|1") in new stack
-- Goto (conferences,900,1)
-- Executing MeetMe("SIP/Brent_ring-4473", "900|sMi|1234") in new stack ==
Parsing '/etc/asterisk/meetme.conf': Found
-- Created MeetMe conference 1023 for conference '900'
-- Recording
-- Playing 'vm-rec-name' (language 'en') Mar 15 16:44:38 WARNING[24014]:
file.cL584 ast_readaudio_callback: Failed to write frame
-- Playing 'conf-onlyperson' (language 'en') Alpha*CLI>
*

Post 2)

*
Thank you for the hint. Now finaly I can 100% reproduce the problem. Yes, if
I hang up during Playing 'conf-onlyperson' my machine freezes. It's not a
GSM Enconding problem as I suspected first, this happens with every
encoding.

magma*CLI>
-- Executing Answer("SIP/11-9d7c", "") in new stack
-- Executing MeetMe("SIP/11-9d7c", "555") in new stack
-- Created MeetMe conference 1023 for conference '555'
-- Playing 'conf-onlyperson' (language 'de') magma*CLI>

Freeze!

Any other who can reproduce that freeze?

Kernel 2.6.15 / * 1.2.5 / ztdummy 1.2.4
**


Sincerely,

Brent A. Torrenga
[EMAIL PROTECTED]

Torrenga Engineering, Inc.
907 Ridge Road
Munster, Indiana 46321-1771

219.836.8918x325 Voice
219.836.1138 Facsimile
www.torrenga.com

___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users