> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Yang, Huijun AVAYA (CAR:9D30) > Sent: Thursday, February 04, 2010 10:55 AM > > > Huijun wrote: > > > > I am working on XX-7452 <http://track.sipfoundry.org/browse/XX-7452> > > :Support configuration of a user identity in Audiocodes > gateway. Here > is my take on the requirement of the issue: > > > > Need an integrated UI that admin can configure the userIdentity for > > the gateway, and corresponding permissions on Audiocode > gateway edit > > page. By "intergrated UI", I mean admin do NOT need to > create a dummy > > user from users page, and set its permissions, then come back to > > manually enter the UserName and Password for Audiocodes gateway > settings. All the configurations to enable this functionality > can be done on EditGateway page. > > > > In other words, my understanding is that this improvement should > > provide an UI that is intuitive for users to enable this > > functionality, and beyond just introducing the new > parameters(UserName, Password, and > AuthenticationMode)required for Audiocodes settings. > > > > > See also the discussions Carolyn led relating to XX-7319 : Create > screen to map TLS peer to permission set > > > - suggested user ids (~~pi~<domain or hash thereof>), xml layout > (peeridentities.xml) etc. > http://list.sipfoundry.org/archive/sipx-dev/msg20859.html > > > - screen design > http://list.sipfoundry.org/archive/sipx-dev/msg21215.html > > > Thanks Paul for bringing this up. ( Originally, I did not > want to mention this on purpose as if the requirement for > this release is only to add the new parameters for > Aududiocodes, then XX-7319 will become irrelevant; If the > requirment is to have a "integrated UI", then I will try to > bring the related issues up in my proposal, such as XX-7319.) > > > Huijun
I see no particular advantage to linking it to XX-7319, but there may be an opportunity for consistency and code/screen sharing. Both issues require a new "special" userid to be created, and Call Permissions assigned to this user. But if XX-7452 can be addressed without requiring the admin to go to any other screen (i.e. if permissions can be integrated with the audiocodes settings) then this seems a simpler approach. I'm not sure that that approach should be used for XX-7319, because we want to keep in mind that TLS connections made directly to the proxy should also apply the trusted peer special user permissions, and I'm not sure where this could be configured (an Unmanaged Gateway might be configured for calls going OUT to the other system, but here we are talking about calls coming IN FROM the system). (For sipXbridge connections it could work, because the calls do come IN to the bridge which is configured with the remote FQDN). Carolyn _______________________________________________ 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/
