On Mon, 2010-02-08 at 13:41 -0800, George Niculae wrote: > Hi All, > > I've done some work in TLS Peer UI area > (http://track.sipfoundry.org/browse/XX-7319) and wanted to have some > feedback since it's a little different than the original proposal. > > The TLS Peer main page > (http://track.sipfoundry.org/secure/attachment/24143/main.png) can be > accessed under Users > TLS Peer menu. > When creating a new TLS Peer, the admin user have to complete first > the configuration screen > (http://track.sipfoundry.org/secure/attachment/24145/config.png).
There are two conceptual problems with these pages. I don't see any reason to display or even configure an IP address on either of these pages. This isn't about the IP address, and we don't need it. The name should be labeled just TLS Peer Name - it may or may not be a fully qualified host name. It is a name that is presented as a subject name in the certificate offered by the peer. > If OK button is accessed, the main page is displayed, otherwise if > admin choose the Apply button then a tabbed view containing > configuration and call permission tab is > shown(http://track.sipfoundry.org/secure/attachment/24144/permissionsTab.png). Why the difference? The permissions tab should be displayed if it's never been filled in. I'm not sure that there's a difference between Ok and Apply here - shouldn't it just be Add Peer? > Same tabbed view is displayed on editing the TLS Peer, by accessing > FQDN name within the main page. > > Carolyn, all, please let me know if this is in-line with your TLS Peer > UI requirements. It would be nice if we could remove the permissions used only for internal operations from the permissions tab (Record Prompts, Voicemail) and display only permissions that are required by some dial plan. Not required, but nice (simpler, clearer). _______________________________________________ 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/
