Damian wrote:
> > We have to implement it in a generic way (not limited to Polycom 
> > sets).
> > Polycom plugin can recognize that lines are shared and create a 
> > specific configuration. In the sense of "plug-in" vs.
> > "core" functionality it's no different from let's say phonebooks or 
> > time zone features.

What other phones will this support?  What will happen if it's enabled
for a phone that does not support it?


Carolyn wrote:
> In addition to the set-specific config, the shared user must 
> be saved in some file so that the Appearance Agent (or Shared 
> Line Agent, or other name suggestions welcomed) knows about 
> it.  I am not sure if that should be done on the main Add 
> User page, or should be implicit from doing the set-specific 
> config (though I prefer the set-specific stuff to be 
> implicit, and the shared setting done at the user level - 
> which might impose the limitation that all appearances of a 
> user marked shared will in fact be shared - which is not 
> actually required by the I-D, but seems reasonable to me).

Maybe it doesn't need to be configured at all?

i.e. The superadmin has configured two Polycoms to both have a line
registered to the same user.  Therefore both phones can make and receive
calls on that line.  It makes sense that both phones should then be able
to see the status of the line and pick up call that are on hold.

This depends of course on how graceful non-supporting phones can be
handled.  

Also, suppose the feature is configured "on" for all users (in the
Shared Line Agent), but no phones in the system are configured to use
it.  What is the CPU and SIP messaging overhead for a user with one
registered phone?  With more than one registered phone?


-Paul
[email protected]

_______________________________________________
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