Result Validation

<< Click to Display Table of Contents >>

Navigation:  Configuration > Configuration Guide (Web Mode) > Verifying the CDR Service >

Result Validation

Navigation: Configuration > Configuration Guide (Web Mode) > Verifying the CDR Service >

hm_btn_navigate_prevhm_btn_navigate_tophm_btn_navigate_next

Verify through this section whether FTPServer can extract ticket files from the unified gateway.

The operation steps and expected results of verifying the FTPServer to extract call orders are shown in Table 1.

Table 1 Verification steps for CDR business

Parameter

Value

1. User A calls User B.

User B's phone rings.

2. User B answers the call.

User A and User B call.

3. User A or User B hangs up.

The call ended.

4. Enter the directory where the ticket files are stored on the ticket server, such as "D: Bill CurFile 192.168.1.20 20140403".

Explanation:

In the path, "192.168.1.20" represents the I address of the unified gateway where the calling user is located, and "20140403" represents the call list storage directory named according to the call date.

Below this folder, you can see the call tickets generated by user A and user B calls.

Explanation:

The FTPServer saves the temporary call ticket file obtained from the unified gateway as "XXX. bill. tmp" and renames it to "XXXbbill" approximately 5 minutes later.

Parent Topic: Verifying the CDR Service

 

 

< Previous topic