Mobile Voice Access with MGCP not working

[m.ranger]

Hi all,

I have a installation with a MGCP gateway and want to configure mobile voice access (MVA). I configured a h323 gateway to the IP address of the MGCP gateway and configured hairpinning for my MVA number.

• If I call my MVA number 98601905 from external which is translated to the internal number 1911905 I get an "destination out ouf order" in ISDN signalling.
• If I call my MVA number 1911905 from internal I get an fast busy

*Mar 12 08:20:37.953: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0xBEF1

       Cause i = 0x809B - Destination out of order

• DID from external is 9860XXXX which is translated to a internal number "site code+extension" = 191XXXX
• Translation from 9860XXXX to 191XXXX is done by Translation Pattern which is triggered by Gateway CSS
• Everyone is my all Phones Partition and is reachable by all Gateway CSS and Phone CSS
• 10.131.14.30 is my CUCM PUB, CUCM SUB is existing but not in focus for configuring MVA at the moment.

My Configuration details:

voice service voip

allow-connections h323 to h323

application

  service cucm http://10.131.14.30:8080/ccmivr/pages/IVRMainpage.vxml

dial-peer voice 19041 voip

service cucm

session target ipv4:10.131.14.30

incoming called-number 1911905

codec g711ulaw

!

dial-peer voice 19042 voip

description Mobile Voice Access

preference 1

destination-pattern 1911904

session target ipv4:10.131.14.30

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

CUCM - Service Parameter:

     Mobile Voice Access Number:     1911904

CUCM - Media Resources - Mobile Voice Access Directory Number:     1911904/Everyone

CUCM - Route Pattern: 1911905/Everyone pointing to RouteList of H323 gateway for MVA

Can anybody see my mistake? User should dial external number 98601905 (internal 1911905) to access MVA.

Best regards

Manfred

[chrysostomos1980]

HI

Your config is not look correct

Pls check this similar discussion.It will solve all your questions

https://supportforums.cisco.com/message/3873342#3873342

Regards

chrysostomos

[m.ranger]

Hi chrysostomos

can you please tell me more detailed what is not correct in your opinion?

I looked at https://supportforums.cisco.com/message/3873342#3873342 and the only difference I have seen is that I use the IP address of CUCU PUB in the dial-peers and in the other case there has been a change to CUCM SUP IP address.

I made this change to my configuration - without any change.

Best regards

Manfred

[chrysostomos1980]

Hi

Did you performed the below steps:Its just an example

Get the IP address of the MGCP PRI gw

- On CallManager, create a dummy H.323 gw with that obtained IP address

- Use MVA hairpinning to redirect the MVA call :

- If MVA number is 69541236, and only the last 4 digits is passed to CallManager from the MGCP gw, I would create a Route Pattern 1236 (in a partition accessible by the 'Incoming CSS' of the MGCP gw) and point it to the dummy H.323 gw created

- You can then create a voip dial peer for incoming called-number 1236, with the mva service in VG

dial-peer voice 5001 voip

description Inbound dialpeer from UCM for triggering MVA VXML

service mva

incoming called-number 1236

codec g711ulaw

no vad

- I would recommend configuring Mobile Voice Acces number to be a different than 1236, to prevent a call loop. It also has to be unique. Let's say 5678 is a unique number for you. You can put in partition 'None', so that everyone can access it.

- Create another voip dial peer for destination-pattern 5678, and back to CallManager

- voice service voip

allow connections h323 to h323

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmfeat/fsmobmgr.html#wp1126351 walks you through the steps of configuring MVA with hairpinning.

[m.ranger]

Hi chrysostomos

in my opinion that is exact what I did.

The 1234 in the example corresponds to my 1911905

The 5678 in the example corresponds to my 1911904.

Sorry, but I do not see any difference between the admin guide, the other supportforum case and my config. Maybe I´m blind and do not see my own mistake or... don´t know what´s wrong.

• I did a restart of the voice gateway
• I restarted the MVA Service in CUCM
• I did not a restart of the complete CUCM

Best regards

Manfred

[chrysostomos1980]

Hi

The numbers in cucm are 7 digits?the incoming digits in mgcp gw config is 7?

Lets say that is 7 digits

The voip dial peers pointed to cucm are h323  dial peers ??

dial-peer voice 19041 voip

service cucm

session target ipv4:10.131.14.30   ---------this dial peer are for incoming calls from cucm ..You dont need the session target

incoming called-number 1911905

codec g711ulaw

!

dial-peer voice 5002 voip

destination-pattern 1911904   ------mva number  (this is the number that you configured as an mva numbner in cucm)

session target ipv4: Pub ip or try sub

dtmf-relay rtp-nte

codec g711ulaw

no vad

!

voice service voip

allow connections h323 to h323

!

[chrysostomos1980]

Hi Manfred

Any news regarding your issue?

Regards

chrysostomos

[m.ranger]

Hi chrysostomos,

sorry for the delayed answer.

First - there is nothing new in the behaviour of my MVA.

Second - My internal dialplan on CUCM is 7digit, 3digit sitecode and 4digit extension.

1905 is the Number which user should dial for MVA

1904 is the Number which is configured in CUCM for MVA (see above for a detailed description)

My Dialplan:

• Number in ISDN Setup from PSTN: 98601905
• MGCP GW receives 98601905 - Incomming CSS hits a translation pattern with translates it to 1911905
• now we are in our privat dialplan which is 7 digits for all DNs
• 1911905 is a Routepattern in "Everyone" Partition which is my Partition for all Phone DNs
• Routpattern 1911905 points to RL - RG - H323 Gateway with IP address of MGCP Gateway
• 1911905 is a voip dialpeer which triggers the application script
• 1911904 is the second dialpeer which is pointing to CUCM PUB

These are the dial-peers which are configured at the gateway at the moment. The session target in dial-peer voice 19041 could be deleted - but no change in the behaviour.

dial-peer voice 19041 voip

service cucm

session target ipv4:10.131.14.30

incoming called-number 1911905

codec g711ulaw

!

dial-peer voice 19042 voip

description Mobile Voice Access

preference 1

destination-pattern 1911904

session target ipv4:10.131.14.30

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

!

Best regards

Manfred