{"id":754,"date":"2011-12-13T19:29:40","date_gmt":"2011-12-13T19:29:40","guid":{"rendered":"http:\/\/192.168.16.235\/?page_id=754"},"modified":"2020-01-17T10:12:30","modified_gmt":"2020-01-17T10:12:30","slug":"the-outlook-june-2010","status":"publish","type":"page","link":"https:\/\/commetrex.com\/?page_id=754","title":{"rendered":"The Commetrex Outlook | June 2010"},"content":{"rendered":"

[vc_row css_animation=”” row_type=”row” use_row_as_full_screen_section=”no” type=”grid” angled_section=”no” text_align=”left” background_image_as_pattern=”without_pattern” el_class=”newsletter_inner_page” z_index=””][vc_column][vc_column_text]<\/p>\n

We Make FoIP Work!<\/h3>\n

 <\/p>\n

Now that enterprises are extending the reach of their IP networks by connecting directly with IP carriers and SIP trunking, we are confronted with challenges of a different sort. The front lines of the FoIP wars have moved.<\/p>\n

 <\/p>\n

In his latest CEO Commentary, Mike Coffee discusses how Commetrex is fully engaged in \u201cmaking FoIP work.\u201d Today, we are working with carriers to correct the problems within their networks that are keeping FoIP from achieving the transaction success rates of PSTN fax. If IP is going to replace TDM, it has to happen, and Commetrex is leading the way.<\/p>\n

 <\/p>\n

Check out his CEO Commentary to learn how “We Make FoIP Work!” And there\u2019s more information on our Blog.[\/vc_column_text][\/vc_column][\/vc_row][vc_row css_animation=”” row_type=”row” use_row_as_full_screen_section=”no” type=”grid” angled_section=”no” text_align=”left” background_image_as_pattern=”without_pattern” el_class=”newsletter_inner_page” css=”.vc_custom_1578991890670{padding-top: 70px !important;padding-bottom: 70px !important;}” z_index=””][vc_column el_class=”newsletter_inner_page_bg”][vc_column_text]<\/p>\n

An Industry First: Commetrex Enhances BladeWare With G.711 Pass-Through Support For V.34<\/h3>\n

 <\/p>\n

Commetrex, inventor of T.38 fax termination now used in media servers everywhere, continues its record of innovation with the announcement of its industry-first support for V.34 G.711 pass-through in its BladeWare HMP telephony platform. This means that BladeWare users can elect to complete IP fax calls using V.34, rather than forcing a fallback to V.17 speeds, which take twice as long to transmit a page. This is important since there are few T.38 Version 3 V.34-capable gateways on the market, and none deployed in carrier networks. Indeed, many VoIP service providers have yet to support T.38 in any version. In these situations, BladeWare delivers faxes with one-half the connection time of any server on the market.<\/p>\n

 <\/p>\n

For example, here at Commetrex we use Cbeyond, an all-IP managed-services provider, for all of our communications over a 3-Mbit clear-channel pipe to Cbeyond\u2019s private metro network. But they don\u2019t support T.38. Instead, all faxes are handled with G.711 pass-through, including V.34, and they are virtually error-free. A BladeWare-based server is setup to use Cbeyond\u2019s SIP trunking. It\u2019s all software, all IP, and with V.34 support.<\/p>\n

 <\/p>\n

\u201cBut how can that be?\u201d you say. \u201cMy vendor tells me that G.711 pass-through fax just doesn\u2019t work.\u201d Well, your vendor has a biased perspective since he can\u2019t do it, and doesn\u2019t want you to ask for it, knowing that only Commetrex supports V.34. Yes, there are networks where G.711 pass-through does not perform well, but there are many where it does. The example above is one. And how about when an IP PBX without T.38 support is being used as the gateway between the PSTN and the fax server? There, the IP connection is over a high-performance LAN. No packet loss need be dealt with, and Commetrex\u2019 exclusive PCM-clock management software means even long G.711 faxes come through error-free.<\/p>\n

 <\/p>\n

Need a fax-resource platform to support IP and PSTN? We make FoIP work! Commetrex\u2019 BladeWare provides the industry\u2019s highest performance, richest feature set, highest scalability, and all at one-third the price. Give us a shot:\u00a0sales@commetrex.com<\/a>\u00a0or 1-770-449-7775 and press 1 for sales.[\/vc_column_text][\/vc_column][\/vc_row][vc_row css_animation=”” row_type=”row” use_row_as_full_screen_section=”no” type=”grid” angled_section=”no” text_align=”left” background_image_as_pattern=”without_pattern” el_class=”newsletter_inner_page” css=”.vc_custom_1578991890670{padding-top: 70px !important;padding-bottom: 70px !important;}” z_index=””][vc_column el_class=”newsletter_inner_page_bg”][vc_column_text]<\/p>\n

SIP Forum FoIP Task Group Update<\/h3>\n

 <\/p>\n

The Chair of the FoIP Task Group is rotating from Dialogic to Cisco and Commetrex co-chairing the group. After serving as the chairman for a full year, Neil Weldon, of Dialogic is moving aside for Gonzalo Salgueiro, of Cisco, and Mike Coffee, of Commetrex. In addition to his co-chair duties, Gonzalo intends to focus initially on making sure the task group\u2019s work product makes it to the appropriate standards organizations on time. Coffee will work to engage the i3 Forum to take full advantage of their growing cooperation to make contributions to the industry together that they could not readily make individually. The first task will be joint testing to quantify the ability of international tandem networks to reliably set up SIP-based FoIP calls.<\/p>\n

 <\/p>\n

After attending the i3 Forum\u2019s meeting in Rome in January, Cliff Schornak, Commetrex\u2019 CTO, and Kevin Fleming, of Digium, participated remotely in the i3 Forum\u2019s meeting in Madrid. They reviewed several of the works in progress with the SIP Forum\u2019s task group and provided Cliff with documents that detailed some of their in-process considerations. And just last week, Cliff attended the i3 Forum\u2019s June meeting in Warsaw, where he and Jerzy Sodrowski were successful in recruiting several of the i3 Forum members in performing FoIP tests in cooperation with the SIP Forum. We will design and implement the tests and test platform over the summer, with testing scheduled for mid-September.<\/p>\n

 <\/p>\n

The task group\u2019s three subcommittees have been busy. The T.38\/V.34\/V.8\/V.152 Call Flow group has submitted their\u00a0document to the ITU<\/a>. T.38 Problems Related to SIP\/SDP produced a new draft on March 17. And a document with a variety of exemplary SIP call flows is in process.<\/p>\n

 <\/p>\n

Learn more about the task group here.\u00a0www.sipforum.org\/content\/view\/310\/252<\/a>\u00a0Here is a link to a recent joint press release from the SIP Forum and the i3 Forum.\u00a0www.sipforum.org\/content\/view\/364\/171<\/a>.[\/vc_column_text][\/vc_column][\/vc_row][vc_row css_animation=”” row_type=”row” use_row_as_full_screen_section=”no” type=”grid” angled_section=”no” text_align=”left” background_image_as_pattern=”without_pattern” el_class=”newsletter_inner_page” css=”.vc_custom_1578991890670{padding-top: 70px !important;padding-bottom: 70px !important;}” z_index=””][vc_column el_class=”newsletter_inner_page_bg”][vc_column_text]<\/p>\n

When Is A Fax Board Not A Fax Board?<\/h3>\n

 <\/p>\n

When it\u2019s a Commetrex MSP board, that\u2019s when. You see, we don\u2019t actually sell fax boards or voice boards. With the power of today\u2019s PCs, that just doesn\u2019t make much sense since a 2.2-Gig dual-core PC comfortably runs 60 V.17 channels with plenty of headroom left for your application. Once you\u2019ve paid for the PC, which you gotta have anyway, using the available MIPS costs you no more than leaving them idle. So why not pay less than $200 per channel for your \u201cfax board,\u201d (software included) rather than $600?<\/p>\n

 <\/p>\n

And BladeWare now supports V.34, which requires more MIPS than V.17, but that\u2019s not a problem. If you run BladeWare on a dual-core Intel-architecture machine, sending a V.34 fax requires 25 MIPS while receiving a V.34 fax requires 33 MIPS. So, more than half the MIPS are available for your application. Need more channels? Get a quad-core machine.<\/p>\n

 <\/p>\n

The price of these boards reflects their bare-bones functionality. What\u2019s more, you write just one resource adapter, which enables your application to address<\/p>\n