#2280 Android 4.2.2 Outgoing call problem + broken OpenSL-ES support

[Anonymous]

Originally created by: v...@scienceprousa.com

What steps will reproduce the problem?
1. setup an account with tls and use it from a non-local ip (lan works)
2. register
3. make an outgoing call (fails firstly because of OpenSL not working but even after changing to Java still fails)

What is the expected output? What do you see instead?
Outgoing call over tls works
instead, it unregisters and won't call OR after changing audio settings to Java hangs up and shows "503 / End Of File(PJ_EEOF)"

What version of the product are you using? On what operating system?
[r2156] (nightly) on Galaxy S2 CM10.1 Jelly Bean 4.2.2-- has also had identical problem on other roms.

Please provide any additional information below.
I have tried various troubleshooting steps (disabling/enabling every combination of STUN/TURN/ICE), reading the logs myself, etc.  It seems to work locally but not externally.  On Asterisk I receive:

WARNING chan_sip.c:3618 __sip_xmit: sip_xmit of 0x7fe5f4054630 (len 748) to xxx.xxx.xxx.xx:33936 returned -2: Success

WARNING chan_sip.c:3618 __sip_xmit: sip_xmit of 0x7fe5f4054630 (len 748) to xxx.xxx.xxx.xx:33936 returned -2: No such file or directory

Thanks for any help

[Anonymous]

Originally posted by: can.oezd...@gmail.com

I have the same problem (PJ_EEOF) on my Galaxy S2 Plus (Android 4.1).
I'm using TLS with ZRTP.

On my HTC Desire S (Android 2.3.5) the same configuration works without errors.
Will this error not be fixed in the market version builds?

[Anonymous]

Originally posted by: bri...@warped-minds.com

Also getting same PJ_EEOF from market version on Galaxy Note 3, TLS/SRTP. Workaround in #2 doesn't have any effect.

[Anonymous]

Originally posted by: pavel.tr...@gmail.com

Hey, men, maybe I've found the cause... It seems that some message is growing too much to be transmitted over TLS... I've found it by "trial & error" method - first I found, that with just one codec permitted, it works, while for more codecs it doesn't. Then I tried to turn on compact SIP headers, and since then, it works for me even with more (tried with 3) codecs! Give it a try as well, maybe it will help you too..
  Regards, Pavel

[Anonymous]

Originally posted by: patrick....@gmail.com

AFAICT in the latest nightly rev 2416 the problem still exists on Samsung S4 Mini LTE with Android 4.2.2 and Nexus S with Cyanogenmod CM11 M7 when using TLS/SRTP.

What works for me:
- TLS & SRTP enabled/mandatory
- compact SIP headers enabled
- only one codec (g722)
- STUN enabled

What doesn't work for me:
- the settings above
- and ICE enabled
- and/or more codecs enabled

ICE adds a lot of info to the invite and to some extent so does adding a bunch of codecs. Is there perhaps an array or buffer too small?

FWIW Asterisk 12 also uses PJSip and I'm not aware of a similar problem. If you have any questions or need help testing stuff please let me know.

Thank you for all your hard work!

[Anonymous]

Originally posted by: patrick....@gmail.com

The nightly [r2423] now works for me. With TLS & SRTP enforced, all codecs enabled, compact SIP headers off, STUN enabled I no longer see the PJ_EEOF error. Tested on a Nexus S with CM7 against Asterisk 11.10.2 with the tlsBigSDP.patch from https://issues.asterisk.org/jira/browse/ASTERISK-18345