01-23-2013 12:19 AM - edited 03-19-2019 06:09 AM
Hi,
Single number reach is not working at all after a site was migrated to CUCM 8.6. We have a publisher and two subscribers. I am not seeing "Cisco Unified Mobile Voice Access Service" in two subscribers under Unified Serviceability while I can see it in the publisher.
I have configured other stuffs like Remote Destination, Remote Destination Profile, End-user configuration in CUCM as they should be. It is just hitting VM after configured number of rings. It
Can someone please advise where I should I double check for single number reach to be working? Could it be related to missing "Cisco Mobile Voice Access Service" in subscribers? Thanks in advance.
Regards,
Lay
Solved! Go to Solution.
01-23-2013 12:55 AM
Hi
You don't need to configure the Mobile Voice service unless you are using the dial-via-office feature. Most customers don't do that - it requires H.323 gateways and they are more intereseted in Single Number Reach.
The most common mistake with SNR is on the remote destination, you need to check 'mobile conect' or it won't work,and then once you have added it another (previously hidden) checkbox appears called 'line association' that you also have to check - people often don't notice this.
Otherwise - you just need to ensure the Calling Search Space and ReRouting Calling Search Space on the RDP are set to a CSS that can reach the remote destination number.
The remote destination MUST be over an ISDN or intercluster-trunk link, you can't use an on-net destination.
Regards
Aaron
01-23-2013 12:55 AM
Hi
You don't need to configure the Mobile Voice service unless you are using the dial-via-office feature. Most customers don't do that - it requires H.323 gateways and they are more intereseted in Single Number Reach.
The most common mistake with SNR is on the remote destination, you need to check 'mobile conect' or it won't work,and then once you have added it another (previously hidden) checkbox appears called 'line association' that you also have to check - people often don't notice this.
Otherwise - you just need to ensure the Calling Search Space and ReRouting Calling Search Space on the RDP are set to a CSS that can reach the remote destination number.
The remote destination MUST be over an ISDN or intercluster-trunk link, you can't use an on-net destination.
Regards
Aaron
01-23-2013 01:55 AM
Thanks very much for that, Aaron. It is working now. I was missing to check 'mobile connect' and 'Rerouting Calling Search Space'. Thanks for the explaination as well.
Regards,
Lay
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