Networked Norstars that cant dial 9-911

[actelcom]

I have 2 Norstars networked together. Each Norstar has its own ATT Local / LD PRI. The ATT PRIs will not support 911/611 etc, so I have 4 POTS lines on System A to support these calls. I just added system B, and need to use the POTS lines of system A for these calls. I am using CDP.
System A:
Dialing Plan, Network ID 6
Destination Codes:
9+Local, Route 001, Absorb 1
9+Long Distance,Route 2, Absorb 2(ATT will not take the 1)
9+911/611 etc, Route 000, Absorb 1
4A, Route 005, Absorb 0
Routes:
Local: Routes 001, Dial out: 775 (Att PRI's require 10 digits for local)Use PRI A, Service Type: TIE
LD: Route 002, Dial out nothing
CDP: Route 005, PRI B, Service type: SL1
Remote Access:
Remote package 002, Access to PRI A, B, Pool A
Remote Line Access: Line 001-023, and 31-53, Line 61 thru 64

System B:
Network ID: 4
Destination codes and routes pretty much the same except:
Destination code: 9611/9911, Route 006, Absorb 0
Route: 006, Service Type: SL1, Type public

From system B, I cannot dial 9911 or 9611 and gain access to the POTS lines in system A

 

[cook1082]

Remove The dest codes and start over with 911 then 91 then 9A then have them go out the specific routes you want them to.911 to analog 9A,91 out PRI.

 

[ptstechnician]

Do you have Remote packages setup in site A, so calls coming from site b are allowed to go out? I'm not in front of a KSU at this time, but I almost sure its Remote Packages.

 

[actelcom]

I do have Remote access turned on in system A, package 002 assigned to lines 001-023 (Pri A) as well as 061-064 (Pool A). I believe it is the remote package also.

 

[hawks]

Did you also turn it ion for the lines under REMOTE LINE ACCESS.

 

[actelcom]

Yes, I have Remote Line access for line 001-23(Pri A) as well as 061-064 (Pool A) os Pkg 001

 

[hawks]

I though you said pkg 2?

Under Remote Package did you also give it Line Pool Access to pool A.

 

[endlesswinter]

do you realize if you are sucsesful with this config that when a caller from system B calls 911 the responders will be sent to sight A?

 

[actelcom]

System A and B are at the same site. They needed to expand their system to provide more extensions.

 

[photon33]

I have had problems getting MCDN PRI networked system to obtain analog POOL-A dialtone over the span regardless of remote access packages. PRI always worked though.

ITAS could not resolve either.





------------------------------------------
Wash, rinse, repeat.

 

[RikRodgers]

Scarry. I assume system a is already running XC software, and fully maxed out on both fiber cards?

 

[photon33]

Your dilemma has made me think and if you want try to program this: system programming>dialing plan>Public network and add or change a 911 entry with a value of 4.

See if that fixes it.

If it doesn't, throw all your local and LD calls over to the remote pots lines and see what if any work.





------------------------------------------
Wash, rinse, repeat.

 

[tnphoneman]

If they are on the same site why not put 2 analog trunks directly into each system.

 

[hawks]

I belive photon is on to something. in system B you really need a prefix in the dialing plan for 9911 & 9611 because by default system B does not know what to do with these calls.

 

[actelcom]

Another Point. Since I am not close to the systems I have created a AUTO DN which allows me to dial in remotely to test. I have built the Remote Packages, Rem Line Access, etc. When I dial in to either system, I do a test to see if I can dial a 9+local number, and It will not let me dial out that way either. I am convinced it is in the Remote package access.