Administrative office calls
Use business calling, transfer and forwarding for daily internal and external communication.
Connect campus calls and announcements.
Integrate campus offices, classrooms, retained phones, and public address zones into a coordinated communication plan so each area can use the call and announcement paths it needs.
The campus challenge
Integrate phones, offices and public address.
Administrative teams, classrooms and public spaces may rely on different types of endpoints and communication methods.
A campus voice design combines retained analog phones, SIP endpoints, business calls and public address functions under a centrally managed UCP architecture.
Existing classroom phones
Retain validated analog endpoints using the FXS gateway capacity.
Campus announcements
Broadcast public address to defined endpoint groups for routine or urgent information.
Multiple buildings or campuses
Use a distributed network and SIP interconnection for shared management.
Connect phones and public address through a single managed call core
Administrative offices, classrooms, service areas and public address groups can share a communication plan while retaining the endpoint role required for each campus area.
Map communication tasks before products and endpoints.
The project starts with zones, users, existing phones, public address groups, trunks and continuity requirements.
Map campus zones
List offices, classrooms, public spaces and additional sites.
Classify endpoints
Record analog phones, SIP phones and public address endpoints.
Define calling and public address rules
Set dialing, permissions, transfer and group communication.
Adapt the architecture
Select UCP, gateway and continuity roles based on the campus map.
Combine the core, analog access and trunk paths.
The final design assigns each OpenVox product family a defined campus responsibility.
Central call control for retained phones.
Based on an OpenVox education deployment and UCP capability documentation.
Education deployment
An OpenVox education use case uses UCP, PSTN access, wireless backup and IAG gateways.
Existing phones retained
IAG gateways connected the client's existing analog phones.
Centralized call management
The deployment introduced shared management of internal and external calls.
UCP communication functions
UCP documentation includes public address, hotline and priority calling capabilities.
Build a voice plan for each campus area.
Share buildings, users, existing phones, public address groups, trunks and continuity requirements. OpenVox can help define UCP, gateway and SIP roles.
Related products
OpenVox iAG802 Analog VoIP Gateway
Supports 8 FXS ports; Supports 2 Gigabit Ethernet ports; Uses the standard SIP protocol;
ACU (Audio Communication Unit)
Audio interface cards available for UCP1600/2120/4131 series chassis; the ACU module provides 2 pairs of audio ports.
Let’s discuss your project
Describe your requirements. Our team can help you select and plan your OpenVox solution.