Telephony Interface Requirements AgilQuest OnBoard® integrates with many telephone PBX and Voice over IP (VoIP) systems to provide reliable and robust telephone service switching capabilities. Requirements for integration with specific switches are detailed below. Integration with other systems may also be available upon request. For Cisco® CallManager (CCM) VoIP Network connection from the OnBoard SwitchAgent machine to the CCM Requestor extensions and workspace MAC Address (Optional: workspace extensions and requester MAC address) Login account to the CCM with administrator capabilities Extension Mobility enabled. Supported Handsets: Any Extension Mobility capable handset. For Avaya (Lucent) DEFINITY® PBX Data Module connected via digitial line to properly configured NET Con Channel or a Telnet connection from the OnBoard SwitchAgent machine to the PBX. Requester extensions and workspace ports (Optional: workspace extensions and requestor ports) Login account to PBX with administrator capabilities Supported Handsets: Any analog or digital handset (may only switch digital to digital and analog to analog). For Nortel Meridian PBX Serial connection from the OnBoard SwitchAgent machine to an available COM port on the PBX Appropriate numbers of requester holding sets (2616 telephone sets with two add-on modules each - each will support approximately 60 requesters) Extensions for all requesters Extensions and port addresses for all workspaces Account for logging into the PBX with appropriate access and permissions Supported Handsets: SL1-2008, 2616, 2317, 3902, 3903, 3904; SL100 - Any digital handset. For Siemens PBX Serial connection from the OnBoard SwitchAgent machine to an available COM port on the PBX Extensions for all requesters Extensions and port addresses for all workspaces Account for logging into the PBX with RSCA access and permissions Supported Handsets: Any digital handset Copyright 2006 AgilQuest Corporation. All rights reserved. AgilQuest OnBoard and SwitchAgent are trademarks or registered trademarks of AgilQuest Corporation. Other names used in this document may be the trademarks or registered trademarks of their respective owners.