Hi All,
Please find below some thoughts about the internal user for a TLS Peer and
peeridentities.xml replication
- I've looked at the existing SpecialUser and I found no mean to reuse it as an
internal TLS Peer user support (SpecialUser is more service related, meaning
that a service is associated with (only) one special user). Therefore I was
thinking to use regular users and to add a new discriminator column to
differentiate between admin configured users and internal users (the query used
in user table model will be modified not to include internal user instances).
- I guess we don't have to bother about the internal user SIP password and PIN
token (they can be randomly generated or leaved empty)
- per my understanding - peeridentities.xml will be declared as <osconfig>
resource in sipxbridge-process.xml.in and sipXproxy-process.xml.in and it will
not require service restart after replication. I think there is some additional
work required on Operation side to handle this new resource and also to pick up
changes on the fly?
Please comment,
Thanks,
George
_______________________________________________
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/
