blocks|key|4277189|text|RingCentral支持将传真存储为PDF和TIFF文件。配置首选项适用于每个分机。在检索时，Content-Type+HTTP响应头将设置为application/pdf或image/tiff|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4277190|您可以检查响应头是否具有"Content-Type“：'image/tiff'，以便在通过消息存储端点检索传真时将附件保存为.tiff文件格式：|4277191|GET+/account/~/extension/~/message-store|4277192|有关更多信息，请参阅我们的RingCentral-Fax-FAQ|4277193|有关任何与支持相关的问题，请联系我们的开发人员支持人员，网址为：|4277194|Portal：https://developer.ringcentral.com/support.html|4277195|Email：devsupport@ringcentral+(包含必要的细节)|4277196|entityMap|0|LINK|mutability|MUTABLE|url|http://ringcentral-faq.readthedocs.io/en/latest/fax/|1|https://developer.ringcentral.com/support.html|2|http://devsupport@ringcentral.com/^0|0|B|J|3|N|4|1C|C|20|F|2G|A|0|D|C|S|A|0|0|3|4|10|0|D|J|0|0|0|0|6|7|1A|1|0|0|5|6|M|2|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1Q|8|@]|D|@$9|1R|A|1S|1|1T]]|E|$]]|$1|L|3|M|5|6|7|1U|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1V|8|@$9|1W|A|1X|B|C]]|D|@$9|1Y|A|1Z|1|20]]|E|$]]|$1|P|3|Q|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@$9|24|A|25|1|26]]|E|$]]|$1|R|3|-4|5|6|7|27|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]|Z|$5|U|V|W|E|$X|10]]|11|$5|U|V|W|E|$X|12]]]]

<code>RingCentral</code> supports storing faxes as <code>PDF</code> and <code>TIFF</code> files. The configuration preference is available per extension. Upon retrieval, the <code>Content-Type</code> HTTP response header will be set to <code>application/pdf</code> or <code>image/tiff</code>

You could check to see if the response header has "<code>Content-Type</code>" : '<code>image/tiff</code>', so as to save the attachment as .tiff file format when you retrieve the faxes via the message-store endpoint :

<code>GET</code> <code>/account/~/extension/~/message-store</code>

For more information you could refer to our <a href="http://ringcentral-faq.readthedocs.io/en/latest/fax/" rel="nofollow noreferrer">RingCentral-Fax-FAQ</a> 

For any support related issues, please open a case with our developer support at :

<code>Portal</code> : <a href="https://developer.ringcentral.com/support.html" rel="nofollow noreferrer">https://developer.ringcentral.com/support.html</a> 
<code>Email</code> : <a href="http://devsupport@ringcentral.com" rel="nofollow noreferrer">devsupport@ringcentral</a> ( with the necessary details )

blocks|key|303553|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|303554|在重新运行我的测试后，我意识到这些传真在web界面上也有问题，所以附件一定是因为某种原因而损坏了。|blockquote|303555|303556|303557|很高兴你找到了你的问题，这是由于实际损坏的传真在评论线程。对于遇到这种情况的其他人，这里有一些关于如何测试TIFF文件的信息。|offset|length|style|CODE|303558|如果传真附件恰好是|303559|图像(只有极少数是)，则返回的数据似乎不完整，它始终是390字节...有没有人遇到过这个问题？|303560|303561|303562|使用RingCentral应用程序接口下载TIFF图像对我来说很好。我在community+Ruby+SDK中使用了fax_download.rb脚本。我使用fax_send.rb演示脚本将SDK中包含的test_file.pdf发送到一个为TIFF文件配置的扩展，并且能够使用fax_download.rb脚本将其作为14538字节的TIFF文件下载和读取。|303563|资源链接：|303564|303565|Ruby+SDK|unordered-list-item|303566|fax_send.rb|303567|fax_download.rb|303568|test_file.pdf|303569|303570|有没有一种方法可以强制所有的传真存储为|303571|格式的RingCentral？|303572|303573|303574|正如上面的@CarpeDiem所提到的，每个扩展名都有一个PDF和TIFF的文件类型配置设置。为PDF配置所有扩展名将确保所有存储的传真都是PDF格式。这可以由后端的RingCentral支持来设置，但我不确定是否有面向客户的设置。|303575|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ringcentral-ruby/ringcentral-sdk-ruby|1|https://github.com/ringcentral-ruby/ringcentral-sdk-ruby/blob/master/scripts/fax_download.rb|2|3|https://github.com/ringcentral-ruby/ringcentral-sdk-ruby/blob/master/scripts/fax_send.rb|4|5|https://github.com/ringcentral-ruby/ringcentral-sdk-ruby/blob/master/scripts/test_file.pdf^0|0|0|0|0|1H|4|0|0|0|0|0|L|4|1M|F|27|B|2U|D|3D|4|3V|F|4O|4|10|I|0|1M|F|1|0|0|0|0|8|2|0|0|B|0|B|3|0|0|F|0|F|4|0|0|D|0|D|5|0|0|0|0|0|0|T|3|X|4|1Y|3|0^^$0|@$1|2|3|-4|4|5|6|1U|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1V|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|1W|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|1X|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|1Y|7|@$H|1Z|I|20|J|K]]|8|@]|9|$]]|$1|L|3|M|4|5|6|21|7|@]|8|@]|9|$]]|$1|N|3|O|4|C|6|22|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|23|7|@]|8|@]|9|$]]|$1|Q|3|-4|4|5|6|24|7|@]|8|@]|9|$]]|$1|R|3|S|4|5|6|25|7|@$H|26|I|27|J|K]|$H|28|I|29|J|K]|$H|2A|I|2B|J|K]|$H|2C|I|2D|J|K]|$H|2E|I|2F|J|K]|$H|2G|I|2H|J|K]|$H|2I|I|2J|J|K]]|8|@$H|2K|I|2L|1|2M]|$H|2N|I|2O|1|2P]]|9|$]]|$1|T|3|U|4|5|6|2Q|7|@]|8|@]|9|$]]|$1|V|3|-4|4|5|6|2R|7|@]|8|@]|9|$]]|$1|W|3|X|4|Y|6|2S|7|@]|8|@$H|2T|I|2U|1|2V]]|9|$]]|$1|Z|3|10|4|Y|6|2W|7|@$H|2X|I|2Y|J|K]]|8|@$H|2Z|I|30|1|31]]|9|$]]|$1|11|3|12|4|Y|6|32|7|@$H|33|I|34|J|K]]|8|@$H|35|I|36|1|37]]|9|$]]|$1|13|3|14|4|Y|6|38|7|@$H|39|I|3A|J|K]]|8|@$H|3B|I|3C|1|3D]]|9|$]]|$1|15|3|-4|4|5|6|3E|7|@]|8|@]|9|$]]|$1|16|3|17|4|5|6|3F|7|@]|8|@]|9|$]]|$1|18|3|19|4|C|6|3G|7|@]|8|@]|9|$]]|$1|1A|3|-4|4|5|6|3H|7|@]|8|@]|9|$]]|$1|1B|3|-4|4|5|6|3I|7|@]|8|@]|9|$]]|$1|1C|3|1D|4|5|6|3J|7|@$H|3K|I|3L|J|K]|$H|3M|I|3N|J|K]|$H|3O|I|3P|J|K]]|8|@]|9|$]]|$1|1E|3|-4|4|5|6|3Q|7|@]|8|@]|9|$]]]|1F|$1G|$4|1H|1I|1J|9|$1K|1L]]|1M|$4|1H|1I|1J|9|$1K|1N]]|1O|$4|1H|1I|1J|9|$1K|1L]]|1P|$4|1H|1I|1J|9|$1K|1Q]]|1R|$4|1H|1I|1J|9|$1K|1N]]|1S|$4|1H|1I|1J|9|$1K|1T]]]]

<blockquote>
 After rerunning my test again I realized these faxes are also having problems through the web interface, so the attachment must be corrupted for some reason.
</blockquote>

Glad you found your issue and it was due to actual corrupted faxes in the comment thread. For others that come across this, here's some information on how to test <code>TIFF</code> files.

<blockquote>
 if the fax attachment happens to be a TIFF image (only very few are) the data returned seems to be incomplete, it is always 390 bytes[...] Has anyone come across this issue?
</blockquote>

Downloading <code>TIFF</code> images works fine for me using the RingCentral API. I used the <a href="https://github.com/ringcentral-ruby/ringcentral-sdk-ruby/blob/master/scripts/fax_download.rb" rel="nofollow noreferrer"><code>fax_download.rb</code></a> script in the <a href="https://github.com/ringcentral-ruby/ringcentral-sdk-ruby" rel="nofollow noreferrer">community Ruby SDK</a>. I used the <code>fax_send.rb</code> demo script to send the <code>test_file.pdf</code> included in the SDK to an extension configured for <code>TIFF</code> files and was able to download and read it as a 14538 byte <code>TIFF</code> file using the <code>fax_download.rb</code> script.

Resource links:

<ul>
<li><a href="https://github.com/ringcentral-ruby/ringcentral-sdk-ruby" rel="nofollow noreferrer">Ruby SDK</a></li>
<li><a href="https://github.com/ringcentral-ruby/ringcentral-sdk-ruby/blob/master/scripts/fax_send.rb" rel="nofollow noreferrer"><code>fax_send.rb</code></a></li>
<li><a href="https://github.com/ringcentral-ruby/ringcentral-sdk-ruby/blob/master/scripts/fax_download.rb" rel="nofollow noreferrer"><code>fax_download.rb</code></a></li>
<li><a href="https://github.com/ringcentral-ruby/ringcentral-sdk-ruby/blob/master/scripts/test_file.pdf" rel="nofollow noreferrer"><code>test_file.pdf</code></a></li>
</ul>

<blockquote>
 Is there a way to force all faxes to be stored as PDF by RingCentral?
</blockquote>

There is a file type configuration setting for <code>PDF</code> and <code>TIFF</code> per extension as mentioned by @CarpeDiem above. Having all extensions configured for PDF would ensure all stored faxes were in <code>PDF</code> format. This can be set by RingCentral support on the backend, but I'm not sure if there is a customer facing setting.

I have a program written in Node using the "<a href="https://www.npmjs.com/package/ringcentral" rel="nofollow noreferrer">RingCentral</a>" package, the program downloads faxes sent to a RingCentral account. When the faxes are in <code>PDF</code> format everything works correctly, however if the fax attachment happens to be a <code>TIFF</code> image (only very few are) the data returned seems to be incomplete, it is always 390 bytes. Inspecting the file shows that it is indeed the TIFF image (starts with <code>II*</code>).

Has anyone come across this issue? Is there a way to force all faxes to be stored as PDF by RingCentral?

Thanks,

-Carlos

Processing TIFF Attachments in RingCentral using NodeJS

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我在Node中使用"“包编写了一个程序，该程序下载发送到RingCentral帐户的传真。当传真为PDF格式时，一切正常工作，但是，如果传真附件恰好是TIFF图像(只有极少数)，则返回的数据似乎不完整，始终为390字节。检查文件会发现它确实是TIFF图像(以II*开头)。有没有人遇到过这个问题？有没有一种方法可以强制所...

问使用NodeJS在RingCentral中处理TIFF附件
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用NodeJS在RingCentral中处理TIFF附件EN