Am 10.03.2010 17:33, schrieb Kevin P. Fleming: > Klaus Darilion wrote: > >> That's weird. AFAIK Asterisk does not allow multiple ranges. Maybe they >> are having 2 ranges for RTP and UDPTL (T.38). Asterisk allow >> configuration of different ranges for UDPTL and RTP (although it >> shouldn't be a problem to configure the same ports in rtp.conf and >> udptl.conf) > > It absolutely would be a problem to have identical, or even overlapping, > port ranges specified in rtp.conf and udptl.conf. Those port numbers are > UDP port numbers, and they must be unique across the system for things > to work properly.
Hi Kevin! Is Asterisk really that thumb and announces port befores testing if it actually can open the socket? Usually you have other services running on the same server to (e.g. DNS uses UDP ports), and just specifying port=1000-1999 in rtp.conf does not prevent that any other process on this server uses one of these ports. Thus, usually an application will try to open an UDP socket, and if it that fails, it just tries to open another one (with some logic behind). So, if port 1000 is already taken by another application, Asterisk should try to open another port. Thus I thought that if udptl opened a port within the portrange of rtp, res_rtp should be able to handle this. If this is not the case, IMO it is a serious bug in Asterisk. regards Klaus -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users