Mosaica: Image Stiching for iPhone!

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

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

How to Run VMWare ESXi on PowerEdge T105

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.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

XMLDefault.cnf.xml

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>

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

Cisco IP Phone Model Breakdown

May 28th, 2009

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
Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

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

May 26th, 2009

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.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

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

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.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

The WAPPOE and WAPPOE12 Unofficial Compatibility List

May 1st, 2009
The WAPPOE12 Linksys PoE Injector

The WAPPOE12 Linksys PoE Injector

I purchased the WAPPOE12 for a customer who had a WRT54GX. The original tech who installed the Router opened up the cable and built a 12V injector using the unused pairs within a CAT5 cable. As much as this is a functional method of doing POE, and as many times I may have done this exact same thing in the past, I much prefer to go the standard compliant route when installing commercial solutions. For this reason I bought what seemed like a solution to all my problems, the WAPPOE12. Unfortunately as soon as I plugged it in the WRT54GX started to blink up a confused storm, I ran out and bought a WRT110 which is not on the compatibility list however and it works just fine. To make matters even more confusing the power adapter from the WRT110 works on the WRT54GX without any problems. Anyway, to conclude the WAPPOE and WAPPOE12 are finicky and the compatability list from Linksys is truncated and out of date. For this reason I’m going to be using this post as an unofficial compatability list for users looking to buy one of these products. If you know another product that works, or does not work leave a comment and I’ll add it to the list.

Compatible:

WAPPOE12 (12V)

  • ADSLMUE1
  • AG041
  • BEFSX41
  • BEFW11S4 v4
  • RT31P2 v1.2 and 2
  • WAP54G v2
  • WCG200
  • WGA54G
  • WPS54GU2
  • WRK54G
  • WRT54G
  • WRT54GS
  • WRT54GP2
  • WRT110

WAPPOE (6V)

  • WAP11
  • WAP11 v2.2
  • WAP11 v2.6
  • WAP11 v2.8
  • WAP54G,
  • WAP55AG
  • WAP51AB
  • BEFSR41
  • BEFSR11
  • BEFSR81
  • HPRO200
  • BEFVP41
  • BEFW11S4,
  • WET54G
  • WET11

Not Compatible:

  • WRT54GX (12V)
  • WRT54GL (reported via comment)
Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

Reflash your Cisco 7940, 7941, 7960 or 7961 phone to SIP

April 28th, 2009

apps41.8-5-2TH1-9.sbn
cnu41.8-5-2TH1-9.sbn
copstart.py
copstart.sh
cvm41sip.8-5-2TH1-9.sbn
dsp41.8-5-2TH1-9.sbn
jar41sip.8-5-2TH1-9.sbn
load115.txt
load30018.txt
load308.txt
load309.txt
SIP41.8-5-2S.loads
term41.default.loads
term61.default.loads

Cisco 7960

Cisco 7960

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

Use our web form to transmit your device information.

This guide applies to the Cisco 7940, 7940G, 7941G, 7960, 7960G and 7961G. These phones are the real work horses of the IP Telephony industry. They’re sturdy, configurable and when used with Call Manager very robust. However you’re not here to learn how to use these phones with CallManager you’re hear to use reflash them to SIP, because you want to use them with Asterisk, PiaF, Trixbox, or any other SIP based PBX. This process is not that difficult but it can be frustrating without the right instructions, which is why I’m here to help.

Firstly, I’m not a big fan of these phones in a SIP atmosphere, I have one on my desk so they’re by no means terrible, but realistically Cisco’s SIP firmwares are much more limited than their SCCP firmwares. If you haven’t yet bought your phone, I’d recommend you buy a phone from Linksys. They’re made of virtually the same parts, except designed for the Small Business and SIP customers.

Let me explain more or less what you are doing, you are taking whatever firmware is on your phone and you will be reflashing it to the latest SIP firmware. Typically these phones come from Cisco with the SCCP, often called “Skinny” protocol. This protocol only works with the proprietary Cisco CallManager platform or with special asterisk modules. Although it is very rare to ‘brick’ these phones, it is possible. It is very important that you are patient with each step as well as careful that all of your connections are solid.

Alright, to reflash this phone you’re going to need:

  1. DHCP Server
  2. TFTP Server
  3. P0S3-07-5-00.zip (For the 7940/7960)
  4. cmterm-7940-7960-8.11.00-sip.cop (7940/7960) or cmterm-7941_7961-sip.8-5-2.cop (7941/7961)
  5. XMLDefault.cnf.xml configured correctly for your firmware. (Right Click Save As, or your browser might try to parse the XML) SERIOUSLY FOLLOW THOSE INSTRUCTIONS, THAT’S THE BIGGEST MISTAKE PEOPLE MAKE, MOST MODERN BROWSERS WILL PARSE XML.

If you have a Cisco Smartnet Contract already you can get the firmwares for the 7940/7960 here and for the 7941 and 7961 here. If you don’t have a Smartnet Contract I recommend you buy one from CDW. You can chance it on the internet trying to find a good Samaritan who has uploaded the firmwares for you but it’s seriously worth the 8$/year to have access to firmware updates.

Now the unusual part about reflashing the 7940 and 7960 generation of  phones is that to get them to the most recent firmware often times they will have to be flashed twice. This is because sometime around the 7.5 firmware Cisco changed what I believe was the phone’s bootloader. For this reason it is necessary to take the phones directly from SCCP to P0S3-07-5-00 then to 8-11. Technically some phones may be able to go directly to the latest version from Cisco, but because it seems like the vast majority of phones with the SCCP firmware on them require this process, I now just assume that it will need to be done to streamline the process.

I’m going to steal a few bits from my Cisco 7970G Guide you can always use whatever TFTP server and DHCP server you like as long as you have the ability to set the DHCP options manually. Here we are going to use tftpd32, it has both a tftp and dhcp server inside.

To start make a folder on the desktop, I named mine CP-7940.

If you have a 7940 or 7960 extract the contents of P0S3-07-5-00.zip and cmterm-7940-7960-8.11.00-sip.cop with 7zip or WinRAR. The 7941 or 7961 will require you to extract the cmterm-7941_7961-sip.8-5-2.cop. If the archiver doesn’t automatically detect it’s extractable when you right click. Add a .gz to the end, it’ll figure it out. Then move the XMLDefault.cnf.xml that you downloaded from me into the same folder.

Now if you’re flashing a 7940 or 7960, you should have this in your directory.

  • cmterm-7940-7960-8.11.00-sip.cop
  • copstart.sh
  • OS79XX.TXT
  • P003-07-5-00.bin
  • P003-07-5-00.sbn
  • P003-08-11-00.bin
  • P003-08-11-00.sbn
  • P0S3-07-5-00.bin
  • P0S3-07-5-00.loads
  • P0S3-07-5-00.sb2
  • P0S3-08-11-00.loads
  • P0S3-08-11-00.sb2
  • sip_load7.txt
  • sip_load8.txt
  • XMLDefault.cnf.xml

The P003-* files are SCCP files, but they are used by the SIP. SIP firmwares are typically labeled P0S3-*. You want to make sure the P0S3*.loads file is referenced in your XMLDefault, but the P003 files still need to be available.

or for the 7941/7961

  • apps41.8-5-2TH1-9.sbn
  • cnu41.8-5-2TH1-9.sbn
  • copstart.py
  • copstart.sh
  • cvm41sip.8-5-2TH1-9.sbn
  • dsp41.8-5-2TH1-9.sbn
  • jar41sip.8-5-2TH1-9.sbn
  • load115.txt
  • load30018.txt
  • load308.txt
  • load309.txt
  • SIP41.8-5-2S.loads
  • term41.default.loads
  • term61.default.loads

Now we have to modify our XMLDefault.cnf.xml file to reflect our intent to reflash the phone. Either download my starter file from above or add these line to your XMLDefault.cnf.xml. Here I’ve included the settings for both the 7940 as well as 7960 generation of phones.

&lt;loadInformation8 model="CP-7940"&gt;P003-08-8-00&lt;/loadInformation8&gt;

&lt;loadInformation115 model="CP-7941"&gt;SIP41.8-5-2S&lt;/loadInformation115&gt;

&lt;loadInformation309 model="Cisco 7941G-GE"&gt;SIP41.8-5-2S&lt;/loadInformation309&gt;

&lt;loadInformation7 model="CP-7960"&gt;P003-08-8-00&lt;/loadInformation7&gt;

&lt;loadInformation30018 model="CP-7961"&gt;SIP41.8-5-2S&lt;/loadInformation30018&gt;

&lt;loadInformation308 model="Cisco 7961G-GE"&gt;SIP41.8-5-2S&lt;/loadInformation308&gt;

If you need any other phones check out my post on XMLDefault.cnf.xml loadInformation tags.

Next let’s configure TFTPd32

Firstly, determine how you are going to connect your 7940/60 to your DHCP/TFTP server. You’re going to need to make sure that there is no other routers on the network that could send competing DHCP broadcasts. I recommend one of two scenarios.

  • Connecting the Phone and Computer directly with a Crossover cable.
  • Connecting the Phone and Computer together on a network switch with no other devices. Notice I say SWITCH not a ROUTER. You could use a router if you configured it properly, but that’s another story.

The switch option works better because it prevents the computer’s LAN interface from going up and down depending on if the phone is plugged in or not.

Next you are going to need to get a copy of tftpd32:

Now that you have tftpd32 open and running, we need to configure it:

Open up the settings box

Enable DHCP Server, TFTP Server, and Log Viewer, all others can be unchecked.

Make sure that you have set the directory into the same directory as your Cisco Firmware Files.

Make sure you have the correct configuration files in the directory including a XMLDefault.cnf.xml that at least partially resembles this one: (right click save as)

Set TFTP Security to STANDARD, in the image it says None. It should not be set to none it should be set to STANDARD.

Make certain that the bind address is set to the correct interface.

TFTPD32 Configuration

TFTPD32 Configuration

When done go to the DHCP tab

Make sure a DHCP and DNS server are set. Under additional options set “69″ and make the IP the same as your TFTP server. Do not use these IP settings, they just server as a rough guide. The IP Pool starting address being out of the subnet is not intentional. Also under additional options the 19 was cut off by the size of the box. If you have problems with option 150, try option 66.

TFTPD32 DHCP Settings for Cisco 7970G

TFTPD32 DHCP Settings for Cisco 7960 7940

Check for any settings that I may have missed and double check that everything is correct.

Now it’s time to boot up the phone. If the phone is already on, a quick way to reboot it is by holding down the * key, the six key, and the settings key simultaneously. As the phone boots up watch the logs. With any luck it should boot up, and try to pull the SEPMAC.cnf then give up and move on to XMLDefault.cnf.xml. When it sees that file it should start downloading the firmware files and reboot. If after rebooting you see the phone look for a SIPMAC.cnf file then SIPDefault.cnf, your phone is successfully reflashed.

The 7941/7961 seems to reboot twice grabbing different files each time.

If the phone isn’t reflashing, double check your TFTP settings and make sure the phone is detecting your TFTP server. You may have to go into Network Settings and enable alternate TFTP server. Typically you can do this by moving to the option then pressing **# **to unlock it or going to setting then option 9. The default password is “cisco”. Then go to Network Configuration (Option 3) Then enable “Alternate TFTP Server” (Option 32) then type in the TFTP server address. The most common problem though is an error in the XMLDefault.cnf.xml file. I find myself having to do this very often on many networks.

Once you see the Sip logo in the upper right corner you are now safely flashed to 7.5. You’ll need to perform this process one more time to bring the phone up to the latest firmware. At the time of this writing that was 8.11. Open up your XMLDefault.cnf.xml file and replace the previous lines with

<loadInformation8 model=”IP Phone 7940″>P0S3-08-11-00</loadInformation8>

<loadInformation7 model=”IP Phone 7960″> P0S3-08-11-00</loadInformation7>

Reboot the phone again and it should update to the latest firmware.

This will get the phone reflashed, from here on you’ll need a configuration file to register the phone to a PBX. We have one already made for the Cisco 7941  / 7961 over here.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

Why you shouldn’t buy a Cisco IP Phone

April 22nd, 2009

(unless you’re using CallManager)

That’s it, I’m done. I think that Cisco must hate their customers so much that they intentionally mutilate their products. Let me get the first thing straight, Cisco IP Phones are amazing. They are built with a sturdiness and a level of quality that I have yet to see matched by any other brand. There is a reason why they are the universal telephone of business. With that out of the way, Cisco seems to get some sort of sick pleasure out of torturing customers who use SIP. Their business model seems to focus on frustrating customers into buying CallManager.

Cisco’s forray into IP Telephony seemed to start strong. The 7912 have relatively good SIP support. But as time went by the 7940, 7960, 7970 are just not gauged towards the SIP audience.

Here’s a list:

1. SmartNET contract to download firmwares, seriously?

2. The Cisco 7970 is the most beautiful phone I’ve ever touched, and it doesn’t work because Cisco engineers don’t care.

3. We paid 600$ for this phone, why can’t you give us a simple web administration panel?

4. How long are we going to have to wait for SLA? OR BLF? Seriously.

5. Broken NAT Support, needs to be babied

This leads me to my theory, call it a conspiracy theory. But I think Cisco doesn’t want Small Business customers to buy Cisco products. I think they want you to buy a Linksys IP Phone. Linksys (a division of Cisco) produces excellent SIP phones using many of the same parts from the Ciscos. They are sturdy,  support all of the features that the Ciscos do not, and best of all…they work.

If you were planning on buying a Cisco 7940/60/70. Don’t. Go with a Linksys SPA-94x series phone. They don’t have the same luxurious screen or top notch speaker phone as the Ciscos but you won’t regret it.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit

Greenwire, LLC announces new web design packages for Southwest Florida

April 20th, 2009

Greenwire, LLC announces new web design packages for Southwest Florida

Greenwire will offer both web design/development and SEM/SEO packages to help boost the web presence of customers in Fort Myers, Cape Coral, Naples and the surrounding area.

Cape Coral, Florida

April 20, 2009

FOR IMMEDIATE RELEASE:

Southwest Florida-based information technology firm Greenwire, LLC will be bolstering their already impressive array of services by offering web design solutions to customers in Lee and Collier county.

At the forefront of this initiative is a custom web design and development package for customers who want to establish a unique internet presence. For customers who want to go to the next level, Greenwire will also offer Search Engine Optimization (SEO) and Marketing (SEM) plans to help bring in visitors.

“These days, it’ s impossible to be competitive in any business without a solid web presence,” Greenwire Owner Paul Rausch said. “We can work with customers to do that, and take it a step further by making sure that their sites are the ones people find.”

Thanks to their connections throughout the technology community, Greenwire is able to work with a deep network of independent contractors, along with their in-house staff, to help ensure that client’s sites are built to their exact specifications and to provide specialized functionality for all needs.

The company is also deeply committed to helping their customers succeed past the design and development stages. That’s why they will also offer SEO and SEM service to their customers who want to further expand their presence on the web.

“A lot of companies will just take your money, throw around a couple of links, and call it “optimization,” Rausch said. “I don’t believe in that. I believe in results. I think a lot of people around the area will appreciate that.”

Greenwire has been serving the information technology needs of Southwest Florida since 2008. The company is staffed by certified technicians and offers Telephony and Managed IT Solutions for commercial and residential clients, as well as remote and on-site technical support nationwide.

Contact:

Greenwire, LLC

http://www.greenwireit.com

service@greenwireit.com

(877) 419-9634

-END-

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Technorati
  • Reddit