Mike wrote: > Is there another option for doing this as well? Via an XML > page that can be displayed on the phone?
A good option for Polycoms. Maybe not a Phase 1 item, but something to consider. > Food for thought, here's how Mitel does their provisioning > (the slickest I have seen for system deployment but probably > requires code in the phone to make it work)... > > 1. Users are all programmed into the system with what type of > phone they are to receive. > 2. New phone gets plugged in where it is supposed to be located. > 3. Phone boots as 'unprovisioned' and waits for a 4 digit > security code followed by what extension to make the phone > (if it is the wrong type of phone, it will not provision... > prevents deployment mistakes). > 4. Phone configuration is generated and that user assigned to > that phone. > 5. Phone reboots. I think our proposal will do this, except for the part about pre-programming the type of phone for each user. You will deploy the desired phone model at the user's desk anyway... So isn't it more flexible if you do not need to pre-program the model? > In the case of needing to replace a phone or to assign it to > a new users, a phone can be removed from a user by holding > down a key sequence. That would require code in the phone. Hopefully dialing an IVR and entering your PIN is an acceptable alternative. -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/
