Hello,
I'd like to initiate a discussion for
http://track.sipfoundry.org/browse/XX-6398 from requirements to
sipXconfig point of view.
The following are the requirements to sipXconfig for this feature:
- To allow admin to add/delete/config TLS peer system info, which
include, peer system's name, certificate, and permissions assigned to.
- Extend site-to-site dialing rule (used by sipXproxy) and sipTrunk (
used by sipXbridge) to include peer-to-peer parameters, such as source
peer system, and permissions, etc.
- Create unique identity for each peer system configured, which does not
to be visible from the UI, could be something like ~~peer~{peer}
But after thinking it a bit, I am not sure we need to extend
site-to-site and sipTrunk to include peer system info. To me, a peer
system will be just like a virtual user to the local system, and admin
will grant whatever permissions to it to allow it to access dialplans on
the local systems. For example, if LongDisance permission is granted to
the peer, then PSTN calls from the peer system will be able to access
dialplans that require LongDistance permission. In other words, peer
system will be handled just as it is a user in the local system based on
its permissions. If we allow to configure permission to a peer system,
then the existing dialplan handling should be sufficient to handle it.
There should not be a need to modify Site-to-Site or sipTrunk to
specially handle the peer system to access dialplans.
Maybe I miss something here?
Thanks
Huijun
_______________________________________________
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/
