Page tree
Skip to end of metadata
Go to start of metadata

Prior to the installation of a Routing Node (RNode) in your own infrastructure, you will need to configure a server (physical or virtual) in your data center or on your cloud that meets these minimum requirements and has the available bandwidth and port access described below.  Additionally, you’ll need to set up a user account on this machine and provide us remote access to the account so that we can install our software.  If you have any questions please contact the eZuce sales team to arrange this.   

Server Specification

Our recommended starting configuration to serve 100 ports:

  • 8 cores of CPU of 2 GHz or higher
  • Hyperthreading enabled
  • A minimum of 8 GBytes of RAM
  • GB or better network connection
  • More = More port capacity

In a virtual environment, expanding the Vibe infrastructure can be done easily by increasing the number of cores and RAMs available to the VM and/or spinning additional VMs with similar specifications. Additionally, if you are using a virtual environment, it will be advised to run them on different physical servers to optimize the load.

High-speed connectivity is critical. The more simultaneous meeting participants the greater the burden on the network connection so if you concentrate many users on one machine anticipate using a faster connection.  

Server Operating System Specification

Current versions of Red Hat Enterprise Linux, Linux Fedora Core, Ubuntu, CentOS, SLC, Debian, AWS Linux (AMI) are all acceptable operating systems.  In all cases, the required operating system is version 7 or higher, e.g. CentOS7 or  RHEL7.  

Server Addressing

The server should be registered in your local DNS domain and should have a publicly addressable IP address.  The system commands “hostname -i” and “hostname -f” should be run and their output must be free of any error messages or values listed as “unknown.”  Server needs to have an externally statically NAT'd IP address which will never change with time.

System Account Creation

Please connect the server to your network and create a user account for us with the name “vibe” and provide us with ssh access to it.  In case you need to restrict the login access from limited remote IP addresses, please allow ssh from our login gateways,, Please contact us for ssh public key.   

RNode Admin Account on

Please provide us a name for the RNode account and an email alias for the administrators who will manage the account on  We can only accept an alias for the administrator so you may need to contact your email administrator to set this up. 

Disk Storage

No more than 20 Gigabytes of disk space is required for our system, but if you have the Linux distribution on the same partition, you will need 50 GB total.  

Network Traffic

A heavily used 100 virtual port RNode system could see 150-350 Megabits/second of traffic.  For instances larger than 100 virtual ports contact the eZuce sales team to arrange. 

Required Ports 

Incoming Connections

  • UDP IN any 36015
  • TCP IN any 36015
  • UDP IN any 46015
  • TCP IN any 46015
  • UDP IN any 46014
  • TCP IN any 46014
  • UDP IN any 36016  
  • TCP IN any 36016 
  • UDP IN any 36025 
  • TCP IN any 36025 
  • TCP IN any 5353 
  • TCP IN any 5354 
  • TCP IN any 3232 
  • TCP IN any 3233
  • TCP IN any 3234
  • TCP IN any 3235
  • TCP IN any 3236
  • TCP IN any 3247
  • TCP IN any 3248
  • TCP IN any 4238
  • TCP IN any 9090:9095
  • UDP IN any 20000:57000  

Outgoing Connections 

    • UDP OUT any 36015  
    • UDP OUT any 36025  
    • TCP OUT any 36015  
    • TCP OUT any 36025  
    • UDP OUT any 36016  
    • TCP OUT any 36016 
    • UDP OUT any 46015
    • TCP OUT any 46015
    • UDP OUT any 46014
    • TCP OUT any 46014
    • TCP OUT any 4238
    • TCP OUT any 3306
    • TCP OUT any 6000, 6001, 6002, 8290, 8289, 8288, 80, 443  

H323/SIP connectivity

    • TCP OUT to all H323 devices you want to call (port 1720 is a must, the rest depends on H323 vendor) 

Next Steps

Once you have completed the setup and configuration of your infrastructure to match the above description please contact your eZuce sales support engineer with the location of your server and the user account access information.  Also, the contact information for the technical support person associated with the machine or VM is invaluable should we have any difficulties with the configuration. 

Optional Considerations

The following items are optional, yet provide added value to the implementation of RNode server.

Shibboleth Usage (Optional)

If your organization is part of the InCommon shibboleth federation, you can enable shibboleth authorization with To do this your Vibe™ USHI Customer account admin will need to have a dialog with your institution’s identity provider and one of our engineers. 

Extra Ports (Optional) 

You have two ports open by default - 36015 UDP and 36015 TCP - to connect with Vibe™ clients. Sometimes it is advantageous to open up more ports on your RNode server to improve the usability from non-standard locations.  In airports, hotels, coffee shops,  or in areas where users have no control over the firewall configuration,  it is useful to keep four more TCP ports open to your RNode.  These ports are TCP ports 80, 443, 8080 and 8443 both IN and OUT.  Please contact one of our engineers if you are interested in this configuration. 

Video Control Configuration of RNode Account (Optional) 

When your RNode account is created you will have preset defaults for your meeting options. In particular, each Vibe™ client accesses your RNode will have the same default GUI configuration, full video control GUI and multiple live cameras per client.   In this case, the default should be changed or overwritten on a meeting by meeting basis (using our API).  If this is your situation please contact the eZuce sales team to arrange this. 

API Account (Optional) 

If you plan to use our API interface to implement your own portal or to integrate Vibe™ with another application you will need to get in touch with one of our engineers to configure your instance to use the API.  We will need to know the name of your USHI account which will make the API connection and the IP address of the machine which will be making the API calls. 

  • No labels