Essential Technology: A GCS Blog

A Blog About Business Technology Systems

About GCS

GCS Technologies provides technology services and solutions. You can read more about GCS at http://www.gcsaustin.com. GCS is available for project work covering the topics in this blog and other IT systems.

Fed Compliance

I know all of this stuff because I sell all of this stuff. I call it real-world experience, the FCC thinks it might be a conflict-of-interest.

Snow in Austin Means...Business As Usual?

by Joe Gleinser 28. February 2010 00:59

On Tuesday it snowed in Austin, TX. And when large, puffy white things fall from the sky, all of us at GCS, like many Austinites, fall into a catatonic state. "Look at the pretty snow." That lasts about 5 minutes until we realize we have to drive home with other Austinites equally mesmerized but traveling 70 miles per hour. After weighing our options we elected to close the office early. This was an easy decision because IT DID NOT AFFECT OUR OUTPUT! The Great Snow Day of 2010 was just another Real World Emergency Test of our remote access systems.

At GCS the phone rings about 300 times per day. It is the primary communication tool between GCS and our clients. Each phone call represents a client service request and revenue to be earned. This is very similar to most businesses in the world. How were we able to handle 300 calls per day without an open office? The Telecommuter mode on the Avaya IP Office.

Avaya Telecommuter mode is an add-on to the Phone Manager desktop application for the IP office. The standard Phone Manager product allows you to control your phone from your desktop (answer, hang-up, transfer, etc), but requires you to be near your phone for the actual call. With Telecommuter mode, you can tell the system you are out of the office and give it a phone number where you can be reached. This number can be a cell phone, home phone or any other phone number. When a call comes in to your office phone, the IP Office routes that call your remote phone. If you don't answer it pulls the call back and sends it to your business voicemail. If you do answer, you have the full range of Phone Manager features (transfer, conference, hold, etc) at your disposal to manage the call. 

You can even make outbound calls through the system without showing the caller ID of your home or cell phone! Simply type the number you want to call and click "Connect." The IP Office first calls your remote phone and waits for you to pick up. When you pick up the phone, it then dials out to the number you dialed. You have all the same features on an outbound call that you have on incoming calls.

Our staff left very early on Tuesday. Upon reaching their homes, they were able to receive both hunt group calls (like our incoming Help Desk, Sales, and Accounting groups) and direct calls to their extensions or DIDs. Most GCS staff members relied on their cell phones as the remote line. All of this took less than an hour, mostly drive time, with no decrease in the performance of our major business functions.

Telecommuter performed exceptionally well for us.  Our office was completely dark from 12:00pm through 6:00pm, yet we continued to provide a high level of service to our clients.

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList

Flexing Our Mac Muscle! - Avaya Phone Manager on Snow Leopard 10.6.2

by Joe Gleinser 23. February 2010 01:11

With recently acquired Apple certification in hand, JP McInnis is quickly expanding his Apple knowledge. First up, telephony integration! Mac users have suffered for years due to a lack of support for the Mac OS from most major telephone system manufacturers. On his Snow Leopard 10.6.2, JP mixed up some VMware Fusion 3.0.2 and a VM running XP Pro SP3. A short install of Avaya's Phone Manager later and enabling "Unity Mode" in Fusion, and voilà:

 

Avaya Phone Manager on Mac OS X

All typical functionality was present. We did not test TAPI on this system yet, but it's on the list!

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList

Voice Over IP with the Avaya IP Office and Sonicwall Firewalls

by Joe Gleinser 7. October 2009 17:18

We've long been fans of Sonicwall firewalls at GCS. Advanced features, easy web-based configuration, low failure rates and low cost make it a very compelling option for many clients. With the rollout of the new product lines Sonicwall offers the Enhanced Firmware features (most notably WAN Failover and Load Balancing) as a standard item on every product. My small office clients can now get WAN failover in a device for less than $400. This is a real cloud enabler. For a few grand you get WAN failover plus a High Availability configuration on your firewalls.

Today Avaya released a KB article describing how to configure Sonicwalls to prioritize voice traffic between sites. With the rise in popularity of MPLS and managed routers, we are seeing far more Ethernet handoffs than T1 handoffs these days. The Sonicwall NSA 240 is a great device to terminate that MPLS circuit and appropriately manage the traffic.

 

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList

SIP Trunking on the Avaya IP Office

by Joe Gleinser 26. September 2009 07:13

You've taken the plunge (or not) and are ready for SIP. Now, how do you configure SIP trunks on an Avaya IP Office?

  1. Buy licenses from an Avaya reseller (I can think of one). Each SIP trunk is licensed.
  2. Order SIP service from an Avaya-supported provider. 
  3. Your SIP provider will request a public IP address that has port 5060 forwarded to the IP Office.
  4. Reference the Application Notes with step-by-step instructions from Avaya for your provider here. Any App Note is a decent guide for any provider.

Not all SIP providers have Applications Notes at this time. However, if your provider is listed your Avaya reseller (*ahem* GCS) will be able to configure SIP service. If you're just getting started with SIP it may helpful to read GCS' SIP Primer.

SIP is a mature technology that will likley displace PRIs as the standard for dial tone in the SMB market. The IP Office offers both SIP trunking and endpoints.

 

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList

A SIP Primer

by Joe Gleinser 5. September 2009 01:01

If you're curious about SIP, you're not alone. SIP, Session Initiation Protocol, is a method for terminating dial tone or connecting handsets to a phone switch. It enables vendor competition on proprietary phone systems for the high-margin handsets sales. It also allows dial tone to be passed over internet connections at a higher capacity than a traditional PRI. Most major phone system manufacturers and software based systems support SIP trunking and endpoints. SIP is already in use as a means to transmit voice on many carrier backbones.

Here are several important SIP facts:

  • SIP is run on a typical network connection. Like any VoIP you must have QoS end-to-end for consistently high quality service.
  • Many providers offer SIP to anywhere by pushing it across the public internet. Be wary. Look for vendors who are bringing in their own managed internet connection.
  • On 1 T1 you can have either 23 lines (PRI) or 45+ SIP trunks. If you have ethernet options your phone capacity can scale very easily.
  • SIP supports much of the functionailty of the traditional PRI such as Direct Inward Dial and Caller ID.
  • SIP handsets may not be a good deal. Most major VoIP manufacturers charge a per-handset license fee equal to about the cost savings. However in response to price competition vendors such as Avaya have released lower priced handsets such as the 1600 series.
  • SIP handsets lack functionality available on the proprietary handsets
  • SIP is implemented differently by many manufacturers. Ensure your manufacturer is supported by your provider. Not suprisingly Cisco and Avaya users have many options.

SIP is a mature product with significant cost advantages and flexibility. It deserves consideration as a trunking option for all new installs.

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList

IP Office 5.0 is a big release for Avaya

by Joe Gleinser 12. August 2009 16:28

Reluctantly, I've become a big fan of Avaya's IP Office product. My early impressions of this product were not favorable. However it's mobility and remote connection features have developed into best-in-class features. The IP Office has always been very reliable. Finally, it is price competitive from ten - several hundred handsets. The IP Office is getting even better with the impending release of the 5.0 software upgrade. What's new in 5.0?

Failover: IP Offices can now failover between switches either geographically or within the same location. This is only supported with IP handsets.

Exchange 2007 Integration: Voicemail integration is now supported.

Web Based Telephony: Many users that previously relied on Phone Manager Lite will be able to access similar functionality over the web.

Conference Bridge: The conference bridge can be upgraded from 64 ports to 128 ports.

Small Community Network: IP Offices can now be installed at up to 32 individual locations and networked for 3 or 4 digit dialing between locations.

SIP Endpoints: Though I'm sure this feature has been heavily requested its impact on the market will be negligible. Additional licenses are required per SIP handset. Avaya's 16xx handsets rival SIP handsets in price, do not require an additional license and provide more features.

Licensing: Avaya has simplified the licensing by bundling user and phone switch licenses by user type. There are now three types of switch licenses. Essential uses the Embedded voicemail, which now includes Dial by Name directory. Preferred adds Voicemail Pro functionality. Advanced bundles call center reporting, recorded call management, conditional call routing and more. In addition to the switch licenses there are six types of user licenses - Mobile Worker, Tele Worker, Power User, Receptionist, Customer Service Agent and Customer Service Supervisor. Mobile Worker is essentially for remote extensions without any telephony or handset use. Tele Worker includes all licenses for remote IP phone or telecommuter access. Power User bundles Mobile and Tele Worker licenses. Receptionist adds the soft console application.

Support: IP Office 5 is only supported on the 500, 412 and 406V2 switches.

 

 

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList

The failures of Voice Over IP

by Joe Gleinser 27. July 2009 19:30

It is especially apparent at this late stage in VoIP adoption just how far off some early VoIP predictions were.  The mobile, free, ubiquitous connection that early VoIP proponents espoused is only marginally closer than it was 10 years ago. In fact today the generation-old PSTN provides more of these features than modern VoIP systems.

The remote VoIP handset still suffers many problems. Without point to point connectivity QoS can only be ensured at the endpoints. As many Vonage subscribers can tell you, this leads to dropped calls, distorted voice and static. Many vendors still require VPN connections between sites for these remote handsets to 'function.'

The Avaya IP Office has supported remote VoIP handsets, with an embedded VPN  client, for years. Recently they have improved their mobile solutions with 'old' technology - the PSTN and mobile phone network. New telecommuter features allow a home phone (PSTN, or otherwise) to receive calls directly while providing advanced telephony features through a remote connection to Phone Manager Pro (Avaya's premium telephony app). Great quality, advanced features and very reliable - that's tough to beat. In addition the Twinning functionality supports multiple endpoint connections. Call my DID to ring both my work phone and cell phone. By pushing the call across the 3G network I get a very good quality call that can reach me through my DID. Neither of these advanced voice features require an IP connection (excepting the remote connection to Phone Manager Pro).

Where is VoIP a fit? That might be the next blog post!

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList

Powered by BlogEngine.NET 1.5.0.7
Theme by Mads Kristensen