Creating WireShark file for

Follow these steps:

  • Step One: Download and install the Vertex Configuration Tool. Run and connect with the unit.
  • Step Two: Select the 'Advanced Tab' and enter the password: callerid .
  • Step Three: When all phones are idle, Click the 'Start' button.
  • Step Four: While the capture is in progress, make an Inbound call, answer the phone for a few seconds, and hang up.
  • Step Five: Click 'Stop and Save'. Rename the file adding your Company name to the serial number. Select "OK"
  • Step Six: Click 'Send to', select the file just created and click "Open".

Back to Top

Upgrading firmware

If Vertex is working properly do NOT upgrade. If instructed by visit Firmware Update Guide

Back to Top

Checking if CallerID is being reported

If you ran the Setup Wizard you should have seen the CallerID information during the Test Calls section. If you need to double check that the Vertex is still sending out CallerID data, run Vertex Configuration Tool and select 'Monitor/Call Records'. This will bring up a new screen which will show calls as they come in. Make an inbound and a outbound call to verify the Vertex is working properly.

Back to Top

"Channels Exceeded" message showing on CallerID

If you see 'Channels Exceeded' as your Caller ID name, you do not have enough voice channels available on your Vertex to support the number of calls being processed at that moment. To eliminate this error, contact and purchase more voice channels. You will be given a code to instantly allow your unit to process more simultaneous calls.

Back to Top

LED Boot up sequence for Version 92 and above

  • Vertex is set for Static IP
  • 2 Seconds ON
  • Slow flash until ready
  • Steady ON

  • Vertex is set for DHCP
  • 2 Seconds ON
  • Fast Flash for 4 seconds
  • LED goes OFF while negotiating DHCP

    • If DHCP is acquired
    • Steady On

    • If DHCP fails
    • Fast flashing for 4 seconds
    • Steady ON

Back to Top

Restoring to Factory Defaults

Vertex only needs to be set to Factory Defaults if you are unable to connect to it or have been told to do so by

Option One (hardware reset):
To restore Vertex to factory defaults, flip all the switches on the back of the Vertex up, then unplug the unit for 10 seconds and plug it back in. Once Vertex has booted, flip the switches back down. Vertex is now set to factory defaults.

Option Two (software reset):
Restoring factory defaults by software requires a password from Contact us for the password then select 'Tools/Reset Hardware to Factory Defaults'. Enter password and the unit will be reset.

Back to Top

Restoring Vertex to previous working settings

To restore your Vertex to a previous working configuration, select 'File/Configuration Settings/Load/Backup'. A new window will appear. Select the date closest to the time period of the working Vertex and click 'Load'. After the file is loaded, simply click 'Save all to Vertex' located on the 'Main' tab.

Back to Top

Checking to see if monitoring ports are working

Hook up the Vertex as shown below.

Then go to VCT and select 'Tools\Port Test'

Back to Top

Call Parking and Vertex Operation

Call Parking can be accomplished by two basic scenarios. The first, is to send the caller to a general parking lot, where the exact parking space is determined by the provider. For purposes of identification, we will call this "Public Parking". The second type, is to transfer the call to an exact parking space, which we call "Private Parking". Most VoIP providers offer either one type or the other. Flexible buttons on the handset are usually programmed to accomplish the codes needed to place a call on park and retrieve parked calls.

When a caller is parked in the cloud, the call path is terminated from the caller to the on-site location. The Vertex unit sees a Bye SIP Packet and sends the termination call record. When the call is retrieved from park, the Vertex must see an Invite from the cloud server in order to recognize that a new call path has been re-established.

Public Parking

When a caller is parked in a public lot, the cloud server simply puts the parked call in a parking queue. Although an extension is assigned by the server, it may not be readily apparent. When multiple calls are parked, retrieval of a particular caller may be difficult. Only the next call in queue would be easy to retrieve.

When a parked call is retrieved from a Public Parking queue, the cloud server does not send a SIP Invite packet. Therefore, the Vertex will not recognize that the call has been re-established and will not send a Caller ID record.

Private Parking

Transferring the caller to a specific extension (parking space) allows easy retrieval of a particular parked caller. Flexible buttons (FB) can be programmed to transfer callers to exact parking extensions. These same buttons, can be used to retrieve the caller. For example, FB1 parks a call at x501, FB2 parks a call at x502, etc. Retrieval for a particular caller is as simple as selecting the FB used to park the caller. Flexible button lamps can be used to identify parked callers. Once a call is parked, the FB used to park the call lights up. Upon retrieval, the light goes off.

When a parked call is retrieved from a Private Parking space, the cloud server sends a SIP Invite packet. This allows the Vertex to report the Caller ID information of the retrieved call.

Back to Top

Setting up Vertex for a VPN

Using the Vertex Configuration Tool (VCT)
through a Virtual Private Network (VPN)

(click here for PDF version)

The VCT is required for initial configuration of the Vertex - "Caller ID for VoIP" device. The VCT application can be run on a computer local to the network, or on a remote computer accessing the site using VPN. When DIP switch #1 located on the back of the Vertex is set down (OFF), the Vertex responds to any VCT commands and sends processed call data to a Broadcast IP address ( Any local computers running VCT will see the Broadcast packets. Computers accessing the network via VPN will not.

For VPN access to the Vertex, set DIP switch #1 up (ON). Once the VCT connects with the Vertex, the Vertex sends back all command responses and processed call records via Unicast to the IP address of the requesting computer. Upon reboot, the Vertex sends out all data using a Broadcast IP, until the VCT connects again.

Running VCT via VPN:
  1. Determine IP address on Vertex.
    Login to your router and look for the DHCP assignment of "Vertex-nnnn".

    NOTE: If DHCP is turned off in your router, a known static IP would have to be previously assigned to the Vertex to use VCT through a VPN

  2. Set DIP #1 UP on Vertex. Reboot unit.

  3. Run VCT. It will not be able to connect to the Vertex on startup. Defaults will be loaded.

  4. In VCT, Select File/Location Manager.

  5. Select "Create ". Create new location and use IP address found in step #1.

  6. Select "Connect".

  7. Select File/Setup Wizard. Continue until complete.

  8. If your Caller ID application is Ethernet connected you must:
    Select Tools/Reboot Unit.
    The Vertex will return to the Broadcast mode to send call records to application.

  9. If you need to access the unit again, simply use the Location Manager and connect. Remember to Reboot unit once you are finished.

Back to Top

Copyright 2014 800.240.4637