telman2010

Are you wanting to foward it to a specific number like a cell phone or something, if so just create a virtual and all call foward that virtual to the specified number, then terminate that did number to the virtual you created. If you don't have off premise call fowarding allowed you might have to set that up as well. What route do you did's dome in on? You might have to turn on route to route connections as well.

JJGable

When we fwd a DID back out our PRIs, we are getting low volume. So we want to FWD out on a copper route (Route 1). I have it set up as a virtual, CFW to the outside number (9+xxx-XXXX) but its going out like everything else on the PRI. If it were going to a Centrex number that started with a 6, it would go out over the centrex route (#4). Is there any way I can take this 4 digit DID and send it out to the full 7 digit number on route 1??

telman2010

It sounds like you should be able to set up a direct access code for your copper trunk route. Then foward your virtual out using the new access code (8, 80, 81, xxx-xxxx whatever you want to use) and it should work.

JJGable

Yes, How do I set this up and would it be easy to delete whene we are finished??

2400H/M

This is not as difficult as you think, providing that your calls are allowed to route advance from the PRI to your copper route 1.

First use the command ASCL and find out what the RSC of the extension in question is and write it down.

Next enter the command ARSC, you will see that there is an area to enter the route and that there are RSC's 0 - 15 across the top and RRI 0 -3 down the left side. Under the route data enter the route for the PRI, you will see that data will be filled in with a 1 (allowed) for the RRI's down the side for the individual RSC's across the top. (this is just building an allow table for the route versus the RSC) Look and see if there is an RSC with the RRI's 0-3 set for data = 0. Repeat this for route 1 the outgoing copper route. Hopefully you will have a common RSC for both routes where the RRI's 0-3 are all 0. If you do, then this will be relatively easy.

Do this and come back and post the RSC of the phone from ASCL and the common RSC that has data = 0 for the copper route and the PRI route. Then we will move on to the final step.

Here is an example of how ARSC might look. Hopefully this makes a little sense. Even though the zeros and ones are skewed in the example.

RSC 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
RRI 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0
RRI 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0
RRI 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0
RRI 3 1 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0

JJGable

The RSC for the set from ASCL is 1. PRI route (102) has RSC 0 , all RRIs are 0 but Copper route (1) has RSC 0, all RRIs are 1. After that, both routes for RSC 1 -15 have all RRIs at 1.

2400H/M

How big is the switch? Is it a single stack or multiple stack. A lot of people will program all the RRI's as data = 1, when in fact only 2 to 3 RSC's are actually used. Also what type of switch is it? HDS, IMX, IPX etc. If you can not tell, does it have a CPU with a floppy drive, FLASH card, or firmware? I ask this, because I am trying to determine the best way to proceed. If it is an IMX or IPX with eclipse commands, we can just do a LEN list and find an RSC that isn't used. It is somewhat time consuming, but it is a good listup to have, and it will help you document your programming.

JJGable

It is a multi stack IMX with a floppy drive.

2400H/M

OK. This will be somewhat time consuming for you, but we need to know if all of the RSC's are in use. Go into the eclipse MAT command and do a complete LEN list. Start at 000001 and go through the last LEN for the number of stacks that you have. If this is not a UMG, it will not be higher than 073317. Look through the extensions, and see if all of the RSC's are used. If you have multiple RSC's that are not used, that is OK. We will pick one.