Kamailio + idoubs doesn't work

[GoogleCodeExporter]

a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (wireshark) or Android log (DDMS output)
if you want quick response

What steps will reproduce the problem?
1. Open your idoubs client and login to the kamailio server (connected to WiFi)
2. Make an on net call directly to another connected phone (also with idoubs)
3. The other phone doesn't ring

What is the expected output? What do you see instead?
The phone should present an incoming call but it doesn't

What version of the product or source code revision are you using? On what
operating system?

I'm using the latest revision of doubango(r675) and idoubs (r193).
iOS 5.0.1 on both iPhone 4 phones.

Please provide any additional information below.
I have tested this and if you use any other client it does work, for example:

idoubs -> x (works)
x -> idoubs (works)
idoubs - > idoubs (doesn't work)

I've looked this problem over a couple of dozen times even with my colleague 
the network engineer but we couldn't find what the cause of this problem is. I 
included two wireshark logs; the first (idoubs.rtf) is idoubs -> idoubs test 
which doesn't work and the second (linphone.rtf) is linphone -> linphone which 
does work.

It has something to do with the way the server is configured and how the 
clients have to act to this but regarding the fact that all possibilities work 
but not idoubs -> idoubs it has to be a problem with idoubs itself. If I test 
this with my own client, built on the doubango framework, I do get an incoming 
call screen but when I answer the call the other party doesn't know I did so it 
keeps ringing.

It's a very specific bug so I really hope you could assist me on this problem.

Original issue reported on code.google.com by nightfox...@gmail.com on 3 Feb 2012 at 2:21

Attachments:

• idoubs.rtf
• linphone.rtf

[GoogleCodeExporter]

You should provide wireshark trace with both SIP and RTP.

Original comment by boss...@yahoo.fr on 15 Feb 2012 at 12:24

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 19 Feb 2012 at 4:12

• Changed state: Invalid