03-22-2018 05:56 AM - edited 03-17-2019 07:24 PM
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
03-23-2018 03:27 AM
03-23-2018 03:39 AM
Yes.
Configured as described in this document, step by step.
03-23-2018 04:19 AM
03-23-2018 05:19 AM
Standard CCM End User
Standard CTI Enabled
and all Standard CTI Allow "......."
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide