In ooEndCall call state is – OO_CALL_CLEAR (incoming, ooh323c_1)

Home » Asterisk Users » In ooEndCall call state is – OO_CALL_CLEAR (incoming, ooh323c_1)
Asterisk Users 4 Comments

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 box.

Looking through the ooh323 log below, I suspect this stems from the “Error:Failed to enqueue ReleaseComplete message to outbound queue.(incoming, ooh323c_1)” message – but we don’t don’t see enough H323 installations to dig deeper. Can someone offer some suggested causes and resolutions?

Thanks!

4 thoughts on - In ooEndCall call state is – OO_CALL_CLEAR (incoming, ooh323c_1)

  • 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

  • Vladimir:

    Thanks for that! Does the response mean that the fix is already in the latest Asterisk 1.8 ditribution?

    I would prefer not to upgrade this site to 1.8 (since it requires retesting lots of customer code)…so a patch would be ideal.

    Thanks,
    Michelle
    ________________________________
    Sent: Wednesday, June 06, 2012 11:18 AM

    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

    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 box.

    Looking through the ooh323 log below, I suspect this stems from the “Error:Failed to enqueue ReleaseComplete message to outbound queue.(incoming, ooh323c_1)” message – but we don’t don’t see enough H323 installations to dig deeper. Can someone offer some suggested causes and resolutions?

    Thanks!

  • Michelle,

    I have re-sent your message to the developer. I will let you know when
    I get a reply.

    I do believe this fix is incorporated in 1.8, and all ongoing
    development is done in 1.8+

    Thank you,
    Vladimir

  • Michelle,

    Here is the developer’s reply.

    -Vladimir

    Hi Vladimir,

    Your reply is correct but you can add few more things.

    Standard addons of 1.6 contain old (non reworked) version of ooh323 that
    is unusable in production (IMHO).

    Please ask Michelle to specify the exact version of Asterisk and I will
    send a private link to the patch for reworked ooh323 of required 1.6.

    I can’t publish this link due to Digium’s development policy.