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

 

You can run powershell commands on your Exchange 2010 server from machines whether or not they have the Exchange Management Tools installed using implicit remoting.

Even when you run the Exchange Management Shell on your exchange server, you’re essentially creating a powershell remoting session. The following steps take place in the background when you click the EMS icon:

  • Load the Microsoft.Exchange.Management.PowerShell.E2010 snap-in gets loaded
  • The RemoteExchange.ps1 script is dot sourced
  • The Connect-ExchangeServer function is executed
  • You can set up implicit remoting from any maching using powershell v2. This imports the commands from your exchange server to your local powershell session so you don’t need any Exchange tools installed.

    First we create a session using the New-PSSession cmdlet:

    $s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<CAS FQDN>/PowerShell/ -Authentication Kerberos

    Then, import the session using the Import-PSSession cmdlet:

    Import-PSSession $s

    The Exchange Management Shell commands are now imported into the local PowerShell session.

    You could use the same method to setup a scheduled task from your machine to run a commands on your exchange server.

    [source: ]

     

    This is perhaps the best tutorial on how to set up Active Directory integration in CentOS.

    http://www.linuxmail.info/active-directory-integration-samba-centos-5/

    Update:
    A related link on setting up Kerberos
    http://www.howtoforge.com/samba_ads_security_mode

     

    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

    © 2012 !NSFW Suffusion theme by Sayontan Sinha