Author Archives: networkchief

Firefox connections to CCMAdmin fail

Over the past few weeks I have been plagued with having to modify Firefox to permit connectivity to sites using SSLv3. It appears that Mozilla is trying to limit access to vulnerable sites, but that creates some issues for those of us that haven’t updated large components of our infrastructure. Even more troublesome, I am now having to modify these settings for users since they need to run reports…

In case you haven’t seen the errors, copies follow:

Capture

Capture(1)

The workaround, is simply enabling Firefox to connect to sites with SSLv3 vulnerabilities.

  1. Within Firefox, enter “about:config” in the address bar
  2. Read the warning, I do not accept any responsibility for what happens within. If you accept the responsibiltiy, select the optino “I’ll be careful, I promise!”
  3. Enter “ssl3” into the search field
  4. Ensure the preferences “security.ssl.dhe_rsa_aes_128_sha” & “security.ssl.dhe_rsa_aes_256_sha” are set to false.

Now, we just need to update some servers, phones, more servers, clients….

Call Signaling – It’s for POTS too

This last week I had an annoying experience while trying to get two POTS lines tested prior to connecting to the voice gateway. At the end of the day I thought it would be worthwhile to whip this up into a blog post as a reminder that call signaling is important to understand, regardless of the technology.

After the service provider fully displayed their inefficiencies I had my lines installed about 4 hours later than planned. While I had the service provider engineer there, I wanted to verify the lines were working as anticipated. After placing outbound test calls I connected them to the voice gateway and attempted to test inbound calls, where I discovered one line would ring in, and the other wouldn’t. Back at the demarc with a test set, I was able to confirm that the incoming call was indeed coming in. After some back and forth with the service provider engineer, it dawned on me what was happening, I wasn’t receiving any ring-down voltage for the call. After convincing him to get his meter, I was able to prove my theory. On the line that worked we would see the voltage spike for every ring cadence.

For those not familiar, your phone rings when it detects the 90 volts AC (normal voltage is 48 DC) being sent from the service provider.  In older equipment, this voltage was used to actuate the ringer, nowadays our electronic equipment simply senses the voltage change. For more information, please visit the wiki page. https://en.wikipedia.org/wiki/Tip_and_ring

As I write this, the issue still wasn’t resolved. The engineer didn’t know how to correct the issue, and his support had left for the day. Hopefully they can resolve the issue this week.