Help with linepool restrictions & destination codes

[bwtc]

We recently switched over our corporate site from analog to a digital voice T1 (not PRI).

We have a 2nd T1 that is being used to provide Frame data to our remote location, along with 4 tie-lines.

The remote location is a warehouse running MICS 6.1 (G10). Corporate is running on MICS 5.0.

Prior to switching to the digital T1, all calls from the warehouse went through their own copper lines. We took one of the lines & put it in its own line pool, which was linked to a 6-digit destination code, that we would give to truck drivers, for them to place calls. We do not want temps, etc using the phone.

POTS was pool A
E&M between facilities was pool B
Foyer phone was pool F.

Anyways, we wanted to have as much outbound traffic flow through the T1. So, I set up a new schedule that would take the "9" access code & go through pool B, with an overflow to pool A.

This is working fine. We want to disconnect 2 of the 4 copper lines at the warehouse, since we no longer see the need for them.

Here is the problem...

We do not want to keep a seperate copper line just for the truckers. And, we do not want to dedicate one of the E&M channels (we only have 4) to use a COS associated with DISA.

I want to be able to dial an access code to gain access to a line pool (pool B), but do not want to allow the "9" access code (which is linked to the pool) to be used from this set.

I tried set restrictions, where I created a filter that would prohibit "9" from being dialed. I was hopeful that I could associate the "9" with a route, via the DialOut parameter. However, the set restriction does not allow the access code to work.

I have worked with my vendor on this, and he is unsure how to accomplish it.

Hopefully you can make some sense of what I am trying to accomplish.

Thanks

 

[bwtc]

I figured out a way around the above mentioned problem...

The phone in the foyer has access to line B, and set restriction on, so 9 cannot be dialed.

I took the 2-digit access code & assigned it to Route 001, which is linked to Pool B, absorb length 00.

On corporate side, I set-up the exact same code, which is set for Route 000, that accesses our T1.

I still would appreciate any advise on a better way to do this.

 

[hawks]

So let me understand you have 4 lines going across from site A (main site) to the site B (warehouse). You want people to be able to call someone from A to B but you only want the truckers to be able to use the T1 lines at site A to make calls from site B.

 

[bwtc]

Kind of...

We have 4 tie lines at the warehouse, and 4 copper lines (soon to be reduced to 2).

If someone dials 9 at the warehouse, we want it to go through pool B, to go thru our T1 at corporate, with an overflow to the copper.

Problem is the foyer phone... we do not want dial 9 to work; we want a destination code that will allow the T1 at corporate to be accessed.

Because of the set restriction, even if a code was entered, it would ultimately pass a "9" to corporate, which I would then receive a restricted call message.

The way I got around it was to setup the same code at both sites, and at corporate, have the code be linked to pool A.

So at the warehouse, (let's say the destination code is 655622), the code is entered, it goes through pool B to connect to the T1 at corporate. Corporate sees the code 655522, and accesses pool A, which is the voice T1.