1. Manuals
  2. Brands
  3. Reply Manuals
  4. Measuring Instruments
  5. Sidekick
  6. Pre-installation design manual

Reply Sidekick Pre-Installation Design Manual

Hide thumbs
1
2
3
4

Advertisement

Table of Contents

Pre-Installation Design Guide for the Reply Sidekick
August 2019
The Reply Sidekick has been designed to be installed directly into a customer local network switch, with
no complex requirements or network settings to be made in advance for the Sidekick to function.
Network environements can vary drastically, this document reviews how to answer the following
questions when implementing the Reply Sidekick:
1. What are the connectivity requirements for the Sidekick?
4. Where in the network should the Sidekick be installed?
6. What should the installer be aware of?
Overview
1. What are the Connectivity Requirements for the Reply Sidekick?
The last word in
VoIP support
The Reply Sidekick is not an in-line device.
The Sidekick WAN port connects to the Ethernet switch and operates on the LAN in the same manner as
an IP Phone.
The Sidekick MIRROR port (optional, but recommended) connects to the port on the Ethernet switch
configured to mirror(monitor) all, or all VoIP VLAN packets to the mirror port.
The Reply Sidekick requires 1 or 2 open ports on your switch.
1 x 100Mbps Full Duplex RJ-45 Ethernet -- WAN Port connection (required)
1 x 100Mbps Full Duplex RJ-45 Ethernet -- Mirror Port connection (optional, but recommended)
If the Ethernet topology for the VoIP or native VLAN supporting the IP Phones has more than 1 Ethernet
switch, the Reply Sidekick must be connected to the Ethernet switch connected to the Router/Gateway
(ie: up-stream of all other switches on the VLAN).
If an access-list is desired or required at a location's edge router, an example ACL is provided with the IP
addresses of the servers accessed by the Reply Sidekick for testing and auto-provisioning.
Object-group network Reply-Sidekick
18.233.142.154
34.234.245.213
34.237.115.221
34.237.134.227
52.70.49.68
54.175.45.185
100 permit any object-group Reply-Sidekick any
255.255.255.255
tcp/udp 0-65535
255.255.255.255
tcp/udp 5060, tcp 443, udp
255.255.255.255
10000-20000
255.255.255.255
255.255.255.255
255.255.255.255
replycloud.io
tcp 443
tcp 443
tcp 443
tcp 443

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Sidekick and is the answer not in the manual?

Questions and answers

Related Manuals for Reply Sidekick

Summary of Contents for Reply Sidekick

  • Page 1 Overview The Reply Sidekick is not an in-line device. The Sidekick WAN port connects to the Ethernet switch and operates on the LAN in the same manner as an IP Phone. The Sidekick MIRROR port (optional, but recommended) connects to the port on the Ethernet switch configured to mirror(monitor) all, or all VoIP VLAN packets to the mirror port.
  • Page 2 Sidekick per Layer 3 switch/router (or Layer 2 Network Domain) If there is more than one Sidekick deployed at a single location, they will report as seperate locations in the Reply Portal and can be designated by a unique name (ex: Floor 2).
  • Page 3 On the Ethernet switch with the Router/Gateway connected to it, configure the switch to mirror all Received (RX) packets on all ports (or including all ports with IP Phones, all Trunk ports from other switches, all the port to the Router/Gateway) to the Reply Mirror Port IP Phones...
  • Page 4 5. Does the Sidekick need to be installed on the VoIP VLAN? If the Sidekick is installed without a mirror port, then it can support device visibility and registration from one VLAN only, and must be installed on the VoIP VLAN.

Table of Contents