Bug 11957 - Sofia SIP client always reports the WLAN IP as its local IP
: Sofia SIP client always reports the WLAN IP as its local IP
Status: UNCONFIRMED
Product: Maemo 5 Community SSU
hildon-desktop
: unspecified
: N900 Maemo
: Unspecified normal (vote)
: ---
Assigned To: unassigned
: general
:
:
:
:
  Show dependency tree
 
Reported: 2011-02-20 10:55 UTC by mase
Modified: 2013-03-05 22:30 UTC (History)
1 user (show)

See Also:


Attachments
Broken call, IPv4 address on usb0 set (47.39 KB, application/x-lzma)
2013-03-05 22:29 UTC, Linus Lüssing
Details
Working call, IPv4 address on usb0 removed (21.83 KB, application/x-lzma)
2013-03-05 22:30 UTC, Linus Lüssing
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description mase (reporter) 2011-02-20 10:55:36 UTC
SOFTWARE VERSION: 
(Settings > General > About product)

EXACT STEPS LEADING TO PROBLEM: 
1. Connect via UMTS or OpenVPN.
2. The phone tries to connect to the SIP accounts (asterisk).

EXPECTED OUTCOME: 
The connection is successfull and I can use the phone with
asterisk over UMTS and OpenVPN.

ACTUAL OUTCOME: 
No connection possible, because Sofia uses the WLAN IP
as its local one.

REPRODUCIBILITY: 
always

EXTRA SOFTWARE INSTALLED: 

OTHER COMMENTS: 
At the moment I am using this commands on the maemo-update-resolvconf script:

When up:
mc-tool update sofiasip/sip/server_2esetho_2eorg0
string:local-ip-address="10.8.0.17"

When down:
mc-tool update sofiasip/sip/server_2esetho_2eorg0 clear:local-ip-address
Comment 1 Linus Lüssing 2013-03-05 22:27:42 UTC
I seem to have a similar issue, not sure whether it is the same or a different
one, at least the symptoms are different and the workaround at the bottom does
not seem to work for me:

EXACT STEPS LEADING TO PROBLEM:
- Add a static IPv4 address to the usb0 interface (here: $ ifconfig
192.168.2.2/24)
- Connect to the wifi network
- Connect to the local sip server
- Call another SIP client (here a Snom 360) with the N900 via Sofia.

EXPECTED OUTCOME: After the other client (a snom 360) accepts my call from the
N900 both the snom 360 and the N900 should be able to hear each other. The N900
should announce the IPv4 address from its wlan0 interface (10.130.10.241) as
its 'Connection Address' in the SDP header.

ACTUAL OUTCOME: The Snom 360 hears the N900 fine, but not the other way round.
tcpdump only shows RTP packets from the N900 to the Snom 360, but no RTP
packets from the Snom 360 to the N900. The N900 announces the IPv4 address from
its usb0 interface (192.168.2.2) as its 'Connection Address' in the SDP header.

REPRODUCIBILITY: 
always

OTHER COMMENTS:
- The workaround described by the original reporter does not seem to work.
- Removing the IPv4 address from the usb0 interface seems to be a valid
workaround.
- See the attached RTP+SIP capture for details.
Comment 2 Linus Lüssing 2013-03-05 22:29:41 UTC
Created an attachment (id=3470) [details]
Broken call, IPv4 address on usb0 set
Comment 3 Linus Lüssing 2013-03-05 22:30:16 UTC
Created an attachment (id=3471) [details]
Working call, IPv4 address on usb0 removed