search

fpm123 / sipml5

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

Cannot correct handle SDP m= line when multiple network interface involved #90

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
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 Javascript console log
if you want quick response

What steps will reproduce the problem?

1.I have a PC with one available physical interface to internet(ip addr 
10.140.6.73), and another network interface (ip addr 169.254.110.197) created 
by virtual box (oracle virtual machine software)

2.Use sipml5 to dial out,in INVITE SDP, sipml5 uses c=IN IP4 169.254.110.197 as 
its RTP source, which causes there's no RTP stream out from the actual physical 
interface, one way audio happens.

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

1. When webrtc2sip sending back REGISTER 200 OK to sipml5, expect sipml5 can 
identify and remember its source address from sip header contact info 
(ws-src-ip=x.x.x.x), then sipml5 can use correct network interface when sending 
out INVITE SDP.

Please provide any additional information below.
Using chrome 26.0.1410.64 m

Original issue reported on code.google.com by fuse...@gmail.com on 13 May 2013 at 7:41

GoogleCodeExporter commented 8 years ago 
- c= line is not the RTP source as ICE is always used with means the IP address 
and port will be negotiated (see the candidates)
- remembering the source from the REGISTER is something not expected at all
There is probably an issue as you say there is one-way audio but for sure your 
diagnostic is not correct at all

Original comment by boss...@yahoo.fr on 13 May 2013 at 7:49