{"id":760,"date":"2011-12-13T19:54:08","date_gmt":"2011-12-13T19:54:08","guid":{"rendered":"http:\/\/192.168.16.235\/?page_id=760"},"modified":"2011-12-13T19:54:08","modified_gmt":"2011-12-13T19:54:08","slug":"the-outlook-november-2009","status":"publish","type":"page","link":"https:\/\/commetrex.com\/?page_id=760","title":{"rendered":"The Commetrex Outlook | November 2009"},"content":{"rendered":"<h2>Contents<\/h2>\n<ul>\n<li><a href=\"#article1\">Microsoft Features Commetrex\u2019 BladeWare Fax2Email for Exchange Server 2010 in Case Study<\/a><\/li>\n<li><a href=\"#article2\">Sangoma Analog Support Goes GA<\/a><\/li>\n<li><a href=\"#article3\">Commetrex featured in Microsoft Virtual Tradeshow<\/a><\/li>\n<li><a href=\"#article4\">Commetrex&#8217; New Website<\/a><\/li>\n<li><a href=\"#article5\">SIP Forum FoIP Task Group Report<\/a><\/li>\n<\/ul>\n<p><a name=\"article1\"><\/a><\/p>\n<h2>Microsoft Features Commetrex\u2019 BladeWare Fax2Email for Exchange Server 2010 in Case Study<\/h2>\n<p>In 2008, Commetrex was approached by Microsoft to discuss plans and specifications for Microsoft\u00ae Exchange Server 2010. \u201cThey wanted to provide deep integration of T.38-based &#8220;partner-fax solutions&#8221; with Exchange 2010 since inherent support for fax would not be included in Exchange 2010. We provided feedback on the proposed \u201cPartner Fax Specification\u201d, and were invited to participate in the Exchange &#8220;Testing and Adoption&#8221; program and test a product that would replace the Exchange T.38-fax feature.<\/p>\n<p>Many of Commetrex&#8217; enterprise-fax OEMs include a fax-to-email feature in their high-function enterprise servers, but we saw the need for an economical, easy-to-use fax-to-email product that was a direct replacement for the fax feature being removed from Exchange. It was evident that a large class of Exchange Server users did not need full-function fax servers.<\/p>\n<p>So, we designed a special version of our BladeWare Fax2Email Server, BladeWare Fax2Email for Exchange Server 2010, that would complement the high-function offerings of our OEM customers, and packaged and priced the product to make it appealing to small and mid-size businesses.<\/p>\n<p>The case study can be reviewed at Commetrex case study and the BladeWare Fax2Email for Exchange 2010 product bulletin is available here. For more information, contact Tom Ray at tray@commetrex.com or call him at 770-407-6025.<br \/>\n<a name=\"article2\"><\/a><\/p>\n<h2>Sangoma Analog Support Goes GA<\/h2>\n<p>BladeWare support for the Sangoma analog boards is now generally available.<\/p>\n<p>The combination of the Sangoma PSTN-interface boards and BladeWare yields the industry\u2019s highest-performance yet lowest-cost fax boards. And no offering gives you more choices: two-to-24 FXO and\/or FXS ports in any divisible-by-two combination that requires only one PCI or PCI Express slot. V.34 support will be added in BladeWare 1.5, slated for release by year-end.<\/p>\n<p>We will launch a beta of the digital service manager with PRI support before year-end.<\/p>\n<p>For more information, click here, or call 770-449-7775 and press \u201c1\u201d for sales.<br \/>\n<a name=\"article3\"><\/a><\/p>\n<h2>Commetrex featured in Microsoft Virtual Tradeshow<\/h2>\n<p>In support of the release of Windows 7, Windows Server 2008 R2, Exchange 2010, and other products, Microsoft has launched a major promotional campaign called \u201cThe New Efficiency\u201d. It shows how Microsoft products deliver cost savings, productivity, and innovations. As part of that program, Microsoft is featuring partners that offer products based on these new platforms, that meet the criteria of \u201cThe New Efficiency\u201d. Commetrex is pleased that BladeWare Fax2Email for Exchange 2010 server is a part of this product launch.<\/p>\n<p>BladeWare Fax2Email for Exchange 2010, which is a custom version of BladeWare Fax2Email Server, supports inbound T.38 fax, and is packaged and priced to make it appealing to small and midsize businesses.<\/p>\n<p>Commetrex is prominently featured in the Silver Sponsor section. To view our virtual booth, just click on this link.<\/p>\n<p>For more information, please contact Tom Ray at tray@commetrex.com.<br \/>\n<a name=\"article4\"><\/a><\/p>\n<h2>Commetrex&#8217; New Website<\/h2>\n<p>We\u2019ve given our venerable Website a thorough once over. Check it out. We\u2019ve updated much of the content, made it much easier to navigate, and improved the look. In addition, we\u2019ve reworked the customer section, identifying many of our customers by application and product. We\u2019ve long maintained that we are the leading developer and licensor of fax technologies, this section may convince you. Of course, BladeWare and our unrivaled offering of fax and fax-related licensed technologies are there.<\/p>\n<p>We\u2019ve also given proper attention to our new MSP product line, based on the Sangoma line of PCI and PCI Express boards.<\/p>\n<p>Please visit us at www.commetrex.com.<br \/>\n<a name=\"article5\"><\/a><\/p>\n<h2>SIP Forum FoIP Task Group Report<\/h2>\n<p>We are making progress, not as fast as we want (we all have day jobs), but we are making progress:<\/p>\n<p>We have submitted our problem statement to the IETF as an informational document as \u201cSIP Forum \u2013 Fax Over IP Task Group Problem Statement draft-jones-sip-forum-fax-problem-statement-00.txt.\u201d<\/p>\n<p>We have also submitted our work on Question 5 to the ITU as TR-30.1\/09-09-030 \u201cV.34 Facsimile to Standard G3 Facsimile Fallback Procedures with SIP\/SDP in ITU-T T.38.\u201d<\/p>\n<p>Here\u2019s Question 5:<\/p>\n<p style=\"padding-left: 30px;\">The rapid adoption of V.34 technology in fax machines, and slow deployment of V.34 fax-enabled gateways, makes the start up of a T.38-based fax session over an Internet Protocol (FoIP) network much more complex than before, when G3 facsimile dominated the market. This document collects, identifies, and investigates various issues associated with V.34\/V.8\/V.152 with T.38 in SIP networks. The purpose of this document is to provide guidance and best-practice recommendations on these issues, and, if needed, to propose changes in the relevant ITU-T Recommendations (T.38 in particular) for better and more reliable T.38-based Fax-over-IP communications.<\/p>\n<p>Question 6 is in progress:<\/p>\n<p style=\"padding-left: 30px;\"><strong>6. SDP Negotiations<\/strong><\/p>\n<p style=\"padding-left: 30px;\">In general, implementers are inconsistent in their handling of T.38 SDP negotiations. When should a Re-invite to T.38 be accepted? When can and should T.38 capability be declared? Should fax-only T.38 endpoints be able to invite directly to T.38?<\/p>\n<p>Question 1 is on hold pending getting some participation from the long-haul IP carriers, which may be largely responsible for the problems. Here\u2019s Question 1:<\/p>\n<p style=\"padding-left: 30px;\"><strong>1. Network Interconnection and Peering<\/strong><\/p>\n<p style=\"padding-left: 30px;\">Effective wide-area transport of IP fax requires that T.38 be supported in all IP networks traversed by a fax session, and that the inter-network signaling be correctly implemented. Yet the information needed by equipment vendors, integrators, and end users is difficult to obtain due to the difficulty of obtaining SIP trunking and peering information from service providers. It is a goal of the TG to assist interconnection and peering through its recommendations, but carriers and equipment vendors can immediately improve the situation by publishing on the Web all the information needed for T.38 inter-network interoperability.<\/p>\n<p>If you\u2019re interested, take a look at the FoIP problem statement on <a href=\"http:\/\/www.sipforum.org\/\">www.sipforum.org<\/a>. If you believe you can contribute to the resolution of any of these questions, join up!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Contents Microsoft Features Commetrex\u2019 BladeWare Fax2Email for Exchange Server 2010 in Case Study Sangoma Analog Support Goes GA Commetrex featured&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":553,"menu_order":12,"comment_status":"closed","ping_status":"open","template":"","meta":{"footnotes":""},"class_list":["post-760","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/commetrex.com\/index.php?rest_route=\/wp\/v2\/pages\/760","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/commetrex.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/commetrex.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/commetrex.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/commetrex.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=760"}],"version-history":[{"count":0,"href":"https:\/\/commetrex.com\/index.php?rest_route=\/wp\/v2\/pages\/760\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/commetrex.com\/index.php?rest_route=\/wp\/v2\/pages\/553"}],"wp:attachment":[{"href":"https:\/\/commetrex.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=760"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}