Hi! On 11.08.2008 18:43, Ralf Schlatterbeck wrote: > On Mon, Aug 11, 2008 at 05:09:33PM +0200, Klaus Darilion wrote: >> Chris Maciejewski schrieb: >>> On 11.08.2008 13:32, Klaus Darilion wrote: >>> >>>> Actually if all SIP user agents would be standard conform then even the >>>> proxies need not to use port 5060 (SRV lookups). >>> >>> Well, in my opinion we should try to make Qutecom as close to the >>> standards defined in RFC 3261 (and others) as possible. And IANA >>> assigned port for SIP is 5060 (5061 TLS) >> >> Using a random port for SIP is 100% standard conform. The assigned port >> is the one which is used if the port is not specified in the URI. > > I think so far we've identified two things: > 1) The port that is used by qutecom (and other sip devices) when > registering with a registrar should be random. AFAIK Qutecom currently > uses 5060 even in this case.
Yes! I think that's the point! Listening on a port (for incoming connections) is one thing, using a port for outgoing connections is another! > 2) When listening for incoming connections it might make sense to use a > well-known port (security issues aside). This should be configurable. > But probably you don't want a random port here. And I agree with > Klaus that you probably don't want to use 5060 if connecting directly > to the internet. > Both cases should be clearly distinguished. As far as I know, Qutecom > uses 5060 also for case 1 above and does some special handling to > achieve port-reuse when scanning if the port is already used. Nevertheless both cases "should" allow setting a fixed port by a configuration setting. That said outgoing connections should be random by default while listening ports "can" be fixed and probably be 5060. Don't you think that would be the best solution? On the other side the main question remains: any idea why my "random port" patch breaks the Linux and Mac builds? Greetings && HAND - Darsha P.s. As I will attend the "A1 Innovation-Days"[1][2] end of August and it seems that quite a few ideas are not fully filled with team-members there is good chance to join and it would be somehow fun to discuss this or similar subjects in RL... If you have an questions don't hesitate to contact me... [1] http://www.a1innovations.at/en/static/a1innovationdays [2] http://article.gmane.org/gmane.comp.voip.qutecom.devel/200/match=developer _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
