[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_1579010269234{padding-top: 70px !important;padding-bottom: 70px !important;background-color: #f6f6f6 !important;}” z_index=””][vc_column][vc_column_text]<\/p>\n
<\/p>\n
FaxLogic<\/a>\u00a0offers its enterprise customers a unique cloud-based way to outsource the enterprise fax server using BladeWare andBladeWare Fax Media Server<\/a>. Indeed, FaxLogic has developed what is, in all likelihood, the industry’s most-sophisticated FoIP routing algorithm to deliver trouble-free FoIP.<\/p>\n <\/p>\n Back in the last half of the last decade they used multi-protocol label switching to avoid carrier routing and the low success rates it provided.\u00a0According to Wikipedia:<\/p>\n <\/p>\n “Multi-protocol label switching is a scalable, protocol-independent (packet-based) transport. In an MPLS network, data packets are assigned labels. Packet-forwarding decisions are made solely on the contents of this label, without the need to examine the packet itself. This allows one to create end-to-end circuits across any type of transport medium, using any protocol.”<\/span> <\/p>\n But fast forward to today’s Internet and the improvements made by carriers in packet loss and other impairments. FaxLogic found that with their call volumes and the number of carrier partners they use (Would you believe 18?), they can predict, with a high degree of certainty, which of those carriers can deliver a given fax error free, making a highly informed choice as to which carrier should be assigned the task.\u00a0<\/span><\/p>\n <\/p>\n For inbound, they know which carriers do a good job with T.38 and which ones don’t and use that knowledge to negotiate their service agreements. They route the calls from the T.38-capable carriers to BladeWare servers configured to issue a T.38 reINVITE and the other carrier’s calls to G.711-only BladeWare servers. And remember, BladeWare’s proprietary design gets rid of PCM clock-sync problems, so they get solid G.711 performance.<\/span><\/p>\n <\/p>\n FaxLogic’s service gives customers a cloud-based enterprise fax server. Their Advanced Web Client is a web-browser application that lets you send, receive, sort, store, manage and share all your faxes, much as you would an on-premises fax server. FaxLogic also provides ATAs so their customers can continue to use their legacy fax machines.<\/p>\n <\/p>\n FaxLogic combines the convenience, features and benefits of analog fax, Internet fax, and fax servers, while eliminating the drawbacks and incompatibilities. A complete fax communications and document-management system, FaxLogic securely sends, receives, stores and manages business documents starting at prices lower than the phone lines that the service replaces.<\/p>\n <\/p>\n And it’s all done with BladeWare and FaxLogic’s amazing routing software. \u00a0To learn more, please click to read the latest white paper on\u00a0“How to Make FoIP Work”<\/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 <\/p>\n In many presentations and white papers, Commetrex has identified carrier routing as the source of many of the FoIP failures your customers experience. Indeed, the number-one problem solved by Commetrex\u2019 patented Smart FoIP\u00ae is\u00a0late-T.38 reINVITEs, which only happens with carrier-routed calls. If you avoid carrier routing, Smart FoIP\u2019s primary benefit goes from solving the\u00a0late-T.38 reINVITE problem<\/a>\u00a0to making\u00a0G.711 pass-through<\/a>\u00a0calls work, which is still a big deal, but not quite as big.<\/p>\n <\/p>\n So, what\u2019s the problem with carrier routing? Well, from our experience, it\u2019s primarily due to the carriers believing that an FoIP call is to be routed just like a voice call\u2013after all, it begins life as a G.711 INVITE, doesn\u2019t it? Well, yes, but we don\u2019t expect an HD voice call that is mindlessly routed to succeed as an end-to-end HD call, do we? Best effort just doesn\u2019t hack it.<\/p>\n <\/p>\n Of course, Smart FoIP is a big step in the right direction, but Commetrex\u2019 marketing reach is not such that we can change the industry with this innovation. Instead, the carriers must realize that fax calls must be routed as fax calls\u2026no IP-TDM\/PSTN-IP\u2026only IP routes that have been tested for FoIP \u201cfriendliness.\u201d And one way to make that happen is for service providers to pitch in and insist on the adoption of RFC6913.<\/p>\n <\/p>\n Let\u2019s talk about it.\u00a0Call 770-449-7775\u00a0and press 1. Yeah, it\u2019s \u201cOne for sales\u201d, but you\u2019ll reach us.[\/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_1579010143762{padding-top: 70px !important;padding-bottom: 70px !important;background-color: #f6f6f6 !important;}” z_index=””][vc_column el_class=”newsletter_inner_page_bg”][vc_column_text]<\/p>\n <\/p>\n Yes, we\u2019ve been harping on it. RFC6913 is a big part of the answer to the carrier-routing problem. Check it out. A simple addition to the SIP-invite header that indicates this is a fax call is the beginning of the end of bad carrier routing. We\u2019ve done our part; we hope you\u2019ll do yours. We\u2019ve added support for this new recommendation to Commetrex BladeWare (and NetGen\u2019s Smart ATA\u00ae).<\/p>\n <\/p>\n According to Cliff Schornak, NetGen\u2019s CTO, \u201cLess-than-optimum routing of FoIP calls by carriers is the primary reason for poor FoIP success rates in international FoIP calls. And it\u2019s not because they don\u2019t want to, it\u2019s because the SIP standards haven\u2019t supported it prior to RFC 6913.\u201d<\/p>\n <\/p>\n
\nOf course, major carriers offer MPLS over IP networks, and since the route is established by the carrier for the user, inter-carrier FoIP routing can be avoided by placing both FoIP endpoints in the MPLS network. But this solution required that the calls remain on the MPLS network to be fully effective, which wasn’t scalable.<\/p>\nWhat Is It About Carrier Routing?<\/h3>\n
RFC6913?<\/h3>\n