On Wed, Oct 6, 2010 at 5:09 PM, Douglas Hubler <[email protected]> wrote:
> On Wed, Oct 6, 2010 at 8:59 AM, Laurentiu Ceausescu <[email protected]> > wrote: > > I'm working on http://track.sipfoundry.org/browse/XX-8614 "Add NAT > Traversal > > support for TLS port in sipXconfig" ... > > In Services/Server/NAT panel, I need to put a new input text for 'public > tls > > port'. > > My question if is this port mandatory (like public port for UDP and TCP) > > When you ask if it's mandatory, that is more of a usability question > right? I would be consistent with what configuring TCP and UDP are > like, which is to show it.. > > Also the label for TCP/UDP is just > > Public port: _______ > > And if we add TLS, then we should change the label from "Public port" > to "SIP Port" and name TLS port to "TLS SIP Port" as it is in the > proxy configuration UI. > > Thanks, this is what I was looking for, I'll implement this way
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
