Symptom:there are 2 problems fixed with this cdet.
- UCM Core Dump in shanghai alpha when Jabber user calls it's own DN number
- Wrong presence status in Corporate Directory for mobility devices (dual mode and single mode remote destinations)

Conditions:It happens when Jabber mobile is configured without MI and DVO is disabled.  When mobile user is calling itself, it triggers the core. 

also, when a mobility device is configured without a mi or rd, single number reach status reported as idle as supposed to unknown. this leads to wrong presence status.