011146 SIP Paging Server with Bell Scheduler

Part Number: 011146

MSRP: $499.00

Each CyberData device comes with a Two-Year Warranty. Extended Warranty extends your warranty for an additional two years. Already have a CyberData device and want to add a Two-Year Warranty? Please click the link below to register your device first:

http://support.cyberdata.net/register.php


The CyberData SIP Paging Server enables users, through a single SIP phone extension, to access multiple zones for paging with bell scheduling in a VoIP network and to connect to legacy analog overhead paging systems.

The SIP Paging Server can page directly to Polycom phones.

A second SIP extension can be configured as a Night Ringer, playing a user-uploadable audio file.

NEW FEATURE:
The SIP Paging Server now has a built in bell scheduler that enables, through a secure web interface, scheduled notifications to be sent to different multicast zones and legacy analog paging systems.

Perfect for schools, universities, manufacturing or any environment where scheduled audio notification is paramount.

In addition to the bells, the user can have 25 stored messages that are utilized through paging groups.

Note: https://www.cyberdata.net/pages/user-uploadable-bells has a set of sounds that can be downloaded.

The user can upload 25 unique bell files that can be used in up to 250 scheduled events.

SPECIAL NOTE:
CyberData is offering this new feature to current users of the 011146 SIP Paging Server via firmware download for units with serial number 1461xxxxx and firmware version 11.3.0 and above.

  • Up to 25 unique bell files that can be used in up to 250 scheduled events
  • Up to 25 stored messages that are utilized through paging groups
  • Can page directly to Polycom phones
  • Voice prompting and password controlled zones
  • SIP RFC 3261 compatible
  • NTP-based internal clock
  • Multicast output
  • Two SIP endpoints (one for Night Ringer)
  • DTMF control of zone selection
  • Delayed page support
  • Line-In connection for background music multicasting
  • Line-out connection to support analog amplifiers
  • User uploadable audio files
  • Web-based configuration and firmware upload
  • PoE 802.3af enabled (Power-over-Ethernet)
  • 19-inch Rack mount option
Protocol SIP RFC 3261 Compatible
Ethernet I/F 10/100 Mbps
Power Input PoE 802.3af or 48VDC
Operating Temperature -10 degrees C to 50 degrees C (14 degrees F to 122 degrees F)
Payload Types G711, A-law and u-law, G.722
Page Port Output Balanced 600 Ohm 5 VPP
RCA Input Signal Amplitudes 2.0 VPP maximum
RCA Input Impedance 10k ohm
RCA Output Signal Amplitudes 2.0 VPP maximum
RCA Output Level +2dBm nominal
RCA Output Total Harmonic Distortion 0.5% maximum
RCA Output Impedance 10k ohm
Dimensions Length: 6.11 inches [155.19 mm], Width: 4.05 inches [102.87 mm], Height: 1.15 inches [29.21 mm]
Boxed Weight 1.8 lbs.
Compliance UL 62368-1, RoHS Compliant, FCC; Part 15 Class A, IEEE 802.3 Compliant; Reference Number for UL: E129569 Vol 4 Sec 1
Warranty 2 years limited
Part Number 011146
How do I update my firmware?

Check to see if your current firmware is the latest version before attempting to update. Download the latest version firmware which includes the Update Firmware Utility. To upload the firmware from your PC, see your Operations Guide.

What IP phones do you recommend for setting up a Peer to Peer with this device?
What does this product do?

Our Paging Server is a POE enabled, single SIP-endpoint enabling user defined paging zones through a multicasting connection to CyberData VoIP speakers.

How does this product support 99 zones?

The 99 zones supported are with a Bogen-type Zone Controller, in that our product is able to recognize the two-digit DTMF tone the user enters after it receives a cal and passes this tonal information to the Zone Controller so that the specific paging zone associated with the call can receive the audio.

Are you able to traverse the NAT with your IP paging products?

Our IP paging products are programmed to traverse the NAT using Session Border Controllers (SBCs) of the VoIP hosting company or service provider. The SBCs act as an outbound proxy and manage the SIP traffic between the SIP server and the SIP endpoint behind the NAT.

I was able to register your device with our SIP server, but when I tried to enter a DTMF tone there was no function.

Make sure your SIP phone is set to 101 for the DTMF payload type (Out of Band RFC2833).

After a period of time, my device stops working or is unreachable.

This is a common problem when the re-registration time value is not set correctly. On our device, you need to make sure that the re-registration time value (in minutes) is less than that is set on the IP-PBX server.

On an Asterisk-based VoIP SIP PBX system, the CyberData SIP Device status is "Busy" or "Unreachable."

In the PBX setup page for the extension of the CyberData device, find the Qualify= value and change it to NO. If the Qualify= value requires a numeric value, then change it to 0. Note that on some Asterisk systems (such as Intuitive Voice) this value is called the Heartbeat= value. Set the Heartbeat= value to NO, and then save the settings. Also, on the product's SIP Setup page, make sure that the Register Expiration (minutes) setting is set to less than 6 minutes (5 minutes is good) because it needs to be a value less than the Asterisk default value of 6 minutes. Save the settings after changing the Register Expiration (minutes) setting.

When I dial the SIP extension, the Paging Server answers, but then appears to hang. There is no ready tone, and no paging happens when I dial the mgroup zone paging DTMF tones.

This is a bug specific to the CyberData Paging Server and occurs when videosupport is enabled on the PBX. We are working on a firmware fix. If you do not use VoIP Video Phones, then you can work around this bug by disabling videosupport. On the switchvox or asterisk system, in the SIP.CONF file [general] area, you'll find the following line: ?videosupport=yes? Either change it to no or delete it. You will probably have to restart the system for it to recognize the change. Most PBX servers have this as a selectable option.

I upgraded my 3CX PBX server to 7.1 and now my Rev B CyberData VoIP IP Speaker and My VoIP Paging Amplifier do not stay registered with the server.

There is a 3CX version 7.1 registration / timing bug. To correct this problem, complete the following steps: (1.) Log into the 3CX PBX system, and select SETTINGS -> ADVANCED -> CUSTOM PARAMETERS. (2.) Scroll down to select the NONCEEXPIRATION parameter. (3.) Change the NONCEEXPIRATION value from 1 to 2 and save the changes. (Note: There are pictures of the 3CX PBX pages and parameters at the end of the document at this link: 3CX 7.1 Issue

If I wanted to power the device by using the auxiliary power connector, what type of power supply do I need?

The power connection requires a +48v 380mA (min) power brick. The connector is 2.5mm with a positive center. Cisco's CP-PWR-CUBE-3 power brick is approved.

I am unable to connect with the unit when it is plugged into a Cisco SLM 224P switch.

The cables or switch ports that you are connecting to are set in switch or hub mode instead of endpoint stations. The MDIX setting needs to be changed to MDI since our VoIP products are end stations. From the Cisco SLM 224P User Guide:

Change to MDI: MDI/MDIX displays the Media Dependent Interface (MDI) / Media Dependent Interface with Crossover (MDIX) status on the port. Hubs and switches are deliberately wired the opposite of the way end stations are wired, so that when a hub or switch is connected to an end station, a straight through Ethernet cable can be used, and the pairs are matched up properly. When two hubs or switches are connected to each other, or two end stations are connected to each other, a crossover cable is used to ensure that the correct pairs are connected. The possible field values are: MDIX

Use for hubs and switches. MDI Use for end stations.
I have a Cisco 6513 switch. When I plug in a CyberData VoIP device, the device constantly reboots and will not register to the SIP server.

Please adjust the switch power selection to Power inline static, as opposed to Power inline dynamic. This will allow the device to continuously receive 15.4W of power.

We have registered the device on Cisco Call Manager but are unable to register the device's Nightringer using the device's MAC address. How do I configure two extensions on Call Manager for the device?

Create a second directory number and user for the Nightringer extension. You may need to fudge a digit of the MAC Address so that Call Manager allows you to associate it to the new user. Be sure this MAC address does not match any other CyberData devices on your network.

I have a Cisco Catalyst series switch. How do I set the unit so that it can use PoE (under 15.4w) instead of an external power source?

There are known PoE limitations with third party devices on the Cisco Catalyst series switches. This includes the 2500, 3500, and 6500 series switches. It's important to keep in mind that CyberData devices are considered third party devices and require switch port setting adjustments. Be sure to turn power policing off if it has been enabled on your switch. Power policing is disabled by default. Also, configure your port for no shutdown. Use the following command to configure inline power: power inline static max 15400.

How do I page to phones that can listen to Multicast?

See the CyberData Technical Support Knowledgebase article providing documents How Do I Page to Phones That Can Listen to Multicast?

I see that there is an option for alternate power supply of 48 VDC as an option instead of PoE for the Paging Gateway. Can you tell me the minimum amperage requirement for the power supply unit I should be looking for and can you recommend one?

For low power mode: 48VDC X .321 Amps = 15.408 Watts which is just a little over the 802.3AF PoE requirement. For products like the Paging Server 011146 and the Paging Gateway 010846 with the +48v power jack, we recommend using the CISCO cp-pwr-cube-3 48V supply.

Can you give me specifications for the correct alternate power supply needed if I don?t have a Switch?

The most cost-effective option would be to use our Power Injector (010867), plugging one end into the network source (non-PoE hub) and one end into the device. Alternatively, for products like the Paging Server (011146), the Paging Gateway (010846) and 4 Port Zone Controller (011171) with the +48v power jack, we recommend using the CISCO 48V supply CP-PWR-CUBE-3. These devices can be powered locally with a power adapter (Cisco part number CP-PWR-CUBE-3=) and the appropriate power cord (power requirements for the power adapter: 100-240 VAC, 50-60 Hz, 0.5 A).


Typical Installation

Typical School Installation

Serial Number begins with 1460xxxxx

Documentation
Description Date
PDF Datasheet DATE:6/1/17
PDF Quick Start Guide DATE:12/8/16
PDF Quick-Reference Placemat DATE:12/8/16
PDF Operations Guide (firmware version 7.2.0) DATE:5/27/15
PDF Operations Guide (firmware version 7.1.0) DATE:10/8/14
PDF Operations Guide (firmware version 6.3.1) DATE:11/13/13
PDF CyberData SIP Paging Server and SIP Phone Compatibility List DATE:8/2/16
PDF Configuring VTech ErisTerminal SIP Deskset Phones to Listen to Your CyberData Paging Server DATE:8/2/16
PDF Configuring an Aastra Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a snom Phone to Listen to your CyberData V3 Paging Server DATE:9/3/13
PDF Configuring a Cisco SPA5XX Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a Yealink T2X Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF CyberData V3 Paging Server and SIP Phone Compatibility List DATE:6/10/15
PDF Configuring a Polycom Phone to Listen to Your CyberData V3 Paging Server DATE:6/11/15
PDF Polycom Multicast Diagram DATE:3/17/15
Firmware, Drivers & Utilities
ZIP Firmware 7.2.0, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_sig" must be used to downgrade from versions greater than v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:3/13/15
ZIP Firmware 7.1.0, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_sig" must be used to downgrade from versions greater than v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:11/13/13
ZIP Firmware 7.0.0 with signature, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_sig" must be used to downgrade from versions greater than v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:8/27/13
ZIP Firmware 7.0.0 with no signature,autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_nosig" must be used to upgrade from previous versions to v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:8/27/13
ZIP Firmware 6.3.1 with signature, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "631-uImage-pserver_sig" must be used to downgrade from v7.0.0 only to v6.3.1. DATE:8/27/13
ZIP Firmware 6.3.1 , autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:11/20/12
ZIP Firmware 6.2.0 , autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:11/16/12
ZIP Firmware 6.0.7 , autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:9/8/11
ZIP The Discovery Utility scans the network and reports back any found VoIP devices that are attached to the physical network.

Serial Number begins with 1461xxxxx

Bell Scheduler
Description Date
FIRST: Register your device -
User Uploadable Bells -
Documentation
Description Date
PDF Datasheet DATE:5/18/18
PDF Quick Start Guide DATE:3/7/17
PDF Quick-Reference Placemat DATE:2/15/18
PDF Operations Guide (firmware version 12.0.0) DATE:5/18/18
PDF Operations Guide (firmware version 11.5.4) DATE:4/18/16
PDF Operations Guide (firmware version 11.5.2) DATE:2/9/16
PDF Operations Guide (firmware version 11.5.0) DATE:12/8/15
PDF Operations Guide (firmware version 11.3.0) DATE:8/5/15
PDF CyberData SIP Paging Server and SIP Phone Compatibility List DATE:8/2/16
PDF Configuring VTech ErisTerminal SIP Deskset Phones to Listen to Your CyberData Paging Server DATE:8/2/16
PDF Configuring an Aastra Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a snom Phone to Listen to your CyberData V3 Paging Server DATE:9/3/13
PDF Configuring a Cisco SPA5XX Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a Yealink T2X Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a Polycom Phone to Listen to Your CyberData V3 Paging Server DATE:6/11/15
PDF Polycom Multicast Diagram DATE:3/17/15
Firmware, Drivers & Utilities
ZIP Firmware 12.0.3, autoprovisioning template, and release notes. Only works with devices with serial number 1461xxxxx that started shipping in July 2015. New Bell Scheduler and pre-recorded messaging. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:8/2/17
ZIP Firmware 12.0.1, autoprovisioning template, and release notes. Only works with devices with serial number 1461xxxxx that started shipping in July 2015. New Bell Scheduler and pre-recorded messaging. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:6/1/17
ZIP Firmware 12.0.0, autoprovisioning template, and release notes. Only works with devices with serial number 1461xxxxx that started shipping in July 2015. New Bell Scheduler and pre-recorded messaging. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:3/8/17
ZIP Firmware 11.5.4, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:4/18/16
ZIP Firmware 11.5.2, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:1/11/16
ZIP Firmware 11.5.0, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:12/7/15
ZIP The Discovery Utility scans the network and reports back any found VoIP devices that are attached to the physical network.

Description

The CyberData SIP Paging Server enables users, through a single SIP phone extension, to access multiple zones for paging with bell scheduling in a VoIP network and to connect to legacy analog overhead paging systems.

The SIP Paging Server can page directly to Polycom phones.

A second SIP extension can be configured as a Night Ringer, playing a user-uploadable audio file.

NEW FEATURE:
The SIP Paging Server now has a built in bell scheduler that enables, through a secure web interface, scheduled notifications to be sent to different multicast zones and legacy analog paging systems.

Perfect for schools, universities, manufacturing or any environment where scheduled audio notification is paramount.

In addition to the bells, the user can have 25 stored messages that are utilized through paging groups.

Note: https://www.cyberdata.net/pages/user-uploadable-bells has a set of sounds that can be downloaded.

The user can upload 25 unique bell files that can be used in up to 250 scheduled events.

SPECIAL NOTE:
CyberData is offering this new feature to current users of the 011146 SIP Paging Server via firmware download for units with serial number 1461xxxxx and firmware version 11.3.0 and above.

Features

  • Up to 25 unique bell files that can be used in up to 250 scheduled events
  • Up to 25 stored messages that are utilized through paging groups
  • Can page directly to Polycom phones
  • Voice prompting and password controlled zones
  • SIP RFC 3261 compatible
  • NTP-based internal clock
  • Multicast output
  • Two SIP endpoints (one for Night Ringer)
  • DTMF control of zone selection
  • Delayed page support
  • Line-In connection for background music multicasting
  • Line-out connection to support analog amplifiers
  • User uploadable audio files
  • Web-based configuration and firmware upload
  • PoE 802.3af enabled (Power-over-Ethernet)
  • 19-inch Rack mount option

Specs

Protocol SIP RFC 3261 Compatible
Ethernet I/F 10/100 Mbps
Power Input PoE 802.3af or 48VDC
Operating Temperature -10 degrees C to 50 degrees C (14 degrees F to 122 degrees F)
Payload Types G711, A-law and u-law, G.722
Page Port Output Balanced 600 Ohm 5 VPP
RCA Input Signal Amplitudes 2.0 VPP maximum
RCA Input Impedance 10k ohm
RCA Output Signal Amplitudes 2.0 VPP maximum
RCA Output Level +2dBm nominal
RCA Output Total Harmonic Distortion 0.5% maximum
RCA Output Impedance 10k ohm
Dimensions Length: 6.11 inches [155.19 mm], Width: 4.05 inches [102.87 mm], Height: 1.15 inches [29.21 mm]
Boxed Weight 1.8 lbs.
Compliance UL 62368-1, RoHS Compliant, FCC; Part 15 Class A, IEEE 802.3 Compliant; Reference Number for UL: E129569 Vol 4 Sec 1
Warranty 2 years limited
Part Number 011146

FAQs

How do I update my firmware?

Check to see if your current firmware is the latest version before attempting to update. Download the latest version firmware which includes the Update Firmware Utility. To upload the firmware from your PC, see your Operations Guide.

What IP phones do you recommend for setting up a Peer to Peer with this device?
What does this product do?

Our Paging Server is a POE enabled, single SIP-endpoint enabling user defined paging zones through a multicasting connection to CyberData VoIP speakers.

How does this product support 99 zones?

The 99 zones supported are with a Bogen-type Zone Controller, in that our product is able to recognize the two-digit DTMF tone the user enters after it receives a cal and passes this tonal information to the Zone Controller so that the specific paging zone associated with the call can receive the audio.

Are you able to traverse the NAT with your IP paging products?

Our IP paging products are programmed to traverse the NAT using Session Border Controllers (SBCs) of the VoIP hosting company or service provider. The SBCs act as an outbound proxy and manage the SIP traffic between the SIP server and the SIP endpoint behind the NAT.

I was able to register your device with our SIP server, but when I tried to enter a DTMF tone there was no function.

Make sure your SIP phone is set to 101 for the DTMF payload type (Out of Band RFC2833).

After a period of time, my device stops working or is unreachable.

This is a common problem when the re-registration time value is not set correctly. On our device, you need to make sure that the re-registration time value (in minutes) is less than that is set on the IP-PBX server.

On an Asterisk-based VoIP SIP PBX system, the CyberData SIP Device status is "Busy" or "Unreachable."

In the PBX setup page for the extension of the CyberData device, find the Qualify= value and change it to NO. If the Qualify= value requires a numeric value, then change it to 0. Note that on some Asterisk systems (such as Intuitive Voice) this value is called the Heartbeat= value. Set the Heartbeat= value to NO, and then save the settings. Also, on the product's SIP Setup page, make sure that the Register Expiration (minutes) setting is set to less than 6 minutes (5 minutes is good) because it needs to be a value less than the Asterisk default value of 6 minutes. Save the settings after changing the Register Expiration (minutes) setting.

When I dial the SIP extension, the Paging Server answers, but then appears to hang. There is no ready tone, and no paging happens when I dial the mgroup zone paging DTMF tones.

This is a bug specific to the CyberData Paging Server and occurs when videosupport is enabled on the PBX. We are working on a firmware fix. If you do not use VoIP Video Phones, then you can work around this bug by disabling videosupport. On the switchvox or asterisk system, in the SIP.CONF file [general] area, you'll find the following line: ?videosupport=yes? Either change it to no or delete it. You will probably have to restart the system for it to recognize the change. Most PBX servers have this as a selectable option.

I upgraded my 3CX PBX server to 7.1 and now my Rev B CyberData VoIP IP Speaker and My VoIP Paging Amplifier do not stay registered with the server.

There is a 3CX version 7.1 registration / timing bug. To correct this problem, complete the following steps: (1.) Log into the 3CX PBX system, and select SETTINGS -> ADVANCED -> CUSTOM PARAMETERS. (2.) Scroll down to select the NONCEEXPIRATION parameter. (3.) Change the NONCEEXPIRATION value from 1 to 2 and save the changes. (Note: There are pictures of the 3CX PBX pages and parameters at the end of the document at this link: 3CX 7.1 Issue

If I wanted to power the device by using the auxiliary power connector, what type of power supply do I need?

The power connection requires a +48v 380mA (min) power brick. The connector is 2.5mm with a positive center. Cisco's CP-PWR-CUBE-3 power brick is approved.

I am unable to connect with the unit when it is plugged into a Cisco SLM 224P switch.

The cables or switch ports that you are connecting to are set in switch or hub mode instead of endpoint stations. The MDIX setting needs to be changed to MDI since our VoIP products are end stations. From the Cisco SLM 224P User Guide:

Change to MDI: MDI/MDIX displays the Media Dependent Interface (MDI) / Media Dependent Interface with Crossover (MDIX) status on the port. Hubs and switches are deliberately wired the opposite of the way end stations are wired, so that when a hub or switch is connected to an end station, a straight through Ethernet cable can be used, and the pairs are matched up properly. When two hubs or switches are connected to each other, or two end stations are connected to each other, a crossover cable is used to ensure that the correct pairs are connected. The possible field values are: MDIX

Use for hubs and switches. MDI Use for end stations.
I have a Cisco 6513 switch. When I plug in a CyberData VoIP device, the device constantly reboots and will not register to the SIP server.

Please adjust the switch power selection to Power inline static, as opposed to Power inline dynamic. This will allow the device to continuously receive 15.4W of power.

We have registered the device on Cisco Call Manager but are unable to register the device's Nightringer using the device's MAC address. How do I configure two extensions on Call Manager for the device?

Create a second directory number and user for the Nightringer extension. You may need to fudge a digit of the MAC Address so that Call Manager allows you to associate it to the new user. Be sure this MAC address does not match any other CyberData devices on your network.

I have a Cisco Catalyst series switch. How do I set the unit so that it can use PoE (under 15.4w) instead of an external power source?

There are known PoE limitations with third party devices on the Cisco Catalyst series switches. This includes the 2500, 3500, and 6500 series switches. It's important to keep in mind that CyberData devices are considered third party devices and require switch port setting adjustments. Be sure to turn power policing off if it has been enabled on your switch. Power policing is disabled by default. Also, configure your port for no shutdown. Use the following command to configure inline power: power inline static max 15400.

How do I page to phones that can listen to Multicast?

See the CyberData Technical Support Knowledgebase article providing documents How Do I Page to Phones That Can Listen to Multicast?

I see that there is an option for alternate power supply of 48 VDC as an option instead of PoE for the Paging Gateway. Can you tell me the minimum amperage requirement for the power supply unit I should be looking for and can you recommend one?

For low power mode: 48VDC X .321 Amps = 15.408 Watts which is just a little over the 802.3AF PoE requirement. For products like the Paging Server 011146 and the Paging Gateway 010846 with the +48v power jack, we recommend using the CISCO cp-pwr-cube-3 48V supply.

Can you give me specifications for the correct alternate power supply needed if I don?t have a Switch?

The most cost-effective option would be to use our Power Injector (010867), plugging one end into the network source (non-PoE hub) and one end into the device. Alternatively, for products like the Paging Server (011146), the Paging Gateway (010846) and 4 Port Zone Controller (011171) with the +48v power jack, we recommend using the CISCO 48V supply CP-PWR-CUBE-3. These devices can be powered locally with a power adapter (Cisco part number CP-PWR-CUBE-3=) and the appropriate power cord (power requirements for the power adapter: 100-240 VAC, 50-60 Hz, 0.5 A).

Installation


Typical Installation

Typical School Installation

Downloads

Serial Number begins with 1460xxxxx

Documentation
Description Date
PDF Datasheet DATE:6/1/17
PDF Quick Start Guide DATE:12/8/16
PDF Quick-Reference Placemat DATE:12/8/16
PDF Operations Guide (firmware version 7.2.0) DATE:5/27/15
PDF Operations Guide (firmware version 7.1.0) DATE:10/8/14
PDF Operations Guide (firmware version 6.3.1) DATE:11/13/13
PDF CyberData SIP Paging Server and SIP Phone Compatibility List DATE:8/2/16
PDF Configuring VTech ErisTerminal SIP Deskset Phones to Listen to Your CyberData Paging Server DATE:8/2/16
PDF Configuring an Aastra Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a snom Phone to Listen to your CyberData V3 Paging Server DATE:9/3/13
PDF Configuring a Cisco SPA5XX Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a Yealink T2X Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF CyberData V3 Paging Server and SIP Phone Compatibility List DATE:6/10/15
PDF Configuring a Polycom Phone to Listen to Your CyberData V3 Paging Server DATE:6/11/15
PDF Polycom Multicast Diagram DATE:3/17/15
Firmware, Drivers & Utilities
ZIP Firmware 7.2.0, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_sig" must be used to downgrade from versions greater than v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:3/13/15
ZIP Firmware 7.1.0, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_sig" must be used to downgrade from versions greater than v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:11/13/13
ZIP Firmware 7.0.0 with signature, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_sig" must be used to downgrade from versions greater than v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:8/27/13
ZIP Firmware 7.0.0 with no signature,autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "700-uImage-pserver_nosig" must be used to upgrade from previous versions to v7.0.0. Note: Users will not be able to upgrade directly from versions older than v7.0.0 to versions greater than v7.0.0. Users will have to upgrade to v7.0.0 then move on from there. DATE:8/27/13
ZIP Firmware 6.3.1 with signature, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. Note: "631-uImage-pserver_sig" must be used to downgrade from v7.0.0 only to v6.3.1. DATE:8/27/13
ZIP Firmware 6.3.1 , autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:11/20/12
ZIP Firmware 6.2.0 , autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:11/16/12
ZIP Firmware 6.0.7 , autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:9/8/11
ZIP The Discovery Utility scans the network and reports back any found VoIP devices that are attached to the physical network.

Serial Number begins with 1461xxxxx

Bell Scheduler
Description Date
FIRST: Register your device -
User Uploadable Bells -
Documentation
Description Date
PDF Datasheet DATE:5/18/18
PDF Quick Start Guide DATE:3/7/17
PDF Quick-Reference Placemat DATE:2/15/18
PDF Operations Guide (firmware version 12.0.0) DATE:5/18/18
PDF Operations Guide (firmware version 11.5.4) DATE:4/18/16
PDF Operations Guide (firmware version 11.5.2) DATE:2/9/16
PDF Operations Guide (firmware version 11.5.0) DATE:12/8/15
PDF Operations Guide (firmware version 11.3.0) DATE:8/5/15
PDF CyberData SIP Paging Server and SIP Phone Compatibility List DATE:8/2/16
PDF Configuring VTech ErisTerminal SIP Deskset Phones to Listen to Your CyberData Paging Server DATE:8/2/16
PDF Configuring an Aastra Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a snom Phone to Listen to your CyberData V3 Paging Server DATE:9/3/13
PDF Configuring a Cisco SPA5XX Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a Yealink T2X Series Phone to Listen to your CyberData V3 Paging Server DATE:4/3/13
PDF Configuring a Polycom Phone to Listen to Your CyberData V3 Paging Server DATE:6/11/15
PDF Polycom Multicast Diagram DATE:3/17/15
Firmware, Drivers & Utilities
ZIP Firmware 12.0.3, autoprovisioning template, and release notes. Only works with devices with serial number 1461xxxxx that started shipping in July 2015. New Bell Scheduler and pre-recorded messaging. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:8/2/17
ZIP Firmware 12.0.1, autoprovisioning template, and release notes. Only works with devices with serial number 1461xxxxx that started shipping in July 2015. New Bell Scheduler and pre-recorded messaging. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:6/1/17
ZIP Firmware 12.0.0, autoprovisioning template, and release notes. Only works with devices with serial number 1461xxxxx that started shipping in July 2015. New Bell Scheduler and pre-recorded messaging. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:3/8/17
ZIP Firmware 11.5.4, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:4/18/16
ZIP Firmware 11.5.2, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:1/11/16
ZIP Firmware 11.5.0, autoprovisioning template, and release notes. Please note that a firmware upgrade could change your configuration. Therefore, please be sure to back up your configuration before upgrading your firmware. DATE:12/7/15
ZIP The Discovery Utility scans the network and reports back any found VoIP devices that are attached to the physical network.