Conference Asserts in Release Build

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am getting an assertion that end the program from conference.c in release
build.  The code below is for muting the call and is in the main thread.
This seems to happen when the call disconnects somewhere in-between the
validation and the actual call to pjsua_conf_adjust_tx_level.

 

 

if (pjsua_call_is_active( call_id))
// Valid call

if (pjsua_call_get_info(call_id, &info)   == PJ_SUCCESS)
// Got structure

if (info.state ==  PJSIP_INV_STATE_CONFIRMED)
// Connected

                  if (pjsua_conf_adjust_tx_level(info.conf_slot,0)==
PJ_SUCCESS)          // Mute Call 

                  {

                        printf(">> Call TX Muted\n");

                  }

            }

      }

}

 

I get the follow assertion:

 

Assertion failed: conf->ports[slot] != ((void *)0), file
..\src\pjmedia\conferen

ce.c, line 1276

 

This application has requested the Runtime to terminate it in an unusual
way.

Please contact the application's support team for more information. 

 

Questions:

 

1) Am I muting this call in the right spot?  

2) The pj_assert works in release mode.  Should it just return an error
instead of calling the c library assert to stop the program?

3) Is there a better way to mute the call or catch this error without a stop
occurring?

 

Thank you in advance,

Archie 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080727/fcba9a69/attachment.html 


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux