On Mon, 2009-12-14 at 10:13 -0500, Beeton, Carolyn (CAR:9D60) wrote:

> How about this, then:
> 
> peeridentities.xml (used by both sipXproxy and sipXbridge)
> 
> <peeridentities
> xmlns="http://www.sipfoundry.org/sipX/schema/xml/peeridentities-00-00";>
>   <peer trusteddomain="trusteddomain.com">
>      <internaluser>~~id~trusteddomain.com</internaluser>
>   </peer>
>   <peer anothertrusteddomain="10.10.1.2">
>      <internaluser>~~id~10.10.1.2</internaluser>
>   </peer>
> </peeridentities>
> 
> - one entry per trusteddomain
> - same user can be specified for multiple trusteddomains (?)

To be consistent with the style we've used elsewhere, I'd say make
'trusteddomain' be an element rather than an attribute.

> For sipXbridge, the natural place to create a special user and specify
> permissions for it, is on the ITSP Account page.  sipXconfig needs to do
> this (as part of http://track.sipfoundry.org/browse/XX-6398).  Not sure
> where it would fit for sipXproxy.
> 
> There are some config issues to be discussed: 
> - is the special user visible to the administrator?

We need to be able to configure the permissions for it, so it needs to
be visible somehow, but I don't see that the internal name needs to be
visible.  Using your examples above, the admin configures permissions
for 'trusteddomain.com', not '~~id~trusteddomain.com'.

Incidentally, these should get a new two letter prefix, not use 'id' as
above - 'id' is for services.  Pick a value and put it into
meta/system-sip-identities.

> - does he have to create it, or is it created automatically?  Can he
> pick an existing user, if he wants to?

Automatically, and no.

> - are permissions set for the special user as per the normal mechanisms,
> or in some other way?

They have to be settable somehow, I think.  I don't see why it should
look any different from other permissions-setting screens...


_______________________________________________
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/

Reply via email to