TVOICE – Device Mobility- Device Mobility Concepts and Configuration

Intro…It’s a problem we never experienced in the PBX days: a phone that MOVES from site to site. Because of the havoc this can cause with Device Pool configurations (regions, locations, etc…), Cisco created Device Mobility! In this Nugget, Jeremy walks through the complete concept and configuration of Device Mobility for centralized CUCM deployments.  ——————- Roaming Devices cause issues with: (Roaming Settings excluding the CSS) -Region -Location -SRST Reference -AAR Group -CSS-MRGL Device Mobility solves this by making these settings Dynamic. The Facts Centeralised Call Control Model Typical applied to Softphones/Wireless Phones CUCM determines phone location based on it’s IP Address Works through 2 configurations: -Roaming Sensitive Settings (Non-Call Routing Impact) -Device Mobility Settings (Call Routing Impact) Configuration 4 Elements:

  • Device Pool (CORE)
  • Device Mobility Info (DMI) (Subnet)
  • Physical Location (PL)
  • Device Mobility Group (DMG)

How it all works… 1. Phone plugs in, CUCM compares IP address with DMI (SUBNET) 2. If phones home DP is equal to the DMI selected DP = Non-roaming 3. If DMI selected DP is Different – PL checked 4. If PL is different, apply roaming settings then check DMG 5. If DMG is the same, apply device mobility settings DMG Settings = CSS Roaming Setting = Everything Else (-Region-Location-SRST Reference-AAR Group-MRGL) Practical Example for Device Mobility Group Capture Device Mobility Groups = USA, Australia *Global Route Plan = Simple and minimal route patterns with Local Route Groups. How to configure Device Mobility… 1. Configure Physical Locations (California, New York, Australia) 2. Configure Device Mobility Groups (California, New York, Australia) 3. Configure Device Mobility Infos/Subnets 4. Configure Device Pools 5. Enable Device Mobility (Per Phone or Cluster) *****Update***** I revisited this topic as it hurt my head each time I hit any practice questions… So to help me out…. Device Mobility Group Example of Essex May contain Physical Locations of Chelmsford and Rayleigh. Device Mobility Group Example of Florida May contain Physical Locations of Miami and Orlando. Basically you group sites together that share dialing properties.

More on Device Mobility…

This topic is fairly easy in principal, but the rules/conditions for Device Mobiiity are a headache. So here I try to sum it up again with a real world example:

‘Has the physical location changed?

If Yes, apply Roaming Sensitive settings of phones new Device Pool

If the Device Mobility Group is the same, apply Device Mobility Settings (Call Routing Impact such as CSS)

Physical Location Example: Rayleigh
Device Mobility Group: Essex

If the Device Mobility Group is NOT the same, do not apply any CSS/Call Routing cfg

Physical Location Example: Rayleigh
Device Mobility Group: Japan

This makes sense as you dont want to use a CSS for Rayleigh, when you are physically sitting in Japan! Therefore you will use the Japan CSS, but bring across the Roaming Sensitive settings from Rayleigh.’

UPDATE – 050815

This is probably the only topic of CIPT2/TVOICE that I am struggling with. It’s always the DMI rule that catches me! Lets try and simplify AGAIN….

‘If the Device Mobility Group IS THE same – Apply the CSS on the new Device Pool/Change CSS

If the Device Mobility Group IS NOT same – Use the CSS on the originating Device Pool/Do not change CSS

Easy concept I guess but a nightmare of a topic that I can never see myself using in my current role!! :/