-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PJSUA Android: App Crashes Due to Assertion Failure After Sending DTMF Signal #4316
Comments
When I tested it here, it seemed to work fine.
The first line seems to be missing from your log (i.e. the media should be set as inactive which would later prevent the DTMF sending). I'm not sure what the cause though, it could be due to race condition because it looked like you were trying to send DTMF when there's an incoming re-INVITE? If so, can you enable the time in your log ( |
Hi @sauwming Thanks for your help, Please find the attached log file. Let me know if you need any additional details. |
This seems to have nothing to do with DTMF since the log showed that it's been sent and it happened some ~0.5 sec before the crash:
The most likely cause is the media teardown due to the incoming re-INVITE which hasn't completed. Please test it with the latest master, in particular I believe the issue may be related to #4301. |
Describe the bug
After calling an IVR number and sending a DTMF signal using RFC2833 method, an assertion error occurs, causing the app to crash. This issue happens with only one specific IVR number, while signaling works fine for the other two numbers used for testing.
Steps to reproduce
assertion "a->addr.sa_family == PJ_AF_INET || a->addr.sa_family == PJ_AF_INET6" failed
PJSIP version
2.15.1
Context
#define PJ_CONFIG_ANDROID 1
#include <pj/config_site_sample.h>
Log, call stack, etc
The text was updated successfully, but these errors were encountered: