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.


Failure to Make Outgoing Calls

Publication Date:  2015-04-17 Views:  485 Downloads:  0

Issue Description

When a user dials 13825055381 through an extension 8200, the call fails to be set up and the user hears a message "The number you dialed does not exist." The user then dials again and the call is set up that time. When the user dials for the third time, the call fails to be set up again. However, when the user dials for the fourth time, the call is set up again. This situation repeats.

Handling Process

Step 1 Capture outgoing call logs.

This user makes outgoing calls using the PRA trunk.

Step 2 Analyze the PRA flowchart using the UCMaint.

When the user makes the first outgoing call, PRA signaling cannot be recognized. However, during the second attempt, PRA signaling is recognized.

Step 3 Analyze the logs.

The following exception information is identified.
[2011-11-09 15:05:31.37][ccm.c 51522][dwCCMNo= 52] CCM_CheckIfSipTk
[2011-11-09 15:05:31.37][ccm.c 51544][dwCCMNo= 52] Called is SIPTK!
According to the CCM analysis result, this call is routed out through the SIP trunk.

Step 4 Conclude the failure reason.

In principle, one office route can be bound with multiple trunks. In this case, during the route selection, the SoftCo selects an invalid trunk.
Office TKGType Priority Detail CodeType DPX
------ -------------------- -------- ------------------------------------- -------- ---
0 PRA[BIDIRECTION]\SIP 0\0 Card[1]\PeerComponent( N/A
PeerDeviceName SendMask RecvMask CarrierId RegGroupId Officetype AlarmPercent
-------------- -------- -------- --------- ---------- ---------- ------------
NA NA 0 0 External 100
OfficeSelectCode TimeIndex Charge UserPriorLevel CfgPercent CurPercent CallNum Prefix
---------------- --------- ------ -------------- ---------- ---------- ------- -----------
0 - - - - - - 0

Step 5 Run the config protocol sip disable officeno 0 command to delete the invalid trunk.


Root Cause

The possible cause is that data.bin configurations on the SoftCo are incorrect.