The route testing dialer is a software module that lets you test quality of routes provided by your vendors by automatically dialing certain auto-generated or manually entered numbers.

The dialer may be used to:

• obtain information on the quality of service provided by your vendors and use it to change your switch routing.
• resolve conflicts with vendors when they charge you for FAS.

• Automation of outgoing dialing. Test requests are created via a clear and convenient interface, several 5gVision users may create requests simultaneously.
• Initiate route tests for a certain stats object (vendor, area) right from the Table, Report, or Alert modules.
• FAS (False Answer Supervision) detection for routes tested.
• Full CDRs with information like duration, PDD, TTC, disconnect codes, etc.
• Signaling logs and Call flow charts for each test call. It is possible to send a call flow chart as an external link to a vendor or save the signaling packets into a PCAP file.
• Recording of media stream with or without early media in wav or mp3 formats.
• Task scheduler to allow users to run various dialer requests automatically according to time schedule.
• Sending tickets to vendors on the basis of testing results.

• Switch to send calls to - one of your switches for the test calls to be routed to.
• Call recording options - how the call will be recorded - wav or mp3, with or without early media.
• Simultaneous test calls - number of simultaneous calls to test numbers in a batch.
• Caller ID pattern - caller ID to show to called numbers (you may generate random numbers using a pattern).
• Vendor from statistics - vendor from the statistics module to test termination of calls to.
• Vendor technical prefix - technical prefix to add to each number.
• Area from statistics - areas from the statistics module to match when extracting numbers from CDRs or generating random numbers.
• Numbers area codes - area code for which to retrieve test numbers from CDRs.

• Min duration in CDRs, Max duration in CDRs - when the System selects destination numbers from CDRs, it will only consider CDRs with the duration over the minimum and less than the maximum.
• Search interval, Search offset* - the System will select destination numbers from CDRs within the interval from the offset.
• Minimum numbers length - minimum valid numbers length for tested codes. Needed to generate random (= this length) and wrong numbers (< this lehgth).
• Flag FAS for short numbers - flag a call as FAS one if connect is to a wrong number shorter than the set minimum.
• CDRs/random/wrong pattern - defines the count of real numbers (from CDRs) / (random numbers) / (intentionally wrong numbers) to be tested.
• Numbers to dial - the list of numbers to be dialed.

The key column in the request log table is the Test result which contains the status of the test (% done, OK or FAIL) updated as the test progresses. The test is considered a success if the ASR value was above a preset threshold and there were no calls with FAS.

The system considers an attempt to be FAS-terminated in the following cases:

• The call connected to a specially generated incorrect number.
• The call disconnected as the maximum duration time was exceeded.

You may open a CDR screen via the pop-up menu over the desired test record or by double-clicking the record in the Request log. A new CDR window will pop up with only the calls pertaining to the test filtered.

Apart from usual CDR parameters including detail media statistics, this window will contain the Audio recorded column with audio waveform to playback and the Audio get file column hosting a link to the recorded call.

You can easily display Signaling logs or Call flow for a certain call right from the CDR table using the context menu.

They include all signaling packets that were exchanged between the dialer and your switch.

You can see RTP streams, play media and show detail media stats right in the call flow window.

Shared links let your partner see the shared data in the same way as you do.

You always can export signaling logs as a PCAP file.

You should just select required CDRs of a certain test request and click the Ticket button.

Most of the fields in the floating form will be automatically filled up according to the chosen CDRs but they are editable.

You may select preconfigured Ticket reasons and Email templates. Special keywords can be used in the Email subject.

Results of tickets sending are displayed in the separate Ticket log.