Mobile voice access Remote destination profile doubt

[prakashar]

Hi,

A company has 2 offices one at San Jose and the other at Shelton (Single CUCM cluster). I have Mobile voice access implemented.San jose MVA number is x and Shelton MVA number is y.

Now, if a Shelton user is at his home location, he uses Shelton MVA number, whereas when he moves to San Jose, he makes use of San Jose MVA number.

Here is my question:

Is it possible to achieve the following,

1. Shelton user moving to San Jose and dialing into San Jose MVA number should utilize San Jose voice gateway.

2. San Jose user moving to Shlton and dialing into Shelton MVA number should utilize Shelton voice gateway.

-Prakash

[Joseph Martini]

The DID number that is used to hit your local gateway to invoke the VXML application can be different than the number configured as your MVA DN, so yes this will work correctly as in your example.  You will have a different DN to hit each gateway, which calls the same VXML script to send the call to call manager (using the same DN).

[prakashar]

Hi Joe,

I understand that outbound dialing rights after authentication is decided by concatenation of line Css + Device CSS (Remote destination profile CSS).

Assuming that I am a Shelton user.

So if this resulting CSS has a static configuration to route calls through Shelton only, how is it going to route through San jose gateway when I use san jose MVA number?

Home Location Call Flow:

PSTN User-->Shelton (MVA Number)-->Shelton Gateway-->CUCM Cluster 1-->Auhentication-->Outgoing gateway is shelton gateway(Using Remote destination profile CSS)

Remote location Call flow

PSTN User-->SanJose (MVA Number)-->SanJose  Gateway-->CUCM Cluster 1-->Auhentication-->Outgoing gateway is shelton  gateway(Using Remote destination profile CSS) ***** Here is where my problem is i want to use SanJose Gateway for Outgoing calls*****

I thought about Standard Local Route Group concept to achieve this, but for MVA Standard Local Route Group will not work as the Standard Local route group will be work based on Device Pools and Device Pool of the Remote Destination Profile is static and will always be Shelton.

Thanks,

Prakash