# Fax and T.38 in cloud calling

Canonical: https://warmtransfer.net/knowledge/fax-t38

Last verified: 2026-09-24

ITU-T Recommendation T.38 is titled Procedures for real-time Group 3 facsimile communication over IP networks[^13]. As of 2026-09-24, the in-force edition of ITU-T T.38 is T.38 (11/15), and earlier editions from 06/98 onward are superseded[^12].

## Standards and protocol mechanisms

RFC 3362 registers the image/t38 media subtype for T.38 real-time fax used in SDP-based call setup and says the registration is not intended for email[^18]. RFC 3362 notes that T.38 allows the use of either TCP or UDP depending on the service environment[^19]. RFC 7345 defines transport of UDPTL (the predominant T.38 transport) over DTLS negotiated in SDP with the proto value UDP/TLS/UDPTL[^23]. RFC 7345 states that earlier secure fax mechanisms such as T.30 Annex H and T.38 over RTP/SAVP achieved little market adoption[^22].

RFC 6913 motivates the sip.fax tag by noting that fax calls are treated as voice calls until after they are connected which can route them to non-fax endpoints[^21]. RFC 6913 defines the sip.fax media feature tag with values t38 and passthrough so SIP user agents can advertise fax capability in REGISTER and callers can request it with Accept-Contact in INVITE[^20].

## Webex Calling fax architectures

Cisco's Webex Calling help article on ATA fax transmission says that enabling T.38 mode can improve fax quality through an ATA[^40]. In Webex Calling ATA fax guidance, T.38 mode is disabled by default[^39]. Cisco states that when T.38 is enabled on a Webex Calling ATA, faxes are not encrypted[^38]. In the Webex Calling Local Gateway configuration for the registration-based trunk, T.38 fax transport is enabled by default[^14]. Fax (T.38) is listed among the features not supported in Webex for Government Calling[^29]. Local Gateway for Webex for Government does not support Fax (T.38)[^28].

A documented Webex Calling fax failure is that the T.38 switchover ReINVITE from a registered fax device is answered with SIP 488 Not Acceptable Here so T.38 is never negotiated[^33]. The 488 tech note presupposes that T.38 mode is already configured in Control Hub on the fax device[^30]. Cisco's fix for the Webex Calling T.38 ReINVITE 488 error is to set the fax user's or workspace's Call Experience compression to Normal compression in Control Hub on the Calling tab[^32]. After changing compression to Normal for the 488 T.38 issue, Cisco says the fax device must be restarted for the change to apply[^31].

Webex Calling Fax Messaging extends the user messaging service so users can receive store review and manage fax messages with notifications similar to voicemail[^42]. Fax Messaging for a Webex Calling user is enabled in Control Hub under the user's Calling voicemail settings with the Receive Fax Messages toggle and a fax phone number and requires the user's voicemail to be enabled[^43]. Webex Calling Fax Messaging delivers received faxes in TIFF image format retrievable by email or from the User Portal voicemail section[^44]. A Webex Calling voicemail group can be set to receive fax messages[^47]. A Webex Calling voicemail group needs a separate full phone number for fax service while a number is optional for voicemail only[^46]. Before unassigning the phone number of a Webex Calling voicemail group with fax enabled the administrator must disable fax messaging[^45].

## Cisco gateway and ATA engineering

For fax on Cisco ATA 191 and 192 multiplatform firmware Cisco recommends G.711u (USA) or G.711a (elsewhere) as the preferred codec with silence suppression and echo cancellation disabled[^6]. Cisco's ATA 191/192 guide advises allocating at least 50 kbps for T.38 fax and approximately 100 kbps for G.711 fallback[^3]. On Cisco ATA 191/192 multiplatform firmware if a T.38 call cannot be set up the call automatically reverts to G.711 fallback[^5]. Cisco's ATA 191/192 guide says that when a Cisco media gateway terminates to the PSTN, T.38 fax relay should be disabled and fax enabled via modem passthrough (fax protocol pass-through g711ulaw with fax rate disable) with a T.38 alternative given[^4].

Cisco states that NSE-based fax switchover is Cisco-proprietary so CUBE fax interworking with third-party equipment must use standards-based T.38 relay or protocol-based G.711 pass-through[^9]. In CUBE fax call flows the terminating gateway detects the V.21 preamble and triggers switchover to T.38 with a SIP ReINVITE (or H.323 RequestMode) which CUBE must permit[^11]. Cisco's CUBE fax note says T.38 version 0 carries G3 fax speeds while T.38 version 3 supports Super G3 from Cisco IOS 15.1(1)T[^10]. For third-party interoperability Cisco recommends configuring CUBE with fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none with dial-peer configuration taking precedence over global settings[^8]. Cisco says the fax transport method must be consistent end to end across the originating gateway CUBE and terminating gateway path[^7].

## Multi-vendor cloud calling platform behaviors

To connect analog devices to Microsoft Teams Direct Routing an ATA is required and the ATA must be supported by the certified SBC vendor[^24]. Microsoft's Direct Routing analog devices guidance counts fax machines among analog devices alongside analog phones and overhead pagers[^25].

Zoom documents fax setup for the Poly OBi30X OBi508 and ATA40X analog telephone adapters on Zoom Phone[^51]. Zoom's Poly OBi fax setup for Zoom Phone sets T38Enable to Disabled and FaxPassThroughCodec to G711U (North America) or G711A so fax uses G.711 passthrough rather than T.38[^52]. Zoom's AudioCodes MP1XX fax setup sets Fax Transport Mode and the V.21 to V.34 modem transport types to Events Only with a G.711 fax/modem bypass coder and supports only FXS ports[^48].

RingCentral states that T.38 is not guaranteed for every end-to-end connection and recommends testing speed quality and reliability before relying on ATA faxing[^16]. RingCentral requires a fax ATA to be connected to a DigitalLine product offering[^15].

## Physical fax machine tuning and PSTN fallback

Cisco notes that keeping a dedicated PSTN line remains an option for best fax and modem performance instead of faxing through a Webex Calling ATA[^37]. Zoom says fax over VoIP has technology-based industry-wide limitations and recommends that businesses dependent on regular multi-page faxing keep an analog line and a traditional fax machine[^49].

Cisco advises setting the fax machine behind a Webex Calling ATA to Fax mode or Auto Answer Fax mode so incoming calls are not treated as voice calls[^36]. If Webex Calling ATA fax problems persist, Cisco advises lowering the fax machine baud rate to 9600 or 2400 bps[^34]. Cisco's Webex Calling ATA fax troubleshooting steps include adjusting Error Correction Mode settings and reducing the number of pages per transmission[^35].

Zoom's OBi fax guidance tells users to lower fax speed (to no less than 9600 bps) and disable Error Correction Mode and compression on the fax machine[^50]. 8x8 advises lowering fax speed to 9600 bps disabling ECM and using Standard resolution on fax machines connected through an ATA[^1]. 8x8 Support will help with general fax machine settings but cannot troubleshoot the fax machine itself or a fax server once the ATA is confirmed working[^2].

## See also

See also [Analog gateways ATA and paging devices](https://warmtransfer.net/knowledge/analog-gateways-ata).
See also [PRI and TDM gateway interworking](https://warmtransfer.net/knowledge/legacy-pri-tdm).
See also [DECT and wireless voice devices](https://warmtransfer.net/knowledge/dect-wireless-voice).
See also [SS7 and carrier interworking concepts](https://warmtransfer.net/knowledge/ss7-carrier-interworking).

## Applicability

Applies to: ITU-T T.38, IETF RFC 3362, IETF RFC 7345, IETF RFC 6913, Cisco Webex Calling, Webex Calling Local Gateway (Cisco IOS XE), Cisco Webex for Government Calling, Cisco Webex for Government Calling Local Gateway, Cisco ATA 191, Cisco Unified Border Element, Microsoft Teams Phone Direct Routing, Zoom Phone, RingCentral RingEX, and 8x8 Work. Deployments: cloud, on-premises, multi-tenant, premises-gateway, and standard. Sources checked 2026-09-24. Cisco IOS 15.1(1)T and later introduces support for T.38 version 3 on CUBE[^10]. Fax (T.38) and Local Gateway Fax (T.38) are explicitly unsupported in Webex for Government within the United States region[^29][^28]. RingCentral DigitalLine requirements and T.38 operational statements apply to the United States region[^15][^16].

## What remains uncertain

Whether Microsoft Teams Direct Routing supports native T.38 transmission directly on certified Session Border Controllers is not covered by the sources below.

## Sources

[^1]: 8x8 advises lowering fax speed to 9600 bps disabling ECM and using Standard resolution on fax machines connected through an ATA. Source: [Troubleshooting Issues with Fax Devices](https://help.8x8.com/docs/troubleshooting-issues-with-fax-devices), Fax machine settings list. Checked 2026-09-24.
[^2]: 8x8 Support will help with general fax machine settings but cannot troubleshoot the fax machine itself or a fax server once the ATA is confirmed working. Source: [Troubleshooting Issues with Fax Devices](https://help.8x8.com/docs/troubleshooting-issues-with-fax-devices), Support scope paragraph. Checked 2026-09-24.
[^3]: Cisco's ATA 191/192 guide advises allocating at least 50 kbps for T.38 fax and approximately 100 kbps for G.711 fallback. Source: [Cisco ATA 191 and ATA 192 Analog Telephone Adapter Administration Guide for Multiplatform Firmware - Advanced Options for Phone Services](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cata/19x/3PCC/english/admin-guide/at9x_b_ata191-192-admin-mp/at9x_b_ata191-192-admin-mp_chapter_01000.html), Optimize Fax Completion Rates section. Checked 2026-09-24.
[^4]: Cisco's ATA 191/192 guide says that when a Cisco media gateway terminates to the PSTN, T.38 fax relay should be disabled and fax enabled via modem passthrough (fax protocol pass-through g711ulaw with fax rate disable) with a T.38 alternative given. Source: [Cisco ATA 191 and ATA 192 Analog Telephone Adapter Administration Guide for Multiplatform Firmware - Advanced Options for Phone Services](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cata/19x/3PCC/english/admin-guide/at9x_b_ata191-192-admin-mp/at9x_b_ata191-192-admin-mp_chapter_01000.html), Optimize Fax Completion Rates section; Cisco media gateway guidance. Checked 2026-09-24.
[^5]: On Cisco ATA 191/192 multiplatform firmware if a T.38 call cannot be set up the call automatically reverts to G.711 fallback. Source: [Cisco ATA 191 and ATA 192 Analog Telephone Adapter Administration Guide for Multiplatform Firmware - Advanced Options for Phone Services](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cata/19x/3PCC/english/admin-guide/at9x_b_ata191-192-admin-mp/at9x_b_ata191-192-admin-mp_chapter_01000.html), Optimize Fax Completion Rates section. Checked 2026-09-24.
[^6]: For fax on Cisco ATA 191 and 192 multiplatform firmware Cisco recommends G.711u (USA) or G.711a (elsewhere) as the preferred codec with silence suppression and echo cancellation disabled. Source: [Cisco ATA 191 and ATA 192 Analog Telephone Adapter Administration Guide for Multiplatform Firmware - Advanced Options for Phone Services](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cata/19x/3PCC/english/admin-guide/at9x_b_ata191-192-admin-mp/at9x_b_ata191-192-admin-mp_chapter_01000.html), Optimize Fax Completion Rates section. Checked 2026-09-24.
[^7]: Cisco says the fax transport method must be consistent end to end across the originating gateway CUBE and terminating gateway path. Source: [CUBE Third-Party Interoperability Fax Guidelines](https://www.cisco.com/c/en/us/support/docs/voice/t38/116280-configure-cube-00.html), Background Information and CUBE Configuration sections. Checked 2026-09-24.
[^8]: For third-party interoperability Cisco recommends configuring CUBE with fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none with dial-peer configuration taking precedence over global settings. Source: [CUBE Third-Party Interoperability Fax Guidelines](https://www.cisco.com/c/en/us/support/docs/voice/t38/116280-configure-cube-00.html), CUBE Configuration section. Checked 2026-09-24.
[^9]: Cisco states that NSE-based fax switchover is Cisco-proprietary so CUBE fax interworking with third-party equipment must use standards-based T.38 relay or protocol-based G.711 pass-through. Source: [CUBE Third-Party Interoperability Fax Guidelines](https://www.cisco.com/c/en/us/support/docs/voice/t38/116280-configure-cube-00.html), FoIP Transport Methods section. Checked 2026-09-24.
[^10]: Cisco's CUBE fax note says T.38 version 0 carries G3 fax speeds while T.38 version 3 supports Super G3 from Cisco IOS 15.1(1)T. Source: [CUBE Third-Party Interoperability Fax Guidelines](https://www.cisco.com/c/en/us/support/docs/voice/t38/116280-configure-cube-00.html), FoIP Transport Methods section; T.38 versions. Checked 2026-09-24.
[^11]: In CUBE fax call flows the terminating gateway detects the V.21 preamble and triggers switchover to T.38 with a SIP ReINVITE (or H.323 RequestMode) which CUBE must permit. Source: [CUBE Third-Party Interoperability Fax Guidelines](https://www.cisco.com/c/en/us/support/docs/voice/t38/116280-configure-cube-00.html), CUBE Fax Call Flows section. Checked 2026-09-24.
[^12]: As of 2026-09-24 the in-force edition of ITU-T T.38 is T.38 (11/15) and earlier editions from 06/98 onward are superseded. Source: [T.38 : Procedures for real-time Group 3 facsimile communication over IP networks](https://www.itu.int/rec/T-REC-T.38), Recommendation version table; In force and Superseded rows. Checked 2026-09-24.
[^13]: ITU-T Recommendation T.38 is titled Procedures for real-time Group 3 facsimile communication over IP networks. Source: [T.38 : Procedures for real-time Group 3 facsimile communication over IP networks](https://www.itu.int/rec/T-REC-T.38), Recommendation landing page title. Checked 2026-09-24.
[^14]: In the Webex Calling Local Gateway configuration for the registration-based trunk, T.38 fax transport is enabled by default. Source: [Configure Local Gateway on Cisco IOS XE for Webex Calling](https://help.webex.com/en-us/article/jr1i3r/Configure-Local-Gateway-on-Cisco-IOS-XE-for-Webex-Calling), Configure Webex Calling registration-based trunk section. Checked 2026-09-24.
[^15]: RingCentral requires a fax ATA to be connected to a DigitalLine product offering. Source: [Fax Set Up Analog Telephone Adapter ATA](https://support.ringcentral.com/article-v2/Fax-Set-Up-Analog-Telephone-Adapter-ATA.html?brand=RC_US&product=RingEX&language=en_US), Page body; requirements. Checked 2026-09-24.
[^16]: RingCentral states that T.38 is not guaranteed for every end-to-end connection and recommends testing speed quality and reliability before relying on ATA faxing. Source: [Fax Set Up Analog Telephone Adapter ATA](https://support.ringcentral.com/article-v2/Fax-Set-Up-Analog-Telephone-Adapter-ATA.html?brand=RC_US&product=RingEX&language=en_US), Page body; T.38 paragraph. Checked 2026-09-24.
[^17]: RingCentral's ATA fax article states that the service uses the T.38 standard for fax and adheres to FCC guidelines regarding its use. Source: [Fax Set Up Analog Telephone Adapter ATA](https://support.ringcentral.com/article-v2/Fax-Set-Up-Analog-Telephone-Adapter-ATA.html?brand=RC_US&product=RingEX&language=en_US), Page body; T.38 paragraph. Checked 2026-09-24.
[^18]: RFC 3362 registers the image/t38 media subtype for T.38 real-time fax used in SDP-based call setup and says the registration is not intended for email. Source: [Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration](https://www.rfc-editor.org/rfc/rfc3362.html), Section 2 and Section 4. Checked 2026-09-24.
[^19]: RFC 3362 notes that T.38 allows the use of either TCP or UDP depending on the service environment. Source: [Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration](https://www.rfc-editor.org/rfc/rfc3362.html), Section 3. Checked 2026-09-24.
[^20]: RFC 6913 defines the sip.fax media feature tag with values t38 and passthrough so SIP user agents can advertise fax capability in REGISTER and callers can request it with Accept-Contact in INVITE. Source: [Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)](https://www.rfc-editor.org/rfc/rfc6913.html), Section 4 Usage; Section 7 IANA Considerations. Checked 2026-09-24.
[^21]: RFC 6913 motivates the sip.fax tag by noting that fax calls are treated as voice calls until after they are connected which can route them to non-fax endpoints. Source: [Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)](https://www.rfc-editor.org/rfc/rfc6913.html), Section 3 Motivation. Checked 2026-09-24.
[^22]: RFC 7345 states that earlier secure fax mechanisms such as T.30 Annex H and T.38 over RTP/SAVP achieved little market adoption. Source: [UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)](https://www.rfc-editor.org/rfc/rfc7345.html), Section 1 Introduction. Checked 2026-09-24.
[^23]: RFC 7345 defines transport of UDPTL (the predominant T.38 transport) over DTLS negotiated in SDP with the proto value UDP/TLS/UDPTL. Source: [UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)](https://www.rfc-editor.org/rfc/rfc7345.html), Section 1 Introduction; Section 4 SDP Offerer/Answerer Procedures. Checked 2026-09-24.
[^24]: To connect analog devices to Microsoft Teams Direct Routing an ATA is required and the ATA must be supported by the certified SBC vendor. Source: [Direct Routing - Connecting analog devices](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-analog-devices), Introduction paragraph. Checked 2026-09-24.
[^25]: Microsoft's Direct Routing analog devices guidance counts fax machines among analog devices alongside analog phones and overhead pagers. Source: [Direct Routing - Connecting analog devices](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-analog-devices), Considerations section; first bullet. Checked 2026-09-24.
[^26]: Because Microsoft's Direct Routing analog guidance says nothing about T.38 and defers ATA and SBC configuration to the SBC vendors, fax media handling in Direct Routing appears to be the responsibility of the ATA and SBC rather than a documented Teams capability (inferred). Source: [Direct Routing - Connecting analog devices](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-analog-devices), Example section; SBC manufacturer documentation links. Checked 2026-09-24.
[^27]: Cloud calling vendors diverge on ATA fax transport: Webex Calling guidance points toward enabling T.38 and RingCentral says it uses T.38 while Zoom's documented OBi setup disables T.38 in favour of G.711 passthrough (inferred). Source: [Setting up faxing (Poly OBi series ATA)](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0068395), Codec settings step; compared with cisco-help-fzwl6ab-improve-fax-ata T.38 guidance and ringcentral-fax-set-up-ata T.38 paragraph. Checked 2026-09-24.
[^28]: Local Gateway for Webex for Government does not support Fax (T.38). Source: [Configure Local Gateway on Cisco IOS XE for Webex Calling](https://help.webex.com/en-us/article/jr1i3r/Configure-Local-Gateway-on-Cisco-IOS-XE-for-Webex-Calling), Local Gateway for Webex for Government section. Checked 2026-09-24.
[^29]: Fax (T.38) is listed among the features not supported in Webex for Government Calling. Source: [Webex for Government Calling](https://help.webex.com/article/n592cco), Features not supported in Webex for Government. Checked 2026-09-24.
[^30]: The 488 tech note presupposes that T.38 mode is already configured in Control Hub on the fax device. Source: [Fix 488 SIP Error for Fax T.38 ReINVITE Rejected by Webex Calling](https://www.cisco.com/c/en/us/support/docs/unified-communications/webex-calling/222133-fix-488-sip-error-for-fax-t-38-reinvite.html), Prerequisites or problem context. Checked 2026-09-24.
[^31]: After changing compression to Normal for the 488 T.38 issue, Cisco says the fax device must be restarted for the change to apply. Source: [Fix 488 SIP Error for Fax T.38 ReINVITE Rejected by Webex Calling](https://www.cisco.com/c/en/us/support/docs/unified-communications/webex-calling/222133-fix-488-sip-error-for-fax-t-38-reinvite.html), Solution section; final step. Checked 2026-09-24.
[^32]: Cisco's fix for the Webex Calling T.38 ReINVITE 488 error is to set the fax user's or workspace's Call Experience compression to Normal compression in Control Hub on the Calling tab. Source: [Fix 488 SIP Error for Fax T.38 ReINVITE Rejected by Webex Calling](https://www.cisco.com/c/en/us/support/docs/unified-communications/webex-calling/222133-fix-488-sip-error-for-fax-t-38-reinvite.html), Solution section; steps 1 to 5. Checked 2026-09-24.
[^33]: A documented Webex Calling fax failure is that the T.38 switchover ReINVITE from a registered fax device is answered with SIP 488 Not Acceptable Here so T.38 is never negotiated. Source: [Fix 488 SIP Error for Fax T.38 ReINVITE Rejected by Webex Calling](https://www.cisco.com/c/en/us/support/docs/unified-communications/webex-calling/222133-fix-488-sip-error-for-fax-t-38-reinvite.html), Problem section. Checked 2026-09-24.
[^34]: If Webex Calling ATA fax problems persist, Cisco advises lowering the fax machine baud rate to 9600 or 2400 bps. Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), Improve fax transmission with your ATA; troubleshooting steps. Checked 2026-09-24.
[^35]: Cisco's Webex Calling ATA fax troubleshooting steps include adjusting Error Correction Mode settings and reducing the number of pages per transmission. Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), Improve fax transmission with your ATA; troubleshooting steps. Checked 2026-09-24.
[^36]: Cisco advises setting the fax machine behind a Webex Calling ATA to Fax mode or Auto Answer Fax mode so incoming calls are not treated as voice calls. Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), Improve fax transmission with your ATA; fax machine configuration. Checked 2026-09-24.
[^37]: Cisco notes that keeping a dedicated PSTN line remains an option for best fax and modem performance instead of faxing through a Webex Calling ATA. Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), Improve fax transmission with your ATA; introduction. Checked 2026-09-24.
[^38]: Cisco states that when T.38 is enabled on a Webex Calling ATA, faxes are not encrypted. Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), Improve fax transmission with your ATA; T.38 mode guidance. Checked 2026-09-24.
[^39]: In Webex Calling ATA fax guidance, T.38 mode is disabled by default. Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), Improve fax transmission with your ATA; T.38 mode guidance. Checked 2026-09-24.
[^40]: Cisco's Webex Calling help article on ATA fax transmission says that enabling T.38 mode can improve fax quality through an ATA. Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), Improve fax transmission with your ATA; T.38 mode guidance. Checked 2026-09-24.
[^41]: For Webex Calling ATA fax the documented choice is a trade-off between the encrypted default path and T.38 which improves reliability but is unencrypted; no Webex source found documents RFC 7345 secure T.38 (inferred). Source: [Improve fax transmission with your ATA](https://help.webex.com/en-us/article/fzwl6ab/Improve-fax-transmission-with-your-ATA), T.38 mode guidance; compared with rfc-7345-udptl-over-dtls Section 1. Checked 2026-09-24.
[^42]: Webex Calling Fax Messaging extends the user messaging service so users can receive store review and manage fax messages with notifications similar to voicemail. Source: [Configure Fax Message Feature for Webex Calling Users](https://www.cisco.com/c/en/us/support/docs/unified-communications/webex-calling-app/221591-htz-01-2024-configure-fax-message-featu.html), Background Information section. Checked 2026-09-24.
[^43]: Fax Messaging for a Webex Calling user is enabled in Control Hub under the user's Calling voicemail settings with the Receive Fax Messages toggle and a fax phone number and requires the user's voicemail to be enabled. Source: [Configure Fax Message Feature for Webex Calling Users](https://www.cisco.com/c/en/us/support/docs/unified-communications/webex-calling-app/221591-htz-01-2024-configure-fax-message-featu.html), Prerequisites and Configure sections. Checked 2026-09-24.
[^44]: Webex Calling Fax Messaging delivers received faxes in TIFF image format retrievable by email or from the User Portal voicemail section. Source: [Configure Fax Message Feature for Webex Calling Users](https://www.cisco.com/c/en/us/support/docs/unified-communications/webex-calling-app/221591-htz-01-2024-configure-fax-message-featu.html), Verify section; retrieval methods. Checked 2026-09-24.
[^45]: Before unassigning the phone number of a Webex Calling voicemail group with fax enabled the administrator must disable fax messaging. Source: [Manage a shared voicemail and inbound fax box for Webex Calling](https://help.webex.com/en-us/article/mcjd4u/Manage-a-Shared-Voicemail-and-Inbound-Fax-Box-for-Webex-Calling), Delete or edit a voicemail group section. Checked 2026-09-24.
[^46]: A Webex Calling voicemail group needs a separate full phone number for fax service while a number is optional for voicemail only. Source: [Manage a shared voicemail and inbound fax box for Webex Calling](https://help.webex.com/en-us/article/mcjd4u/Manage-a-Shared-Voicemail-and-Inbound-Fax-Box-for-Webex-Calling), Create or edit a voicemail group; phone number field. Checked 2026-09-24.
[^47]: A Webex Calling voicemail group can be set to receive fax messages. Source: [Manage a shared voicemail and inbound fax box for Webex Calling](https://help.webex.com/en-us/article/mcjd4u/Manage-a-Shared-Voicemail-and-Inbound-Fax-Box-for-Webex-Calling), Create or edit a voicemail group; fax message option. Checked 2026-09-24.
[^48]: Zoom's AudioCodes MP1XX fax setup sets Fax Transport Mode and the V.21 to V.34 modem transport types to Events Only with a G.711 fax/modem bypass coder and supports only FXS ports. Source: [Setting up faxing (AudioCodes MP1XX series)](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0068042), Prerequisites; Configuration > VoIP > Media > Fax/Modem/CID Settings step. Checked 2026-09-24.
[^49]: Zoom says fax over VoIP has technology-based industry-wide limitations and recommends that businesses dependent on regular multi-page faxing keep an analog line and a traditional fax machine. Source: [Setting up faxing (AudioCodes MP1XX series)](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0068042), Introductory note. Checked 2026-09-24.
[^50]: Zoom's OBi fax guidance tells users to lower fax speed (to no less than 9600 bps) and disable Error Correction Mode and compression on the fax machine. Source: [Setting up faxing (Poly OBi series ATA)](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0068395), Fax machine settings step. Checked 2026-09-24.
[^51]: Zoom documents fax setup for the Poly OBi30X OBi508 and ATA40X analog telephone adapters on Zoom Phone. Source: [Setting up faxing (Poly OBi series ATA)](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0068395), Prerequisites and title. Checked 2026-09-24.
[^52]: Zoom's Poly OBi fax setup for Zoom Phone sets T38Enable to Disabled and FaxPassThroughCodec to G711U (North America) or G711A so fax uses G.711 passthrough rather than T.38. Source: [Setting up faxing (Poly OBi series ATA)](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0068395), Codec settings step. Checked 2026-09-24.