Client/Server Features
 

Client List
Client Edit Screen
Client Test
Troubleshooting Client/Server problems
 

Client List

Shows the list of clients registered with the CallingNow Server. Clients are active after they are added. To select a client in the list, double click any column in the row.

Note: Each client requires a separate license. Client licenses can be purchased individually or in a bundle.

Toolbar
The Client List toolbar contains the options for adding, editing and removing the clients accessed from the CallingNow Server:.
Save Save the changes to the current client list.

Edit Edit the name, location or protocol of the client.

Add Add a new client at the end of the list.

Copy Create a copy of the highlighted client below the existing client.

Insert Insert a new client immediately below the current client.

Delete Delete the client from the list.
 

 Client List Columns

#ID – Sequential index number in current directory. This number is assigned when the directory editor is started. If you change the order of the clients, then the next time the client editor is opened the numbering of the servers will reflect the new order.

Name – Network name of the client

Address – IP address of the client.

#Protocol – Protocol used to communicate with client.

Type – Client.

Status – Active, Passive or Inactive.

Status Date – Date of last status change.

Notes – optional annotation.

Calls – Number of calls relayed since program started.

Call Date – Date last call was relayed.

 Hints

• Expand the client list and form by dragging the left edge of the screen to the right.

•  Selected clients can be deleted, copied, viewed or played from the toolbar, or by right-clicking with the mouse.

• Listing can be alphabetically sorted by any of the column headings by clicking on the column title.

• Double click the client to select the client to edit.

•  A single right click of the mouse will give the client edit options in a pop-up context menu.

Client Edit Screen

The Edit server screen permits users to add new or edit clients in the list.

Pressing the Add or Edit button on the Directory toolbar accesses this screen.

Client name

Enter the Name  of the client (i.e. SALES).

IP Address

Enter the full IP address of the client (i.e. 192.123.22.34)
Find It – look up the IP address using the client’s name.

Client Protocol

Select the time-sync protocol used to communicate with CallingNow Client. The choices are:

TCP (TCP protocol) Default setting.

UDP  

Notes:

·         Protocol must be the same on both CallingNow and Service module.

·         Use UDP protocol if TCP is unavailable or has problems

·         Port number is an application wide setting and is set in the Options-> LAN screen

Active/Inactive Passive/Skip – shows if client is currently active and in use by CallingNow.

A client is considered either:
Active -running  CallingNow Client
Inactive -running CallingNow Client, but not currently logged on, running or connected,
Passive (visible on the network but not running CallingNow Client) or
Skip – disabled or not visible on the network.

Notes: Optional field to identify location of the client, i.e.: Receptionist desk

Client Test

This form is the base test screen for conducting client communication tests.

Test Features

•        Checks client access and connection with 4 different tests.

•        Includes name lookup test and ping test to check for basic accessibility of the client.

The client test lets you check both the connection and the capability of local or remote clients. Compatibility and connection problems can be diagnosed using the built in 4-point connection test. 

Client Section        
Current settings in CallingNow.

Address
Name of the client. This is the name that will be used for testing.

Port        
Number of TCP or UDP port used to communicate with client.

Test Request Section        
Choose tests to run on client.

Test        Check to select the individual test

Tests Available:

Resolve name

Check that network name can be resolved to an IP address.

Ping

Common connection test to verify connection to a remote client. The ping utility uses the ICMP echo request and echo reply packets to determine whether a particular IP system on a network is functional.

TCP

TCP protocol used to communicate with client using given port number.

• Passes test: A pass means that the server can communicate with the CallingNow client via the TCP protocol using the port specified and that the client responded.

• Fails test: If it fails this test then check communication between the server and client computer. Check to see if firewalls are blocking communication. Check also to see that the client is visible in Windows on the network using Windows Explorer. Finally check if the CallingNow client is running, and that the port number and protocol are the same on both the client and server.

UDP

UDP protocol used to communicate with client using given port number. See the TCP test above for interpreting test results.

Protocol        
Name of the test to run.

T/U
Whether the test uses a TCP or UDP type connection.

Port
Port number used to communicate with client in test. Unless configuring behind a proxy server, accept the default.

X
Toggle all tests on or off.

Test button
Start to run the tests selected from top to bottom.

Cancel button
Cancel any remaining tests (will finish current test).

Timeout Interval
Interval in seconds to wait for the client to respond for each test.  If the client does not respond within the interval, then the test fails.

Test Results Section

Shows the results of the communications tests.

Pass (Gd) Test Checkmark
The client has responded to the test with the appropriate response.

Fail (Bd) Test Checkmark
The client has failed to respond to the test on the port specified, or the response was in an unexpected format.

Remarks/Data
The string returned by the client or the results of the test.

Buttons

Help        
For on-line help.

Exit                
Exits the client test.

Troubleshooting Client/Server       

The LAN Options specify if CallingNow Server will listen for Clients and, if so, will specify the port and protocol it uses.

Server Fails to Contact Client

• Check the licensing of the Server (see the “Exceeds License” message below).
• Check the address specified on the timeserver tab of the Client (run ipconfig from the DOS command line on the Server to determine the Server’s IP address). Try the IP address instead of the server name.
• Check that the port and the protocol are the same on both the Server’s LAN option tab and the Client’s LAN option tab.
• Check the communication (ping from the Client to the Server using the address).
• Check that the port is available for use by CallingNow (run netstat –a from the DOS command line on both client and server for a listing of TCP and UDP ports currently in use).
• Use the Client Test to check if the server can communicate with the client and that the client software is running.

Clients get “Exceeds license” message

• CallingNow Server must be licensed for each CallingNow Client in use. Contact Beagle Software to purchase additional licenses or to obtain an evaluation license for multiple clients.

Clients fail to Screen Pop when I press the “Test” button

• The socket connection used to communicate with the Server and a specific client remains open for approximately 2 minutes after the client makes a time request.  This is a Windows operational setting and individual clients must wait at least 2 minutes between successive time setting requests.

CallingNow won't relay call to client

• Check that the connection to the LAN is working by “pinging” the client.

• Client isn't running

• Client/Server doesn't have the same settings for communication

• There is no LAN connection to the client selected

Log doesn't show anything”

• No call with a match has been made since startup.

• The log file has not been specified or is turned off

• Logging is off or no file has been specified to write the log to.

• File system is full.

 ‘Address in Use’ or ‘Can’t Reset Server’ Error Messages

• Is usually due to the TCP port that the Client-Server communication normally uses is being used by another application or otherwise unavailable. . If another application is using this port then CallingNow is unable to open it and complains.

• The port number can be changed on both Server  and Client.

Diagnostic Routine

You can run CallingNow in the diagnostic mode, which provides a trace log to pinpoint problems.

1. Run CallingNow in diagnostic mode  by selecting the "Diagnostic trace" option under logging.

2. View the diagnostic trace file (DebugFile.txt)

3. Check for “ERRORS” or connection problems in the trace. If necessary, you can forward the trace file to Beagle Software support for analysis.