bad line report

[tooneman]

If somebody flags a bad line on a Hicom 300 how do I list a report that shows the trunk that was flagged as bad. Thanks

 

[donb01]

Yeah.... I just went through that scenario myself - they give you the function and don't tell you how to use it!

What the badln function does is create an entry in the HISTA table. You need to know at least the date the user pressed the button (or transferred to *563) unless you want to search through a bunch of logs. I asked my users to flag the call and then jot down a note of date and approx time.

I use STA-HISTA with type = SEARCHB. Fill in your chosen start and end date and time using the strange format provided (if you enter a ? at the stime prompt it will show you). The hista reoprts will scroll by and you can look for the line erros. It will note the trunk number not by PEN, but by the logical port number of the trunk that you can get from TCSU (I think, if I remember right).

If this doesn't work for you I can probably force an example and then screen capture it for you.

 

[tooneman]

unfortunatly, I am limited to fast path codes. STA-HISTA is not one.I may have to get help from those with better access to PBX. Thanks

 

[tooneman]

I found a password but the command has a few more questions to be answered. Can you help? I've mucked through pretty many but feel I do not have the right combo yet to get bad trunks reported.

<sta-hista

RTYPE = searchhb

M34: VALUE NOT WITHIN ADMISSIBLE RANGE
RTYPE = searchb

STIME = 11 04 18 00 01

ETIME = 11 04 19 11 00

ANS = ?

ANS : ANSWER
CHARACTERISTIC : OPTIONAL
POSSIBLE VALUES : Y FILE OUTPUT
N STOP FILE OUTPUT
C OUTPUT OF ALL FURTHER DATAS
ANS = y

CONTEXT = ?

CONTEXT : SEARCH TYPE
CHARACTERISTIC : OPTIONAL CONDITIONAL
POSSIBLE VALUES : ALARM SEARCH OVER CLASS OF ALARM
FUNCT SEARCH OVER FUNCTION COMPLEX
UA SEARCH OVER USER ADDRESS
CC SEARCH OVER CALLCODE
EC SEARCH OVER EXCEPTION CODE
PRI SEARCH OVER MESSAGE PRIORITY
STNO SEARCH OVER STATION NUMBER
PEN SEARCH OVER HW - INFORMATION
MID SEARCH OVER A/E NUMBER
CONTEXT = ec

EC = ?

EC : EXCEPTION CODE
CHARACTERISTIC : REQUIRED
POSSIBLE VALUES : 1-65534
EC = 1
STA-HISTA:SEARCHB,11 04 18 00 01,11 04 19 11 00,Y,EC,1;
H500: AMO HISTA STARTED
H1: 00000 ERROR MESSAGES FOUND

AMO-HISTA-111 READ HTS HISTORY FILE
START COMPLETED;
<

 

[Iamnothere]

You left out the dashes or colon or whatever the punctuation is between the time components! Use the ? and the Hicom will tell you exactly what to type in the Start and End fields.

 

[tooneman]

Thats not the problem, it wants a space. Its the questions after the date I do not know what to enter for a bad line report. Too many options that do not give me the info I want.

When it asks ANS, what should I answer
When it asks CONTEXT wat should I answer.

I played @ for 30 to get a bad line report but have not hit the right combo. Anybody know it?

 

[donb01]

For ANS if you put Y it will stop after each page and ask you if you want to continue. If you put C it will just keep scrolling and then you can roll back thru the buffer. I prefer C, myself.

When you put in your Y or C for ANS follow that letter immediately with a semicolon ; and then press enter. The semicolon means "skip all the rest of the optional stuff" I believe search type, start date, end date, and ANS are the only things required. Then you will get all the fault messages.

 

[tooneman]

Ahah, I am getting some where now. Thanks donb01!