Continent/Country roaming users

Unanswered Question
Jul 10th, 2008

Does a document exist which assists in configuring the CM 6.1 to use the gateway in the respective country where the call is targeted?

Example: Users from UK travel to Romania and login to the Cisco VoIP phones at that location. Calling internally in the LAN/WAN poses no problem, however, calling to a Romanian external number from Romania is routed over the (configured users) UK gateway, this can be a cost intensive scenario. It would of-course be fine when he/she is phoning a number in UK, this would greatly reduce calling cost. Is there a way to automate the call initiation so that the gateway in the respective country where the user currently resides or phones to is used?

Any assistance or tips would be appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (5 ratings)
Loading.
tomide_ccie Thu, 07/10/2008 - 06:06

what is the partition and CSS on the device, is UK and Romania in the ame cluster, your problem basically comes down patitions and css on the phone and the device profile, make sure the css on the phones can search the partitions, where you have your patterns and gateway.

Ayodeji oladipo... Thu, 07/10/2008 - 09:10

Your best solution as Javalenc has pointed out is to use device mobility.

The alternative is to use CSS anbd partitions,

Make sure that the CSS on your phones in Romania only have access to the the gateway in Romania and ensure that Your gateway in UK only have access to the gateway in UK.

Configure your users such that the CSS on them only have internal access and not PSTN access, this way they will be forced to use only the CSS on their phones for PSTN dialing....and since you have restricted the phone on each location to use the local gateway, that solves your headache

CSS rule is like an OR logic...Its the css on your phone + CSS on your device that detrmines the final CSS rule that will be applied to the dailed number.

This is what we have here in our network becaues we are running CCM4.X which does not have device mobility

KlausSteger Mon, 07/14/2008 - 02:41

Thanks for the help.

FYI:Both regions are in the same cluster.

We remove the CSS from the line and placed it on the device. Noticed that the line CSS took precedence over the device CSS, if we remove the lines ability to go at least nationally (internal only) and due to the lines precedence over the device, we could not phone externally.

We were able to work out a good solution for our situation, the devices now have a CSS to their local GW's and the line has no CSS at all, this way the device setting has full control.

We are going to look at setting up device mobilty, but this gives us a temporary fix until we can implement device mobility properly.

Thanks again for the assistance!!

Ayodeji oladipo... Mon, 07/14/2008 - 02:49

Hi,

3 things...

1. Good to know you found a temp solution

2. The line css and the device css are added to detrmine the final css.

So if your line css cant call externally and your device css can, you will be able to call. This is how I have my office system setup!

You can put a line css on your lines and it will work...test it and see. Make sure the line css is an internal one that doesnt have access to the Route patterns partition for the local gateways. This way only the CSS on the gateways will be used.

This is how my office is setup...

3. Lastly, always remeber to rate useful posts!

Actions

This Discussion