Category
T-38
See Us at ITEXPO West in Austin
- September 19th, 2012
- analog telephone adapter, bladeware, blog, event, fax, g.711, itexpo, itsp, smart ata, t.38, v.34
- 0 Comments
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
- August 15th, 2012
- analog telephone adapter, blog, g.711, pcm clock-sync, sip forum, t.38, testing, v.34
- 0 Comments
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
- March 12th, 2012
- blog, g.711, itsp, smart foip, t.38
- 0 Comments
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
What Does Great OEM Developer Support Look Like?
- November 10th, 2011
- blog, fax oem, pcm clock-sync, t.38
- 0 Comments
What does great OEM developer support look like? Here’s but a small sample. It’s a response by our support guy to a question from a T.38 relay licensee. Full Post
The Smart ATA Story: Solving Three Big FoIP Problems
- August 25th, 2011
- analog telephone adapter, blog, g.711, itexpo, pcm clock-sync, smart ata, smart foip, t.38, v.34
- 0 Comments
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 Needs ENUM!
- July 5th, 2011
- bladeware, blog, sip forum, t.38
- 0 Comments
Two years ago we did some serious outbound testing with the cooperation of Copia International, one of our enterprise-fax server OEMs. Copia’s CopiaFacts is a full-function server for the enterprise, but it has a bunch of features that the mission-critical fax-broadcast guys find to be really helpful. So we were able to gather some very beneficial data as Copia performs evals for broadcast customers. Full Post
FoIP Presentation at ITEXPO East 2011
- February 7th, 2011
- analog telephone adapter, bladeware, blog, g.711, itexpo, itsp, sip forum, t.38, v.34
- 0 Comments
Here’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
- January 7th, 2011
- blog, g.711, t.38, v.34
- 0 Comments
Cliff Schornak
Smart FoIP in Gateways
- November 8th, 2010
- blog, g.711, smart foip, t.38, v.34
- 0 Comments
The 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!
- September 16th, 2010
- blog, g.711, itsp, t.38
- 0 Comments
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
