Please enable JavaScript to view this site.

IP Office Basic Edition - Web Manager R11.1

There are a number of ways to make page calls.

To Page a Group

For a call to a group of extensions, putting a * in front of the extension number of the group being called makes the call a page call. The group type is ignored, instead, all users who are members of the group, have phones that support auto answer and are currently not on another call, hear a single beep and can then hear you. However, you cannot hear the group members.

To Page the Loudspeaker Extension

A loudspeaker paging device can be connected to an analog extension port on the system. The equipment Type of that extension is then set to Loudspeaker Paging. That device can then be accessed by any user by dialing 70 when making an internal call.

To Make a Simultaneous Page

In addition to loudspeaker paging (see above), users can also page the loudspeaker paging device and the members of Calling Group 1 at the same time by dialing *70 when making an internal call.

To Make a Direct Call to an Extension

For an internal call to an individual extension, putting * in front of the extension number of the user being called makes the call into a direct voice call. If supported by the phone being called, the call is automatically answered after the called users hears 3 beeps. If the phone called does not support auto answer, the call is turned into a normal call.

Unlike a page call, the called user can also speak without having to take any further action if their phone has a handsfree microphone. Otherwise they need to pickup the handset to be heard.

If the user called is already on a call when you attempt a direct voice call to them, you call is turned into a normal waiting call.

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

© 2020 AVAYA
Issue 05.a.–
Thursday, July 23, 2020