Mobile Voice Access issue

Unanswered Question
Jul 6th, 2010

Hi All,

I have everything configured as given in the mobile voice access configuration guide,

My SNR is working fine....when i dial in to MVA, it is promping to enter userID and password.  After successful login i enter option 1 to make a external call. once i enter the external transfer number followed by # i am getting a dead silence for some time and  the call is getting disconnected.

when i execute debug voice application vxml all command on the gateway and i am able to see the external transfer number in the RDNIS field. but i dont see any outbound pots dialpeer being matched.

My question here is, once i enter the external number in MVA how does CUCM process the call?



I have this problem too.
1 vote
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
htluo Tue, 07/06/2010 - 10:35

Once you enter the destination number, CUCM will try to make an outbound call to that number.  Of course, CUCM will expect any prefix (like 9, 91, etc.) like any regular outbound calls.  If you don't want to enter the prefix on MVA, you may configure application dial rules.


aravindhanelango Tue, 07/06/2010 - 10:50

Hi Michel,

I was able to see that the application was abel to recognise my external transfer number....but i dont see any kind of number analysis happening for the external transfer number in CUCM SDI logs.



htluo Tue, 07/06/2010 - 11:02

If you don't see DA on CUCM, you'd better focus on the H323 GW config.

Depending on your service provider, they might only send the last couple digits of the DID number.  You need to make sure those digits match your CUCM configuration for MVA.


Yufang Zhou Tue, 07/06/2010 - 21:14

You need to make sure the number configured in Call Routing --> Mobility Configuration --> Enterprise Feature Access Number can be matched against one of your voip dial-peer destination-pattern configuration, and if this is the case, you also need to make sure the h.323 gateway inbound calling search space contained the partition for Enterprise Feature Access Number which is the route partition configuration for Enterprise Feature Access Number.


This Discussion