đź“„ Vertex
Sign in

Vertex Caller ID for VoIP Manual

Version 2.1 (01/27/2020)

Overview

The Vertex unit is designed to capture Caller ID and other telephony signaling on VoIP phone calls and send this information to computers. Depending on the software running on the computer, applications such as Caller ID popup screens for delivery, dispatch, phone billing, and logging calls are available.

Critical Information

  1. The Vertex is designed to capture only standard non-encrypted SIP (Session Initiation Protocol).

    SIP transmitted via TLS (Transport Layer Security) and SRTP (Secure Real-time Transport Protocol), or other types of encoding are not supported. Refer to Appendix B - Known Incompatible VoIP Providers.
  2. There are 3 network ports on the Vertex. The 2 VoIP Bridge Ports provide a pass-through link between two network endpoints and processing circuitry connected in parallel. This approach allows passive packet "sniffing" thus eliminating any network point-of-failure. The Management Port is the only port that presents itself as an endpoint on the network.
  3. A single network connection carrying all VoIP traffic of interest must pass through the Vertex VoIP Bridge Ports to capture the incoming and outgoing telephone call signaling. Your network topography will determine where the Vertex bridge ports will connect all VoIP traffic.
  4. The unit will pass a maximum of 100BaseT speed through its VoIP bridge ports. At least one Gigabit endpoint on either side of the bridge port may need to be re-booted to auto-configure to 100BaseT. Passive packet "sniffing" is technically impossible on a Gigabit connection.
  5. The 100BaseT Vertex throughput speed will not adversely affect VoIP phones connected through VoIP bridge ports. Only computers connected to switches or phones linked through the Bridge Ports may be affected.
    1. If possible, we suggest that VoIP phones are connected on a different leg of the network than computers and the Vertex VoIP Bridge Ports link only the VoIP leg.
    2. If the link to the internet passes through the Vertex VoIP Bridge Ports, only the internet speeds above 100mbs would be affected. A Gigabit LAN speed will not be affected.

Types of VoIP

There are basically two types of VoIP service, Hosted VoIP and Managed VoIP.

Hosted VoIP is defined by the service provider performing all voice switching, routing, messages on hold, call queuing, and other functions. In most cases, the end user needs only to connect VoIP phones to their network. Any significant programming and configuration is done by the service provider. At the time of this writing, popular companies offering Hosted VoIP are Nextiva, Vonage, 8x8, and Jive.

Note that Hosted VoIP service providers can also provide multi-line VoIP to analog conversion devices. If you are not using VoIP phones and still using analog or digital phones, then our analog devices may fit your needs better than the Vertex.

Managed VoIP involves additional equipment on site that handles most of the VoIP switching, routing, and call processing. Various terms and acronyms apply to Managed VoIP including SIP trunking, Asterisk PBX, ISDN PRI, and T1 feeds. There are many types of architectures available using particular combinations of these and other items. If you have a Managed VoIP system, your IT person and/or telephone switch provider should know the details.

Installation

Basics

  1. The Vertex Management Port is the only Vertex Endpoint on the network and used to configure the device. It connects to the same subnet as the PC running the Vertex Configuration Tool. Caller ID data is also sent out this port to software applications that have integrated Ethernet connected Caller ID devices.
  2. The two “VoIP Bridge Ports" are pass-through, monitoring ports that connect two endpoints (I.E. network switches, routers, etc.). A single network connection that carries all VoIP traffic of interest must pass through the Vertex VoIP Bridge Ports.
  3. To capture Caller ID and other telephony data from VoIP phone calls, call paths must travel through the VoIP Bridge Ports on the Vertex. In the simple block diagram below, the connection from the Router to the Network switch in made through the Vertex VoIP Bridge Ports. This allows monitoring of all VoIP traffic in and out of the premise.
    When existing network architecture allows, it is recommended that Bridge Port connections be made nearest to the VoIP telephones as possible, while still in-line with all VoIP phones of interest. The following configuration shows the Vertex between the network switch and a P.O.E. switch powering the phones.

Installation Instructions

  1. Refer to Figs. 1-4 to decide which connection diagram best matches your VoIP Network architecture. Chances are, none of the diagrams will match your Network topography exactly. Therefore, connecting the Vertex in an appropriate location on the network requires a basic understanding of the device operation. Review the Critical Information and Basics sections above.
  2. Make Vertex connections when no VoIP calls are in progress and internet traffic is at a minimum. Note that the Vertex will not pass a Gigabit connection.
    1. If the Vertex is placed between 2 Gigabit network endpoints (I.E Router, Switch), reboot at least one device to allow automatic negotiation to 100BaseT.
    2. If rebooting does not establish a link between the two network endpoints, one endpoint will need to be hard set from automatic negotiation to 100BaseT. You will only need to change this speed parameter on the specific port that connects to the Vertex Bridge Port.
  4. Power-up the Vertex and wait until power light remains steady on. The unit will attempt to negotiate DHCP in an effort to automatically obtain an IP address.
  5. Check the other lights on the front panel. Amber lights on all three channels should be steady on, indicating a network connection. If any amber light is not on steady, refer to the troubleshooting section on Amber lights. The green lights on each channel should flash, indicating data packets detected.
  6. Close any software application on this computer that is meant to interface with the Vertex. For example, if you are running a Caller ID enabled POS or Taxi Dispatch application on this computer, close it now. Close any Caller ID services associated; they may bind to ports needed for setup.
  7. Download and install the Vertex Configuration Tool (VCT) at VCT.CallerID.com.
  8. Launch VCT. Upon startup, VCT must detect the Vertex hardware. If not, turn off any third-party Firewalls or virus checking programs, re-check Ethernet connections, and try again. Refer to troubleshooting: VCT detection of Vertex.
  9. Once the hardware is detected, select “Yes” to load parameters from the Vertex.
  10. VCT will prompt you to run the Setup Wizard. Run the Wizard and follow all steps carefully. When completed, exit VCT.
  11. Set the appropriate parameters within your software application to enable Caller ID pop-up screens.

Hosted VoIP Connection Diagrams (3 Figures)

Hosted VoIP is defined by the service provider performing all voice switching, routing, messages on hold, call queuing, and other functions. In most cases, the end user needs only to connect VoIP phones to their network. Any significant programming and configuration is done by the service provider. If you are not sure whether you have Hosted VoIP service simply contact your service provider.

Figure 1 - Phones and Computers on the same Switch

A typical Hosted VoIP network architecture is shown below with a Vertex unit connected. If a separate gateway router and network switch is not present, you will need to install a network switch. The original connection is removed and the Gateway Router is connected to the Network Switch through the VoIP Bridge ports on the Vertex. This allows all VoIP traffic to flow through the Vertex. The “Management Port” on the Vertex is connected to the Network Switch. Green lines below indicate new connections.

Figure 2 - VoIP Phones connected to Auxiliary Switch

For architectures employing an auxiliary network switch to connect the phones, we recommend installing the Vertex between the auxiliary switch and the main switch. The original connection is removed and the Gateway Router is connected to the Network Switch through the VoIP Bridge ports on the Vertex. Removal of the original connection allows all VoIP traffic to flow through the Vertex “VoIP Bridge Ports”. The Vertex “Management Port” can be connected to any switch on the network. Green lines indicate new connections below.

Depending on your application software, the data output will be delivered via the Management Port connection or the serial port.

Figure 3 - Separate VoIP and Data Networks

This network architecture is seen with controlled POS systems that supply a separate router enabling all their equipment to reside within its own subnet. Remove the original VoIP connection (dotted line below) and route the connection carrying all VoIP traffic through the two Vertex “VoIP Bridge Ports”.

If the POS application collects Caller ID via Ethernet, connect the Vertex “Management Port” and your PC running the Vertex Configuration Tool (VCT) to the Data Subnet Router, as shown in the diagram below. Conversely, if the POS obtains Caller ID data through a Serial Port, connect the Management Port and your PC running VCT to the VoIP network.

If DHCP is enabled, the Data Gateway MAC is obtained automatically upon Vertex re-boot. If not, it will need to be entered manually. If the Management Port is connected to the Subnet Router, use that MAC as the Data Gateway

Managed VoIP Connection Diagram

Managed VoIP involves additional equipment on site that handles most of the VoIP switching, routing, and call processing. Various terms and acronyms apply to Managed VoIP including SIP trunking, Asterisk PBX, ISDN PRI, and T1 feeds. There are many types of architectures available using particular combinations of these and other items. One sample diagram is below. If you have a Managed VoIP system, your IT person and/or telephone switch provider should know the details.

Note: Although an Asterisk PBX is considered managed VoIP, if the VoIP gateway is the same as the Data Gateway refer to the Hosted diagrams above

Figure 4 - Dedicated VoIP Gateway

Refer to this diagram when your managed VoIP service employs a SIP appliance connecting a dedicated VoIP Gateway. The SIP server/Gateway can be an Asterisk device or Telephone switch card fed with a SIP Trunk or ISDN PRI circuit.

Remove the original connection (dotted Line). Re-route the connection carrying all VoIP traffic through the two Vertex “VoIP Bridge Ports”. Connect the Management Port to the Network Switch.

Installation Checks

  • Computers are working and have internet connectivity. 
    • No - Reboot endpoints connected to VoIP Bridge Ports to auto-configure to 100BaseT. If still no connection is present, log into one endpoint and manually set speed to 100BaseT
  • VoIP phones have registered and are working properly.
    • No - Reboot endpoints connected to VoIP Bridge Ports to auto-configure to 100BaseT. If still no connection is present, log into one endpoint and manually set speed to 100BaseT.
  • Vertex has steady power light.
    • No - Make sure correct power supply is used. Reboot using power cord on back of Vertex.
  • Vertex shows all 3 amber link-lights steady on.
    • No - Refer to Amber Lights blinking or not steady on in Appendix A - Troubleshooting.