Cisco 7961 and 7941 SIP Configuration SEPMAC.cnf.xml

Wednesday, September 9, 2009 @ 12:09 AM
posted by Paul

We now sell the SmartNET Service Agreements for these phones! (Necessary to get Firmware)

Use our web form to transmit your device information.

Here is a basic cleansed Cisco 7941/7961 Configuration file. This file was provided by Henry over at Axxtel, LLC in Lawrenceville, Georgia. He was kind enough to provide us his basic configuration file with comments provided.

You will need to make certain that your phone has been reflashed to the SIP firmware. Most phones come with the SCCP firmware on them. To learn more about this procedure check our out article on reflashing Cisco 7940 and 7960 phones over here: Cisco 7940 and 7960 guide. Once you’ve done that you can use this configuration file to register your phone to your Asterisk  or other SIP based PBX.

Go ahead and replace the relevant fields with information related to your phone and PBX. You can download that file here. Make sure you right click and go to save target as. This is very important as most modern browsers will attempt to parse the XML file.

Here’s the file copy and pasted, I do not recommend you use more than one line from this file, downloading the XML file will typically work much better. I would recommend editing this file in Notepad++.

<device xsi:type=”axl:XIPPhone” ctiid=”[Employe phone number ex 6785551212]“>

<deviceProtocol>SIP</deviceProtocol>

<sshUserId>[SSH User]</sshUserId>

<sshPassword>[SSH Password]</sshPassword>

<devicePool>

<dateTimeSetting>

<dateTemplate>M/D/Ya</dateTemplate>

<timeZone>Eastern Standard/Daylight Time</timeZone>

<ntps>

<ntp>

<name>192.43.244.18</name>

<ntpMode>directedbroadcast</ntpMode>

</ntp>

</ntps>

</dateTimeSetting>

<callManagerGroup>

<members>

<member priority=”0″>

<callManager>

<ports>

<ethernetPhonePort>2000</ethernetPhonePort>

<sipPort>5060</sipPort>

<securedSipPort>5061</securedSipPort>

</ports>

<processNodeName>[Asterisk IP Address]</processNodeName>

</callManager>

</member>

</members>

</callManagerGroup>

</devicePool>

<sipProfile>

<sipProxies>

<backupProxy></backupProxy>

<backupProxyPort></backupProxyPort>

<emergencyProxy></emergencyProxy>

<emergencyProxyPort></emergencyProxyPort>

<outboundProxy></outboundProxy>

<outboundProxyPort></outboundProxyPort>

<registerWithProxy>true</registerWithProxy>

</sipProxies>

<sipCallFeatures>

<cnfJoinEnabled>true</cnfJoinEnabled>

<callForwardURI>x–serviceuri-cfwdall</callForwardURI>

<callPickupURI>x-cisco-serviceuri-pickup</callPickupURI>

<callPickupListURI>x-cisco-serviceuri-opickup</callPickupListURI>

<callPickupGroupURI>x-cisco-serviceuri-gpickup</callPickupGroupURI>

<meetMeServiceURI>x-cisco-serviceuri-meetme</meetMeServiceURI>

<abbreviatedDialURI>x-cisco-serviceuri-abbrdial</abbreviatedDialURI>

<rfc2543Hold>false</rfc2543Hold>

<callHoldRingback>2</callHoldRingback>

<localCfwdEnable>true</localCfwdEnable>

<semiAttendedTransfer>true</semiAttendedTransfer>

<anonymousCallBlock>2</anonymousCallBlock>

<callerIdBlocking>2</callerIdBlocking>

<dndControl>0</dndControl>

<remoteCcEnable>true</remoteCcEnable>

</sipCallFeatures>

<sipStack>

<sipInviteRetx>6</sipInviteRetx>

<sipRetx>10</sipRetx>

<timerInviteExpires>180</timerInviteExpires>

<timerRegisterExpires>3600</timerRegisterExpires>

<timerRegisterDelta>5</timerRegisterDelta>

<timerKeepAliveExpires>120</timerKeepAliveExpires>

<timerSubscribeExpires>120</timerSubscribeExpires>

<timerSubscribeDelta>5</timerSubscribeDelta>

<timerT1>500</timerT1>

<timerT2>4000</timerT2>

<maxRedirects>70</maxRedirects>

<remotePartyID>false</remotePartyID>

<userInfo>None</userInfo>

</sipStack>

<autoAnswerTimer>1</autoAnswerTimer>

<autoAnswerAltBehavior>false</autoAnswerAltBehavior>

<autoAnswerOverride>true</autoAnswerOverride>

<transferOnhookEnabled>false</transferOnhookEnabled>

<enableVad>false</enableVad>

<preferredCodec>g711ulaw</preferredCodec>

<dtmfAvtPayload>101</dtmfAvtPayload>

<dtmfDbLevel>3</dtmfDbLevel>

<dtmfOutofBand>avt</dtmfOutofBand>

<alwaysUsePrimeLine>false</alwaysUsePrimeLine>

<alwaysUsePrimeLineVoiceMail>false</alwaysUsePrimeLineVoiceMail>

<kpml>3</kpml>

<natEnabled>false</natEnabled>

<natAddress></natAddress>

<phoneLabel>[Employee Name(do not exceed 11 charaters)]</phoneLabel>

<stutterMsgWaiting>1</stutterMsgWaiting>

<callStats>true</callStats>

<silentPeriodBetweenCallWaitingBursts>10</silentPeriodBetweenCallWaitingBursts>

<disableLocalSpeedDialConfig>false</disableLocalSpeedDialConfig>

<startMediaPort>16384</startMediaPort>

<stopMediaPort>32766</stopMediaPort>

<sipLines>

<line button=”1″>

<featureID>9</featureID>

<featureLabel>[Employee phone number ex. 678.555.1212]</featureLabel>

<proxy>[Asterisk IP Address]</proxy>

<port>5060</port>

<name>[Employee Extension]</name>

<displayName>[Employee Name]</displayName>

<autoAnswer>

<autoAnswerEnabled>2</autoAnswerEnabled>

</autoAnswer>

<callWaiting>3</callWaiting>

<authName>[Employee Extension]</authName>

<authPassword>[SIP Password]</authPassword>

<sharedLine>false</sharedLine>

<messageWaitingLampPolicy>1</messageWaitingLampPolicy>

<messagesNumber>*97</messagesNumber>

<ringSettingIdle>4</ringSettingIdle>

<ringSettingActive>5</ringSettingActive>

<contact>[Employee phone number]</contact>

<forwardCallInfoDisplay>

<callerName>true</callerName>

<callerNumber>false</callerNumber>

<redirectedNumber>false</redirectedNumber>

<dialedNumber>true</dialedNumber>

</forwardCallInfoDisplay>

</line>

<line button=”2″>

<featureID>9</featureID>

<featureLabel>Intercom</featureLabel>

<speedDialNumber>[paging group]</speedDialNumber>

<proxy>[Asterisk IP Address]</proxy>

<port>5060</port>

<name>[1 then Employee extension]</name>

<displayName>[Employee Name]</displayName>

<autoAnswer>

<autoAnswerEnabled>1</autoAnswerEnabled>

<autoAnswerMode>Auto Answer with Speakerphone</autoAnswerMode>

</autoAnswer>

<callWaiting>3</callWaiting>

<authName>[1 then Employee extension]</authName>

<authPassword>[SIP Password]</authPassword>

<sharedLine>true</sharedLine>

<ringSettingIdle>4</ringSettingIdle>

<ringSettingActive>5</ringSettingActive>

<contact>[1 then Employee extension]</contact>

</line>

</sipLines>

<voipControlPort>5060</voipControlPort>

<dscpForAudio>184</dscpForAudio>

<ringSettingBusyStationPolicy>0</ringSettingBusyStationPolicy>

<dialTemplate>dialplan.xml</dialTemplate>

<softKeyFile>softkeys.xml</softKeyFile>

</sipProfile>

<commonProfile>

<phonePassword>[Phone Password]/phonePassword>

<backgroundImageAccess>true</backgroundImageAccess>

<callLogBlfEnabled>2</callLogBlfEnabled>

</commonProfile>

<loadInformation309>SIP41.8-5-2S</loadInformation309>

<loadInformation115>SIP41.8-5-2S</loadInformation115>

<vendorConfig>

<disableSpeaker>false</disableSpeaker>

<disableSpeakerAndHeadset>false</disableSpeakerAndHeadset>

<pcPort>1</pcPort>

<settingsAccess>1</settingsAccess>

<garp>0</garp>

<voiceVlanAccess>1</voiceVlanAccess>

<videoCapability>0</videoCapability>

<autoSelectLineEnable>0</autoSelectLineEnable>

<webAccess>1</webAccess>

<spanToPCPort>0</spanToPCPort>

<loggingDisplay>1</loggingDisplay>

<loadServer></loadServer>

</vendorConfig>

<versionStamp></versionStamp>

<userLocale>

<name>English_United_States</name>

<uid>1</uid>

<langCode>en_US</langCode>

<version>1.0.0.0-1</version>

<winCharSet>iso-8859-1</winCharSet>

</userLocale>

<networkLocale>United_States</networkLocale>

<networkLocaleInfo>

<name>United_States</name>

<uid>64</uid>

<version>1.0.0.0-1</version>

</networkLocaleInfo>

<deviceSecurityMode>1</deviceSecurityMode>

<authenticationURL></authenticationURL>

<directoryURL></directoryURL>

<idleURL></idleURL>

<informationURL></informationURL>

<messagesURL></messagesURL>

<proxyServerURL></proxyServerURL>

<servicesURL></servicesURL>

<dscpForSCCPPhoneConfig>96</dscpForSCCPPhoneConfig>

<dscpForSCCPPhoneServices>0</dscpForSCCPPhoneServices>

<dscpForCm2Dvce>96</dscpForCm2Dvce>

<transportLayerProtocol>4</transportLayerProtocol>

<capfAuthMode>0</capfAuthMode>

<capfList>

<capf>

<phonePort>3804</phonePort>

</capf>

</capfList>

<certHash></certHash>

<encrConfig>false</encrConfig>

</device>

Testing the ‘Hard drive in the Freezer’ Trick

Wednesday, July 15, 2009 @ 09:07 PM
posted by Paul

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

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.

This problem had me going nuts for about 30 minutes. Typically when an update comes out, I just edit all of my configuration files by changing the subversion up by one number. This time around I was having problems with the phones unable to find the firmware on the TFTP Server. My aha moment came when I ran the following commands:
root@pbx:/tftpboot $ ls *08-11*
P003-08-11-00.bin P003-08-11-00.sbn P0S3-08-11-00.loads P0S3-08-11-00.sb2
root@pbx:/tftpboot $ ls *08-12*
ls: *08-12*: No such file or directory

Cisco has changed the syntax ever so slightly from 08-* to 8-*. Hope that helps someone!

Mosaica: Image Stiching for iPhone!

Monday, June 8, 2009 @ 05:06 PM
posted by Paul

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 3, 2009 @ 11:06 PM
posted by Paul

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 28, 2009 @ 01:05 PM
posted by Paul

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>

Cisco IP Phone Model Breakdown

Thursday, May 28, 2009 @ 01:05 PM
posted by Paul

Cisco 7960 IP Phone

Cisco 7960 IP Phone

We now sell the SmartNET Service Agreements for these phones! (Necessary to get Firmware)

Use our web form to transmit your device information.

So you ask yourself?

What’s the difference between the Cisco 7940 and 7940G or the 7960 and 7961-GE?

What’s the difference between a Cisco 7940 and a 7945G?

Scroll down for a chart!

The Cisco 79xx series of phones is now a well established line of IP Telephones. Probably best known for their High Quality Speakerphone, and Sturdy construction. There are a number of reasons why they’re not always the best choice when buying an IP Phone. But that’s another story.

The 79xx line of phones is so well established that it has grown to include a variety of subversions. Whereas the product line used to contain just a handful of phones, Cisco has continually upgraded and released subsequent updates to their phones. For this reason we see the current multitude of phones on the market. Fortunately for us the numbering and naming scheme follows a pretty consistent logic.

Although there now exists a multitude of phones, as a general rule of thumb the majority of Cisco phones are based around one of three models. The 7940, 7960 or 7970. Most phones are simply subversions of these phone with different features and capabilities.

The Base Models

The 794x Series of Phones are all 2 Line Grayscale Phones

The 796x Series of Phones are Identical to the 7940s except with the presence of 6 lines instead of 2.

The 797x Series of Phones are Colour Executive Phones with 8 lines, which will drive you insane trying to configure.

The Subversions

The final number, and the letters that come after each of the phone models each represent a different version of the phone. Each with different features and limitations.

79xxG – The “G” in any Cisco Phone stands for “Global” it means that the phone supports Firmwares in Languages other than English. I will not include it in the below graph as it has no other bearing on any other features in the phones. Many of the later models all include this G, that is because Cisco eventually made it a standard feature on all the phones.

79×1 – This was the first generation of revisions to the Cisco line up released in 2006. The 79×1 phones are 802.3af PoE Compliant. For example, the 7940G supports only Cisco’s Prestandard PoE, whereas the 7941G will work with any normal PoE Switch. Additionally the 79×1 typically has a higher resolution screen than the 79×0.

79×1-GE – This is a further revision on the 79×1 phones, phones with the GE feature tag afterwards have been upgraded to support Gigabit Ethernet.

79×2 –An oddball version. High Resolution Greyscale Screen. Can’t find much else about it. Comments!

79×5 – The most recent update in the Cisco Series, now has a higher resolution standard, are colour, and have Gigabit Ethernet Ports standard.

79xx-CH1 – This is the exact same product as the one without the CH1, however the CH1 typically denotes that the CallManager License is included with the phone. (Only applies to customers using CallManager)

Model 7940 7941 7942 7945 7960 7961 7962 7965 7970 7971 7975
# of Lines 2 2 2 2 6 6 6 6 8 8 8
Gigabitt N GE Only N Y N GE Only N Y N GE Only Y
Screen Type Grey Hi-Res Grey Hi-Res Grey Colour Grey Hi-Res Grey Hi-Res Grey Colour Colour Colour Colour
PoE Cisco 802.3af 802.3af 802.3af Cisco 802.3af 802.3af 802.3af Cisco 802.3af 802.3af
Protocols SIP, SCCP, MGCP SIP, SCCP SIP?, SCCP SIP, SCCP SIP, SCCP, MGCP SIP, SCCP SIP?, SCCP SIP, SCCP SIP, SCCP SIP, SCCP SIP, SCCP

VoIP and IP-PBX Help in Cape Coral and Fort Myers

Tuesday, May 26, 2009 @ 06:05 PM
posted by Paul

Are you looking for professional help with your IP-PBX? We specialise in Asterisk based IP Phone Systems, one of the few providers in the Cape Coral / Fort Myers area.  Just google online for information on Cisco 7940 and Cisco 7960 phones and you’re going to find one of our guides. If you’re looking to make the jump to VoIP or looking to repair your existing phone system give us a call at 239-444-5522.

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

Sunday, May 10, 2009 @ 01:05 PM
posted by Paul

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.


Recent Posts: Greenwire News

Recent Posts: Walk Throughs

  • Fort Myers Certified Cisco Certified Partner
  • Tell us what you think, on Google Maps
  • Greenwire, LLC announces new web design packages for Southwest Florida
  • Greenwire, LLC Now Offers Non-Profits Cost Saving Price Schedule for All its Information Technology Solutions
  • We’re now a Microsoft Authorized Refurbisher!
  • Office 2010 Home and Student, Unable to “Open With” Word, Excel etc.
  • How to Convert an Avast Pro 4.8 Key into a Avast 5.0 Key
  • Complete Guide to Install Windows 7 on the eee PC 1000 series (Drivers, ACPI and All)
  • Reflash your Cisco 7940, 7941, 7960 or 7961 phone to SIP
  • Script to automatically turn your CentOS 5.2 installation into a Router with Squid Caching
  • How to Install Windows XP on a Dell Vostro 220 or Vostro 1520, the Crashless way!



  • 2722 Skyline Blvd, Ste 2, Cape Coral, FL 33914