Categories
Business

Announcing trefor.net Technology Marketing

trefor.net Technology Marketing

At trefor.net we regularly get asked if we can help out with content generation. Add to that our PR, video production and graphic design skills and you have a powerful mix of capabilities.

Enter trefor.net Technology Marketing. trefor.net Technology Marketing is a fully blown marketing agency that can help you get your product or service out there, noticed and bringing in the cash.

Innovative ideas combined with a deep understanding of technical and communications markets are the makings of success. Some of our notable successes include:

Pigeon v Broadband race got blanket TV and radio coverage and resulted in public statements from both BT and the Government.

Move Over IPv4 Bring on IPv6 Party to end all parties at the London Transport Museum, Covent Garden attracted 400 people from the UK internet technology scene together with a Government Minister who came along to give a keynote.

Most Comments on a blog post World Record attempt received over 5,500 comments in 24 hours and raised £6,000 for the RNLI.

If you are a vendor trying to sell to Network Operators, Cloud Operators, ISPs and ITSPs in the UK you should be talking to us. If you are a Service Provider then we understand your business model intimately and can help you succeed.

Whether you need short term help just to get going or for one specific project, or ongoing support right across the calendar we can help you.

Check out our full capability here. Talk to us about what we can do for you by calling Tref on 07957 904477, hook up with @tref on Twitter or email [email protected].

Categories
Bad Stuff End User security

Mcafee offers – how to choose anti virus software

How to choose anti virus software

how to choose anti virus softwareAs regular readers will know I don’t use Microsoft software anymore. I’ve suffered from so many problems in the past that with the advent of Chromebook and the cloud I exist happily with my head up there in the fluffy stuff.

This is not the case for all members of my family and my wife in particular still has a Windows 8 laptop (yuk). In fact I only bought it to run our CCTV monitoring software but it does very occasionally get used for other things when her iPad doesn’t cut the mustard.

Because family PCs have suffered badly from viruses over the years I made sure that when I bought the cheapo Windows 8 laptop it was covered by McAfee anti virus software. It was a deal that covered the whole family for £25 if I recall. Fair enough. Install and forget.

how to choose anti virus softwareLast week the license ran out. McAfee bless em wanted £59.99 for me to renew. I looked online and saw a number of deals including a lowball £25.50 but decided to nip into PC World so see what they had.

All they could do was £60 including a white labelled online backup service free for the first year. A bargain at £30 pa thereafter for 2TB. However I’d been stung in the past with that. Or at least one of the kids had when he installed it on his laptop only to have the thirty quid taken from his youthful bank account the following year. Phone calls to PC World revealed that they didn’t actually control the service and no way Jose could he have his cash back.

I gave him his money, deinstalled the (unused) client and asked PCW to cancel next year’s subscription. Shysters I thought. So I wasn’t going anywhere near a product that could only give me a (inadequate) discount based on taking the backup service.

how to choose anti virus softwareThe salesman/advisor simply suggested Norton at £40 (£39.99). No problemo.

I got home and commenced installation operations. To begin with I had to wait half an hour whilst the laptoip updated the Microsoft software. Then I had problems with the Norton site – their servers were overloaded – hope it wasn’t a virus.

Eventually I managed to download the executable and began to install the Norton Symantec anti virus software. This took ages because it needed to deinstall McAfee which took several reboots and a number of Microsoft updates.

Gor Blimey. The next day I found that “windows 8 has its own anti virus but I also need it to cover a kid’s Window 7 machine and a MacBook Air. Hey.

I realise that Microsoft is following Google into the cloud but it doesn’t remove my present pain. These security software vendors are also seen to be dubious wheeler dealers with all the various deals to confuse customers. Can they survive the fact that in the cloud all the security services seem to come free of charge?

Read all about how to choose anti virus software on Wikipedia.

Categories
Business ofcom

Ofcom Business Connectivity Market Review

Ofcom Business Connectivity Market Review

As part of their Business Connectivity Market Review (BCMR), Ofcom published a document last Friday detailing its proposals related to competition in the provision of leased lines.

Ofcom are looking at whether BT should grant access to its Dark Fibre network to other ISPs. They also want to consider reducing the Service Level Agreement for leased line installations by Openreach from 46 to 40 days by 2017 (for some reason Ofcom call this Quality of Service). Also Ofcom thinks London is a highly competitive market (which it is) and doesn’t include the Capital in the review.

The news has come as a surprise to many as Ofcom’s previous review of business connectivity (carried out in 2012) which also investigated leased lines rejected the idea of using ‘passive remedies’, including ‘dark fibre’ access.

The proposals are subject to a consultation which will close on 31 July 2015, with Ofcom stating that they expect to publish their final decisions in the first quarter of 2016.

What Ofcom should also be doing in tandem is insisting the government review the whole business rates system for fibre which is stitched up by BT. It’s all very well making BT open up it’s dark fibre estate to competition but BT’s favourable rates deal means that they are almost certainly going to be able to quote the end customer more competitive rates for that same fibre route.

Ofcom also published a press release on the proposals which is available here.

Loads of posts on the subject of fibre rates on this blog here. More specific detail on the subject in the post entitled Fibre Rates Inequity Iniquity. In Valuation Office Parlance the rates are called hereditament btw. Just shows you how archaic the whole system is. The whole system needs reviewing. The problem is that it’s a huge bag of worms. BT may well argue that they pay a fair amount of rates based on their business as a whole but it doesn’t stop the fibre rating system being wrong.

You have until the end of July to get your comments in, at which point there will be nobody in the office at Ofcom to read them.

Ciao

Categories
Business End User Engineer fun stuff

Happy Birthday to us

Happy Birthday to tref, Happy Birthday to tref, Happy Birthday to trefor dot net, Happy Birthday to tref.

I was writing a proposal last night and in it put a vague “trefor.net has been going 7 or 8 years”. This didn’t feel particularly right. I should know how long the blog has been going.

I looked it up. The next day, ie today was the date of first posting. Nothing particularly inspirational but at least a start. I’m not even going to link to it.

When I started I very much kept quiet about it. I didn’t know how interesting that might be. It’s a subjective thing anyway, interesting. After a while my co powers that be at Timico found it and asked if I could do more of the same. They occasionally whinged about me going off message.  For example when I did guess the royal baby competition but hey, those competitions got tons of entries, mostly from people in the industry. Obviously there are lots of royalists in the internet game (or more likely people up for a laugh).

7 years isn’t a particularly important milestone. It’s where we are at though and we have had a few major things happen in that time:

Pigeon v Broadband race got blanket TV and radio coverage and resulted in public statements from both BT and the Government.

Move Over IPv4 Bring on IPv6 Party to end all parties at the London Transport Museum, Covent Garden attracted 400 people from the UK internet technology scene  and a Government Minister.

Most Comments on a blog post World Record attempt received over 5,500 comments in 24 hours and raised £6,000 for the RNLI

There will I’m sure be more to come. In the seven years we have had nearly 2,500 posts with 750k unique visitors.  We didn’t start monitoring for a couple of years so the actual number will be higher. Those visitors have left over 11,000 comments. There have been many more spam comments but Akismet has done a good job looking after us there.

The number of comments has dropped over the last year or two. This is either down to the blog redesign or a change in the type of post. On the other hand the number of social media shares has grown significantly and comments are often left on LinkedIn or Facebook instead of the blog.

One recent post by Rob Pickering during the ipcortex WebRTC week got 15 Facebook shares, 26 on LinkedIn, 90 tweets and even 8 Google+ shares which is pretty darn amazing (G+ that is – there’s never much engagement there). Socail media shares are the way ahead present. They are a far better indication of the reach of a post than comments (in my inexpert mind).

The featured theme weeks and guest editor weeks are proving to be very successful. Firstly they make for a better variation in content. Our pre-election political week attracted 10 posts from 10 different industry experts (including an MP) each offering advice to David Cameron on what he should and shouldn’t be doing with internet regulations.

Rob Pickering’s guest week is also a good example. 8 posts on WebRTC received around 300 shares. Concentrating on one specific subject for a week allows us to cover that subject reasonably well and it’s a great opportunity for someone wanting to establish web credentials to do so by becoming guest editor for the week. A guest editorship (?) also enhances the content in a way that I couldn’t do as a solo writer.

trefor.net is now a business and has been widening its base. Firstly we brought out broadbandrating.com. This is a broadband comparison site that initially did business in the consumer broadband space. That market is heavily dependant on how much money you can spend marketing so we have evolved that site to include B2B ISPs.

These B2B ISPs don’t get the volume of traffic and level interest of a BT or Virgin spending heavily on above the line advertising. They do however represent a significant market value that is there to be tapped somehow. A referral to a consumer ISP can generate as much as £140 in commission. B2B players tend not to have the systems in place to manage these affiliate relationships but they do pay their channels significant bonuses for bringing on customers. Broadbandrating.com together with some follow on sites represent an interesting prospect for the future.

The other developmental areas are in Events and Marketing Services. trefor.net events include workshops, Executive Dinners and of course the now famous Xmas Bash are effectively networking opportunities for vendors to meet service providers in environments that are non-salesey. They are really industry get-togethers. Expect hte number and nature of these to grow and evolve.

Marketing Services are also a natural place for trefor.net to evolve. Content generation, PR and assistance with events and general marketing are essentially what I have been doing over the last few years. We now have a great team of specialists in this space. In my experience it is difficult to find marketing resources that understand tech.

Now you need look no further – If you need help with this type of activity get in touch – hooking up with @tref on Twitter would be a start.

All in all the first seven years have been very exciting and makes me even more excited about the future. In the meantime now would be an appropriate time to sing Happy Birthday to trefor dot net  – the full words are in the sub header of this post.

C ya…

Categories
Engineer engineering internet peering

RIPE70

I have to tell you about RIPE70.

RIPE70 was held in the Okura hotel in Amsterdam. Very nice hotel. Nice pool, sauna, bars etc etc. Amsterdam was very nice too. Great restaurants, picturesque streets and canals. Only downsides were the lethal nature of the roads and the beer. Re the roads you have to look out for cars, cyclists and trams. All on different roadways. I made it back alive. As far as beer goes all I can say is Heiniken. Nuff said.

So far so good. The purpose of this post though is not to tell you what a great time I had. 5* hotel, beer, cocktails, great food etc. It is to reinforce the value of attending such meetings.

Even if you don’t go to the talks, and I did go to a few, the real value is in the corridor chats. At RIPE, just as at most internet conferences, as long as you don’t spout rubbish, you can expect to be sitting down for a coffee with some real heavy hitters in the networking game. Or a beer. Or food.

This industry must be amongst the most egalitarian going. The opportunity to make useful contacts is very real in attending these conferences. You do have to understand how to play the game though.

I remember at the last LINX meeting there were a couple of sales guys stood wearing suits talking to themselves. That’s because they didn’t get it. If the sales people had turned up in jeans, or shorts and t-shirts it would have been a different story.

LONAP attends these meetings because a big proportion of our membership sends engineers to them. It’s a great place for sorting out ongoing issues (planning bandwidth upgrades for example) and meeting new prospects.

It isn’t unusual to have over 50 conversations during a RIPE meeting.  Conversations that might normally be categorised as sales or customer support touch-points. You try having that many useful conversations during a normal business week

They don’t have to be sales conversations. Could be pure engineering idea swapping.

Anyway if you’ve never been you need to sell it to the boss. See ya.

PS check out a load of posts from RIPE69 here.

PPS just got some meeting stats off RIPE:

– 678 attendees checked in
– 166 first-time attendees
– Attendees from 58 countries
– 143 presentations
– 2,691 ratings for presentations submitted

Categories
Engineer internet peering

Lonap traffic contines to grow apace

Internet traffic growth at Lonap

The chart in the featured image is the yearly 1 day average internet traffic growth at Lonap.

What you see is effectively a reflection of how the internet is growing. The Lonap traffic includes organic growth plus the addition of new members but the details needn’t concern us really – it’s all up and to the right. It’s pretty much the same story in every IXP (except IXP Cardiff but more on that anon). Also peak traffic on the exchange is quite a bit higher than the numbers shown.

internet traffic growthIn 19 months the traffic has almost quadrupled. It’s also interesting to note the drop off at holiday times – notably Christmas and the school summer holidays .

Lonap, in case you didn’t know is an Internet Exchange Point (IXP) and is one of the two main players in London. London in turn is one of the key points of presence on the internet, Amsterdam and Frankfurt being the others in Europe.

It makes sense for networks to employ peering via an internet exchange for both cost and performance reasons. It also makes sense to use multiple IXPs. Only yesterday the Amsterdam based exchange AMS-IX had an outage. It was apparently human error on the part of a member connecting to the exchange.

This type of issue could happen to anyone, despite lots of efforts to minimise the likelihood of a problem. The point is that when an unplanned outage like this happens networks need a back up solution. Whilst IP transit does the job it would be far better to have a suitable IXP alternative.

These alternatives aren’t always available at a given location but where they are then you should consider using one.

In the meantime internet traffic growth is making this industry an exciting place to be. Check out our other internet peering posts here.

Categories
Business Legal Regs

Sharing data in a Digital Single Market

lyndsey burton digital single marketLyndsey Burton comments on Digital Single Market

The European Commission announced details of their plan for a Digital Single Market in Europe. With it, they’ve outlined a “free flow of data” proposal. Unfortunately it’ll be another wait before we know exactly how they’ll do this – a detailed proposal won’t be ready until 2016. A Digital Single Market has been on the cards for years – earlier this year, the European Commission pushed forward plans for “protecting an open internet” and changes to mobile roaming rules. These were small steps toward more cohesive regulation. But the single market is set to go much further, with far more shared regulation – as the name suggests, the idea is to scrap Europe’s digital borders, creating one big, Digital Single Market.

Reforming data protection rules

To create a Digital Single Market though, a host of outdated policies need modernising first – among them, and the first thing to change, is a long awaited reform of the European Union (EU) Data Protection Directive 1995. The reform – first proposed back in 2012 – could finally be in place by the end of the year. The Commission’s approach is to: improve clarity and coherence of the rules; strengthen individual’s rights; and reduce administrative formalities.

Facebook’s recent experiences with EU national regulators highlighted the kind of red tape the Commission hope to avoid – after meeting Ireland’s data protection rules, the Netherlands and Belgium proceeded to take issue with Facebook’s data protection, and lock Facebook in a regulatory spiral. If the Commission’s plans go ahead, companies would have just one set of data protection rules to abide by in the EU, compared to the 28 they now grapple with. This would make it both easier and cheaper for companies to do business in the EU, and hopefully encourage new digital business in.

Benefits for consumers?

For consumers though, data protection reform is all about building trust, something many agree is lacking at present. Under the reform, we’ll be able to decide how our data is used; we can more easily access our data; we’ll have the right to know if our data’s been hacked; and we can choose to have our data deleted for good.

Overall, the Commission want to “strengthen individuals’ rights, and at the same time reduce administrative formalities to ensure a free flow of personal data within the EU and beyond”. That’s all great – in the UK, our Data Protection Act 1998 could probably do with an update too. But aside from modernising the law, the real point of the EU reform is to get the right rules in place so every EU member state is working under the same regulation ahead of other big digital changes.

Big Data and the Digital Single Market

Of all the uses reliant on data protection reform, there’s possibly none so obvious as the use of personal data for Big Data analyses. In their Digital Single Market strategy, the Commission say Big Data is a “catalyst for economic growth, innovation and digitisation across all economic sectors”. It’s a huge money-spinner. But the seeming contrast between Big Data and an individual’s right to keep their information private won’t be lost on most. How can we maintain control over our personal information, yet allow companies easier and freer access to it?

By March 2018, all new built European cars must have automatic emergency call devices as standard. This is an excellent example of technology that relies on Internet of Things (IoT) – simply, the cars will call up emergency services if there’s a crash, sharing some information about the crash in the process. Technically this isn’t a part of the Digital Single Market but it’s given us a glimpse of the kind of control we could keep over our data as more and more IoT services are introduced throughout Europe. Thanks to rules introduced in conjunction, automatic calls made after a crash would only give the minimum amount of data for the service to be of any use. This would include the type of vehicle, fuel used, time of the accident, the exact location, and the number of passengers. The information couldn’t be passed to any third party without express consent, and later the data would be fully and permanently deleted.

It sounds a logical and fair balance between an innovative, helpful service, and the need for companies to access our data to deliver that service. Let’s hope then, the Commission follows this same logic and doesn’t get too “free” with our data. The Digital Single Market will give us easier access to goods and services – who wouldn’t want that? But it’ll rely heavily on getting data protection right if its benefits are to really outweigh any consumer worry.

Lyndsey Burton is founder of Choose, a consumer information site covering personal finance, home media and retail.

Categories
Business Legal Regs

Digital single market strategy

EU Digital Single Market Strategy

The ITSPA secretariat have published a summary of issues that concern the Internet Telephony Service Providers’ industry in last week’s Digital Single Market Strategy. I’m sure much will be written on this subject in the coming months. In the meantime the ITSPA summary is a good little crib sheet of the issues:

Last week the EU Commission published its Digital Single Market Strategy. In the document the Commission sets out 16 key actions which it intends to complete by the end of 2016 based upon the three following pillars:

Better access for consumers and businesses to digital goods and services across Europe

Creating the right conditions and a level playing field for digital networks and innovative services to flourish

Maximising the growth potential of the digital economy

The DSM Strategy also included the following specific actions of particular relevance to ITSPA members and the telecoms industry:

Present legislative proposals to reform the current telecoms in 2016

the Strategy includes a pledge to overhaul the EU’s telecoms rules, including more effective spectrum coordination, and common EU-wide criteria for spectrum assignment at national level.

creating incentives for investment in high-speed broadband

ensuring a level playing field for all market players, traditional and new; and

creating an effective institutional framework.

Perform a comprehensively analysis of the role of online platforms (such as search engines, social media, app stores, etc.) in the market.

Reinforce trust and security in digital services, notably concerning the handling of personal data. Building on the new EU data protection rules, due to be adopted by the end of 2015, the Commission will review the e-Privacy Directive to ensure that it is aligned with the reformed data protection legislation.

We in the UK have big challenges over the next few years in respect of internet and tech related legislation. Not least since the General Election wiped some tech talent off the parliamentary map. I’m thinking in particular of former Cambridge Lib Dem MP Julian Huppert who was heavily involved in fending off the Snooper’s Charter.

It’s a bit of a worry when I see some of the text in the Digital Single Market Strategy. The worry comes in two guises. Firstly yes some of these areas need looking at. The role of search engines etc. We don’t want them forcing unfair practices.

Secondly I’m not sure I like the idea of government interfering. This is somewhat counter to my first point. If nothing else, governments rarely have the expertise required to get involved.

We aren’t going to solve it all here and now but certainly look out for more content in this space in the coming weeks and months.

Categories
Business webrtc

Where is the WebRTC money? We don’t just do this for fun.

WebRTC monetisation – where is it at?

Last week I chaired a WebRTC workshop. There seem to be a lot of them around at the moment. Very trendy/topical. It was an ITSPA/trefor.net event.

We previously had a WebRTC workshop two years ago where a room full of engineers  were treated to fairly uninspiring demos of WebRTC in action. The uninspiring bit was down to the fact that effectively what we were being shown was person to person video. This kind of service was something that everyone in the room had been offering since time immemorial (we have short memories in the VoIP business – it’s still a young industry).

My prior experience with WebRTC, incidentally,  was at an ipcortex event the previous year where I was privileged to have been one of the first people to make a WebRTC to PSTN call.

Regardless of the number of panel sessions there have been recently on this subject we decided it was reasonable to follow up that first ITSPA workshop with a progress report. The theme of this workshop was the WebRTC business model. Where’s the money?

It took quite a few years for VoIP monetisation to happen. In the early years the only people profiting from the technology were conference organisers. Then came a batch of startup acquisitions – SIP vendors being snapped up by established businesses who had woken up to the fact that they needed to be in the game. Now of course VoIP is mainstream and the growth of the ITSPA membership is testament to the health and profitability of the industry.

So where is WebRTC when it comes to making money?

Before we can answer that we need to understand a little about the technology. The whole reason for being of WebRTC is scalability. If we want to be able to embed communications into any device, and seemingly we do, then current client technology, mostly SIP, doesn’t cut it. WebRTC can be embedded in any browser in theory. At least that’s the ultimate goal. WebRTC also comes with a simple set of APIs that should allow any web developer to incorporate the capability into a site design. One can envisage a WordPress plugin for example.

So WebRTC is about simplicity and scalability of deployment. It’s also about interoperability but I’m not going to touch on that in this post. Interop goes with scalability really.

What about WebRTC monetisation then? WebRTC isn’t something you are going to sell per se. It’s not like an iPhone or a toothbrush (make what you will of my choice of saleable objects). WebRTC is an enabler. The issue is how you take advantage of it

What you will be selling is a capability. A solution. An added value function. There are one or two business models that spring to mind. Using the WordPress example from earlier in this post there is likely to be a support ecosystem for devs in the same way that now exists for WordPress. Linux is another example.

Web developers will be able to sell Real Time Communications functions in websites they pitch to their clients. Customer service organisations will lap up such capabilities. How great will it be to ba able to talk to customers browsing your website and answer any sales questions? Push some relevant product pages maybe?

There could well be some infrastructure money to be made. PSTN Gateways?!

The biggest question in my mind is how a sales channel might approach WebRTC. It’s always been said that traditional telephony channels found it hard to adjust to the world of VoIP. WebRTC takes this a step further away from their comfort zone. Now you need to be able to talk web design to customers.

We live in fast moving and interesting times and it won’t take WebRTC nearly as long to climb the maturity curve as did VoIP. In fact  it is already pretty wide scale use. Google Hangouts for example, and Facebook Messenger.

The Internet of Things is a natural port of call for the tech. IoT, IPv6 and WebRTC. An engineer’s dream. We got it wrong with the concept of the intelligent fridge. Really we shouldn’t expect it to know when we need more milk. We will however find it useful ourselves to talk to Tesco to ask them to deliver some more and we will do that via WebRTC. Strike while the iron’ hot and before the milk runs out.

At last we will be talking to our fridges mwahahahahahaaaaaaaaa.

Previous posts from the ipcortex WebRTC week:

WebRTC and the reseller

Real Time Campaigning: How will WebRTC and other tech impact elections in 10 years’ time?

Hacking together a WebRTC Pi in the sky – keevio eye

Wormholes, WebRTC and the implications of algorithmical analysis

Matrix.org: Defragmenting today’s communications

WebRTC – where are the real world applications?

Welcome to ipcortex WebRTC week on trefor.net

Check out all our WebRTC posts here

Categories
4g Business Mobile ofcom UC webrtc

WebRTC and the mobile reseller opportunity

The WebRTC opportunity for mobile sales dealers

So far in the ipcortex WebRTC week we’ve talked a lot about the impact that WebRTC will have on how we might communicate, as well as exploring some of the technical aspects of the technology. One thing that we’ve not really touched upon is the way that WebRTC will change the commercial comms ecosystem and, being browser based technology, how it will come to affect the mobile business market.

We invited Dave Stephens,  ‎Sales Manager at major O2 dealer Aerial Telephones to share his views on the current challenges in the business mobile market, diversification into unified communications and how WebRTC will impact the delivery of solutions that marry the two.

A changing market

mobile conversationThe business mobile market is in a difficult space right now. Monthly prices are falling whilst handset costs are rising dramatically; a situation made worse in the UK where by and large we still expect to be able to get a free handset with a new contract. Of course we all know the handset is not really free, rather subsidised by the selected tariff, but the result is that many mobile providers only seeing a profit in month 18 onwards.

This differs from  most other countries, where the norm is to select a tariff and then have to purchase the handset separately. While this alternative is beginning to creep into the UK market it’s proving to be a very difficult shift from the “free handset” culture that’s become so ingrained over the last fifteen years.

The business mobile world has also taken a few other hits recently. Non traditional mobile players are making real plans to infringe on the space. WhatsApp are now offering phone calls over 3G, 4G and Wi-Fi, and Google have confirmed their intention to act as an MVNO (in the US at first). Their Project Fi will introduce pay-for-what-you-use data plans, where unused data allowance is credited at the end of the billing cycle. Add to this that within the last few months, Ofcom have proposed a dramatic cap on the price of mobile phone calls between different networks. This will reduce another revenue stream for most UK mobile providers.

For business mobile resellers, there is additional pressure in that many of them have seen their base being attacked by traditional IT or unified comms resellers. It is true that it is far easier for IT or UC resellers to move into the business mobile market than it for a mobile reseller to go the other way, which would take significant investment and upskilling.

Adapt or perish

ChameleonThis all contributes to an environment where companies in the mobile space must adapt or perish. This isn’t limited to resellers, either. It can even be seen at a mobile network operator level where even the big players are beginning to move into some very untraditional services such as hosted telephony, landline services and even hosted IT products.

For the opportunistic and imaginative reseller, however, moving into other areas of business comms like these can present significant benefits and is a challenge worth attempting. “Mobility” is a growing concern within the IT and Telecoms industry right now with many businesses striving to adopt a “work anywhere” approach. We are seeing a clear push to give employees the tools they need to be effective wherever they are. This is ideal for the savvy mobile reseller that has always had this as their core remit.

There are of course issues when looking after a truly mobile unified communications platform. Primarily this is related to the fact that there are 3 core mobile operating systems which are constantly being upgraded, not to mention the 1000s of different handsets that users can choose from, each with their own quirks and nuances. Standard native mobile apps delivered by PBXs produce all kinds of headaches for engineering teams. This is where the development of WebRTC is really exciting as it may negate the need to install, upgrade and manage these difficult situations.

That’s a long way off – not every mobile OS supports WebRTC – but we are watching the progression of the standard with a keen eye.

Previous posts from the ipcortex WebRTC week:

Real Time Campaigning: How will WebRTC and other tech impact elections in 10 years’ time?

Hacking together a WebRTC Pi in the sky – keevio eye

Wormholes, WebRTC and the implications of algorithmical analysis

Matrix.org: Defragmenting today’s communications

WebRTC – where are the real world applications?

Welcome to ipcortex WebRTC week on trefor.net

Check out all our WebRTC posts here

Categories
End User social networking surveillance & privacy webrtc

Real Time Campaigning: How will WebRTC and other tech impact elections in 10 years’ time?

What might a WebRTC enabled democracy & election process look like in 10 years’ time? (Or, technically, 12)

There’s a lot of pre-election stuff that’s the same every year. The campaigning, the squabbles, the gaffes and the villains: they’re all regular plot lines in Britain’s most depressing pantomime. As we go to the polling stations tomorrow, however, we can reflect on 2015 as the year that something did change – the first year that the parties appear keen, rather than reluctant, to embrace technology. We’re seeing as many memes and mashups as we are manifestos; not surprising really as this is, afterall, what many of the traditional media outlets have dubbed “the social media election”.

It’s true that there’s been far more activity on the social media battlefield than ever before (even if they’ve not quite got it right) and it seems that parties are even beginning to use big data – although they’ve a long way to go to replicate the success that Obama had with data in his 2012 campaign. But what role could or should technology play in the elections of the future? What might, say, the 2027 election look like? How might WebRTC play a part in that? Here’s what I imagine might happen…

Every campaign sits on a foundation of micro targeting

TargetIf there’s a question worth asking, in 2027 there’ll be some data that supports the answer. Parties will dedicate greater spend to using big data as the foundation of each campaign – whether that’s in the capture and curation of data relevant to them or analysing it.
This will allow focus of specific campaign messages on certain groups, or even at an individual level. They’ll focus on swing voters, and those within swing constituencies, targeting them with whichever marketing method suits that opportunity, at that time. Meaningful, one-to-one engagement with individual voters will be commonplace, made easier with social media. In addition, these engagements will be more memorable because they’ll use video and other real time comms via WebRTC.
Shaping campaigns in this way has obvious benefits for the parties, but could this type of targeting backfire? Will voters get creeped out and perceive the relevant party in a negative way? Will the long heralded privacy backlash make it too difficult to capture the right data in the first place? Do we rely too much on the integrity of the people to whom we give our data?

Predicting outcomes and campaign agility

With so much data available, much of it collected from social media engagements, will it be easier to predict results?

In the 2012 election in the US, analyst Nate Silver created a model that accurately predicted the winner in every state. Was his success simply due to the fact that Nate was ahead of the curve with the system he was using, and no one had time to react? In 2027, prediction models will have become even more sophisticated and we will see a greater emphasis on doing this in real time. That will then have an effect on parties’ activities and focus throughout the campaign. Each party will need to be agile and have the means to react quickly to changing predictions. Technology like WebRTC could provide another way to communicate with party members, on the ground campaigners or even swing voters in a really quick and effective way.

Real democracy in real time

Electronic systems could allow the public to vote on issues before or as decisions are taken in Parliament. The government paid lip service to using technology to help represent the public’ views with e-petitions, but will they ever be brave enough to open up decision making to registered voters on a regular, or even real time basis? Technology like WebRTC, with its low barrier to delivering enriched comms universally, could potentially be used to allow voters to watch a live debate and then vote at the end. This vote could then shape Members’ opinions or, even, make the decision outright. Would Parliament ever be that bold, and would MP’s accept their role being changed from being a voting representative of a constituency to its steward?

Some governments have already trialled this kind of approach, albeit to shape decision making in advance of its debate. DemocracyOS is an example of this: an open source solution that seeks to provide voters with the means to inform, debate and vote on bills before they are passed. According to them, it’s already been used by the Government of Mexico, the Congress of Buenos Aires, and by some congressmen in the US amongst others. Adopting this kind of approach would be an interesting way to reduce the effectiveness of large companies’ lobbying, and ensuring that airtime in front of MPs isn’t just a question of money and power.

I easily can imagine that forward-thinking councils in the UK, or even individual MPs could use this kind of democratic technology to debate local issues, gaining traction by social media sharing. It would be a welcome alternative to local, “public” consultations that are conducted so discreetly that the public are not properly represented.

Even if government, councils and elected representatives don’t themselves adopt that approach, there are other organisations that seek to make government more democratic from the outside. US startup Placeavote has an interesting model, where site members vote on bills on any range of topics and Placeavote’s candidates will represent the majority of voters. It has failed to gain much traction so far but could prove disruptive given the chance, and I imagine that by 2027 we could have seen someone try a similar approach in the UK.

Reducing expenses, humanising politics and customer service 101

keevio webrtc interfaceIn 2027, MPs will find it much easier to balance their Parliamentary duties with those in their constituency. Technology like WebRTC will mean there’s little excuse to not participate in a debate or vote because they will be able to do so remotely, and there would no longer be the possibility for bills to be passed due to poor scheduling and low turnour. Furthermore, MPs won’t need a second home in London and can spend more time in their constituency.
Internet connectivity will be ubiquitous, as will devices to access it. This means that they can use tech like WebRTC to engage with their constituents in a different way with memorable, multimedia enriched conversations with the same universal reach of the phone systems of the past. For example, elected MPs and their representatives could use this to make their “MP surgeries” more accessible for their constituents by negating the need to travel. They could even adopt a real time “ask me anything” approach during pre-election campaigns.
By 2027, local MPs will have learned lessons from the way that businesses use technology to improve their customer service. Communicating with your MP will be more efficient and timely and, as a result, people will engage with them more than ever before.

The voting process itself

DecisionAn obvious area where technology could improve elections is in the voting process itself. For example, how backwards and archaic is it that we should turn up to a physical location with just a polling card and no verification of identity, yet we already need an online government gateway ID to get a passport? And how secure is it really to leave counts of paper ballots to volunteers? Technology like WebRTC could reduce the technical barrier of providing biomechanical verification in the process.

In addition, increasing the number of people who are registered to vote, and those who actually do place a vote is an ongoing challenge. Technology could make the process of registering and voting more convenient in the hope of increasing participation. To this end, the Political and Constitutional Reform Committee has already proposed that all electors should have the choice to vote online in the UK by 2020. Electronic voting has already been trialled in some countries and so some level of e-voting in the UK by 2027 is not unimaginable – although the experience in Estonia hasn’t actually increased turnout in itself so its effect on this could be in question. Furthermore, whilst paper counting by humans may have its drawbacks, it is very open, auditable and therefore resilient against high level, systematic abuse. Will we ever have the same level of assurance with an electronic vote?

Whatever happens, it’s pretty safe to say that the stage has been set for much wider use of technology during the election process. The challenges will be cultural and institutional – and we’ll be interested to see which parties will be first to adopt real time technologies to make a real difference to the voting public.

Previous posts from the ipcortex WebRTC week:

Hacking together a WebRTC Pi in the sky – keevio eye

Wormholes, WebRTC and the implications of algorithmical analysis

Matrix.org: Defragmenting today’s communications

WebRTC – where are the real world applications?

Welcome to ipcortex WebRTC week on trefor.net

Check out all our WebRTC posts here

Categories
Engineer gadgets webrtc

Hacking together a WebRTC Pi in the sky – keevio eye

WebRTC on a drone

Team ipcortex put together the keevio eye hack for the TADHack London mini hackathon at Idea London on 11-12th April. The idea was to develop a proof of concept for WebRTC running headless on small embedded devices and talking to our keevio video chat interface. Hardly mission critical but TADHack is a load of fun, and a good way of trying stuff out that pushes the technology envelope a bit which inevitably ends up feeding back useful ideas and techniques into our core platforms. There was also a lot riding on this after our success with RTCEmergency at TADHack last year. Matt Preskett is one of our lead developers and the guy behind the hack, and this is his write up of the experience of developing the app.

On the Tuesday evening before TADHack we hadn’t had time to think about possible hacks. We’d been busy with other events and the process of progressing our core keevio platform towards release. A few months ago we were playing with the idea of a WebRTC Raspberry Pi security camera for our bike shed, so as I walked out of the office I suggested, perhaps to my detriment, that it might be a fun idea to use our JavaScript API, running on a Raspberry Pi strapped to the bottom of a quad copter feeding live video via WebRTC…

I did a bit of research on Tuesday evening, but decided with the timescales involved and some of the parts/equipment needed that perhaps we were biting off more than we could chew. Also I wasn’t really sure how I was going to run our API on a headless Raspberry Pi 50ft in the air. Even if that could be overcome I wasn’t sure the ARM processor would be up to the task of decrypting and encrypting the streams.

Wednesday morning I had all but written off the idea. At the time I was working on load testing our UC platform, which required running our API on a headless server. I set about looking into running headless Chromium, and, by the end of Wednesday with the help of Xvfb I had our API running and automatically accepting video chat from keevio.

Thursday was a busy day we didn’t really have an opportunity to discuss the hack. Rob as perhaps a sign of desperation speculatively ordered a Pi and Pi camera.

Friday morning and we still hadn’t concluded what we’d be doing for the hack, after a quick meeting we gave Pi copter (Pi in the sky?) the go ahead. We had just over 48 hours to put all the pieces together. I started off with Raspbian; I don’t really like the extra gumpf that comes with this distribution but I didn’t have time to piece a fresh instance of Debian together. Raspbian only offers Chromium 22 in its repositories; this was when WebRTC was in its infancy. I looked at compiling the latest Chromium, but this would require either a cross compile environment or compiling on the Pi, neither of which I had time for. I looked around again for an alternative distribution and settled on Arch after checking that they offered an up to date version of Chromium for ARM. It’s a bit bleeding edge but more than sufficient for our requirements.

After getting the Pi installed the first thing was to get Chromium to recognise the camera. Chromium talks to video devices through the V4L component of linux.

I inserted the following lines to /boot/config.txt to enable the camera:

gpu_mem=128

start_file=start_x.elf

fixup_file=fixup_x.dat

Then I added the camera module to /etc/modules-load.d/raspberrypi.conf:

bcm2835-v4l2

After rebooting the Pi, udev created a /dev/video0 device, so it was looking good. The next step was to install Chromium, Xvfb and lighttpd. I setup lighttpd to listen on loopback as I was going to be hard coding the username and password into the webpage: not nice but necessary.

This is the JavaScript I wrote for the hack, due to using our API I could keep it short and sweet.


var keevioShare = (
  function(username, password) {

    function avCB(av) {

      console.log('INFO: avCB with', av);

      if ( av.get('existing') )
        return;

      av.hook(
        function() {
          if ( av.get('status') != 'acknowledged' )
            return;
          getUserMedia(
            {
            video: {mandatory: {maxWidth: 640, maxHeight: 480}},
            audio: false
            },
            function(stream) {
              av.accept(stream);
              console.log('INFO: Accepted request with', stream);
            },
            function(e) {
              console.log(e);
            }
          );
          console.log('INFO: Getting user media.');
        }
      );
    }

    function authCB(authenticated) {
      if ( authenticated ) {
        IPCortex.PBX.startPoll(
          function() {
            if ( ! IPCortex.PBX.enableFeature('av', avCB, ['chat']) )
              console.log('ERROR: av not enabled!');
            /* Set myself online */
            IPCortex.PBX.enableChat(function() { });
          },

          function(number, description) {
            console.log('ERROR: API reports ' + description + '!');
          }
        );
        console.log('INFO: Authenticated.');
      } else
        console.log('ERROR: Failed to authenticate!');
    }
    onAPILoadReady = (
      function() {
        IPCortex.PBX.Auth.login(username, password, null, authCB);
      }
    );
  }
);

Next I needed Chromium to start automatically on boot, I cheated a little bit by using cron. I’m not overly familiar with systemd so writing a startup script didn’t seem a priority with the time scale involved. I added the following to crontab:

@reboot /usr/bin/xvfb-run –wait=15 /usr/bin/chromium –use-fake-ui-for-media-stream –disable-default-apps –remote-debugging-port=9222 –user-data-dir=remote-profile http://

localhost &

Chromium required a few switches to allow it to run headless:

1) To stop Chromium asking for permission to access the camera:

–use-fake-ui-for-media-stream

 

2) To stop Chromium asking to be set as default:

–disable-default-apps

 

3) For remote debugging (it only listens on loopback):

–remote-debugging-port=9222

 

4) Place the users Chromium profile in a defined location:

–user-data-dir

At this point I started running into trouble with the camera. Every time I started up Chromium I could only get a maximum resolution of 16×16 no matter what v4l2-ctl commands I ran, which wasn’t going to be a good experience. After quite a lot of searching I found the solution and added the following to /etc/modprobe.d/bcm2835.conf:

options bcm2835-v4l2 gst_v4l2src_is_broken=1

 

We needed to serve everything over https as Rob was going to be in London and I would be back in Buckinghamshire flying the quad. That caused me another headache as you can’t load secure and insecure content in the same page. I setup lighttpd to serve pages via https using a self-signed certificate for localhost. Due to Chromium running headless I couldn’t accept the certificate security warnings; I needed access to the Xvfb instance. Installing x11vnc enabled access to the X display. I started the service using the following command on the Pi:

# x11vnc -localhost -display :99

By default xvfb-run starts on display 99. I port forwarded VNC via SSH:

# ssh root@(hostname) -L 5900:127.0.0.1:5900

Then I connected using vncviewer to localhost; this allowed me to import the localhost certificate into Chromium’s certificate authority to stop the security warnings.

I settled on netctl to setup the wireless network as this was quick and easy, after having a bit of a nightmare with an access point I borrowed from work I ended up using an old Sky router I had lying around.

keevio eye - the Pi in the sky
keevio eye mk II: no zip ties in sight!
keevio eye - the Pi in the sky
Special lightweight case and minimal gubbins inside due to payload limitations

Finally I put everything together. Feeding power from the balanced charging port of the LiPo battery to a 5V UBEC into the Pi’s GPIO interface. In the process, I managed to accidentally reverse the polarity into the GPIO… which felt like game over as it was now midday Saturday. Luckily something in the supply saved me and it was OK. Attaching the Pi to the quad was an engineering challenge in itself but inventive use of zip ties and self adhesive pads worked out. After a quick test run we got clean video up to 150M and still received video up to 300M.

Here’s a quick video of keevio eye in action!

Previous posts from the ipcortex WebRTC week:

Wormholes, WebRTC and the implications of algorithmical analysis

Matrix.org: Defragmenting today’s communications

WebRTC – where are the real world applications?

Welcome to ipcortex WebRTC week on trefor.net

Check out all our WebRTC posts here

Categories
Engineer surveillance & privacy video webrtc

Wormholes, WebRTC and the implications of algorithmical analysis

James Batchelor is Founder and Chief Executive at Alertacall, an organisation which uses neat technology to deliver services which increase human contact with people at risk and are used to improve the lives of many thousands of vulnerable people. Prior to that he was involved in the creation several ventures in the internet service provision, internet retail, telecoms, recruitment and telecare sectors. James has been an ipcortex customer since some of our earliest days and is one of those people who, every time I have the pleasure of chatting to him, I always walk away with a valuable bundle of unique insight. I posed the question to James about the technology impact of WebRTC, and this is what he came back with…

WebRTC meets wormholes

On a long-haul flight in 2001, with the occasionally pungent aroma of reconditioned air in my nostrils and the drone of Rolls Royce engines through my headphones I was transported for a few hours not only to USA – but in to an alternative future. I had the immense pleasure of having time and little else to do but read a novel and a science fiction one too.

The story I read, “The Light of Other Days”, is centred on the discovery of wormhole technology which can be used to pass information instantaneously between points in the space-time continuum. The technology is commercialised by a global media company and used to create the “wormcam” which allows for anything anywhere to be viewed with profound implications for privacy.

As I ponder the applications and implications of WebRTC, and explore its own wormhole like qualities, I wonder whether there are similar impacts for humanity and how the absolute digitisation of our communications streams – coupled with the massive computing power now at our fingertips – could impact upon our own privacy in novel and unexpected ways.

My own company Alertacall is particularly interested in understanding how patterns in the way people communicate with us can indicate a change in their “need”. This is with the positive goal of helping our older customers get the help they need before a situation escalates and becomes materially more difficult to manage. And, as our future products and services start to use WebRTC and other similar communications technologies I wonder what additional data we’ll have at our disposal.

Real-time analysis

I’ve long hypothesised that computers should be able to detect from cameras and other input devices subtle things about human physiology that the human eye cannot, but only had clear evidence of it after stumbling across the fascinating TED talk See invisible motion hear silent sounds.

This talk demonstrates the possibility of detecting heart rate with nothing more than video, by analysing the microscopic movements in our skin caused by pulsating arteries. I wonder how long it is before a methodology to determine skin temperature is devised, or what can be inferred by knowing how quickly someone breathes, blinks or swallows?

In 2012 the mathematician Mr Max Little announced that Parkinson’s symptoms can be detected by using algorithms that analyse voice data. There is also Voice Stress Analysis, which can indicate a range of emotional states including the detection of whether someone is potentially lying. What else could be inferred from a “call”?

But what specifically has this got to do with WebRTC and similar stacks? I suggest that the incredible proximity of these communications streams to silicon provides an unprecedented opportunity to develop applications that exploit all of these methods for causes good and bad. For example: imagine if calls to emergency services were prioritised using real-time analysis of video and voice, where the person most likely to be having a heart attack is answered first.

Also, imagine a world, in which the person or organisation you are in a call with has installed one of the dozens of analysis applications that are likely to emerge – and can infer huge amounts about your physiology. “Mum, I’m absolutely fine” the daughter says to her mother, but moments later the concerned mother’s machine tells her it’s simply not true with a simple Chrome plugin.

We’re tremendously excited about the applications we can build with WebRTC to connect with our customers and to connect our customers to each other – but live in constant wonder about what opportunities will emerge.

 

Previous posts from the ipcortex WebRTC week:

Matrix.org: Defragmenting today’s communications

WebRTC – where are the real world applications?

Welcome to ipcortex WebRTC week on trefor.net

Check out all our WebRTC posts here

Categories
Bad Stuff Business scams voip

Mechanics behind International Shared Revenue Fraud

VoIP fraud continues to rear its head this week with a post on ISRF mechanics.

Continuing with his week as guest editor covering VoIP fraud issues David Cargill has invited industry expert Martin John from AQL to discuss IRSF mechanics – how it actually works:

As we all know International Shared Revenue Fraud (ISRF) plays a large part in the overall fraud that we see in the industry, even though services are marketed legitimately they are widely used for fraudulent purposes and the artificial inflation of traffic, whilst some of the traffic will terminate in the target country a high percentage will never reach the expected destination (commonly referred to as short transit or short stopping)

Whilst the ITU governs the allocations of Country Codes once the code is allocated the usage and numbering plan is controlled by the responsible authority in the recipient country, the ITU publishes updates on the reported use of each numbering block for each allocated Country Code (http://www.itu.int/oth/T0202.aspx?parent=T0202) however this is based on information submitted by the responsible authority and is not always an up to date source of information.

Historically Telecoms Operators interconnected directly via TDM on a bilateral basis, a settlement rate would be negotiated with a key objective being the balance of traffic to reduce any financial settlement between the parties, using this method the majority of ISRF traffic actually terminated in the country that holds the number allocation.

isrf mechanics

Smaller countries or those with financial constraints could not justify or afford this method and opted for a cascade accounting method, cascade accounting meant that the smaller operator would make an agreement with one or two larger international operators whereby the larger operators became an aggregation point for the allocated country code and in return kept a percentage of the revenue.

isrf mechanics

With cascade accounting traffic to designated number ranges could potentially be short transited, the authority responsible for the allocation and administration of the number ranges may have requested that the cascade accounting partner terminate certain prefixes to alternate carriers/partners for other services, these opportunities were very financially rewarding due to the expensive part of the network (the international circuits) not being utilised.

isrf mechanics

 

 

As the market developed and with the establishment of VoIP clearing houses/exchanges and traffic aggregators cascade accounting has become less popular, operators favour being able to interconnect to lots of different operators in one place, increase their profitability as they no longer have to give a percentage to the cascade accounting partner and lower their cost base as they would no longer need to purchase other international routes via their previous cascade accounting partner, however this simply made ISRF easier, the telecoms market is more cost driven today than it has ever been operators strive to  maintain lcr with the minimum of man power and international destinations that are outside of their main business area are commonly terminated through large traffic aggregators or clearing houses, interconnection between the aggregators and clearing houses is a common practice it is in their business interest for a call attempt to complete and convert to revenue and therefore as the financial barriers to connect to clearing houses are small the interconnection by parties that want to abuse the situation is relatively easy.

Take for example the following scenario:-

The island of High Termination Rate is assigned the country code of +997 from the ITU the and files a numbering plan. The island of High Termination Rate Telecommunication Regulatory Authority (HTRRA), announces the following:
isrf mechanics table

 

 

The national operator of the island of HighTerminationRate HTRT is a respectable and ethical company that interconnects to a large traffic aggregator and a clearing house to not only gain access to a full international A-Z for terminating traffic but also to ease interconnection with other international carriers so that the residents of The island of HighTerminationRate are globally reachable, the per minute rate is advertised as £1.00 ppm

aql4
To this point everything is legitimate however there is nothing stopping the aforementioned opportunistic man in the middle/ISRF reseller from also interconnecting to an aggregator and clearing house and advertising a rate of £0.98 ppm supporting either the full list of breakouts or “specialising” in certain areas such as HTR Mobile +99780

aql5

 

 

In the background the ISRF reseller has been busy harvesting numbers and happily upsetting the observed statistics (reduced ASR’s etc) whilst tying up network capacity to obtain a better understanding of the utilisation of the ITU allocation.  Once this understanding has been obtained numbers can be tested and resold to customers.

Some may wish to offer chat services or other services of the like whilst avoiding any national regulation and of course this then opens the door to parties that wish to generate fraudulent traffic.  To expand further after number harvesting it is discovered that anything that starts +99780752 can NOT be completed via the legitimate route offered by HTRT.  It is a range that falls within the allocation but perhaps due to demand has not been opened yet.

Any traffic generated to this range will fail on the HTRT route if in fact it even attempts the HTRT route first due to the ISRF route being marketed at a lower rate. Once that call has failed the aggregator/clearing house would normally route advance the call to the next available route where ISRF are happy to complete it.  Legitimate traffic that the ISRF route receives is simply terminated back to another carrier. Whilst this incurs a loss with restrictive routing and capacity the impact is minimal and aesthetically legitimises the service offering provided by the ISRF route.

aql6

 

 

 

 

 

 

 

Martin John is the General Manager of aql wholesale. aql, established in 1998, is a wholesale integrated Telecommunications Operator, Regulated by Ofcom. Providing services to many of the FTSE 100 and is one of the UK’s largest IP Telephony fixed line operators.  It is recognised as a significant market force in fixed and mobile services by the UK Regulator.

Check out our other VoIP fraud posts here. Below are links to other fraud related posts this week:

PABX fraud by Manuel Basilavecchia here
IRSF Fraud by Colin Yates here
CLI Spoofing detection by Matt Anthony here

Categories
Business internet social networking webrtc

Matrix.org: Defragmenting today’s communications

Matrix.org Comms Federation

In his week as guest curator Rob Pickering of ipcortex now has a post by Amandine Le Pape who discusses WebRTC federation.

I’ve held a view for a long time that the world would be a better place if there were a widely used standard for messaging federation, so that I could for example have one universal public chat address on my business card just like I have a phone number and e-mail address. I know quite a few folks disagree with this, and think that it is a “feature” rather than a bug that they have to use a myriad of apps each with their own private chat space and no interoperability, but I think this is a big usability headache.

Like most things, there is an Internet standard for messaging interop: XMPP, but it doesn’t have the wide adoption of other standards like SMTP for e-mail, or HTTP for the web. In fact it suffered a bit of a body blow when Google dropped support for messaging interop via XMPP from its front line messaging products a couple of years ago – I wrote about this at the time. Whilst XMPP is a well documented protocol, it is over complex with many extensions to do fairly basic operations. A new initiative has emerged from the folks at Matrix which aims to produce a de-facto standard protocol for messaging interoperability – I wish them well and suspect that this is probably our last chance to sort this out. Here is what Amandine Le Pape from Matrix has to say…

Take a look at your smartphone. Chances are, among the various icons on the screen, there are quite a few messaging apps and apps with a messaging capability. Whether text, chat, calling or via video, every week brings a new app to download. We use all these different applications daily – LinkedIn for colleagues, Facebook for family, WhatsApp for the sports club, Viber for some international contacts, Skype for video and that is without even touching messages sent from within other apps.

The only point where these apps and the profiles on them converge, is on your phone. We then have to juggle what app connects me to what person, or holds the information you need. Matrix.org is a new open source and non-profit project aiming to fix the problem of fragmented IP-communications between devices, people and services with a very pragmatic and novel approach. Matrix defines a persistent data layer for the Web, with open federation, strong cryptographic guarantees, eventual consistency and push semantics. Like the Web, Matrix can be used for many purposes, from Instant Messaging to IoT, via VoIP and WebRTC. With it the “missing link” of interoperable calling between WebRTC silos becomes interoperable and as simple as a single HTTP PUT to invite the callee, and a single HTTP PUT for them to answer. Meanwhile, OTT messaging apps can finally federate by synchronizing their conversations into Matrix; letting users own their history and select their preferred app and service.

As an open source project, any developer can use Matrix (it’s all on Github) to easily create and host their own feature-rich real-time communication apps that openly interoperate with one another, or add such features to an existing service whilst building on the Matrix community of users. Existing communication services can also easily join in and integrate with the Matrix ecosystem, extending their reach while participating in this collaborative effort to break down the walls between communication silos.

Matrix is an open project and will stay so because for Matrix to achieve its mission of making all communications services interoperable we believe it needs to be truly open; giving people access to take all the code we produce to use and build on top of it. We need the trust and support of those who want to use Matrix in their own applications and startups and want to see an end to all walled garden applications and closed silos.

We firmly believe in doing what is right for the consumer and the internet user. As people begin to use interoperable communications tools, service providers will have to compete on the quality of their service, security and features rather than relying on locking people into their walled garden. Can you imagine using a phone network that only allowed you to call people on the same network? We genuinely hope that one day, Facebook, Whatsapp, BBM etc will all integrate with Matrix voluntarily.

Once consumers realise they can choose to use their favourite app, from their trusted app provider, and still be able to communicate with friends using competing apps and services, they will likely demand integration and interoperability.
Matrix is here to help foster innovation throughout the Internet. We are making communications safer, more ubiquitous and innovative. Generic messaging and data synchronization across the web will never be quite the same again. The project may well provide the disruption needed to change how real-time data is shared on the Internet, and usher in a new age of services which by default collaborate rather than compete. There is no doubt that a revolution of sorts has begun and Matrix intends to fan the flames.

As a company or an individual, whether you believe that today’s communications are fragmenting and need to change or not, check out the Matrix.org website or follow us on Twitter @Matrixdotorg. We also recently launched our ‘Matrix Console’ app which is free to download from the Google Play or Apple App Store.

Amandine Le Pape is the Co-founder and Business lead for Matrix.org

Previous posts from the ipcortex WebRTC week:

WebRTC – where are the real world applications?
Welcome to ipcortex WebRTC week on trefor.net

Check out all WebRTC post on trefor.net here.

Categories
Engineer webrtc

WebRTC – where are the real world applications?

I’ve been working with WebRTC for a few years now and from time to time talk in public about the technology and its potential. A pretty popular question goes along the lines of “that’s all very well, but where is the revenue in it for me?”

Around the time we did our first end-user demo of WebRTC technology making phone calls in 2012, I wrote up an article where I predicted a range of applications for the technology. Thankfully none of the fairly scary scenarios that I painted in that post have come to pass. Standardisation and browser support have been a bit slower than some of us would have liked but spite of this WebRTC has been quietly making inroads into both the traditional communications space and being used to deliver novel new applications. With the Microsoft announcement about WebRTC support in the next version of their browser, and Google’s massive strides in reliability and interoperability in the core WebRTC project, the future of the technology now looks certain.

At ipcortex we’ve worked on a number of WebRTC developments including RTCEmergency, a weekend hack last year to re-imagine the way we do emergency services calls which won a Google prize for innovation at TADHack Madrid and, with feet closer to the ground, our first major commercial WebRTC end-user application keevio which provides a full range of business Unified Communication services into any device with a WebRTC capable browser.

Amazon Mayday and other apps, do they or don’t they?

An interesting property of WebRTC is that in a really well implemented application, a user need not know or care if it is using WebRTC. It is of course really easy to tell if a web-page prompts to use the device camera or microphone in Chrome or Firefox and then delivers in-page audio and video without a 10-minute plugin dance, but for a dedicated mobile app with no web interface, it is impossible to know for sure without resorting to examining the source code or tracing interactions on the wire.

That is how the world found out that the Amazon Mayday service was using WebRTC to provide real time video chat as part of its live support service.

Other consumer communication applications that have more or less publicly adopted WebRTC to deliver real time communications over the past couple of years include:

  • Comcast – streaming personal video between set-top boxes and handhelds using WebRTC
  • AT&T – allowing calls to/from own mobile number via browser & API
  • Google Hangouts – Google are the major force behind WebRTC development and it was seen as a bit of a coming of age for the technology when they publicly announced that their flagship hangouts product was now using it half way through 2014.
  • Facebook Messenger – head over to www.messenger.com using Chrome and start an audio of video call with a Facebook friend. Your conversation just used WebRTC. That is a huge user base.

Now to some extent many of these don’t need to use WebRTC to deliver what they do; all of these companies have sufficient muscle that they could have developed dedicated applications or plugins to achieve the same functionality – albeit in a less usable way. Indeed most of the examples above still do use plugins that have been developed if you access them from a browser that doesn’t include native WebRTC support, so WebRTC is just a way of streamlining certain kinds of access.

That’s the point really, WebRTC isn’t something users care about – it should be invisible. It is the applications you create with it that have the user-visible value.

The value is in the application not the network

Whilst the simple messaging use cases for WebRTC have been early adopters, and nobody could claim that Facebook, or WhatApp are commercially insignificant, their existence has probably closed the door on making vast amounts of cash out of building a simple consumer messaging application with a bit of WebRTC voice and video thrown in.

If that is bad news for a would-be application developer, the good news is that the universal end-to-end capability that WebRTC delivers means that smart applications can still emerge which generate value by streamlining some aspect of communication.

Metcalfe’s Law (smart guy, even if he did have to eat his own words after predicting the Internet would collapse by 1997) says that the value of a telecommunication network is proportional to the square of the number of participants. This was later tweaked for social networks to be closer to n  log(n) for the number of participants, but you get the point – it is a hockey stick curve where biggest network creates vast value and smaller networks have a very low comparative value. It explains why for example Fring sold a couple of years ago for a reported $50m and the WhatsApp acquisition closed out at close to $22bn, it also explains RCS’s commercial failure. It is really hard to build networks that acquire enough scale quickly enough to have significant value.

WebRTC is a bit different as, once browser and device support is complete, it builds a ready rich communication network of “everything on the Internet”. That isn’t by the way just “everything on the Internet with a screen”; we’ve put full implementations of WebRTC applications on a Raspberry Pi and strapped it under a quadcopter running off the flying machine battery (more on that later this week!).

A really important feature of building an application with WebRTC is that you get a huge potential Metcalfe’s Law advantage before you write a line of code (but so does everyone else).

Contextual vs Free Communication

So if there is vast amount of potential derived from intrinsic network size, and one class of basic social communication applications are already stitched up, where will the next killer communication applications, perhaps using WebRTC, come from?

Most new applications succeed because they are either some large factor better than what currently exists (10 times is an oft quoted number), or they solve a universally felt pain point.

Thankfully there are lots of pain points in communication, and it is relatively easy to deliver 10 times the value of a 3KHz phone call. Unlike the personal realm, where some quite good messaging tools not only exist but now dominate, business in many areas still relies pretty heavily on basic communication mechanisms.

Look at how phone calls work. Users sit working on a processing task and in the middle of this a loud intrusive ringing sound comes from a plastic box on their desk. They have just a few seconds to decide whether to respond, and the only choice they have is to ignore it and lose the conversation (or even worse commit to a longer interruption to pick up a voicemail later), or pick it up and be immediately dropped into a high bandwidth synchronous communication with no context. The only information they may have about the reason it is ringing will be the name or number of the caller. We must respond immediately, context switching away from what we are doing or not at all. Depending on the job that you do, just the interruption itself, never mind the actual cost of dealing with the communication has probably cost 5-10 mins of productive work. You really wouldn’t invent a system like that from scratch today, and indeed much of the value in existing business phone systems relate to applying workarounds for these fundamental drawbacks (call queues to make interactions asynchronous for the recipient, screen popping/click to dial to give agent context etc).

Phone calls are then initiated outside of any particular context, and once started are synchronous, demanding the undivided attention of both participants.

It is far easier to initiate communication without moving away from a task flow, and with the benefit of additional context. In this way attention flows naturally and productively between communicating and processing. This is one of the important ways that WebRTC will deliver contextual communication from within other task based systems – dealing with customer support communications within the context of a support application etc. Done properly, because it is web based, this will be entirely seamless and the user will just view communication as another task experience.

Synchronous to Asynchronous

Many folks of my age are conditioned and therefore still obsessed with calling each other, but fast forward to the next generation and they pretty much exclusively run their lives far more effectively on asynchronous messaging, only escalating to realtime (usually group) voice/video when they really want to give some high bandwidth communication their undivided attention. This is way more efficient and allows interleaving and prioritising of communications and processing.

Asynchronous, Synchronous, Free and Contextual communication - a quadrant diagram

Not only will the next business communication apps be primarily contextual, if they want to remove pain points, they will also offer asynchronous communications as the norm with a simple escalation path to high bandwidth, rich synchronous communications like video and screensharing with voice.

So in summary what does all this mean to me if I’m thinking of deploying my first WebRTC based service or application?

  1. Don’t think of it as a “WebRTC service”. That shouldn’t be visible to your users if you do your job properly.
  2. A personal multimedia messaging application for free communication among your own customers is fine, but won’t set the world on fire – you will be competing with WhatsApp, Facebook, appear.in, Google etc and Metcalfe’s law is on their side (unless federation ever happens and don’t bet on that).
  3. If you are looking for a USP, think of integration with a key business process to either massively streamline communication or remove a pain point.
  4. Find a bunch of 16-25 year olds and test your application with them. If it has the key attributes of contextual and asynchronous then it will probably pass muster with them. If it doesn’t, they will wonder what planet you come from.
  5. Don’t think about it for too long – just get on and do it! The time for producing WebRTC toolkits, APIs, test applications and pilots was 2013, it is about delivering polished applications and services ahead of the competition now.

 

Previous posts from the ipcortex WebRTC week:

Welcome to ipcortex WebRTC week on trefor.net

 

Categories
Bad Stuff Business scams security voip

Caller ID Is Broken – How Can We Fix It?

matt anthony pindropCLI spoofing doesn’t have to be as big a problem as it is.

In the third of this week’s posts on VoIP fraud guest editor David Cargill has Matt Anthony, Vice President of Marketing at Pindrop Security as a contributor.

There was once a time when people trusted the number that showed up on their Caller ID. Phone companies charged extra for the service. Even banks allowed you to activate your credit card just by calling from a registered phone number. Today, that is no longer the case.

Caller ID (CLI) and Automatic Number Identification (ANI) were originally designed as systems to be used internally by the phone companies. As such, they didn’t need any real security. As they emerged as consumer facing tools, they never developed the security features that we expect today.

The result is that spoofing Caller ID data, or ANIs, is very easy. A quick Google search turns up pages of articles on how to spoof a number. App stores are full of easy to use apps that enable spoofing. One smartphone app, Caller ID Faker, has over 1,000,000 downloads.

spook card - disguise your caller id

Adding to the problem is the fact that in general, Calling Liner ID spoofing is completely legal. Though it is always illegal to use CLI spoofing for fraud or threatening messages, it is perfectly legal to spoof a number as a friendly prank, or as a helpful business practice. (Think doctors on call who don’t want to give out their cell phone number.) While it might be fun to spoof a CLI in a prank call to your friend, too often fraudsters are the ones disguising their numbers to hide their criminal activity.

Pindrop Security tracks phone fraud activity and trends. We have found that CLI and ANI spoofing is the most common technique used by phone fraudsters. In addition, more than half of the caller ID spoofing attacks cross international boundaries, meaning they are almost impossible to track down and prosecute.

Consider the case of one attacker, known to Pindrop researchers as “Fritz.” This fraudster is likely based in Europe and works alone. Fritz is in the business of account takeover. He calls financial institution call centres, impersonating legitimate customers by spoofing ANIs, and socially engineers the bank into transferring money out of an account. In one four month period, we found that Fritz had targeted 15 accounts. We estimate that he has netted more than £650,000 a year for at least several years.

While there is no technology that can prevent CLI spoofing, it is possible to detect these calls. The key is to detect anomalies between the information being sent over the Caller ID and the actual audio characteristics of a call using phoneprintingTM, created by Pindrop Security.

Phoneprinting technology analyses the audio content of a phone call, measuring 147 characteristics of the audio signal in order to form a unique fingerprint for the call. Phoneprinting can identify the region the call originated from and determine if the call was from a landline, cell phone or specific VoIP provider. These pieces of information provide an unprecedented level of insight into caller behavior.

So, if a Caller ID says a call is coming from London, but the phoneprint of the call shows that the individual is calling from 1,000 miles away, it should be a red flag for anyone running a call centre that the caller has malicious intent.

pindrop caller id verification

 

 

 

 

 

 

 

 

One recent fraud attempt thwarted by Pindrop tools happened on a Saturday night, a time when most call centre employees are not at their most vigilant. The caller asked to transfer £63,900 from one bank to another. The Caller ID matched the phone number associated with the account, and the caller knew all the answers to the identity questions the agent asked. However, while the Caller ID said the call was coming from San Francisco, Pindrop detected that the call was actually coming from a Skype phone in Nigeria. As a result, the wire transfer was put on hold, and the bank was able to verify with the account holder that the request was fraudulent.

Pindrop phoneprinting solutions are already protecting calls to top banks, financial institutions, and retailers. The Pindrop platform is a comprehensive solution designed to protect the entire call system: inbound, outbound, live, recorded and in the IVR, customer-facing and employee-facing interactions. Pindrop uses the information from the phoneprint to create a highly accurate and highly actionable risk score for each call, which has allowed it to catch more than 80 percent of fraud calls within 30 seconds after the call has been initiated.

Historically, the phone channel has been over-trusted and under-protected, making it a major target for fraudster exploitation. Today, technology is available to detect spoofing and stop phone fraud.

Matt Anthony, Vice President of Marketing

www.pindropsecurity.com

Matt Anthony is the Vice President of Marketing at Pindrop Security. With over twenty years of experience in the technology industry, Matt is a frequent speaker at technical conferences. Prior to joining Pindrop, Matt served as Director of Marketing at Dell SecureWorks. Matt has also held marketing roles at CipherTrust, Monorail, and Dell Computer. He is a graduate of the University of Texas at Austin.

Check out our other VoIP fraud posts here. Below are links to other fraud related posts this week:

PABX fraud by Manuel Basilavecchia here
IRSF Fraud by Colin Yates here

Categories
Engineer webrtc

ipcortex WebRTC week cc @ipcortex

Welcome to ipcortex WebRTC week on trefor.net.

It is with some terror that I accepted the invitation to contribute a series of posts here on the future of communication technology – Tref’s readers are a pretty smart bunch and this is a great opportunity make complete fools of ourselves when our crystal ball inevitably turns out to be myopic given a few months or years of hindsight.

We’ve instead decided to ask the following question as a theme for the week and then invite some posts that illustrate views of the future from different perspectives, not just our own.

Game changers like WebRTC are emerging and will spawn a wide new range of services with secure, contextual user to user and user to server communication. Wildly imaginative applications for this technology are already starting to be developed and many more are probably yet to be invented.

Irrespective of the technology most people already rely on the rich and intuitive communication capabilities of various existing Internet based silos to run their personal and social lives.

On the other hand, much of our business and formal communication is still using the kind of systems that we are giving up on in the personal realm: email, telephone calls etc.

So the question is this: what factors will shape how we use communication technology in future? will users just be swept along on application by application waves of technical features, or can we hope to shape things by applying what we have learned about how people want to communicate to build useful global capabilities?

In line with this theme, coming up we have:

  • Some ideas on how the future of WebRTC will pan out, timed to coincide with the ITSPA workshop in London today
  • Matt, one of the developers of keevio eye, an R&D hack to put video chat on a Raspberry Pi and strap it on a drone will be talking about how he did it and the kind of serious applications this enables
  • The folks from matrix.org will be talking about their attempt to build an open standard for decentralised communications and federation

This is an exciting time with some big recent shifts, and even bigger ones ahead. We hope you enjoy reading the ipcortex week posts and that they stimulate some healthy debate.

Rob Pickering is CEO and Founder of British communication software vendor ipcortex. An engineer with a technical pedigree tracing back to the beginnings of TCP/IP, he is a keen innovator and a champion of open standards like WebRTC, which are helping to improve the way we work. His team have worked on a number of WebRTC developments including keevio, their latest production interface that extends UC and multimedia functionality to the web browser, and RTCEmergency, the Google prize-winning proof of concept app that augments emergency services calls with real time video

Footnote by Tref: This is Rob’s first post on WebRTC on trefor.net. Rob has significant form when it comes to the technology. I first encountered WebRTC at an ipcortex seminar in which I was thrilled to make one of the first WebRTC to PSTN phone calls. Check it out here.

Loads of WebRTC posts on this blog here.

Categories
Business scams security voip

Telecom Fraud – Investment in Prevention and Detection initiatives not always available.

colin yatesIRSF- International Revenue Share Fraud

This week we have David Cargill as guest editor. David runs the Operations Working Group at  the Internet Telephony Sevice Providers’ Association (ITSPA) and takes a special interest in VoIP Fraud. David has invited a number of experts to contribute guest posts on fraud related subjects. This ties in with the ITSPA/trefor.net Workshop on Wednesday that has VoIP fraud and WebRTC as its main themes. This is his second choice of post, in which IRSF is discussed, is written by Colin Yates, Managing Director of Yates Fraud Consulting Limited:

The telecommunications industry has a huge gap between those operators who manage fraud effectively and those who do not. Those who are effective fraud managers, whether they are a Tier 1, 2 or 3 operator, are generally those who have matured over the years with a strong mandate and support from their Executive to do the job, while being provided with the necessary budget, resources and tools to do it well. Some senior management unfortunately view fraud losses simply as a cost of business, and allocate very little budget and resource to it. In these cases fraud losses are generally not measured or reported, so will remain unknown and not reflected in quarterly, half yearly or annual financial reporting.

There are some CSP’s who have enjoyed reputations within the industry as leaders in the management of fraud, but over time these reputations have diminished and their fraud losses have increased. Some of this could be blamed on a change of senior leadership who failed to appreciate the importance of effective fraud management. This could also be a result of a fraud manager who failed to continually make it clear to the organisation how much value they were adding to the business by effectively managing fraud. An effective Fraud Manager will take whatever steps are necessary to ensure that the papers for every Board meeting will include his quarterly fraud report to clearly identify the fraud recoveries and averted losses they have achieved during the period since the last meeting.

Fraud within Telecom operators is generally measured as a percentage of total revenue, and depending on which organisation is providing the figures, this could be estimated at anywhere between 1% and 5% of total revenue. In my experience an operator with a mature fraud team with the necessary fraud detection/prevention tools, along with the support of his management team is likely to maintain their fraud losses at under 0.50%. Assuming this is a tier 2 operator with total revenues of $US1.5 billion, if the effectiveness of the fraud team was permitted to deteriorate to a point where fraud losses increased by another 0.25% of total revenue, this would add a further $US3.75 million to the annual fraud losses. To recover this revenue through adding new customers would require upwards of 10,000 new customers to be added to the business, assuming an average ARPU of around $US370 per year. Would it not make better business sense to continue to support the fraud management function with resources and tools at a cost of probably 10% of the additional fraud losses suffered.

Subscription fraud is without a doubt the biggest contributor to fraud losses across the industry. While most operators would agree that their aggregated subscription fraud loss far exceeds those suffered by any other fraud type, the drive to attract and connect new customers can make it difficult to manage. Most sales channels will require that a potential customer who meets basic identity verification checks will be provided service during that one visit to a physical or on-line store. Without investment in real time subscription fraud detection tools, this type of fraud is always going to be difficult to manage. Some of these tools are no longer expensive and can allow a CSP to take more risk when providing service to new customers.

International Revenue Share Fraud (IRSF)1 has to be regarded as the one fraud type that the industry has failed to manage effectively, primarily again because of a lack of investment in tools and resources by some to prevent and detect an attack early to minimise losses. IRSF Fraudsters can attack a business using many enablers, for example subscription fraud, roaming Fraud, PBX hacking, Mobile Malware, Wangiri Fraud and others. Some CSP’s use tools, either developed in-house or obtained from an FMS provider and do manage their IRSF risk effectively, but many others simply operate in the belief that this fraud will never impact them, so they will make no investment in a defensive strategy, and simply take the risk.  This decision is typically not taken by those accountable for managing fraud, but by those a level or two above who control the budgets. In most cases, this decision maker will have no idea what the actual risk is, and the impact of not implementing these controls may result in losses way above his delegated financial authority. It is still not unusual to hear of IRSF losses that have amounted to over $US500,000 in a 2 or 3 day period. An investment of under $US30,000 could have avoided most of these losses.

It is well documented now that around 85 to 90% of all IRSF incidents occur in the period between Friday evening and Monday morning when many CSP’s fraud monitoring staff are not in the office. Unfortunately even some of those who have made the investment in monitoring tools will continue to ‘take the risk’ over weekends and will not take that monitoring a step further to enable some automation, or diversion of outputs from their monitoring systems to a 24×7 activity within their business. In a roaming situation, NRTRDE (high roaming usage) records are delivered within 4 hours of a roaming call completing, and this includes the period right through the weekend. Having made an investment to implement this fraud control, it is hard to understand why no-one would be looking at these in real time to identify fraud, or have some automated process set up to manage an obvious fraud indicator.

Without effective monitoring tools, some operators will simply block what they consider are high risk destinations assuming that this will reduce their risk of becoming a victim to IRSF. We currently monitor destinations and numbers used for IRSF and the total Countries advertised by IPRN Providers number 221 and the test numbers we have recorded in to these countries number over 100,000. However the top 10 high risk destinations very seldom change and are as indicated in the graph below. These 10 destinations are responsible for 50% of the IPR numbers being advertised, but any of the remaining 211 country International Revenue Share numbers advertised could result in significant fraud losses being suffered.

VoIP fraud by country
Sources of telecom fraud by country

Fortunately there are more and more operators who have identified the value of 24 x 7 fraud monitoring, and have managed to make the argument for resources and tools to allow this compelling enough to obtain sufficient budget to implement this strategy.

Unfortunately this has not resulted in a reduction of the overall IRSF problem. It has simply driven the fraudsters to look for easier targets and these are currently smaller MNO’s and more recently MVNO’s. Fraudsters have come to realise that many MVNO’s do not have Fraud Management expertise in-house, or access to the information and networking industry forums that most MNO’s have available to them.

Prevention and Detection are the fundamentals of Fraud Management, which is particularly relevant for the telecommunications industry. The costs of pursuing a fraud strategy based on implementing the resources and tools required to monitor network usage are insignificant when compared to the likely losses you will suffer if you simply rely on luck. Anyone with any doubt in this area should arrange for an independent contractor to come in to their business and conduct a fraud risk review so that the full extent of the risks can be identified. A simple example of an MNO with an effective fraud monitoring process in place identifying and stopping an IRSF attack within 30 minutes, compared to an MVNO with no fraud process, allowing an IRSF attack to continue for 48 hours before detection, is demonstrated in the diagram below.

IRSF effective telecom fraud momitoring
effective telecom fraud momitoring

IRSF has now been around for at least 10 years in some form or another. Some CSP’s have lost significant amounts of money to it, and some fraudsters have generated small fortunes in fraudulent income from it. Many customers have been impacted through bill shock after their handset has been stolen or their PBX hacked, and many small countries have suffered social and economic impact as a result of their number ranges being hijacked by these fraudsters.

The argument for effective prevention and detection initiatives is compelling, but this does require some support and investment by an MNO or MVNO’s senior management team. After around 10 years of suffering from this fraud, it should be apparent that the various industry groups who have been searching for solutions are unlikely to come up with anything positive in the next year or two, so it really is up to the individual operators to take action to protect themselves.

1IRSF involves fraudsters calling international numbers that attract a high termination rate, from a stolen or fraudulently obtained connection, with an intention to inflate traffic in to those numbers and be paid a per minute fee from a number provider for each call made. Payment for these calls will eventually be required from the originating network, who will have no hope of recovering these costs.

Colin Yates is a telecommunications professional with over twenty five years’ experience, specifically in the area of fraud, investigations, RevenueAssurance and threat management. Colin specialises in the areas of Telecoms Fraud (Internal and External) and Investigations. He also has considerable experience with Personnel and Physical Security, Law Enforcement Agency Liaison,Intelligence Management, Regulatory Compliance, Revenue Assurance and Policy development.

Check out his website at www.yatesfraudconsulting.com. Also check out our other VoIP fraud posts here.

Read yesterday’s post on PABX fraud by Manuel Basilavecchia here

Categories
Business security voip

PABX fraud is on the up – by Manuel Basilavecchia of Netaxis

PABX fraud growth

This week we have David Cargill as guest editor. David runs the Operations Working Group at  the Internet Telephony Sevice Providers’ Association (ITSPA) and takes a special interest in VoIP Fraud. David has invited a number of experts to contribute guest posts on fraud related subjects. This ties in with the ITSPA/trefor.net Workshop on Wednesday that has VoIP fraud and WebRTC as its main themes. This is his first choice of post, in which PABX fraud growth and is discussed, is written by Manuel Basilavecchia – Co-owner, Sales and Marketing Director of NetAxis Solutions.

It is commonly agreed to estimate that the loss due to fraud in the telecommunication industry represents 0.5% to 5% of revenue of telecommunications operators.

Even if all of those scenarios are well known for years, many of them are still impacting the telecom industry. Of course, not only Telecom providers are impacted, as retail/corporate customers are impacted as well by telecom fraud.

In this article, we’ll focus on a specific kind of PABX fraud (and all mechanisms related) which is PABX hacking.

To make a fraud possible and generate money, a fraudster needs two things:  Traffic (generation) and a termination (Cash collection).

In order to generate the traffic the fraudster will hijack a PABX. Alternatively the fraudster will pay a third party to perform the hijacking. In that case, we’ll talk about IRSF fraud type (International Revenue Shared Fraud). Once the access to the PABX is effective, the PABX will be used as resource to generate calls to high cost destinations.  As the fraudster owns the numbers targeted by the fraud, a money flow will be established and the fraudster could retrieve the money.

At first glance, the mechanism is not that complex, but the thing is that it has worked for years and is still working nowadays.

Let’s try to figure out why

In most of the cases, hijack of the PABX is not that difficult. Indeed, very often the password by default has not been changed by the administrator. Also in case the password has been changed, a very basic password is used which is quite easy to guess by a fraudster. Alongside this, these systems are always subject to vulnerabilities which can be easily exploited by a basic hacker.

In most of the cases, that attack is made outside business hours  including weekends, assuming that the PABX activity is not monitored during these intervals.

In this way, the customer is even not aware that he has been victim of an attack.

This lack of monitoring during some times of the day/week has the consequence that very often the fraud is discovered when the customer receive his telecom supplier’s invoice.

There is also an aggravating factor which is the payment terms. Indeed, usually the billing period between retail customer and its telecom provider is monthly while the billing period for Premium rate numbers is weekly with as consequence that once the fraud is discovered, the fraudster already got the money and it is very difficult to get the money back (or withhold payment).

This is having negative consequence on the relationship between the retail or the corporate customer and the telecom provider. Indeed, as the fraud is involving international destinations, international carriers are part of the scheme.

Having several players in the scenario makes it quite complex and difficult to find a fair solution for all the parties and someone as to assume the loss generated by the fraud. Let’s consider a practical case that will illustrate all those considerations:

A fraudster buys some Premium rate numbers in a foreign country, keeping in mind the high cost per minute associated. As a second step, he will ask and pay (share revenue) somebody to generate traffic artificially towards those numbers.

Once the attacker gets access to the PABX, he will generate as much as possible traffic in the shortest time (night or week-end)

The fraudster will receive payment from the Premium rate number 7 days later.

Assuming that nobody will notice this traffic increase on customer side (same on operator side) this traffic will become visible when the customer will receive his telecom invoice; usually one month later.

Quite clearly it is too late to react and very difficult to avoid a loss. Indeed, the usual traffic flow for international traffic is the following. Traffic starts at a retail customer and is sent to his telecom operator. As it is regarding international traffic, the telecom operator will use one or several international wholesalers to terminate this traffic. Those international wholesalers could also use different suppliers to terminate the traffic. The number of intermediaries and the misalignment of the payment terms make it complex to withhold payment and very often a party will have to suffer a loss, in most cases being the retail customer of his telecom supplier

In case of fraud, the size of the operator could put him in a very difficult situation. There have been cases where the operator is forced to choose between losing the customer or have to assume the loss generated by the fraud. If the telecom supplier is not financially robust, this could have very big impact on business.

As a conclusion, to avoid risks linked to this type of fraud it is important to:

  • Take all appropriate measures to secure the PABX of the customer. This point is often difficult due to the diversity of the installed based or the lack of expertise at customer side. So a good information campaign needs to be setup.
  • Deploy a Fraud Management System that, in near real time, will look at any customer traffic patterns in order to detect abnormal activity in terms of volume or destination.

Of course, the FMS needs to be operated by people having skills in fraud detection, or better, expert consultants to detect fraud but also to avoid false positive cases and not block legitimate traffic (and revenues).

Additionally, this will provide the capabilities to the operator to mitigate the financial exposure by reacting quickly to fraud cases (reducing the impact) and by providing evidences in order to open claims towards authorities and upstream providers (Recovering losses).

Manuel Basilavecchia is Co-owner, Sales and Marketing Director of Belgium based NetAxis Solutions. Manuel Basilavecchia brings over 17 years of business strategy, innovation and technology experience to his role as co-founder. As Director of Sales and Marketing, Manuel is focused on developing NetAxis Solutions business by bringing advanced carrier-grade communications services to Service Providers and Corporations and by providing high-technology products to the industry. Manuel holds a Master in Electrical Engineering – Electronics and Physics, a Master on Medical Physics and Bioengineering, and an MBA in management.

Loads of posts on PBX fraud here. Also come back for a different VoIP fraud post each day this week.

Categories
Business voip voip hardware

Practical IP Phone Design

ip phone hot-desking ip phone roi ip phone interoperability ip phone security lesley hansen on designing an ip phonePractical Applications for Your IP Handsets

In the last of her articles on IP handset design Snom Marketing Manager Lesley Hansen talks about practical applications including ip phone hot desking.

IP phones are unique in that they were built to support IP first and telephony second. When businesses embrace the richer world of unified communications the benefits of IP phones become evident. With IP phones business users can use converged services which incorporate voice into data and video applications.  Advanced IP phones are really multimedia endpoints that bring these capabilities together with a single interface. IP phones interface with IP Telephony servers or IP PBXs and they can deliver features to your phone that are not available with more traditional office phones. Business productivity features such as Auto Attendants, Music on Hold and Automated Personal Attendant services, but also user productivity features such as caller id, voicemail, voice to email, transfer announcements and speed dial.

Beyond the elegant feature list on an IP phone there are certain practical applications that the handset needs to be designed to accommodate in order for the business to get the most from their IP handsets.

Hot Desking

In IP Telephony hot-desking can be best described as when your extension is whatever phone you’re logged onto. Hot desking means that a business can make efficient use of office space allowing workers to use available desk space rather than deploying one desk per user and having empty unused desk spaces when employees who spend time in other offices or at customer sites are not in their local office. Hot desking in an office environment can save on lighting, heating, and power and space costs and promote improved interaction between employees.  In a call centre where a desk space may be expensive because of the tailored equipment, Hot desking is an excellent way of using the resources available to best effect.

IP phone hot desking does not only save money for the business it also make the individual more productive. Any small business with multiple locations will see a great benefit in hot desking.  A person may have a number of offices and travel and work out of each of them, depending on the day of the week or week of the year.  With hot desking, they’re always connected to their voice mail, and easily accessible via their extension number.  They have all the features and functions that they are used to having on their IP phone.

Hot desking also benefits the end customer, the employee can log in on any phone in any office and be fully connected.  No more problems for the end customer searching and guessing to find out what office their contact is working out of today.

When designing an IP phone for hot desking it needs to accommodate multiple IDs simultaneously and to be able to download user profiles from the switch when a new user logs on.

Home Working

Home working is the scenario where you live and work in the same place and brings new challenges to the design of IP Telephony handsets. Enabling home working allows for a reduction in commuting charges and mobile bills. As calls on your private IP network are free you can also make savings on call costs. Home working requires an IP phone to be easy to setup and reliable to use. There is no technical resource in most homes and to keep costs down and productivity up the IP phone needs to be a plug and play device. Once a phone is plugged in needs to be fully operational with the same features and functionality as the user has when in the office. The principle behind home working is that the user is allocated a single IP extension on the IP Switch which is retained no matter whether working on a home extension or logged in to an office extension.

Moves, Adds and Changes

Moves, adds and changes (MAC) is the general term for the routine work performed on items such as Telephony handsets in an enterprise, including installations, relocations and upgrades. MACs can cost a business valuable time and can involve reconfiguration, physical relocation and testing and setup. Using an IP phone the costs for MACs can effectively be eliminated since users can log themselves onto any handset and so effectively manage the move or change themselves. Costs savings from user empowerment through IP in moves such as office relocation or re-organisations, staff rotation and data centres moves are considerable. It is important when selecting an IP phone to ensure it has been designed to easily accommodates remote deployment and remote management facilitating low cost moves, adds and changes within the business.

Support for Multiple Profiles

It is not uncommon for a business to employ people who work representing more than one role or business venture. In these situations the IP phone can be designed to allow the user to have multiple identities so that they can have calls coming in to multiple incoming numbers over multiple lines and can recognise which line the call is coming in on and answer the calls appropriately for the businesses. When making calls in this type of situation it is also important that the outgoing caller id is appropriate to the business being represented. The ability to support multiple identities is a simple feature of IP phones but one that is easiest to use when designed into the handset.

Speaker or Conference Phone

Clear communications is critical if business calls or meetings are to be productive. The audio quality achieved through a speaker-phone or a specially designed conference phone is different, they are optimised differently to handle multiple voices and background noises. Therefore understanding the use of a phone is an important consideration in phone design and selecting a phone that is optimised to the task being performed is key to experiencing good voice quality. With a High Definition voice codec in use by all conference participants, combined with decent quality microphones and speakers, you will experience much clearer audio.

This post on practical ip phone applications is the 8th and last in our series on how to design an ip phone. Other posts in the series are linked to below:

How to design an ip phone
How to design an ip phone for voice quality
IP phone design for it departments
IP Phone Security
IP Phone Interoperability
IP phone ROI
IP Phone aesthetics

Check out all our VoIP posts here.

Categories
Business voip voip hardware

IP Phone Aesthetics

ip phone roi ip phone interoperability ip phone security lesley hansen on designing an ip phoneDesigning IP Phones for Beauty and Practicality – IP phone aesthetics

In the 7th of 8 posts on how to design an IP phone Snom Marketing Manager Lesley Hansen talks ip phone aesthetics.

Design is at the service of the user and the product functionality. In order to reach a good design, we must give priority to decisions that are taken during the products development. A design that is artistically pleasing is one of the criteria that is considered by Snom when we design any new handset or conference phone.

All telephone handsets have at their base the model used by Siemens in their first handsets for traditional telephony 30 years ago. Siemens invested in the development of the technology from day one. They set great store by ergonomics, intent on making the telephone more convenient. They started with the introduction of the hand receiver, followed later on by the scoop-shaped receiver which typified the design for many years.  This investment in design and interest in the ergonomics and practicalities of handset manufacturer is an approach emulated by Snom Technology to this current day.

The handset designer is not working with a blank sheet of paper on which to fashion their creations.  Each new handset has a specification which details the features and functionality that are required in the handset. These features and functions dictate the chipset to be used and the memory and circuit board content that has to be incorporated into the unit.  The designer typically works with a telephone engineer who has an awareness of the audio rules to achieve best quality audio. For example every speaker needs a chamber and the chamber design can fundamentally affect the voice quality.

IP phone aesthetic design is a trade-off between artistic and audio quality. It is in this area more than any other that Snom pushes at the limits in IP Phone design. Snom add uniqueness to their product offering in the quality of audio achieved improving and enhancing the basic CODEC quality.

Once a drawing of the design is approved a prototype is made and the handset is tested mechanically to ensure the design is practical and efficient. There follows a series of tests and modifications aimed at achieving an optimum balance of audio quality, practical efficiency and beauty in design.

It is during this stage that unique elements can be added into the handset design to enhance it’s usability in the workplace. For example some of the Snom handsets have a unique stand that enables them to be either desk or wall mounted at the angle best suited to the user.  This makes them more comfortable in use for some workers. There are also differences between handset models based on the environment in which they are to be used.  For example a phone designed for voice use in noisy offices is designed to reduce interference from outside noise.  One intended for use in an office where users have to concentrate has a handset designed to be put down quietly without disturbing other people in the office.

Another example is that a handset designed for use by service providers and on premise installations with remote office must avoid the need for local provisioning or configuration, and one designed for use in a local office environment must include abilities to interface with other devices in the office. Mobility is the main design feature that users focus on as a differentiator.  However in a professional handset range there are numerous other features that make one handset more appropriate for use than another.

The design of the handset is critical.  If a handset feature is incorrectly optimised by the manufacturer then new software can be introduced to make the change needed to improve the sound or usability.  Although this is inconvenient to the customer, and unprofessional from the manufacturer’s perspective the costs incurred are low.

This is not an approach used at Snom but some manufacturers do release multiple software upgrades using just this model – test and change at the expense of the customer in order to keep their own costs low and speed to market rapid.

If the basic phone design changes the costs incurred for replacement of the expensive and specialist tools used to inject the plastic components are irrecoverable.  This high cost of error is one reason that Snom keep all our design and prototype manufacture in house in Berlin. Hence we have the control to ensure the design is tested in small quantities tool production before it moves to mass production elsewhere. This approach ensures we have a tight control over the quality of our handsets and are able to ensure that we produce professional and enterprise IP phones.

This post on ip phone aesthetics is the 7th in our series on how to design an ip phone. Other posts in the series are linked to below:

How to design an ip phone
How to design an ip phone for voice quality
IP phone design for it departments
IP Phone Security
IP Phone Interoperability
IP phone ROI

Check out all our VoIP posts here.

Categories
Business UC voip

6th trefor.net UC Executive Dinner sponsored by Snom

kevin murphy btuc executive dinner is another hit

Just a quick footnote re the 6th trefor.net UC Executive Dinner held on Tuesday night in London. We had 23 top industry executives signed up for the event which is by invitation only. Tuesday night’s event was held at London’s top Michelin starred Spanish restaurant Barrafina.

The speaker Kevin Murphy runs BT’s voice network and treated us to a great talk on where BT’s voice capabilites are going. This event is gaining in strength each time it is held.

On Tuesday we had C Level representation from a great mix of companies including some who had flown in especially for the occasion. Major multi nationals including BT, Ring Central and Vonage mixed with smaller business focussed UK companies together with key vendors in our space.

snom sidebar adAs well as extending a special thanks to Kevin Murphy I’d like to thank German SIP handset manufacturer Snom for their generous sponsorship. Snom were one of the first manufacturers of SIP phones and are therefore one of the oldest companies in the game.

These evenings are operated under Chatham House rules whereby nothing said on the night is attributable to any individual. This makes for a very open discussion in an environment where many of the participant are competitors. That isn’t to say this is a cartel under another name. The topics discussed are those relevant to the industry as a whole.

Check out what people say about the trefor.net Exec Dinners:

Colin Duffy – CEO,  Voipfone
The trefor.net uc executive dinners are always good for high quality gossip, industry chit chat and networking – you can guarantee learning something or meeting someone new and useful. Far more importantly though, they’re just a damn good evening out.

Tim Meredith – Director of Unified Communications and Mobile, Daisy Group PLC

I just wanted to thank you for being an excellent host and putting on a really informative (and fun) evening. I hope to attend many future evenings!

Andy Davidson – CTO Allegro Networks, Chairman LONAP, Chairman IX-Leeds, Director Euro-IX

Lively, informative, and tasty!  That’s how I’d describe each evening I’ve spent in the company of Tref and his invited guests.  You’re guaranteed several conversations with colleagues and key decision makers at organisations across the industry over a relaxed dinner at a fantastic hand-picked menu and location.

Check out our events page here.

Categories
Business security webrtc

ITSPA Spring Workshop in association with trefor.net

It’s that time of year again – the ITSPA Spring Workshop in association with trefor.net

Another hand picked packed programme with something to suit all:) This ITSPA Spring Workshop is going to cover two hot topics: WebRTC and VoIP fraud. We have an exciting competition announcement and a real live voip hacking demo to look forward to.

ITSPA Spring Workshop

Date: 29th April 2015
Time: 2.30pm – 5.00pm
Location: Charles Russell Speechlys, 6 New Street Square, London EC4A 3LX

Session 1: WebRTC

i) Announcement of the Genband Hackathon Competition in association with trefor.net
ii) WebRTC Panel session: 2 years on from our last session on WebRTC – where is the money?

Panellists:
Stuart Goble – Genband
Matthew Hodgson – Matrix
Rob Pickering – IP Cortex
Peter Dunkley – Acision

Session 2: Fraud Part 2: Keeping your business safe and how best to report telecoms fraud

i) International Revenue Share Fraud: How, why and what we can do to stop it
ii) Real-time PBX Hacking Demo
iii) Reporting Fraud to Action Fraud

Sponsored by:in association with:
Post workshop drinks, sponsored by Lonap, will take place after the workshop 
Book your tickets now by emailing: [email protected]. Tell em you know me:)

As a footnote, ITSPA, or the Internet Telephony Service Providers Association as an organisation have been getting busier and busier. There is an active calendar of events with workshops in the Spring and Autumn, a Summer Forum that is timed to coincide with the AGM, an Awards event plus the Christmas do.

These are all great opportunities to network with the ITSP industry and for companies trying to sell to this community an ideal place to get valuable visibility. ITSPA Workshops can be sponsored to get your brand seen. You should also consider running adverts on this blog during the same weeks as the events as we typically carry more VoIP specific content at these times.

If you want to know more get in touch.

ciao

Tref

Categories
Business UC voip voip hardware

Designing for the Financial Director – IP Phone ROI

ip phone roi ip phone interoperability ip phone security lesley hansen on designing an ip phoneWhy does the Finance Director care about IP Phone Design? It’s all about IP Phone ROI

In her sixth post this week the SNOM’s prolific Marketing Manager Lesley Hansen talks about IP Phone ROI (Return on Investment).

The best quality and most elegantly designed IP Phone in the world will not be widely accepted unless it meets business expectations regarding cost. Cost in its broadest sense will include cost of acquisition, cost of deployment, cost of ownership and return on investment. Any IP Phone design must consider each and every one of these aspects. It is because of the pressure on all businesses to meet financial targets that the Finance Director is a critical player in our considerations as we design and manufacturer each new IP handset.

Since much of the motivation for moving to IP telephony is cost related building an accurate business case, including capital, implementation, and operational costs, is crucial to selecting the best vendor and architecture for your organization.

Cost of Acquisition

There are hundreds if not thousands of IP phones on the market and they range in price from around £50 for standard phones to several thousand pounds for secure encrypted handsets for use by government employees.

Soft phones are the simplest and least expensive type of IP telephone since many are available free of charge. Soft phones work through specialised software installed directly onto a PC, laptop, or mobile phone handset. With a soft phone no handset is required, but for the comfort of the user and for improved voice quality soft phones are best used with a good quality headset or USB telephone.

One you start looking at an IP handsets at the bottom of the range you find the standard phone without many bells and whistles.  Typically standard features include caller ID, limited conferencing capabilities and speed dial.  As you move up in price you gain capabilities such audio capabilities and audio quality for features such as speaker phones, wider conferencing capabilities, history memory, programmable options and support for hearing aids.

Even further on you get advanced functionality such as support for voicemail and CTI options.  You also gain connectivity options as the price increases, moving from a connected IP handset with an Ethernet port to ones that supports WiFi and Gigabit Ethernet, multiple Ethernet USB connections and even Bluetooth.

At the top of the range, excluding specialist phones such as the security handset already mentioned, are complex professional handsets with high quality audio provided through noise cancelling capabilities making them ideal for the busy and noisy office. Some come with programmable options for integration into your business processes as well as colour display screens with web access.

Depending on the role of the person using the IP Phone, there will be a different set of needs and each person will be looking for something different in their handset. An executive may want the latest and greatest IP Phone, while a receptionist may only be concerned with the number of total calls they can handle at one time. Most people want the standard features in a phone such as Call Waiting, Call Transfer, Call Parking and Conferencing. The items that will most effect the cost per handset are needs such as a high quality speakerphone, a large display and the capability for extra extensions.

So the selection of the right IP Phone is likely to involve a number of different handset types,  a range of costs to meet the difference requirements of different employees and a degree of integration with your business functions. Doing your homework on what handsets are needed by the business is likely to save the company money in the long run. Providing handsets where the price reflects the importance of features to the business is paramount.

Cost of Deployment

Hosted VoIP is increasingly being adopted to avoid the excess costs and complexities of deployment of on-premise solutions. This is great from the end customer’s point of view as they get predictable costs.  For the IP phone manufacturer it simply moves the demands for easy to  deploy handset to the service provider rather than the end customer. The need is still there. The installation, provisioning and training costs for IP handset deployment varies greatly from vendor to vendor as well as from installation to installation. For example the question of how many remote deployment teams are needed and the complexity of the server/PBX installation will affect costs.

To reduce the costs of deployment Auto Provisioning can be used to provide general and specific configuration parameters (“Settings”) to the phones and to manage firmware actualization. Deployment applications enable enterprise customers and service providers to reduce deployment costs with automated remote configuration and ongoing management of the IP phones.

The Auto Provisioning application provided by Snom allows remote administration (configuration and maintenance) of an unlimited number of distinct Snom phone types. This application enables the user to unpack a Snom handset from the box, connect it to a local network and get it up and running without the need to configure anything.

The phones can be set up manually but the easiest way to provisioning the IP Handsets is to use the built-in plug and play provisioning functionality. The phone configures itself by retrieving a PBX generated phone configuration file from interoperability partners or using the phones DHCP.  The provisioning manager needs to approve the handset registration and assign an extension. The server will send a provisioning link to the phone. Once the phone receives the link, it will apply the configuration on the fly, and will be ready to use. If a firmware update is needed, a restart will be performed.

Selecting handsets designed for remote provisioning is critical in the long term cost of any IP Telephony solution.

Cost of Ownership

A lot has been written about the ongoing costs of owning an IP Telephony systems. It’s tough to get accurate operational costs before actually incurring those costs, but we do know based on experience that operational costs tend to be highest during the first two years of usage of a new technology. Once staffs gain expertise from using the technology, the operational costs drop by about 20%.  Reports indicate that without installing a solution offering ease of operation and remote management it is easy for a company to simply spend the money they have saved on Moves, Adds and Changes (MACs) by moving to IP Telephony on the management and monitoring of the new IP telephony system. External MACs for an old TDM environments use to cost £120 on average, and range from £50 to £200 each. IP MACs typically cost under £10 each.

The Graphical User Interface of an IP-PBX or Telephony Server will be much more user friendly than traditional PBXs.  This allows for easier changes and additions. Because phones are IP based, they are like PCs, and when they are moved from one connection to another they connect right back up to the PBX server.

These offer considerable savings compared to a time when a simple phone move needed to have cross connects changed and a phone technician making a billable service call. However if the IP Handset is at a remote site and local configuration or a remote restart is needed then there can still be costs incurred.  The best way to control these costs is with the selection of a handset with remote management and configuration capabilities and from a vendor who is not prone to excessive numbers of firmware updates which require handset resets or reconfiguration.

Here the recommendation is that to keep operational costs low you ensure that the phone´s interface allows remote users to simulate the usage of the phone´s keypad and special features.

IP Phone ROI

The idea of moving to IP Telephony solely to save money has slowly subsided, although it has not gone away entirely. In the early years of VOIP, companies had to find an ROI in order to justify replacing tried-and-true equipment for new technology. Now, they’re more often already in a TDM-replacement phase, so ROI becomes less important as organizations are focusing on other benefits, such as streamlined features, improved productivity, and integrated voice/data/video collaborative applications.

To be clear, there can be a net savings, and this is typically achieved after the first two years. But this net saving is easily eroded if the IP Handset selected is not suitable so that handsets have to be replaced, possibly because the wrong model for the role was selected in the first place or because the usage levels experienced in a busy office.

While the eventual costs savings for installing IP Telephony can be substantial, the start-up costs of deploying an IP telephony solution depend on a number of variables, including the size of the enterprise and the choice of vendor. To help organizations understand the total cost of ownership (TCO) of an IP telephony.

Other posts in our IP phone design week:

How to design an ip phone
How to design an ip phone for voice quality
IP phone design for it departments
IP Phone Security
IP Phone Interoperability

Check out all our VoIP posts here.

Deployment is a key contribution of the Value Added Reseller involved in the sale. Anyone interested in becoming a Snom VAR can check out their site here.

Categories
Business voip voip hardware

IP Phone Interoperability cc @snom

No man is an island – IP Phone interoperability explored

ip phone interoperability ip phone security lesley hansen on designing an ip phoneIn the fifth article of the series SNOM UK Marketing Manager Lesley Hansen talks about IP Phone interoperability.

Ensuring that you make the most out of your investment is important and is often a consideration as you shop for a new phone system. Budget-conscious business decision makers will want to protect their investment in existing hardware or applications. Forward looking companies plan for the longer term and want to ensure today’s investment remains part of tomorrows solution,. IP phone interoperability is therefore an important issue.

Gateways can be used to help businesses connect a legacy PBX, take the first step towards SIP, or even connect to a Unified Communications(UC) solution. However using a gateway is like involving an interpreter in a conversation. The information will get across but it is slower and more likely to be subject to misunderstandings.#

Optimum performance and simplicity is achieved by selecting products that have been tested and proven to interoperate together.

There is no unique definition of ip phone interoperability because the word has different meanings depending on the context. There are also different shades of interoperability. What can be interoperable in one given system implementation may not work with another, different implementation.

The glossary of telecommunications terms, from NTIA’s ITS defines interoperability as “the ability of systems, units, or forces to provide services to and accept services from other systems, units or forces and to use the services so exchanged to enable them to operate effectively together” and as “the condition achieved among communications-electronics systems or items of communications-electronics equipment when information or services can be exchanged directly and satisfactorily between them and/or their users.”  To me the interesting words here are effectively and satisfactorily.

 The more diverse networks, products and vendors exist, the greater the need to ensure that they can interoperate to ensure that end-to-end communication is possible. At the same time, the more difficult the problem becomes.

So what happened to the standards?

Standards enable interoperability in a multi-vendor, multi-network, multi-service environment. Good standards should leave little room for options and should be universal, produced in consensus with other interested bodies. Of course, this needs time, so a proper balance between quality and speed is needed otherwise a standard that takes too long to produce becomes obsolete.

In a competitive situation not all vendors will choose to comply to all parts of the standards. Moving away from a standard in small ways is what often produces competitive differentiation. It is often non-compliance with standards that secures a long term customer unable to incorporate other vendors’ products into the network. Often, particularly  with larger vendors, a divergence from a standard will over time evolve into a new standard, further confusing business user with a wide array of incompatible standards.

End points in the telephony solution are one of the low cost high volume items in the network.  As such IP Phones are one of the aspects of the IP Telephony solution where standards and interoperability should give the business choice and flexibility without loss of functionality.  Here there is little if any justification for  the use of non-standard based products.  Even standard products however can still have interoperability issues.

Is Interoperability Important to IP Handsets?

There are two possible approaches to IP handsets.  One is to regard the handsets as disposable with a write off period of 12 or 18 months. In this case durability and interoperability are probably both moot subjects as long as the handset functions as well as needed when purchased.  The handset will effectively be written off in the first year of the project and there is no need for it to be interoperable with any other part of the network.

Alternatively there are professional and enterprise handsets where the investment in the handset is recognised as being not only the cost of the hardware but the provisioning and support and maintenance costs. In this case the build quality of the handset is likely to be considerably higher and the life of the handset considerably longer. The Snom 300 series handset for example has a life expectancy in excess of 8 years, a fact that considerably improves the ROI for any IP Telephony project.

If you make the decision to invest in a short life, low cost end points then it is possible using an Audio Lab to have the solution tested with the PBX and IP network to ensure you are not sacrificing voice quality. In a fully equipped Audio Lab you can measure the quality of your VoIP phones and VoIP accessories including wired and wireless headsets, speakerphones and conference audio-devices by utilizing state-of-the-art audio quality measurement equipment and an anechoic chamber facility.

Leading measurement technology combined with the know-how and experience of the audio quality team enables comprehensive subjective and objective testing to determine audio quality parameters to maximize VoIP device potential. The measurement system should use the IP phone specifications published in the latest ETSI and TIA releases.

Establishing IP Handset Interoperability

VoIP systems employ session control and signalling protocols to control the signalling, set-up, and tear-down of calls. They transport audio streams over IP networks using special media delivery protocols that encode voice, audio with audio codecs. Various codecs exist that optimize the media stream based on application requirements and network bandwidth.

So we must look beyond the standardised elements such as session control, signalling and codes when we look for IP Handset interoperability. This is where testing comes in and why most vendors are committed to working with partners to establish and maintain the inter-operability of their products for effective and satisfactory working. Effective and satisfactory implies the need to support the features of the device without any loss of voice quality or service or any degradation to the advertised features of the products.

For example the Microsoft Unified Communications Open Interoperability Programme tests and qualifies devices, infrastructure components, online solutions, services, and solutions provided by third party companies for interoperability with Microsoft Lync Server and clients. Their qualification programs for enterprise telephony services and infrastructure ensure that customers have seamless experiences with setup, support, and use of qualified telephony infrastructure and services with Microsoft’s unified communications software.

Testing IP Handsets

Typically only products that meet rigorous and extensive testing requirements and conform to the specifications and test plans will receive qualification in a vendors interoperability programme. While the specifications are based on industry standards, the programs also define specific requirements for interoperability with third party devices and testing requirements for qualifying interoperability. To qualify as interoperable with third party PBXs or telephony servers IP handsets must meet enterprise-class standards for audio quality, reliability, and scalability. Basic interoperability testing for IP Handset with a PBX would include items such as

  • Call Origination
  • Call Termination (calls are terminated correctly)
  • Call failure handling
  • Hold – Unhold a call
  • DTMF functionality

Additional to these basic interoperability tests the following functions are recommended for IP Handset/PBX interoperability testing:

  • VoiceMail integration
  • attended/unattended transfer
  • Music on Hold
  • Busy lamp field

As a footnote the VoIP industry periodically gets together to test ip phone interoperability. This get together was originally called the SIP bakeoff until a certain bakery products manufacturer threatened legal action. These “test fests” have long since been called SIPITs, details of which can be seen here.

Other posts in our IP phone design week:

How to design an ip phone
How to design an ip phone for voice quality
IP phone design for it departments
IP Phone Security

Check out all our VoIP posts here.

Categories
Business security voip voip hardware

IP Phone Security

ip phone security lesley hansen on designing an ip phoneIP Phone Security ensures IP Telephony is not compromising the business

She’s back again. Guest editor Lesley Hansen discusses what needs to be considered in ip phone security design.

VoIP or IP phone security is a hot topic. Security attacks continue to evolve and attackers find ever more sophisticated ways of attacking systems. VoIP is only an application running on the IP network, and therefore it inherits the security issues of the IP network. This means VoIP security is only as reliable as the underlying network security and if the IP network has security vulnerabilities, these can be exploited once VoIP is implemented.

The goal of every IP network component manufacturer should be to build a product that maintains a high level of security and provides relevant data to tools to monitor the system for attacks.  Once the system in in place ongoing IP telephony security maintenance is primarily related to the IP PBX or telephony servers; keeping up-to-date with operating system and third-party service packs to eliminate well-known security holes, implementing critical support patches on servers, updating anti-virus definitions to protect against well-known worms and viruses and performing daily backups of servers with periodic data recovery tests.

But the IP handset is an important point of access into the IP network. End points such as IP handsets provide a point of vulnerability and a number of standard exist to secure the telephony network, but these are not always supported in the IP Handset, and where supported they are not always implemented by the network manager.

Avoiding Denial of Service Attacks

Denial of Service (DoS) attacks can take down telephony. A distributed DoS (DDOS) attack is a concerted and coordinated effort to flood a network with requests. Though the attacked network may not be penetrated, these attacks can “busy” a system rendering it unusable. To protect against this it is important while implementing the IP handsets to ensure that ports are not unnecessarily left open, all unnecessary ports and services should be shut down and unused services should be deactivated. This is where interoperability partners become key.

For example PBX manufacturers like 3CX and Vodia Snom 1 and Asterix PBXs support the Snom security settings from the handset – out of the box.  This means there are no configuration requirements so delivering a rapid roll out while ensuring the system is up and running with full security and minimum disruption or delays. Not all PBX manufacturers and IP handset vendors will be interoperability partners.  To ensure a wide number of PBXs can be supported and provide the business with a high degree of choice handset vendors should work with the TLS and SRTP standards for configuration setup.

TLS and SSL encrypt the data of network connections in the application layer. They use X.509 certificates and hence asymmetric cryptography to authenticate the other party with whom they are communicating, and to exchange a key. This session key is then used to encrypt data flowing between the parties.

Protect Against Unauthorised Access

When deploying an IP telephony system IT personnel and voice administrators need to take appropriate measures to prevent threats such as toll fraud. Toll fraud refers to internal or external users using the corporate phone system to place unauthorized toll calls. Toll fraud can occur with both TDM and IP-based voice systems and a standard method of protecting against it is the ability to control call type’s for example banning mobile or international calls.

This call control is sometimes handled by low cost routing within the PBX but it can also be done within the IP handset dial plans. A handset with this capability helps to protect against telephone fraud even when the PBX does not have low cost routing.

Ideally in a well-designed handset the telephone will provide security beyond that provided by the firewall. Security at the handset ensures protection from people on the inside network who have physical access to phones and can bypass the firewall. This means the handsets provide a higher level of security against phone tapping/unauthorised access. Supporting the 8021x standard helps avoids fraudulent use of the network and protects against 3rd party/un-authorised devices. Handsets that supports 8021x, where the PBX also supports the standard, will allow the device to request authentication from the switch. This ensures that if a device connecting to the switch does not have the credentials then the switch does not allow access.

Encryption Against Eavesdropping

VoIP systems that don’t use encryption make it relatively easy for an intruder to intercept calls. Any protocol analyser can pick and record the calls without being observed by the callers. In man-in-the-middle attacks, an internal user spoofs the IP address of a router or PC to spy on voice traffic as well as data entered on the phone keypad during a voice conversation, such as passwords. After copying the information, the user forwards the voice traffic to the intended destination so that neither the sender nor the recipient knows that the conversation was intercepted. Typical motives include espionage and harassment.

Eavesdropping has become easier because of widely available packet-sniffing tools. The method used to combat this is encryption. Provided that both the handset and the PBX supports the standards, encryption ensure that the audio and the signalling traffic are both protected. Products can be configured as enabled for security so that signalling is in TLS and audio in SRTP. These security encryption standards means that all communications from the handset to the PBX/Server is protected from snooping and tapping.

Greater levels of encryption are available but at a cost. At the top of the pile Secusmart in Dusseldorf provides an encryption technology currently used by the German government that can be incorporated into the IP Handset, these handsets are forbidden for sale to counties under embargo and the end users need to be checked and validated before despatching handsets. At CeBit a Snom handset with GSMK Cryptophone technology was presented, this provides an internationally accepted secure IP handset solution that sells to sells to organisations such as military, government, pharmaceutical and broadcasting where the information has such a high value that the increased cost for the handset and call manager with encryption is justified.

Once end points with the required standards are selected, for many organisations attention to detail during set up and use of passwords, plus a controlled rollout of the handsets and strictly following instructions when installing the endpoints plus using the SRTP protocol or VPN tunnels to increase network security will provide a secure solution without the additional investment in these higher levels of encryption.

Other posts in our IP phone design week:

How to design an ip phone
How to design an ip phone for voice quality
IP phone design for it departments

Check out all our VoIP posts here.

Categories
Business voip voip hardware

What the IT department is looking for in an IP phone design

lesley hansen on designing an ip phoneIP Phone Design for IT Departments

In her third post of the week on IP phone design SNOM Technology AG Marketing Manager Lesley Hansen explores the issues that have to be taken into consideration to keep the CIO happy – IP phone design for IT departments.

The average Information Technology (IT) Department is a busy places, especially since IT and Telecoms have now come together in one area of responsibility within most organisations. The challenges posed by telephony have increased since hot desking and mobile working have become an intrinsic part of business life.

The scale may change but the same challenges apply whether you are an individual running IT for a small business or a team running IT for a large company. In addition to maintaining existing systems and handling moves, adds and changes most IT departments are actively working to introduce new systems and applications and they often also provide a helpdesk function for assistance to all staff with use systems and application software.

So when we introduce the IT department to a new IP handset it is important to have recognised the demands and pressures they are under and so we need to have made sure we have incorporated their requirements while designing the product. Critical considerations for IT are those characteristics that facilitates the easy and cost effective operation of their department. In practical terms this means we need to consider issues of support, adds, moves and changes, return on investment, configuration, maintenance and use of the handset in multiple scenarios and situations.

Supporting Moves, Adds and Changes

Moves, adds and changes (MAC) is the general term for the routine work performed on computer and telephony equipment in a business and includes installations, relocations and upgrades. The professional handset must be easy to set up and administer ongoing and must not break the IT budget and MACs can be one of the most costly aspects of supporting a telephone system.

Adding additional IP handsets involves the configuration and installation of the new handsets and it’s synchronisation with the PBX or Telephony server. With professional IP handsets today this can be done remotely by the network manager or by the Value Added Reseller using predefined user characteristics and then the preconfigure handset can be despatched directly to site to be plugged in by the user. The saves the IT specialists from travelling to site and allows them to have a central controlled view of the installations.

Change is inevitable in business as organizations grow, expand, and adapt to new market demands. Whether the changes involves moving staff or equipment in the present location or moving to an entirely new location there is a potential cost involved to the IT Team as they deploy new IP handsets or allocate users to new handsets. One of the advantages that can be designed in to an IP handset it that it can be relocated by plugging into a new Ethernet port and will automatically re synchronise with the PBX or Telephony Server.

Security Considerations

Security is a big issue today – so it is important to design IP handsets to support encryption and Snom handsets are all designed in accordance with the EU privacy recommendations. A risk of MACs is that it introduces an opportunity to security attacks. Remote Provisioning delivers substantial benefits for ITSPs & End Users, but Provisioning Servers must be secured. As a vendor we are aware that Provisioning Servers are a prime target for attack to steal SIP credentials which can then be used to make fraudulent calls.

Key protection considerations according to the Internet Telephony Services Providers’ Association (ITSPA) recommendations for provisioning are authentication of provisioning requests which should ideally be using HTTPS client certificates, ensuring that SIP passwords are deleted from SIP servers as soon as provisioned and avoiding the use of TFTP for remote provisioning. All of these considerations are important to the IT department when selecting an IP handset and Snom’s provisioning application is fully compliant with the ITSPA Recommendations for Provisioning Security, released in July 2014.

Securing VoIP communication minimizes threats to the network and the risk of theft of private information by a hackers. Security issues with a VoIP implementation often have little to do with the telephony system. If an existing network has security vulnerabilities, these can be exploited once VoIP is implemented. Your choice of handset can play a vital part in addressing security concerns. For example the Snom 710 comes with a preinstalled security certificate for quick and secure provisioning without manual interaction. It also supports the latest VoIP security protocols to ensure secure desktop communications.

Support and Cost of Downtime

Another concern for the IT specialist is downtime, a report from a major telephone supplier last year indicated that one in five companies fire an employee when a network outage occurs. The sectors where IT staff were most at risk of losing their jobs due to core network errors were the natural resources, utilities and telecoms sectors, where one in three companies fired employees. This is because network downtime is costly to the business. Gartner analyst Andrew Lerner in mid-2014 cited a figure of  $5,600 p/minute, which extrapolates to well over $300K p/hour. Even if these figures seem excessively high for your business it makes the point that the reliability, resilience and durability for all components of the network are key to the business and if neglected risk business profitability, and so the IT specialist is looking for an IP Handset that is reliable and easy to support.

Snom handsets are designed to have an have exceptionally low RMA’s – we ensure this is the case to reduce the cost to the business both in downtime and in support costs.

Costs of Ownership (COO) and Return on Investment (ROI)

A solution that will be cost effective and easy to roll out means considering not only the cost of acquisition, but the cost of ownership and life of the product but also the durability of the handset and it’s connecting network, as they effect the cost of operation and their IT budgets.

Interoperability is also key as it effects not only the cost of the solution today but also the cost to the business if changes are needed in the future. Only when all these aspects are taken into account will the IP Handset be considered to deliver value for money to the IT department. Ensure the handsets you are considering are compatible with a large number of SIP components and VoIP systems of other manufacturers. Standard based handsets reduce operational cost and complexity and so have the ability to reduce the cost of building and supporting a telephony infrastructure. Interoperability enables “best-of-breed” deployments, this best-of-breed environment meets the requirements for rapidly deploying IP Telephony solutions. Interoperability also empowers you to leverage existing investments effectively extending the life of existing components and protecting the investments you’re your business has made.

IP Handset durability is also important in this area because if reduced this increases the exchanges required due to faulty handsets, with knock on costs for repair or replacement. To keep the cost of ownership down a vendor need to ensures that the product life is sufficiently long to provide the project with a return on investment.

Further posts in this week’s guides to how to design an IP phone can be found below:

How to design an ip phone

How to design an ip phone for voice quality

Categories
Business voip voip hardware

Designing IP Phones for Voice Quality

lesley hansen on designing an ip phone designing an ip phone for voice qualityDesigning IP Phones for Voice Quality

In the second of this week’s posts on designing IP phones SNOMTechnology AG UK Marketing Manager Lesley Hansen explores the subject of designing IP phones for Voice Quality.

Voice quality is not a single thing, and it can be highly subjective. Although you can measure the voice quality of a codec used in the IP Phone each vendor’s implementation of these codecs may be different, resulting in higher or lower voice quality. But voice quality is one of the primary requirement in IP Phone design for a professional and enterprise handset and skimping on voice quality testing is one of the easiest ways for a vendor to avoid development costs and produce a sub quality handset.

What is Toll Quality?

Toll Quality is the panacea. The aim of every VoIP Vendor, and the claim of many vendors is to provide Toll Quality Voice. That is voice quality equal to that of the analogue long-distance public switched network. But it is not measurable. A common benchmark telephony vendors and carriers use and the ITU has adopted to determine the quality of is the mean opinion score (MOS). MOS is a test that has been used for decades in telephony networks to obtain the human user’s view of the quality of the network. A MOS score of 4 is perceptible but not annoying and 5 is rated as excellent. But MOS provides a subjective measurement based on a single set of circumstances. For instance the MOS score given in a quite office and that given in an office with extensive background noise would be different.

Measuring Voice over IP (VoIP) is more objective, and uses a calculation based on performance of the IP network over which it is carried. The calculation is defined in the ITU-T PESQ P.862 standard. Like most standards, the implementation is somewhat open to interpretation by the manufacturers. Even more significant, depending on the implementation by the IP Phone manufacturers, a calculated MOS of 3.9 in a VoIP network may actually sound better than the formerly subjective score of > 4.0 that was considered to be the equivalent to Toll Quality.

Building the Handset

The design of the handset will also affect audio quality, this includes aspects such as the thickness of the plastic selected and the shape of the phone. For best quality IP Phone design an audio engineer is involved with the industrial designer from the first stage of each new phone design. The audio engineer can explain the audio rules to the designer.

For instance every speaker needs a chamber to create depth of voice, the curves on the phones will affect how audio signal is reflect, and the thickness of the plastic used is critical to the final audio quality achieved.

Handset design is a trade-off between the rules of audio and the aesthetic vision of the designer. It is this seeking for high quality audio combined with pleasing aesthetic design that forces IP Phone developers to improve and come up with new solutions that take them beyond today’s knowledge on achieving high quality audio.

Selecting the CODECs

The word codec is a shortening of ‘compressor-decompressor’ or, more commonly, ‘coder-decoder’. A codec encodes a data stream or signal for transmission, storage or encryption, or decodes it for playback or editing. As with conventional telephony, with VoIP the speech is initially captured in analogue form with a microphone. This analogue information is then transferred into a digital format by a converter and changed through codecs into corresponding audio-binary formats.

In order for the data to be converted correctly back into speech after being transported, the receiver must use the same codec as the sender. Depending on the codec used, the data can be compressed to differing extents in this process. Most codecs use a procedure through which information not important for the human ear is omitted. This reduces the amount of data and thus reduces the bandwidth required for transfer. However, if too much information is omitted, the speech quality will suffer.

Different codec procedures handle the audio compression with different levels of efficiency. Some are specifically designed to achieve a low bandwidth at any cost. Depending on the codec, therefore, the bandwidth needed and the speech quality will vary. The design skills of the IP Phone manufacturer in the management of codecs creates a clear differentiation between vendors.

Refining Voice Quality

Methods such as jitter buffers, echo suppression, echo cancellation and packet loss concealment can be used in IP handset design to improve voice quality.

Echo suppressors work by detecting a voice signal going in one direction on a circuit, and then inserting loss in the other direction. This added loss prevents the speaker from hearing his own voice. Echo cancellation is based on recognizing the originally transmitted signal that re-appears, with some delay, in the transmitted or received signal. Once the echo is recognized, it can be removed by subtracting it from the transmitted or received signal.

When silence suppression is on, comfort noise needs to be generated locally by the IP Handset at the other end of the call so that the other party will not mistakenly believe that the call has been terminated. By preventing echo from being created or removing echo if it is already present voice quality is improved, at Snom we call this Automatic Noise Reduction.

IP Phones echo controls are implemented digitally using a digital signal processor (DSP) or software and at Snom we implement to the ITU requirements. Digital signal processing is the mathematical manipulation of the information signal to modify or improve it. DSP is not one size fits all. Different DSP coefficient pre-sets are needed for different room types. Refining the voice using these techniques will improve the subjective quality, as an additional benefit the process also increases the effective use of bandwidth as silence suppression prevents echo from traveling across the voice network.

Transmitting high quality voice over IP is made more difficult due to packet loss and jitter. A technique used to reduce jitter involves buffering audio packets at the receiving handset, so that slower packets arrive in time to be played out in the correct sequence at the appropriate times. The objective of jitter buffering is to keep the packet loss rate low and so improve the voice quality. A fixed method, which uses a fixed buffer size, is easier to implement than an adaptive method, but will result in less satisfactory audio quality because there is no optimal delay when network conditions vary with time.

Snom handsets support adaptive jitter buffers which although more complex and expensive to implement perform continuous estimation of the network delays and dynamically adjust the playout delay at the beginning of each transmission so ensuring a high quality of voice.

Packet loss concealment (PLC) is a technique to mask the effects of packet loss in VoIP communications. Because the voice signal is sent as packets on a VoIP network, they may travel different routes to get to destination. At the receiver a packet might arrive very late, corrupted or simply might not arrive. This could happen where a packet is rejected by a server which has a full buffer and cannot accept any more data. In a VoIP connection, the receiver should be able to cope with packet loss.

All these voice techniques enhance and improve voice quality, and are quantifiable and measurable components of high quality IP Phone design and should be viewed as absolute requirements in professional and enterprise handsets.

Testing the Voice Quality

Testing voice quality on a new product should begin as soon as a first injection of plastic is produced and continue throughout the life cycle of the product.  In Snom we believe in the value of doing our testing house and have made a considerable investment in German engineered state of the art Audio equipment that will simulate not only the voice from the phone handset and speaker phone and in relationship to the human head, but also test for voice quality under different conditions such as with background noise from a busy office or factory and in a variety of network conditions. Ongoing testing ensure the quality of voice provided by VoIP phones and VoIP accessories and end points including wired and wireless headsets, speakerphones and conference audio-devices.

Accurate and effective audio measurements require time, preparation and patience. Snom’s testing in done in our Head office in Berlin using our state-of-the-art audio quality measurement equipment and anechoic chamber facility. Leading measurement technology combined with the know-how and experience of the Snom audio quality team enables comprehensive subjective and objective testing to determine audio quality parameters to maximize VoIP device potential. The measurement system uses the IP phone specifications .published in the latest ETSI and TIA releases.

Check out a past article on SNOM audio quality testing here. Also the first post in this series of designing IP phones can be found here.

Categories
Business voip voip hardware

How to design an IP phone

lesley hansen on how to design an ip phoneWhat is involved in designing an IP Phone?

Lesley Hansen is UK Marketing Manager of German SIP handset vendor SNOM Technology AG and is this week guest editor of trefor.net. This role of guest editor is one that I have introduced to bring a focus on specific themes and is an enhancement of the “themed weeks” that have become so successful on this blog.

Lesley is a time served veteran of the telecoms industry and SNOM are one of the oldest players in the SIP game. SNOM were there right at the beginning of the SIP industry before commercial services were available. When SNOM introduced their first handset the only other vendors around were Siemens and Pingtel (long since deceased). SNOM and Lesley are uniquely positioned to talk about their subject.

This week Lesley  has at my invitation put together  a series of posts outlining the issues and challenges involved in the design and manufacture of IP Telephony handsets. SNOM are obviously going to get a lot of mentions in this series but the intent is not to be a sales pitch for the company. It is natural for Lesley to refer to her own company’s experience in writing the pieces. In this first post Lesley outlines the areas that she is going to cover this week.  She refers to articles that are coming during the week and to which I will link as they go live. I leave the rest to her…

This is the introduction to a multi-part series of articles looking at the issues involved in designing an IP phone. Founded in 1996, Snom Technology AG manufactured the world’s first SIP Handset and continues today to provide a market leading brand of professional and enterprise IP Handsets. As such we are exceptionally well qualified to discuss the concerns and challenges of designing IP Phones.

What is an IP Handset?

A VoIP or IP phone is simply a handset that uses Voice over IP (VoIP) technology to allow calls to be made and received over an IP network (like the Internet) instead of using the traditional Public Switched Telephone Network (PSTN). The audio signals from the voice calls are digitized into IP data packets, the handset is connected to an IP network and these IP packets are routed through a private IP network or over the public Internet creating a connected voice call.

IP Phones look very much like traditional office handsets but they are based on a different underlying technology. The use of IP Technology raised potential issues of call quality due to the breaking of the voice into small data packets and these have to be managed in the handset design, and since IP Phones interface with VoIP system telephony software, they have to be able to support features and capabilities that were not provided by traditional office phones. This additional functionality makes the user interface more critical to ensure an easy to use and reliable handset. A good quality of design in an IP Phone can make the IP Handset a valuable resource for many years. A poor design can deliver poor quality voice and become an expensive resource to support and a source of much frustration from business users.

Designing to meet user expectations

Users have clear demands. They want their IP Phones to work and they want them to look good. The problems in designing an IP Phone arise when we try to quantify what working and looking good really means. Elegance and simplicity are very important in phone design but must be balanced with practicality and ease of use this is one of the challenges of IP Phone design. (Further Information: Article on Designing for Beauty)

People are very finicky about voice quality in VoIP because they were used for years to the impeccable quality of landline phones.  The standard for voice quality on a telephone handset has therefore been set by the PSTN and this is what we refer to as toll quality voice.

Voice quality was one of the darkest spots on VoIP’s reputation the early years after its introduction. Now there has been much improvement. For toll quality voice to be achieved on an IP Phone the issues created by using a packet based network where there are no inherent controls on the order or speed of delivery of the packets have to be considered in the phone design. Echo, choppy voice, broken voice, buzzing and delayed speech are common descriptions of problems experienced with the early VoIP connections.  Although some of these factors are the result of a variety of factors not all related to the handset itself, the handset design must minimise the effect of each of these. The one of these most attributed to the IP Handset is echo and designing for echo cancellation and control is key. (Further Information:  article on Voice Quality)

Designing for the demands of IT

One of the challenges with an IP Phone is that the handset has to be configured before the phone can talk to the IP Telephony PBX or IP Server, so before the phone can be used. Provisioning is critical, at its core, the provisioning process monitors access rights and privileges to ensure the security of an enterprise’s resources and user privacy. As a secondary responsibility, it ensures compliance and minimizes the vulnerability of systems to penetration and abuse. In a good quality phone design it is possible to configure phones centralised, which saves a lot of time and money in sending personnel to site.

But the demand is not only these during setup, the design should also ensure updating phones or setting special configurations is easy. This is possible because of this centralisation. Auto-provisioning or auto-configuration is the name we give to this easy and time-saving way to configure IP-phones for IP-PBXs. With auto-provisioning, all user information is entered at the central web interface of the PBX or form the IP Phone management software.  Required data includes the MAC address of the IP-phone, the desired extension and the caller ID which is displayed on the called party phone display. The IP-phone receives the configuration over the local IP network. (Further Information:  Article on Designing for the IT Department)

Ensuring IP Telephony is not compromising the Business

The growing reliance on VoIP has reduced business telephony costs, but it also increases their complexity and this needs to be kept in mind in the IP Handset design. Security has become one of the hottest issues in telecom management. IP telephony not only increases the complexity of data networks, particularly in hybrid telephony environments built with equipment from multiple vendors but it increases security risks. For IP telephony management to be effective it cannot focus solely on reporting on network usage, ensuring dial tone availability and managing call quality, it must place an emphasis on security and protecting the enterprise from telephony-borne attacks.

Today telecom managers face pressure to protect the organization from telephony-related threats, and to do it all while cutting costs and improving ROI. Security measures such as encrypting voice services, placing VoIP equipment behind firewalls, and defending against Denial of Service (DoS) attacks are just some of the steps you can take when introducing VoIP into your organization’s network infrastructure.  Other measures include guarding against toll fraud, securing phone records, and protecting the phones. While there is no such thing as a bulletproof VoIP implementation, you can protect your business by selecting IP Handsets designed to provide high quality security to the business. (Further Information:  article on Designing for Security)

No man is an island – and neither is an IP Phone!

Many solutions using IP Phones are hybrids. A hybrid telephony solution could be mixing either IP or PSTN, it could involve a mix of hosted and on premise telephony services and to get the fully set of functionality needed by the business it is likely to include hardware from multiple vendors. Even if an IP Telephony solution is deployed as single vendor, single deployment single technology it is highly likely that over time elements of third party products or new technologies will be introduced.

It is therefore very important when designing an IP Handset that standard are complied with consistently to ensure the IP Phone is able to operate in a mixture of existing and potential environments. Snom’s operates an interoperability program that gives customers the opportunity to find out which components work with each other. To assure the interoperability between the IP Phones and other elements of the IP Telephony solution, all Snom handsets undergo a range of interoperability tests in our labs. Advanced features such as transfer and Music on Hold are required to work. For our partners gaining the Snom Advanced level of interoperability means that the customer can be assured that the tested functionality works smoothly. (Further Information:  article on Designing for Interoperability)

And the final design criteria – cost

The best quality and most elegantly designed IP Phone in the world will not be widely accepted unless it meets the business expectations regarding cost. Cost in its broadest sense will include cost of acquisition, cost of deployment, cost of ownership and return on investment. Any IP Phone design must consider each and every one of these aspects. (Further Information:  article on Designing for the Financial Director)

Snom’s investment in Handset design is significant and over 45% of our workforce is focused on Handset design, testing and development. This approach has made Snom a leader in the market and unique software and hardware developments on the Snom handsets are emulated by many other IP Telephony and Handset manufacturers.

Lots and lots of VoIP posts on trefor.net – check em out here