See Us at ITEXPO West in Austin

Hope you're going to ITEXPO West 2012 in Austin (Oct. 2-5). We'll be there in booth 722. If you're an ITSP and trying to make FoIP work, save yourself some aggravation and come to see us since we have "FoIP in a box" for you. Full Post

The State of FoIP: 3Q2012

In 3Q2012, the state of FoIP is good. Why? Because the right things are happening. In the enterprise, FoIP has become a given in the corporate network. True, many smaller organizations still keep their POTS lines for fax, but in larger private networks, fax is either done over SIP trunking or via gateways to the PSTN. But the real action is in service provider and carrier networks. Full Post

Reporting from the Trenches in the FoIP Wars

What is the key to FoIP success when using SIP trunking? First, you must have FoIP endpoints that really work. They must support both G.711 pass-through and T.38 FoIP. And, if they don’t have Commetrex’ Smart FoIP, you’re going to have to accept an up to five-percent failure rate regardless of what you do. Full Post

ITEXPO West 2011

Just returned from ITEXPO. It was in blazing-hot Austin, TX, which is a very cool town. And it was very cool for Commetrex and NetGen Communications, our sister company, which is producing and marketing Smart ATA, which we announced at the show. It also turned out to be way cool for the ITSPs who stopped at our booth when they learned about Smart ATA, and what it could do for their success with FoIP. Full Post

The Smart ATA Story: Solving Three Big FoIP Problems

If you read our newsletters, you may remember that Commetrex has developed a new FoIP technology, Smart FoIP, which, among other things, improves the success of FoIP session establishment by up to 10% in SIP networks. Now, instead of talking about technology, we’re talking about a product that uses the technology to solve major problems for the industry. Full Post

FoIP Presentation at ITEXPO East 2011

i3 forumHere’s a summary of my talk at ITEXPO given on 2/3/11. “Telefacsimile” went commercial 150 years ago. Seems like yesterday, doesn’t it? G3 fax, made possible by the microprocessor, is now 31. And T.38 turned 12 last October ... a mere kid. Full Post

Cut the Big Guys Some Slack

Cliff Schornak

Cliff Schornak

In marketing, it’s axiomatic that the market leader enjoys the highest margins, but it doesn’t end there. It extends to giving the large company a ride when it comes to interoperability problems in the field. If there’s a problem, it must be the little guy. Right? In this case, the little guy is Commetrex. And even though we can make a very strong case for being the industry’s interop leader, we still must prove that it’s not our problem if the other vendor is much bigger then we are. Goes with the territory. Full Post

Smart FoIP in Gateways

Smart FoIPThe wide-scale deployment of V.34 fax terminals is making the design of FoIP-capable IP-PSTN gateways much more of a challenge since V.34 terminals employ a completely different start-up sequence than non-V.34 machines. Moreover, since gateways typically begin calls in G.711 pass-through mode (rather than T.38), V.34-capable endpoints can actually “hear each other” well in advance of the resolution of the SIP signaling resolving the session’s setup. This means the gateways must take an “activist” role to ensure that T.38 is “given a chance” prior to the endpoints going on their merry way, leaving the gateways behind. Full Post

T.38′s Not the Problem!

Whenever I hear someone tell me that T.38 isn’t capable of bringing reliable real-time fax to IP-carrier networks, I resist the temptation to roll my eyes. Instead, with missionary zeal, I explain that if T.38 provides reliable fax in enterprise IP networks, and, if real-time fax is problematic in carrier networks, it’s not because there is a problem with T.38, there’s a problem with the way it’s being used ... possibly abused. You might argue that it doesn’t matter why, either it does the job or it doesn’t. Good point. Read on. Full Post

What Gives with V.34 Fax?

Currently, there are not many V.34-capable gateways available, and only one V.34-capable FoIP fax server. This is so despite the fact that over half of the machines installed in the last five years support V.34. So, what gives? Full Post