On Tue, May 24, 2011 at 5:49 AM, M. Ranganathan <[email protected]> wrote: > Bad idea #1 : > > Allow for other processes to grab ports in the range reserved for sipXrelay > and deal with it on the fly. Reason: Posted already. FAIL configtest if port > range is specified in ephemeral range. > > Bad idea #2: > > A single port to multiplex all RTP traffic. Would fail for firewalls that > randomize source port and change source port periodically as a security > measure. Currently sipXrelay can deal with this (it auto learns ports ). > Thus it becomes firewall agnostic. You cannot do this with a single port > through which you multiplex all traffic. Also increases the overhead > slightly ( packet inspection ). > >
All, thanks for your feedback, especially to Ranga for the technical details. I'll stick with updating the page and alert admin not to overlap port range and ephemeral range Thanks, George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
