mattKnight
Programmer
Hi All,
I have multiple remote gateways and local trunks across the EMEA region, all on a UK core ACM 5.2.1 system. Mostly we use 96XX or 96x1 IP handsets in a multi location environment. This all works as expected.
However, we have started to roll out One-X communicator as a softphone for remote (not office) users. However, our VPN solution is based in a single location which means that all IP addresses used by RAS users (and hence One-X Communicator) are sourced from a single range. This means that it is not possible to use the ip-network-map to link these users to their "home" ip-network-region and location.
From a user's perspective, this means that for example a Dutch user has to dial a local Holland number as an international number, as the trunks it uses are in the UK; against the expectation that home workers using IP softphone will reduce call costs - it actually increases them and adds a level of complexity that many won't be able to grasp... To make matter's worse, the Dutch hard-phone users (for example) dial 9 for attendant access and 0 for ARS access - and the softphone users do the opposite, unless they are in the office!
What I am looking for, is a suggestion about how I can map an extension/user to a use specific location's trunks regardless of their physical IP address / ip-network-region and location.
The only option I can see at the moment is a COR for each location and using partition group routing to route the call to the user's "home" route patterns - but it is a lot of work and is a very fundamental change to our PABX call routing.
Other options that are not going to happen
1) Change RAS infrastructure - no way is this going to happen
2) Upgrade to ACM - is planned but I can't bring this forward to a timescale that suits.
All thoughts!
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
I have multiple remote gateways and local trunks across the EMEA region, all on a UK core ACM 5.2.1 system. Mostly we use 96XX or 96x1 IP handsets in a multi location environment. This all works as expected.
However, we have started to roll out One-X communicator as a softphone for remote (not office) users. However, our VPN solution is based in a single location which means that all IP addresses used by RAS users (and hence One-X Communicator) are sourced from a single range. This means that it is not possible to use the ip-network-map to link these users to their "home" ip-network-region and location.
From a user's perspective, this means that for example a Dutch user has to dial a local Holland number as an international number, as the trunks it uses are in the UK; against the expectation that home workers using IP softphone will reduce call costs - it actually increases them and adds a level of complexity that many won't be able to grasp... To make matter's worse, the Dutch hard-phone users (for example) dial 9 for attendant access and 0 for ARS access - and the softphone users do the opposite, unless they are in the office!
What I am looking for, is a suggestion about how I can map an extension/user to a use specific location's trunks regardless of their physical IP address / ip-network-region and location.
The only option I can see at the moment is a COR for each location and using partition group routing to route the call to the user's "home" route patterns - but it is a lot of work and is a very fundamental change to our PABX call routing.
Other options that are not going to happen
1) Change RAS infrastructure - no way is this going to happen
2) Upgrade to ACM - is planned but I can't bring this forward to a timescale that suits.
All thoughts!
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.