Pin outs for an ADTRAN 512 to KIV

[gbroo]

Good Day,
Does any posess the pinout for ADTRAN 512 to KIV7?

Thanks

[pzielie]

Yes, Send me your email and I will send you the document. What kind of codec are you using?

[BlackGDI]

Hi Pzielie, I will appreciate if you could forward me the document too. Thanks

[jwallace]

Just a friendly reminder!

Kiv-7 drawings or other proprietary information should only be directed to Safenet Mykotronx. You may contact our technical support team at kiv7support@mykotronx.com or call our hotline at 1-800-KIVSEVEn option 1 then option 2

[mazzarak]

OK jwallace

I think you've made your point ;)

[TomParsons]

I could use this pinout as well. My organization is also setting up a secure VTC node (for connection to DISN DVS) using the Adtran 512 mux, KIV-7HS, and Tandberg 6000 codec. And not surprisingly, we are having trouble getting things up and running. We are dialing at the Adtran, rather than using a dial isolator and dialing from the codec. We have tried making a call (to the DVS loopback number) bypassing the KIV-7 by disconnecting the KIV cables and mating them together, without success. This is making us suspicious of the cabling- so I could really use this pinout information.

I would also appreciate any lessons learned on getting this setup to work end-to-end. For example, how should we configure the Tandberg? 449/V.35, or X.21? Leased-line, or manual? Any hints from successful DVS users would be greatly appreciated. Thanks in advance!

Tom P.

[11B-33T]

Tom P, sent you a PM with info you can use...

[TomParsons]

11B-33T-
Thanks!

Tom P.

[jbyrd]

I could also use some help. I have a Tandberg 6000 going directly to KIV-7, and then to the Adtran ISU 512. Calls work fine when the KIV-7 is taken out of the loop, but something hangs up when the KIV is in-line. Trying to eliminate cables before KIV. Thanks in advance for any help.

[11B-33T]

I could also use some help. I have a Tandberg 6000 going directly to KIV-7, and then to the Adtran ISU 512. Calls work fine when the KIV-7 is taken out of the loop, but something hangs up when the KIV is in-line. Trying to eliminate cables before KIV. Thanks in advance for any help.

1. What kind of TB 6000 are you using?
2. Are you using 530 or 449 cables?

[jbyrd]

6000 MXP with NET to 530.

[11B-33T]

Do you dial with the IMUX or the codec? Dial-isolator in the string?

[jbyrd]

Currently no dial-isolator, straight dialing from the IMUX.

[11B-33T]

What are you using as your call control (under External Network settings, i.e. manual, data triggered, or leased line) on your Tandberg?

[jbyrd]

-External Network
- Data Triggered

[11B-33T]

Data Triggered works differently on different software versions of the MXP. You may need to press the connect button to assert the DTR lead which the KIV-7 needs. If using an KIV-7HSB, highlight everything in the Setup A, I/F CTRL. This will force all leads. You don't need the lead pulsing since you are dialing and hanging-up from the Adtran. Set your DTR option in your Adtran to Ignore DTR.

[jbyrd]

Let me give the settings a try and I'll post whether or not I was successful. Thanks for the assistance.

[RMMOORE]

I am trying to certify a new system install and am running into the issue specified in this thread. I have a Polycom VSX-8000 (has the newest firmware on it) endpoint, a KIV-7HS, a dial isolator, and an ADTRAN 512 S/T (also with the newest firmware) with a quad NT-1 device. Without the KIV-7 and KIV cables, the system works great.

When I plug the KIV-7 red and black side cables back to back to test the system with the KIV cables but without the KIV-7, the Polycom constantly attempts to answer an incoming call that does not exist. I gather that this is being caused by a control lead being looped back by the KIV cables.

Are there DTE options (DTR/DCD/RTS/etc) that I can configure on the Polycom or ADTRAN to counter this, or do I need to build some KIV cables myself?

[11B-33T]

1st let's check out your Adtran settings. Under the DTE options, try setting CD Options to #2 normal and DSR Options to #2 Off Idle + Test.

[RMMOORE]

I have CD options set to normal and DSR set to Off Idle + Test. I have also tried all the DTR settings. Some allow normal operation while others cause the ISU to stay connected after I end the call from the codec.

Are there mandatory I/F control options on the KIV that can stop the codec from trying to answer a ghost call?

[11B-33T]

RMMOORE, PM inbound to you so check your maibox.

[jbyrd]

HELP....

I have been working on getting our Tandberg 6000 MXP to work in a secure call with no success. Tandberg has not been able to provide any answers to this dilemma and I am at wits end. The 6000 MXP works in an unsecure call with no issues. I can even do a secure loopback. But when I try to call another site the imux will bond, the kiv will sync, the codec will display 'negotiating please wait' and then we get 'call disconnected'; both the imux and the kiv will stay connected. Any help will be greatly appreciated.

I forgot to mention that the other site we are calling is within our facility with a matching key & settings. Just wanted to eliminate the obvious of non-matching key/setting.

[11B-33T]

Sounds like your IMUX is set to 'ignore DTR' so the call stays up until you end it at the IMUX. The call not negotiating is usually keymat. Just check that each KIV is actually using the desired option setting the TEK is loaded into e.g. 1 or 2 by scrolling down while the KIV is online....

[MichaelG]

jwallace, we wrote you last week with some concerns. whats the turn around time on your reply.

thanks bud
M

[THOMASMILLER28]

Can someone send me the pinouts for 449 from Codec to Kiv? THOMASMILLER28@YAHOO.COM thanks.

[THOMASMILLER28]

What is the normal way to dial commercial to DSN numbers?

[11B-33T]

What is the normal way to dial commercial to DSN numbers?

I'm assuming your site has DSN capabilities so it depends on how your servicing switch is set to access/route data grade calls to a DSN trunk like the following example:

94-50X-555-1234
8-50X-555-1234

The 'X' is whatever digit you will require to access the geographical DSN area you are attempting to call...