Tag Archive for VoIP

WFH Was Growing Before COVID

Updated 05/17/2020 – Statista published this chart which shows the top reasons for WFH in 2019, as cited by U.S. remote workers.

Top reasons Americans wanted to work remotely

WFH Was Growing Before COVIDWork from home (WFH) – the practice of working remotely – has exploded with the COVID-19 pandemic. With social distancing in place, millions of more workers around the world started working from home in March 2020. But WFM is not a new trend. Computer Economics reports that over the past 11 years work from home has grown for many reasons.

Working remotely

Despite the pandemic, the trend toward telecommuting was already well underway according to Computer Economics. To measure how much telecommuting is occurring, they polled IT managers and asked them to estimate the percentage of their total staff that works from home at one of three levels.

In the 2019 report Trends in Telecommuting in the IT Workforce, Computer Economics found that 92% of IT shops allowed some form of remote work:

  • 37% “only a specified amount of time”
  • 35% “only under special circumstances
  • 20% allow personnel to work from home as they choose
  • 8% did not allow any telecommuting in 2019.

Trends in Telecommuting in the IT Workforce, Computer Economics

When Computer Economics conducted the same research in 2008, 64% of IT organizations did not allow their personnel to work from home – at all.

Computer Economics concludes that even before the pandemic, the growth of WFM was enabled by a number of technologies. They cite the growth of high-speed internet, mobile devices, remote access, low-cost web conferencing, VoIP, and cloud computing.

three business demandsWFM growth has been driven by three business demands. The research firm identified concerns about work/life balance, workforce retention, and business continuity. in the face of a pandemic is just one more benefit of the trend.

Tom Dunlap, research director for Computer Economics, wrote in the presser:

Many business leaders are learning a hard lesson … Having robust, companywide telecommuting capabilities in place—even if only used one or two days a week—should be deployed as a contingency measure during pandemics or other natural disasters.

rb-

I work for one of the 35% “special circumstances” firms. At the beginning of the month, I submitted a proposal to start to allow “specified amount” telecommuting. But with the onset of COVID – they started to allow WFH – we will see if it sticks  around in the “new normal.

Stay safe out there!

Related article

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

IVR Security Threats

IVR Security ThreatsOn his excellent VoIP/UC Security Blog, Mark Collier points to some interesting work on Interactive Voice Response (IVR) security threats by Rahul Sasi. IVR systems are used in phone banking, call centers, hospitals, and corporations mainly for information retrieval and account management via phone lines. As a security researcher for iSIGHT Partners, Sasi is doing research on a variety of security vulnerabilities that may be present in IVRs.

The author says that IVR security threats are present in IVR systems used for financial transactions. Sasi presented some of his findings at Hack In The Box Malaysia 2011 and the video is available here. Collier summarizes the IVR security threats in his blog:

  • Telcom closetInformation harvesting – for account numbers and PINs, guessing a static 4-digit PIN for a range of account numbers. The odds of a hit are pretty good. Some IVRs lock the account but reset at midnight.
  • Injection – through the input of spoken words (“test”, “.”, “com”, etc.), supporting VXML servers can be fingerprinted, affected, and possibly even crashed.
  • DTMF DoS – by entering a large number of tones or adjusting frequency/tone duration, it may be possible to affect or crash DTMF processing software in IVRs. This could be particularly nasty, as DTMF processing is very common.

Collier concludes that since most of these IVR attacks simply involve the transmission of DTMF, they are very easy to execute and automate. These vulnerabilities could impact any IVR, whether it is TDM, VoIP, the latest UC.

rb-

None of these issues seem new to me, they are just new applications of old attack vectors.

  • Ma Nell telephone operatorsWho remembers blue boxes or the most famous phone phreak John “Captain Crunch” Draper.
  • Info harvesting is a typical technique in web 2.0. Attackers successfully harvest personal info from websites like LinkedIn all the time.
  • Does VXML injection = SQL injection? time for the programmers to step up.
  • DTMF DOS can lead to a buffer-overflow, are your systems patched? 

All in all these vulnerabilities create IVR security threats.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Power over Ethernet 802.3af

Power over Ethernet 802.3afA client recently asked what happened to the network design rule of thumb which said do not install data cables anywhere near electrical cables? The fear of cross-talk, interference, and corruption of the data traffic seems to have disappeared with Power over Ethernet (PoE). He rightly pointed out that now it seems OK to mix data and power in the same cable going to a networked device. 

Read part 2 here.

Plain Old Telephone SystemPoE is similar in principle to the way that the copper wire pair that carries your POTS (Plain Old Telephone System) telephone signals into your house also carries enough electricity (48v DC) from the telco Central Office to power the phone’s core elements of the headset, dial, and ringer. Power over Ethernet’s development started with early implementations of Voice over Internet Protocol VoIP)phone systems. VoIP pioneers did not have a telco CO to power the phones and powering the VoIP phones with wall warts proved unreliable. The phones stopped working when unplugged from the wall or if the building lost power.

In 2000 Cisco (CSCO) developed the first successful technique of putting 48v DC on the LAN data cable along with the data traffic. This proprietary system allowed Cisco to overcome customer objections to wall warts and sell a lot of VoIP systems.

Cisco logoCisco’s original PoE equipment was capable of delivering up to 10W per port. The endpoint and the Cisco switch negotiated the amount of power to be delivered based on a power value in the proprietary Cisco Discovery Protocol (CDP). The Power Sourcing Equipment (PSE) will send a Fast Link Pulse (FLP) on the transmit pair. The Powered Device (PD) connects the transmit line to the receiving line via a low pass filter. And thus the PSE gets the FLP in return. Cisco’s original PoE implementation is not software upgradeable to the IEEE 802.3af standard. Cisco manufactured many IP phones and WLAN access points devices that were not compliant with the IEEE 802.3-2005 Clause 33 including:

Cisco pre-standard IP phones
7985G7960G7940G7910G7910G + SW
7912G7905G7902G7970G
Cisco IEEE 802.3af and pre-standard IP phones
7970G7961G7906G7941G
7911G7962G
The Cisco 7936 Conference Phone does not support any LAN based power and requires a Cisco power injection adapter
Source

Throughout 2001 and 2002, other VoIP and Wireless Access Point (WAP) vendors saw Cisco’s success and developed their own proprietary (and often non-interoperable) powering systems. As more proprietary systems were developed the Institute of Electrical and Electronics Engineers (IEEE) recognized the need to standardize PoE. The IEEE 802.3 Ethernet Committee assigned PoE technology to a new working subcommittee called 802.3af. The IEEE working group’s charge was to create a standardized version of the Power Over Ethernet so that any manufacturer who wanted to could make their products PoE ready. The IEEE working group took commentary from 2001 to 2003 and released the ratified IEEE 802.3af-2003 Power over Ethernet standard in June 2003 which added clause 33 to the IEEE 802.3 standard

Institute of Electrical and Electronics Engineers (IEEE) 802.3 Ethernet CommitteeThe 802.3af document describes how PoE systems should work.  The standard defines two types of PoE equipment, Power Sourcing Equipment (PSE) and the Powered Device (PD). Power Sourcing Equipment sends the power out over the LAN cabling system to the Powered Device. The PSE would send out a maximum of 15.4 watts DC per link to each device, (limited to standard Ethernet distances). 12.95 watts are assumed to be available at the PD because some power is lost in the cable.

The nominal voltage is 48 V, over two of the four available pairs on a Cat. 3/Cat. 5e cable. “Phantom power” is used to allow the powered pairs to also carry data. This permits PoE to be used with 10BASE-T and 100BASE-TX, which use only two of the four pairs in the cable, but also with 1000BASE-T (gigabit Ethernet), which uses all four pairs for data transmission. This is possible because all versions of Ethernet over twisted pair cable specify differential data transmission over each pair with transformer coupling; the DC supply and load connections can be made to the transformer center-taps at each end. Each pair thus operates in “common mode” as one side of the DC supply, so two pairs are required to complete the circuit. The polarity of the DC supply may be inverted by cross cables; the powered device must work with either pair: spare pairs 4-5 and 7-8 or data pairs 1-2 and 3-6. Polarity is required on data pairs and ambiguously implemented for spare pairs, with the use of a bridge rectifier. (Source)

VOIP devicesPower Sourcing Equipment can be in two form factors. A PSE can be implemented as an endspan which is an Ethernet switch with powered ports (a PoE enabled switch) or midspan which is a power hub that is used along with a non-powered switch the end-user already has in place. PD’s can receive PoE equally well from either type of PSE per the standard. The decision to use an endspan or a midspan is left up to the end-user.  The end device can use either powering technique.

The Powered Device (PD) is a network device like VoIP phones, Wireless Access Points, and IP cameras. which are capable of taking the power off the LAN cable, through the RJ-45 (8P8C) connector and using it to power itself. Some pre-standard PoE devices are incompatible with 802.3af equipment. More PoE ready PD’s are available every year  PoE ready end devices can reduce installation costs by as much as 90% over traditional powering techniques.  Among the newer PoE PD’s devices on the market or coming soon are IP Paging, Speaker Systems, POS Terminals, Door and Gate Security hardware, Public Information signs, Building Access, Temperature Control Systems, Stage Lighting, and Computers. These newer PD’s were pushing 802.3af to its limits and the IEEE began work to evolve the standard. This power limitation prevented “high power” devices that required up to 30W to be supported via the industry-standard PoE solution.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Converting from Centrex to a PBX

Converting from Centrex to a PBXSomething to be aware of as you plan a migration from Centrex to PBX or VoIP. There is a potential that if the customer does not use the phone system that the LEC sells, the LEC may charge the customer for the in-house wiring.  There have been cases where the LEC was seeking over $100,000 for the wiring after the customer switched.

Cable plant

In some areas, regulators have allowed the LEC to carry some OSP (Outside Plant Cables) on the regulated side of the books so some projected accounting value minus the depreciation would need to be recovered by the LEC if the customer were to leave the LEC. OSP has a life expectancy of 25 years or more, especially in environmentally protected locations such as equipment rooms.

A general rule of thumb is if the cable is black jacketed it is OSP. If the cable is gray or beige it is Inside Wire or cable such as riser. In some states, at the time of the ATT break up and thereafter black jacketed cable is still carried on the LEC’s books while the gray jacket is expensed. However, the customer should talk to the LEC OSPE (Outside Plant Engineer) as soon as possible to determine your specific situation.

The OSPE may want the customer to buy the risers and black jacket, which may include a 50-year-old black jacket, a mixture of Paper & Lead (a method of insulating conductors using paper pulp and covering in a lead jacket) as well as more current PIC (Plastic Insulated Cable).

An option would be to rebuild the complex. This option could be less expensive and easier than negotiating with the OSPE to take over 50 years of infrastructure.  Infrastructure which will never support any modern high-speed services.

Rebuilding the infrastructure also provides an opportunity to turn the tables on the LEC. With their own infrastructure, it is possible for the Owner to tell the LEC to vacate the building since they no longer provide service beyond the MDF. Maybe this is your opportunity to link the buildings with fiber and replace older copper while it is in good shape (having been inside most of its life).

Another tactic would be to convince the Telco into certifying that they had “abandoned the cable in place.” If the LEC has installed the infrastructure, and if they want to claim ownership of the cable then they would be responsible for removing the cable as is required by state/local building codes. In many areas, if a cable is not terminated on both ends then it is considered to be abandoned and must be removed. Removing cable is almost as expensive as installing it.

PBX Circuit sales

Another advantage Owners may have is that the LEC is the Centrex provider. A PBX deployment still represents an opportunity for DS-1, DS-3, and trunks sale. Another lever would be to keep a small Centrex as a backup, as part of a business continuity plan as well as ISDN services to remote locations.

One consideration is that when taking over the cable plant the LEC will have to deal with the fact that there may be customers within the facilities that were not part of the enterprise and which were customers of the LEC. We ended up having to sign a “Shared Sheath” or condominium agreement with the owner. The condominium agreement will let the LEC support their customers on the Owners riser system. The Owner will have to provide a technician to help the LEC in mapping out cable pathways for their customers.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Home Wireless Equipment Revenues to Double

Wireless Takes Over Home NetworksHome wireless networking equipment revenues are set to double according to In-Stat. Ethernet LANs have given way to wireless technologies. The market research firm forecasts that equipment revenues from home networking will climb from almost $9 billion in 2004 to over $21 billion in 2009. They further notes that the home wireless market is now dominated by multi-band 54Mbps 802.11g devices, as the number of installed home networks worldwide grew by 13 million from 2003 to 37 million in 2004. The company also finds that home networking equipment is continuing to drop in price while increasing functionality such as wireless and VoIP are being integrated. Silicon prices, higher volumes, and competition have all contributed toward aggressive pricing, says In-Stat.

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.