I have a stock room that needs two different phones in the very long room. I would like it so that if someone calls either extension that both phone ring and the user can pick up either line from both phones.
is this possible? can someone point me in the right direction?
This is a simple shared line configuration. Configure the 1st phone with a DN, ex 1000, make sure you set it's busy trigger to a minimum 3 but I would recommend 4 for this config. Max number of calls is usually set to double of busy, so set it to 6 or 8. On the 2nd phone configure it with a DN of 1000 as well. Make sure it's in the same partition. This will enable a shared line. Complete the steps again for busy trigger and Max # of calls.
A shared line means it will ring on both phones. When one picks up the other cannot access that call but can receive other inbound calls. If the 2nd phone wants to let the 1st phone access the call he just puts the call on hold. Additionally you can enable barge (built-in barge callmanager service parameter) to let the other phone jump on the call as well.
Mainly the busy trigger is going to say how many calls are active on the line before it uses the call forward busy setting. This configuration will give you up to 3 or 4 calls active before presenting a busy or forwarding to another destination. The Max calls allows for transfers and holds out.
Alternatively you could add a rollover line. To do this just make multiple shared lines on each phone, 1000, 1001, 1002. Then use the call forward busy setting to forward to the next number. Some people like that better than the call waiting. This can also be done with the same number on each phone but you would need to use multiple css and partitions.
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.