Avaya Communication Manager Administrator's Manual page 1548

Feature Reference
Group paging
•
Bridging
Bridging is disabled on this feature. A bridged appearance of a group member does not receive
any indication of a call when the page arrives. The bridged appearance cannot bridge onto the
page.
•
Call Coverage
Pages do not follow group members' coverage paths. A page group cannot be a coverage point.
•
Call Park
Group members who receive a page cannot park the call.
•
Call Pickup/Direct Call Pickup
Other extensions cannot pick up a group page.
•
Call Forwarding
Group pages cannot be forwarded.
•
Conference
Neither group members receiving a page nor the originator of the page can conference the page to
other extensions.
•
Distributed Communications System (DCS)
Page groups cannot be administered across DCS servers/switches. DCS is not supported.
•
Do Not Disturb
If a member of a page group activates Do Not Disturb, that member does not receive pages.
•
Go to Cover
The Go to Cover feature is ignored because group pages do not follow coverage.
•
Hold
The originator of a group page can put the page on hold, but group members cannot.
•
Leave Word Calling
Leave Word Calling (LWC) is disabled. A page group cannot receive messages.
•
Manual Signaling
The Manual Signaling feature cannot be assigned to a page group.
•
Send All Calls
If a member of a page group activates Send All Calls (SAC), that member does not receive pages.
•
Service Observing
Group page members and page originators cannot be observed while active on a page.
•
Transfer
Group members cannot transfer a page.
•
Trunks
Trunks cannot be added to a page group.
•
Vectoring
Paging groups cannot be explicitly added to a vector path.
NOTE:
If a vector has a collect digits step and a route-to digits step, a person who uses the vector
can enter a page group extension. Ensure that the COR of the vector restricts the vector
from calling the page group if this action is not desired.
1548 Administrator's Guide for Avaya Communication Manager
November 2003