The phone screen displays "Call Traced" for a few seconds when answering a call. (two hipath4000 pbx connect with ECMAV2,H323 protocol)

[wabe-hk]

Hello everyone
I am currently facing a strange issue. Two Hipath 4000 systems (v5.0) are networked through HG3550IP H323 ECMAV2 protocol. Recently, when the PBX at site B answers a call dialed from site A, the screen displays “Call Traced" for a few seconds. The settings at both sites should not have been changed. This issue seems to have appeared suddenly, and even after restarting the PBX, the problem persists. Could anyone please advise on a possible solution? Thank you very much.

The following are some of the system settings：
ADD-TDCSU:NEW,1-04-079-0,85,85,0,0,100,32,32,"IP ",0,"ECMAV2",8,,NONE,,,
,GDTR,N,TIE,NONE,N,0,,,,,,,31,MANY,100,0,1,1,EMPTY,85,10,N,,,,,,16,8,1,10,,EC&G71
1&G729AOPT,,100,CIR,Y,SECURE,HG3550IP,1&&30,N,1,3,0,0,0,0,0,N,;

ADD-COT:85,XFER&ANS&CEOC&CEBC&ITT&CBBN&CBFN&DPRE&LWNC&CECO&DFNN&NLRD&DSDL&NCT&DTM
F&NTON,,;

ADD-COP:85,DTMF&SFRM&L3AR&NTON&DTM4,,,,;

DD-COSSU:,100,,,,,,,,;
CHANGE-COSSU:COS,100,TA&TNOTCR&CDRATN&CDRS&CDRSTN&CDRC&CDRIND&CDRINT,,,,,,,;
CHANGE-COSSU:COS,100,COSXCD&CFNR&VCE&FWDNWK&CFB&FWDDIR,,,,,,,;
CHANGE-COSSU:COS,100,,NOCO&NOTIE,,,,,,;
CHANGE-COSSU:COS,100,,,NOCO&NOTIE,,,,,;

 

[Moriendi]

Is it all calls from A to B ? Or a specific extension?

A tracs trace would show if the message was delivered from A, or created by B.

What is the "TRACE" value set to in SBCSU?

Is any HISTA created for each call?

You could take an old regen from the PAS area, create a new regen and compare for both nodes.

I have never seen that message so I am just guessing.

 

[wabe-hk]

Hi,Mr Moriendi
thank you for you reply,
it is all calls from A to B(any digital phone at site b) will diplay "call traced" ，but site B call to site A is OK.
61730 is the phone at site B ,the trace=N
DIS-SBCSU:61730;
H500: AMO SBCSU STARTED
----------------------------- USER DATA ----------------------------------------
STNO =61730 OPT =OPTI COS1 =10 DPLN =0
MAINO =61730 CONN =DIR COS2 =10 ITR =3
PEN =1- 1-103- 0 LCOSV1 =6 COSX =0
INS =Y ASYNCT =500 LCOSV2 =6
SSTNO =ONLYEXT PERMACT = LCOSD1 =1 CBKBMAX =5
TRACE =N EXTBUS = LCOSD2 =1 RCBKB =N
ALARMNO =0 DFSVCANA= SPDI =0 RCBKNA =N
HMUSIC =0 FLASH = SPDC1 = CBKNAMB =Y
PMIDX =0 SPDC2 =
SECR =N DIGNODIS=N DSSTNA =N COMGRP =0
STD =19 CALLOG =ALL DSSTNB =Y TEXTSEL =ENGLISH

REP =0 OPTICOM =N OPTIUSB :0 VPI =
IDCR =N OPTICA = OPTIS0A :0 VCI =
APPM =N OPTIDA = OPTISPA :0 PATTERN =
OPTIUP0E:0 OPTIABA :0
DCFWBUSY=N HEADSET =N APMOBUSR=N APICLASS=
DNIDSP =N HSKEY =NORMAL IPCODEC = SECAPPL =0
DTMFBLK =N IPPASSW =
DTMFCTRD=Y BASICSVC=
DVCFIG =OPTIP500* TSI =1 SPROT = SOPTIDX =
DPROT = DOPTIDX =
FPROT = FOPTIDX =
------------------- ACTIVATION IDENTIFIERS FOR FEATURES ----------------------
HTOS :N DND :N
HTOD :N VCP :Y TWLOGIN :N
HTOF :N CWT :N
------------------- FEATURES AND GROUP MEMBERSHIPS ---------------------------
PUGR :12 ESSTN :
KEYSYS :N NOPTNO :
SRCGRP 1 ) TCLASS : 0
HUNT CD :N
------------------- SUBSCRIBER ATTRIBUTES (AMO SDAT) -------------------------
KN
------------------------------------------------------------------------------
*) OPTIPOINT500

AMO-SBCSU-111 STATION AND S0-BUS CONFIGURATION OF SWITCHING UNIT
DISPLAY COMPLETED;
<

<reg-hista;
REG-HISTA;
H500: AMO HISTA STARTED
ADD-HISTA:10000,ACT;
ACTIVATE-HISTAEACT;
CHANGE-HISTA:STALARM,DEACT;

I regen a new vegas few days ago
How to get the information of : Is any HISTA created for each call?
Could it be that some trace function is turned on in the system that causes this problem? Is there any command to view or turn off all the trace commands currently set or runing in the system?
Thanks again！

 

[Moriendi]

You want an old regen, and a new regen. Compare the two.

You don't want a reg-hista, you need sta-hista.

So if the problem has for sure happened today, then

sta-hista:search,2025-02-10/00:00;

Will list all messages from midnight.

 

[wabe-hk]

Hereafter is 32234 (site A) call to 61730 (site B )
<sta-hista:search,2025-02-10/16:00;
STA-HISTA:SEARCH,2025-02-01/00:00;
H500: AMO HISTA STARTED
H1: 15503 ERROR MESSAGES FOUND

F2750 M8 N7628 MC TRACE BPB MC TRACE 25-02-10 16:39:28
ALARM CLASS:CENTRAL:024
INCOMING PEN:01-04-079-000
STNO INTERN:61730 (site B ) STNO EXTERN:32234 (site A)
FIRST DIVERTING NO:----------------------
LAST DIVERTING NO:----------------------
SERVICE:MCID--
FORMAT:2E

the MC TRACE Function I had setup for long time (may be 5 years) ,it is OK untill few days ago, No other abnormal messages were found

 

[Moriendi]

What's the phone COS and trunk COT look like at the A end ? Malicious call identification appears to be turned off on B side, but still you see it. So let's look at A end. Something is driving this message.

You should check FEASU on B side too. It must be active, you don't want it, you should turn it off.

CHA-FEASU:D,TRACE;

(TRACE = MALICIOUS CALL TRACING)

 

[wabe-hk]

Hi,Moriendi
Thank you very much for your suggestion. Today I went to the customer's site to make some modifications. I cancelled all the TRACE, MCIDA and MCIDM in cossu (CHANGE-COSSU:TYPE=COS,COS=10,DVCE=MCIDA&MCIDM&TRACE;E); and the fault disappeared. I have enabled this function for 5 years since 2020 and have never encountered this problem. It was only a few days ago that the customer reported that this fault was suddenly discovered. Although the fault has been temporarily solved, I still don't understand where the problem is. If it is caused by these parameters, why didn't it happen before? If these parameters have no effect, why did the fault disappear after it was cancelled? The customer asked me to give the specific reason, but I can't analyze it either. I am depressed...

 

[Moriendi]

The parameters do have an effect, they do activate malicious call tracing.
You might have to use the LOGBK AMO to see if anyone switched the phone COS or made any other central config (FEASU).