[jitsi-dev] Fwd: Bug#735409: uses 5060 as default SIP client port


#1

Package: jitsi
Version: 2.3.4952-1

In the SIP settings, Jitsi defaults to using port 5060 as the local SIP
port that it binds to

It is not clear that this is a good idea as people running multiple
processes (e.g. a multi-user system, or developer box with a local SIP
proxy) can not all bind to 5060 at the same time.

If Jitsi is just acting as a client and registering to a proxy then it
can probably use a randomly selected client port by default

The statically defined port is only really needed for people who want to
make calls using their hostnames but I suspect that is not so common

···

---------- Forwarded message ----------
From: Daniel Pocock <daniel@pocock.com.au>
Date: Wed, Jan 15, 2014 at 10:26 AM
Subject: Bug#735409: uses 5060 as default SIP client port
To: Debian Bug Tracking System <submit@bugs.debian.org>


#2

Just a quick note: I think that's just a problem with the GUI. By
default Jitsi doesn't use a specific port. But going to the SIP setting
and just clicking on the "SIP client port" text field causes 5060 (or
whatever is in the field) to be used, and then there is no way (apart
from manually editing properties) to reset it.

Regards,
Boris

···

On 1/15/14 9:44 AM, Damian Minkov wrote:

---------- Forwarded message ----------
From: Daniel Pocock <daniel@pocock.com.au>
Date: Wed, Jan 15, 2014 at 10:26 AM
Subject: Bug#735409: uses 5060 as default SIP client port
To: Debian Bug Tracking System <submit@bugs.debian.org>

Package: jitsi
Version: 2.3.4952-1

In the SIP settings, Jitsi defaults to using port 5060 as the local SIP
port that it binds to


#3

Hey Daniel,

It would be great to have Jitsi reports on our mailing lists so that we don't have to monitor extra trackers. More inline.

From: Daniel Pocock <daniel@pocock.com.au>
Date: Wed, Jan 15, 2014 at 10:26 AM
Subject: Bug#735409: uses 5060 as default SIP client port
To: Debian Bug Tracking System <submit@bugs.debian.org>

Package: jitsi
Version: 2.3.4952-1

In the SIP settings, Jitsi defaults to using port 5060 as the local SIP
port that it binds to

Indeed, and this is configurable from Settings -> Advanced -> SIP

It is not clear that this is a good idea as people running multiple
processes (e.g. a multi-user system, or developer box with a local SIP
proxy) can not all bind to 5060 at the same time.

Indeed, but it is not clear to me that this is a use case that we should optimize for, given that other people often use Jitsi with RegistrarLess accounts, in which case receiving calls strongly depends on listening on 5060.

Note that people running proxies only need to make sure that their proxy starts before Jitsi so that they could take 5060.

If Jitsi is just acting as a client and registering to a proxy then it
can probably use a randomly selected client port by default

It can and it will in case 5060 is taken.

The statically defined port is only really needed for people who want to
make calls using their hostnames

You mean "receive" rather than "make", right?

but I suspect that is not so common

Certainly not less so than those who run a proxy on their desktop machine.

Cheers,
Emil

···

On 15.01.14, 09:44, Damian Minkov wrote:

---------- Forwarded message ----------

--
https://jitsi.org


#4

Hey Daniel,

It would be great to have Jitsi reports on our mailing lists so that we
don't have to monitor extra trackers. More inline.

If you prefer, I can put things like this directly in your trac system?

It is probably only necessary to use the Debian bug tracker for things
relating to the packaging, but I don't think that applies to any of
these issues.

From: Daniel Pocock <daniel@pocock.com.au>
Date: Wed, Jan 15, 2014 at 10:26 AM
Subject: Bug#735409: uses 5060 as default SIP client port
To: Debian Bug Tracking System <submit@bugs.debian.org>

Package: jitsi
Version: 2.3.4952-1

In the SIP settings, Jitsi defaults to using port 5060 as the local SIP
port that it binds to

Indeed, and this is configurable from Settings -> Advanced -> SIP

It is not clear that this is a good idea as people running multiple
processes (e.g. a multi-user system, or developer box with a local SIP
proxy) can not all bind to 5060 at the same time.

Indeed, but it is not clear to me that this is a use case that we should
optimize for, given that other people often use Jitsi with RegistrarLess
accounts, in which case receiving calls strongly depends on listening on
5060.

I wasn't suggesting that Jitsi should drop support for the port 5060 use
case, just that it might require the user to actively specify they want
that port.

Note that people running proxies only need to make sure that their proxy
starts before Jitsi so that they could take 5060.

If Jitsi is just acting as a client and registering to a proxy then it
can probably use a randomly selected client port by default

It can and it will in case 5060 is taken.

The statically defined port is only really needed for people who want to
make calls using their hostnames

You mean "receive" rather than "make", right?

Well, the hostname is being typed by the person making the call

but I suspect that is not so common

Certainly not less so than those who run a proxy on their desktop machine.

and Asterisk and test cases from reSIProcate and other stuff.

···

On 15/01/14 19:21, Emil Ivov wrote:

On 15.01.14, 09:44, Damian Minkov wrote:

---------- Forwarded message ----------


#5

Hi,

···

On Wed, Jan 15, 2014 at 8:21 PM, Emil Ivov <emcho@jitsi.org> wrote:

It would be great to have Jitsi reports on our mailing lists so that we
don't have to monitor extra trackers. More inline.

I'm changing the package to add our dev mailing list listed in
maintainer field so we will automatically receive mails for future
bugs, and we can just reply to them here.

Cheers
damencho


#6

Hey Daniel,

It would be great to have Jitsi reports on our mailing lists so that we
don't have to monitor extra trackers. More inline.

If you prefer, I can put things like this directly in your trac system?

Our trac system is overwhelmed with stuff as it is so we prefer having it on the list first.

It is probably only necessary to use the Debian bug tracker for things
relating to the packaging, but I don't think that applies to any of
these issues.

Unless someone is explicitly committed to fixing bugs that appear on the Debian bug tracker, we'd really rather have them all here.

From: Daniel Pocock <daniel@pocock.com.au>
Date: Wed, Jan 15, 2014 at 10:26 AM
Subject: Bug#735409: uses 5060 as default SIP client port
To: Debian Bug Tracking System <submit@bugs.debian.org>

Package: jitsi
Version: 2.3.4952-1

In the SIP settings, Jitsi defaults to using port 5060 as the local SIP
port that it binds to

Indeed, and this is configurable from Settings -> Advanced -> SIP

It is not clear that this is a good idea as people running multiple
processes (e.g. a multi-user system, or developer box with a local SIP
proxy) can not all bind to 5060 at the same time.

Indeed, but it is not clear to me that this is a use case that we should
optimize for, given that other people often use Jitsi with RegistrarLess
accounts, in which case receiving calls strongly depends on listening on
5060.

I wasn't suggesting that Jitsi should drop support for the port 5060 use
case, just that it might require the user to actively specify they want
that port.

Sorry, I am not sure I get that. Are you suggesting that Jitsi should do something like popup a dialog and tell the user something like "Please specify a port where you would like Jitsi to run its SIP stack on." ?

I know that Linux users are in general believed to be more technically savvy that Win/OSX but wouldn't this take things a bit too far?

To me this sounds like the perfect case for adopting a default value and letting those interested change it.

Note that people running proxies only need to make sure that their proxy
starts before Jitsi so that they could take 5060.

If Jitsi is just acting as a client and registering to a proxy then it
can probably use a randomly selected client port by default

It can and it will in case 5060 is taken.

The statically defined port is only really needed for people who want to
make calls using their hostnames

You mean "receive" rather than "make", right?

Well, the hostname is being typed by the person making the call

but I suspect that is not so common

Certainly not less so than those who run a proxy on their desktop machine.

and Asterisk and test cases from reSIProcate and other stuff.

Yup ... still not sure that this beats registrarless but it doesn't really matter: either you run Jitsi after your server or you simply open the configuration window and modify the default port.

Emil

···

On 15.01.14, 19:43, Daniel Pocock wrote:

On 15/01/14 19:21, Emil Ivov wrote:

On 15.01.14, 09:44, Damian Minkov wrote:

---------- Forwarded message ----------

--
https://jitsi.org


#7

All I'm suggesting is that the default should be 0, for randomly
selecting the port that Jitsi binds to.

It wouldn't prompt anybody, it would only be changed if the user goes to
the settings and wants to change it to 5060 or some other fixed value.

···

On 15/01/14 19:51, Emil Ivov wrote:

On 15.01.14, 19:43, Daniel Pocock wrote:

On 15/01/14 19:21, Emil Ivov wrote:

Hey Daniel,

It would be great to have Jitsi reports on our mailing lists so that we
don't have to monitor extra trackers. More inline.

If you prefer, I can put things like this directly in your trac system?

Our trac system is overwhelmed with stuff as it is so we prefer having
it on the list first.

It is probably only necessary to use the Debian bug tracker for things
relating to the packaging, but I don't think that applies to any of
these issues.

Unless someone is explicitly committed to fixing bugs that appear on the
Debian bug tracker, we'd really rather have them all here.

On 15.01.14, 09:44, Damian Minkov wrote:

---------- Forwarded message ----------
From: Daniel Pocock <daniel@pocock.com.au>
Date: Wed, Jan 15, 2014 at 10:26 AM
Subject: Bug#735409: uses 5060 as default SIP client port
To: Debian Bug Tracking System <submit@bugs.debian.org>

Package: jitsi
Version: 2.3.4952-1

In the SIP settings, Jitsi defaults to using port 5060 as the local SIP
port that it binds to

Indeed, and this is configurable from Settings -> Advanced -> SIP

It is not clear that this is a good idea as people running multiple
processes (e.g. a multi-user system, or developer box with a local SIP
proxy) can not all bind to 5060 at the same time.

Indeed, but it is not clear to me that this is a use case that we should
optimize for, given that other people often use Jitsi with RegistrarLess
accounts, in which case receiving calls strongly depends on listening on
5060.

I wasn't suggesting that Jitsi should drop support for the port 5060 use
case, just that it might require the user to actively specify they want
that port.

Sorry, I am not sure I get that. Are you suggesting that Jitsi should do
something like popup a dialog and tell the user something like "Please
specify a port where you would like Jitsi to run its SIP stack on." ?

I know that Linux users are in general believed to be more technically
savvy that Win/OSX but wouldn't this take things a bit too far?

To me this sounds like the perfect case for adopting a default value and
letting those interested change it.