Wierd PRI/Target line issue 2

[Norstarguy]

Hello guys-

I've got a system I'm trying to program remotely that I'm having an issue with and can't seem to figure out.

I've done numerous PRI installs without a hitch, but haven't seen this problem before. Got the target lines built, got outbound working fine with the routing, etc- however the calls aren't being routed properly across the target lines...in fact, they won't ever ring on the targets. Only rolls in to the prime set on the PRI Trunks, ie x6800 in this case.

I have verified from the provider end that they are sending me 4 digits (as is programmed in the MICS), so that isn't the issue, had their NOC on the phone verifying that they can see the 4 digits going out to my MICS on test calls...but I've been beating my head against a wall on this for the last two days.

Any ideas? I'm really of the opinion that it's something screwy on the circuit itself, but trying to tell VZ that has its own "complications" LOL.

TIA-

NG

 

[NorstarWiz]

What type od switch are they coming out of in the central office? What protocol are you set for in your switch, Ni-2, dms100,dms250, or 4ess? I seen problems like this where the CO was coming out of a 5ess and i was set to NI-2. Make sure Verizon is ginving you NI-2 or some call it National and you may clear up the issue.

Let us know what you find.

 

[Norstarguy]

Internal CSU, Marv01.

NorstarWiz- The switch is set to NI-2, and Verizon is supplying NI-2. Confirmed this with the tech the other day (who confirmed it with Engineering).

Didn't get a chance yesterday to get anywhere with it, so I'm hoping to give it a shot on Monday. We'll see what happens when we swap out the Combo card.

NG

 

[senk1s]

did this get resolved?
are u using a Rel 2 cartridge - as there were wierd problems on Rel1 NVRAM

 

[Norstarguy]

No, I still have not gotten it resolved. Having problems getting the tech (who I'm helping out) on site to get the card swapped out.

Am hoping to try again tomorrow, but we'll see. I'll update as soon as I know where we're at.

NG

 

[jerryreeve]

Can you make calls out on the PRI?

what is the config of your target lines?

since you have received calls on the prime set for the trunks then you may want to go back over the settings for the received digits (should be 4) and assignments of target lines to a telephone set.

working with the RAD you can use the terminal emulator and assign a target line to the rad's telephone set (the one on your computer screen) and see what is happening.

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

 

[Norstarguy]

Jerry-

Config of the target lines is receive 4 digits, programmed as such, (ie 6885), primed to x6885, busy to prime.

Only dealing with 4 particular phones setup as test sets at the moment, and have assigned the lines to the RAD extension to monitor incoming traffic (of which none shows up).

Can make outbound calls from the site without issue.

NG

 

[MJSD333]

Norstarguy,
I did a circuit(not PRI) on an MICS 6.1 a couple of weeks ago and I kind of had a similar problem. I forgot to set Answer with DISA to No. After that change, calls to certain target lines tested good. Before they would only go the the reception set which was the control set.Outbound calling worked from the beginning.
Dmac,

 

[hawks]

Do you know what type of switch that you are connected to back at the CO? If it is a 5ESS try changing the NSF to WATS. Also when it rings to the PRIME set have someone view the information and see what line number you get. Slim chance but probably not likely the COMBO card has bad DTMF receivers on it.

 

[Norstarguy]

Hawks-

The system is supposedly a GTD5, according to my paperwork-

NG

 

[Norstarguy]

OK guys-

Swapped out the combo card, had no effect. One thing that I have noticed here is that they are sending me the name info on the Caller ID, and this is the first time I think I've seen that on a PRI on a Norstar.

I was wondering if (even though the Norstar seems to be reading the name info ok and displaying it, albeit only to the prime set of the trunks) this might be causing a problem with the receive digits?

I'm scraping the bottom of the barrel here, and not having any luck with finding anything on my end that is wrong. Any more suggestions?

NG

 

[senk1s]

when it is ringing on the prime set - is the call coming in on the target line or the physical line?

if it is not on the target line - then the DNIS information is not reaching or being misread by the Norstar

(if u do a feat811 it'll display all options)

 

[Norstarguy]

Hello senk1s-

It's ringing in on the prime set of the trunks, not the target line(s)- if it was coming in on the target lines I wouldn't have any problem (and oh what a happy day that would be). LOL.

The issue at hand is that I've been on the phone with Verizon's NOC troubleshooting as well as requested to have a tech go to the site and verified (which he has) that the digits are coming thru the circuit prior to hitting the Norstar...so at this point if it's on Verizon's side it's much deeper than anything we found after about 4 hrs on the phone.

The reason why I brought up the Name on the Caller ID on the PRI was because I seem to recall the NOC tech saying something to the extent that some switches wig out when they see the Name info I didn't give it much thought at the time because the calling name seems to work fine on incoming calls (albeit on the prime, not the targets)- has anyone here had any experience with this on a PRI on a Norstar?

NG

 

[luv2ski]

the name or number is the reason most go to the pri ..should not be an issue....have you called itas..also try yahoo groups BCM-Norstar groups...just dont ask basic question"like the ones we are seeing in this forum"

http://groups.yahoo.com/group/BCM-Norstar/

6 months until ski season starts...sadly i must resign myself to the warmer weather"this will include a normal 8-5 work day, 5 days a week"

 

[polarbear85]

Looking back at the beginning of this thread, I see MICS 4.1. My impression from reading this forum is that PRI with version 4 is buggy at best, so... at risk of sounding like a front line tech support guy, have you considered upgrading to the latest software? I have to wonder if your "customer supplied" equipment might be a mix of firmware levels that don't necessarily get along, particularly with 4.1.

My direct experience is with MICS 6.1, and caller ID with name on PRI has worked wonderfully from day 1 (Oct 2003).

polarbear85

 

[Norstarguy]

Thx for the feedback, polarbear85-

Yes, I've thought about that, from the beginning- however I'm stuck in a situation trying to explain to the customer that this might be a problem, the customer telling me it worked fine in another office (with T1 service, not PRI) and steadfast resistant to having to fork over the money to upgrade the MICS software as well as the software on their NAM.

Trying to get a vendor meet scheduled for sometime this next week to get this wrapped up, so we'll see what happens then.

NG

 

[ThePhoneGURU]

Hey NorstarGuy,
I work for a Telco out in Toronto who's switch is a 5ess...I believe a customer we were trying to turn up was running Norstar. The Interconnect wasn't recieving calls although our NOC stated that the digits where being sent to his switch..all calls were bouncing back NIS message.
I know that the TELCO solved the problem because of some glitch in software in 5ESS when using NI2 protocol w/name display. By default TELCO provisioned PRI with Name Display flagged to Y, as soon as the NOC flagged to N calls started hitting far end. Not sure if this helps or relates...just trying to give suggestions...
Good luck

 

[Norstarguy]

PhoneGURU-

Thx for the tip. Once we get our vendor meet setup, I'll bring that up as the first course of action, just to see if we get anywhere. Thx!

NG

 

[Norstarguy]

Another update-

Had another system come in for another customer (also with PRI) that I had a tech go out and pop on the wall at this customer's location- Brand new MICS w 6.1 sw-

Programmed the PRI, setup the first target line, and boom, came right up. No ifs ands or buts-

So now, I'm stuck in a bit of a situation trying to figure out why the 4.1 that was originally installed didn't work as it should've, but at least I've eliminated the fact that there was a circuit problem.

NG

 

[senk1s]

thats an interesting twist
do u have Rel 1 NVRAM? - if so that probably needs to be changed, as it had some memory corruption issues
did to try rebooting the MICS (i had to ask)

 

[Norstarguy]

Not for sure, senk1s- I'd have to get a tech to verify onsite.

Rebooted several times over the course of the past few weeks.

NG