Jabber Mobile Android 11.9.3 over Expressway DVO-R alternate number

[D!DoubleU]

Hi guys,

problems with my Jabber for Android and DVO-R.

I have CUCM 11.5 SU4 and Expressway 8.10.3 for MRA configured.
All is working also over MRA (VoIP, Chat, Video, DVO-R with the configured MobilityIdentity)

Version of Mobile Jabber is 11.9.3.257962 and Android 7.0.

If I want to use DVO-R with the option in Jabber use alternate number, I can type in the number and save.

In Jabber it looks fine, but on CUCM the MobilityIdentity is still my mobilenumber and also not a second RemoteDestination with my second phonenumber is configured.
And as a result the DVO-R dialing fails. there is a short beep on the mobile and errormessage (not valid number or busy, check number ....)

But if I configure my second number instead of my mobile as MobilityIdentity it works.

So it is not a question of rerouting css and dialplan etc..

What's wrong?
Is there a missing configpart in CUCM to accept alternate numbers for DVO-R?

Where can I check on CUCM adminpage after the alternate number in Jabberclient is setup?
Is there a second RemoteDestination?
Or is my MobilityIdentity temporary overwritten with this number?

KR
Dirk

[Mohammed al Baqari]

Have you followed this?

https://www.cisco.com/c/en/us/support/docs/unified-communications/expressway/200198-Configuring-Dial-via-Office-Reverse-to-W.html

[D!DoubleU]

Yes.
Configured as described in this document, step by step.

[Mohammed al Baqari]

What permissions are assigned to end user

[D!DoubleU]

Standard CCM End User
Standard CTI Enabled

and all Standard CTI Allow "......."