[asterisk-users] warnign

Vladimir Mikhelson vlad at mikhelson.com
Thu Oct 24 10:53:57 CDT 2013


Hi,

Here is the reply from the developer as to what can be done immediately
to remove the offending logging.

"He can just ignore these messages, they say that chan_ooh323 don't
known indication signal 33 (AST_CONTROL_PVT_CAUSE_CODE) and processing
of this signal isn't mandatory.

If he would to remove this messages he can comment ast_log string in
chan_ooh323 in ooh323_indicate function on the bottom of function:

       default:
                ast_log(LOG_WARNING, "Don't know how to indicate
condition %d on %s\n",
                                                                       
condition, callToken);"

Ultimately the developer will take of the issue properly.

Thank you,
Vladimir





On 10/24/2013 10:04 AM, troxlinux wrote:
> thnk Matthew  , would be great if someone could add this to the h323
> channel, if I could, I would, but the saddest thing is that I will
> have to be seeing these warning on my console
>
>
> 2013/10/23 Matthew Jordan <mjordan at digium.com <mailto:mjordan at digium.com>>
>
>
>     On Wed, Oct 23, 2013 at 7:12 PM, Vladimir Mikhelson
>     <vlad at mikhelson.com <mailto:vlad at mikhelson.com>> wrote:
>
>         Richard,
>
>         And what is "condition 33" after all?  Maybe it needs to be
>         processed, not ignored.
>
>
>     The various indication control frames are defined in frames.h.
>     Frame type 33 was added to Asterisk 11:
>
>     AST_CONTROL_PVT_CAUSE_CODE = 33, /*!< Contains an update to the
>     protocol-specific cause-code stored for branching dials */
>      
>     This is part of the hangup cause feature that was added to
>     Asterisk 11. When a channel driver raises this control frame, the
>     channel core uses the information in the frame to update protocol
>     specific cause code information. Channel drivers are supposed to
>     indicate to the core that they don't want to handle that frame,
>     i.e., return -1.
>
>     So Richard is correct: chan_ooh323 should, in ooh323_indicate,
>     handle the frame by returning -1.
>
>     Actually raising the frame to pass a channel technology specific
>     hangup cause code is completely up to the channel driver. Not all
>     channel drivers support it; if someone wanted to add that
>     functionality to chan_ooh323 that'd be great; but it's completely
>     different than the condition that the OP is seeing.
>
>     Matt
>
>     -- 
>     Matthew Jordan
>     Digium, Inc. | Engineering Manager
>     445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>     Check us out at: http://digium.com & http://asterisk.org
>
>     --
>     _____________________________________________________________________
>     -- 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
>
>
>
>
> -- 
> rickygm
>
> http://gnuforever.homelinux.com
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20131024/0f69064c/attachment.html>


More information about the asterisk-users mailing list