Possible Causes for Inbound Calls Routing Issue to Country B
Question
A Cisco Unified Cm user is set up with one remote destination profile that has two remote destination numbers: the first destination number is the user's mobile phone in country A and the second is a mobile phone located in country
All outbound calls are centralized from the gateway at country A.
The user reports that inbound calls are properly routed to the mobile phone as long as the user is in country A.
But inbound calls are not successfully routed to country B.
Which two options could be the cause of this? (Choose two)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.AE.
The issue reported by the user indicates that inbound calls are failing to reach the second remote destination number, which is a mobile phone located in country B. It is important to note that outbound calls are centralized from the gateway in country A. Based on this information, there are two possible causes for the issue.
The rerouting calling search space assigned to the user's remote destination profile must have access to international calls. The first possible cause of the issue could be related to the rerouting calling search space assigned to the user's remote destination profile. If the rerouting calling search space does not have access to international calls, then inbound calls from country B may be blocked or restricted. To resolve this issue, the administrator needs to verify the rerouting calling search space assigned to the user's remote destination profile and ensure that it has access to international calls.
The value of remote destination limits should be changed to 2 instead of the default value of 4 under the end user page. The second possible cause of the issue could be related to the value of remote destination limits. By default, the value is set to 4, which means that a user can have up to 4 remote destination numbers. However, in this case, the user has only two remote destination numbers. If the value is not adjusted to 2, then the system may not be able to properly route calls to the second remote destination number. To resolve this issue, the administrator needs to adjust the value of remote destination limits to 2 under the end user page.
Other options mentioned in the answer choices may not be relevant to the reported issue or may not address the root cause of the problem.
The enable mobile connect option must be selected under the user's second remote destination number: This option is related to Mobile Connect, which allows a user's remote destination phone to ring simultaneously with the desk phone. However, it is not relevant to the reported issue of inbound calls failing to reach the second remote destination number.
The enable mobile voice access option must be selected under the end user page: This option enables users to access their Cisco Unity voicemail box from a remote destination phone. However, it is not relevant to the reported issue of inbound calls failing to reach the second remote destination number.
The value of maximum wait time for desk pickup should be changed to 20000 instead of the default of 10000, under the end user page: This option is related to the maximum amount of time a call can wait before being answered by the desk phone. However, it is not relevant to the reported issue of inbound calls failing to reach the second remote destination number.
