The Quick and Dirty Reference to Cisco Call Manager Express

Printer Only Link

In seriousness, if you’re all wired at home, or you are interested in wiring up your home for multi line telephony or have the ability to answer calls from a number of phones or internally call people from within… I think given the consolidation and the access to them, the recommended path is to Cisco. As much as I can’t stand a lot of their technology, you do not need to need  to have everything running on Cisco to do Cisco telephony. Being frank. I have switches using Netgear, and I have some third party endpoints.

Click below for more, and jump to six different parts

Continue reading

The News With Shepard Smith Begins Tonight… Predictions

It was Gram’s 79th birthday last year, October 11th, a Friday fall afternoon. 3:59 pm Eastern Time. I am having a late lunch. I can hear the TV in the dining room of which Gram is watching. I hear context of self-reflection. I also hear something about contracts and leaving. I literally run to the living room and saw the abnormal closing of Shepard Smith Reports on the Fox News Channel; using my ears, I knew he was gone. Both of us looked puzzled Because our box has a DVR, I rewound back 2 minutes before to see it again. This time, we see the leadup to to Neil Cauvto who went like “wola” and was felt he was thrown under the bus. In fact when you see the last jib cam shot, you see a group of people on an Avaya phone almost like coordinating his shadowed exit. 

Ironically Emily Rooney’s show on WGBH was on tape that evening because it was the upcoming Columbus Day Weekend. Did the panel follow up and made a segment the following Friday? Nope!  Not to mention in January she made a remark confused of where he was on the channel. I said he left on the week y’all off! Brian Steltzer had a tingle in his eye when the news broke at CNN.

Nevertheless Shep’s disappearance (whether you like him or not, whether or not you like his politics or whether or not you approve of his sexuality) was a huge void missing in cable, of which I am pointing to YOU COVID19 and POTUS & Friends! The news of Shep moving to CNBC was announced in mid to late summer and promos are running on CNBC’s air this week. His show begins tonight 7:00 Eastern on CNBC.

My predictions:

  • If you wanted balance and stable coverage on COVID19, Shep is the go-to guy. If you were missing better coverage, Shep being off the air didn’t help
  • There will most likely be some business and market coverage. That 7:00 ET slot had been reserved for emergent market events; and Shep can do that either on his own or help with his new CNBC team
  • Will Shep chase the storms in studio or in the field? That may not be out of the realm of possibilities.
  • This may not occur, but CNBC is due for a massive rebrand….way overdue. Because the dark blue colors of graphics and set have gone for too long. In fact in it’s 31 years, nearly half of it has been around dark blue/black; whether it’s graphics or sets and/or both. CNBC’s history has not had many years had vibrant colors. Their current studios is roughly 17 years old, and for at least 15 years, CNBC has had a lot of dark backdrops and lighting in the largest part of the building, the newsroom. You can’t tell me that it’s growing mold and other elements of sick building syndrome, which actually what SBS stands for.

Continue reading

How to Implement Cisco Call Manager Express at Home, part four

TFTP: (Sometimes known as the “CUCM address”)

TFTP and call management in Cisco land is the same. It’s assumed you are treating your router to just do voice, and you’re not mixing this with another network like an ASA or an AirPort Express with it’s own IP network, etc. (I am not the only one that had this inexperience.) You use SolarWinds or tftp32d to insert new files to the Cisco router; then use the tftp-server command to serve the files for the actual sets themselves. You typically don’t use the laptop/management PC’s TFTP server to have the phones get their files. Why?

TFTP and call management in Cisco land is the same.

Now depending on the files, you’re going to have to do this individually. If you have some mind in IOS, you can do in config mode, tftp-server flash:loa [first three letters of the file, then Tab] you can speed up this process. This flags the files living in the flash: directory this can be spit out to the TFTP server you have previously set up. Ensure that in config mode your tftp-server source-interface is set on the same network/subnet that the VOIP is running under.

Your going back to the telephony-service function yet again, this is where you enter in the “Loads” for your Skinny phone. Why if say it works out of the box and it registers? You may run into some bugs. My Cisco 7970 which I’ve had for years; didn’t understand the quad-lines very well, and it locked up, and sometimes would constantly reload. The firmware dates back to CME 4 years and perhaps it needed a little more up to date code so it would work better.

You type in the telephony-service prompt in config mode the following:

load 7970 [filename without the .loads, or .default]

change the model number if different from the example

There’s roughly 6 files, and it’s best you put them in the order that the other documentation has it.

The Cisco IP Phones basically phones home via TFTP and if it sees a new bootloader and firmware and checks against what it has, it should restart and attempt to upgrade.

There are catches and gotchas, ensure you have read Cisco’s documentation on upgrading, because hopping well past major versions will make the phone become a brick, or totally just ignore the new files. For an example, you can’t go to version 9 unless you have patched to 8 if the version is below 7. Understandable for IP appliances, yeah?

*

How to Implement Cisco Call Manager Express at Home, part three

The Numbers Game

There are several types of telephone numbers, known as “tags” to identify the individual extensions, sets, etc.; similar to how an Internet routing path works.

ephone for [Selsius] Ethernet Phone, or known today as Cisco IP Phone (the company Cisco acquired in the late 1990s)

ephone-dn for Directory Number (easy if you came off from Nortel)

voice register pool for a SIP Phone, whether it’s a Cisco or not

voice-register-dn the number for the SIP phones or devices

SIP and Voice Registers are in a separate post. As of this writing in 2020, the CME releases prior to 9 are essentially becoming End of Life; and SIP is now becoming the only protocol Cisco will officially support, no new models since the mid 2010s uses SCCP exclusively; though CME doesn’t work well with SIP natively if you have the 7900 series with SIP firmware. Since version 11, it only handles SIP at the desktop level, SCCP only works if you still have the VG200 analog phone gateways; or the smaller FXS cards. The more recent, 7800, 8800 and 9900 models only runs on SIP protocols. In reality, SIP is much more mature (but still not the best VOIP protocol around), and the newer generations of Cisco IP Phones with the SIP stack reflect it. The 7900 was never really intended to take all the lack of benefits to SIP and not only that the very original generations the 79×0 models limited it’s use to support BLFs, the speaker was half duplex, and the audio quality was at level of a POT set, over a set that had a Skinny firmware.

Trunk mode: Key System (“Call on Line 1”)

As much as I admire the 1A2 systems, and my poor fine motor skills, I don’t want to forget history of the largest types of systems, PBX are actually a microcosm in the telephony world. If you got a 796x, this will be easy; without loosing button space for other line appearances.

In this example, this would be a dummy extension

CORE1(config)# ephone-dn 60

CORE1(ephone-dn)# number 200

CORE1(ephone-dn)# label Line 1

CORE1(ephone-dn)# name Line 1

If you have Call Waiting and you enabled Switchook flash in telephony-service, you could set this up to be a dual-line, to achieve this, to do that, all you would need to do is add  “ephone-dn 60 dual-line” to the end if you did this already, and made a mistake you will need to remove it (using “no ephone-dn 60”  as the example) and reenter it as such.

FXO Configuration (voice-port)

Now it’s time to define that FXO port to match that dummy extension. Now you’ll branch out to the trunk level and assign various commands to make this work:

CORE1(config)# voice-port 0/1/0

Which means on the Cisco 2801, it’s on router  0, slot 1, port 0 (the female jack),  similar to 01A0401 on say a large Avaya PBX.

CORE1(voice-port)# supervisory-disconnect anytone 
CORE1(voice-port)# groundstart auto-tip
CORE1(voice-port)# timeouts-interdigit 6
CORE1(voice-port)# timeouts call-disconnect 28

I use this because the Xifinity Digital Voicemail, and if no one answers by the 6th ring, it stops ringing. If you do not have this type of timeout, the router “answers” the call and rings to the command below. If you do not insert this, the phones will “ring off the hook”. In fact it concerned one of my grandmother’s doctors who just happened to call on the same day of the final cutover, and I realized I omitted it.

connection plar opx 200

This means it will connect to a Private Line Automatic Ringdown to Off Premise Extension of 200, the ephone-dn 60 for the dummy “Line 1”. Ironically OPX must think the extensions is off premise to the router’s mind.

description Comcast POTS

caller-id enable

If say you wanted only one phone to answer the call (which this would act like a PBX, where a single point of entry), you’d use the DN that is of the extension you wanted to answer, such as say 101. For the home, it’s easier to lump sets on a dummy extension in case of some network flare up that caused a phone to go down, someone unplugged a set, etc. I’m a clumsy guy, and if you had one set go down, a busy signal would generate on the other end, because no device is able to ring.

There was some issues where the phones would ring once every 10 minutes or so. Upon a google search, I found entering the following in the config mode, this helped

voice class custom-cptone Comcast

 dualtone disconnect

  frequency 480 625

ephone-dn (Extension Number)

As previously explained, the ephone-dn is for the extension. In Release 8 and higher, there is more than just an option dual-line, but an octo-line. Octo means 8 different instances of calls can come into a CME  instance without a busy signal. Though in Cisco, your call appearances are virtual and requires juggling using softkeys and no hard keys like how Avaya is known for. With SIP, you could return back to the Avaya-style as call-waiting or appearance buttons are device-centric and not phone system specific, which in a lot of ways could be easier. In fact octo-line is designed for call-parking, which will be discussed in the future.

Depending on that PVDM that’s required to anything, even if you were just playing with commands, the more instances of calls will chew up resources on the PVDM, even if you are within the limits. This is because after you assign a Cisco IP Phone, the ephone command already populates the  lines after configuring, so that means that phone will have dedicated lines literally.

The SCCP protocol can support up to 200 simultaneous calls, but that’s more for say a UCM, and given how it can’t roll over to another idle button like an Avaya; it’s an overkill; especially when it’s line specific, not phone specific. It’s better off being a dummy extension than anything else.

Setting up Cisco IP Phones

If you did the ephone-dns for all your relevant extensions; and you’re in no hurry to add BLFs, you could in theory use auto-reg-ephone in the telephony-service function, and plug in the phones one at a time, to then to match extensions to phones. But if you want to do more, one at a time maybe your only  bet

For all intensive purposes, start with one. In config mode enter the following

CORE1(config)# ephone 1
CORE1(ephone)# mac-address 0000.0000.0000
CORE1(ephone)# type 7970
CORE1(ephone)# button 1:1
CORE1(ephone)# button 3m70

In mac-address use the MAC that is on your VOIP set that you’re adding ensure it’s split up into threes and add a “.” every 4 characters in the hardware address.

For all intensive purposes, “button 1:1” means Button 1 is tied to Directory Number 1, extension 100; button “3m70” is functioning as BLF for the dummy extension of 200 that’s acting as a Key line and is monitoring the line; you can access it and it will ring when the number receives a call. And I believe you could use 0s for MAC addresses if an event you’re waiting for a new Cisco phone to ship and use it as holding till the set arrives. I know this can be done in voice-register, but didn’t verify with ephone.

*

TMOT: Analysis (The History of Telephony)

As part of divesting content from The Museum of Telephony, anything identified by moi has been sent back to me as being the rights holder. 

Steven M. Clickford

As I am writing this history, it’s 2020, nearly a century after the Spanish Flu; and the midst of the growth of telephony that grew around that time. Also: our country is more divided, not just red and blue, not just Republican or Democrat, not Ford vs Chevy, not Nortel vs. AT&T or Avaya Red vs. Avaya Blue. We are up against a very divided country; and allegedly the U.S. is dealing with what could become the deadliest pandemic since 1918 known as COVID19 or the novel Coronavirus from China. In the technical sense of division; from the mind of an engineer, conflict brings innovation; but from a customer, division confuses them; from a business standpoint since the 1980s, it’s all about making money and being rewarded with cash… but what do they do with it? Sit on it!

What about the middle class? Why is my Cisco phone “Made in China”? What about the people who were proud to work at Ma Bell at the repair plants? What about the Boomers and people like my gram’s age who is very sensitive to reliable telephony?

We have forgotten what made the past so great that brought us the present. Too often Americans (by choice) want to have short attention spans. Americans do not care about “the past” they by choice “want to move forward”. Today many Gen Z (the youngest generation coming to age) want to spend money on “experiences” completely opposite to the Baby Boomers of yester-generation. But like the Boomers, they want things cheap and will laugh at the price of an iPhone; but yet will whine about the “monopoly”.

The so-called “monopoly” by the technologists today is far from what it used to be. AT&T would’ve been shamed if they were hoarding cash or gave a Western Electric exec stock options, since stock options wasn’t really a “financial instrument”. The Bell System was for sure corrupt, at some parts of the company. For whatever reason some other groups felt “secure” that their phones worked, that they had “service” that they “took care” of their customer. The ones who had a grudge was people who were fixated on price, the engineer who didn’t like using a telephone, and wanted to extend the Internet, etc.

AT&T would’ve been better of breaking up the communications equipment; go into their failed attempt in computing, and then keep the all local telephone service. The company was loosing margins on their Long Lines (or long distance services) from the 70s to the Divestiture.

What the 1984-implemented Divestiture caused

  1. allowed dog-eat-dog, cut throat competition.
  2. Shareholders came first; customers, employees came second (MCI was known for cheap long distance service; the amount of customers and cash coming in resulted in a high stock price, enabling “insiders” to use MCI as a private bank to leave the company, start it up, if it succeeded or failed, they’d return back.)
  3. Local telephone service was under siege by the Telecommunications Act of 1996; ElChea0 Telephone could by law co-locate with a Baby Bell central office, and the Baby Bell had to comply!
  4. With the Telecommunications Act, this forced Baby Bells to merge and consolidate, to grow their profit margins (remember shareholder-first)
  5. Lenient laws for “innovation” = new markets, but enabling sub-par standards (such as crappier audio quality)
  6. Lenient laws to “maximize shareholder profits”, taking skilled labor (whether you like unions or not) out of a job.
  7. “High tech” companies brought today’s new economy on zero regulation, with zero corporate governance, and zero accountability, forcing customers to “trust” these “digital companies” that reinvent (err rewriting) standards/policies/goal posts to throw smaller people out of business (Baby Bells, etailers like Amazon and eBay)
  8. The consumer is more confused by whose the villain or the hero in the economy, when in reality the populous views is far from accurate (the smaller “innovative” companies are profiting like crazy while the service providers are being sucked out of cash, even though they are pocketing customer’s money too.)

The fact is, that after the breakup, the very same thing the market wanted would actually be the beginning of the end of telephony, or standardized telecommunications, the end of customer social norms, and the inmates controlling the asylum (the shareholders and corporate executives.)

I was born 3 years after Divestiture. I didn’t follow much of AT&T’s past, until a few years before the first carnation of The Museum of Telephony. The old AT&T’s reputation was tainted by popular opinions that was probably conflated facts. The Divestiture confused a bunch of customers. Post Diveisture, customers were confused. Like some techies, some looked up to IBM even if they had skeletons in their closet, mine was literally AT&T (the competitive company of course.) I literally saw Ma Bell literally fall to her death. I remember they spun off NCR when 5 years before they bought them out as National Cash Register, the same year IBM divested ROLM. I remember AT&T’s buyout of TCI, then Media One, to then sell them off to Comcast. To then see AT&T basically sell themselves out to SBC, the Baby Bell of the West Coast and Connecticut.

The AT&T after 2005 was basically a Baby Bell inheriting their mother’s name, but still operating in that dirty corporate culture that America so wanted so badly in the 1980s; that they are bitching about today.

Lastly, because of the “cutting edge”, progressive, anti “antiquated” tech mindset, the 1 year refresh cycle (remember the 3 year cycles in the Wintel/Cisco world?); as technology has evolved, there is rarely something, that is a thing, an object that unifies us. Most Millennials can’t tell a story of a item that others shared, except if you’re like me a deep techie. But for the older, non techies, that infamous plastic clad, 500-type rotary dial telephone, brings older generations with stories or “remember-that”?

For the human side of technology, the best unity was before PCs, clearly before mobile phones, and anything that was made prior to 1987, let’s just end that the year I was born was the end of unified technology that multi-generations can relate to.

For many of my audience, I’m an old heart, and don’t subscribe to IT-group-think nor do I care for today’s consumer tech. This narrative was written out of respect of the technology that long came before my existence, because I knew there was a world before I came onto this planet too!

How to Implement Cisco Call Manager Express at Home, part two

Setting up Cisco CME without the setup command

For versions prior to 8x, the “setup” command has been “depreciated”, but yet it’s still seen on the Cisco router. It literally gets bitchy and basically tells you to eff-off and configure it the more complex way.

Also for $85 in the summer of 2018, it did not include the GUI. While I had an image for the GUI, it was for Release 4. And yet all the nerds love to brag doing everything in terminal  I also defend GUI because it also helps you for the small things, like changing the time at the end of the Daylight time, if you happened to fudge it up, or you want to change the music on hold, stuff like that. I consider the GUI to be the admin, and the terminal for heavier lifting tasks like the routing, etc.

If you so choose to, you’re going to have to set things up line by line.

If you have not assigned a DHCP pool yet, and the VOIP VLAN is separate to your data VLAN; you’re going have to enter (if you don’t have a DHCP server for the sets)

ip dhcp pool ITS*   

network 172.18.2.0 255.255.255.0

option 150 ip 172.18.2.2

default router 172.18.2.2

dns-server 172.18.2.16

* I used “ITS” for the sake of legacy uses because this is what would’ve been entered for the name if you had “setup” still in use.

Network means the server will spit out IP addresses along the network it’s bounded on, by the IP address set up on the interface. I used FastEthernet 0/0 because I felt internal/private LAN should be on the lowest port possible. Your option 150, handles the TFTP server, which will need it’s own discussion later.

Now enter telephony service by entering in

CORE1# telephony-service

Now you want to tell the router how many Cisco SCCP phones you want to have, say

CORE1(telephony)# max-ephones 24

For the number of extensions, double it plus a few more (especially if you want to do paging and Key system functionality)

CORE1(telephony)# max-dn 80

you want to remind the telephony service where its assigned on

CORE1(telephony)# ip source-address 172.18.1.2 port 2000

where port 2000 is the default pipe for Cisco’s SCCP

Do you want to change the line of “Cisco Unified CME” (that on the big CallManager it’s known by “Your Current Options” above the softkeys?

CORE1(telephony)# system-message  ((')) Merry Halloween (('))
CORE1(telephony)# voicemail 8*97

The voicemail button could in theory dial any pre-defined number, and I just used the most likely default carrier number if you don’t have Unity Express installed.

CORE1(telephony)# moh music-on-hold.au

ensure your music-on-hold.au meets Cisco’s spec and it’s living on the flash drive

Entering IP phones is not done in telephony-service at all. This could be because it could be used for SRST functionality, and they kept that prompt at the low level.  You can’t do SRST and CME at the same time.

For more on how the numbers game works in Cisco CME, it’s got it’s own page.

TMOT: Lorriane Nelson Profile (AUDIX Voiceover)

I had done an email interview of the once well known voiceover to millions of voicemail boxes domestically for The Museum of Telephony in 2016. Since I no longer manage TMOT nor did the new management care about this highlight, I’m allowed to retain the rights and have the original piece featured here.

There was as sidenote in 2019: By winter of that year; there was an attempt by your’s truly to reach out to her to do an actual interview (whether it was to be a phoner or video call; she did respond and was willing to do so, March was the start of the planning process; but the decision to drop it was me; as ongoing personal conflicts prevented me from doing it altogether.)

Welcome to AUDIX. For help at anytime, press star-H. Please enter your extension and pound sign.

Default AUDIX Login prompt

In part of the continuing series of the early history of modern day Avaya PBX systems, you humble curator had actually reached out to the “Voice of Voicemail”, Lorraine Nelson. I would like to thank her for her cooperation with the project.

image of Lorraine Nelson from voicelady.com

Image courtesy from voicelady.com

This investigative project is mostly the background to the voice behind the legendary voice mail system, that has been branded AUDIX (the acronym known as Audio Information Exchange), Intuity, Modular Messaging and smaller systems like Partner and Merlin Messaging. Technical information or specific dates or years is not part of the narrative because she doesn’t have that information. Regardless, the early days of the enterprise voicemail system has some interesting history in itself.

 Despite her claim to fame, she was not the first voice of Audix.  According to her, a woman with a Texan drawl (the person’s name is unknown) had done the prompts for at least Release 1. The Bell Labs team wanted the voice to sound more New York, however they didn’t know where to go. Hey I wouldn’t blame them too. In the world of business, if you had a Texan (or heck someone from the West Coast) giving you prompts, would you go asleep or a loose a prospective customer? Especially when a product of AT&T was about to evolve into the competitive marketplace during the time Divestiture?

A man who had once worked on a Bell Labs project of a system with an A/V interface that could bridge such equipment in various rooms or classrooms through a telephony system; was tasked to find the voice. The said project is believed to never gone to market. This manager called a film producer in the Yellow Pages and asked he knew any voice over talent. The film producer had recommended a radio talent to the Bell Labs manager. They spotted a radio news reporter in the Denver market who worked at KADE in Boulder, then KADX going by the name “Lauren Hendricks.”

Despite the illusion of multiple personalities (read below), the woman they found would be Lorraine Nelson.

(On a sidenote: I guess name spoofing wasn’t just isolated to the world of Shadow Traffic or Metro Networks reporters! I never understood concept of a same voice, but  different names on different radio stations – thought it was always a slap in the face to the listening audience’s intelligence.)

Editorial aside, this was probably the best move. A native (and now a resident again) of Connecticut, as she told me where she “grew up to speak properly!” who also studied at the University of Colorado with a Communications major – not the telecommunications, but in the radio, TV scope. She met their crieteria – but could she pull it off?

 After the discovery and making the decision, she would arrive to a frugal Bell Labs factory, with low end technology with no quiet place to record since this was a manufacturing plant. Not only that, apparently AT&T could’ve paid her a little better for such an enormous task.

 How come? What they had was a reel to reel tape deck in a cubicle, and apparently according to her they wanted to mimic (in her words) a “telephoney” sound. Because of this low tech practice in a dark time in the 1980s; people didn’t like the voice, and it felt too quick or abrupt. They gave her another chance to re-record the fragments this time they didn’t over direct her. By this time she interjected her own personality (and from seeing that other video – this would explain the “nicest secretary” vision.) This seemed to help according to Nelson and kept it for Audix 1 and 2 (again released in mid to late 1980s most likely.)

Despite publicized peer reviewed reports on the System 75 in January 1985, with developers touting the design of the human in mind, the Audix team apparently didn’t have the interests of the users in the beginning according to Nelson.  She would record nearly a thousand prompts (known formally as “fragments and menus”) into the phone at the factory after the work day ended there and had to go through each one and dial it in to be able to record, enter the fragment number, press a command to playback, and if it didn’t sound well to hit a command to rerecord. She was annoyed at how she would record it without any problems, but the system would cut off part of her speech.

 Essentially what she did was no different than a customer getting root or Administrator access to the system and basically change the voice prompts, because in modern voice mail systems if you dislike the voice over you could in theory rewrite their voice. (If only I could get those 100 prompts to rewrite my Asterisk box it would be so awesome!) In the early days, there was no studios, no MP3, WAVE or AIFF PC/Mac based files; this was a simple rewriting over the voice of that Texan woman by logging into a telephone and press buttons to do the overwrites.

 Because the AUDIX history (at least in the mid 80s) is hard to find and hardware probably been vanished from Earth (and thank you Avaya for destroying your historical collection!) I could possibly speculate how they would reproduce the new voice on newly produced systems. I can imagine that the new AUDIX became test machine for the new voice in the shop; perhaps take a backup of the new voice and just insert them into the new systems and do it over and over  – since afterall she was recorded this first version on the shop floor. (And phone systems, mind you, don’t get reproduced often like PCs, like making thousands a day. A lot of times, these specialized systems would be made specifically for their customers near the time of purchase.)

Reflecting this primitive procedures, one would consider the production or development of this system as a glorified answering machine despite the very high rich, expensive nature of the equipment. First thing I compared this to today’s standards was, if say a friend with a good voice you wanted on your answering machine, and he recorded it on an MP3 send it you and play it off a BlackBerry. (I did this before we moved to a new house and use the service provider’s voicemail.) Or even 25 years ago if you wanted friend to record a quasi professional recording on a micro cassette player for you on those other tape based answering machine.

She would come in for changes over time including additional work for Lucent (by this point) recorded with enhancements to AUDIX, a faster pace, voicing over for two commands per prompts (oh I mean “fragments” and “menus”) and provided the voice for the Partner Messaging and Merlin Messaging (mid to late 90s) as well and even the IP Office in the last decade. And by this time it was more professional and was recorded digitally as well.

 She is still strong and active, and still heard by millions (including your humble currator, when his mother occasionally misses a call made by me to her office set.)

Note: Many thanks to Lorraine for her cooperation, answering and the prompt response through email. If only there would be more people that could send meaningful email within a few minutes, it’s a rare exception. 

*