We have to Norstar Systems with point to point PRI's. We can dial extension to extension dialing, and dial out to local trunks on the main system. We can not figure how to route incoming DID calls coming into site 1 and route the call over to site 2. Any help would be appreciated.
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!
DID Routing with Advanced Private Networking 1
- Thread starter bdalida
- Start date
-
1
- #2
- Thread starter
- #3
Try this
Example: Digits 1234 (did) comes into system A on Target Line 157 and you want those digits to end up on system B at ext 245.
1)Take a phone on system A and assign Target Line 157 to Appear and Ring.
2) Make sure that this phone has redirect capabilities turned on and can call ext 245 at system B.
3) Use Feature 84 for Line Redirect, when it ask for line to redirect choose Line 157.
4) Then when it ask for which line to use to go out choose Intercom and put in whatever number you use to go to extension 245 at system B.
5) Test it and when you get it to work then you can unassign line 157 from the phone and it should continue to work.
When you need to change it or cancel it just follow the same steps. Make sure you keep up to date paperwork because if you are doing alot of these and then wanting to make changes later it could be a nightmare if you don't have all the information down.
Example: Digits 1234 (did) comes into system A on Target Line 157 and you want those digits to end up on system B at ext 245.
1)Take a phone on system A and assign Target Line 157 to Appear and Ring.
2) Make sure that this phone has redirect capabilities turned on and can call ext 245 at system B.
3) Use Feature 84 for Line Redirect, when it ask for line to redirect choose Line 157.
4) Then when it ask for which line to use to go out choose Intercom and put in whatever number you use to go to extension 245 at system B.
5) Test it and when you get it to work then you can unassign line 157 from the phone and it should continue to work.
When you need to change it or cancel it just follow the same steps. Make sure you keep up to date paperwork because if you are doing alot of these and then wanting to make changes later it could be a nightmare if you don't have all the information down.
- Thread starter
- #5
No problem thanks, once you do it a couple of times it really don't take that long. Like I said the problem comes if you don't keep good notes and you have to make changes later. If you have mulitiple lines you want to redirect then just assign more to the phone.
- Thread starter
- #8
bdalida,
We're about to do the same upgrade.
I'm pretty clear from the documentation that the 2 sides each have to start with different lead digits to make this work. Was this a new install for you or did you have to make numbering plan adjustments to accommodate existing extension numbers with similar lead digits residing at both locations?
Also, did you have to match the number of externally received DID digits to the internal DN digit length number? Or perhaps your system was already matched?
All of the Norstar documentation examples show equal digit lengths (internal and external) and so that is one of our questions before we pull the trigger and try to make the APN/ Centralized VM work. I wouldn't think that it matters since external DID digits can normally be any length relative to DN length. But unfortunately, the Norstar documentation is not really very complete or specific about answering questions depicting different scenarios.
Besides the DID target forwarding, what were some of the other sticking points that caused the gray hairs?
We're about to do the same upgrade.
I'm pretty clear from the documentation that the 2 sides each have to start with different lead digits to make this work. Was this a new install for you or did you have to make numbering plan adjustments to accommodate existing extension numbers with similar lead digits residing at both locations?
Also, did you have to match the number of externally received DID digits to the internal DN digit length number? Or perhaps your system was already matched?
All of the Norstar documentation examples show equal digit lengths (internal and external) and so that is one of our questions before we pull the trigger and try to make the APN/ Centralized VM work. I wouldn't think that it matters since external DID digits can normally be any length relative to DN length. But unfortunately, the Norstar documentation is not really very complete or specific about answering questions depicting different scenarios.
Besides the DID target forwarding, what were some of the other sticking points that caused the gray hairs?
- Thread starter
- #10
You don't have to have your DID's match your DN's, but I highly recomend you do. It makes things much easier. If the systems haven't been programmed yet, make everything match. Make sure the Rec'd# length matches your DN length also, just an FYI. If your DN's don't match your DID numbers, then you have twice as many target lines to program.
Are you going to do any advanced routing? Do you want to dial out local trunks on the remote or main site from the other system? If so you will need to set up a remote access package and assign your pri line pool to it.
Are you going to do any advanced routing? Do you want to dial out local trunks on the remote or main site from the other system? If so you will need to set up a remote access package and assign your pri line pool to it.
- Status
Similar threads
- Locked
- Question
- Locked
- Question