Carolyn wrote: ... > > 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).
Understood, and I have removed the link between XX-7452 and XX-7319. Thanks! -Paul [email protected] _______________________________________________ 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/
