I am trying to setup a 4 line analog system with rollover from the local telco. The idea of course is that all outside calls are placed to 5551212 and the system will connect them to line1, line2 and so on if lines are busy. The following is what I am trying but it doesn't seem to work. When Line1 is busy the subsequent calles are not answered instead of going to line2. Any help here would be appreciated.
Your suggestions look very good, thank you. One thing though, I can't use both dual-line and trunk command on one DN. I use the trunk command to establish a one-to-one relationship between a DN/button and a trunk line. Is there a way to keep this relationship without using the trunk command?
Maybe just using the "no call-forward busy" would be enough since I believe we can still place calls on hold, transfer and park without the dual-line, no?
Come to think of it, shouldn't the telco get the busy from the CME on that line and then ring the second trunk/port line?
You should be able to request the phone company set up your lines as a 'rotary group', which means they will give you a single number as the main pilot number, and this will hunt through all lines if the individual lines are busy. You can also call each individual number to go direct to the voice port it is connected to. The pilot number is advertised as your "Listed Directory Number" , or LDN so callers only need to know a single number to call your organisation.
Looks like the ability to use trunk and dual-line is not version dependent but platform dependent. I downloaded the latest spservices IOS for the 2800 and still could not use both commands. However by chance I tried it on a UC500 and the commands could be used simultaneously. Go figure...
Anyway, my rollover is working now thanks to your example.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.