TN464GP Issues

[SOConnor]

I am trying to use TN464GP circuit boards in 2 different situations and both are giving the same results. These are on a G3r running R1.3.

1. I configured and added a TN464GP board for a 10th PRI circuit to an existing PRI trunk group and signalling group. This board was configured the same as the other isdn-ext boards already working in the group. There are only 2 D-channels for the ten circuits. Only TN464 boards are used for this group although all are vintage F except the new one. The lights are red on the board and our service provider cannot see our equipment. Tests indicate that no incoming signal is seen either. Board, CSU and cables have all been changed. Problem moves with the TN464GP when placed in a working slot.

2. A line-side isdn-pri was configured for a new Tandberg video conferencing system. It was configured as specified by the video vendor (National ISDN, B8ZS, ESF, etc). Again we are getting only red lights on front of TN464GP and tests show no signal in. Video equipment sees no signal from PBX. Board, CSU and cable have all been replaced with no change.

There seems to be a pattern here but I cannot figure out why these are not working. Making changes to the DS1, signalling group or trunk group have no affect whatsoever on the lights or test results.

 

[RFWatts]

SOConnor

For problem #1, have you updated the firmware to the latest (FV17)?

For your second problem, I would do away with the CSU, and make sure you need/don't need a T1 Crossover. Also, does the vendor need a line-side station configuration, or a trunk-group config?

Either way, make sure your firmware in your TN464GPs are up to date.

 

[SOConnor]

All are on FV17.

They need the trunk group (individual channels). They were going to order a PRI circuit from SBC. Sixteen DID numbers are pointed to this group so that they can have up to 16 simultaneous calls.

I'll have the cable checked to see if it is T1 crossover.

 

[phoneguy55]

Some times the LEC leave the T1 on the 66 block backwards. Try flipping your pairs. 4/5 to 1/2 and 1/2 to 4/5, it may be as simple as that.

 

[RFWatts]

What happens if you take a known working card and place it in the new configuration?

Also, can you loop and and see the bearer channels come up? Your D-channel will still show down, but you should at least be able to see that you have a loop.

 

[lopes1211]

And I assure you a cross over T-1 cable (NOT THE SAME AS A CROSS OVER ETHERNET CABLE) is needed for the Tandberg setup. As stated above, depending on your area, many lecs flip xmit an recv by accident (or on purpose just to mess with us) which may require you to use a cross over there as well. You may not be able to just swap this with a working card on the existing trk grp since they are different suffixes.

-CL

 

[SOConnor]

We got the video working with the crossover cable. They cannot dial out from the video system now but dialing in works fine. I did a list trace when they tried an outbound call and got a "denial event 1367: BCC incompatibility". Anyone know what that means?

 

[phoneguy55]

Play with the route pattern. I had the same thing when trying to route video.

 

[lopes1211]

change the route pattern from "rest" to "both". Also, you need an SDS plan with your LD provider.

-CL

 

[schned99]

BCC incompatability can mean that the T1 provider does not provide video bearer on it's outbound routing or you have a problem with your route pattern. I just went through a similar situation with a customer. They where able to receive inbound video fine, but got the BCC incompatiblity when trying to initiate an outbound LD video call. The LEC we where dealing with swore up and down for 6 months that the customer was set up for outbound video. Local outbound worked fine, but LD video got the BCC incompatability error. It turns out, the LEC had two long distance PIC codes. One had video bearer, the other did not. They had my customer set up for the wrong one. When I finally got their switch side people on the phone, we found the problem and got the right PIC code on the outbound calls and all was well. Before you push back to them, make sure your route pattern for video calls has ITC set to "both" and BCIE set to "ept". You may also need to set the numbering format to "unk-unk". Also make sure you don't need to specify a service type like megacom or SDN. Good luck.

Statements expressed in this post are my own opinions and should not be considered as the opinion of my employer.

 

[SOConnor]

We finally got the video to working. It did require a crossover cable plus some changes to the BCC programming. Otherwise everything was correct.

We have not checked the cable yet for the SBC PRI but will be doing that soon.