  Starting Voice Services
Do not start Voice Services until you have completed all hardware installation and you have configured Voice Services.
Once the Call Answer account and the administration preferences have been set, start Voice Services by double-clicking the Voice Services icon on the Windows desktop on the Voice Services machine.
 Analog configuration
While Voice Services is starting, watch the Brooktrout cards. The card on which the lights illuminate first is the primary card.
While Voice Services is starting, check that the number of port is correct. The screen should look something like this:
 Dialogic D42/D82 voice board configuration
When you start Voice Services with all debug levels set to 0 (default configuration), you should see something like this:
 T1/E1 configuration
When you start Voice Services with all debug levels set to 0 (default configuration), you should see something like this:
 Stopping Voice Services
To stop Voice Services, choose Server > Polite Shutdown. This will allow processes to finish before being shut down.
 WarningNever stop Voice Services by clicking the X in the top right corner of the screen. This may corrupt settings in Voice Services and the Brooktrout driver configuration.
Restarting Voice Services
Voice Services requires a restart when performing the following tasks:
• changes to the prompt directory
• changes to the area code or country code files
• changes to any field on the SMDI tab of the Voice Services Administration form
• changes to all TUI resources
• changing the pilot number
• selecting Do not answer calls at If there is no server connection on the general tab of the Voice Services Administration form
• changes to any option on the Call Logging tab of the Voice Services Administration form
• changes to the User Prefs tab, the Security tab, or the Services tab on the Group Privileges form.
The entire Voice Services machine requires a restart when performing the following tasks:
• any change to the Dialogic DCM requires a restart of Voice Services and the Voice Services machine to ensure that the firmware is correctly updated.
Voice Services log files
There are two types of voice services logs files: a session log and channel logs.
Session log
A Voice Services log file is created every time Voice Services starts. The file contains information about the Voice Services session. This log file would be helpful in troubleshooting issues where Voice Services is unavailable, there are voice gateway problems, when users can't log in, etc.
The Voice Services log file is in the same directory as the Voice Services executable file.
The log file is called VSvcs.log.
When Voice Services is restarted, the VSvcs.log is automatically renamed VSvcs.old. If you are performing several tests and need to retain all the log files, rename VSvcs.old to another name before restarting Voice Services.
Voice Services logs will only be used in troubleshooting by customer support. There is no need to be familiar with these logs, exept to know they exist and where they are located.
Channel log files
Channel log files are created on systems using Dialogic hardware every time Voice Services starts if you have selected to enable channel logging from the Advanced tab of the Voice Services Administration form. These files contain information about the individual voice channels. These log files would be helpful in troubleshooting issues where Voice Services does not answer or rings busy constantly, when there are issues with fax or DTMF tones, when calls are being dropped during a session, etc.
In order for Voice Services to generate these logs, you must create a folder in [drive]:FCServer\VS called LOGS.
Each channel will have a log file called dxxxB#C#.log. The log file names correspond directly to the channels configured in the gcconfig.cf file. See information about the gcconfig.cf file for Dialogic D42/D82 or T1 configurations.
When Voice Services is restarted, the channel logs are automatically overwritten. If you are performing several tests and need to retain all the log files, rename the logs before restarting Voice Services.
Voice Services channel logs will only be used in troubleshooting by customer support. There is no need to be familiar with these logs, exept to know they exist and where they are located.
|