I have committed the initial version of the Shared Appearance Agent
(SAA). Now I will watch for the inevitable build failures (I did test
the rpmbuild...)
Config required to try it out:
- generate profiles for the system (this adds credentials for the new
special identity sipXsaa)
- copy the file src/sipXsaa/etc/appearance-groups.xml into the sipx
config directory and edit it to contain the users you want shared.
- configure the shared appearances for each phone in the group (only
works on Polycom sets):
* add a line on the phone for the shared user, if necessary
* under the Registration screen for this line, set the type to
"shared" (default "private")
* under the Registration screen for this line, set the thirdPartyName
to match the line registration name
* (optional) under Advanced, set lineKeys to 2 or more: this will
assign several buttons to the shared appearance. Then you can see how
multiple calls are handled, and how it behaves when sets have different
numbers of appearance buttons.
- manually configure the service to start:
sipxproc -u SharedAppearanceAgent -v 4.1.0
sipxproc -s SharedAppearanceAgent
It sometimes takes a while to get all the subscriptions set up properly.
When everything is working, selecting the shared line on one set should
make the light go on on all sets in the group. Putting a call on hold
will result in all the lights flashing; the call can then be retrieved
from any set in the group by pressing the flashing button.
This is still work-in-progress. Comments and feedback welcome. There
is a Crucible review open at http://code.sipfoundry.org/cru/XECS-31
which does not quite match the committed code (but it's close).
Carolyn
_______________________________________________
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/
