Personally I wouldn't try to use LCR - just set the POTS lines to the same outgoing line group. You may have to move your hardware around (swap PRI and 4LS cards for example) to get it to use them in the desired order. Last I checked the IPO will use lower numbered lines first (very silly I know) but that may have changed with R3.
Main route lower the time value to 5 seconds then create a short code like so
Short Code: ?N
Telephone Number: .
Line group: 1 (The PRI/T1 Line group)
Feature: Dial
In the alternate route creat short code
Short Code: ?N
Telephone Number: .
Line Group: 2 (The line group of the POT's)
Feature: Dial
If the T1 goes down you will see "Waiting for line" in the display after 5 seconds it will try the POT's line and dial out. Works like a champ. I'm sure this method is not supported by Avaya. If you are using a CO trunk to page DO NOT use this it will stop working.
If you are using a CO trunk to page the above can still be used.
Any system short code with a feeature of dail the tereanslated number is padssed to LCR, this will override the line group ID. You just have to remember to programme the code to page into the LCR.
using the LCR fall back in this way is exactly how it is intended & would be supported by Avaya
I never saw this in any doc's I assumed it wasn't supported. BTW i'm refering to my shortcodes that have ?N with the period as the telephone number.
Sweet now I can use my fail over method when people have paging. Question I have to you is, how do I build the short code into LCR? Say My short code is #1 for paging.
Short code: #1
Telephone Number: (Blank)
line Group: 1 (My page trunk)
Feature: Dial
Do I just insert this into this into the LCR form? My fear is that people making outbound calls will then somehow place outbound calls over the paging system.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.