Stun server causing calls not to properly answer then disconnect

[GoogleCodeExporter]

What steps will reproduce the problem?
1.add OSTN account with ostel.me details
2. have zrtp enabled
3.enable stun server (stun.counterpath.com) defualt
4. call contact also using OSTN with ostel.me
5. answer call

What is the expected output? 
After answering the call should stay active until user hangs up

What do you see instead?

call remains listed as "incoming call" even though you can hear each other and 
verify ZRTP SAS. Disconects after approx 30 seconds. Even after swipping to 
answer and opening the box with 3 dots and selecting answer the call still 
lists as incoming.

THIS DOES NOT HAPPEN WITH STUN SERVER DISABLED

What version of the product are you using? 

both phones running 0.04-04 r1916

On what operating system?
my phone is using android 4.0.4

Please provide any additional information below.

If stun is disabled no sound
Using wifi to test

Original issue reported on code.google.com by aliz.ja...@gmail.com on 28 Sep 2012 at 3:27

[GoogleCodeExporter]

I have same issue at my GSIII with 0.04-04 r1916 for 3G and wifi.

Original comment by ovdiyuk on 9 Oct 2012 at 7:24

[GoogleCodeExporter]

I can confirm this issue.

Samsung Galaxy SIII i9300
Android 4.1.1
CsipSimple 0.04-04 r1916

ZRTP calls on ostel.me and intimi.ca are dropped after 31 seconds when using 
stun. 

1. OSTN with ostel.me or intimi.ca
2. Use the OSTN preset. Enter User name, Password, server.
3. ZRTP will auto enable when the OSTN preset is used. 
4. Enable stun server. Have only tried with stun.counterpath.com
5. Call another user on the same network from 1. 
6. Call is dropped after exactly 31 seconds. 

There are no issues with non ZRTP calls on other servers. When stun is disabled 
phone calls using ZRTP work perfectly as long as no NAT needs to be 
transversed. Tested with 3G <-> 3G, wifi <-> wifi, 3G <-> wifi. 

Need to test with other stun servers. 

Original comment by erik.ad...@gmail.com on 14 Nov 2012 at 6:43

[GoogleCodeExporter]

I've change a parameter in build that should help with some device and this 
kind of problems.
Can you try latest nightly build (http://nightlies.csipsimple.com/trunk/) and 
let me know if it helps.
Thanks

Original comment by r3gis...@gmail.com on 4 Dec 2012 at 10:09

• Changed state: Fixed

[GoogleCodeExporter]

Same problem here with CsipSimple 0.04-04 r1916 on Samsung S3 BUT solved with 
latest nightly 0.04-05 r1916 !!!. Thanks!

Original comment by pedroarg...@gmail.com on 23 Mar 2013 at 7:08