Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Rollout: DiVitas Networks Mobile Convergence Appliance and Client: Page 3 of 6

We also had to hunt for the phone's serial number/ name (it's hidden on every device, and sometimes the hex rather than decimal version must be used) and enter it on the MCA along with the device type and group name. For large deployments, this process is cumbersome--DiVitas is considering some kind of autoregistration.

Finally, because Windows Mobile does not offer the equivalent of a Windows Startup folder, there is no mechanism to load the MCC upon device power on, which means users must remember to load the client and log in with their extension and password after every soft reset and battery outage.

When In Roam

After getting the phones configured, basic calls and roaming were the next tests. Vo-Fi calls between phones worked consistently, and the voice quality was far better than with most cellular calls.

If both cellular and Wi-Fi service are available, DiVitas will default to using Wi-Fi. If the MCC determines that the Wi-Fi voice quality has weakened significantly, it initiates a roam to the cellular network. The TyTn handset had a particularly poor Wi-Fi radio and would hand off after one flight of stairs. We were able to walk half a block away with the MC70.