"clean shutdown" figured out: Yocto/BusyBox/Bash does not handle output redirection well, truncated output caused the appearance that pjsua_destroy did not return. My own blunder in creating a codepath that didn't release an application semaphore (that pj_mumble should not have cared about) enhanced the image of pj_destroy not returning. Sound problems still continue. ________________________________ From: pjsip [pjsip-bounces@xxxxxxxxxxxxxxx] on behalf of Brunner, Brian T. [bbrunner at gai-tronics.com] Sent: Thursday, November 20, 2014 9:53 AM To: pjsip list Subject: Re: pjsua-based-app: shutdown troubles IN MY CODE moved _disconnect_ calls to after call_hangup call added pjsua_player_destroy() added pjsua_recorder_destroy() added a sem_post() result: clean shutdown. Sound remains horrid, so the codec/bitrate question remains. Since the rest of the dump is in previous posts, I delete it here. ________________________________ From: pjsip [pjsip-bounces@xxxxxxxxxxxxxxx] on behalf of Brunner, Brian T. [bbrunner at gai-tronics.com] Sent: Wednesday, November 19, 2014 4:16 PM To: pjsip at lists.pjsip.org Subject: pjsua-based-app: shutdown troubles IN MY CODE (upon call duration exceeded) log_call_dump(LV.CallId); pjsua_conf_disconnect( LV.CallerConferenceBridgeSlot, LV.RecordPort ); pjsua_conf_disconnect( LV.CallerConferenceBridgeSlot, 0 ); pjsua_conf_disconnect( LV.PlayerConferencePortNo , LV.CallerConferenceBridgeSlot ); pjsua_call_hangup (LV.CallId, 408, &CallTimeOut, &msg_data); pjsua_call_hangup_all(); pjsua_stop_worker_threads(); pjsua_acc_del(LV.MyAcctId); pjsua_destroy(); MY ANALYSIS/GUESSWORK 3: I can't tell which codec is in use, nor whether the same codec is in use (at the same bit-rate) at both ends; the audio is horrible (screech louder than the message) 5: I wonder if I must stop the player & recorder I created. (it appears so) ________________________________ ---------------------------------------------------------------------------------------------------------------------------- Confidentiality Requirement: This communication, including any attachment(s), may contain confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that you have received this communication in error and any unauthorized review, use, disclosure, dissemination, distribution or copying of it or its contents is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or e-mail and destroy all copies of this communication and any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20141120/01f5f5e0/attachment.html>
