Here's an outline that looks workable to me. (The user experience is
mixed in with implementation notes (which are indented).)
Admin enters user into sipXconfig. (I see no way to avoid this step;
even if we trust the user to create his extension number via an IVR, we
still need the admin to add the user's name to the database.)
sipXconfig provides PIN for auto-configuring the user's extension.
Optional: Admin enables user for auto-provisioning and/or restricts
type of phone that can be auto-provisioned for this user.
User connects phone to network.
Phone obtains SIP provisioning address via DHCP or via user
entry.
Phone contacts provisioning server (TFTP, FTP, HTTP, or
whatever). Auto-provisioning monitor discovers provisioning
request for non-existent phone configuration and reports it to
sipXconfig. sipXconfig generates default configuration
(possibly inheriting from a group, possibly specific to the
phone type (How does auto-provisioning determine phone type?))
Configuration contains a single default line. (Either a common
special user-name, or one created for this phone.)
Configuration is provided to phone on either its first
provisioning request or when phone retries provisioning request.
Auto-provisioning monitor adds phone to sipXconfig database of
configured phones, and possibly a special pool of "auto-provisioned but
available" phones.
Phone is now able to make calls with permissions of default user
(presumably very restricted permissions), including emergency calls.
User dials (star-code)(user's extension)(PIN), as printed on sheet of
paper by sipXconfig in the first step. Call is routed to
auto-provisioning server, which verifies the PIN, then assigns user to
phone in the database, deletes the special line from the phone,
generates configuration files, orders phone to reboot. (Reboot can be
done through Contact address of this call, or by other mechanisms.)
Phone reboots, retrieves configuration of its user, and is fully
functional.
That seems to reduce the human labor to the minimum possible.
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/
