Memo to Apple: Partner with Cisco
The VAR Guy saw this coming: For months, he has called on Apple to partner with Cisco Systems to ensure the iPhone worked with Cisco-based networks. Now comes word that Duke University (a major Cisco customer) is experiencing network problems — allegedly due to iPhone-related problems.
Kudos to Network World for covering Duke’s iPhone challenges. Now it’s time for Apple to answer the call for help and speed-dial the folks at Cisco Systems. For months, The VAR Guy has anticipated a possible unified communications partnership between Apple and Cisco. But even Cisco CEO John Chambers has stated that Apple has to decide whether it wants to play ball.
Hmmm. Cisco’s big customer summit is July 22 in Anaheim, Calif. It’s the perfect stage for Chambers to disclose a potential relationship with Apple. For the sake of Duke University and other customers, let’s hope Apple finally comes to the negotiating table.
<b>Update: July 23, 2007:</b> Duke University now blames the network problem on Cisco’s gear rather than the iPhone. However, complete details are still sketchy. Here’s some perspective from The Wall Street Journal.
The VAR Guy should take a bow on this one. He was one of the few during the iPhone battle that actually said Apple would be smart to partner with Cisco. In fact, he even asked Chambers directly during a Qamp;A session at the Cisco Partner Summit. Nicely done VAR Guy.
Ok, so 1 location has reported a problem. Yes, they are complaining that the communication is one way so far, but look at the reality of the situation. One client out of millions is reporting a problem and they are assuming that it is with the new product. Maybe the issue is with how Duke setup the Cisco equipment and not with either the iphone or Cisco? Forgive everyone except for Duke for not running around and screaming that the sky is falling.
From what I recall, Apple uses Cisco internally so I’m betting that they were already partnering with them to make sure it worked all along. I’d be willing to bet that they would have discovered any issues that would have arose in a properly configured environnment. Also notice new info from Duke today that backs off on previous statements regarding whose fault it is.
So, I guess the real kudos goes to MacWorld for quickly and accurately reporting that a malfunctioning access point was the problem, not a problem between the iPhone and Cisco products. So before you go off and break your arm patting yourself on the back, you might want to consider that you were simply spreading misinformation as quickly as you could. For a nice resolution to the “issue” read here
http://www.macworld.com/news/2007/07/20/dukecisco/index.php?lsrc=mwrss
Wow, I guess that one client with one malfuctioning piece of hardware really was worth all of these headlines. It would have been nice if your writers could have considered the entirely real possibility that this was an isolated case rather than jumping on the I told you so bandwagon right away. Anyone feel like stepping off of that bandwagon now?? Maybe consider printing a retraction especially since it has been reported that Apple and Cisco did get together and isolate the problem??