[SIPForum-discussion] FAX T.38

Jastak, Eric Eric.Jastak at adp.com
Thu Jan 10 17:38:30 UTC 2013


Yes, you can configure the "sending" device (A-party) to send the re-invite.  Of course, the B-party device needs to be able to handle an incoming re-invite for T.38...some devices (gateways) don't handle that so well.  I've done this type of configuration in the past with Cisco 2102 ATAs, but it's not recommended.  One of the downsides is that you can run into glare issues if both A and B-parties send T.38 re-invites simultaneously.   This can result in failed negotiations and, ultimately, inconsistent results.   The exact behavior depends on the CPE and Fax gateways in the path; for example, if you fax a variety of different voice gateways (e.g., T.38 to different carriers) you will likely end up with an unreliable fax solution.

With that said, my advice is to stick with the T.38 recommendation that only the receiving party (B-party) send the T.38 re-invite.

From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of Moh, Yee-Kuang
Sent: Monday, January 07, 2013 9:35 PM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] FAX T.38

Hi,

Good day. Wondering using Fax T.38, isn't that B-party has always send Re-INVITE T.38 upon codec negotiation? Can A-party send Re-INVITE T.38 if B-party doesn't?

Thanks in advance.

Regards
moh


This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130110/5ae283db/attachment-0002.html>


More information about the discussion mailing list