Hi all,

Thanks for all the feedback yesterday, very helpful.

I've been asked to put together a scaled-down Phase 1 proposal that
might get implemented in 4.2.  Here's what the feature would like.
(Thanks Scott for the help on this!)


The main goal is to discover the MAC and model of un-provisioned
Polycoms that have made a configuration file request to sipXecs.  (The
Polycoms acquire the sipXecs address either through DHCP Option 66, or
via manual programming.)

Once a Polycom is discovered, a Devices->Phones entry is created with
the MAC and model set, but no Lines assigned.  The IP address that the
phone uses at discovery time will be written into its Description, along
with a short unique identifier.  (In Phase 1 the uniqueness of the
identifier may not be 100% guaranteed.)

Discovered Polycoms will register, and have limited calling
capabilities.  The unique identifier will be shown on the line label of
the phone.  

The superadmin would then still need to manually assign these phones to
users in the normal fashion.  However, the unique identifier can be read
from the phone and then used to search in sipXconfig.  This will allow
an administrator to quickly find a phone that has been selected for
deployment to a user.

(TBD if Phase 1 will include a new sipXconfig filter for phones that do
not have any lines configured.)

To be clear, the discovered phones will not show up under Devices ->
Discover Devices, nor will they be put into any Groups.


Limitations:

- Phase 1: Polycom only.

- Phase 1: No IVR.

- Phase 1: Restarting discovered phones from sipXconfig will not be
supported.

- Polycoms deleted from Devices->Phones may be subsequently
re-discovered if they are not removed.  


If this is acceptable functionality and user experience, then I'll
propose an architecture.


-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