As We May Think - Atlantic Mobile

Director of the Office of Scientific Research and Development, Dr. Vannevar Bush, 1945

http://theatlantic.com/magazine/archive/1945/07/as-we-may-think/3881/


As Director of the Office of Scientific Research and Development, Dr. Vannevar Bush has coordinated the activities of some six thousand leading American scientists in the application of science to warfare. In this significant article he holds up an incentive for scientists when the fighting has ceased. He urges that men of science should then turn to the massive task of making more accessible our bewildering store of knowledge. For years inventions have extended man's physical powers rather than the powers of his mind. Trip hammers that multiply the fists, microscopes that sharpen the eye, and engines of destruction and detection are new results, but not the end results, of modern science. Now, says Dr. Bush, instruments are at hand which, if properly developed, will give man access to and command over the inherited knowledge of the ages. The perfection of these pacific instruments should be the first objective of our scientists as they emerge from their war work. Like Emerson's famous address of 1837 on "The American Scholar," this paper by Dr. Bush calls for a new relationship between thinking man and the sum of our knowledge. —THE EDITOR

By Vannevar Bush, 1945

Click here to read the full article

-Bill Carter

My Networking, Virtualization, Storage, Wireless, et al. Google Custom Search Engine

When I started this blog it had a single purpose. I had discovered the Google Custom Search Engine and I needed a web site to host it. I had become very proficient in structuring Google search to get the results I wanted. However, was primarily limiting these searches to vendor sites.

I found Google Custom Search rand realized I needed a website to host the search engine. So I created my blog billyc5022.blogspot.com

I am now up to 107 sites indexed. I use the Google CSE, everyday, all day. I find great results in my searches without obscure, meaningless sites.

I would like to do two things. #1 invite everyone to try it out. #2 solicit from you which sites I should add.

Please try it out and give me some feedback.

-bill




Home

Telex Radio Dispatch System Integration with Cisco Unified Communications. Part 3

A reader has asked about our progress with this and it reminded me I haven't talked about our results.

I want to just reiterate what the Telex Radio Dispatch System is.

Telex provides an integration with multiple communications systems. This is commonly used in an environment where dispatchers communicate on multiple communications systems. The Telex C-Soft console provides dispatchers a point and click interface to interact with the various communications systems. Dispatchers can increase or decrease audio volumes from a specific radio system. They can also click on a specific radio system and, through their headset, talk on a particular radio system. The Telex Radio Dispatch System also allows for a phone system integration.

For example, consider an ambulance company. Their ambulances provide services for town A, town B, town C. All these towns communicate on specific radio channels. The ambulance company has radio towers and systems that connect to each radio channel/network. For each radio channel/network/town, Telex has a VoIP adapter that converts the radio communications to VoIP. The Telex system multicasts the audio from the radio system to the dispatchers.

For Cisco centric people, think Cisco IPICS.

We were brought in to integrate a Cisco CallManager phone system with the Telex system.

The primary problem we had was the integration between the physical phone and the Telex C-Soft Dispatch console. The physical integration is provided via in-line adapter connected to the phone (See Part 1). Often a NENA compliant phone is used. Cisco, as well as most other vendors, do not have NENA compliant phones (We later learned NENA compliant phones can cost several thousand dollars a piece). When an inbound call is presented to the dispatcher, they can answer the call by clicking on the appropriate icon on the dispatch console.

We connected a Cisco IP Phone to the Telex in-line adapter. On an inbound call, the dispatcher had to physically press the appropriate button on the phone to answer the call. This would not work, the customer wanted to use the C-Soft Dispatch Console to click and answer the call.

We tried removing a physical phone all together and use the C-Soft SIP phone. This worked ok for receiving calls. The C-Soft SIP phone was configured as a basic SIP phone in CallManager. To place outbound calls, dispatchers had to append @10.1.1.1 (CallManager's IP Address) to every outbound call, either internal or external. I held out hope the SIP client would work, but it looked to me like a freeware no frills SIP softphone. For the customer, this was a no go.

We found a small company in California which produces a box which connects to a physical phone (pretty much any phone) and provides the proper signalling to integrate with Telex (Sorry I don't have the companies name right now, but I can find it on request). With this box, dispatchers could click to answer the call, however C-Soft didn't pickup the audio.

After much troubleshooting we found the phone system needed to generate a tone or a beep when the call was answered to cause C-Soft to "hear" the call and mix the audio. After banging our heads together a co-worker suggested enabling the "call recording tone" on the dispatchers phones. This is normally used to play a tone to callers indicating the call is being recorded. We were not using a call recording system, but playing this tone caused the C-Soft console to recognize the call and mix the audio.

Telex Radio Dispatch System Integration with Cisco Unified Communications. Part 1

Telex Radio Dispatch System Integration with Cisco Unified Communications. Part 2

Home

Cisco Wireless AP - LWAPP: How to Recover an AP from Mis-Configuration

I am quickly learning Cisco Wireless. I had a problem with a Cisco LWAPP AP located at a remote office. This AP had not previously registered with a Wireless LAN Controller (WLC). We rely on the DNS discovery method where the AP boots up and does a DNS lookup for CISCO-LWAPP-CONTROLLER or CISCO-CAPWAP-CONTROLLER.

Well this is were the fun began. IP address and name-server was manually configured in the AP, but the name-server IP address was fat-fingered. The APs will save their IP and LWAPP configuration automatically. On a reboot, the AP came up with the same configuration. I was finally able to restore the configuration to factory default and have it discover and join the controller.

To do this a console connection to the AP is required. I had a user at the remote office connect a console cable to a notebook and let me RDP in..

1) I need to clear the static IP address settings, convert to DHCP, and have the AP connect to the WLC. With LWAPP/CAPWAP APs, you can't just go into the config and change things.

"debug lwapp console cli" (if that doesn't work try "debug capwap console cli" )

This allows me to make changes to the running configuration, but these changes can not be saved to what us router-jockeys call "startup-config". The "magic" here is that when a LWAPP/CAPWAP access point connects to a WLC, it saves the controllers address in nvram. Thus when reboted, the AP always knows which WLC to try to connect to.

"interface f0"
"ip address dhcp"

I created a DHCP pool on the core switch and included the correct DNS server. In about 5 seconds, the AP obtained an IP address and the new DNS server. Then it registered with the controller

2) One problem. After rebooting, the Cisco Wireless AP came up with the old static IP addressing and DNS old/wrong DNS server. I was, however able to register with the controller because it had previously registered with that controller.

3) I logged into the Cisco Wireless Control System (WCS) and found the AP. I removed the Static IP setting and saved. The AP rebooted and registered, still had the wrong DNS server.

In WCS I went to Configure - Access Point and found the AP, scrolled to the bottom for "set to factory defaults", clicked "clear config".

Finally cleared it!

Home

Who Needs English

Looks like I have encountered a licensing issue. Upgrading Unity Connection, customer is in the United States, Unity gives this error.

"The Cisco Unity Connection license file(s) that are installed do not allow you to use U.S. English for language-specific Connection features, and no other languages are installed. Do one of the following:

Download and install one or more Connection languages. Languages for your version of Connection, as well as documentation on how to install them, are available at http://www.cisco.com/kobayashi/sw-center-sw-voice.shtml.
If you have one or more license files that allow you to use U.S. English, go to the Licensing page and install them now.
If you do not have additional license files and you want to use U.S. English, contact your Cisco account team to purchase a license upgrade that allows you to use U.S. English."