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

Vladimir Mikhelson vlad at mikhelson.com
Wed Jun 6 10:18:00 CDT 2012


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 6/5/2012 8:58 AM, Michelle Dupuis wrote:
> 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!
>  
>  
> ---------Date 06/01/12---------
> 02:45:33:447  New connection at H225 receiver
> 02:45:33:447  Created a new call (incoming, ooh323c_1)
> 02:45:33:463  Receiving H.2250 message (incoming, ooh323c_1)
> 02:45:33:463  H.2250 message length is 12
> 02:45:33:463  Received Q.931 message: (incoming, ooh323c_1)
> 02:45:33:463  Received H.2250 Message = {
> 02:45:33:463     protocolDiscriminator = 8
> 02:45:33:463     callReference = 0
> 02:45:33:463     from = originator
> 02:45:33:463     messageType = 7d
> 02:45:33:464     Cause IE = {
> 02:45:33:464        Q931NormalUnspecified
> 02:45:33:464     }
> 02:45:33:464  No UserUser IE found in ooDecodeUUIE
> 02:45:33:464  Error:Failed to decode received H.2250 message.
> (incoming, ooh323c_1)
> 02:45:33:464  Decoded Q931 message (incoming, ooh323c_1)
> 02:45:33:464  }
> 02:45:33:464  ERROR:Failed ooH2250Receive - Clearing call (incoming,
> ooh323c_1)
> 02:45:33:464  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:33:464  Building Release Complete message to send(incoming,
> ooh323c_1)
> 02:45:33:464  Built Release Complete message (incoming, ooh323c_1)
> 02:45:33:479  Asn1Error: -4 at ooh323c/src/encode.c:584
> 02:45:33:479  ERROR: UserInfo encoding failed
> 02:45:33:479  Error:Failed to encode uuie. (incoming, ooh323c_1)
> 02:45:33:479  Error:Failed to encode H225 message. (incoming, ooh323c_1)
> 02:45:33:479  Error:Failed to enqueue ReleaseComplete message to
> outbound queue.(incoming, ooh323c_1)
> 02:45:33:479  Receiving H.2250 message (incoming, ooh323c_1)
> 02:45:33:479  H.2250 message length is 12
> 02:45:33:479  Received Q.931 message: (incoming, ooh323c_1)
> 02:45:33:479  Received H.2250 Message = {
> 02:45:33:479     protocolDiscriminator = 8
> 02:45:33:479     callReference = 0
> 02:45:33:479     from = originator
> 02:45:33:479     messageType = 7d
> 02:45:33:479     Cause IE = {
> 02:45:33:479        Q931NormalCallClearing
> 02:45:33:479     }
> 02:45:33:479  No UserUser IE found in ooDecodeUUIE
> 02:45:33:479  Error:Failed to decode received H.2250 message.
> (incoming, ooh323c_1)
> 02:45:33:479  Decoded Q931 message (incoming, ooh323c_1)
> 02:45:33:479  }
> 02:45:33:479  ERROR:Failed ooH2250Receive - Clearing call (incoming,
> ooh323c_1)
> 02:45:33:479  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:33:579  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:33:679  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:33:779  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:33:879  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:33:979  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:079  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:179  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:279  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:379  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:479  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:579  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:679  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:779  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:879  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:34:979  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:079  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:179  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:279  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:379  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:479  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:579  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:679  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:779  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:879  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:35:979  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:36:079  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:36:179  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:36:279  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:36:379  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
> 02:45:36:479  In ooEndCall call state is - OO_CALL_CLEAR (incoming,
> ooh323c_1)
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>                http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20120606/7bf36952/attachment.htm>


More information about the asterisk-users mailing list