Overhead Paging

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
There are three possible methods to integrate overhead paging to the PBX; SIP, FXS, or FXO.
 
There are three possible methods to integrate overhead paging to the PBX; SIP, FXS, or FXO.
=Overhead Paging=
+
 
==Paging Devices==
+
= Overhead Paging =
===SIP===
+
 
Using a SIP based overhead paging device is the best option as the device registers directly to the PBX as a SIP extension. This allows for the easiest integration as we do not need a gateway between the PBX and the paging device. In order to page, you will dial the SIP extension, and since it is registered as a SIP extension, you are also able to add the overhead to a paging ring group, along with the other extensions on the system.
+
== Paging Devices ==
 +
 
 +
=== SIP ===
 +
 
 +
Using a SIP based overhead paging device is the best option as the device registers directly to the PBX as a SIP extension. This allows for the easiest integration as we do not need a gateway between the PBX and the paging device. In order to page, you will dial the SIP extension, and since it is registered as a SIP extension, you are also able to add the overhead to a paging ring group, along with the other extensions on the system.
  
 
We have guides that go over the configuration of [http://www.ipitomy.com/webrelease/Valcom/ Valcom] and [http://www.ipitomy.com/webrelease/Cyberdata/ Cyberdata] SIP based paging devices.
 
We have guides that go over the configuration of [http://www.ipitomy.com/webrelease/Valcom/ Valcom] and [http://www.ipitomy.com/webrelease/Cyberdata/ Cyberdata] SIP based paging devices.
 +
  
  
Line 13: Line 18:
  
 
=== FXO ===
 
=== FXO ===
An FXO paging device requires an FXO gateway ([http://www.ipitomy.com/pbx_files/ip400/IP400-Quick_Guide.pdf IP400] or [http://www.ipitomy.com/webrelease/Grandstream/Tech%20Bulletin%202011-008%20Grandstream%20Configuration%20Guide.pdf Grandstream]) to integrate to the PBX.  You then need to create a new [http://www.ipitomy.com/webrelease/IPitomy/IP1100+/Outbound_Routing_Quick_Guide.pdf Outbound Route] and add the trunk the paging device is connected to so the user can dial and access the overhead.  Our experience has shown you want to be sure to strip digits in the trunk otherwise they may hear digits being dialed in the overhead. 
 
  
Using an FXO paging device is the least advised method for a few reasons. The main reason is how you make the call. Instead of registering as an extension that can easily be dialed, you have to create an Outbound Route to access the gateway, meaning you cannot create a Ring Group with the paging device and some extensions included. Another reason has been our dealers experience with the FXO paging devices themselves. Sometimes special programming is needed that they are not aware of (eg. requiring an outside power source to give line voltage). It seems historically, the FXO overhead paging devices have been the most problematic so it is our advise to avoid them if possible.
+
An FXO paging device requires an FXO gateway ([http://www.ipitomy.com/pbx_files/ip400/IP400-Quick_Guide.pdf IP400] or [http://www.ipitomy.com/webrelease/Grandstream/Tech%20Bulletin%202011-008%20Grandstream%20Configuration%20Guide.pdf Grandstream]) to integrate to the PBX. You then need to create a new [http://www.ipitomy.com/webrelease/IPitomy/IP1100+/Outbound_Routing_Quick_Guide.pdf Outbound Route] and add the trunk the paging device is connected to so the user can dial and access the overhead. Our experience has shown you want to be sure to strip digits in the trunk otherwise they may hear digits being dialed in the overhead.
 +
 
 +
Using an FXO paging device is the least advised method for a few reasons. The main reason is how you make the call. Instead of registering as an extension that can easily be dialed, you have to create an Outbound Route to access the gateway, meaning you cannot create a Ring Group with the paging device and some extensions included. Another reason has been our dealers experience with the FXO paging devices themselves. Sometimes special programming is needed that they are not aware of (eg. requiring an outside power source to give line voltage). It seems historically, the FXO overhead paging devices have been the most problematic so it is our advise to avoid them if possible.
  
 
== FAQ ==
 
== FAQ ==
===FXS Paging System Doesn't disconnect===
+
 
 +
=== Grandstream FXS Paging - Paging System Doesn't disconnect ===
 +
 
 +
Problem: The external paging equipment will answer and broadcast page announcement but when the user hangs up the phone the paging system doesn't disconnect.
 +
 
 +
Solution: The problem is that the Grandstream is set at default for too short a duration of loop current interruption. The paging equipment doesn't recognize the short interruption as a valid disconnect and therefore remains connected - even though the connection has been terminated between the phone and the Grandsream. The solution is to increase the loop current interruption time so that the paging equipment will detect the on-hook condition and disconnect. Grandstream sets this value at 200ms at default. We suggest changing it to 1000ms (1s) or greater.
 +
 
 +
#Navigate to the Grandstream GUI PROFILE page (usually Profile 1).
 +
#Locate the datafield "Loop Current Disconnect" and set it to YES.
 +
#Locate the datafield "Loop Current Disconnect Duration" and set it to: 1000.

Revision as of 11:06, 7 September 2012

There are three possible methods to integrate overhead paging to the PBX; SIP, FXS, or FXO.

Contents

Overhead Paging

Paging Devices

SIP

Using a SIP based overhead paging device is the best option as the device registers directly to the PBX as a SIP extension. This allows for the easiest integration as we do not need a gateway between the PBX and the paging device. In order to page, you will dial the SIP extension, and since it is registered as a SIP extension, you are also able to add the overhead to a paging ring group, along with the other extensions on the system.

We have guides that go over the configuration of Valcom and Cyberdata SIP based paging devices.


FXS

An FXS paging device requires an FXS gateway (IPr20, PAP2, Grandstream, or SPA112) to integrate as a SIP extension and is the second best option. Again, you would dial the extension to page, or you can add the extension to a ring group and page overhead along with a group of phones.

FXO

An FXO paging device requires an FXO gateway (IP400 or Grandstream) to integrate to the PBX. You then need to create a new Outbound Route and add the trunk the paging device is connected to so the user can dial and access the overhead. Our experience has shown you want to be sure to strip digits in the trunk otherwise they may hear digits being dialed in the overhead.

Using an FXO paging device is the least advised method for a few reasons. The main reason is how you make the call. Instead of registering as an extension that can easily be dialed, you have to create an Outbound Route to access the gateway, meaning you cannot create a Ring Group with the paging device and some extensions included. Another reason has been our dealers experience with the FXO paging devices themselves. Sometimes special programming is needed that they are not aware of (eg. requiring an outside power source to give line voltage). It seems historically, the FXO overhead paging devices have been the most problematic so it is our advise to avoid them if possible.

FAQ

Grandstream FXS Paging - Paging System Doesn't disconnect

Problem: The external paging equipment will answer and broadcast page announcement but when the user hangs up the phone the paging system doesn't disconnect.

Solution: The problem is that the Grandstream is set at default for too short a duration of loop current interruption. The paging equipment doesn't recognize the short interruption as a valid disconnect and therefore remains connected - even though the connection has been terminated between the phone and the Grandsream. The solution is to increase the loop current interruption time so that the paging equipment will detect the on-hook condition and disconnect. Grandstream sets this value at 200ms at default. We suggest changing it to 1000ms (1s) or greater.

  1. Navigate to the Grandstream GUI PROFILE page (usually Profile 1).
  2. Locate the datafield "Loop Current Disconnect" and set it to YES.
  3. Locate the datafield "Loop Current Disconnect Duration" and set it to: 1000.
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox