Re: [GnomeMeeting-devel-list] SIP, RTP ports and firewall



Le mardi 22 novembre 2005 à 19:34 +0100, Daniel Huhardeaux a écrit :
> Damien Sandras a écrit :
> 
> >Le lundi 21 novembre 2005 à 23:46 +0100, Daniel Huhardeaux a écrit :
> >
> >  
> >
> >>I started gconf-editor and modify RTP ports to 6970:6990, then run GM, 
> >>then the druid: "NAT avec restriction de port" (NAT with restriction 
> >>port), called 612 fwd pulver com and call went smooth.
> >>
> >>I closed GM, modify RTP ports to 16384:16388, run the druid: "NAT avec 
> >>restriction de port" (NAT with restriction port), called 
> >>612 fwd pulver com and call failed like reported above.
> >>
> >>I have some difficulties to understand why changing the RTP ports should 
> >>interfere with STUN. Remember that registration is always ok.
> >>    
> >>
> >
> >STUN is using those local ports to determine the holes on the gateway.
> >
> >Unfortunately, I have no idea why STUN reports NAT with restricted
> >ports, and works with some ports, but not with others.
> >
> >Perhaps Craig has an idea?
> >  
> >
> Got it:
> 
> RTP port range has to have minimum 9 ports eg 16384:16392 or 6170:6179 
> If this condition is fulfilled, everything is working well: you can 
> place how much calls you want, STUN is OK, no crashes, life is 
> beautifull (anyway) ;-)
> 
> Another thing to know is that for udp_port range, even if you put 
> 5060:5060, ports till 5072 (more?) are used. I put those range to 
> 42600:42700 and it's working. This can avoid the problem of few softs 
> running on the same computer, listening to 5060, 5061,....
> 

I will still ask Craig to fix pwlib to prevent the assertion.

-- 
 _      Damien Sandras
(o-     GnomeMeeting: http://www.gnomemeeting.org/
//\     FOSDEM 2006 : http://www.fosdem.org
v_/_    SIP Phone   : sip:dsandras gnomemeeting net 
                      sip:600000 gnomemeeting net




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]