Re: [asterisk-users] OOh323 log fills with : In ooEndCall call state is - OO_CALL_CLEAR (incoming, ooh323c_1)

2012-06-07 Thread Vladimir Mikhelson
] On Behalf Of Vladimir Mikhelson [v...@mikhelson.com] *Sent:* Wednesday, June 06, 2012 11:18 AM *To:* Asterisk Users List *Subject:* Re: [asterisk-users] OOh323 log fills with : In ooEndCall call state is - OO_CALL_CLEAR (incoming, ooh323c_1) Michelle, I forwarded your message to the OOH323

Re: [asterisk-users] OOh323 log fills with : In ooEndCall call state is - OO_CALL_CLEAR (incoming, ooh323c_1)

2012-06-06 Thread Vladimir Mikhelson
Michelle, I forwarded your message to the OOH323 maintainer / developer. Here is his reply. Vladimir, there is 1.6 asterisk which is unsupported already, you can recommend upgrade to 1.8 or higher version. I can produce patch for 1.6 but upgrade is better way Thank you, Vladimir On

Re: [asterisk-users] OOh323 log fills with : In ooEndCall call state is - OO_CALL_CLEAR (incoming, ooh323c_1)

2012-06-06 Thread Michelle Dupuis
From: asterisk-users-boun...@lists.digium.com [asterisk-users-boun...@lists.digium.com] On Behalf Of Vladimir Mikhelson [v...@mikhelson.com] Sent: Wednesday, June 06, 2012 11:18 AM To: Asterisk Users List Subject: Re: [asterisk-users] OOh323 log fills with : In ooEndCall call state

Re: [asterisk-users] OOh323 log fills with : In ooEndCall call state is - OO_CALL_CLEAR (incoming, ooh323c_1)

2012-06-06 Thread Vladimir Mikhelson
*From:* asterisk-users-boun...@lists.digium.com [asterisk-users-boun...@lists.digium.com] On Behalf Of Vladimir Mikhelson [v...@mikhelson.com] *Sent:* Wednesday, June 06, 2012 11:18 AM *To:* Asterisk Users List *Subject:* Re: [asterisk-users] OOh323 log fills with : In ooEndCall call

[asterisk-users] OOh323 log fills with : In ooEndCall call state is - OO_CALL_CLEAR (incoming, ooh323c_1)

2012-06-05 Thread Michelle Dupuis
We have an Ast 1.6 installation which is connected to an Avaya using ooh323. Something is causing the log to fill with In ooEndCall call state is - OO_CALL_CLEAR (incoming, ooh323c_1) messages every 100ms. This causes the log to grow to 300MB in just 5 minutes, which eventually overloads the