Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple location dailplan fails with x-ports

Status
Not open for further replies.

vtec

Programmer
Feb 13, 2002
44
NL
Hi,

Anyone experienced the following problem:

- You have a decentralized system across the US and Europe
- ARS code for the US is '9' and for Europe '0'
- Both the US and Europe have different location parameters
- Stations are either assigned to locations by means of their cabinet/gateway and/or IP adress (network-map)

Now, when you have a station that is an x-port there is no location assigned to it. The station defaults to location 1 and inherits the same ARS code and tables etc. Now, when you call this station and it is either forwarded or covers off-net, all goes wrong when calling from a location with DIFFERENT ARS tables and featurecodes. Example:

- Station 1000 is an x-port with remote coverage to 00204303202 (0 for ARS and then a local phonenumber in the Netherlands, Amsterdam)
- When calling from the US you will get the operator (since 0 is attendant in the US)

Anyone seen a solution for this problem? It only affects x-ported stations...

Rgds,

David
 
Do you have two different servers working as standardlone server in US and Europe? If yes, I don't think the x port station has confused the location because it was configued in the European system. Since the staion 1000 is a virtual staion, why not configured it as a VDN number, and you can route to the destination number in vec, maybe you can try it. If the US and European system is controled by one server, can you replace the 0 as the TAC number of the trunk in European site, but you shoud set the Dial Access in Trunk group to Y. Maybe it works.

Regards
 
We have the same problem and don't know what causes this.
I also solved it by using the trunkcode in the remote cover instead of a 0 or a 9
 
Guys thanks for the info, however I do not want to enable the TAC because of possible toll fraud. Also, has anyone tested this situation with IP agent in telecommuter mode?
 
There are a couple of solutions to this problem.

1. Assign a port.
2. Use a COR assigned to a different partition group.





James Middleton
ACSCI/ACSCD/MCSE
Xeta Technologies
jim.middleton@xeta.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top