This document assumes the administrator is familiar with the basic concepts and components of Citrix EasyCall. This document is targeted to the steps and requirements for successfully building a Citrix EasyCall Proof-of-Concept environment and does not address all the intricacies or interactions of XenApp environment. The goal is to provide a working example of the technology.  
An EasyCall Proof-of-Concept environment is expected to be isolated from the production environment (if possible). 
A successful EasyCall Proof-of-Concept environment has five parts. The five parts covered in this document are pre-installation check list, installation of the EasyCall Gateway, configuring the EasyCall Gateway, installation of the EasyCall agent (agent can be installed local, streamed, published, and a web services API), and call test scenarios. Each of these parts is discussed in the sections below.

Pre-Installation Requirements

The successful Proof-Of-Concept (POC) begins with simple preparation, if completed correctly will allow for the completion of the POC in a timely manner. Below is a list of pre-installation requirements that are recommended.  

Firewall Requirement

The firewall used for the EasyCall Gateway must allow TCP traffic over port 8443 for communication with the EasyCall Agent or Web Services API.

If SIP trunking is used, the telephony system and the EasyCall Gateway must not be separated by a firewall or NAT. 

Basic Network Connectivity


  • Interface 1 IP address:

(By default, Interface 1 (left port) is configured with the static IP address and a subnet mask of and Interface 2 (right port) is configured for DHCP.  Interface 1 must always be used for SIP trunking.)

  • Subnet mask:
  • Default gateway IP address:
  • DNS server (s): 

Citrix License Server

Review Citrix License Server documentation at

One of the first question is to ask if the site has a current Citrix License Server.  If they have a current server we can use it and install evaluation licenses.  The preferred method would be to setup a new Citrix License Server just to support the POC.  That way when the POC concludes the Citrix License Server can be removed without effecting production.  
The items below are setting for the EasyCall Gateway UI for Citrix License Server: 

  • Do you have a Citrix License Server? (yes/no)
  • Citrix License Server IP address:
  • Citrix License Server host ID/MAC address:
  • Use Citrix Presentation Server Platinum Licenses? (yes/no)  
    Citrix Licenses can be downloaded through the following url and links: >support >downloads >licensing components  

Telephony System

EasyCall Gateway listens for SIP messages on UDP port 5060 (default port).  The PBX side of the port is configured by the customer.  See the EasyCall Gateway Integrator’s Guide for specific PBX requirements.

Select the telephony system used at the site: 
Please see EasyCall PBX Integration list for currently supported PBXs and configurations. 

Call Setting Configuration

Settings below are from the EasyCall Gateway UI:

  • External Trunk Access Code: (example 9, 8, 0)
  • Country Code: (example 1 for U.S., or 44 for the U.K.)
  • Area Code:
  • International Dial Prefix: (example 011 for U.S. or 00 for the U.K.)
  • Domestic Dial Prefix: (example 1 for the U.S.) 

Call Setting Customization

Other local area codes or overlays: (this is used if there are multiple local area codes for large cities/areas) :

  • Area code: (does local dialing require the area code? Yes/no), (Domestic prefix? Yes/no)
  • Numbers to be recognized as extensions: (example 3, 4, or 5 digits)
  • Extensions preceded by: (example #, /, Ext., Ext:, other) (“Ext” includes all variations of capitalization)
  • Extension prefix?
  • Dial private network numbers as an: External or Internal number 

Directory Source Configuration

Settings below are from the EasyCall Gateway UI, you can also add multiple directory sources within the EasyCall Gateway configuration.  During a POC it would be best to add one LDAP source either from an Microsoft Active Directory connection or a CSV file located on a FTP server.

  • LDAP server IP address and port number: (LDAP server port defaults to 389.  If you use an indexed database, using port 3268 will significantly speed the LDAP queries.)
  • LDAP Bind DN and password: (example – ou=administrator,dc=ace,dc=com)
  • LDAP Base DN: (example – ou=Users,dc=ace,dc=com)
  • LDAP Attribute Fields: (example – Display Name=cn, Surname=sn, FirstName=givenName)  These fields will vary depending on the setup the LDAP environment.