trace of hipath4000 1

[bitapn]

hi all.
I want to trace hipath 4000 version 6.
would you please tell me the step by step procedure of tracing the system?

 

[sbcsu]

Hi,
What do you need to trace and why ?
To what level do you need to trace ?
Is it just for information or for support

 

[bitapn]

I want to trance calls and trunks.
I need it for troubleshooting now but I want to learn it completely.
is there a specific application for it?

 

[sbcsu]

There are multiple traces and ways of tracing depending on what is required.

For easy starting at general level
Go to Assistant - 192.0.2.5
Ensure your PC has gone through 'client preparation' otherwise the Java trace display will not work.
Log on to the Assistant.
Check in Base Administration/Application Control that 'Real Time Diagnosis System' has been enabled- if not enabled then click it to enable it.
Go back to the main page of Assistant - if you had to enable the 'Real Time Diagnosis System' then refresh the main page (F5)
Click on Diagnostics/Switch Diagnosis Support / Real Time Diagnosis System.
Click on Monitor Trunk/Line/Data Line/ISDN Trace
Log on there just by putting in your Initials in 'User Name' and click 'Logon'
Follow any Java prompts to click on screen etc.
Click again on Monitor Trunk/Line/Data Line/ISDN Trace on Left hand side
If nothing shows then you need to allow 'popups' in your browser.
In the Station/PEN put in an extension number or a Port Equipment Number (PEN)
and click on type - if it is a trunk use Trunk Monitor etc.
To see the status of the trace click then on Monitor Display or ISDN Trace Display on the bottom to see the tracing in real time.
To save resources ensure you 'Stop All' when finished and 'Shutdown RDS' then close all relevant windows.

This is not Call Detail Recording - CDR
You can not keep these traces
This is elementary tracing - nothing fancy

 

[bitapn]

many thanks dear sbcsu.
the real problem is I have registered some HFA and some SIP phones.
the HFA phones call dial HFA numbers.
the sip phones can not dial neither HFA phones nor sip phones.
the HFA phones can not dial sip phones too.
for example,4007 is a sip phone and 4006 is a HFA one. I first dial 4007(SIP) by using 4006(HFA) and then I dialed 4006(HFA) by using 4007(sip) and I got the attached result

 

[sbcsu]

CHA-ZAND:OPTLOAD;
and test again.

 

[bitapn]

done.
still no effect.

 

[sbcsu]

Show the trace again please - the attached is just your C:\ Drive

 

[bitapn]

please find it in the attached file.

 

[donb01]

I don't know if it matters, but the difference between my HFA station COS and my SIP station COS is that SIP has the additional 2 values. I don't know if that makes any difference, but does the COS you are assigning to yours have them in?

| | UUS1IM | | |
| | UUS3 | | |
+------+-----------------+

I'm also using SIPSEC for the connection type and SOPP for the device combination (in Assistant).

Just throwing a couple things out there. I use the same LCRV settings for the SIP phones as for the HFA ones.

 

[sbcsu]

Hi,
Using Comwin/Expert access
Please
REG-SBCSU:4007;
also
DIS-SBCSU:4007;
and paste here
Thanks

 

[bitapn]

actually I always use the same class of service for both HFA and SIP phone and there was no problem. this is the first time that I face it.
please fine the result of AMO reg-sbcsu and dis-sbcsu below:


ADD-SBCSU:4006,OPTI,IP2,1-1-49-1,OPTIIP,1,5,5,1,1,1,1,0,0,N,0,0,,,N,0,0,N,,,Y,0,
N,N,N,Y,N,,,,,,,,5,,,,N,NORMAL,Y,ENGLISH,0,ALL,,0,,,,,,,,,G711P,,;





ADD-SBCSU:4007,FPP,SIP,1-1-49-33,S0PP,5,5,1,1,1,1,0,0,N,0,0,,,"SBDSS1",Y,Y,0,10,
N,N,,,5,0,,,,"8Gp7M","4007","4007",,,,;






USER DATA ----------------------------------------
STNO =4006 OPT =OPTI COS1 =5 DPLN =0
MAINO =4006 CONN =IP2 COS2 =5 ITR =0
PEN =1- 1- 49- 1 LCOSV1 =1 COSX =0
INS =Y ASYNCT =500 LCOSV2 =1
SSTNO =N 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 =0 CALLOG =ALL DSSTNB =Y TEXTSEL =ENGLISH

REP =0 OPTICOM =N OPTIUSB : VPI =
IDCR =N OPTICA = OPTIS0A :0 VCI =
APPM = OPTIDA = OPTISPA :0 PATTERN =
BLF =N OPTIUP0E:0 OPTIABA :0

DCFWBUSY=N HEADSET =N APMOBUSR=N APICLASS=
DNIDSP =N HSKEY =NORMAL IPCODEC =G711P SECAPPL =0
DTMFBLK =N IPPASSW =
DTMFCTRD=N BASICSVC=
DVCFIG =OPTIIP * TSI =1 SPROT = SOPTIDX =
DPROT = DOPTIDX =
FPROT = FOPTIDX =
------------------- MOBILE HFA STATE -----------------------------------------
IP PHONE INACTIVE :N
------------------- ACTIVATION IDENTIFIERS FOR FEATURES ----------------------
HTOS :N DND :N
HTOD :N VCP :Y TWLOGIN :N
HTOF :N CWT :N
------------------- FEATURES AND GROUP MEMBERSHIPS ---------------------------
PUGR : ESSTN :
KEYSYS :N NOPTNO :
SRCGRP 1 ) TCLASS : 0
HUNT CD :N
------------------- SUBSCRIBER ATTRIBUTES (AMO SDAT) -------------------------
NONE
------------------------------------------------------------------------------
*) OPENSTAGE





USER DATA ----------------------------------------
STNO =4007 OPT =FPP COS1 =5 DPLN =0
MAINO =4007 CONN =SIP COS2 =5 ITR =0
PEN =1- 1- 49- 33 LCOSV1 =1 COSX =0
INS =Y ASYNCT = LCOSV2 =1
SSTNO =N PERMACT =Y LCOSD1 =1 CBKBMAX =5
TRACE =N EXTBUS = LCOSD2 =1 RCBKB =N
ALARMNO =0 DFSVCANA= SPDI =0 RCBKNA =N
HMUSIC =0 FLASH = SPDC1 = CBKNAMB =
PMIDX =0 SPDC2 =
DVCFIG =S0PP LWPAR = PROT =SBDSS1 OPTIDX =10
SMGSUB =N IPCODEC =G723P USERID ="4007"
FIXEDIP =N AUTHREQ =N PASSWD =*****
IPADDR =0.0.0.0 SECZONE ="4007"
DTMFCTRD=N
------------------- ACTIVATION IDENTIFIERS FOR FEATURES ----------------------
HTOS :N DND :N
HTOD :N VCP :N TWLOGIN :
HTOF :N CWT :N
------------------- FEATURES AND GROUP MEMBERSHIPS ---------------------------
PUGR : ESSTN :
KEYSYS : NOPTNO :
SRCGRP 1 ) TCLASS : 0
HUNT CD :N
------------------- SUBSCRIBER ATTRIBUTES (AMO SDAT) -------------------------
MBCHL
------------------------------------------------------------------------------

 

[sbcsu]

Delete the SIP extension
DEL-SBCSU:4007,ALL;
Then add it back in as follows:
ADD-SBCSU:4007,FPP,SIP,1-1-49-33,S0PP,5,1,1,1,1,1,0,0,N,0,30,0,,SBDSS1,Y,Y,0,10,N,N,,,5,0,1,G711;

See if you can register the phone from either a hardware phone or from a software phone like zoiper or similar.
Use 4007 as the extension and then use the IP address of the card
example
Register
4007@192.168.1.1

 

[bitapn]

I could solve the issue by using the AMO copy-prode.
but could you please inform me other ways of tracing or any application or document?

 

[sbcsu]

The AMO Prode is the 'Protocol Descriptor' which defines default protocols for ISDN and other Protocols for your Territory/Country.
The other ways of tracing are beyond the scope of this forum - If you have issues now with setting up 2 extensions then tracing as you have done will only show you where the call is failing - not how to solve it.

Have you set the SIP extension as above ? - can you use that extension by installing a SIP program like zoiper or similar from your PC on the STMI Card network ?

 

[GZgidnick]

Even if you get the trace, TRACE 2, TRACE 3, whithor without additonal flags, which is done via AMO, you will still need proper decoder to get the info in human readable form. Those apps used for translation are either the Message Doctor used by the European HiPath techs or TraceEx used by the US hipath techs. And even if you get the trace in human readable form you will still need to use calculator for some HEX to Decimal conversion. Also, provided you have advanced protocol knowledge, without someone spending few months with you explaining the bits and pieces of those traces you will hardly make use of them on your own.

If you stil want to learn how to make teaces let me know and I'll provide you tge AMO's

 

[bitapn]

many thanks for your reply.
I really need it.would you please provide me with the step by step procedure because i am new ti Hipath 4000?

 

[GZgidnick]

Okay here we go...

1. TRACE 2 + ACL
CHA-DIAGS:COMP=CP2,S04=ON;
Plase this line in order to track forwarding issue before other lines of the trace
_____________________________________________

CHA-DIAGS:COMP=CP,S14=ON;
CHA-DIAGS:COMP=DH,S03=OFF;
CHA-DIAGS:COMP=DB,S03=OFF;
EXEC-TRACS:BP;
RES,ALL;
RST,OFF;
FLAGTR,OFF;
SELMSG,RCV,G1,CD1,DEST,40;
SELMSG,RCV,G1,CD2,SRC,40,NE;
MSGLEN,RCV,G1,64;
SELMSG,PP,G1,CD1,BYTE,4,BA&97;
SELMSG,PP,G1,CD2,BYTE,15,8;
MSGLEN,PP,G1,288;
SELMSG,PP,G2,CD1,BYTE,4,B8;
MSGLEN,PP,G2,500;
SELMSG,PP,G3,ALL;
MSGLEN,PP,G3,128;
SELMSG,CP,G1,CD1,BYTE,4,9B&CD&EF;
MSGLEN,CP,G1,500;
SELMSG,CP,G2,ALL;
MSGLEN,CP,G2,128;
SELMSG,SD,G1,CD1,BYTE,0,08;
MSGLEN,SD,G1,1024;
USER,"TAC TRACE2ACL";

on,hd,:diag:NAME,200,y,y;


2. Trace 2 clean
CHA-DIAGS:COMP=CP2,S04=ON; (FORWARDING SWITCH)

cha-diags:comp=cp,s14=on;
ex-tracs:bp;
res,all;
flagtr,off;

selmsg,pp,g1,cd1,ev,ba&97&74;
selmsg,pp,g1,cd2,byte,15,08;
msglen,pp,g1,280;
selmsg,pp,g2,all;
msglen,pp,g2,32;
selmsg,cp,g2,all;
msglen,cp,g2,48;
selmsg,rcv,g1,cd1,dest,40;
selmsg,rcv,g1,cd2,src,40,ne;


on,hd,:diag:CLEAN,200,y,y;



3. Trace 2 + MTS
CHA-DIAGS:COMP=CP,S14=ON;
CHA-DIAGS:COMP=DH,S03=ON;
CHA-DIAGS:COMP=DB,S03=OFF;
EXEC-TRACS:BP;
RES,ALL;
RST,OFF;
FLAGTR,OFF;
SELMSG,RCV,G1,CD1,DEST,40;
SELMSG,RCV,G1,CD2,SRC,40,NE;
MSGLEN,RCV,G1,64;
SELMSG,PP,G1,CD1,BYTE,4,BA&97;
SELMSG,PP,G1,CD2,BYTE,15,8;
MSGLEN,PP,G1,288;
SELMSG,PP,G2,CD1,BYTE,4,B8;
MSGLEN,PP,G2,500;
SELMSG,PP,G3,ALL;
MSGLEN,PP,G3,128;
SELMSG,CP,G1,CD1,BYTE,4,9B&CD&EF;
MSGLEN,CP,G1,500;
SELMSG,CP,G2,ALL;
MSGLEN,CP,G2,128;
USER,"TAC TRACE2";

on,hd,:diag:NAME,200,y,y;



4. Trace 2 with stop condition on seizure:
CHA-DIAGS:COMP=CP,S14=ON;
CHA-DIAGS:COMP=DH,S03=OFF;
CHA-DIAGS:COMP=DB,S03=OFF;
EXEC-TRACS:BP;
RES,ALL;
RST,OFF;
FLAGTR,OFF;
SELMSG,RCV,G1,CD1,DEST,40;
SELMSG,RCV,G1,CD2,SRC,40,NE;
MSGLEN,RCV,G1,64;
SELMSG,PP,G1,CD1,BYTE,4,BA&97;
SELMSG,PP,G1,CD2,BYTE,15,8;
MSGLEN,PP,G1,288;
SELMSG,PP,G2,CD1,BYTE,4,B8;
MSGLEN,PP,G2,500;
SELMSG,PP,G3,ALL;
MSGLEN,PP,G3,128;
SELMSG,CP,G1,CD1,BYTE,4,9B&CD&EF;
MSGLEN,CP,G1,500;
SELMSG,CP,G2,ALL;
MSGLEN,CP,G2,128;

selmsg,stop,g1,cd1,dest,6c;
selmsg,stop,g1,cd2,src,6c;
selmsg,stop,g1,cd3,ev,04;
selmsg,stop,g1,cd4,byte,06,xx;
selmsg,stop,g1,cd5,byte,07,yy;

xx: byte 06 is the low byte from exec-disps of the stop number
yy: byte 07 is the high byte from exec-disps of the stop number

on,hd,":diag:2648340",500,y,y;


As I said, without using Message Doctor or Mike's Bishop-Jones TraceEx.exe you won't be able to make much sense of the output is it comes in HEX