The Basics

[alyas404]

I am new to PABX config, but as I live in a remote area have been given the task of learning all I can. So far I have found this site invaluable. Absolutly amazing!!
I'm only using telnet as I have found the omni software fairly irritating.
I am finding alot of detailed answers to complex problems here, however, I am struggling to find here there or anywhere all the basic info, such as;
*Full list of telnet commands
*List of out of service cause meanings
*list of shortcuts on the handsets (such as #05 to logout)

Basically lists of commands for everything telnet is what im after here.
If anyone could either point to a thread where this has already been addressed or list these here I would be eternally grateful, I have already started my own file with everything I have found so far but it is very short, a little messy and most of it has been pieced together from this site anyway, so I'm not really after bits and pieces and odd commands, im after complete lists.

[Eliott_DUP]

*Full list of telnet commands
Not available.
Try help and choose 16

*List of out of service cause meanings
There is a list below listerm or listout output

Code: Select all

 | (A: att_mserv|S: hs smooth), C: hs_defich, I: hs_isolauto, X: hs_isolman|
 | T: hs_terdef U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol|    

*list of shortcuts on the handsets (such as #05 to logout)
There is no default.
You have to make your own list using the prefix plan.

[tincho.rn]

Hi. I think about #05, you are talking about call center features. Check numbering plan and confirm if #0 is ACD prefix. If so:
1 - withdrawal
2 - wrap-up
5 - logout
6 - login
Regards.

[alyas404]

une) je nais parle francais, so I dont really know what the codes mean in real terms of troubleshooting
deux) for the #05, in my organisation I can walk up to any handset, press #05 then the phone will say 'enter your personal code' and then say 'your request has been granted', next time I pick up the handset it will ask 'please enter your own extention' then again will ask for the personal code to log in, I would like to know what others there are or if this is programable, if so how? also I was once shown a code that was something like #53 (I dont remember what but do remember this was invaluable as it displayed the terminal extention, so I didnt have to keep calling the switchboard to find out what number I was on....)

[Eliott_DUP]

Why french?!

Code: Select all

HELP

- Hardware maintenance    :  1
- Resources's status      :  2
- Network maintenance     :  3
- Incidents               :  4
- Duplication             :  5
- DECT                    :  6
- Data base               :  7
- Accounting              :  8
- Voice guides, tones     :  9
- System                  : 10
- Application             : 11
- Entities                : 12
- Explaining problems     : 13
- ACD v2 maintenance      : 14
- Remote extension        : 15

- List of commands        : 16
q - quit

Your choice [1-16]: 16

Here is the list of specific commands usable by all users:
- cpu_ready : <description to be filled>
- listtool : list of specific commands
- mnt4615 : A4615 maintenance tool
- rst4615 : reset A4615 VMU
- scpu : send message to CPU
- simdeport : Equipment replacement or visualisation
- simtrace : Redirection of messages from the cpu to a coupler
- tcyc : all cyclical test activation
- domstat : Display Domain Info
- intipstat : Int Ip Information
- ippsim : PCMM2 Simulation Mode
Here is the list of specific commands usable by mtcl:
- abcchain : check notification and facilities chainage
- acdhtml : Make html file for acd
- acdsup : Display acd configuration
- acrlist : Send a message to the associated node and wait for the answer
- actdbg : active traces for debug
- agacd : Display agent parameters
- agfsb : Display agent parameters for forseeable wait
- alarmrel : alarm relay:change state, incidents, info
- antdiv : correct antenna diversity field in DB and remanents
- asn1chain : check asn1 chainage
- attag : List of attached agent in a processing group
- autor2 : internal datas of R2
- aux4600 : Q23 detector state of a 4600 rack
- aux5400 : Q23 detector state of a 5400 rack
- bascul : switch over on the twin CPU
- bbc2stat : Statistics on BBC2 boards
- bckdebug : Call Server : Back up signaling link information
- boardinfo : Display board info
- call_ident : data of busy trunk and it's peer
- callbstat : internal datas of call back service
- calledfilt : List of called filtering parameter
- callprof : call profile
- ccdcom : Display ccd application number
- ccdn : CCDn Routage
- ccstat : call completion internal datas
- cdtstat : <description to be filled>
- cfnstat : Display meet me conference structure
- cmdcpl : toolbox for IP boards
- cnx : <description to be filled>
- cnx_eqt : for agreement:forces connexion
- code_debug : active code of debug
- compvisu : compression tool
- config : all coupler's status
- config_gsm : GSM notification configuration
- configold : coupler's status before last save of ops files
- country_code : Country codes
- cpl_online : online debug of standard couplers
........

[alyas404]

alcatels a french company right? hence all this:-
| (A: att_mserv|S: hs smooth), C: hs_defich, I: hs_isolauto, X: hs_isolman|
| T: hs_terdef U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol|
is french right? (my french is terrible)
I REALLY appreciate the screen dump, on my system the commands list is option 18.... so I was pressing 16 and getting something completely different... my bad
but now I can get the specific commands for my system so thats awesome.
Thank you so much
If anyone else has anything else to contribute please do

[alyas404]

one other thing that seems kind of basic that I cant work out is how to pipe/redirect info from the dos prompt to a .txt
I want to get a list of all the addresses that are in use but out of service so I can work out which hotel room fones are out of service, and also so I can claim back some extentions that are logged in but not in use as we are running out(so a pbx tech who we had fly down told me), if I search for extentions under
users
descend
all instances
filters = shelf/board/location
all set to 255

I only have about 30 left to play with

[Eliott_DUP]

is french right?

No. But a mix.

My interpretation:
The most important is A = Generally out of service
and T = Terminal or wire problem.
B is the marker on the Backup/Standby CPU.
I is automatic isolated e.g. there is no set managed on this port
X is manual isolated e.g. command outserv
S is similar to X manual outserv but smooth (e.g. command outserv on a T2 access with smooth option)
There is also a N (seen for DSP channels)

I've seen C U P Y in some systems but I don't know the exact meaning.
I guess Y and U is something with the board/ACT and P with the parity for transmissions

In R8.0 is 16 MIPT info (Mobile IP Touch) and 18 the command list, right.

[zanex]

T = Terminal or wire problem.

From experience i have always thought that this is when a fault has occured since last reset/termstat or when the set is disconnected

[pemby_DUP]

Found this in some old (release 1.4) doco. it explains the meanings in the *stat commands (termstat, eqstat etc)
A: waiting for activation, station declared into MAO but never connected
I: automatin isolation, the terminal is isolated due to an anomaly recognised by the CPU
X: manual isolation, the terminal is isolated by the operator
P: error of parity, the terminal is out-of-time, it induces an automatic isolation
U: the signalling unit is unplugged
C: the board of the terminal concerned is unplugged
T: Station unplugged, miscall for analogue stations
B: the erminal is out of service afther the CPU switching

dont know that is really clears anything up but his is th only reference i have ever found to the actual meanings of the letters