search

zeined / idoubs

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

Do not receive incoming calls #130

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Installed and using idoubs on iphone 5, ios 6, sim and device and using a 
standalone voip client for incoming calls that uses a Peer To Peer connection.
2. Start testAudiocall and call another P2P network device, outbound call works 
fine, hang up.
3. Use other device to make an incoming call back to iPhone or Sim, iDoubs does 
not answer (or detect a connection).

What is the expected output? What do you see instead?

Expected Local Notification or alert

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

ios6, latest SVN of iDoubs/ ios-ngn-stack, Doubango

Please provide any additional information below.
I know that the interface is receiving the request from Wireshark:

192.168.0.18 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.250:5060;rport;branch=z9hG4bK1614948075
From: "Door1" <sip:Door1@192.168.0.250>;tag=184110336
To: <sip:192.168.0.18>
Call-ID: 520907185
CSeq: 20 INVITE
Contact: <sip:Door1@192.168.0.250:5060>
Content-Type: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, REFER, OPTIONS, INFO, REGISTER
Max-Forwards: 70
User-Agent: VoIP Guard
Subject: Phone call
Expires: 120
Content-Length:   413

v=0
o=- 123456 654321 IN IP4 192.168.0.250
s=A conversation
c=IN IP4 192.168.0.250
t=0 0
m=audio 7078 RTP/AVP 0 8 2 3 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:2 G726-32/8000/1
a=rtpmap:3 GSM/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
m=video 9078 RTP/AVP 34 102
a=rtpmap:34 H263/90000
a=rtpmap:102 H264/90000
a=fmtp:102 profile-level-id=428014;packetization-mode=0

But the device or Sim ignores this invite, one thing to note, immediately after 
the INVITE is received on the port , wireshark detects a failed ICMP ping to 
the invite source.

Would appreciate any help in getting this working, also note, the service I am 
building uses a Peer to Peer connection.

Best regards,

Iain

Original issue reported on code.google.com by i...@appit.co.uk on 31 Oct 2012 at 12:20

GoogleCodeExporter commented 8 years ago 
An update on this, I have a socket listener in the app, to check if the 
connection is made and it is, as soon as I try to connect to the phone from the 
remote party I detect the socket connection and print this out:
Connect on port:5060 from host:192.168.0.250 with Data: INVITE sip:192.168.0.3 
SIP/2.0
Via: SIP/2.0/UDP 192.168.0.250:5060;rport;branch=z9hG4bK1945122293
From: "Door1" <sip:Door1@192.168.0.250>;tag=909883863
To: <sip:192.168.0.3>
Call-ID: 1118047131
CSeq: 20 INVITE
Contact: <sip:Door1@192.168.0.250:5060>
Content-Type: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, REFER, OPTIONS, INFO, REGISTER
Max-Forwards: 70
User-Agent: VoIP Guard
Subject: Phone call
Expires: 120
Content-Length:   413

v=0
o=- 123456 654321 IN IP4 192.168.0.250
s=A conversation
c=IN IP4 192.168.0.250
t=0 0
m=audio 7078 RTP/AVP 0 8 2 3 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:2 G726-32/8000/1
a=rtpmap:3 GSM/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
m=video 9078 RTP/AVP 34 102
a=rtpmap:34 H263/90000
a=rtpmap:102 H264/90000
a=fmtp:102 profile-level-id=428014;packetization-mode=0

Why wont the app answer the call?  I'm pretty sure that this is a simple one to 
answer, if you have the experience with this code.

Many thanks in advance for pointing me in the right direction.

Iain

Original comment by i...@appit.co.uk on 31 Oct 2012 at 4:36

GoogleCodeExporter commented 8 years ago

Original comment by boss...@yahoo.fr on 5 Nov 2012 at 6:26

GoogleCodeExporter commented 8 years ago 
Why Invalid?  Clearly there is an issue, just wiping it out as invalid makes me 
think you dont really care!!!!

Original comment by i...@appit.co.uk on 5 Nov 2012 at 6:33

GoogleCodeExporter commented 8 years ago 
Invalid because there is no enough information and the explanation is confusing.
You should attach a wireshark trace instead of a single plain text INVITE 
request

Original comment by boss...@yahoo.fr on 5 Nov 2012 at 6:42

GoogleCodeExporter commented 8 years ago 
That was from wireshark.

Original comment by i...@appit.co.uk on 5 Nov 2012 at 6:43

GoogleCodeExporter commented 8 years ago 
The explanation confusing, its pretty simple to me, run the app call it over 
the local network from another device and it doesn't ring. Although when i put 
a port listener onto 5060, the protocol is being received on the port.

Original comment by i...@appit.co.uk on 5 Nov 2012 at 6:46