Putty is an ssh client for Microsoft Windows which can automate secure logins to remote computers. This tutorial allows you to automate these logins using your public/private key pair.
Putty can be downloaded from here: http://www.chiark.greenend.org.uk/~sgtatham/putty/. Download and install the entire putty distribution.
During this procedure the following high-level steps are taken:
- First, create a public-private key pair using
- Second, create a session for logging into a particular host. This session will include the IP address, and can include the username and location of your private key
- Lastly, add your public key to the host you’ll be logging into.
Each of these steps is detailed below. Continue reading “Automating Secure Shell Login using Putty”
This became a surprisingly full day. An earthquake near Taiwan around 1 PM local time disrupted communications lines to our out-sourced call center in Manila, the Philippines. This was certainly a surprise to our Customer Care group as they were under the, apparently mistaken, impression that diverse redundant voice routes were provided by the out-source company.
Regardless, it caused the Engineering department some serious headache. As the assumption had been that redundancy was built-in, a business recovery plan had not been created. A scramble was required to cobble together a work-around to reduce the impact on our customers, whose calls in the meantime were being dumped on the floor.
Continue reading “Out-source Call Center recovers from catastrophic outage”
TeleTips Network has just opened a new message board for the Nortel EV-DO. There seems much to learn. Nortel has provided a training course which I’ll be following over the next few weeks. I’ll post the course specifics later, and a review of the course materials. In the meantime, this board can be used for your Nortel EV-DO discussions.
The second week of September in Ottawa, Ontario, Canada, Nortel will be hosting their users for a week-long conference of training, product demonstrations and sales. It is also expected to be a good chance for users to get together, compare notes, swap stories and have some fun. TeleTips Network will be there, blogging from the conference and calling attention to highlights and news. We’ll be showing the flag and recruiting some new members, too. If you’ll be attending drop us a note and look for us there.
Here’s a link to the Nortel CDMA Wireless Users Group Conference
Vodafone and Verizon are again in the news. I’ve posted a recent story to our message boards, and written about them previously in the context of the upcoming American 700 MHz auctions. (Full disclosure: I used to work for AirTouch, which was acquired by Vodafone, and for Arun Sarin, now CEO of Vodafone.) The recent news is about their difficulties getting along together and about the possibility that the dividend Verizon pays to Vodafone, as a major stockholder, might not be paid again until 2010 or later. Continue reading “Verizon and Vodafone stir the pot”
Overnight I implemented a script that dynamically generates the home page. The purpose of this change is to give better visibility to new information and reader contributions. Off to the side you can see sections showing recent entries into our message boards, recent reader comments to our blog , most popular forum topics.
There’s much left to be done. The style sheet for the blog is not 100% synced up with our home page, though that ought to require a relatively modest effort. The far greater challenge will be to extend our look and feel into our message boards. That’s one of the challenges of open source software: reverse-engineering someone else’s style sheet.
Stay tuned, and thanks for being a part of the TeleTips Network.
So today the American Federal Communications Commission decided to make the winner of the upcoming 700MHz spectrum auctions accept terminals and applications from 3rd-parties. This was at the suggestion of Google and others, and is excellent news for American consumers. It likely will lead to more handsets from which to choose and more innovative applications being available more quickly. Probably it also will mark the beginning of the end of the glory days for America’s incumbent mobile operators.
This ruling heralds much more difficult times for America’s coddled mobile operators. Handset choice and the ready access to innovative applications are not what they are known for. These will force them to change their current business models, which is likely to reduce their margins as well as their subscriber numbers. Their good times now have a hard stop.
Continue reading “Google scores a victory for consumers”
The purpose of this Method Of Procedure (MOP) is to add ranges of IP Addresses, called “pools”, to the Starent 16000 PDSN. An IP address from an IP pool is assigned to a subscriber by the PDSN when a data session is initiated.
Begin this procedure by creating a backup of the PDSN configuration file. Use the copy command to create a new configuration file.
[local]pdsn1# copy /flash/system.cfg /flash/system.backupfile.cfg <CR>
The file called
system.backupfile.cfg is created as a contingency in the event a problem occurs during execution of this method.
Continue reading “Starent 16000 PDSN MOP – Adding IP Pools”
I’ve been working for a couple months now to create the software infrastructure for allocating wireless data network resources based upon the product purchased by the subscriber. This means granting them access to the purchased resources, and denying access to other resources. This is one of the functions of the PDSN, in cooperation with the AAA server.
I post trouble reports and questions as they arise to the TeleTips Message Board for the Starent PDSN. Here is a step-by-step procedure for testing on the PDSN. Continue reading “Starent 16000 PDSN Troubleshooting”
We continue working to deploy new Wireless Data plans. This week we’ve stumbled on an issue in the edge router. It does not appear to be properly detecting the OSPF routes. This problem manifests itself when the 4th octet of the IP address assigned by the PDSN to a handset exceeds “128”. Whenever a higher number gets assigned all data calls fail. Doing a stare and compare with other IP address ranges in the router shows the difference. But so far the cause cannot be explained.
Nortel has proposed flushing the OSPF cache on the PDSN with this command:
clear ip ospf process
After the command has been entered, we’ll monitor use of the use of the erring address space to see if data sessions having an IP Address above .128 succeed.