need help setting up CCIS between ips2000 and SV8500

[phadobas]

I have been trying to make this work for the last 2 days.
The 2 phone systems are in the same office, so it's very easy for me to experiment. I got as far as getting green lights on both ends, and on the 8500, the LYR light is also green indicating the data channel is up.

The thing I can't figure out is that the first 22 voice channels show "busy" with DCON on the 8500, and I can't un-busy them. The ips "bl" red light is blinking at 60/min rate indicating that some channels are in use (if I remember well).

The framing between the 2 is SF (not ESF) and D4. I checked both systems and they are licensed for CCIS. Yet, I keep getting fast-busy when I try to dial across the link. Can the 8500 work with the older PN-24CCTA crads that I got from an ICS?

I did the programming following the CCIS manual of both systems, and double checked each steps at least 2 times. I can't go beyond this point.

Any ideas?

 

[3racefan3]

If your programming is correct you may need a chip kit for the cards. When we do upgrades new chips are usually involved.

 

[phadobas]

Ok. that's one thing to check... I'll give a call to my vendor.

 

[phadobas]

I also have a 2400ics. So I took the ccta card from the 8500 and stuck it in the 2400. Programmed it up nicely and got the exact same problem:
The 2400 show all trunks busy (but not busied-out).
Link-lights are green and the 2400 even has the LYR light on.
The IPS has the link light green but the BL light is blinking red. And any attempts to make calls from either side results in fast busy.
I think my problem is on the 2000-side. Before I started I wiped all programming from it. The cards installed in there are as follows:
L/T0:
L/T1: IPPAD32
L/T2: 8dlc
L/T3: 8dlc
L/T4: 4lcd
L/T5: 4lcd
L/T6: 4lcd
L/T7: 4lcd
L/T8: 4lcd
L/T9:
L/T10: 24ccta
L/T11:
MP12/FP12: PN-CP24

I use the 2000 as the slave (user side) and 8500 or 2400 as the master.
Any more ideas?

 

[phadobas]

OK. I've created the CCIS link between the 2400ICS and the 2000IPS. But there is one thing to still overcome: while I can call from the IPS to the ICS, and I see the extension and name-display, I can't call from the ICS to IPS.

I always get fast-busy. When I watch it with dconx on the 2400, I see that when I finish dialing the extension number, it grabs a channel on the CCIS link, but it appears that the 2000 rejects the call.

I'm fairly new to the (old) 2000 series, and I'm not sure what else to look for. Before I stared this, I completely wiped the 2000, so there might be some setting, feature, restriction, or something that blocks incoming calls, or restricts the station from getting incoming calls, etc.

I don't suppose I need to get into a whole DID programming and digit-translation, since this CCIS link is a TIE trunk.

Any suggestions?

 

[phadobas]

Oh and one other thing. While the CCT card in the 2400ICS always show all channels idle when they are idle, the CCT card in the IPS always has its BL light blinking at 1blink/sec speed. So it always thinks that one channel is in use...

 

[belevedere]

The one channel always in use is the "D" channel. A slow flash rate is normal. A fast flash rate is 2-9 channels in use and solid is more than 10- channels in use.

 

[phadobas]

I see. Thank you.

Well I still can't call into the ips. I literally went through the entire command manual, looking for options to restrict incoming calls, etc. I went through the CCIS manual's "Basic data programming" section about 3 times. Nothing.
I can't seem to figure this out. My predecessor, who is not here any more, created a CCIS link to another ips from this ics, which works just fine. I compared all programming in regards to the basic data assignment. Everything checks out.

I don't know any more. Again, it's and IPS that was wiped, and all I did was created 2 stations with Matworx and then programmed the CCIS with the help of the CCIS manual. Of course I also set the time, and assigned an IP address to the CP24 so I can talk to it over IP.

Any other ideas?

 

[belevedere]

The ICS requires many commands to set up CCIS. But since you can dial from the IPS you can look at the following in the ICS:
ADPC = destination point code (of the IPS)
LCR settings, AFRS, AOPR, AMND, ARRC, ARSC.
In ARSC, allow all 1's for the CCIS route
In ARRC, allow incoming to outgoing route connections including the LCR route.
In AFRS, set the first digit of a station in the IPS to an OPR
In ASPA, set that same digit to the AFRS table being used.
In AOPR, first choice set the CCIS route with no deletion or additions
In AMND, set it up for the exact number of digits as the IPS station numbers. (3, or 4, etc)

 

[phadobas]

Thanks belevedere. I think the ICS end is OK, When I try to call from the ICS, dconx show that it DOES grab a trunk form the CCIS route connecting to the IPS, but then disconnects immediately and gives fast busy to the caller on the ICS end.

But still, I'll review those commands you suggested to make sure I didn't miss anything.

 

[belevedere]

Check your CIC codes and make sure that they are the same on both sides. EX: if the ICS starts with 24 then the IPS should be 24 also.Especially since you have two CCIS links. The same codes on two spans or mis matched codes can cause this problem

 

[phadobas]

It's still not working. I checked the already existing CIC numbers on the 2400ICS.

It already has 2 working CCIS links. One going to another IPS2000, and the CIC-s go from 1-24. Another CCIS link goes to an SV8500 (70 channels), and the CIC-s go from 1-70.

I programmed my link with CICs 1-24 and the same on the IPS2000 side. Should I not use the same CIC-s that are already in use on another CCIS link?

Or anything else to check?

Thanks

 

[phadobas]

WORKS!!! Unbeleivable!!!

I've been on it for the last 2 weeks! And it was AOPR. One of the parameters - PNL - was set to 1 by accident probably on day one, and so some digits were being added all the time.

It's now working. Thanks very much.