Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

February 26 2014


November 18 2013

Zula, The Mobile Collaboration App From VoIP Pioneer Jeff Pulver, Gets A Seed Round From Microsoft Ventures
Microsoft took a big step into enterprise collaboration when it acquired Yammer, and an equally big step into VoIP when it bought Skype. Now it's taking an investment in Zula, a new startup that is offering a solution for how those two kinds of services might potentially work together. The Israel-based mobile collaboration app co-founded by Jeff Pulver, one of the original people behind Vonage and VoIP, is today announcing a seed round from Microsoft Ventures.
Sponsored post
Reposted byLegendaryy Legendaryy

July 09 2013

Google Finally Brings Voice Calling To Hangouts, But Not To Its Mobile Apps
Some Google fans were mighty miffed when Google removed the ability to make voice calls from inside Gmail, but now the feature is back, flying under Google's Hangouts banner. Instead of just being able to place calls from within Gmail though, users can dial up friends and family while poking around on Google Plus or by using the Hangouts Chrome extension.

August 13 2012

VoIP Service KeKu Hits 500K Users, Quietly Launches Group Calling App
We wrote about the official launch of KeKu, a New York-based VoIP telephony startup earlier this year and since then, the company has managed to grow quickly. Today, KeKu announced that it hhas surpassed 500,000 customers around the world who use its free and paid services. The company, which offers Android and iOS calling apps, allows users to make free VoIP calls between its users and also offers cheap international calls to cell phones and landlines by allowing users to assign local numbers to their friends and family.
Tags: TC keku voip ios

May 04 2012

Twilio Expands Again In Europe, Adds VoIP API In Belgium, Finland, Netherlands, and Sweden
Twilio Europe
Twilio, the upstart software maker of voice and other telephony APIs used by developers in web and mobile apps, is marking another chapter in its European expansion today: the company's voice API -- which lets users make and receive calls through those apps -- is now available in Belgium, Finland, the Netherlands and Sweden, bringing the total number of countries supported on this side of the pond up to 10, in addition to the U.S. and Canada. The news comes in the same week that Twilio announced a strategic partnership with Microsoft that will see the Windows giant offering Twilio voice and text APIs to developers on its Azure cloud platform, and one week after the company announced a significant hire for its European team, James Parton, as a new European VP.

April 27 2012

Twilio’s European March Continues With Its First Full-Time Hire Outside The U.S. [And Telefonica Loses One]
Twilio Logo
Twilio, developer of a VoIP API that is used by companies like eBay, Airbnb and Hulu to add voice services into their consumer apps, has been adding support for European countries as part of its expansion strategy, first the UK and then Austria, Denmark, France, Ireland and Poland. Now Twilio is giving that effort a bit more muscle with the appointment of its first employee outside the U.S. James Parton is joining the company as its new European marketing director. His hiring is also effectively a jab at the carrier market that Twilio very much has the chance to really disrupt: Parton has been poached from Telefonica, the Spanish mobile powerhouse, where he has most recently been running developer marketing for Telefonica's multi-regional API effort BlueVia, and before that for BlueVia's more local precursor, Litmus at O2 UK.

December 12 2011


life# reload

Post image for life# reload

If you’ve been reading Evil Routers for a while, you already know that, back in May, I quit my job.

The idea was that, after I took care of some things here, I’d eventually move to the west coast. Basically, that never happened. I got lazy over the summer and did absolutely nothing that I needed to do and, instead, took advantage of all the free time to do things that I’ve wanted to do (not necessarily a bad thing).

In addition, I started a company to pursue a couple of ideas I’ve had for a long time. As you might guess, that required a lot of my time for a good while (like, every waking moment of every day). I’ve managed to off-load most of that to others and my involvement is pretty minimal at this point, which has freed up a lot of my time.

I was working on that “project” when I headed out to San Jose with my fellow networking nerds for Net Field Day 2. While there, I received an e-mail from a guy who reads this blog. He knew of a company in my area that was looking to fill a recently vacated position and wondered if I might be interested. I wasn’t really looking for a job at the time but I said I’d be willing to meet up with the guys and at least talk to them.

A few days after returning from NFD, I met up with the two guys at a restaurant to discuss their businesses, their needs, goals, and future direction. By the time we left, they had offered me a position there.

Like @fryguy_pa, I, too, have made a new start. My first day was just a couple of days after our little meeting. I would have preferred to wait a week or two, but they were anxious and excited for me to get started.

Officially, I am working for one of their companies, which I could best describe as a VAR and provider of outsourced IT. For some of our customers, we are their only IT support. Other customers have their own in-house IT staff and simply call on us when they’re in over their head and could use a little help. Without going into much detail, most of my work thus far in this role has centered around resolving server-side issues (like huuuuge SQL databases filling up the volume) and installing and maintaining Cisco ASAs.

In the coming weeks and months, I expect I’ll also get to work with various wireless technologies and VoIP as well. I’ll be involved in many different things but that should keep it interesting. So far, no two days have been exactly the same.

The other half — and more exciting part — of my work is for one of their “sister companies”, which is a wireless Internet Service Provider (WISP). Ironically, not long before meeting up with these guys, I decided that I’d like to work for a service provider, which I imagined would be a completely different environment that what I was used to at the .edu. Boy, was I ever right.

To borrow a word that my boss used a few days ago, the current network can best be described as a “clusterfuck”. When the WISP started out, they apparently took the “easy way” of doing things. That actually worked out just fine while they were relatively small. As the business and customer base has grown, however, the things that have been done in the past just aren’t going to cut it anymore.

To provide an example, the network currently stretches over a huge geographical distance with gear on a total of 54 towers and the customers numbering in the four digits. The entire network, however, is bridged.


Yep, one flat layer 2 network. One big broadcast domain.

I’m fairly certain that I don’t need to explain to any of you why this is bad, so I’ll save my breath. I think we can agree, though, that this only scales to a certain point and, well, we’re pretty much at that point.

Anyway, in the coming weeks I certainly have a challenge on my hands. In order to achieve some of the goals of the business (which I’ll talk more about later), one of the first things we need to do is get away from bridging and instead start routing traffic across our network. Considering this means we’ll likely have to touch nearly every piece of CPE gear out there, this is no small feat!

I’ll keep you updated in the coming weeks as this project (and my new position) progresses. Fortunately, the work ahead of me will, I’m certain, lend itself to some interesting (and maybe some not-so-interesting) posts. Stay tuned!

Related posts:

  1. How To Make Your Routers Reload Faster
  2. Conferences, certifications, and such…
  3. The EC2/EBS outage: What Amazon didn’t tell you

July 29 2011


VU#690315: Avaya Secure Access Link (SAL) Gateway information disclosure vulnerability

Vulnerability Note VU#690315

Avaya Secure Access Link (SAL) Gateway information disclosure vulnerability


Avaya Secure Access Link (SAL) gateway releases 1.5, 1.8, and 2.0 have an information disclosure vulnerability in the default install.

I. Description

According to Avaya's Product Support Notice PSN003314u [PDF]:

"On installation of SAL Gateway with the default properties provided along with the installer, the Secondary Core Server URL and the Remote Server URL points to the and respectively which are invalid public domain servers and not owned by Avaya. These servers resolve to invalid domains and pose a security threat. Secondary Core Server URL should be same as the primary Core Server URL and Secondary Remote Server URL should be same as the primary Remote Server URL."

II. Impact

Information from the SAL gateway, such as alarms or logs, may be sent to and email addresses.

III. Solution

The Avaya Product Support Notice PSN003314u [PDF] states:

"To resolve this problem, please do the following steps:

  1. Login to the SAL Gateway UI with the user having either Security Administrator or Administrator role.
  2. Navigate to the Administration section of the SAL Gateway menu, click on Core Server.
  3. In the Secondary Core Server field, enter the host name same as the primary Core Server hostname for the secondary Secure Access Concentrator Core Server.
  4. In the Port field, enter the port number same as the primary Core Server port number for the secondary Secure Access Concentrator Core Server.
  5. Click on Apply.
  6. Navigate to the Administration section of the SAL Gateway menu, click Remote Server.
  7. In the Secondary Remote Server field, enter the hostname same as the primary Remote Server hostname for the secondary Secure Access Concentrator Remote Server.
  8. In the Port field, enter the port number same as the primary Remote Server port number for the secondary Secure Access Concentrator Remote Server.
  9. Click on Apply.
  10. Logout from the Gateway UI."

Vendor Information

VendorStatusDate NotifiedDate Updated Avaya, Inc.Affected2011-07-272011-07-28



Thank you to the reporter who wishes to remain anonymous.

This document was written by Jared Allar.

Other Information

Date Public:2011-05-16 Date First Published:2011-07-29 Date Last Updated:2011-07-29 CERT Advisory:  CVE-ID(s):  NVD-ID(s):  US-CERT Technical Alerts:  Severity Metric:0.91 Document Revision:11

Tags: Avaya VOIP leak

May 25 2010


Port forwarding a range of ports on Cisco IOS

One question that routinely comes up in a particular forum that I frequent is “How do I port forward a range of ports?”  Usually, this question is met with one of two answers:  1) you don’t, or 2) manually enter 10000 “ip nat …” statements.

The correct answer is actually number three.  It turns out that it is, indeed, possible to forward a range of ports in IOS.  I tested this in my lab and everything works just as I would want it to.  Here’s the topology:

We have a single router that we’re using.  The RFC1918 address block 192.168.0/24 is being used internally, and the router will NAT all internal addresses to its public address,, as it forwards it out FastEthernet 0/0.

The PC at will represent a host on the Internet, attempting to access services on the PC at  Since falls in the RFC1918 address space, we’ll need to use Port Address Translation (PAT), or “port forwarding”, on the router.  This is nothing new and most of us probably do it all the time.  The problem arises, however, when we want to forward a large number of ports — typically ports 10000-20000 for Voice over IP (VoIP).

As I mentioned, there is a way to do this, and it’s easier than you think.

First, set up your basic NAT configuration (“ip nat inside”, “ip nat outside”, etc.).  Check out “Configuring Basic NAT with overloading“, if necessary.

Next, let’s create an IP NAT pool, for a single IP address (the IP address of the internal host,

R6(config)# ip nat pool PORTFWD netmask type rotary

Then, create an access list (ACL) matching the ports you want forwarded.  In the case of 10000-20000/UDP for VoIP, we can use the “range” keyword to simplify things for us tremendously:

R6(config)# access-list 100 permit udp any any range 10000 20000

Last, we’ll tie our access-list 100 to the PORTFWD NAT pool that we created:

R6(config)# ip nat inside destination list 100 pool PORTFWD

Now, any UDP traffic coming into our router’s public interface (FastEthernet 0/0) with a destination port between 10000 and 20000 will be forwarded to the host at  I was able to verify this by generating UDP traffic on my MacBook and having the router forward it to another laptop with a tcpdump capture up and running — it worked wonderfully.  I was running 12.4(10a) on a 2621XM.  Try it out and let me know if it works for you as well!

Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.
No Soup for you

Don't be the product, buy the product!

YES, I want to SOUP ●UP for ...