{"id":4492,"date":"2018-08-15T21:13:35","date_gmt":"2018-08-15T21:13:35","guid":{"rendered":"https:\/\/www.commetrex.com\/?page_id=4492"},"modified":"2020-01-14T12:12:12","modified_gmt":"2020-01-14T12:12:12","slug":"outlook-august-2018-2","status":"publish","type":"page","link":"https:\/\/commetrex.com\/?page_id=4492","title":{"rendered":"The Outlook | August 2018"},"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=”” css=”.vc_custom_1579003276222{padding-top: 70px !important;padding-bottom: 70px !important;background-color: #f6f6f6 !important;}”][vc_column][vc_column_text]<\/p>\n

Reaching IP Telephony\u2019s Full Potential<\/h3>\n

 <\/p>\n

Our industry and the public have enjoyed the many benefits of IP telephony: costs are down, quality is up, and innovation and business formation are greater than ever. But there is plenty of innovative potential in IP telephony that, when tapped, will deliver unprecedented user value. We\u2019re talking about moving beyond the tired paradigm of least-cost routing, and moving to smart routing,allowing users to control their call\u2019s destination with a precision unavailable with today\u2019s E.164 model. Smart routing, sometimes called service-based routing, will mean the value of any service that requires an all-IP route, such as HD voice and FoIP, to become readily accessible. And that unique value-adding service you developed can be discovered by your growing market.<\/p>\n

 <\/p>\n

Our perspective comes from Commetrex\u2019 extensive background in FoIP. The industry suffers from call routing better suited to the industry of the last century. The age of IP telephony, at least as far as an FoIP or HD voice is concerned, are services that need an all-IP call route for optimum performance. For example, a FoIP call with a PCM segment can only run at modem speeds, not Internet wire speeds. Moreover, PCM-IP handoffs can be error prone, making the transition from pass-through to T.38 problematic. Additionally, HD voice cannot even be transported by the PSTN.<\/p>\n

 <\/p>\n

Knowing this, the SIP Forum developed IETF RFC6913, which was intended to improve FoIP call routing. However, we would be surprised if there has ever been a call routed over an all-IP route due to an RFC6913-specifed contact header. RFC6913 specifies the SIP.fax=\u201dT38\u201d and SIP.fax=\u201dpassthrough\u201d media tags for use in an FoIP SIP INVITE.<\/p>\n

 <\/p>\n

RFC3840 specifies how to use media tags in the user-agent (UA) contact header to indicate the UA\u2019s capabilities and, implicitly, how the call should be routed. RFC3841 defines SIP header fields: “Accept-Contact”, “Reject Contact”, and “Request-Disposition”, enabling a caller to specify what calls will be accepted or rejected, as well as the handling instructions for proxies.<\/p>\n

 <\/p>\n

Let\u2019s not leave out ENUM, an elegant system for E.164-to-URI mapping, which, if fully implemented, would really take the industry to the proverbial next level. For more information, see “Techniques for Carriers\u2019 Advanced Routing and Addressing Schemes” from the i3 Forum.)<\/p>\n

 <\/p>\n

So, it\u2019s all there; we just need to use it. Contact Commetrex at 770-449-7775 to see how you can implement Smart FoIP\u00ae into your next-generation peripheral devices.[\/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_1579003431348{padding-top: 70px !important;padding-bottom: 70px !important;}” z_index=””][vc_column el_class=”newsletter_inner_page_bg”][vc_row_inner row_type=”row” type=”full_width” text_align=”left” css_animation=””][vc_column_inner width=”1\/2″][vc_column_text]<\/p>\n

Testing SIPfaxEngine<\/h3>\n

 <\/p>\n

Last year we announced SIPfaxEngine, which is now shipping. It\u2019s the core technology needed to build a SIP-based fax media server. (There is still all the surround stuff of a server for the OEM user to develop.) But how does an OEM go about testing a server that supports hundreds of FoIP ports?<\/p>\n

 <\/p>\n

Well, we\u2019ve got your back.[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_single_image image=”5460″ img_size=”full” alignment=”center” qode_css_animation=””][\/vc_column_inner][\/vc_row_inner][vc_column_text]Our SIPfaxEngine product includes an unlimited-port-count BladeWare license for testing. You also get a license to our FaxTap NG, which picks up where Wireshark leaves off in fax analysis and image rendering.<\/p>\n

 <\/p>\n

Features:<\/p>\n