VSX 8000 V.35/RS-449 Settings

[bigfish]

Has any one used the Polycom VSX-8000?

[USAFVTCGUY]

I have. What's your question?

[Slimey]

heh really we need more details...

USAFVTCGUY how is the river ,still cold as always? :P

[bendamoi@filternet.nl]

What is the point here

Greetz

ben

[dnshbedi]

yeah tell me what is the problem

[USARMYVTCGUY]

Heres the facts: We just recieved a POLYCOM VSX8000. It testes fine in nonsecure, but does not work secure. It is connected to a KIV-7, then to a ADTRAN ISU512, then to my ISDN LINES/NT1 DEVICE. I have verified the pinouts for the KIV and believe them to be correct. From the VSX-8000 it is using a V.35 connector, cable splits to RS366 & RS449. According to ADTRAN the RS366 goes directly to the dialing port on the ISU512. The RS449 is connected to a special cable that goes directly to the KIV-7. Out of the KIV is another special cable that connects to the ISU512. I have spent lots of time on the phone with everyone of the vendors and am now thoughly frustrated. Should the VSX8000 see the ISDN lines on the other side of the KIV? They currently do not. Also I am having a problem linking the ISU512 to a distant end. It works fine w/ the guys at the plant, but I can't seem to get it to link with my distant end. Does anyone know someone I can shoot to in order to test? Also my distant end is using a TANDBERG, is there a compatability issue?

[Entropy3XD]

You say it works fine with the guys at the plant. Is this in secure mode as well? If you work fine with the guys at the plant in secure mode, but not at the distant end, it may be a mismatch in crypto keys, crypto settings, or possibly ISDN issues with you dialing out or their receiving calls. When you dial the far end, do you see the Adtran connect and bond? The codec will not see the ISDN lines on the other side of the KIV. How are you doing your tests in non-secure? Can you dial non-secure to the far end you are having issues with? When setting up a new codec I typically take the red and black cables off of the KIV and mate them together. I then test everything out with the far end in non-secure. Once I get all the bugs out and everything works fine I add the KIV last. This will prove that everything works (IMUX, Codec, and ISDN lines), leaving the KIV as the only possible culprit.

One point to make......You say Adtran told you to connect the 366 cable directly to the Adtran 512. This would be correct if you are in a non-secure ONLY environment. If you wish to use the equipment in a secure environment and still use on screen dialing, you will require a dial isolator. Without a dial isolator, when you go secure, you will still have a dedicated copper path from the IMUX to the codec, bypassing the crypto. This is a violation. The alternative to not using a dial isolator is to leave the 366 cable disconnected and dial from the IMUX.

[11B-33T]

:thumbup: Entropy3XD is center mass with his diagnosis ArmyVTCguy. Follow his troubleshooting steps to first establish you can call out PTP non-secure, then add the secure comms to the mix. Doubt very much the TB at the far is causing a compatability issue but don't rule it out. Email me if you need to do some testing..

[gdsharpe]

When going secure with this set-up, all dialing must be done from the ISU 512. No wiring is allowed to go around the crypto.

The Adtran ISU 512 ONLY does BONDing Mode 1 connections, it is not capable of, say, a 2x64k connection. That is to say, the ISU 512 will do 64k, 128k, etc., only in the BONDing Mode 1 mode. The difference is in the connection set-up protocol. If your far end equipment is set up for 2x64, or is not capable of BONDing Mode 1 operation, you will not be able to connect using the ISU 512. The Polycom may be able to do both types of connections, and as such will work when you are not using the crypto and the IDU 512.

Make sure your ISU 512 is set up properly with SPIDs, and LDNs, and be sure the other end is set up properly.

The sequence of steps is:
1 - Dial the far end-point and allow the Terminal Adapters to connect and establish the path.
2 - The KIV-7HSs should now start to synchronize.
3 - Once the crypto is in sync you have a secure data path. The VTCs at each end should now start to synchronize.

At what point in this sequence is your call failing?

-gary

[Outkaste]

VSX8000 will not see it As ISDN only sees the v.35 interface The IMUX sees the ISDN (outside world) 366 is dial side (and YES if it runs straight to IMUX it is not certifiable you must use a dial ISO "titan makes one". If you are using the Polycom Y cable 2457-21263-001 (which in this case I think you are) look at end lables one side RS366 other says RS530 from the HD66 which connects to port one (BOTTOM) of v.35...as you can see..rs530 is not 449 there is an adapter I hear (I think a patch bay should work also).
The Imux will ready ready across 1/2/3/4/ lines you may have on the front (look at your configurations and double check with provider) and ADTRAN 888-4adtran will help you through....

[Da Riddler]

New to this web site, but I just recently stood up a secure room myself and wonder why in the world he has a NT1 off of a ISU 512, are there ISU 512's out there that don't do the NT1 function?

[ChuckF]

Yes. The ISU comes in two flavors, 512U and 512ST. 512ST used mostly in EU countries.