No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

The MCU PRI can not call out

Publication Date:  2019-07-23  |   Views:  214  |   Downloads:  0  |   Document ID:  EKB1000015575


Issue Description

The MCU PRI can not call out, including local and long-distance calls, but the terminal is capable of normal call in.

Alarm Information


Handling Process

At first, suspected carrier Bureau data is not right, carefully checked the MCU data settings, the operator defined meeting place and added the country code 86 to each meeting place, and added the area code 01* to the local meeting place. Removed 86 and 01*, the MCU called local terminal and quickly accessed to the conference. Then called a S place's terminal, still calling barrier, called to the bureau to confirm, PRI does not open long rights. The next day opened long right, then the MCU call the S place normal.

Root Cause

MCU define venue, the venue number part need to confirm focus. The current method is that when define meeting, the country code and area code have a default value of "86 and 07**". So that many people do not pay attention when configure meeting place, the original local number is unnecessary, but because there is no notice to delete it, so cause these problems. Proposed two modifications:
(1) Doesn’t provide a default value. If you really need the country code and area code, set by the users themselves, which should not overly;
(2) All the meeting places set the country code and area code, but to increase judge operation in background or foreground software. If find the calling and called numbers their area code of the country code are same, that is say it is a local number, remove the country code and the area code. If they are not same, it is a long-distance, using the area code or the country code.