Neax 2000 IVS CAS to PRI conversion failure

[dirtcheap]

A little over a year ago I had to convert a system in a hotel from a CAS T1 to Comcast PRI. I knew nothing about the Neax at the time so this forum got me through the change with few problems. Now I have another site with the same system that has to change to Comcast. I went through the same procedure as last time but I can't get it to work. Comcast says the D-channel is not coming up. I even pulled the Digital Trunk card and D-channel Handler to test them at the first site and they worked fine there. I quadruple checked the programming and can't find any differences. As near as I can tell the systems are the same. They were installed at the same time, by the same company, with the only difference being more single line cards for more rooms at the 2nd hotel. What can I check on the 2nd system to find out why it's not working?

 

[OzzieGeorge]

What happens if you do a loopback on the pri, do you see layer 2 come up, Have you checked to see if you have the right channel set up as the D channel. Are you sure you have the right protocol being supplied by the provider?

 

[belevedere]

Check out the link below for a cheat sheet on setting up a PRI. It's best if you set it up new instead of converting the T-1 programming. Also make sure that you reset the system after programming it up. That's usually required to get the clocking up. Place a loopback plug on the cabling and verify the D channel comes up as Ozzie suggested. You could do it with switch settings if you don't have a plug. See

http://www.wedophones.com

for manuals. Switch settings can be found in the installation manual or in the ISDN/PRI manual.

http://www.nectekhelp.com/docs/2000/ISDN PRI.pdf

 

[dirtcheap]

Thanks guys. I printed out the cheat sheet and will go there later today to check it out. The 2nd site doesn't have a set of printed manuals but the 1st one does so I'm going to there and borrow them. How can I check the Neax to see if the D-channel is coming up with a loopback? Is there a command dialed on the programming phone?

 

[belevedere]

Look for the LYR LED on the card. It should be solid on.

 

[dirtcheap]

I got the manuals and looked for a "LYR" light and didn't find one. At this point I realized that we're not talking about the same thing. The system I'm working on is a 20 year old IVS. I'm dealing with a 24DTA-A digital trunk card and a SC01 D-channel handler. However, your mentioning of LED's got me looking at them. I noticed that the "LC" light on the SC01 does not come on. The manual says this "Lights when communications are normally ongoing with the D channel data links connected" Once again I took the card out and plugged it into the working system. The light comes on and the PRI works fine. It doesn't come on when plugged into the system I'm working on. What other card in the system could cause this problem? CP card? Backplane? I know it's not the 24DTA because I tried that in the working system and it was OK. Do you need to know the part number of everything in the control cabinet?

 

[OzzieGeorge]

There are the new cards and old cards, the newer ones combine the SC01 and the 24DTA into one card, you can use either arrangement in that system. You have to tell the system what sense switch setting corresponds to the card, have you set the switch setting and programmed it accordingly?

 

[belevedere]

The LC LED on indicates that the "D" channel is up. Depending on how old the system is, the software and/or SC-01 card firmware may not be fully compatible with NI-2 signaling. If it is, then you need to work with your PRI provider to get the "D" channel up.
EX: T-1 card sense set to 4, SC-01 set to 5.
commands:
05:04:09 = T-1 card
05:05:05 = SC-01 card
0701>0400>D100 = first T-1 channel trunk number
0701>0401~0423>D101~D123 = the remaining trunks
Reset the system
0607>0>05
Reset the system
A0>04>0 = AT&T specs
A6>05>20 = AT&T, 21 = DMS 100/200, 28 = NI2, you need to know what CO protocol you have
A700>0>123 = D channel trunk
3000>100~122>31 = voice trunk route
3000>123>30 = D channel trunk route
3002/3003>100~122>18 = ISDN
3007>100~122>000~122 = CIC code for every voice trunk
3500>31>00 = ISDN trunk route
3504>31>2 = answer signal arrives
3509>31>03 = wink start
3518>31>0 = digit conversion allowed
3520>31>00 = wink start
3590>30 + 31 = 0 ISDN
3593>05>0 = ISDN circuit 0 to SC-01 card (ties it together)
Reset system
Knowing your software level and SC-01 firmware may help.
It's been a while for me setting this up on an older 2000, I hope I didn't overlook something. If I think of something else, I will repost.

 

[belevedere]

Some corrections.

3509>31>100~122>08 = ISDN
3512>31>2 = 3 digits from telco, 4 or default = 4 digits from telco
410>50>05 = timing
410>57>05 = timing
36>3030>0/3031>0/3130>0/3131>0 (make all trunk route to trunk route connections 0)
05>05>12 = SC-01 card
0608>0>05 = ISDN channel to card NOT 0607
3590>30 + 31>3 = ISDN, NOT 0
A900>0>123 = d channel to circuit, NOT A700, reset system required
3521>31>01 = sender pre-pause timing
3546>31>0 = 2 seconds sender release timing
NOTE some programs are for voice route only and some are for D channel route only.

It's starting to come back to me.

 

[dirtcheap]

First, I want to say thanks for all the help. I got the PRI (sort of) working finally. However, for some reason calls are getting rejected by the PBX if I use the DID conversion to send the main number to TAS (760 & 761 = 4300>D13). Calls appeared on the ANS button on the multiline sets (9000>7070,22>F4001) This was how the T1 was programmed and I thought I could just leave it that way. Instead, calls were going to the "unreachable destination" set up by Comcast because the PBX was send an "Alerting" message to them. I got it to work by changing the DID conversion to send calls to "0". "0", however, did not ring phones at the front desk. It is an extension that is connected to a ringer in the ceiling between the front desk and office. They would answer internal calls by pressing a "Directed Call Pickup" button and dialing "0". This wasn't going to work in the long run though because the GM already hated that "0" calls went to the ringer and wanted me to change it so they went to the front desk phones. I tried to change "0" to a button on the front desk sets and got internal calls to ring on that button but now external calls would get a message saying that "The number is no longer in service"!?!?!
Any ideas as to what is causing these problems with external calls? How, if even possible, can I get "0" and PRI calls into call queues that can ring to the front desk phones?

 

[belevedere]

Is 0 programmed on a line key at the front desk phones? Is CMD 1308 set to 0 for the analog port that has the ringer attached?

 

[dirtcheap]

Unfortunately, the line that provided remote access to the site is disconnected so I can't check from here right now. I just looked up 1308 in the manual and the description is a bit confusing but what I can tell you is that when I put a button on the sets with just "0" as the data, the set would ring along with the overhead and the button would flash. Dial "0" calls could be answered pushing the button but DID calls redirected to "0" would get rejected.

 

[dirtcheap]

And to further clarify things, the GM wants the overhead ringer out of the picture if possible. He just wants calls to queue up to front desk phones with the ability to put calls on hold and pick up another call and switch back to the first, etc.

 

[belevedere]

1308 allows a SLT to appear on a button on a MLT. Or, when you press the button on the MLT the LED will not go out.
Redirecting DID's should be a matter of programming 760/761.

Note: When digit conversion of the leading 2-4 digits of a DID incoming LDN is available (CM35 YY = 78, Data =
0), the leading 2-4 digits of the LDN should be assigned as the first data. (When the DID incoming LDN is one
digit, the digit conversion for only one digit is not available.

Is oyur incoming number one digit in length? If so, this will not work.

 

[dirtcheap]

The incoming digits are 4 in length, specifically, 4300 for the main number. DID numbers translated in CMD 76x to office station numbers are OK. The only thing I was able to get working was translating 4300 to 0, the overhead ringer. And only if 0 did not appear on the front desk sets. I was able to put an appearance of 0 on an office set temporarily to test it and calls didn't get rejected. Both the overhead and the office set rang and the set could answer calls.

A few CO trunks on POTS line left on the system (soon to be disconnected) go to TAS and ring on the ANS button on the sets OK. When 4300 came in on the old T1 and 4300 was translated to TAS it used to work like the CO's.

Why does the PBX reject PRI calls when 4300 goes to TAS or if 0 appears on the front desk sets but not office sets? What can be different about the front desk sets that gets PRI calls rejected?

 

[belevedere]

Verify the button assignments are the same on the front desk and office sets. No reason for it to fail if it works elsewhere. If everything is the same and a system reset has not been done, I would consider it.

 

[dirtcheap]

Last night I got a call about a new problem. Now that the hotel has reopened after being remodeled there are a lot more incoming calls. Calls that don't get answered after ringing for a while (wasn't told an exact amount of time) go to a reservation line for the old franchise! How do I stop this?

Also, internal "Dial 0" calls seem to go to the housekeeper's phone if they aren't answered in time.

Is there a way to get a printout of the customer data so that I can see everything at once? This telephone display/button interface sucks.

On an unrelated note, when one room is called the port just busies out immediately. I had someone on site swap out the single-line card for a spare and it made no difference. Any ideas?

I'm beginning to think there is something wrong with this system. Is there a processor upgrade available? Something that provides you with a better interface?

 

[belevedere]

At this point in time you need to call in a certified NEC technician.