Avaya’s IPOffice platform provides a monitor application to troubleshoot all sorts of issues with calls and phones.
A nice reference for IP Office’s Monitor application is hosted at this link.
http://www.oc-stuff.com/mergedProjects/monitor/
Another handy reference when troubleshooting dropped calls are the ISDN cause codes.
http://www.oc-stuff.com/mergedProjects/monitor/htm_cause_codes_(isdn).htm
Everyone knows you can use SSH to tunnel traffic through a remote host running an SSH server. This can allow you to use the web, for instance, as if you were at that remote host. You do this by creating a SOCKS proxy and then setting your local browser to use this proxy.
$ssh -D 8888 username@remotesshserver
This command tells your machine to create a tunnel to the remote ssh server and create a proxy on your local machine at port 8888 for you to use.
Now all you need to do is configure your browser to use this proxy.
Server: localhost or 127.0.0.1
Port: 8888
Although using this proxy through firefox will secure your web traffic, it will not hide your DNS queries. With SOCKS 5 in Firefox you can specify which side of the proxy handles DNS lookups. This can be done by setting network.proxy.socks_remote_dns = true in about:config.
This is high-level overview of an ISDN call.
Call Setup
993697mS ISDNL3Tx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Remote)
Message Type = Setup
InformationElement = BearerCapability
0000 04 03 80 90 a2
InformationElement = CHI
0000 18 03 a9 83 97
InformationElement = CallingPartyNumber
0000 6c 0c 00 80 33 30 33 35 35 35 31 32 30 34
InformationElement = CalledPartyNumber
0000 70 0b 80 37 32 30 34 34 34 35 32 33 37
Call Handling Information
993737mS ISDNL3Rx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Local)
Message Type = CallProceeding
InformationElement = CHI
0000 18 03 a9 83 97= use B channel 23
Phone rings on the other side
993746mS ISDNL3Rx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Local)
Message Type = Alerting
The other side answers the call
1005111mS ISDNL3Rx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Local)
Message Type = Connect
InformationElement = PI
0000 1e 02 81 82
InformationElement = Shift 6
InformationElement = ??(28)
0000 28 0e 31 73 74 20 32 20 77 69 72 73 20 44 43 50
Speech path established
1005112mS ISDNL3Tx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Remote)
Message Type = ConnectAck
Call disconnected
1007058mS ISDNL3Rx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Local)
Message Type = Disconnect
InformationElement =
0000 08 02 81 90=Cause code 90=Normal call clearing
Channel Released by provider
1007059mS ISDNL3Tx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Remote)
Message Type = Release
Channel free for new use
1007077mS ISDNL3Rx: v=0 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0011(Local)
Message Type = ReleaseComplete
Quest Software’s free ActiveRoles Management Shell for Active Directory PS-Snapin simplifies a lot of the AD related functions through Powershell. Following is a list of some commonly used user related actions.
Finding non-expiring passwords
get-QADUser -PasswordNeverExpires
Finding disabled accounts
get-qaduser -disabled
Enabling disabled accounts
enabled-qaduser -identity
The sfc /scannow command (System File Checker) scans the integrity of all protected Windows 7 (XP or Vista as well) system files and replaces incorrect corrupted, changed, or damaged versions with the correct versions if possible.
Running the command requires an elevated command prompt. A log file of the entire operation is created at C:\WINDOWS\LOGS\CBS\CBS.LOG.
The following command extracts the ‘fixes’ from the log and places it in a file called sfcdetails.txt.
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > sfcdetails.txt