[cisco-voip] T.38 SIP/H323 and fax-relay ecm disable?

[Nick Matthews]

T38 is a version of fax-relay, so I would expect so.  The two options for
fax relay would be Cisco Fax Relay and T38.  With MGCP you would use a
different command, so you're correct it's just T.38 with H.323/SIP

You can usually test this by disabling ECM on the fax machine as well if
you think it's not taking hold.  Otherwise get a packet capture and see
what's in the T.38 packets.

-nick

On Wed, Apr 18, 2012 at 10:18 AM, Jason Aarons (AM) <
jason.aarons at dimensiondata.com> wrote:

> Does the command “fax-relay ecm disable” on dial peer do anything when you
> only have T.38 configured globally without fallback? I thought fax-relay
> would only kick in with fallback not actual T.38 but I guess it could
> disable ecm with T.38/H323/SIP.****
>
> ** **
>
> fax-relay ecm disable****
>
>
> http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_fax_services_over_ip_application_guide/t38.html#wp1156099
> ****
>
> ** **
>
> Voice service voip****
>
>    fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
> ****
>
> ** **
>
> Where ecm disable made the faxes illegible****
>
> http://www.gossamer-threads.com/lists/cisco/voip/130593****
>
> ** **
>
> show call active fax brief****
>
> ** **
>
> Having some faxes fail, I suspect the root cause is something else (packet
> loss) and ecm disable might help, but is not the real problem. Planning to
> enabled t.38 redundancy.****
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120418/7598d705/attachment.html>