Avaya 2 manual Text-to-Speech output is not heard, Automatic Speech Recognition fails

Page 32

Contents

Text-to-Speech output is not heard

If TTS output does not play in an application, use the following procedure to investigate the problem.

To investigate the problem:

1.Check for allocation errors (TTS008) in the error log.

This error indicates that a request for a TTS resource was denied, and the associated TTS will not be heard. This error occurs when there are no TTS resources in service. Either there are not enough TTS resources administered for the application or the resource is temporarily out of service because the connection dropped. In either case, consider adding more TTS ports on the Avaya Interactive Response.

2.Run a trace of the application and/or the Avaya Interactive Response VROP process.

3.MRCP errors (called status codes or completion causes) are logged in the VROP trace and are reported to an application. At the highest trace level (5), the VROP trace will show all MRCP messages exchanged. A SPEAK request will contain the TTS intended for play and the corresponding SPEAK-COMPLETE from the server will contain the status code or completion cause for that request.

Interpret the trace results using the MRCP specification and by consulting with the MRCP server vendor as needed.

Automatic Speech Recognition fails

If speech recognition fails, use the following procedure to investigate the problem.

To investigate the problem:

1.Check for allocation errors (PROXY011) in the error log.

This error indicates that a request for a recognition resource was denied and speech recognition will fail. This error occurs when there are no recognition resources in service. Either there are not enough resources administered for the application in use or the resource is temporarily out of service because the connection dropped. In either case, consider adding more ASR ports on the Avaya Interactive Response.

2.Run a trace of the application and/or the Avaya Interactive Response ASRPROXYMGR.

MRCP errors (called status codes or completion causes) are logged in the ASRPROXYMGR trace and are reported to an application. At the highest trace level (5), the ASRPROXYMGR trace will show all MRCP messages exchanged. A recognition request spans several MRCP messages, each with a corresponding response. If the request fails, then the response will contain a status code or completion cause.

Interpret the trace results using the MRCP specification and by consulting with the MRCP server vendor as needed.

32 Avaya IR R2.0 Troubleshooting

Page 31 Page 33
Image 32
Page 31 Page 33
Contents Issue 1.0 April 2006 Avaya Interactive ResponseDocumentation disclaimer Troubleshooting overview TCP/IP FacilitiesPage Contents Public switched telephone network Pstn ContentsAvaya IR R2.0 Troubleshooting Requirements for successful operationsConnections and communications SwitchesVoice response applications Possible malfunctions and errors Incorrect system administrationSystem and LAN capacity Hardware malfunctions and failuresApplication errors Connection and communication problemsCircuit-based configurations Packet-based configurationsSpeech Identifying possible causes of problemsProblems Effects Actions LAN Troubleshooting procedure Reviewing the Display Equipment screen Using IR system eventsGathering information on a problem Using Sun diagnostic tests Monitoring live operationsChecking system history State MeaningTroubleshooting based on observations Using commandsInvestigating operations problems Call-handling problemsVoice system not answering ― Enter display card all and press EnterAll calls dropped Calls droppedCalls dropped at initial prompt Calls not transferred properly VoipcallforceclearedNo Dtmf tones Wink protocol Fax problems Typical fax problemsPoor audio quality on VoIP calls Touchtone not interpreted correctlyLocating fax errors Interpreting negative fax valuesReviewing fax repair procedures Host interaction problemsHost sessions recover repeatedly Fax text or file not foundSpeech and TTS problems Speech delayed or cut offNo response for application with host interface Calls to host droppedAll ports Broken on speech server Cannot configure speech recognitionSpeech resource bad or non-configured Speech recognition rejecting many responses Speech response delayedSpeech server not running Speech recognition not working Speech not playingMrcp problems Checking for errorsChecking the server connection Mrcp connections and protocolsMrcp configuration file Parameter Description Default SettingExample TrueMrcp servers are frequently out of service Erratic availability of Mrcp speech resourcesASR Server Name Base Servers Port NumbText-to-Speech output is not heard Automatic Speech Recognition failsR2.0 Returning TTS resource state to Inserv Text-to-Speech problemsSelect Administrative Tools Select Component Services System process problems Unix commands failing or disk errorsExecute Unix command failed On the Tree tab, select Services LocalChecking Oracle object size limits Database problemsChecking Jdbc operations Checking communications Word about the Tomcat server logChecking LAN communications Localhostlog.2004-05-07.txtTroubleshooting speech server disconnections Typical causes of LAN problemsResources for LAN troubleshooting Troubleshooting database server disconnections Troubleshooting intermittent LAN problems Troubleshooting persistent server problemsPinging server connections Monitoring Ethernet packetsTracing LAN activities Specify the IP time to live for multicast packetsDetecting incorrect IP addresses arp Displaying network statistics netstatDisplaying packet route traceroute Resolving a problem when the monitor does not display Checking hardwareChecking cable connections Sun Blade 150 cable connectionsContents Label Function and troubleshooting considerations Label Function and Troubleshooting Considerations Sun Fire 280R cable connectionsTesting platform hardware FC-ALChecking card and channel states Checking NMS card configurationCommands Functions Restoring Manoos cards and channels Restoring Netoos cards and channels Restoring Foos cards and channelsRestoring Broken NMS and VoIP cards Inspecting the IR system platformChecking card administration Removing and restoring cards Displaying data on VoIP cards Gathering data on card operationsDisplaying data on NMS cards Checking for hard disk drive failures Performing root cause failure analysisReplacing a failed hard disk drive Running the metastat command Removing a failed hard disk drive Spare Okay C1t1d0s1Enter mirroradmin detach Activating disk mirroring for a new hard disk driveRestoring the system if both hard disk drives fail Disabling disk mirroringContents Issue 1.0 April 2006 Page Index Index
Related manuals
Manual 51 pages 39.31 Kb

2 specifications

Avaya 2 is an advanced communications solution renowned for its robust features and adaptability, catering to businesses of all sizes. It is part of Avaya's strategic focus on delivering unified communications and contact center solutions that emphasize efficiency, collaboration, and customer satisfaction.

One of the main features of Avaya 2 is its seamless integration with a variety of communication tools. This includes voice, video, messaging, and conferencing capabilities that empower organizations to connect with employees and customers effortlessly. The system supports both on-premises and cloud deployment, allowing businesses to choose an infrastructure that aligns with their operational strategy.

Avaya 2 leverages cutting-edge technologies such as artificial intelligence and machine learning to enhance user experience. These technologies streamline processes by automating routine tasks and providing insights through data analytics. For instance, AI-driven chatbots can handle customer inquiries, freeing human agents to focus on more complex tasks, ultimately improving response times and customer satisfaction.

Another characteristic of Avaya 2 is its customizable user interface. The platform allows users to personalize their workspace, making it easier to access the features they use most frequently. This level of customization fosters better productivity, as employees can tailor the system to suit their specific workflows.

Security is a top priority for Avaya 2. The solution incorporates advanced security measures including encryption, authentication protocols, and compliance with industry standards to protect sensitive data. This is especially crucial for organizations handling proprietary information or customer data, as it mitigates the risk of breaches and builds trust with clients.

Moreover, Avaya 2 enhances collaboration through features such as team messaging and video conferencing, facilitating real-time communication among teams, which is essential in today’s hybrid work environment. Organizations can create dedicated channels for projects, ensuring everyone is aligned and informed.

Overall, Avaya 2 stands out in the crowded field of communication solutions due to its unique blend of features, state-of-the-art technology, and emphasis on security and customization. It serves as a reliable platform for businesses looking to enhance communication efficiency, improve collaboration, and elevate customer satisfaction in an increasingly digital world.
Top Page Image Contents