[\/vc_column_text][\/vc_column_inner][\/vc_row_inner][\/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” z_index=”” el_class=”ceo_commentary_sec_two”][vc_column][vc_column_text]These problems have been addressed one-by-one. But the remaining problems caused by least-cost routing-as-usual for FoIP calls are significant enough to slow the industry\u2019s move to an all-IP global network. FoIP-aware routing, which would be IP everywhere but to and from the TDM-connected fax terminals, is usually required for success.<\/p>\n
<\/p>\n
A SIP call switches from voice to FoIP (which usually means T.38) when the called fax endpoint answers. Of course, by that time the call has already been routed, since routing decisions begin when the on-ramp proxy or SIP server receives the first SIP Invite. At that point, the provider\u2019s routing algorithm should, if possible, route the call over qualified FoIP routes.<\/p>\n
<\/p>\n
Ten months ago the two task groups proposed that the SIP servers routing a fax call would set the user= parameter to user=fax in the header of the SIP Invite (see RFC 3261, section 25.1). But then just last month we found a better answer: RFC 3840, \u201cIndicating User-Agent Capabilities in SIP\u201d, which is specific to the task. According to RFC 3840, setting the header fields to indicate the capabilities of a terminal (user agent) can be used to \u201cexpress a preference for routing.\u201d<\/p>\n
<\/p>\n
The SIP and i3 Forum FoIP task groups are now moving ahead to standardize \u201cSIP.FAX=\u201d. It is interesting to note that RFC3840 defines 18 different feature tags in its section10, with none of them being fax, so we are setting out to make that 19 tag definitions.<\/p>\n
<\/p>\n
![\"Mike](\"http:\/\/commetrex.com\/wp-content\/uploads\/2011\/11\/MBCsig.jpg\" "\\"Mike's")