Datasets:
Devilishcode
/
hacking

Dataset card Data Studio Files
xet
Community
text
stringlengths
0
1.99k
ACT : This activates a command in the buffer.
Commands Explained:
Okay, so now we'll go through all of these commands and show you what they
do, and of course, explain each example.
LREP:
LREP lists a number of reports which can be ran. Here is an example:
REP# NAME SYNTAX
---- ---- ------
1 - CURRENT STATUS ACD 1,(FIRST),(LAST),(START),(INT),(#INT),(CLR),(REP)
2 - CUMULATIVE STATUS ACD 2,(FIRST),(LAST),(START),(INT),(#INT),(CLR),(REP)
3 - TRUNK DISPLAY GROUP ACD 3,(FIRST),(LAST),(START),(INT),(#INT),(CLR),(REP)
4 - POSITON PERFORMANCE ACD 4,(FIRST),(LAST),(START),(INT),(#INT),(CLR),(REP)
5 - ABBREVIATED AGENT ACD 5,(FIRST),(LAST),(START),(INT),(#INT),(CLR),(REP)
6 - DAILY PROFILE ACD 6,(FIRST),(LAST),(START),(INT),(#INT),(CLR),(REP)
7 - CUMULATIVE AGENT ACD 7,(FIRST),(LAST),(START),(INT),(#INT),(CLR),(REP)
Current Status : Gives you the current status of the PBX system.
Cumulative Status: Quite obvious.
Trunk Display Grp: Obvious again.
Position Prfrmnce: ???
Abbreviated Agent: ???
Daily Profile : Gives you a report of how the PBX ran on date 00/00/00.
Cumulative Agent : ???
ACD:
I purposely skipped all the other commands, since they are pretty obvious.
They all have to do with adding commands to the buffer, modifying them and
running them..etc. If you get access to a system, it would be wise to LST
all of the commands that the operators have been running and then try them
yourself. No biggy, but oh well. The ACD command activates a command and
lists the desired report on your terminal. While the whole thing can be
typed on one line, you can just type ACD <REPORT NUMBER> <CR> and do it
step by step (a little easier to get the hang of it). Now we'll go through
this, and show you an example of building a command to list the Trunk
Display Report.
?ACD 3
<CTRL-G>FIRST GP OR AGENT ID: (Try 1)
<CTRL-G>LAST GP OR AGENT ID: (Try 2)
START TIME: (Enter START TIME in army time such as 22:52:00)
INTERVAL: (Not sure, hit return)
# OF INTERVALS: (Not sure, hit return)
CLEAR(Y/N): (Type Y, but this is stored in the last cleared log)
REPEAT DAILY?: (No!)
PRINT LAST CLEARED(Y/N): (Here's where the last cleared shows up)
It then prints out the command and executes it, showing you the desired
report.
The end result:
Some other things can be done, such as commands like C and M and a host
of others, but unfortunately, as I said, these systems are very strange
and it's hard to find two alike. The computer is not worthless, and
lots of things can be done on it, but this file is getting quite lengthy.
If there is enough demand, I will write a follow-up. In the meantime, if I
have made any mistakes, or you have more knowledge that you would like to
share with me, I can be reached on the following boards:
ShadowSpawn Private, Hell Phrozen Over, Phantasie Realm and a few others.
-/\-/\-/\-/\-/\-/\-/\-/\-/\-/\-/\-/\-
\ /
/ An Evil Jay/Phrack, Inc. \
\ /
/ Presentation \
\ /
-/\-/\-/\-/\-/\-/\-/\-/\-/\-/\-/\-/\-
==Phrack Inc.==
Volume Two, Issue 12, Phile #8 of 11
BUSY LINE VERIFICATION PART II
WRITTEN BY PHANTOM PHREAKER
This file is meant to be an addition to the first file that was included
in Phrack Inc. Issue XI. It is assumed that the reader has read and understood
the previous file. Most of this information will be taken from Bell System
Publications so you don't have to worry about it being incorrect.
First off, I'd like to correct a minor error included in the first file. I
use the format 'KP+0XX+PRE+SUFF+ST' to show the MF routing that is used. This
is not correct AT&T syntax though, the correct format is KP+0XX+NXX+XXXX+ST.
This is minor detail, but some people are very picky.