03-31-2013 08:38 PM - edited 03-19-2019 06:30 AM
Hello All,
I am trying to configure MVA in Call Manager 8.6 (1 Publisher - 10.0.2.3 with 2 Suscribers - 10.0.2.4 and 10.0.2.5). Call Manager is inactive in the publisher but active in all the suscribers. My gateway is a Cisco 3925 Router (MGCP). I have done the following things:
1. Enable MVA Service in Cisco Unified Serviceability
2. Configure Service Parameters:
3. Go to Media Resources > Mobile Voice Access. Set MVA DN to 8000
4. SSH into the Voice Gateway (IP Address: 10.0.2.10) and enter the following configurations:
service mva http://10.0.2.3:8080/ccmivr/pages/IVRMainpage.vxml
allow connections h323 to h323
h225 timeout tcp establish 3
destination-pattern 8000
session target ipv4:10.0.2.3
voice-class h323 1
dtmf-relay h245-alphanumeric
codec g711alaw
no vad
service mva
session target ipv4:10.0.2.3
incoming called-number 1998
codec g711alaw
5. Configured H323 Gateway, Route List, Route Group and Route Pattern in CUCM
However, dialing MVA number gives me a fast busy tone. The error shown in RTMT Tool is: (27) Destination out of order
Any help will be appreciated
Solved! Go to Solution.
04-08-2013 03:18 AM
Hi Chris,
Tried to add the command you mentioned. Still not working but there is some progress. The fast busy tone turns to no tone at all (the call is immediately dropped) and sh call application voice mva indicates that there is an incoming call (attached). I think the VXML script is triggered, as debug voice application vxml application shows something (attached). I have also restarted the gateway.
Edit: So the mistake is that the codec should be g711ulaw, not g711alaw.Now I can hear the female voice. However, the voice tells me that "you are not authorized to make calls, please contact your administrator" instead of asking to input remote destination/pin. Any ideas why this happens? I have set up remote destination profile and number correctly.
04-08-2013 06:09 AM
Hi Aldred,
Just want to confirm, do you have Enable Mobility/Enable Mobile Voice Access selected under User Management > End User
HTH,
Chris
04-09-2013 06:33 PM
Hi Chris,
Yes I did. Turns out the mistake is I did not add the DN in Remote Destination Profile. Now it's working.
However, is it possible for this scenario to occur?
1) My extension/DN is 1818
2) I dialled the MVA, entered my remote destination number and decided to call somebody (a remote mobile phone)
3) Instead of 1818 as the source (calling) number, the calling number is some other DID DN (for instance, 1900).
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: