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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Norstar can receive calls can't call out

Status
Not open for further replies.

hippster2001

Technical User
Jan 24, 2011
26
We have a customer who has had a Norstar for a long time. They called to say they can receive calls but can't dial out. When they dial the access code the display says line busy. Checked programming and it looks okay. We changed the trunk module. Any ideas?
 
Maybe you have a dead line within your line pool or just not enough lines? Do you have a reception phone where all lines appear? Check every line on the system that way or with a butt set from the rj block.

Jeremy J. Carter
Charm City Communications
Norstar. BCM. CS1000 Programmer
 
OK well that changes things. Did you check the status of the DTI card? Try to disable and reable it, also check to see what the card itself is doing. Does it have any lights lit on it?

Jeremy J. Carter
Charm City Communications
Norstar. BCM. CS1000 Programmer
 
Also see what rout the desti code is using and make sure that rout is set to use the PRI.
 
Hawks is taking you down the right path.

The old NVRAM's (rls 01) would reset all the routes to Use Pool A in the event of a power failure or reboot. (if I remember correctly!)

Check your route and make sure it is set to Use PRI-x and not Pool A.

-SD-
 
Nortel PRI Route programming

On Mics 4.1 and 5.0 PRI programming will sometimes lose route information and customers will be unable to make outbound calls even though they can receive inbound calls

To program

Enter programming
Feature ** 266344
266344 (password)
Bottom Right twice (services)
Top Right
Bottom Right twice (Routing Services)
Top Right twice (show route)
001
Top Right
Bottom Right (it probably says use:poolA)
Press change (change to PRI A)
Bottom Right (Service type:public)
RLS (exit programming)



Next check that there are no limitations on Route 1

BR twice to Services
TR
BR twice (Routing Service)
TR
BR (Dest Codes)
TR (Show Dst Code:)
BR Dst Code: 9
BR (should say “end of list”. If there are other Dst codes such as “.” or “9.” delete them)
Go back to Dst Code:9
TR (normal 001) If it is 000 or anything other than 001, change to 001
TR AbsorbLength:ALL (or change to ALL)

By setting to AbsorbLength:All this will override Dialing Plan limitations which could limit local area codes, 7vs10 digit dialing or long distance dialing


In some situations calls may fail to complete or dial correctly on a PRI. Someone may have set dialing rules in the past causing issues for numbers such as 404-351-4114 in which the “411” is seen by the phone system as someone dialing “information” and the system immediately sends out the call without waiting for the last “4” If the Absorb Length All is set up Public Network DN Lengths are not necessary since any call on PRI-A will be sent to the PRI out and out to the carrier.

Goto System Programming, Dialing Plan, Public Network, Pub DN Lengths, scroll using the bottom right button to “411” and remove it. Then make a test call to the number having a problem and make sure it will dial correctly, also call 411 information and make sure that goes through as well.


7/2008

Before Routes and destination codes will work, remove line pool and external access codes under Line Programming.

Under Services, Route Services and Router, you can use Route 000 and set it to pool A vs PRI-A if you don’t have PRI installed. Leave the External Number blank unless you have carrier access codes that need to be dialed.

For destination codes, typically program “9, Any” and set normal and night to absorb 1 will allow all calls to route out correctly. At O’K Duluth we had a DNIS number that started with “96” which was causing “9, Any” not to work for calls starting with 6. In this case we had to program destination codes 91any, 92any, 93any, 94any, 95any, 96any, 97any, 98any, 99any and 90any. This then allowed calls to route out correctly for 770, 404 and 678 numbers.

Last check the Public DN lengths for prefix default and make sure it is set to 10 vs 7 for Atlanta 10 digit dialing, 0=11, 00=12, 01=17, 011=18, 1=11, 411=3 and 911=3
 
The problem was Telco. ATT used a Cisco 8310 to deliver the T1 to the Norstar. It lost it programming.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top