Administrator Guide: Personal User Mobility 3.0
Personal User Mobility (PUM) enables a user to move from one desk to another while having his personal settings available on whichever phone that is being used. These settings are stored in a virtual phone (SVE) and are applied to any physical phone via a PUM login procedure.
The mobility is available in a single SOP configuration or in SOP-cluster configuration.
Login of virtual phone on a phone
On the current phone:
- From the provided extension search for the primary phone and check that this one is a virtual phone
On the virtual phone's SOP
- Check that the virtual phone is not already logged in
- If needed logout the virtual phone
- Update lock of virtual phone (new physical phone)
On TFTP SOP
- Apply virtual phone settings on the current phone
On current SOP:
- Request the current phone to reload its configuration
- If a virtual phone is already logged on the current phone, remove the lock between the physical and the logged virtual phone
Once reconfigured the phone will register its self on the virtual phone's SOP and with the virtual phone name
Logout of virtual phone
On TFTP SOP:
- Restore the phone's original configuration
On current SOP:
- Request the phone to reload the configuration
- Remove the lock between the virtual phone and the physical phone
Once reconfigured the phone will reconnect to its original SOP with its original name.
Active/Active support is provided for the PUM service.
In this configuration the virtual phone register itself on both primary and secondary SOP.
If the primary SOP goes down, the secondary SOP will automatically been used to make a call from the virtual phone or to receive the call on the virtual phone.
The virtual phone can also logout and login via the secondary SOP. When the primary or the secondary SOP goes back, it will resynchronize itself with the secondary SOP in order to have the excat state of all the virtual phone it is taking care of.
Active/Standby support is provided for the PUM service.
In this configuration, phone registration and PUM state information are replicated from the active SOP to the standby SOPs.
- Inter-SOP PUM is only possible between SOPs in the same cluster
- PUM module and its dependencies
- Polycom Phones: Polycom Virtual Phone resource
- Aastra: Aastra Virtual Phone resource
- Grandstream: Grandstream Virtual Phone resource
To understand whether PUM is supported on a particular phone, check the phone feature table (http://myservice.escaux.com/docs/OffGenMain_PhoneTable.html
) and verify all the module and resource dependencies.
- Check the requirements
- Provide the PUM settings parameters (TFTP-SOP) and install PUM module
- For each user requesting the mobility, create a virtual phone (SVE2 for SDP4 and SVE1 for SDG3) and set this virtual phone as the primary phone of the user's extension in the Internal Directory of the SMP.
- Install the 'Mobility Login' and 'Mobility Logout' call flows on the cluster or SOP and associate the extension in the Internal Directory of the SMP.
- To be able to manage the PUM from the Escaux UC System administration page (SVE reset, virtual phone logging tracking) check for an available upgrade of the SMP.