Connecting Rad via ATA

[ct442]

I was told a long time ago that i could access the rad remotely threw the ATA. I am at the site know and have been playing with it all day.
I currently have the ata hooked up as follows
the digital side on port 416 ext# 249 and the analog side connected to an unused C.O port line# 76. i have the rad set to answer line 76, but when i call ext: 249 it rings but no modem sound. If i am doing somthing wrong please tell me.

 

[luv2ski]

the ata is set to answer "y" that line"76"

Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com

Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.

 

[Arr]

CT442,
I've had similar issue. Done it fine with IATA.. except there's no disconnect supervision and I find the mock CO line doesn't disconnect.. but that aside, I think the non answer has something to do with the intercom ring. Try alowing ext 279 to appear and ring from an outside line. My test failed with an 8/24 Modular, ATA2 and Fast Rad.
My next attempt will be with a Stick and a CO line. But that won't be for a bit yet.

Cheers
PhM

 

[VencomRob]

Why nopt just hookup the RAD to digital port and set to answer line 76. I don't understand what you need the ATA for!? Sounds like a waste of a good ATA.

 

[Arr]

Rob,
Idea here is to simulate a loop start CO line with an ATA where a CO line is unavailable. For the same cost, and I think better effectiveness, a Stick line sharing device may be used in a similar fashion.

Cheers
PhM

 

[capcoms]

I recently upgraded a MICS from 1.1 to release 5.0. I had installed a fastrad on the 1.1 system prior to the upgrade. It worked fine on line 27, but after the upgrade which also included installing a T1 in place of the loop start cards I could not access the RAD via DID target lines. I directed an available DID to an unused ATA port and connected the analog side of the ATA directly to line 27 and it works fine.

My problem probably resulted from the RAD not having the latest firmware installed and so it was not completly compatible with 5.0

By the way, you are using the correct vintage RAD with the MICS release you have right?