CSipSimple v15 and v16 Auto-Answer Mode

[GoogleCodeExporter]

We have csipsimple softphone register on an Innvovaphone pbx v9 hf19.

We are using the Innovaphone TSP HF7(8124) to start a call to a specific 
extension.

Test was made with v15 and v16 respectively on Android 4.0.4 and 4.1.1?

CsipSimple in v15 is not working. CsipSimple v16 is working.

At Innovaphone tech-support we received the following explenation of this 
strange behavour:

"Here is an example of the INVITE sent by the PBX for a CTI Call: 

INVITE sip:TEST001@10.56.14.12:47059;ob SIP/2.0 
Via: SIP/2.0/UDP 172.17.13.220:5060;branch=z9hG4bK-56E030CC;rport 
From: <sip:anonymous@172.17.13.220>;tag=2318020383 
To: <sip:6398@172.17.13.220;user=phone> 
Call-ID: 5417b09de909d311839d0090332b0087@172.17.13.220 
CSeq: 4137364 INVITE 
Contact: <sip:anonymous@172.17.13.220:5060;transport=UDP> 
Allow: 
REGISTER,SUBSCRIBE,NOTIFY,INVITE,ACK,PRACK,OPTIONS,BYE,CANCEL,REFER,INFO,UPDATE,
PUBLISH
Call-Info: <sip:domain>;answer-after=0 
Content-Length: 173 
Content-Type: application/sdp 
Max-Forwards: 63 
Supported: 100rel,replaces,privacy,timer,from-change,histinfo,answermode 
User-Agent: (innovaphone IP0010/9.00 hotfix19 [9.061180/9061180/610]) 
Answer-Mode: Auto 
P-Sig-Options: Sending-Complete 

v=0 
o=- 92 1 IN IP4 172.17.13.220 
s=- 
t=0 0 
m=audio 1 RTP/AVP 8 0 18 13 
c=IN IP4 172.17.13.220 
a=fmtp:18 annexb=no 
a=ptime:60 
a=silenceSupp:off - - - - 
a=sendrecv 

What this call have from unique/different than normal direct calls is the 
"Answer-Mode: Auto" and also the "From" field as anonymous (From: 
<sip:anonymous@172.17.13.220>;tag=2318020383). 

Now the SIP device that receives this call must support the "Answer-Mode: Auto" 
in order to work. 

In your non-working cases the SIP device doesn't reject the call with Forbidden 
or not supported message, he just doesn't reply to it. What could let us think 
it's a network/connectivity problem singe we got no answer to our retries. 
However you have a working case for a device in the same network and if you can 
do direct calls then it's not a connectivity problem. The SIP device just 
ignore this type of call and gives no answer to it. 

Your solution, get SIP devices that support "Answer-Mode: Auto" specifically. "

Do you think we can get this working with CsipSimple v15 (Android 4.0.4) as for 
CsipSimple v16 (Android 4.1.1)?

Thanks a lot.

Best regards,
  John

Original issue reported on code.google.com by swlinksrl on 17 Dec 2012 at 4:58

[GoogleCodeExporter]

Hi,

CSipSimple has no version per android api level. I didn't understand first what 
you called v15 vs v16 ;)

So it should work the same way with android 4.0.4 and 4.1.1.

If not, the issue is probably elsewhere.
Could you try latest nightly build version :
http://nightlies.csipsimple.com/trunk/CSipSimple-latest-trunk.apk
current latest version is r2028.

Some clue about the problem :
 - The Answer-Mode header as sent by the server is currently ignore by the app. What's supported in the Call-Info header. 
*But* anyway should not impact the fact there is an incoming call. It will not 
auto-reply, but should ring normally.
 - The application if there is some matching codec will ring. If no matching codecs it will reply with a sip error code. So it's weird you have no reply.
 - There is a known bug on some ROM (custom unstable rom based on cyanogen) with the audio layer. It could produce symptoms you describe. This has been worked around in latest nightly build. But it's definitely a bug on cyano like roms.
 - To know exactly what is going wrong it could be interesting to have logs from the app (see http://code.google.com/p/csipsimple/wiki/HowToCollectLogs?wl=en wiki page)

Thanks 

Original comment by r3gis...@gmail.com on 7 Jan 2013 at 5:51

• Changed state: Need-Details

[GoogleCodeExporter]

Sorry for version v15 e v16 I meant 0.04-04 r1915 and 0.04-04 r1916 as shown in 
the about box of the application.

We will give a try at the new version in the coming days and inform you about 
the test results.

Thanks a lot for helping us.

Original comment by swlinksrl on 8 Jan 2013 at 11:31

[GoogleCodeExporter]

You can download the required log file from the following link

http://www.rarodevelop.net/data/_uploaded/downloads/logs_13-01-08_131056.txt

You should already have received it through your cSipSimple log interface too.

Thanks.

Original comment by swlinksrl on 8 Jan 2013 at 3:03

[GoogleCodeExporter]

Thanks for the logs.

From logs reading it appears that no invite packets are received by the app. It 
only receive the cancel packet.

What I see interesting in your logs comparing to first invite sample you copy 
pasted here from server is that IP range seems different.
From your server something is sent to 10.56.x.x
While from csipsimple it seems registered on a 192.168.x.x IP addressing.

Apparently you de-activated the "Allow contact rewrite" option. Maybe it could 
be interesting to keep it active. (If your sip server doesn't support inline 
contact de-registration, try to enable "legacy" contact rewrite method)

Original comment by r3gis...@gmail.com on 9 Jan 2013 at 11:12