search

JagannathS / webrtc2sip

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

rtcweb breaker selecting wrong IP for SDP #65

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Install per technical guide
2.have more than 1 ethernet device on server (I have 3)
3.config.xml defined with transport = real world IP address of server (2.2.2.2)

What is the expected output? What do you see instead?
immediately following m=audio 'port' RTP/AVP 0 101 I would expect to see
c=IN IP4 2.2.2.2
instead I'm seeing
c=IN IP4 10.241.82.74 (an internal IP defined on the host but not define as 
'transport' in config.xml

What version of the product are you using? On what operating system?
V2.2.0 on RHEL 6

Please provide any additional information below.
sip trace clip as received by my SIP Proxy

Original issue reported on code.google.com by JacBar...@gmail.com on 27 Feb 2013 at 6:06

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 27 Feb 2013 at 7:43

GoogleCodeExporter commented 9 years ago 
Ideally we would have separate transport configuration for the rtcweb breaker.

Original comment by H.P.Przy...@gmail.com on 29 Apr 2013 at 1:15

GoogleCodeExporter commented 9 years ago 
Issue 98 has been merged into this issue.

Original comment by boss...@yahoo.fr on 31 May 2013 at 6:56

GoogleCodeExporter commented 9 years ago 
https://groups.google.com/group/doubango/msg/63d62ed7082da167?

Original comment by boss...@yahoo.fr on 18 Jun 2013 at 3:57

GoogleCodeExporter commented 9 years ago 
Hi,
I made an update of the original code to have RTP address and port range 
configurable in config.xml. I'm aware it's not fully tested but it worked for 
my basic case (chrome 2 legacy call through webrtc2sip on IPv4). I attach diffs 
(Doubango rev. 909, Webrtc2sip rev. 100) so please feel free to use. I also 
sent them to Mamadou as a base proposition for this functionality in the 
original projects.

best regards,
slawek

Original comment by slawekh...@gmail.com on 2 Jul 2013 at 2:02

Attachments:

GoogleCodeExporter commented 9 years ago 
I am facing same issue ( wrong ip in SDP connection parameter) . Another issue 
is that all interfaces  get listed  in SDP  and  this causes the packet to be 
big causing IPv4 fragmentation.

Original comment by anishpar...@gmail.com on 30 Apr 2014 at 6:33