ACK to 401 Sent to Wrong IP

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enable RTCWeb Breaker
2. Place a call
3. Have the SIP proxy challenge the INVITE with a 401

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

I would expect the ACK to be sent to the IP:port associated with the SIP Proxy. 
 Rather I'm seeing the ACK being sent to an unknown IP.  In fact in all tests 
the ACK is being sent to 72.167.131.132 rather than 206.169.49.10.  Attached is 
a pcap file showing the SIP messages between webrtc2sip and the SIP proxy.

What version of the product are you using? On what operating system?
OS: CentOS 6.6
webrtc2sip: 2.6.0
doubango: branch 2.0

Please provide server logs with DEBUG level equal to INFO
See attached log file

Please provide browser logs

Original issue reported on code.google.com by stephen....@gmail.com on 13 Nov 2014 at 6:36

Attachments:

• Bad-ACK.pcap
• ACK-Issue.log

[GoogleCodeExporter]

I have same issue.
webrtc2sip(r139) DOES NOT send ACK to IP:port(Sip outbound proxy URL specified 
by sipML5 expert page), it seems that webrtc2sip instance sent ACK to 
realm:5060.

Original comment by xmg...@gmail.com on 16 Jan 2015 at 9:59