Dale Worley wrote: > On Tue, 2009-09-15 at 13:40 -0400, Damian Krzeminski wrote: >> I am reviewing a patch for http://track.sipfoundry.org/browse/XX-5958 >> It adds capability to change proxy ports. It specifically allows for >> configuring: TCP, UDP and 'secure' ports. >> Until now sipXconfig always configured TCP and UDP port to the same value. >> Do separate values for UDP and TCP make sense? > > There is a disadvantage of having different port numbers for TCP and > UDP: You can't compose a Contact header that specifies both of them. > If you are listening on both TCP and UDP port 10000, then you can use > "Contact: sip:1.2.3.4:10000", which lets the far end decide what > transport to use. But if you listen on TCP 10001 and on UDP 10002, then > you have to use either "Contact: sip:1.2.3.4:10001;transport=tcp" or > "Contact: sip:1.2.3.4:10002;transport=udp", but not both. This > constrains the immediate sender to use TCP or UDP, depending. >
OK. I'll stick to a single value for UDP and TCP for now. We can split it later if anyone sees the advantage of doing that, but it looks like a separate issue (and would probably require some other changes in config files). D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
