Why I’ve Been Forced to go to Unified Communications as a Consumer, Part Two

Back to me, myself and I: Why did I have to jump to consumer UC services?

Over the last couple of years, I have done more texting, chatting, emailing over voice; because the people I talk to have desk phones that are VOIP based. Of the few, they are using Allworx. They are just lousy phones! Once these cutover, the heartless IT admins who hate their users and get paid to hate, will not touch any of these phones. (Don’t get me started with security risks and reliability issues.) So as a result, I email. Until the email servers go down on the other end because the Exchange admins think patching a server at lunch time and not understanding customers emailing their to that organization while they are on their lunch is most likely occuring.

Continue reading

Why I’ve been Forced to go to Unified Communications as a Consumer

Unified Communications is pretty much a broad term now then it was a few years ago. Originally it was IP Telephony with SIP and other goodies; now this terminology and technology has evolved into multi media applications embedded in social networking and social media. In 2016, your Facebook Messenger is also a “phone”. And now you have more “professionals” at your local Starbucks using their VOIP app to make important “business” calls in a noisy environment and let’s assume Starbucks has QOS and say multimedia isn’t on priority in some locales. Some stores use AT&T, some like in my town uses Google, it depends of what their ISP is and how much data it can handle.

Continue reading

SIP Experiences, part two

SIP is like a PC, it’s a great technology. It’s like “I wanna have a computer on my desk but I dunno what I really want out of it”. As the 1990s came along, these little things became a nightmare for network administrators. Not only that but PCs had too much power for what many people didn’t need. What I am talking about is enterprises not consumers.

SIP is in fact much like a PC.

Continue reading

Dev Notes: SIP Expierences

Today’s writings is the memories I’ve forgotten without regrets (or whatever party animal line is) about personal runins with the Session Initiation Protocol better known as SIP.

These runins were not done when I was drunk, nor were these done professionally, and if I had a LAN party related to telephony maybe these stories would be more funny.

Continue reading

Phones @ Work – Local Walgreens


This was a recent photo of a Cisco 7961 taken at a local Walgreens. Once a Norstar shop, I’ve been told by someone familiar with the company had cutover to Cisco company wide. Apparently since the last time I visited (which could’ve been a couple years now) they are using them.

It appears to be a Cisco Unified Communications Manager tied to some corporate data center (notice the “system message” stating “Your current options”) and if an event it can’t get through  to the data center, then you get some different message such as a fallback warning on that same screen. The paging does loudspeakers, but I’m not so sure on the sets, because the larger CM does not support set paging. (I could do a post on the lack of features in UCM 10, but then I’d start a religious war and be framed as a Cisco hater, and stuff like that.)


Rants: Sales & Marketing’s Abusive Telephony Agenda

If you thought the previous post on lies about TDM PBX not capable of modern telephony was good, then to use the ol Ron Popiel cliche But Wait There’s More!

This post will be a little raunchy, I should’ve posted this on my personal site, but I couldn’t help to resist when I got a couple off-site feedback from people defending my first one, so “the hits keep on coming!” I hope.

This same site had another post from some dude that can’t tell ISDN from T1 or that anything that supports TDM telephony because afterall TDM is automatically native to VOIP technology. The practices of torture, lies and manipulation from S&M (now did you get the innuendo?) is just getting complex now. Anyone that wants to push SIP as a be-all-end-all solution is now getting pushed to customers who can’t a) fight back or b) they don’t know anything about telecom/telephony so they’ll take a solution and in many VOIP setups w/out telecom support, they leave the system abandoned and most often the VOIP system plus the S&M types push and torture, will often be unsupported, phones crashing, users wanting assistance to then be denied by the heartless IT administrators… (why am I writing this during the holidays when this should be more of a Halloween themed post?)

Continue reading

Phones @ Work – Mother’s Workplace – Avaya 9608


In honor of Mother’s Day, I took a picture of my mother’s desk set, an Avaya 9608 IP telephone. I visited her workplace the other day (shh, don’t tell anyone!) I woke up the phone to see what kind of goodies the set has. Not so much. Her set can handle up to 24 call appearances or feature keys  and as I was scrolling up and down I kept landing on the same 3 call appearances.

Unlike the 4600s, the 9600’s scrollable screen also features dual LED lamps. As you scroll down, the LED lamp moves as a way to assist where you are on the virtual keys. But get this, my mother is funny with her OCD – after I messed around with it, she scrolled back to the first button but accidentally picked up the handset, which automatically goes to the first available call appearance!

This setup is interesting as well as she has dual ethernet cables, one for her dockable laptop, and the other for the phone. It could be because it doesn’t use POE or maybe it is on a separate LAN (defeats the purpose of converged networks – but there’s a method to a customer’s madness I suppose.)





Implementing Asterisk

I’ll be doing a series on Implementing Asterisk. This subject is about VOIP*, to some is sexy in terms of lower costs and high benefits like click to dial, Active Directory Implementation, etc. etc. VOIP is  really not a sexy subject, especially when implementing and set up the idea of reliability, security and resiliency. This could be the case if you are someone who hoards alot of analog phones and TCP/IP knowledge is second hand knowledge.

This is a work in progress and these are my documented notes to provide as a service to my followers if you are learning IP or learning VOIP and ether don’t have experience in networking. This series will bridge them together (at least that’s the intent.)

* I use all caps for most of all abbreviations/acronyms even if “over” or “of” or “as” are lowercase. I come from the background of using capitals just to make it look more professional and not some CraZY MySpAceGirl. 🙂

I’ll be talking about a project implementing basic VOIP services for a customer as a lab project. Before I go on I am keeping very technical details vague or withheld as this project is beta testing project for a customer of which I want to keep it confidential.

Lets drill down quickly on the Asterisk softswitch

  • Contrary to the belief by the PC geeks, Asterisk is still and will never be a true “PBX”. Or at least compared to the ones made in the last 30 years. Asterisk is basically a PBX equivelent to the ones made before the digital ones, where it could make calls, receive calls and do other basic things in the modern sense like basic voicemail, basic conferencing and basic paging (if you’re lucky to get that accomplished!)   Most I have seen in the various distros, the Asterisk can max at about 400 terminals and I don’t know tens of trunks. The Asterisk (and it’s respective distros) still miss out on many core PBX features that still haven’t been able to be reversed engineered.
  • It’s mostly a snapon Linux service (that is more painful to snap on unlike a Windows service, without a distro.)
  • I’ve used the now dated TrixBox CE, but also trying FreePBX and Elastix. Elastix is cool though in my application, I am using IBM Lotus Notes (transitioning from an MS Exchange setup) so I really don’t need email/calendar but the IM to me can be relevant in an IPT/UC setup. The official Asterisk releases I wasn’t too thrilled with, and release 1.7 I got reservations. The GUI one in R1.7 uses Google cloud UI – not good if you don’t trust in Google.
  • Networking. The most amusing thing from these PC guys is you never hear QOS, VLAN and ensuring at least a four-nine reliability. The PC geeks believes everything will “plug and play” nice. If you think you can brag about setting up a “PBX”, think twice before you brag if you aren’t familiar with IP Networking  Read on

Now I will focus on networking aspect as this is the core component of implementing any type of IP based PBX. (Including systems like Avaya’s IP Office which I run elsewhere at home.)

I am no networking expert, Three Letter Acronyms or TLAs go over my head, and often explaining things without proper detail or explain how each IP network are supposed to talk is limited online. I am the guy who likes things that will plug in and play when  everything set up exactly (like TDM.) Sadly the IP and cyber world is not exact, physical and/or logical.

Hardware Setup

On the data front, I have a heavy data setup with mostly a single server running mini operating systems within a VMware server. Typically the CPU runs about 6 out of 9 production OSes, including an Asterisk (the TrixBox). The server runs on a dual core, 64 bit CPU with 8GB of memory with the ability to max on a quad core, 32GB RAM with specific 4GB modules per slot, which is the long term goal so I only will have to worry about one physical server. Of course, I’d like acquire a backup server in case the primary fails, which requires more money.

I standardized on ESXi since early 2013, but later changed to a VMware Server 2.0  because it doesn’t gel well with hardware and because of its 8 or so year age, it couldn’t do CPU virtualization or even mount USB ports or even detect any generic PCI cards that a VMware Workstation can (fax modems, backup Ethernet cards, etc.) This server ran ESXi 5.1 even when it wasn’t supported officially (which was a pretty cool version of the hypervisor), but unfortunately I had to go to a 64bit Windows Server running Server 2.0 on top (so I can go beyond the 4GB restriction if I went w/ the regular 32 bit release.) This tradeoff also works in case of a disaster (which this occurred in March before the downgrade) because a compatible VMware Workstation can take the virtual computers file and run (which eliminates the flip-and-convert process, which can take lots of time.)

What does this mean to the voice network? The Domain Controllers, private email, messaging and web and file services do take a lot of internal bandwidth (CPU resources are probably the most clogging). The file server is the common driver for the data traffic as files get stored, opened or moved, printers receive items to be printed and sometimes large (ISO discs) get moved onto this virtual file server. By the way: Asterisk currently runs on this same server.

The Asterisk VOIP System

The current setup are two Mitel IP Phones running on SIP firmware. The models are 2 5224 IP Phones, with paper desis. I’ve never used any Mitels before, only familiar with them in passing mostly the Superset TDM phones, like this guy I’ve posted a while back. Mitel’s IP phones at least in recent years have gone towards a cloud setup, even before “the cloud” got its name. Some phones I’ve seen from resales had logos from service providers like Sprint. Unlike Avaya, Mitel’s focus on the cloud is the hardware (like IP phones) while Avaya’s marketing is more software and in house or cloud based social platforms and less push to sell phones. (Always an equal opportunity offender here even if I am Avaya biased!)

Anyway, in this situation, I’ve set up the Asterisk as a form of SIP gateway. It will later be setup to have external VPN access through this system. This is mostly an internal communications system with a later plan to tie this to a PSTN remotely.

Think of this as an ol’ in house Centrex. Basically the featuresets are the standard Free PBX plus any SIP endpoint’s feature sets. Mitel supports on set call hold, shared line appearences, distantive ringing, call forwarding and Do Not Disturb.

The problem I am dealing with is spotty coverage, calls getting jittery and a lack of full fidelity. I realize some of this could be the virtual server itself . The Asterisk is running on 256mb of RAM and a hard drive about 40GB. I will have to put blame on some of it being a bloated Linux server, and another part not having an appliance, like a little hardware device.

Now some Avaya or even Cisco people would laugh at why would an Asterisk choke on such specs when an Avaya server with those same specs (sans a VM format) run fine at a max of 15,000 (IP only) for an Avaya or nearly 5,000 on a Cisco?

A part has to do with the protocol. I’ve come to understand that the first generation of VOIP/IPT systems were dependent on external hardware devices, and the phones running on a proprietary protocol like an H323 format. Avaya’s protocol that allegedly was modeled off their DCP (see glossary) and Cisco’s Skinny required a hardware endpoint to ether ring a non IP phone or to dial out, what’s known as a voice gateway. This didn’t require using the entire resources of the media server (known by some as the PBX).

SIP on the other hand is strictly software and strictly app based, since you know you don’t inhale your coffee, you “sip” or even your appetizer right, hahaha?

It’s so true. It is an app and it is very important to understand that the SIP protocol essentially makes your non H323 IP phone basically a switch in the phone. However to talk to other IP phones or non IP phones or to dial out, it requires a server and an application server to do this. This can be a pitfall depending on how much resources you have and how many phones and how important voice is to your enterprise. If you are using a low end PC, it might barely handle 5 endpoints.

Part 2 coming soon, notes for deployment and ensuring reliability.