Faxmaker 14 & Diva SoftIP, no outbound faxes

Faxmaker 14 & Diva SoftIP, no outbound faxes (Full Version)

All Forums >> [Messaging] >> GFI FAXmaker

Message

karst -> Faxmaker 14 & Diva SoftIP, no outbound faxes (25.Apr.2008 1:23:37 PM)
Hey guys, We just switched over to Faxmaker 14 from Faxmaker 12. No problems with that. But today we've started to test a new PBX that supports FoIP (T.38). The eicon diva softip line-test software can call and receive calls and faxes without any problems, so it seems the pbx and eicon diva configuration itself is ok. But it seems that GFI has somewhat more trouble. The exact problems is that while GFI can receive faxes correctly, GFI can't send them. While sending a fax the monitor shows 'calling <number>' for only 1 second, after that the message 'Call failed: 46' shows. It kind of hangs up right away. The outside line isn't even accessed, since that would show up on our PBX terminal. So it seems that it tries to call, but can't access the outside line... After studying some log files we changed the local Fax ID from nil to our internal number (300) and it made no difference. We also tried changing it to our external number (030...) but this also made no difference. We changed this because our Eicon Diva line-test software gave errors when the calling-party-number was left empty. Before this we were testing with Faxmaker 12 and there filling the local fax ID actually made the difference between no outbound calling and successfull outbound call (BUT without the fax arriving). What happened in the last case was that the fax was transmitted, but faxmaker hung on closing the connection. Does anybody has a clue what to do about this annoying problem? Thanks in advance, Karst

Whargoul -> RE: Faxmaker 14 & Diva SoftIP, no outbound faxes (28.Apr.2008 10:15:34 AM)
the latest build of faxmaker uses the fax number field from the sending user's Active Directory properties instead of local fax id. try filling that in for the user you are testing from, removing the user, restarting the service, readding the user, restarting the services, then send another test.

JoeKern -> RE: Faxmaker 14 & Diva SoftIP, no outbound faxes (28.Apr.2008 2:43:11 PM)
Karst, Please make sure that in your GFI FAXmaker Configuration, under Lines/Devices (properties) then on the properties of each line, that you are NOT using Tone dialing or Wait for Dial tone. If you make any changes please apply them and restart your GFI FAXmaker Services What you may also want to do is make use of WireShark (www.Wireshark.org) to trace the VIOP calls to see what is happening during the transmission. 1. Download WireShark and install. 2. Click on Capture, then click on Interfaces. Please then click the Start next to your Nic card. 3. While the Capture is running send a fax. After it fails stop the Capture. 4. Then click on Statistics and then VIOP Calls. Here you should be able to see your call and select it then click the graph button. This will allow you to see the communications between your Gateway and the Nic of the card. You will see arrows in the direction of the communication, if you see the communication in one direction several times then there may be an issue from the opposite direction. There should be an indication as to what might be "rejecting" the transmission.

karst -> RE: Faxmaker 14 & Diva SoftIP, no outbound faxes (2.May2008 5:55:22 AM)
@Whargoul: Thanks, your hint worked. I've now changed all users fax numbers to our internal fax number and now we can send faxes without problems.

karst -> RE: Faxmaker 14 & Diva SoftIP, no outbound faxes (9.May2008 9:53:41 AM)
Okay, almost everything works now, but there is just one little annoying thing... After sending a fax the line stays open and the gfi monitor says ´Disconnecting´. When I click abort in the monitor gfi breaks up the connection and sends a success mail to the sender. Does somebody know how to fix this problem? Karst

JoeKern -> RE: Faxmaker 14 & Diva SoftIP, no outbound faxes (12.May2008 10:43:17 AM)
Karst, Well to me it sounds like we are never receiving disconnect, or a Message confirmation from the other end. The only way to find out would be to follow my directions above to run a WireShark trace to see which is happening. There should be some settings that we can put in place to "end" the call after a certain number of seconds, but we need to be sure that this is the problem.

Page: [1]