Failure to Retrieve Voice Messages of the SmartCall 1000

Publication Date:  2015-07-25 Views:  148 Downloads:  0
Issue Description
Huawei's lab in India uses the SmartCall 1000 in the V100R001C01 version to demonstrate the voice message solution to customers. The system time zone of the SmartCall 1000 is set to GMT+05:30 of Calcutta, India. After the SoftCo and the service data on the SmartCall 1000 are configured, user A calls user B's IP phone and the call is automatically forwarded to the voice mailbox. The SmartCall 1000 plays an announcement indicating that the voice message is saved, but user B cannot retrieve the message left by user A.
Handling Process
Step 1 Log in to the server as the root user using tools such as PUTTY.

Step 2 Access the VoiceMail database, enter the psql -U postgre -d tstardb command, and press Enter.

Note:
After an access to the database, the tstardb=# commandprompt is displayed.

Step 3 Enter the ALTER TABLE ums_messages ALTER msgtime TYPE character varying(40) command at the database command prompt and press Enter to modify the table structure.

Note:
If ALTER TABLE is displayed, the table structure is successfully modified.

Step 4 Enter the \q command at the database command prompt and press Enter to shut down the database connection.

Step 5 Re-perform the process of voice message leaving and retrieval. The message is successfully retrieved.

----End
Root Cause
The possible cause is that the database design is improper. Because the SmartCall 1000 plays an announcement indicating that the voice message is saved and the recording file is saved to a folder of the SmartCall 1000, the SoftCo and trunk problems are ruled out. The lab analyzes the SmartCall 1000 logs and finds that inserting the recording file index to the database fails, though the voice message is saved. The failure log is value too long for type character varying while executing the query (non-fatal). Based on the fault diagnosis, it is found that the database design causes the problem. Because the GMT offset is half an hour in the home time zone, the length of the recording duration inserted exceeds the length of the time field in the ums_messages table, which further leads to the failure of inserting the recording file index. Consequently, messages fail to be retrieved.

END