Vertex – Caller ID for VoIP
The Vertex is compatible with any software designed to use CallerID.com’s analog products. It is configured via the
Ethernet "Management Port”. The serial port output is for software that does not accept Caller ID data via Ethernet.
• The Vertex is designed to capture only
• If you are using standard telephones, a CallerID.com analog device will be required, instead of the Vertex.
Determine Your Type of VoIP
Hosted VoIP
call functions. In some cases, the end user needs only to connect VoIP phones to their network. Any significant
programming and configuration is accomplished by the service provider. Most small bu sinesses use Hosted VoIP.
Managed VoIP
processing. If you have a Managed VoIP system, an IT or telephone professional would have installed it.
Basics
1. There are 3 network ports on the Vertex. The 2 VoIP Bridge Ports provide a pass-through li nk between two
network endpoints at 100BaseT, with processing circuitry 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.
The service provider performs all voice switching, routing, messages on hold, call queuing, and other
involves additional equipment on site that handles most of the VoIP switching, routing, and call
standard, non-encrypted SIP (Session Initiation Protocol).
2 The Management Port is used to configured the device. Data is sent out this port to software applications that
accept Caller ID via Ethernet. Connect this port to the same subnet that your Ethernet enabled Caller ID
application is running.
3. The two VoIP Bridge Ports are pass-through ports. They are not seen as endpoints by the network. They
simply connect the wire that carries all VoIP traffic between 2 endpoints such as a switch and a router.
All VoIP traffic of interest must pass through the VoIP Bridge Ports for correct Vertex operation.
4. We recommend the Vertex Bridge Ports connect the two network endpoints nearest to the VoIP telephones,
while still being in-line with all VoIP traffic. The diagram below shows the Vertex connecting a network switch to
a P.O.E. switch powering the phones.
Vertex Setup Instructions
1. Refer to Figs. 1-4 to decide which connection diagram best matches your VoIP Network architecture.
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. If the Vertex is placed between 2 Gigabit endpoints,
reboot each device to allow automatic negotiation to 100BaseT. Refer to troubleshooting below.
3. 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.
4. 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, refer to troubleshooting below. The green lights on each
channel should flash, indicating data packets detected.
5. 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.
6. Download and install the Vertex Configuration Tool (VCT) at www.VCT.CallerID.com
7. Launch VCT. Upon startup, VCT must find the Vertex hardware. If the hardware is not found, turn off any thirdparty Firewalls or virus checking programs, re-check Ethernet connections, and try again.
8. Once the hardware is detected, select “Yes” to load parameters from the Vertex.
9. VCT will prompt you to run the Setup Wizard. Run the Wizard and follow all steps carefully. When
completed, exit VCT.
10. Set the appropriate parameters within your software application to enable Caller ID pop-up screens.
.
Setup Troubleshooting
Issue: Vertex Configuration Tool (VCT) will not detect the Vertex hardware.
Solutions:
A. Check the Vertex Management Port lights. The amber light must be on and the green light flashing.
B. Turn off any 3rd party Firewalls (i.e. Norton, McAfee, Trend Micro, etc.).
C. If DHCP on the router is enabled, re-boot Vertex hardware in an attempt to negotiate DHCP.
D. Check the router DHCP table to determine whether the Vertex is listed. If shown, UDP broadcasts may be
blocked by a network appliance. Ping the address listed. If the Ping is successful, go to step F.
E. If DHCP on the router is disabled, try to Ping the Vertex at the default IP address of 192.168.1.90.
F. If Pinging the device is successful, you may have to use File/Connection Manager in VCT to communicate
via unicast. In order to use the VCT Wizard via unicast, follow the same instructions as "Setting up Vertex
for a VPN" under Troubleshooting, at www.VCT.CallerID.com.
Issue: One or both amber lights on the VoIP bridge ports are not steady on. Note, both amber VoIP bridge ports
Solutions:
Technical Support 770.263.7111
8:30 am - 5:00 pm, M-F, EST
Support@CallerID.com (Include Serial Number of Device)
CallerID.com 5680 Oakbrook Pkwy. #150 Norcross, GA 30093 USA
must be steady on for the Vertex to operate correctly.
A. If you are placing the Vertex VoIP bridge ports between 2 Gigabit endpoints, both endpoints may need to be
re-booted to auto negotiate to 100BaseT. If re-boot does not create a network connection, the port
connected to the Vertex on one endpoint will need to be configured to 100BaseT.
B If the network connection is working properly and one or both amber lights are still not on steady, try
connecting the Vertex to another location closer to the VoIP phones. If the problem still exits, refer to "Amber
Lights not Coming On or Flashing", under Troubleshooting, at www.VCT.CallerID.com.
Loading...