GNOME Bugzilla – Bug 619568
Local ports for streams and SIP are not configurable
Last modified: 2018-05-22 14:14:32 UTC
My ISP blocks UDP ports except in particular ranges (e.g. allows ports 50000-50050). Currently it is not possible to specify these ranges to ensure that traffic of forwarded. A work around for SIP is to update the local-port variable using mission control: $ mc-tool update sofiasip/sip/account uint:local-port=50000 This ensures that SIP/SDP messages get through. However this still leaves the RTP streams blocked. They appear to be hard-coded in telepathy-farsight to start at port 7078 for audio and 9078 for video. It would be nice to be able to configure this starting port or have some arrangement to ensure the ports are negotiated within the allowed range.
I could probably add something to tp-fs to configure it. Should it go through the CM or be set on tp-fs directly by the UI ?
Not sure what you mean by "CM". Having it in the UI would be nice, but perhaps it would be confusing for some. My situation is rather rare (I hope).
This is blocked by https://bugs.freedesktop.org/show_bug.cgi?id=30237
Austin, as far as I can see in the Empathy 3.4 UI, I can configure the various ports for my SIP account. Does this work for you now?
I don't see anything about the local binding port for SIP. I see two options for setting the STUN port and Proxy server port, but not the local port.
As Olivier said, we'd need a way to define this in (tp-)fs.
For the RTP part, we can either do it in the telepathy level, by having extra connection parameters and proxying it through the CM, that will require extra spec work. Or we can add some API to tp-fs to set these on Farstream. For the SIP part, I think it's only empathy missing the UI. Although I'm really unconvinced that this sort of stuff should be in the UI, having networks only allow some random port ranges sounds like a really strange case that should be fixed by fixing the network.
(In reply to comment #7) > Although I'm really > unconvinced that this sort of stuff should be in the UI, having networks only > allow some random port ranges sounds like a really strange case that should be > fixed by fixing the network. Broken networks are the rule rather than the exception. Our corporate network breaks heaps of stuff (e.g. apple internet recovery). However, this brokenness is due to management decisions and will not be fixed. Other SIP software can configure these things (e.g. Ekiga), admitedly it's in an "advanced" section. But at least it is there.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/empathy/issues/241.