On Mon, 2009-09-21 at 13:23 -0400, Yang, Huijun (CAR:9D30) wrote: > > On Mon, 2009-09-21 at 12:18 -0400, Yang, Huijun (CAR:9D30) wrote: > > > > > > Sorry that I did not make myself clear. So I am proposing to have a > > > new page, that you can create a peer, which include peer name, > > > certicate, permissions, etc. and underneath, system will create an > > > itentity for the peer, and as you suggested, there is no need to > > > expose the identity on the UI. > > > > > ... and what relationship would that page have to the configuration of > a dial plan between the peers? > > My point is there should be no need to create a tailored dialplan > between peers. I guess it is similar to the case that we do not > configure dialplan based on user, but permissions. It will be the > question if a peer system ( a virtual user) has the permissions to > access to a dialplan or not.
I see your point. But the administrator has to add that peer somewhere in the configuration, and I think that most administrators currently think of this as a feature related to dial plans. They think of this as 'anything coming in over this connection' rather than as 'anything coming from this peer via any connection'. While there might not be any real difference within our permissions scheme, it can be helpful from a UI point of view to cater to the mental model the user already has. _______________________________________________ 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/
