语音和统一通信 : Cisco Unity

Unity IP传真出站故障排除

2016 年 10 月 24 日 - 机器翻译
其他版本: PDFpdf | 英语 (2015 年 8 月 22 日) | 反馈


目录


简介

从一个Cisco Unity用户的出站传真在公共交换电话网(PSTN)的一台传真机的支持与从Cisco Unity 4.0(4)和Cisco IOSï ¿  ½软件版本12.3(7)T开始的Cisco Unity IP传真配置向导。此服务允许用户通过一简单电子邮件发送出站传真。目的地传真电话号码在电子邮件的标题栏包括和发送对该的邮箱Cisco Unity IP传真服务检查。服务重新排版消息,回报在相应的格式的所有附件,再寻址,并且传送信息。信息通过简单邮件传输协议(SMTP)传送到Cisco IOS网关配置以T.37离线管道功能为了发送传真到目的地电话编号。

本文讨论您使用排除故障的普通的步骤。参考Cisco Unity IP传真出站网关配置示例关于Cisco IOS网关的初始配置步骤。参考Cisco Unity的IP传真配置向导

先决条件

要求

Cisco 建议您了解以下主题:

有Cisco Unity IP传真配置向导版本2.0.0.19或以上的一个活动Cisco Unity服务器与定义的网关配置一道使用在本文为了有一个完整,有效的系统。在支持的IOS网关侧, Cisco IOS路由器T.37离线管道功能和Cisco IOS软件版本12.3(7)T或者以后与Cisco Unity版本4.0(4)或以上用Microsoft Exchange 2000或2003一起要求作为合作伙伴消息存储。

注意: 介质网关控制协议(MGCP)网络不支持T.37离线管道。当您使用T.37时,参考T.37存储和发送传真配置指南关于平台和其他限制的更多信息。

使用的组件

本文档中的信息基于以下软件和硬件版本:

  • Cisco3725作为IOS网关

  • Cisco IOS软件版本12.3(8)T4

本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始(默认)配置。如果您使用的是真实网络,请确保您已经了解所有命令的潜在影响。

规则

有关文档规则的详细信息,请参阅 Cisco 技术提示规则

背景信息

为了说明故障排除程序,了解此功能基本操作是重要的。问题然后缩小到一个特定的组件,并且更多信息对此收集。

/image/gif/paws/63355/out-fax-ts-1.gif

  1. 系统的最终用户发送电子邮件对传真邮箱。此消息必须包含在主题的[FAXPHONE=9915550]对传真邮箱(例如, fax-unity2@vnt.com),其中9915550是目的地传真机的编号。基于在网关设置的拨号计划,此编号或者先于与9或唯一接受某些位字符串。一旦它发送, Microsoft Exchange提供消息对此邮箱。

    注意: 如果电子邮件起源于另一个域,则域名系统(DNS)和远程邮件系统配置提供邮件到传真邮箱驻留的域和邮件帐户。

  2. Cisco Unity IP传真服务周期地登录传真邮箱并且检索消息。现在附件读。消息在Cisco Unity服务器被回报(例如,转换对TIF文件),假设能处理该大小的附件。

  3. 一旦附件被回报,信息传送到IOS网关。Microsoft Exchange必须配置能传送信息,被寄给收件人,例如fax=9915550@c3725-51.gateway.com。这典型地意味着一个A记录和邮件交换记录(MX纪录)该主机的(c3725-51.gateway.com)被添加到DNS和SMTP连接器被添加到Exchange路由消息。因为最终用户从未发送电子邮件直接地到网关,使用的电子邮件地址和主机名这里不需要是用户友好的。

  4. IOS网关为T.37离线管道功能配置,允许它收到SMTP消息,解释fax=9915550地址,发出呼叫到991550个编号(在任何可能的数字操作以后),然后传达TIF文件给接收传真机。

    注意: 网关不能使用MGCP使用此功能。然而,电路不需要投入只电传。语音和传真在同一个语音电路并用。在路由器的拨号对等配置确定什么实际上执行与呼叫。

  5. 一旦传真传送,网关送回传送状态通知(DSN)消息到传真邮箱(fax-unity2@vnt.com)。这指示是否传真顺利地传送。当IP传真服务登陆时, DSN消息被检索。在它未顺利地传送的案件中,原因代码被检查。或许凭此原因代码,或者再发出消息(远程传真忙碌)或消息被退还的给通知问题的用户的最终用户。没有此, IP传真服务从未知道传真是否顺利地传送。

其中一个此体系结构优点是所有问题通常被分解为相关组件。

在您排除故障前

确保CsIpFaxSvc服务安装,配置,并且运行

在您开始前,请检查设置。

适当地设置网关。参考Cisco Unity IP传真出站配置示例IP传真配置向导

设置Exchange,以便邮件从最终用户的邮件库传送到那个传真邮箱驻留的地方。它在反向也传送,以便状态消息可以被退还的到来源。邮件需要能从传真帐户传送到网关和上一步。这在DNS和Exchange介入配置。

保证IP传真服务适当地安装。在设置程序启动后,请运行Cisco Unity的配置向导并且选择Start > Programs > Unity > Cisco Unity IP传真配置向导

IP传真服务不能回报您发送对它的任何。当IP传真服务接收文件附加对电子邮件时,首先检查确保,能认可分机。这些在第三方传真管理工具设置。允许的默认扩展名是BMP、HTM、TIF和TXT。如果DOCS分机希望,则工具必须添加它,当此示例显示。

注意: 有防止在第三方传真管理工具列表的最后分机正常操作在一些版本的一个问题。欲知更多信息,请参阅Caveats部分

/image/gif/paws/63355/out-fax-ts-2.gif

选择的传真服务器是Cisco Unity IP传真路由。DOCS被添加到允许文件扩展区域。这意味着IP传真服务提供对转换引擎的附件。一旦这执行,转换引擎依靠应用程序关联与分机类型,以便能打开本文和打印它到一个文件用其打印驱动程序。DOCS扩展典型地允许默认情况下,因为Wordpad应用程序在Cisco Unity服务器安装,并且打开多数微软Word文档。一应用程序例如Acrobat Reader帮助您电传PDF文件。欲知更多信息,请参阅本文的Caveats部分

注意: 思科正式支持的唯一的申请对.doc扩展是Wordpad。如果应用程序类似Wordview或微软Word与文档分机一起使用,回报引擎可以发生故障。

注意: 请勿安装在Cisco Unity服务器的微软办公软件。这终止Cisco Unity正常操作。在Cisco Unity服务器应该安装仅支持的第三方应用。当您安装在Cisco Unity服务器时的所有第三方软件小心。

Start > Administrative Tools > Services验证CsIpFaxSvc是活跃和登录,因为字段是相同的象AvCsMgr服务。如果AvCsMgr服务没有开始,很可能,有问题。这也影响CsIpFaxSvc。参考Cisco Unity 3.1(x)和4.x :欲知更多信息, AvCsMgr服务不能开始

设置邮件客户端监控传真帐户

如果它不工作,在IP传真服务和网关安装以后,第一步将使用Microsoft Outlook Express (与)检查IP传真邮箱的互联网邮件访问协议(IMAP)或Outlook (或另一个邮政方案。因为最终用户传送信息对此邮箱,并且IP传真服务检查并且传送从此帐户的信息,请确保消息到达,并且他们适当地发送。被看到的一切此处可以诊断与使用日志文件和交换消息跟踪中心。但是,这也帮助说明产品的操作。

奥特卢克Express在Cisco Unity服务器自动地安装。Outlook是选择邮件程序与统一消息部署的Cisco Unity的。

警告 警告: 请勿安装在Cisco Unity服务器的Microsoft Outlook。它造成Cisco Unity终止操作。在Exchange服务器不应该也安装Outlook。在客户端机器必须安装然后配置它为了连接到Exchange服务器。

当您添加一个或更多邮件帐户到奥特卢克Express时,请确保您指定IMAP。如果选择POP,造成所有邮件消息从邮件库立即下载。然后IP传真服务不检测其中任一新建的消息。指定IP传真服务帐户。如果密码不知道,访问激活目录用户和计算机,查找IP传真帐户,并且重置密码是安全的。

在本文提供的故障排除方法不是您能使用的只那个。例如,如果访问IP传真帐户和通过Outlook或奥特卢克Express登陆,您能发送一测验电子邮件直接地从该位置对最终用户。您能也发送电子邮件直接地到网关。这缩小问题,因为证明,一个元素或别的适当地运作。

注册表设置

为了帮助在故障排除,请改变诊断标准,以便更多输出被记录。选择Start > Run并且登录在命令框的regedit为了启用此在CsIpFaxSvc运行的Cisco Unity服务器。一旦登记编辑工具出现,请选择HKEY_LOCAL_MACHINE \软件\激活Voice\IPFaxRouter\1.0

选择Edit > New > DWORD value。指定的名称是Diaglevel。当它创建时,请双击此密钥。在Value Data字段的输入3。这是最高诊断水平。以后,您能更改它到0 (默认)。此更改不要求您重新启动服务。

警告 警告: 当您更换错误注册表密钥或输入不正确的值时,引起服务器发生故障。确认您会恢复它,如果问题发生,在您编辑注册表项前。参考在注册表编辑器帮助内的恢复的主题欲知更多信息。Cisco Unity服务器的典型的备份不备份注册表。对于Cisco Unity故障切换系统,因为注册表更改没有复制,在一个Cisco Unity服务器的注册表更改在另一个Cisco Unity服务器手工做。请与思科技术支持联系关于如何更改注册关键设置的更多信息。

/image/gif/paws/63355/out-fax-ts-3.gif

另一有用的密钥在一些情况中是MaximumWait密钥。如果不是存在,此密钥默认到24 (几小时)。在非递送信息传送给最终用户前,它指定最大数量时刻存消息。此密钥在故障排除不直接地帮助,但是频繁地请求。

OutboundRouterDomain密钥包含使用作为邮件后缀的电子邮件域,当邮件消息被寄给将传送的地址对出站传真传送的时Cisco IOS网关。为了执行此,值,在本例中的vnt-3725-51.gateway.com,必须通过DNS解决。ping此条目可以是有用的。如果此条目不正确,电子邮件返回到发送方并且通知他们网关条目不可以是解决的。

提示: 此事实为排除故障是有用的:如果有一切安装除了Cisco IOS网关,您能临时地更改此注册表条目到一个假值,例如,不在DNS的事。然后请传送传真消息对传真邮箱。CsIpFaxSvc服务检索消息,回报附件,然后不能找出网关。一个非递送收据(NDR)通知被退还的到发送方用传送到网关传真消息的被回报的TIF附件。如果执行此,您验证那:

  • 电子邮件可以从您的最终用户被发送到传真帐户。

  • 传真可以顺利地被回报。

  • 电子邮件可以是被退还的从传真帐户对最终用户。

一切被排除了除了发送消息从传真帐户到网关和从网关到传真帐户。

封面密钥包含被回报封面的位置。传送的每传真包含与一些信息的一张封面,例如页数量。编辑此页和插入自定义信息或公司徽标是可能的。如果密钥更改到一个不存在的文件,则封面没有发送。

排除故障每个组件

步骤 1:验证信息可以从最终用户传送到传真帐户

传送从用户的信息到传真帐户。在此图表中,消息被寄给fax-unity2,是传真邮箱。用户要呼叫的编号在标题栏指定,在这种情况下是9915550。用户要电传的本文附加。

/image/gif/paws/63355/out-fax-ts-4.gif

在此信息传送后,在最初设置的传真邮箱到达。此图显示邮箱的奥特卢克Express视图。

/image/gif/paws/63355/out-fax-ts-5.gif

如果消息不到达,有一个基本电子邮件交付问题。您应该看到发送方是否接收交付故障消息。Microsoft Exchange 2000/2003有交换消息跟踪功能,允许您发现关于邮件发送的其他详细信息。例如如果发送方和传真帐户在两个独立的域,例如, a.com和b.com,则请确保发送的邮件系统适当地配置提供邮件到目的地邮件服务器。这在DNS介入设置A和MX记录然后添加SMTP连接器路由邮件。邮件在非递送消息的反向应该也能发送能被退还的对最终用户。

此图显示IOS网关的一个DNS条目有A和MX记录的。

/image/gif/paws/63355/out-fax-ts-6.gif

SMTP连接器是需要的以交换该邮件主机。

/image/gif/paws/63355/out-fax-ts-7.gif

DNS用于路由到地址空间。地址空间配置作为c3725-51.gateway.com。这只是一个许多配置。这是测验的示例环境设置。典型的公司Exchange环境更加复杂。点是确保,您从用户有邮件传真邮箱。检查Microsoft网站关于这些主题的更多信息。

确保邮件被发送从最终用户到传真帐户和从传真帐户给最终最终用户。

步骤 2:验证消息由IP传真服务处理

在IP传真服务配置时,轮询间隔指定。这指示多么IP传真服务频繁地登录传真邮箱并且检查新的消息。思科推荐设置此值低,直到产品的正常操作验证。

最好的诊断记录日志文件是IPFaxSvc<date/time>.log。它在位于在\通用服务器\日志目录。

注意: 在此trace示例,一些信息删除。

您能看到日志文件登录在每个间隔的邮箱。您能也看到它处理出站传真。

注意: 所有跟踪反射Diaglevel = 3前面提到的注册表设置。

"Logging on to mailbox [VNT2-EX1\fax-unity2]"
"CIpFaxCdoHelper::LogonToMailbox() name returned from Logon is [fax unity2]"
"Processing outbox, message count= 1"
"CIpFaxCdoHelper::ProcessFaxOutbox() processing message receipts"
"CIpFaxCdoHelper::DetermineMessageDisposition() current message 
subject=[[faxphone=9915550]]"
"CIpFaxCdoHelper::DetermineMessageDisposition() setting disposition to OUTBOUND"
"CIpFaxCdoHelper::ProcessFaxOutbox() message looks like outbound fax - not 
processing as receipt message"

重要的是出站进程顺利地登录正确邮箱,意识到有消息,获取主题,并且视为它是一出站传真。

"_RecordsetPtr::Open(Select * from tblIpFaxData where MessageEntryID = 
'00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0DEF46B5F8EAF983C6C512000000
05E5B20000E7E65E238D0DEF46B5F8EAF983C6C51200000005F55A0000') returned [0] rows - 
Code: 0x80004005. Method: CIpFaxAdoHelper::GetRecordSet. [IpFaxAdoHelper.cpp::403]"

"CIpFaxAdoHelper::Execute() Cmd=[INSERT INTO tblIpFaxData (MessageEntryID, Status, 
ScratchDirectory, TifFileName, NdrErrorCode, BusyCounter, RnaCounter, 
TimeFirstHandled) VALUES ('00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0
DEF46B5F8EAF983C6C51200000005E5B20000E7E65E238D0DEF46B5F8EAF983C6C51200000005F55A
0000', '0', 'C:\CommServer\unityMta\IpFaxScratchpad', '0188c93ff8194177b9f313edab
c2ea73.tif', '0', '0', '0', '2004-10-14 08:27:17')]"

现在消息被读取。第一条语句表明服务运行SQL查询在Cisco Unity服务器的报告数据库的tbllpFaxDatatable发现与该MessageEntryID (消息的MAPI ID的一个消息)是否存在。它没找到任何如此条目(0返回的行),因此添加与此信息的新的行。此MessageEntryID使用作为主题字段在电子邮件被发送对网关。当您直接地时查看SQL您看到:

/image/gif/paws/63355/out-fax-ts-8.gif

SQL用于记录每个消息。当传真邮箱不是空的时, SQL通过它在每个间隔并且检查占了根据此消息ID的每个消息。附件在这种情况下复制对临时目录C:\CommServer\unityMta\IpFaxScratchpad。如果有此同样消息的DSN,只需要更新类似的BusyCounter或的事。但是这是服务记录每个消息的方法。即然文件复制对临时目录,转换发生。

out-fax-ts-9.gif

"CIpFaxCdoHelper::RenderCurrentMessage() scratch file=[C:\CommServer\
unityMta\IpFaxScratchpad\render.tif]"

"CIpFaxCdoHelper::RenderCurrentMessage() outputting message body to file 
name=[C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt]"

"Rendering file [C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt] to 
[C:\CommServer\unityMta\IpFaxScratchpad\render.tif]"

"CIpFaxCdoHelper::RenderCurrentMessage() added [1] pages to TIFF"

转换进程开始。每传真包含一张封面、一个页与消息主题和任一或所有的附件。封面显示被电传页的数量。因为首先,总是发送正文首先被回报。因为它每次只回报一个消息,总是呼叫消息主题MsgBody.txt和临时输出文件render.tif。转换由图象制造者软件执行。在每转换进程完成后,返回被回报页的数量。在这种情况下,它是一个页。

步骤 3:验证转换操作

图象制造者转换引擎是打印驱动程序。它采取输入文件,打开相关的默认应用(Wordpad, Notepad,等等),并且使用图象制造者驱动程序打印它到文件。这创建TIF文件。

完整诊断文件在附录部分。当您提交问题对与转换引擎时涉及的思科技术支持,这些文件是必要的:

  • C:\ImgMaker\Conversion _Toolkit \日志\ ODCDAEMON.log —通过批处理文件完成转换的守护程序

  • C:\log\ImageMakerDocCnvrt Driver.txt —驱动程序级别信息

多数有用的信息在ODCDAEMON.log文件。对于将被回报的每个文件,您看到:

10/14/04 08:27:17
Start time: Thursday, October 14, 2004 08:27:17 AM
Daemon logged in as user: vnt2-u1-ms
Using registry root: HKEY_LOCAL_MACHINE
08:27:17: Pipe name: PrintDocDaemonPipe
08:27:17: Default printer name: ImageMaker DocCnvrt Driver
08:27:17: Registry server: <local>
08:27:17: Service started
08:27:19: 08:27:19: 10/14/04 08:27:19 ServiceRequest thread started
08:27:19: Processing 'Convert v1.0' request
08:27:19: Processing file: C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt
08:27:19: Output file: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:19: Printer name: ImageMaker DocCnvrt Driver
08:27:19: AppendTo filename set to C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:19: Input filename: C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt
08:27:19: Output filename: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:19: 0xE90: <10/14/04 08:27:19> StatusThread timeout value for jobstart: 60000
08:27:21: AutoShutdown feature activated
08:27:21: Sending response 1 to client
08:27:21: 10/14/04 08:27:21 ServiceRequest thread ended

查看的第一个元素登陆作为用户。这是CsIpFaxSvc服务使用登陆的同一个帐户。

/image/gif/paws/63355/out-fax-ts-10.gif

因为此用户启动所有应用程序并且回报他们,知道此是重要的。下一元素是输入和输出文件名。第三个要素,答复,指示被回报页的数量。在这种情况下它是一。如果答复是负的,指示一个错误。如果有错误,您必须查看立即先于它的线路。在许多情况下,错误为某些文件类型仅出现。如果错误仅出现为所有转换或为某些分机类型, ODCDAEMON日志文件显示。

手工练习转换引擎进一步测试此是有利的。登陆作为管理CsIpFaxSvc服务的同一个用户。这是为了验证同一个错误是否出现,当转换引擎从服务时启动。

如果有每个允许分机类型文件,请通过双击打开每个文件对此。相关应用程序打开并且检查更新(或一相似的进程)。一旦Acrobat,例如,这可以禁用。

终止CsIpFaxSvc。如果任何仍然ODCDAEMON进程运行,终止它与任务管理器。

注意: 如果ODCDAEMON日志文件必须保存供进一步参考,必须完成,在您ping CsIpFaxSvc前。当您重新启动服务时,它清除ODCDAEMON日志文件,并且输出丢失。

/image/gif/paws/63355/out-fax-ts-11.gif

展开从文件夹C:\ImgMaker\Conversion _Toolkit的ODCDAEMON.EXE进程。当此图显示,窗口显示:

out-fax-ts-12.gif

开从同一个文件夹的CPCOM.EXE文件。

/image/gif/paws/63355/out-fax-ts-13.gif

大多默认设置优良是。在转换字段的文件中,一个希望的输入文件选择。思科建议您分开测试每个分机类型。如果输出文件没有更改,输入文件被添附到输出文件。

点击转换。应用程序开始打印,并且此对话框出现:

out-fax-ts-14.gif

单击 Ok。选择输出的视图,当完成选项。TIF查看器启动和输出文件显示。如果有错误,在某些情况下他们是作为的相同的什么在日志文件被提交了,此示例显示。

03:07:39: Input filename: d:\CommServer\UnityMTA\IpFaxScratchpad\render.tif
03:07:39: Output filename: d:\CommServer\UnityMTA\IpFaxScratchpad\9484f347996b4ea18b0caeb52ffda465.tif
03:07:39: 0x15F0: <11/19/04 03:07:39> StatusThread timeout value for jobstart: 60000
PrintTo command does not exist for file type: MSPaper.Document
03:07:39: AutoShutdown feature activated
Conversion unsuccessful. Deleting file d:\CommServer\UnityMTA\IpFaxScratchpad\9484f347996b4ea18b0caeb52ffda465.tif
03:07:39: Sending response -20 [PrintTo command does not exist] to client

输入文件是TIF附件。但是文件类型是DOCS (MSPaper.Document)。问题在这种情况下是Microsoft应用程序例如词和Excel在服务器安装,并且他们更改注册的文件关联。编辑HKEY_CLASSES_ROOT \ .tif和TIF并且更改默认键对TIFImage.Document而不是MSPaper.Document为了改正此错误。

一旦每种文件类型验证,请关上CPCOM和ODCDAEMON windows并且重新启动CsIpFaxSvc服务。

如果所有附件出故障或有初始化错误,请重新安装转换引擎。请使用instfax.exe -z命令从IPFaxConfigWizard驻留为了卸载它的图象制造者文件夹。它然后重新安装,要求重新启动,并且重新运行从Start > Programs > Unity的Cisco Unity IP传真配置向导

最后一个选项测试错误是绕过守护进程和回报从line命令的文件。在大多数情况下,如果失败前面,它也失败此处。但是,它在某些情况下提供其他信息。这在PDFILCNV可执行帮助下执行。此程序在IPFaxConfigWizard安装路径的图象制造者子目录。例如:

PDFILCNV products.doc -Fproducts.tif

确保您能打开出现的文件。

此示例是从IpFaxSvc日志文件:

"CIpFaxCdoHelper::RenderCurrentMessage() processing attachment=[products.doc]"

"CIpFaxCdoHelper::RenderCurrentMessage() attachment written to file=
[C:\CommServer\unityMta\IpFaxScratchpad\products.doc]"

"Rendering file [C:\CommServer\unityMta\IpFaxScratchpad\products.doc] to 
[C:\CommServer\unityMta\IpFaxScratchpad\render.tif]"

"CIpFaxCdoHelper::R\
)ll
\-
\]
'==e-nderCurrentMessage() added [2] pages to TIFF"

产品DOCS附件被回报。它被添附到创建的render.tif文件前。它有两个页,做总数页三。

"CIpFaxCoverPage::GenerateFile() file=[C:\CommServer\unityMta\IpFaxScratchpad
\cover.htm] name=[Unity2 Subscriber] num=[9915550] pages=[3]"

"Rendering file [C:\CommServer\unityMta\IpFaxScratchpad\cover.htm] to 
[C:\CommServer\unityMta\IpFaxScratchpad\0188c93ff8194177b9f313edabc2ea73.tif]"

"Rendering file [C:\CommServer\unityMta\IpFaxScratchpad\render.tif] to 
[C:\CommServer\unityMta\IpFaxScratchpad\0188c93ff8194177b9f313edabc2ea73.tif]"

封面是文件cover.htm。它是有一些变量的一个简单HTML模板。它以发送消息、数字称为和发送的页数量的用户的名义填装。

在自定义cover.htm文件创建后,被回报到messageid.tif文件。及早创建的render.tif文件使,例如,被添附,对messageid.tif文件。这时messageid.tif文件是被发电子邮件或被电传的实时消息。

它顺利地被回报。SQL的一些字段更新,并且信息传送。

"2004-10-14","08:27:29","CIpFaxAdoHelper::Execute() 
Cmd=[UPDATE tblIpFaxData SET Status = '1' WHERE MessageEntryID = 
'00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0DEF46B5F8EAF983C6C
51200000005E5B20000E7E65E238D0DEF46B5F8EAF983C6C51200000005F55A0000']"

"2004-10-14","08:27:29","CIpFaxAdoHelper::Execute() Cmd=[update tblipfaxdata 
set TimeLastAttempted = '2004-10-14 08:27:29' where MessageEntryID = 
'00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0DEF46B5F8EAF983C6C5120
0000005E5B20000E7E65E238D0DEF46B5F8EAF983C6C51200000005F55A0000']";

消息的状况设置到1,并且最近更新时间填写。它发送到网关。

步骤 4:验证路由器收到并且提供消息

从IP传真帐户的发送的消息到网关必须以形式fax=####@router.gateway.com。一般, DNS A和MX记录在DNS要求,并且SMTP连接器需要被添加到Exchange路由消息到该主机。一旦这执行,您能继续进行排除故障网关。

如果只有路由器设置,您能仍然验证工作,如果使用Telnet为了访问SMTP端口和手工传送信息,当此示例显示:

telnet vnt-3725-51.gateway.com 25
Trying 14.80.51.14...
Connected to 14.80.51.14.
Escape character is '^]'.
220 vnt-3725-51.gateway.com Cisco NetWorks ESMTP server
ehlo
250-vnt-3725-51.gateway.com, hello <empty HELO/EHLO> [172.18.106.123] (really )
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-PIPELINING
250-HELP
250-DSN
250 XACCOUNTING
mail from:test@test.com
250 2.5.0 Sender <test@test.com> ok
rcpt to:fax=9915550@vnt-3725-51.gateway.com
250 2.1.5 Recipient <fax=9915550@vnt-3725-51.gateway.com> ok, maps to `9915550' (cp=no)
data
354 Enter mail, end with a single "."
This is a test message from the router.
.
554 5.3.0 An unknown error occurred
quit
221 2.3.0 Goodbye from vnt-3725-51.gateway.com; closing connection
Connection closed by foreign host.

在这种情况下有未知错误。用于传送的这发生,因为主速率接口出站传真发生故障。这是另一示例:

telnet vnt-3725-51.gateway.com 25
Trying 14.80.51.14, 25 ... Open
220 vnt-3725-51.gateway.com Cisco NetWorks ESMTP server
ehlo
250-vnt-3725-51.gateway.com, hello <empty HELO/EHLO> [172.18.106.66] (really )
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-PIPELINING
250-HELP
250-DSN
250 XACCOUNTING
mail from:test@test.com
250 2.5.0 Sender <test@test.com> ok
rcpt to:fax=9915550@error.com
553 5.4.4 <fax=9915550@error.com> Unable to relay to remote host
quit
221 2.3.0 Goodbye from vnt-3725-51.gateway.com; closing connection

在这种情况下无法中继到远程主机错误消息意味着mta接收别名列表在Cisco IOS配置里没有error.com配置。

远程登录到路由器或通过控制台访问它开始直接地排除故障网关。当您是已远程登录的时,请发出terminal monitor命令debug输出被看到。打开debug fax mta全部。如果出站语音电路是PRI, debug isdn q931也是相关命令。

警告 警告: 当您启用在路由器时的跟踪,有时影响性能。当它完成时,请用no debug all命令关掉跟踪。

注意: 这些日志被削为了节省空间。

debug输出是从一活动示例:

Oct 15 08:27:26.003: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   context(0x66CA9AC4), state=1
Oct 15 08:27:35.051: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   Calling smtp verb: ehlo 
Oct 15 08:27:35.051: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   context(0x66CA9AC4), state=1
Oct 15 08:27:35.599: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   Calling smtp verb: mail 
Oct 15 08:27:35.599: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   context(0x66CA9AC4), state=1
Oct 15 08:27:36.143: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   Calling smtp verb: rcpt 
Oct 15 08:27:36.143: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_command_rcpt:
   context(0x66CA9AC4)
Oct 15 08:27:36.143: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_command_rcpt:
   context(0x66CA9AC4)
Oct 15 08:27:36.143: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   context(0x66CA9AC4), state=1
Oct 15 08:27:36.691: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   Calling smtp verb: data 
Oct 15 08:27:36.691: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   context(0x66CA9AC4), state=2
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Received: from vnt2-ex1.vnt.com ([14.84.31.12]) by VNT1-EX2.vnt.com 
with Microsoft SMTPSVC(5.0.2195.6713);'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `       Thu, 14 Oct 2004 08:27:29 -0400'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Return-Receipt-To: "fax unity2"'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Subject: 00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0DEF46B
5F8EAF983C6C51200000005E5B30000E7E65E238D0DEF46B5F8EAF983C6C51200000005FB680000'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Date: Thu, 14 Oct 2004 08:27:29 -0400'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Message-ID: '
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `X-MS-Has-Attach: yes'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `MIME-Version: 1.0'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Content-Type: image/tiff;'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `      name="BODY.TIF"'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `X-MS-TNEF-Correlator: '
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Content-Transfer-Encoding: base64'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Content-Description: BODY.TIF'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Content-Disposition: attachment;'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `      filename="BODY.TIF"'
Oct 15 08:27:37.239: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Thread-Topic: 00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0
DEF46B5F8EAF983C6C51200000005E5B30000E7E65E238D0DEF46B5F8EAF983C6C51200000005
FB680000'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   context(0x66CA9AC4), state=2
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Thread-Index: AcSx6SvU9sc3nVffS3a4/Dwqi2Bpww=='
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `From: "fax unity2" '
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `content-class: urn:content-classes:message'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `To: '
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `Return-Path: fax-unity2@vnt.com'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `X-OriginalArrivalTime: 14 Oct 2004 12:27:29.0487 (UTC) FILETIME=[2BE0DDF0:01C4B1E9]'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_work_routine:
   (S)R: `'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_new_part:
   Field name: `subject:'
   Field value: `00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0DEF46B5F
8EAF983C6C51200000005E5B30000E7E65E238D0DEF46B5F8EAF983C6C51200000005FB680000'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_new_part:
   Field name: `date:'
   Field value: `Thu, 14 Oct 2004 08:27:29 -0400'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_new_part:
   Field name: `message-id:'
   Field value: `'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_new_part:
   Field name: `Content-Type:'
   Field value: `image/tiff; name="BODY.TIF"'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_new_part:
   Field name: `Content-Transfer-Encoding:'
   Field value: `base64'
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_new_part:
   Field name: `from:'
   Field value: `"fax unity2" '
Oct 15 08:27:37.243: //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_new_part:
   Field name: `to:'
   Field value: `'
Oct 15 08:27:37.247: //-1/E7B232638008/SMTPS/esmtp_server_engine_new_part:exit@1977
Oct 15 08:27:37.251: ISDN Se2/0:23 Q931: pak_private_number: Invalid type/plan 
0x0 0x1 may be overriden; sw-type 13
Oct 15 08:27:37.251: ISDN Se2/0:23 Q931: Applying typeplan for sw-type 0xD is 
0x0 0x0, Called num 99915550
Oct 15 08:27:37.255: ISDN Se2/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0003 
        Bearer Capability i = 0x8090A2 
                Standard = CCITT 
                Transer Capability = Speech  
                Transfer Mode = Circuit 
                Transfer Rate = 64 kbit/s 
        Channel ID i = 0xA98397 
                Exclusive, Channel 23 
        Called Party Number i = 0x80, '99915550' 
                Plan:Unknown, Type:Unknown
...
Oct 15 08:27:46.003: ISDN Se2/0:23 Q931: RX <- CONNECT pd = 8  callref = 0x8003
Oct 15 08:27:46.003: ISDN Se2/0:23 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x0003
Oct 15 08:27:52.003: %ISDN-6-CONNECT: Interface Serial2/0:22 is now connected to 
99915550 
...
Oct 15 08:30:11.735: //-1/E7B232638008/SMTPS/esmtp_server_engine_buf_mgmt:
   buffer offset=1368, state=3
Oct 15 08:30:11.735: //-1/E7B232638008/SMTPS/esmtp_server_engine_dot_check:
   Not found the terminating Dot!
Oct 15 08:30:11.739: //-1/E7B232638008/SMTPS/esmtp_server_engine_buf_mgmt:
   state=3
Oct 15 08:30:11.739: //-1/E7B232638008/SMTPS/esmtp_server_engine_buf_mgmt:
   buffer offset=1412, state=3
Oct 15 08:30:11.739: //-1/E7B232638008/SMTPS/esmtp_server_engine_dot_check:
   Found the terminating Dot!
Oct 15 08:30:11.739: //-1/E7B232638008/SMTPS/esmtp_server_engine_work_routine:   
context(0x66CA9AC4), state=10Oct 15 08:30:12.483: //-1/xxxxxxxxxxxx/SMTPS/
esmtp_server_engine_update_recipient_status:   faxmail status=6Oct 15 08:30:27.883:
 //-1/xxxxxxxxxxxx/SMTPS/esmtp_server_engine_update_recipient_status:   
faxmail status=7

在路由器的邮件服务器收到消息。SMTP会话的所有字段获得解析在路由器代码的多种级别,直到呼叫被做到编号。注意的要素在一些配置步骤列出。

show running-config输出中,您看到:

  • 传真interface-type传真邮件

  • 必须装载离线管道软件到闪存或在FTP/TFTP服务器。应用程序然后设置。例如,呼叫应用程序语音离线管道flash:app_faxmail_offramp.2.0.1.1.tcl

    注意: 用于OnRampï ¿  ½离线管道功能的工具指令语言(TCL)软件从思科下载(仅限注册用户)下载。

  • mta接收最大<recipients> —编号极大比0

  • mta接收别名<string> —必须匹配DNS后缀。例如,如果从Cisco Unity的电子邮件被发送对fax=912345@myrouter.com然后别名必须是myrouter.com。您能有多个mta接收别名

  • Exchange server>的mta send server < IP地址—为了发送DSN,网关必须连接到邮件服务器提供消息。仅一个Exchange服务器需要配置,虽然多个Exchange服务器可以配置。证实所有无效mta send server地址是否删除。否则,在列表总是使用第一个。

  • mta接收生成固定误差—这要求为了路由器能适当地送回DSN到Cisco Unity。

  • 拨号对等配置。例如:

    dial-peer voice 5590 pots
           destination-pattern 991….
           port 2/0:23
           forward-digits all
           prefix 9
         !
         dial-peer voice 2 mmoip
           application offramp
           information-type fax
           incoming called-number 991
           dsn delayed
           dsn success
           dsn failure
         !

    如果消息不到达在网关,则您必须排除故障Exchange。在Exchange 2000内的诊断为此是非常有用的。例如:

    out-fax-ts-15.gif

    类别SMTP协议和连接管理器MSExchangeTransport诊断启用。这在交换系统管理器在单个服务器属性下。当您传送信息时,错误在应用程序事件浏览器日志被看到。其中一最普通的误配置是,当在路由器的mta接收别名参数不匹配电子邮件后缀时。例如,如果传真服务尝试传送信息到fax=91234@router.abc.com,然后网关必须有mta router.abc.com配置的接收别名

步骤 5:验证路由器传送DSN信息

这是生成的通知。trace的部分省略节省空间。

Oct 15 08:30:41.739: //-1/E7B232638008/SMTPS/
esmtp_server_engine_generate_notification:
   context(0x66CA9AC4)
Oct 15 08:30:41.739: //-1/E7B232638008/SMTPS/sendDSN:
   context(0x66CA9AC4)
Oct 15 08:30:41.739: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_open:
   from=, to=fax-unity2@vnt.com
Oct 15 08:30:41.739: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_open:exit@1866
Oct 15 08:30:41.739: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_add_headers:
   from_comment=Fax Daemon
Oct 15 08:30:41.739: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_dispose_context:
exit@2109
Oct 15 08:30:41.739: //-1/E7B232638008/SMTPS/sendDSN:
   DSN sent, context(0x66CA9AC4)
Oct 15 08:30:41.739: //-1/E7B232638008/SMTPS/
esmtp_server_engine_generate_notification:exit@35
Oct 15 08:30:41.739: //-1/E7B232638008/SMTPS/esmtp_server_engine_work_routine:
   context(0x66CA9AC4), state=1
Oct 15 08:30:41.983: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_work_routine:
   socket 0 readable for first time
Oct 15 08:30:41.983: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_work_routine:
   socket 0 readable for first time
Oct 15 08:30:41.983: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 220 vnt2-ex1.vnt.com Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 
ready at  Thu, 14 Oct 2004 08:31:09 -0400 
Oct 15 08:30:41.987: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: EHLO vnt-3725-51.gateway.com
Oct 15 08:30:41.987: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-vnt2-ex1.vnt.com Hello [14.80.51.14]
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-TURN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-ATRN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-SIZE
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-ETRN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-PIPELINING
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-DSN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-ENHANCEDSTATUSCODES
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-8bitmime
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-BINARYMIME
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-CHUNKING
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-VRFY
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-EXPS GSSAPI NTLM LOGIN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-EXPS=LOGIN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-AUTH GSSAPI NTLM LOGIN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-AUTH=LOGIN
Oct 15 08:30:42.463: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-X-LINK2STATE
Oct 15 08:30:42.467: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250-XEXCH50
Oct 15 08:30:42.467: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250 OK
Oct 15 08:30:42.467: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: MAIL FROM:<>
Oct 15 08:30:42.467: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:43.011: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250 2.1.0 <>....Sender OK
Oct 15 08:30:43.011: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: RCPT TO:
Oct 15 08:30:43.011: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:43.555: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 250 2.1.5 fax-unity2@vnt.com 
Oct 15 08:30:43.555: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:44.103: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_getln:
   (C)R: 354 Start mail input; end with .
Oct 15 08:30:44.103: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: Received:  by vnt-3725-51.gateway.com for  (with Cisco NetWorks); 
Fri, 15 Oct 2004 08:30:44 +0000
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: To:  
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: Message-ID: <00042004083044107@vnt-3725-51.gateway.com>
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: Date: Fri, 15 Oct 2004 08:30:44 +0000
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_write:
   return code=0
Oct 15 08:30:44.107: //-1/xxxxxxxxxxxx/SMTPC/esmtp_client_engine_writeln:
   (C)S: Subject: Delivery Status Notification
...

如果它不工作,必须设置mta send server命令在配置里为正确Exchange服务器和端口(25默认情况下)。DSN在传真消息匹配的MMOIP拨号对等体需要配置,当发送时,并且mta receive generate permanent-error命令存在。有时命令不存在,或者指向不正确邮件服务器。

注意: Cisco IOS配置允许您配置多mta send server命令。除非该设备变得完全不能得到,但是,使用仅第一个。因此,当您更换mta send server时,您必须删除上一个一个。

如果安排Outlook或奥特卢克Express和您监控传真邮箱,您看到DSN被传送那里,在下个间隔处理由IP传真服务前。

out-fax-ts-16.gif

消息的正文包含消息ID。以前它是主题。错误在消息主题的底部附近被提及。他们是ISDN Q.931错误代码的抽象。欲知更多信息,请参阅附录

一均等地有用工具是交换消息跟踪中心。它被构件到Exchange 2000/2003系统管理器。这些是邮件消息:

/image/gif/paws/63355/out-fax-ts-17.gif

步骤 6:验证DSN消息接收

当DSN消息在IP传真服务的邮箱时,请检查为了确保,处理消息。IpFaxSvc日志文件是有用与此。

"2004-10-14","08:31:30","Logging on to mailbox [VNT2-EX1\fax-unity2]"
"2004-10-14","08:31:30","CIpFaxCdoHelper::LogonToMailbox() name returned from 
Logon is [fax unity2]""2004-10-14","08:31:30","Processing outbox, message count= 2"
"2004-10-14","08:31:30","CIpFaxCdoHelper::ProcessFaxOutbox() processing message 
receipts"
"2004-10-14","08:31:30","CIpFaxCdoHelper::DetermineMessageDisposition() 
current message subject=[Delivery Status Notification]"
"2004-10-14","08:31:30","CIpFaxCdoHelper::MessageIsReceipt() processing message, 
type=[IPM.Note]""2004-10-14","08:31:30","CIpFaxCdoHelper::MessageIsReceipt() 
processing message as DELIVERY STATUS NOTIFICATION"

消息处理。

"2004-10-14","08:31:30","CIpFaxMessageBodyParser::GetOriginalSubject 
returning subject=[00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0DEF4
6B5F8EAF983C6C51200000005E5B30000E7E65E238D0DEF46B5F8EAF983C6C51200000005FB680000]"
"2004-10-14","08:31:30","CIpFaxMessageBodyParser::GetCauseCode returning cause 
code =[16]"

原始主题从消息的正文解析。这允许您查找消息在数据库。原因代码也解析作为16。这是正常呼叫清除。这些原因代码对应于Q.931原因代码。请参阅Q.931断开原因代码关于原因代码的更多信息。

条目从数据库安全删除并且重新加写以状态0。

"2004-10-14","08:31:30","CIpFaxAdoHelper::Execute() Cmd=[DELETE 
FROM tblIpFaxData WHERE MessageEntryID = '00000000377C58FB04A29C468DAB3CBC07D
7F94B0700E7E65E238D0DEF46B5F8EAF983C6C51200000005E5B20000E7E65E238D0DEF46B5F8
EAF983C6C51200000005F55A0000']"

"2004-10-14","08:31:30","_RecordsetPtr::Open(Select * from tblIpFaxData where 
MessageEntryID = '00000000377C58FB04A29C468DAB3CBC07D7F94B0700E7E65E238D0DEF46
B5F8EAF983C6C51200000005E5B20000E7E65E238D0DEF46B5F8EAF983C6C51200000005F55A0000')
 returned [0] rows - Code: 0x80004005. Method: CIpFaxAdoHelper::GetRecordSet. 
[IpFaxAdoHelper.cpp::403]"

"2004-10-14","08:31:30","CIpFaxAdoHelper::Execute() Cmd=[INSERT INTO tblIpFaxData
 (MessageEntryID, Status, ScratchDirectory, TifFileName, NdrErrorCode, 
BusyCounter, RnaCounter, TimeFirstHandled) VALUES ('00000000377C58FB04A29C4
68DAB3CBC07D7F94B0700E7E65E238D0DEF46B5F8EAF983C6C51200000005E5B20000E7E65E
238D0DEF46B5F8EAF983C6C51200000005F55A0000', '0', 'C:\CommServer\unityMta\
IpFaxScratchpad', '2fd36f2af94d4137835928894fb397eb.tif', '0', '0', '0', 
'2004-10-14 08:31:30')]"

两个邮件消息删除。当您检查出站传真消息时,有无。

2004-10-14","08:32:30","Processing outbox, message count= 0"

警告

这些是存在当前测试的版本的一些个当前警告。参考IP传真配置向导或帮助文件解决这些问题的更多当前版本的。

附录

回报引擎跟踪文件

这些是在本文讨论的示例的跟踪。有两个文件。一个文件是为守护程序,并且另一个文件是为打印驱动程序。典型地这些不是需要的。但是,其中每一的示例为能相比较包括。当您提交问题用转换引擎时,这些文件与正常IP传真日志一起要求。

ODCDAEMON.log

C:\ImgMaker\Conversion_Toolkit\log\ODCDAEMON.log

频繁使用得此文件并且是相当易读的。输入和输出文件在独立的部分列出,并且答复代码是列出的。如果答复代码是正的,则指示被回报到输出TIF文件页的数量。否定答复代码指示一个错误。检查进程运行的用户。这是关键,因为这是一定能打开单个应用转换他们到TIF的用户。

10/14/04 08:27:17
Start time: Thursday, October 14, 2004 08:27:17 AM
Daemon logged in as user: vnt2-u1-ms
Using registry root: HKEY_LOCAL_MACHINE
08:27:17: Pipe name: PrintDocDaemonPipe
08:27:17: Default printer name: ImageMaker DocCnvrt Driver
08:27:17: Registry server: <local>
08:27:17: Service started
08:27:19: 
08:27:19: 10/14/04 08:27:19 ServiceRequest thread started
08:27:19: Processing 'Convert v1.0' request
08:27:19: Processing file: C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt
08:27:19: Output file: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:19: Printer name: ImageMaker DocCnvrt Driver
08:27:19: AppendTo filename set to C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:19: Input filename: C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt
08:27:19: Output filename: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:19: 0xE90: <10/14/04 08:27:19> StatusThread timeout value for jobstart: 60000
08:27:21: AutoShutdown feature activated
08:27:21: Sending response 1 to client
08:27:21: 10/14/04 08:27:21 ServiceRequest thread ended
08:27:21: 
08:27:21: 10/14/04 08:27:21 ServiceRequest thread started
08:27:21: Processing 'Convert v1.0' request
08:27:21: Processing file: C:\CommServer\unityMta\IpFaxScratchpad\products.doc
08:27:21: Output file: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:21: Printer name: ImageMaker DocCnvrt Driver
08:27:21: AppendTo filename set to C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:21: Input filename: C:\CommServer\unityMta\IpFaxScratchpad\products.doc
08:27:21: Output filename: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:21: 0xEB8: <10/14/04 08:27:21> StatusThread timeout value for jobstart: 60000
08:27:23: AutoShutdown feature activated
08:27:23: Sending response 2 to client
08:27:23: 10/14/04 08:27:23 ServiceRequest thread ended
08:27:23: 
08:27:23: 10/14/04 08:27:23 ServiceRequest thread started
08:27:23: Processing 'Convert v1.0' request
08:27:23: Processing file: C:\CommServer\unityMta\IpFaxScratchpad\cover.htm
08:27:23: Output file: C:\CommServer\unityMta\IpFaxScratchpad\
          0188c93ff8194177b9f313edabc2ea73.tif
08:27:23: Printer name: ImageMaker DocCnvrt Driver
08:27:23: AppendTo filename set to C:\CommServer\unityMta\
          IpFaxScratchpad\0188c93ff8194177b9f313edabc2ea73.tif
08:27:23: Input filename: C:\CommServer\unityMta\IpFaxScratchpad\cover.htm
08:27:23: Output filename: C:\CommServer\unityMta\IpFaxScratchpad\
          0188c93ff8194177b9f313edabc2ea73.tif
08:27:23: 0xED8: <10/14/04 08:27:23> StatusThread timeout value for jobstart: 60000
08:27:24: AutoClose skipping window: <Print> with class: <#32770> because parent is IE6
08:27:24: AutoClose skipping window: <Print> with class: <#32770> because parent is IE6
08:27:26: AutoShutdown feature activated
08:27:26: Sending response 1 to client
08:27:26: 10/14/04 08:27:26 ServiceRequest thread ended
08:27:26: 
08:27:26: 10/14/04 08:27:26 ServiceRequest thread started
08:27:26: Processing 'Convert v1.0' request
08:27:26: Processing file: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:26: Output file: C:\CommServer\unityMta\IpFaxScratchpad\
          0188c93ff8194177b9f313edabc2ea73.tif
08:27:26: Printer name: ImageMaker DocCnvrt Driver
08:27:26: AppendTo filename set to C:\CommServer\unityMta\IpFaxScratchpad\
          0188c93ff8194177b9f313edabc2ea73.tif
08:27:26: Input filename: C:\CommServer\unityMta\IpFaxScratchpad\render.tif
08:27:26: Output filename: C:\CommServer\unityMta\IpFaxScratchpad\
          0188c93ff8194177b9f313edabc2ea73.tif
08:27:26: 0xEDC: <10/14/04 08:27:26> StatusThread timeout value for jobstart: 60000
08:27:29: AutoShutdown feature activated
08:27:29: Sending response 3 to client
08:27:29: 10/14/04 08:27:29 ServiceRequest thread ended

驱动程序日志

C:\log\ImageMaker DocCnvrt Driver.log

当您提交问题用转换引擎对思科技术支持时,此trace是必要的。

--------------------------------------->
Log session started: 04-10-14, 08:27:19 AM
Platform: WinNT 4.0
Release Compilation
pszPrinterName ImageMaker DocCnvrt Driver
pszAnsiFileName C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt
pszOutFileName C:\CommServer\unityMta\IpFaxScratchpad\render.tif
FileType:0 multiPages:1 command:2 timeout:1800

Entering pdcf_WriteInfoForControlDialog()
oppening file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.FWD"
to transfer data (printdoc.dll -> printdoc.exe dialog)
data flushed!
MS: 18808737
deleted file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
used to transfer data from dialog back to here!
MS: 18808737

Leaving pdcf_WriteInfoForControlDialog()

verb:[printto] params:["ImageMaker DocCnvrt Driver" "winspool" "Ne00:"]
lpFile:[C:\CommServer\unityMta\IpFaxScratchpad\MsgBody.txt]

Calling ShellExecuteEx()
MS: 18808737
ShellExecute() succeded

Calling pdcf_WaitForDoneFromControlDialog()
MS: 18808769

Entering pdcf_WaitForDoneFromControlDialog()
Monitoring cancel event: ImageMaker DocCnvrt Driver.printdoc.cancel
Event already exists [this is good]
  fopen() failed
  fread() failed
!DONE: timeout = 1799
reading file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
to get 'done' signal from dialog
MS: 18809776
ppd_trans_feedback.done = TRUE

Calling pdcf_WriteAckToControlDialog()
MS: 18809776

Entering pdcf_WriteAckToControlDialog
flushing 'done ack' signal to dialog
MS: 18809776
Have to wait

Leaving pdcf_WriteAckToControlDialog


Leaving pdcf_WaitForDoneFromControlDialog()

pdcf_WaitForDoneFromControlDialog() returned
MS: 18810425

Entering pdcf_CleanUpControlDialog()
MS: 18810425
Log session stopped: 04-10-14, 08:27:21 AM
--------------------------------------->

--------------------------------------->
Log session started: 04-10-14, 08:27:21 AM
Platform: WinNT 4.0
Release Compilation
pszPrinterName ImageMaker DocCnvrt Driver
pszAnsiFileName C:\CommServer\unityMta\IpFaxScratchpad\products.doc
pszOutFileName C:\CommServer\unityMta\IpFaxScratchpad\render.tif
FileType:0 multiPages:1 command:2 timeout:1800

Entering pdcf_WriteInfoForControlDialog()
oppening file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.FWD"
to transfer data (printdoc.dll -> printdoc.exe dialog)
data flushed!
MS: 18810518
deleted file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
used to transfer data from dialog back to here!
MS: 18810518


Leaving pdcf_WriteInfoForControlDialog()

verb:[printto] params:["ImageMaker DocCnvrt Driver" "winspool" "Ne00:"]
lpFile:[C:\CommServer\unityMta\IpFaxScratchpad\products.doc]

Calling ShellExecuteEx()
MS: 18810518
ShellExecute() succeded

Calling pdcf_WaitForDoneFromControlDialog()
MS: 18810561

Entering pdcf_WaitForDoneFromControlDialog()
Monitoring cancel event: ImageMaker DocCnvrt Driver.printdoc.cancel
Event already exists [this is good]
  fopen() failed
  fread() failed
!DONE: timeout = 1799
reading file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
to get 'done' signal from dialog
MS: 18811581
!DONE: timeout = 1798
reading file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
to get 'done' signal from dialog
MS: 18812585
ppd_trans_feedback.done = TRUE

Calling pdcf_WriteAckToControlDialog()
MS: 18812585

Entering pdcf_WriteAckToControlDialog
flushing 'done ack' signal to dialog
MS: 18812585
Have to wait

Leaving pdcf_WriteAckToControlDialog


Leaving pdcf_WaitForDoneFromControlDialog()

pdcf_WaitForDoneFromControlDialog() returned
MS: 18812858

Entering pdcf_CleanUpControlDialog()
MS: 18812858
Log session stopped: 04-10-14, 08:27:23 AM
--------------------------------------->

--------------------------------------->
Log session started: 04-10-14, 08:27:23 AM
Platform: WinNT 4.0
Release Compilation
pszPrinterName ImageMaker DocCnvrt Driver
pszAnsiFileName C:\CommServer\unityMta\IpFaxScratchpad\cover.htm
pszOutFileName C:\CommServer\unityMta\IpFaxScratchpad\
0188c93ff8194177b9f313edabc2ea73.tif
FileType:0 multiPages:1 command:2 timeout:1800

Entering pdcf_WriteInfoForControlDialog()
oppening file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.FWD"
to transfer data (printdoc.dll -> printdoc.exe dialog)
data flushed!
MS: 18812890
deleted file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
used to transfer data from dialog back to here!
MS: 18812890

Leaving pdcf_WriteInfoForControlDialog()

verb:[printto] params:["ImageMaker DocCnvrt Driver" "winspool" "Ne00:"]
lpFile:[C:\CommServer\unityMta\IpFaxScratchpad\cover.htm]

Calling ShellExecuteEx()
MS: 18812894
ShellExecute() succeeded

Calling pdcf_WaitForDoneFromControlDialog()
MS: 18812897

Entering pdcf_WaitForDoneFromControlDialog()
Monitoring cancel event: ImageMaker DocCnvrt Driver.printdoc.cancel
Event already exists [this is good]
  fopen() failed
  fread() failed
!DONE: timeout = 1799
  fopen() failed
  fread() failed
!DONE: timeout = 1798
reading file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
to get 'done' signal from dialog
MS: 18814909
ppd_trans_feedback.done = TRUE

Calling pdcf_WriteAckToControlDialog()
MS: 18814909

Entering pdcf_WriteAckToControlDialog
flushing 'done ack' signal to dialog
MS: 18814909
Have to wait

Leaving pdcf_WriteAckToControlDialog


Leaving pdcf_WaitForDoneFromControlDialog()

pdcf_WaitForDoneFromControlDialog() returned
MS: 18815620

Entering pdcf_CleanUpControlDialog()
MS: 18815620
Log session stopped: 04-10-14, 08:27:26 AM
--------------------------------------->

--------------------------------------->
Log session started: 04-10-14, 08:27:26 AM
Platform: WinNT 4.0
Release Compilation
pszPrinterName ImageMaker DocCnvrt Driver
pszAnsiFileName C:\CommServer\unityMta\IpFaxScratchpad\render.tif
pszOutFileName C:\CommServer\unityMta\IpFaxScratchpad\
0188c93ff8194177b9f313edabc2ea73.tif
FileType:0 multiPages:1 command:2 timeout:1800

Entering pdcf_WriteInfoForControlDialog()
oppening file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.FWD"
to transfer data (printdoc.dll -> printdoc.exe dialog)
data flushed!
MS: 18815632
deleted file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD" 
used to transfer data from dialog back to here!
MS: 18815632

Leaving pdcf_WriteInfoForControlDialog()

verb:[printto] params:["ImageMaker DocCnvrt Driver" "winspool" "Ne00:"]
lpFile:[C:\CommServer\unityMta\IpFaxScratchpad\render.tif]

Calling ShellExecuteEx()
MS: 18815632
ShellExecute() succeded

Calling pdcf_WaitForDoneFromControlDialog()
MS: 18815659

Entering pdcf_WaitForDoneFromControlDialog()
Monitoring cancel event: ImageMaker DocCnvrt Driver.printdoc.cancel
Event already exists [this is good]
  fopen() failed
  fread() failed
!DONE: timeout = 1799
reading file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD"
 to get 'done' signal from dialog
MS: 18816667
!DONE: timeout = 1798
reading file: "C:\ImgMaker\Conversion_Toolkit\ImageMaker DocCnvrt Driver.BWD"
 to get 'done' signal from dialog
MS: 18817671
ppd_trans_feedback.done = TRUE

Calling pdcf_WriteAckToControlDialog()
MS: 18817671

Entering pdcf_WriteAckToControlDialog
flushing 'done ack' signal to dialog
MS: 18817671
Have to wait

Leaving pdcf_WriteAckToControlDialog


Leaving pdcf_WaitForDoneFromControlDialog()

pdcf_WaitForDoneFromControlDialog() returned
MS: 18818319

Entering pdcf_CleanUpControlDialog()
MS: 18818319
Log session stopped: 04-10-14, 08:27:29 AM
--------------------------------------->

Q.931断开原因代码

Code      Cause
    0           Valid cause code not yet received
    1           Unallocated (unassigned) number
    2           No route to specified transit network (WAN)
    3           No route to destination
    4           send special information tone
    5           misdialled trunk prefix.
    6           Channel unacceptable
    7           Call awarded and being delivered in an established channel
    8           Prefix 0 dialed but not allowed
    9           Prefix 1 dialed but not allowed
    10          Prefix 1 dialed but not required
    11          More digits received than allowed, call is proceeding
    16          Normal call clearing
    17          User busy
    18          No user responding
    19          no answer from user
    21          Call rejected
    22          Number changed
    23          Reverse charging rejected
    24          Call suspended
    25          Call resumed
    26          Non-selected user clearing
    27          Destination out of order
    28          Invalid number format (incomplete number)
    29          Facility rejected
    30          Response to STATUS ENQUIRY
    31          Normal, unspecified
    33          Circuit out of order
    34          No circuit/channel available
    35          Destination unattainable
    37          Degraded service
    38          Network (WAN) out of order
    39          Transit delay range cannot be achieved
    40          Throughput range cannot be achieved
    41          Temporary failure
    42          Switching equipment congestion
    43          Access information discarded
    44          Requested circuit channel not available
    45          Pre-empted
    46          Precedence call blocked
    47          Resource unavailable - unspecified
    49          Quality of service unavailable
    50          Requested facility not subscribed
    51          Reverse charging not allowed
    52          Outgoing calls barred
    53          Outgoing calls barred within CUG
    54          Incoming calls barred
    55          Incoming calls barred within CUG
    56          Call waiting not subscribed
    57          Bearer capability not authorized
    58          Bearer capability not presently available
    63          Service or option not available, unspecified
    65          Bearer service not implemented
    66          Channel type not implemented
    67          Transit network selection not implemented
    68          Message not implemented
    69          Requested facility not implemented
    70          Only restricted digital information bearer capability
                        is available
    79          Service or option not implemented, unspecified
    81          Invalid call reference value
    82          Identified channel does not exist
    83          A suspended call exists, but this call identity does not
    84          Call identity in use
    85          No call suspended
    86          Call having the requested call identity has been cleared
    87          Called user not member of CUG
    88          Incompatible destination
    89          Non-existent abbreviated address entry
    90          Destination address missing, and direct call not subscribed
    91          Invalid transit network selection (national use)
    92          Invalid facility parameter
    93          Mandatory information element is missing
    95          Invalid message, unspecified
    96          Mandatory information element is missing
    97          Message type non-existent or not implemented
    98          Message not compatible with call state or message type
                   non-existent or not implemented 
    99          information element nonexistant or not implemented
    100         Invalid information element contents 
    101         Message not compatible with call state
    102         Recovery on timer expiry
    103         parameter non-existent or not implemented - passed on
    111         Protocol error unspecified
    127         Internetworking, unspecified

相关信息


Document ID: 63355