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

Reminder

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

upgrade
Knowledge Base

The terminal calls special service number fault because of area code distribution.

Publication Date:  2019-07-23  |   Views:  245  |   Downloads:  0  |   Author:  SU1001573735  |   Document ID:  EKB1000015955

Contents

Issue Description

Terminal call special service number 168 but can join conference. Check GK log, and the reason lies in GK rejection because of:
gkRejAddrTransFailNullAlias.
GK log is shown below:
 

12:16:40 ARQ recvfrom [(61.*.*.46:1719)] [Caller] [***60] [(61.*.*.46:1720)] [Callee] [168] [1024000 bit/s]
12:16:40 ARJ sendto [(61.*.*.46:1719)] [Caller] [***60] [(61.*.*.46:1720)] [Callee] [***11207] [gkRejAddrTransFailNullAlias]
MCU call terminal can join the conference. GK log is shown below:
12:25:50 ARQ recvfrom [(61.*.*.66:1719)] [Caller] [******07] [(61.*.*.66:1720)] [Callee] [***60] [768000 bit/s]
12:25:50 ACF sendto [(61.*.*.66:1719)] [Caller] [******07] [(61.*.*.66:1720)] [Callee] [***60] [(61.*.*.46:1720)]
12:25:50 ARQ recvfrom [(61.*.*.46:1719)] [Callee] [***60] [(61.*.*.46:1720)] [Caller] [******07] [(61.*.*.66:1720)] [768000 bit/s]
12:25:50 ACF sendto [(61.*.*.46:1719)] [Callee] [***60] [(61.*.*.46:1720)] [Caller] [******07] [(61.*.*.66:1720)]


Alarm Information

Null

Handling Process

Change the MCU area code in RMCC.

Root Cause


First, analyze the portion log of terminal call special service number.
12:16:40 ARQ recvfrom [(61.*.*.46:1719)] [Caller] [***60] [(61.*.*.46:1720)] [Callee] [168] [1024000 bit/s]
The above log shows ***60 calling 168 and the bandwidth is 512K.
12:16:40 ARJ sendto [(61.*.*.46:1719)] [Caller] [***60] [(61.*.*.46:1720)] [Callee] [9*****07] [gkRejAddrTransFailNullAlias]


This log shows that GK resolve special service number as conference number 9*****07, but call is rejected. The reason is: gkRejAddrTransFailNullAlias, which means GK cannot find the node which name or number is 9*****07.This result can be proved by GK command:
DOPRA>endpoint show bynumber 9*****07
No such endpoint!
Why MCU calls terminal successful? Let’s see the process of MCU calling:

12:25:50 ARQ recvfrom [(61.*.*.66:1719)] [Caller] [02****07] [(61.*.*.66:1720)] [Callee] [***60] [768000 bit/s]
12:25:50 ACF sendto [(61.*.*.66:1719)] [Caller] [02****07] [(61.*.*.66:1720)] [Callee] [***60] [(61.*.*.46:1720)]
The above two records is calling ARQ/ACF, i.e. the ARQ/ACF sent by MCU. Notice that the calling number is 02****07, but the conference number which resolved by GK is 9*****07 when terminal calls special service number. Normally, the calling number is same with conference number.
12:25:50 ARQ recvfrom [(61.*.*.46:1719)] [Callee] [***60] [(61.*.*.46:1720)] [Caller] [02****07] [(61.*.*.66:1720)] [768000 bit/s]
12:25:50 ACF sendto [(61.*.*.46:1719)] [Callee] [***60] [(61.*.*.46:1720)] [Caller] [02****07] [(61.*.*.66:1720)]


Analyze above phenomenon, and the result is: the MIPU board area code configuration is not equal with RMCC area code in local management desk. MIPU area code configuration is 02*, but the MCU area code is 9**.


Suggestions

Null