search

tuannv19 / idoubs

Automatically exported from code.google.com/p/idoubs
0 stars 0 forks source link

Incoming Call #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Dialed from Bria 3 on Mac to call to idoub app on iPhone
2. Asterisk Server attempted to invite idoubs app but no response from it
3. Bria 3 kill the call due to no response from idoubs app

What is the expected output? What do you see instead?
I would expect to see idoubs to answer the SIP invitation and get this 
connected to Bria 3 or any other applications

What version of the product are you using? On what operating system?
Mac 10.6, Xcode 4.3.2, IOS 4.0

Please provide any additional information below.

Original issue reported on code.google.com by i...@powervrs.com on 6 Jun 2011 at 12:18

GoogleCodeExporter commented 9 years ago 
There is no reason not to work.
Please provide the source code revision.
Please also attach network trace (wireshark).

Original comment by boss...@yahoo.fr on 6 Jun 2011 at 12:21

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
The first capture (Sip Invite Issue) only shows the Bria part. Your server 
returns 503 errors. So I cannot say why your server returns this errors.
The second capture (Sip response) isn't a valid wireshark file.

Is the application running in the background? Which transport are you using 
(TCP/UDP)?
Please provide the SVN revision of your source code.

Original comment by boss...@yahoo.fr on 6 Jun 2011 at 12:44

GoogleCodeExporter commented 9 years ago 
I think there is a problem in your configuration. We have made many tests for 
the incoming calls and all is working as expected.
To get help, you have to give us much more information: svn revision, transport 
type, nat traversal enabled or not, simulator or real device, application on 
background or foreground etc etc

Original comment by boss...@yahoo.fr on 6 Jun 2011 at 12:47

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I'm not using 'doubango.com' at all. I'm using a public network.

Original comment by boss...@yahoo.fr on 6 Jun 2011 at 5:50

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hello,

I had looked closely at that log in XCode

***ERROR: function: "tnet_dns_resolvconf_parse()" 
file......./mydoubs/iPhone/idoubs/branches/2.0/ios-ngn-stack/../../../../../doub
ango/branches/2.0/doubango/tinyNET/src/dns/tnet_dns_resolvconf.c" 
line: "169" 

is  that tnet_dnsresolvconf_parse() error is part of responsible to cause the 
incoming call issue ? 
MSG: Failed to open /etc/resolv.conf.

Original comment by patrickw...@gmail.com on 8 Jun 2011 at 11:27

GoogleCodeExporter commented 9 years ago 
I had tested iPhone to receive the incoming call within private IP domain 
(subnet network of 192.168.0.xxx) instead of going out of Private into Public 
IP domains (subnet network of 12.3.220.xxx) and then go back into Private IP 
domain. It showed the same situation as going out of Private IP domain and go 
back into it. I tested with other SIP client applications they are working very 
well along with the backend servers.

Original comment by patrickw...@gmail.com on 8 Jun 2011 at 11:40

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 23 Jul 2011 at 4:56