Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Legend Loudspeaker Paging configurations

Status
Not open for further replies.

cybertheque

Technical User
May 15, 2011
30
US
...working on an undocumented legend release 2.1 v4.0 that used
to do loudspeaker paging until the processor batteries died. I am restoring this piecemeal. In previous posts I see folks recommending two different methods of handling loudspeaker paging:

1. use the (fxo) line assigned for aux eqpt -> paging directly
on a button (e.g. 808 for the 4th line on the second 408 card)

2. assign a button as a feature to pickup the line, e.g.
*9808

What are the ramifications of these choices?

The system is in 'key' mode and had lines deleted from some
of the line buttons to accomodate features on the ATL phones
(there are no mlx phones) -- the loudspeaker paging button appears after several other feature assigned buttons so I have
been unable to use the direct line assignment (of line 808) to
hit that button. Am I missing something here? How could a line
button in key mode have been assigned to loudspeaker paging above other line buttons that had features assigned to them (unless it was the 'pickup' method described above)?

3. the amp is not a telephone paging amp -- it doesn't provide talk battery. There are rj11 patch cords connected between two ports on an 012 card into two line jacks on one 408 card -- is this possibly to somehow provide talk battery (don't see how as the ports are not the paging ports and there is no hybrid or breakout of the pair for the audio)? The paging port is just wired (badly) into an rca phono jack which connects to the amp.

Much appreciated....
 
It maybe that you don't have overhead paging at all.

The way the ATL Phones would enable "INTERCOM VOICE TO BUSY VOICE TERMINAL" was to provide the T+R of the next port connected to the BROWN WHITE of the previous port.

That is, extension 10 would use the BLUE WHITE of extension 11 connected to it's BROWN WHITE to make this happen.

The system most likely DID NOT use a LINE -808- to do the paging.

It probably just use the ALL PAGE Code.

Either way, unless you upgraded to an R3 or later, you will be faced with the same loss of programming and battery dying issue down the road.

The R3, even if the battery dies, can still have a backup on it's flash card.

I recommend upgrading to an R7, the cost is minimal, and they can be upgraded to use Merlin Messaging.



 
Following up:

The paging amp turned out to be a bogen TU-35 with talk battery -
mystery solved there, and it is working.

The loopback connections from two 012 station jacks to two 408 line jacks is totally unknown, unused, and now disconnected.

Station 10 and 11 ATL phones have their wh/brn pairs wired into
rj11 jacks which were plugged into two 012 ports -- perhaps the
voice announce to busy configuration previously described -- and
now disconnected as unwanted.

Labels on the ATL phones evidently have been freely moved around
so any logic about line assignments is unwarranted.

Thanks for the reply.
 
Previous forum posts describe a message waiting hack using a loopback patch between a t/r port and a line port -- I am moving
questions about this to a new thread
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top