Remote Voicemail on the BCM

For quite a while we have relied on dialing ‘**’ when dialing into the BCM to check our voicemail. However, our snazzy new touchscreen cellphones don’t handle ‘clicking’ the asterisk in a quick, consecutive fashion. I looked around on the Internet for an alternative, but then realized that I could just use the number . . . → Read More: Remote Voicemail on the BCM

Sykes and AT&T

Our AT&T sales rep got us a pretty good deal on a new MPLS implementation, but the install left a lot to be desired. Our previous MPLS install was handled by DPSciences and they did a great job of making sure all the technical aspects were handled and of making sure all the billing issues that accompany such an install were handled as well. However, for the new implementation AT&T used Sykes and they did a wretched job of managing the install: We weren’t given proper ETAs for installs. This resulted in the install at one site being done improperly and the install at a different site apparently not being scheduled at all. This the led to a sticky billing issue where we were billed for circuits that were ready to be turned up, but couldn’t be utilized until the last circuit was brought up. I asked if our Class of Service was brought over. The lack of response should have told me that something was up and it turned out that it wasn’t applied at all by their incompetent tech. The lack of response didn’t register any higher in my mind since their tech never responded to me about anything. They didn’t bring over an important custom configuration for one of our routers as I nagged them to do. How hard is it to save a router configuration and then apply it to a different router that’s the same make and model?!? It took a week of incessant nagging on my part in trying to figure out what was wrong with our new MPLS implementation before they eventually got back to me to let me know that there were routing errors only because one of our old MPLS routers was left on. Yes, I guess I should have known, but would it have killed them to let me know that couple days sooner? As a side note, we had an AT&T MIS Internet circuit put in by ACS and they did a great job as well. There are plenty of other great AT&T outsource choices besides the apparently awful Sykes. . . . → Read More: Sykes and AT&T

SSL on the Nortel BCM

All of these concepts are probably familiar to those in the know, but I wasn’t able to put the pieces together until I upgraded to Windows 7 and found that without a properly working SSL configuration Windows 7 wasn’t going to load up the BCM system administration utility. The documentation for the Nortel BCM states to go to the ‘Maintenance’ section, and then ‘Maintenance Tools’ (well it doesn’t say that but I found it anyway), and then ‘Upload a Certificate and Private Key’. However, where do I get these? I knew that the certification would come from my Windows based CA that runs in the domain, but there wasn’t a tool to generate a certificate request on the BCM. My clue was that a private key, the key used to generate the request, had to be uploaded as well. I then used the version of openssl on the BCM to do the work, though in hindsight it probably would have been easier to use a newer version installed elsewhere. First, upon doing a version check of openssl I noticed that the working directory that it was looking for (‘c:\openssl\ssl’) didn’t exist. I manually created the directory and did the work from there. Eventually I discovered that the ‘openssl.cnf’ file (that was called something else and buried elsewhere on a different drive) that shipped with the BCM was lacking and I ended up brewing my own with the following settings: [ req ] default_bits = 2048 default_keyfile = privkey.pem encrypt_rsa_key = no default_md = sha1 distinguished_name = req_distinguished_name x509_extensions = root_ca_extensions [ req_distinguished_name ] 0.organizationName = Organization Name (company) organizationalUnitName = Organizational Unit Name (department, division) emailAddress = Email Address emailAddress_max = 40 localityName = Locality Name (city, district) stateOrProvinceName = State or Province Name (full name) countryName = Country Name (2 letter code) countryName_min = 2 countryName_max = 2 commonName = Common Name (hostname, IP, or your name) commonName_max = 64 [ root_ca_extensions ] basicConstraints = CA:true I then executed a command along the lines of the following and filling out the ‘form’ that comes up: openssl req -new -newkey rsa:1024 -nodes -keyout bcmkey.pem -out bcmreq.pem I then FTP’d (bad form, but I already said that a different method would have been better) the two files up to my file server. I put the ‘req’ file through my Windows CA (‘Base 64 encoded’, and unlike the HP ILO card I didn’t need the whole chain) to get the web server certificate and I then uploaded them both up the BCM and viola, the SSL warning error messages were gone and the manager was happy under Windows 7. . . . → Read More: SSL on the Nortel BCM

Bandwidth Issues Are Odd

A couple of days after I had updated a series of products within the McAfee EPO, I started getting complaints from users about slow access times over the WAN.  After running a technically intensive test (ping) I determined that their complaints were well founded.  In an earlier time I would hop on the router . . . → Read More: Bandwidth Issues Are Odd

The Amateur Nortel BCM Log File Parser

(UPDATE:  I’ve recoded this in a much better format, go here to check it out)

I feel bad about having never packaged this program into a more usable state, something along the lines of say PsychoStats, but for phone records.  Anyway below is what I have, if someone can make use of it without . . . → Read More: The Amateur Nortel BCM Log File Parser