Gmail in IP phone

How I achieved this

1st you have to download this file.link

There are just two php scripts to make this work!

idle.php - This is set in the 7961G's configuration file to auto load as the idle screen after the phone is idle for 2 minutes. Basically it just tells the phone to download and display a dynamically generated PNG file.

createpng.php - this script given the 'lc' variable (WeatherZone's Location) will generate the current temp, and two day forecast. I know it's not the most efficient coding - but I am only a casual coder!
Note that I use a font I donwloaded for the big temp text which you can get here: Arial-72.gdf
I don't bother caching the generated image as I only use this service on a single phone - obviously would be worthwile if there were more than the 1 phone uitlisting the service!

weather report to IP phone

I develop that application when I MIT. There's a lot of functionality available in the Cisco 7960/7940 IP phones (and some limited functionality in the 7905s). (Note: Now we're using 7961/7941/7906.) Just scratching the surface so far, I've written a simple weather reporting app in PHP that provides pages for the Idle URL.
this is ur download link
enjoy

Internet Download Manager

hi , this is i cracked one. try it and enjoy.


this is download link..

Rss Feed to cisco phone

Installing RSS feed to cisco ip phone on Your Web Server

Step by step directions on how to install the rss2cisco perl script on your windows or linux based web server.

---

Summary This document will cover in a step by step fashion how to download, install and configure a perl script to display RSS feeds on a Cisco VOIP Telephone's LCD display.

Index

1. Configuring your feeds
2. Windows with IIS Specific Instructions
3. Linux/BSD/OSX/etc with Apache Specific Instructions
4. Setting up the Phone Service in Call Manager
5. Conclusion

---

Configuring your feeds

The first step is to actually download the perl script(download link here link), but if you can't figure that out without a tutorial then this is probably the wrong task for you. Once you have the script downloaded, open it up in the text editor of your choice. Do note that because it uses unix line breaks, Notepad on windows is NOT a good choice. Wordpad, however, will display it fine. As will any application on Linux or BSD/OSX.

Look for the line "ATTENTION: EDIT THE FOLLOWING VARIABLES" and go to the $pathto line below it. Do not disturb or change any other characters on this line and inside the single quotes put the location your script will end up at. Such as: 'http://blog.ginc.co.cc/phone_services' Do NOT put a slash at the end of this line as the script will automatically add one later.

Below that line is where we enter the RSS feeds we want. RSS feed configurations are 2 lines per RSS feed. One line is for the title/description, the other is for the URL that the feed is located at. Copy one of the example feeds and replace everything inside the single quotes on the @descriptions line with the name of the feed. Visit a website you enjoy and find their RSS icon or link. Take the URL to the feed and place it inside the single quotes of the @feeds line, replacing the existing feed URL. Do this as many times as you want, however Cisco IP phones have a limit of 64 menu items, so you can't exceed that.

That completes all the changes you need to make inside the script. Please do not change anything else unless you know what you are doing. Even changing by accident a single character will cause the script to fail and you'll have to start over again. Be mindful of your editing!

Save your changes to the file, rename it to cisco.pl and move along to the next step.

Windows with IIS Specific Instructions

These directions are for users who are running Windows server 2000 or 2003 with Microsoft's IIS web server. Please skip them if this is not your configuration.

• Install IIS using Add/Remove Programs if not already installed. (This is left as an exercise for the reader)
• Download and install the Win32 version of ActivePerl from ActiveState
• Click the Start button, go to All Programs, then ActiveState ActivePerl. Click "Perl Package Manager".
• In the console window type exactly: install XML-RSS
• When the install is complete, type: exit
• Open the IIS management console and connect to the web server
• Click on "Web Service Extensions" and ALLOW "Perl CGI Extension" and "Perl ISAPI Extension"
• Right click on your website (probably "Default Web Site") and click "Properties". Click the "Home Directory" tab.
• Make sure "Execute Permissions" is set to "Scripts and Executables".
• Click the "Configuration" button and make sure the extension .pl is in the list.
• Copy cisco.pl to your website's home folder. (probably C:\inetpub\wwwroot\)

Open Internet Explorer and go to URL that your script now lives at. ie: http://myserver.net/phone/cisco.pl If you see something that looks like this:

You have completed the configuration sucessfully! If you see an error or the text of the script itself, then something went wrong and you should start over.

Linux/BSD/OSX/etc with Apache Specific Instructions

These directions are for users who are running Linux, FreeBSD, OpenBSD, or OSX with the Apache web server. Please skip them if this is not your configuration.

• Install and configure Apache with mod_perl. This is done at install on almost all linux distros, however: (This is left as an exercise for the reader)
• (NOTE: This step must be performed as a super user, such as root) At a shell prompt type: perl -e shell -MCPAN
• In the CPAN perl shell, type: install XML::RSS
• If you see any prompts about prepending dependant modules answer Yes
• When the install is complete type: exit
• Copy/Upload cisco.pl to the folder of your choice in your web server's public folder. Remember to place it in a suitable location for CGI execution
• Note that you may need to rename the file to .cgi if your Apache configuration requires this for execution of CGI scripts.
• Ensure that the proper executable permissions are set for rss2cisco.pl

Open Mozilla Firefox and go to URL that your script now lives at. ie: http://myserver.net/phone/rss2cisco.pl If you see something that looks like this:

You have completed the configuration sucessfully! If you see an error or the text of the script itself, then something went wrong and you should start over.

Setting up the Phone Service in Call Manager

Here's where we log into Call Manager's web admin interface and set up the phone service, then apply it to phones. If you don't know how to get into your Call Manager server's web interface what the hell are you doing here?

• Log into call manager and click the "Feature" menu, then click "Cisco IP Phone Services"
• Click "Add a New Phone Service" (it's a small link in the upper right hand side of the page)
• Enter following...
• Service Name: cisco
• Service Description: RSS Feeds for your Cisco IP Phone
• In the Service URL textbox enter the URL to your script, specifically, the address you used to test it in a web browser in the last step.
• Click Insert

Now the phone service is set up and availble in your Call Manager server. To apply the service to individual phones do the following.

• Click "Device", then click "Phone"
• Using the search, find a phone and display it.
• Click the "Subscribe/Unsubscribe Services" link in the upper right corner.
• Select "rss2cisco" from the drop down list and click "Continue"
• Click "Subscribe"
• Reset the phone to apply the changes.

Conclusion

Now that all your steps are done you should be able to go to your phone, load the service, and display RSS feeds. If not then something has gone wrong and you should review the steps and start again from scratch, checking all your work as you go.

Free Network Monitoring Software

From Tony Bradley, CISSP, MCSE2k, MCSA, A+, for About.com
See More About:

* free software
* free network monitoring
* network monitor

Security Ads
Virus Scan AntiVirus Software AntiVirus Freeware Spyware Software Virus Software
Bandwidth Monitor
Daily, weekly, and monthly information logs * Compatible with all versions of windows * Options and graphs for capped users * Multiple users and selectable adapters * Network and dial-up connections * English, Italian, German, and Russian

FREEping - Server Pinging
Do you want to know if all your Windows 2003-XP-2000-NT servers are alive and pinging? Do you want to receive a pop-up message when one of them is not running anymore? FREEping is a free ping software utility which will ping all your IP addresses in free-definable intervals. FREEping automatically pings in the background and shows statistics for each pinged hosts. When a host stops responding, FREEping can send popup messages to a specified destination.

Look@LAN
Auto-Detect of Network Settings * Scanning of one or more Scan-Ranges * Complete Management of Network Profiles * World's Faster Node Discovery Scan * Automatic and Manual Network Configuration * Network Statistics and Graphs * Profile Export (text and HTML) * Advanced Trapping * Network Log * Network Tree View * Proof Single Node Scan * Reporting

Servers Alive
Servers Alive is an end-to-end network monitor program. Among the many checks it can do: it can monitor any Winsock service, ping a host, check if an NT service/process is running, check the available disk space on a server, retrieve a URL, check your database engine, and more.

Sysinternals CPUMon
Use this advanced tool to read the performance counters of Pentium, Pentium Pro and Pentium II processors. Not for the faint of heart, CPUMon is intended for those with a good familiarity of processor architecture. Version 2.0 is integrated with Perfmon.

Sysinternals DebugView
Another first from Sysinternals: This program intercepts calls made to DbgPrint by device drivers and OutputDebugString made by Win32 programs. It allows for viewing and recording of debug session output on your local machine or across the Internet without an active debugger.

Sysinternals DiskMon
This utility captures all hard disk activity or acts like a software disk activity light in your system tray.

Sysinternals FileMon for Linux
This monitoring tool lets you see all file system activity in real-time. Versions exist for all versions of WinNT/2K, Windows 9x/Me, Windows XP 64-bit Edition, and Linux.

Sysinternals FileMon for Windows
This monitoring tool lets you see all file system activity in real-time. It works on all versions of WinNT/2K/XP, Windows 9x/Me, Windows XP 64-bit Edition, and Linux.

Sysinternals Handle
This handy command-line utility will show you what files are open by which processes, and much more.

Sysinternals ListDLLs
List all the DLLs that are currently loaded, including where they are loaded and their version numbers. Version 2.0 prints the full path names of loaded modules.

Sysinternals NTFSInfo Use NTFSInfo to see detailed information about NTFS volumes, including the size and location of the Master File Table (MFT) and MFT-zone, as well as the sizes of the NTFS meta-data files.

Sysinternals PMon This is an NT Gui/device driver program that watches process and thread creation and deletion, as well as context swaps if running on a multiprocessing or checked kernel.

Sysinternals PortMon Monitor serial and parallel port activity with this advanced monitoring tool. It knows about all standard serial and parallel IOCTLs and even shows you a portion of the data being sent and received. Version 3.x has powerful new UI enhancements and advanced filtering capabilities.

Sysinternals Process Explorer Find out what files, registry keys and other objects processes have open, which DLLs they have loaded, and more. This uniquely powerful utility will even show you who owns each process.

Sysinternals PSTools Suite
The PsTools suite includes command-line utilities for listing the processes running on local or remote computers, running processes remotely, rebooting computers, dumping event logs, and more.

Sysinternals RegMon
This monitoring tool lets you see all Registry activity in real-time. It works on all versions of WinNT/2K, Windows 9x/Me and Windows 64-bit.

Sysinternals TCPView
See all open TCP and UDP endpoints. On Windows NT, 2000 and XP TCPView even displays the name of the process that owns each endpoint. Full source to the command-line version of this tool, netstatp, is included.

Sysinternals TDIMon
See TCP and UDP activity in real-time with this advanced network API monitoring tool.

Sysinternals TokenMon
Watch security-related activity, including logon, logoff, privilege usage, and impersonation with this monitoring tool. Full source code included.

Sysinternals WinObj
The ultimate Object Manager namespace viewer is here. Version 2.0 has significant UI enhancements, knows about more object types, and is integrated with NT's native security editors.

Go To: http://netsecurity.about.com/cs/hackertools/a/aafreenetmon.htm

Top 100 Network Security Tools

After the tremendously successful 2000 and 2003 security tools surveys, Insecure.Org is delighted to release this 2006 survey. I (Fyodor) asked users from the nmap-hackers mailing list to share their favorite tools, and 3,243 people responded. This allowed me to expand the list to 100 tools, and even subdivide them into categories. Anyone in the security field would be well advised to go over the list and investigate tools they are unfamiliar with. I discovered several powerful new tools this way. I also point newbies to this site whenever they write me saying “I don't know where to start”.

Respondents were allowed to list open source or commercial tools on any platform. Commercial tools are noted as such in the list below. No votes for the Nmap Security Scanner were counted because the survey was taken on a Nmap mailing list. This audience also biases the list slightly toward “attack” hacking tools rather than defensive ones.

Each tool is described by one ore more attributes:

Visit to: http://sectools.org

What is 802.1x?

Understanding what the IEEE 802.1x standard is and why you should care means understanding three separate concepts: PPP, EAP and 802.1x itself.

Most people are familiar with PPP - Point-to-Point Protocol. PPP is most commonly used for dial-up Internet access. PPP is also used by some ISPs for DSL and cable modem authentication, in the form of PPP over Ethernet. PPP is part of Layer 2 Tunneling Protocol, a core part of Microsoft's secure remote access solution for Windows 2000 and beyond.

PPP evolved beyond its original use as a dial-up access method and iis now used all over the Internet. One piece of PPP defines an authentication mechanism. With dial-up Internet access, that's the username and password you're used to using. PPP authentication is used to identify the user at the other end of the PPP line before giving them access.

Most enterprises want to do more for security than simply employing usernames and passwords for access, so a new authentication protocol, called the Extensible Authentication Protocol (EAP), was designed. EAP sits inside of PPP's authentication protocol and provides a generalized framework for several different authentication methods. EAP is supposed to head off proprietary authentication systems and let everything from passwords to challenge-response tokens and public-key infrastructure certificates all work smoothly.

With a standardized EAP, interoperability and compatibility of authentication methods becomes simpler. For example, when you dial a remote-access server and use EAP as part of your PPP connection, the RAS doesn't need to know any of the details about your authentication system. Only you and the authentication server have to be coordinated. By supporting EAP authentication a RAS server gets out of the business of acting as middle man, and just packages and repackages EAP packets to hand off to a RADIUS server that will do the actual authentication.

This brings us to the IEEE 802.1x standard, which is simply a standard for passing EAP over a wired or wireless LAN. With 802.1x, you package EAP messages in Ethernet frames and don't use PPP. It's authentication and nothing more. That's desirable in situations in which the rest of PPP isn't needed, where you're using protocols other than TCP/IP, or where the overhead and complexity of using PPP is undesirable.

802.1x uses three terms that you need to know. The user or client that wants to be authenticated is called a supplicant. The actual server doing the authentication, typically a RADIUS server, is called the authentication server. And the device in between, such as a wireless access point, is called the authenticator. One of the key points of 802.1x is that the authenticator can be simple and dumb - all of the brains have to be in the supplicant and the authentication server. This makes 802.1x ideal for wireless access points, which are typically small and have little memory and processing power.

The protocol in 802.1x is called EAP encapsulation over LANs (EAPOL). It is currently defined for Ethernet-like LANs including 802.11 wireless, as well as token ring LANs such as FDDI. EAPOL is not particularly sophisticated. There are a number of modes of operation, but the most common case would look something like this:

The authenticator sends an "EAP-Request/Identity" packet to the supplicant as soon as it detects that the link is active (e.g., the supplicant system has associated with the access point).

1. The supplicant sends an "EAP-Response/Identity" packet to the authenticator, which is then passed on to the authentication (RADIUS) server.
2. The authentication server sends back a challenge to the authenticator, such as with a token password system. The authenticator unpacks this from IP and repackages it into EAPOL and sends it to the supplicant. Different authentication methods will vary this message and the total number of messages. EAP supports client-only authentication and strong mutual authentication. Only strong mutual authentication is considered appropriate for the wireless case.
3. The supplicant responds to the challenge via the authenticator and passes the response onto the authentication server.
4. If the supplicant provides proper identity, the authentication server responds with a success message, which is then passed onto the supplicant. The authenticator now allows access to the LAN- - possibly restricted based on attributes that came back from the authentication server. For example, the authenticator might switch the supplicant to a particular virtual LAN or install a set of firewall rules.

Down and dirty with Wireless LAN security
The 3-year-old Wired Equivalent Privacy (WEP) protocol has been discredited so thoroughly that its authentication and encryption capabilities are not considered sufficient for use in enterprise networks. In response to the WEP fiasco, many wireless LAN vendors have latched onto IEEE 802.1x standard to help authenticate and secure both wireless and wired LANs. The wildcard with 802.1x protocol is interoperability.a particular virtual LAN or install a set of firewall rules.

Down and dirty with Wireless LAN security
The 3-year-old Wired Equivalent Privacy (WEP) protocol has been discredited so thoroughly that its authentication and encryption capabilities are not considered sufficient for use in enterprise networks. In response to the WEP fiasco, many wireless LAN vendors have latched onto IEEE 802.1x standard to help authenticate and secure both wireless and wired LANs. The wildcard with 802.1x protocol is interoperability.

Download PDF:
802.1x Authentication Active Directory.