Archive for the ‘Uncategorized’ Category

Configure TFTP Option 66 and Option 150 with dhcpd

Friday, November 6th, 2009

Here is a copy of the top portion of my /etc/dhcpd.conf file. Using this configuration you should be able to setup any TFTP bootable device to look to your TFTP server for configuration files. For example Cisco 79xx series phones, or SPA5xx series phones.

option tftp150 code 150 = string;
option tftp66 code 66 = string;
option tftp150 code 150 = string;
option tftp66 code 66 = string;
DHCPARGS=eth1;
subnet 192.168.1.0 netmask 255.255.255.0
{
option routers                  192.168.1.1;
option subnet-mask              255.255.255.0;
option domain-name-servers      192.168.1.1,;
option tftp150                  ”192.168.1.1″;
option tftp66                   “192.168.1.1″;
range 192.168.1.10 192.168.1.150;
}

Cisco SmartNET Contract for Cisco 7940, 7941, 7960, 7961, 7970, 7971

Wednesday, November 4th, 2009

We now provide expedited SmartNET agreements for all Cisco Devices! Your quoted price will be for the Basic One-Year SmartNET agreement unless you specify a different service level in the notes section. All payments are processed via Google Checkout which means we never see your credit card information. If you have had problems in the past with your device having an “invalid serial number” according to cisco use this form here. These agreements are necessary to obtain the firmware for Cisco 79xx series phones.

You’re information will not be reused or sold. All personal information and device information will be kept strictly confidential.

When we say all fields are required, we mean it, Cisco needs them all.

If you require several devices please provide us the below information in an E-Mail to smartnetATgreenwireit.com

All Fields except Cisco CCO and Notes are required.

Your Name

Your Email

Contact Phone Number

Address

City

State/Province

Zip or Postal Code

Country

Cisco Device Model

Cisco Device Serial

Cisco.com Username (CCO)

Notes/Comments

captcha

Prolific PL-2303 driver Device Cannot Start Windows Vista 64bit and Windows 7

Wednesday, October 7th, 2009

I’ve had this problem a couple times and the solution seems to be slightly different each time.  The problem presents itself as a Device in Device Manager showing “”The Device Cannot Start (Code 10)” after you’ve installed the Prolific PL-2303 Drivers from the Prolific website. Which are available here: http://www.prolific.com.tw/eng/downloads.asp?ID=31

The solution is to use a similar driver set floating around on the internet here: http://www.usglobalsat.com/download/546/win_drivers.zip

Unzip the file and install the executable within. That fix solved the problem for me instantly. To make sure that the new driver take priority over the other one in Windows 7 right click on the device and go to Unistall and check “Delete the driver software for this device”. I found this solution on the microsoft social forums here.

Howto BLF (Busy Lamp Field), SLA (Shared Line Appearance), on the Linksys SPA942, SPA962 and Cisco SPA525G

Wednesday, September 30th, 2009

I’m sure by now you’ve read a few articles saying that you CANNOT do BLF on the SPA942, SPA962 or SPA525G, this is in fact false. BLF works JUST fine on these phones. In fact I have a wall behind me with all three models connected together with Asterisk (elastix) merrily reading each others line states. The red lights are extensions demonstrate extensions in use.

For those of you who do not know what BLF is. BLF or Busy Lamp Field allows you to see which extensions are currently on the phone, or being called. It also allows you to pickup a ringing phone for someone else.

By placing these same configuration details into the SPA932 screen you could also use these instructions to programme a Linksys SPA932 Sidecar.

See, it works!

See, it works!

I’m sure by now you’re jealous of all my little red lights blinking away. Well, fortunately for you the next part of this guide is how you can do it on your own phones. I’m going to break this down into four sections: Configuration in common to all three models, and then three separate sections for configuration elements unique to each phone.

Before Using this Guide Make sure you have the Latest Firmware from Linksys / Cisco

This is NECESSARY

General:

First things first, here is what is more or less common to every model. To do anything you need to log into the phone. To do this you need to get the IP Address of the phone. You can either get it from your endpoint manager or by hitting the settings button, then pressing 9.

Once you’re logged into the phone, we need to log in and switched to advanced.

Admin Login BEFORE you Clicked Advanced

Admin Login BEFORE you Clicked Advanced

On the right hand side you’ll see “Admin Login”, once you’ve done that and it’s switched to “User Login”. Go ahead and hit “Advanced”. Do it in that order else it’ll go ahead and switch back to basic mode and you won’t see the options we need. The SPA525G has a slightly differently looking screen but it’s phrased identically.

Next we’re going to setup the actual BLF and shortcut lines. This step is identical on all the phones so we’ll do it first.

Line Keys Configured for BLF on Sipura Phones

Line Keys Configured for BLF on Sipura Phones

Click on the “Phone Tab” on the menu bar up top. Double check that you’re in Advanced Mode and you should see the Line Keys. I typically leave Line Key 1 configured as a normal extension. This means that the phone will be able to handle two simultaneous calls. If you need four simultaneous calls assign Line Key 2 as well to Extension 1.

For the lines that will require BLF Switch the Extension to Disabled, switch the Share Call Appearance to shared. Enter a short name for the line, this is the name that will show up on the button on the screen.

Once you have that you’ll need to enter the following into the extended function section:

fnc=blf+sd+cp;sub=EXT#@ASTERISKIP;nme=SHORTNAMEHERE

Replace EXT# with the Extension number of the phone you would like to monitor, ASTERISKIP with the IP of the Asterisk server that both phones are connected to and SHORTNAMEHERE with the shortname entered above.

You may fill out as many lines as necessary using this same command. The same syntax is used on the SPA942, SPA962 and SPA525G.

There is one additional step necessary to get BLF working. You must now tell the phone that you want it to use Asterisk style BLF.

Save your settings and move on to the next phone-specific section.

SPA942 Specific Instructions:

While you’re on the Phone Tab, You need to scroll down directly below the last Line Key (should be Line Key 4). You’ll see Line Key Extended Function.

Directly Below the Line Keys on the Phone Tab

Directly Below the Line Keys on the Phone Tab

Here you must switch the Server Type: to Asterisk, and changed the SPA932 Call Pickup Code to *8 to match the Asterisk call pickup code.

That’s it, save your settings and you’re done.

SPA962 Specific Instructions:

On the SPA962 the setting is located under the SPA932 tab (that’s the model name of the sidecar for the SPA962 and SPA525G).

Click on the SPA932 Tab

Click on the SPA932 Tab

Once you’ve clicked on the SPA932 tab you should get this:

Changing the BLF Settings on the SPA932 Tab

Changing the BLF Settings on the SPA932 Tab

If you don’t see this, make sure you’re in advanced mode and logged in as admin (Admin Login button). If you do see this, switch Server Type to Asterisk and SPA932 Call Pickup Code to *8.

Save you’re settings and you’re done!

SPA525G Specific Instructions:

On the SPA962 the setting is located under the Att Console tab (this tab is intended to work with the SPA932 which is the Sidecar for the SPA962 and SPA525G).

Click on the SPA932 Tab

Click on the SPA932 Tab

If you don’t see this, make sure you’re logged in as admin and in advanced mode. Once you see the below dialog we’re ready to change a couple settings for Asterisk:

Change the Att Console Settings for Asterisk

Changing the BLF Settings on the Att Console Tab

Switch the Server Type: to Asterisk and change the Attendant Console Call Pickup Code to *8.

Save your settings and you’re done.

Testing the ‘Hard drive in the Freezer’ Trick

Wednesday, July 15th, 2009

I have a customer with a dead drive. Although occasionally it seems like it will work for a few minutes. It’ll be the intent of this article to test the hard-drive in freezer trick for this clicking and decrepit drive. Let’s see if it works!

Update 1:

It’s in a zip-back in the freezer! Let’s see what happens!

Update 2:

Pulled out of freezer, plugged in and…. WORKS! Holy hell it actually…oh wait it stopped working.

Conclusion:

I was going to write a complete right up about this, before I tested it and more or less got disappointed results. I was amazed that I was almost to boot windows before the drive fell back into senility. So there is definitely some truth to this but your mileage is definitely going to vary.

This guy here wrote a really snazzy write up: http://geeksaresexy.blogspot.com/2006/01/freeze-your-hard-drive-to-recover-data.html

Complete Guide to Install Windows 7 on the eee PC 1000 series (Drivers, ACPI and All)

Tuesday, June 16th, 2009

I saw a few incomplete guides out there, including the one that I used to install Windows 7 on my eee PC 1000. I figured this would be a good time to make a guide specifically for you in the same situation as I was. This guide will tell you how to acquire Windows 7, prepare a flash drive to install Windows 7, and to acquire the neccessary drivers after installation is finished.

Step 1. Acquire Windows 7.

Your Free for One Year Windows 7 Key and Release Client DVD-ISO can be downloaded from here:

http://www.microsoft.com/windows/windows-7/download.aspx

The N270 ATOM processor does not support x86_64 (amd64) extensions, so you’re going to want to grab the 32bit version.

Step 2. Prepare your Flash Drive.

I would recommend a 4GB drive, as the Windows DVD ISO is 2.35GB

First we’re going to open up diskpart to prepare the Flash Disk.

  • Open command prompt. (Start > Run > cmd)
  • At command prompt open diskpart (type diskpart then press enter)
  • Next run the “list disk” command to get a view of the available devices connected to the machine.
  • Now run select disk # where # is the number associated with your flash drive.
  • Type “clean” to wipe the partition table
  • Now type “create partition primary”, which will create a new partition
  • Then type “active”, this will mark the partition bootable
  • Next we will format the drive with the command “FORMAT fs=ntfs” you could also use FAT32 but I prefer NTFS. You can also add “quick” after NTFS to perform a quick format.
  • Finally type “assign” to have windows assign the drive a mount point.
  • Type “quit” to leave bootpart.
  • You should now be back at command prompt.
  • We now need to insert or mount the Windows 7 drive. Either burn the image to a disk or use a ISO mounting tool to mount the disk image. Once you have the image loaded in one way or another we’re going to run a file on the disk.
  • Type the drive letter of the drive i.e. “i:” or “d:”
  • Then type “cd boot”
  • Bow run “bootsect /nt60 driveletterhere” wheras driveletterhere is the drive letter of your flash drive.
  • Now your flash drive is prepared for the Windows 7 files. Copy the entire contents of the Windows 7 disk to the flash drive.

Step 3: Install Windows 7

The installation is actually remarkably straight forward. A lot of guides will tell you you have to run compact on the drive. Fortunately, most eee PC users have a 8GB OS drive and another drive for files. The end installation will leave you with around 1GB of free space on the OS SSD. So running compact is not neccesary if you do not want to.

  • Make sure all of your files are backed up
  • Reboot the eee PC
  • Insert the Flash Drive
  • While the POST screen is showing tap the ESC key
  • From the boot menu select your USB Flash Drive
  • Windows 7 installation should now start as normal.
  • You should format the 8GB OS SSD during the installation, this way it does not install Windows 7 and leave your existing files alone. On the eee PCs with hard drives that may be fine but on the standard eee PC that would result in barely any free space.

Step 4: Drivers and Optimisation

Drivers

Windows 7 actually detects more hardware directly after install than Windows XP does. All of the hardware detects normally except the ASUS ACPI driver. It will detect in Device Manager as an “Unknown Device”. The Device ID is ACPI\ASUS010. This device also controls the eee PC specific hotkeys. For example the ability to turn off the Bluetooth and WiFi radios from within windows.

The ACPI Drivers and other Drivers are available on the ASUS Support website. Select your eee PC from the list, then download the ACPI drivers from underneath the “ATK” category.

You’ll get occasional popups saying that certain keys have been disabled from the utility. You can End the Process to end these messages, but you’ll also loose access to some function keys.

I’ve so far been able to get the the ACPI utility to stop complaining about the Intel Utility. I did this by downloading the Windows Vista 32bit Driver from the Intel Website. It’s the Intel 945GM Chipset that the eee PC 1000 uses. You’ll have to use the “Have Disk” method of overriding Windows 7. Since technically the Win7 driver is newer you’ll have to insist on using the older Windows Vista driver. Once the driver installs, for me I got a blank screen and I had to hard reboot. Once the computer rebooted I got one less annoying error from the ACPI utility. I believe you could use a similar process with the other drivers to satify the ASUS utility. I’ll update as I learn more.

Optimisation

I recommend you enable the “Windows Classic” theme, and go through the Windows Services panel to disable whatever Services you may not need.

I also recommend you right click on the Taskbar and use the properties section to shrink the toolbar. Although it might be perfect for a modern Hi-Res screen the New Windows 7 toolbar is a bit big for an eee PC.

Step 5: Update your Firmware on your eee PC 1000 (Optional)

Download the “ASUS Update Utility” under the Utilities Section on the ASUS Website. Extract it and install it. Use the MSI installer instead of the EXE, because the EXE will give you an error message about the version of windows not being correct. Once installed the ASUS Update Utility will download and install the latest Firmware version for your eeePC BIOS.

Mosaica: Image Stiching for iPhone!

Monday, June 8th, 2009

Two of my good friends from UCF have recently wrote a wonderful new App for iPhone. Brandyn White and Andrew Miller of Dappervision, Inc. have put together a really neat app called Mosaica. The app allows you to take a number of pictures, and the iPhone will take them and fuse them together to form a large Mosaic of the smaller pictures. Although image stitching technology is nothing new I have to say the way it’s handled on the iPhone with Mosaica is absolutely ingenious. It’s really intuitive, remarkably fast, and really fun. I find myself making Mosaics to compensate for the rather low-resolution of the iPhone Camera. They have a few videos posted up on the website, as well as community site to allow you to share Mosaics. I would have to say one of the neatest things is that the app allows you to take close-ups of things within a Mosaic. For example, take a broad photo of your room, then take a close up of your monitor. Mosaica will then recognise the monitor close-up as part of the larger mosaic and show that image when you zoom in on the monitor. Genius!

Check them out at m.osaica.com

How to Run VMWare ESXi on PowerEdge T105

Wednesday, June 3rd, 2009

edit: PowerEdge T105 is now on HCL.

How to Run VMWare ESXi 4.0 on PowerEdge T105, you ask? Simple Answer. Flash Drive. The process goes thusly.

  • Get your ESXi Image ready to go. You can download it from the VMWare website.
  • Get your trusty 1GB+ Empty Flash Drive and stick it into one of the USB Ports on the Server
  • Next, Burn the ISO to a disk and stick it in your drive.
  • Press F11 at the BIOS to select your Boot device.
  • Boot from the DVD-ROM Drive.
  • When prompted where to install VMWare ESXi choose the Flash Drive that should show up in the list.
  • When prompted to reboot, remove the installation media. On reboot enter the BIOS.
  • Switch the Hard Drive Boot Priority to put the USB drive to the top.
  • Boot VMWare ESXi as normal.

Voilà! You’re ready to rock. The PowerEdge T105 is not on the HCL so you’re unfortunately unable to run it natively because of the onboard SATA controller. You could also find a compatible SATA controller and put the drives on that, but realistically the USB Drive is not that big of a hassel for most small environments. It also means you can boot VMWare even in the event of a HDD Failure. I’ve heard that many people will actually put the flash drive inside the case that so it is not at risk of being knocked around.

XMLDefault.cnf.xml

Thursday, May 28th, 2009

This is a bit of a placeholder until I can write a more definitive guide. Until then, here’s what most of you are looking for. Courtesy: voip-info.org

All of the loadInformation you could ever want! Best way to find your phone is to Ctrl + F with the model number.

<loadInformation30002 model=”Cisco 7920″>cmterm_7920.4.0-03-02</loadInformation30002>

<loadInformation30006 model=”Cisco 7970″>SCCP70.8-3-1S</loadInformation30006>

<loadInformation115 model=”Cisco 7941″>SCCP41.8-3-1S</loadInformation115>

<loadInformation30016 model=”Cisco IP Communicator”></loadInformation30016>

<loadInformation30032 model=”SCCP gateway virtual phone”></loadInformation30032>

<loadInformation308 model=”Cisco 7961G-GE”>SCCP41.8-3-1S</loadInformation308>

<loadInformation309 model=”Cisco 7941G-GE”>SCCP41.8-3-1S</loadInformation309>

<loadInformation30019 model=”Cisco 7936″>cmterm_7936.3-3-13-0</loadInformation30019>

<loadInformation12 model=”Cisco ATA 186″>ATA030203SCCP051201A</loadInformation12>

<loadInformation412 model=”Cisco 3951″>SIP3951.8-0-1</loadInformation412>

<loadInformation365 model=”Cisco 7921″>CP7921G-1.0.3</loadInformation365>

<loadInformation30007 model=”Cisco 7912″>CP7912080003SCCP070409A</loadInformation30007>

<loadInformation30035 model=”IP-STE”></loadInformation30035>

<loadInformation369 model=”Cisco 7906″>SCCP11.8-3-1S</loadInformation369>

<loadInformation30018 model=”Cisco 7961″>SCCP41.8-3-1S</loadInformation30018>

<loadInformation20000 model=”Cisco 7905″>CP7905080003SCCP070409A</loadInformation20000>

<loadInformation446 model=”Cisco 3911″></loadInformation446>

<loadInformation307 model=”Cisco 7911″>SCCP11.8-3-1S</loadInformation307>

<loadInformation4 model=”Cisco 12 S”></loadInformation4>

<loadInformation3 model=”Cisco 12 SP”></loadInformation3>

<loadInformation2 model=”Cisco 12 SP+”></loadInformation2>

<loadInformation1 model=”Cisco 30 SP+”></loadInformation1>

<loadInformation5 model=”Cisco 30 VIP”></loadInformation5>

<loadInformation30 model=”Analog Access”>A001C030</loadInformation30>

<loadInformation47 model=”Analog Access WS-X6624″>A002H024</loadInformation47>

<loadInformation51 model=”Conference Bridge WS-X6608″>C00104000001</loadInformation51>

<loadInformation40 model=”Digital Access”>D001M022</loadInformation40>

<loadInformation43 model=”Digital Access WS-X6608″>D00404000029</loadInformation43>

<loadInformation42 model=”Digital Access+”>D00303010033</loadInformation42>

<loadInformation61 model=”H.323 Phone”></loadInformation61>

<loadInformation7 model=”Cisco 7960″>P00308000500</loadInformation7>

<loadInformation100 model=”Load Simulator”></loadInformation100>

<loadInformation111 model=”Media Termination Point Hardware”>M00104000004</loadInformation111>

<loadInformation120 model=”MGCP Station”></loadInformation120>

<loadInformation121 model=”MGCP Trunk”></loadInformation121>

<loadInformation348 model=”Cisco 7931″>SCCP31.8-3-1S</loadInformation348>

<loadInformation9 model=”Cisco 7935″>P00503021600</loadInformation9>

<loadInformation431 model=”Cisco 7937″></loadInformation431>

<loadInformation375 model=”Cisco TelePresence”></loadInformation375>

<loadInformation30008 model=”Cisco 7902″>CP7902080002SCCP060817A</loadInformation30008>

<loadInformation11 model=”Cisco VGC Virtual Phone”></loadInformation11>

<loadInformation10 model=”Cisco VGC Phone”></loadInformation10>

<loadInformation6 model=”Cisco 7910″>P00405000700</loadInformation6>

<loadInformation8 model=”Cisco 7940″>P00308000500</loadInformation8>

<loadInformation115 model=”Cisco 7941″>SCCP41.8-0-1-0S</loadInformation115>

<loadInformation30027 model=”Analog Phone”></loadInformation30027>

<loadInformation124 model=”7914 14-Button Line Expansion Module”>S00105000300</loadInformation124>

<loadInformation119 model=”Cisco 7971″>SCCP70.8-3-1S</loadInformation119>

<loadInformation437 model=”Cisco 7975″></loadInformation437>

<loadInformation404 model=”Cisco 7962″></loadInformation404>

<loadInformation435 model=”Cisco 7945″></loadInformation435>

<loadInformation302 model=”Cisco 7985″>cmterm_7985.4-1-4-0</loadInformation302>

<loadInformation434 model=”Cisco 7942″></loadInformation434>

<loadInformation30028 model=”ISDN BRI Phone”></loadInformation30028>

<loadInformation358 model=”Cisco Unified Personal Communicator”></loadInformation358>

<loadInformation335 model=”Motorola CN622″></loadInformation335>

<loadInformation436 model=”Cisco 7965″></loadInformation436>

How to show dhcpd leases on CentOS (and most linux distros)

Sunday, May 10th, 2009

To show your current dhcpd table of leases is fairly simple. Connect to your server either locally or via ssh and then run the following lines.


cd /var/lib/dhcpd

cat dhcpd.leases

OR TO EDIT


nano dhcpd.leases

From there you can either view or edit your current dhcpd ip address leases.