Warnign

Home » Asterisk Users » Warnign
Asterisk Users 10 Comments

Hi, I recently changed my version of Asterisk to 11.XX, and I see a waning with h323, with version 1.8 did not have these warning

I have connected one avaya ip office 500 h323 with asterisk and the 1.8
version did not have these messages

Oct 23 17:20:35] WARNING[7593][C-000000aa]: chan_ooh323.c:1413
ooh323_indicate: Don’t know how to indicate condition 33 on ooh323c_60
[Oct 23 17:20:35] WARNING[7593][C-000000aa]: chan_ooh323.c:1413
ooh323_indicate: Don’t know how to indicate condition 33 on ooh323c_60
— SIP/3230-000000a6 is ringing
[Oct 23 17:20:37] WARNING[7593][C-000000aa]: chan_ooh323.c:1413
ooh323_indicate: Don’t know how to indicate condition 33 on ooh323c_60

any idea?

10 thoughts on - Warnign

  • The chan_ooh323 channel driver just needs to be updated to ignore that indication condition.

    Richard

  • thnk Richard Mudgett for your quick response , but I have a question I am using the asterisk 11 with ooh323 by default, I can update it?

    2013/10/23 Richard Mudgett

  • Richard,

    And what is “condition 33” after all? Maybe it needs to be processed, not ignored.

    Thank you, Vladimir

  • 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

  • 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

  • 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

  • Hi, make the change in the file chan_h323.c and comment these lines

    // default:
    // ast_log(LOG_WARNING, “OH323: Don’t know how to indicate condition %d on %s\n”, condition, token);
    // break;

    but the message keeps coming, I’m doing something wrong?

    WARNING[19460][C-00000000]: chan_ooh323.c:1413 ooh323_indicate: Don’t know how to indicate condition 33

    2013/10/24 Vladimir Mikhelson

  • Vladimir Mikhelson mikhelson.com> writes:

                                                                           

    Hi! Thanks a lot for your post!!!!
    Have same problem with asterisk 11.8.1 + dongle. I Have this message – “WARNING[8081][C-00000007]: channel.c:1002
    channel_indicate: [Dongle/gsm-mega-08-0100000007] Don’t know how to indicate condition 33”. So i find a file named channel.c and comment like that –
    /* default:
    ast_log (LOG_WARNING, “[%s] Don’t know how to indicate condition %d\n”, ast_channel_name(channel), condition);
    res = -1;
    break; */
    And it’s work =) Warning is gone….