On Fri, 2009-06-19 at 14:04 -0400, Carolyn Beeton wrote:
> I have started to think about what config the Bridged Line Appearances
> feature would need.
>
> For the Appearance Agent side, all it needs is a list of shared URIs (or
> is it AORs?). The list of sets using the shared URI will be discovered
> through registration. I have been using a file called
> appearance-groups.xml, with contents like:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <appearanceGroups
> xmlns="http://www.sipfoundry.org/sipX/schema/xml/appearance-groups-00-01
> ">
> <resource uri="sip:[email protected]"/>
> <resource uri="sip:[email protected]"/>
> </appearanceGroups>
Some nits: The xmlns would end with "-00-00", as this is the first
revision of the schema. It would probably be better to have the file
list extensions (user-parts of AORs) rather than the AORs themselves, if
we are assuming that the Shared Appearance Agent will always only handle
AORs within our domain. OTOH, if the SAA can in principle manage
"foreign" AORs, maybe we should list AORs.
In regard to what information to configure, we need to make sure that
the UI is in terms of the logical model rather than whatever Polycom
does, not least because the SAA may not want to use Polycom's "shared
line" feature.
I assume the UI will need to specify which extensions have the SA
feature (because we won't want to apply the overhead of SA to all AORs).
The more interesting question is how we specify and configure how many
"lines" there are for each AOR. IIRC, the SA feature is designed so
that the different phones on which an AOR appears can have different
numbers of appearances ("lines") for it, but that the SA feature works
best if all the phones have the same number of appearances (as the users
would expect). So presumably, each extension ("user") which has SA
activated will also have a specification for the number of its
appearances, and that information will be propagated into the
configuration of each phone on which the AOR appears.
Dale
_______________________________________________
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/
