Desktop Faxing Desktop Faxing mike2838 (IS/IT--Management) (OP) 27 Mar 06 11:06 When trying to send a fax user is receiving the error code: Failed to send fax, any suggestions? RE: Desktop Faxing elturko (TechnicalUser) 27 Mar 06 14:26 Mike,I'm getting the same thing. I can fax to other CallPilot mailboxes, though. (When using the Fax Driver to print, you enter "m" followed by the mailbox number, i.e. m1628, and the fax gets delivered.)This is 4.04.04.07, supposedly all the latest and greatest.Any ideas from anyone? I'll keep looking into it and post back if I come across anything.Thanks,Matt RE: Desktop Faxing lretrievers (Vendor) 27 Mar 06 17:08 Are you using desktop messaging to send the faxes? Is the server set up with an FQDN for the Call Pilot? It sounds like something is not completely set up. RE: Desktop Faxing elturko (TechnicalUser) 27 Mar 06 18:20 Yes, trying to send from My CallPilot, Outlook Express, or the Nortel Fax printer which allows you to fax from any application. My server is set up with an FQDN, and everything else seems to be working OK.When sending to an internal recipient, My CallPilot creates an address of firstname.lastname@example.org (where 123456 is our VPIM shortcut and 7890 is the mailbox). When trying to send to an external fax, it creates FAXemail@example.com. I did a network trace (watched the actual traffic). It's sending to the CallPilot server using SMTP, so everything is in plain text. When it sends to the internal recipient, everything goes through fine. When sending to the outside recipient, as soon as the server sees the destination address, it responds with a message about not being able to route messages to "inpmwrocallpilot.mydomain.com".One thing I thought of today, and I don't know if it matters, but... The server name is CALLPILOT (the default), but the FQDN is "inpmwrocallpilot.mydomain.com". When setting it up, we tried to make the server name INPMWROCALLPILOT, but it was too long. Would the fact that the host part of the FQDN and the server name don't match make any difference? I looked through the documentation and didn't see any requirements that they match, but thought I would throw that out there just in case.Thanks,Matt RE: Desktop Faxing lretrievers (Vendor) 27 Mar 06 19:17 your FQDN for the callpilot, should be CALLPILOT.yourdomain.com; the names have to match. RE: Desktop Faxing elturko (TechnicalUser) 27 Mar 06 20:19 I can understand needing to be the same, but does it have to be CALLPILOT? I'll have a hard time getting our network people to buy off on that, as the INPMWRO identifieds our office. It also wouldn't be unthinkable that another office would have a CallPilot in the future. Would MWROCALLPILOT work? I might have a better chance of getting that approved.Thanks,Matt RE: Desktop Faxing lretrievers (Vendor) 28 Mar 06 06:11 The computer name can be changed, this is not a problem. However, you also need to rerun the Call Pilot wizard to do this. Changing the computer name in "MY COMPUTER" won't do it in the Call Pilot system itself. It requires the wizard to be udpated too. RE: Desktop Faxing elturko (TechnicalUser) 28 Mar 06 09:04 Thanks for the info. Our infrastructure team is creating the DNS entry and I'll try the rename today. Will post back with results.Mike -- Do you by chance have a mismatched FQDN too? RE: Desktop Faxing elturko (TechnicalUser) 28 Mar 06 13:53 Matching the server name with the host part of the FQDN did the trick! Both are now MWROCALLPILOT and we're happily faxing from our computers. If I could give you more than one star I would. Thanks for the help.--Matt RE: Desktop Faxing lretrievers (Vendor) 28 Mar 06 17:49 You are very welcome. Glad you are up and operational. RE: Desktop Faxing mike2838 (IS/IT--Management) (OP) 30 Mar 06 12:25 I changed the fqdn to match in both places and still having problems. Can receive external faxes, cannot send internal or external. Any suggestions? RE: Desktop Faxing lretrievers (Vendor) 30 Mar 06 19:01 The VPIM is usually the other "gotcha" on that. Have you checked it? It should be 1NPANXX. RE: Desktop Faxing mike2838 (IS/IT--Management) (OP) 27 Apr 06 11:06 The problem turned out to be the customers Macafee had the port blocked.thanks for all of yur help.