Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Lot of problem with FAX sender

Discussion in '3CX Phone System - General' started by gmaoret, Nov 13, 2009.

Thread Status:
Not open for further replies.
  1. gmaoret

    Joined:
    Dec 7, 2007
    Messages:
    28
    Likes Received:
    1
    I've a 3CX (latest version) installed on a Windows 2008 Standard virtual machine under Hyper-V.

    The PBX is connected to 2 Italian ISDN line (Telecom Italia) with a Patton 4554 (firmware 5.3 2009-1-15) with latest generated cfg file.

    All is working fine but FAXsender (configured following the WIKI guide).

    We simply can't send faxes cause they end up in Microsoft interface with "Irreversible Error".

    This is the 3CX log of a FAX sending session:

    13:32:22.881 [CM503008]: Call(89): Call is terminated
    13:32:22.773 [MS210006] C:89.1:Offer provided. Connection(by pass mode): 192.168.50.247:4864(4865)
    13:32:22.772 [MS210000] C:89.2:Offer received. RTP connection: 192.168.50.247:4864(4865)
    13:32:22.771 Remote SDP is set for legC:89.2
    13:32:14.695 Remote SDP is set for legC:89.2
    13:32:14.484 Remote SDP is set for legC:89.1
    13:32:13.494 Session 12766 of leg C:89.1 is confirmed
    13:32:13.393 [CM503007]: Call(89): Device joined: sip:10000@192.168.50.247:5060
    13:32:13.389 [CM503007]: Call(89): Device joined: sip:888@192.168.50.4:5100;user=phone
    13:32:13.388 [MS210007] C:89.1:Answer provided. Connection(by pass mode): 192.168.50.247:4864(4865)
    13:32:13.388 [MS210007] C:89.1:Answer provided. Connection(by pass mode): 192.168.50.247:4864(4865)
    13:32:13.386 [MS210001] C:89.2:Answer received. RTP connection[unsecure]: 192.168.50.247:4864(4865)
    13:32:13.385 Remote SDP is set for legC:89.2
    13:32:05.779 [CM503002]: Call(89): Alerting sip:10000@192.168.50.247:5060
    13:32:03.499 [CM503025]: Call(89): Calling Unknown:0445376959@(Ln.10000@4554_Lentiai_5.3)@[Dev:sip:10000@192.168.50.247:5060]
    13:32:03.498 [MS210006] C:89.2:Offer provided. Connection(by pass mode): 192.168.50.4:10002(10003)
    13:32:03.497 [MS210006] C:89.2:Offer provided. Connection(by pass mode): 192.168.50.4:10002(10003)
    13:32:03.452 [CM503004]: Call(89): Route 1: Unknown:0445376959@(Ln.10000@4554_Lentiai_5.3)@[Dev:sip:10000@192.168.50.247:5060,Dev:sip:10001@192.168.50.247:5062]
    13:32:03.451 [CM503010]: Making route(s) to <sip:0445376959@192.168.50.4:5060;user=phone>
    13:32:03.451 [MS210000] C:89.1:Offer received. RTP connection: 192.168.50.4:10002(10003)
    13:32:03.449 Remote SDP is set for legC:89.1
    13:32:03.447 [CM503001]: Call(89): Incoming call from Fax.888 to <sip:0445376959@192.168.50.4:5060;user=phone>
    13:32:03.440 [CM500002]: Info on incoming INVITE:
    INVITE sip:0445376959@192.168.50.4:5060;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.50.4:5100;branch=z9hG4bK-6B87-BE
    Max-Forwards: 70
    Route: <sip:192.168.50.4:5060;lr>
    Contact: <sip:888@192.168.50.4:5100;user=phone>
    To: <sip:0445376959@192.168.50.4:5060;user=phone>
    From: <sip:888@192.168.50.4:5060>;tag=6F13
    Call-ID: cPi3hYvQvdRW0Noi@192.168.50.4
    CSeq: 179 INVITE
    Allow: INVITE, BYE, ACK, OPTIONS, CANCEL
    Proxy-Authorization: Digest username="888",realm="3CXPhoneSystem",nonce="414d535c010de2c379:0c206c6612e3407869d62fa0e577d29e",uri="sip:0445376959@192.168.50.4",response="be036ae86f43d17960773639f982d931",algorithm=MD5,cnonce="5B70",opaque="",nc=00000001
    User-Agent: Netbricks-Sip-T.38IAF/2.01 (PRODUCT ID:5, 05 Jul 2007)
    Content-Length: 0
     
  2. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,528
    Likes Received:
    71
    Hi
    Try to send the fax to 888 first, to see if it works.
    Regards
    vali
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. gmaoret

    Joined:
    Dec 7, 2007
    Messages:
    28
    Likes Received:
    1
    Sending to 888 works fine.
     
  4. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,971
    Likes Received:
    278
    I suggest upgrading to the latest Patton firmware. Ensure you have commercial edition and check whether inbound faxes works well. Please note that the fax sending module is provided as is - its not part of 3CX Phone System. That said, if you have commercial edition with support we will try to help you - please open a support ticket in the support portal...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. coslau

    Joined:
    Sep 28, 2009
    Messages:
    6
    Likes Received:
    0
    Dear,
    We're using Berofix 1600 Gateway.
    Reception works well thru gateway, calling 888 works, but sending fails...
    On the gateway tracelog, it's like nothing is sent by FaxServer... Do you have any idea of what is wrong ?

    Here are the 3cxvirtfax.log
    • 14:37:31.753|0D1C|3CXVirtFax.cpp(85): FaxDevStartJob(), Entered
      14:37:31.753|0D1C|FSP.cpp(291): FSProv::StartJob(), Job 8 registered
      14:37:33.456|0CFC|3CXVirtFax.cpp(101): FaxDevSend(), Entered
      14:37:33.456|0CFC|FSP.cpp(359): FSProv::Send(), Fax file: C:\ProgramData\Microsoft\Windows NT\MSFax\Queue\1CA78D4C20D45.FRT
      14:37:33.456|0CFC|FaxSender.cpp(446): CProtSocket::SendRequest(), Entered
      14:37:33.456|0CFC|FaxSender.cpp(512): CProtSocket::SendReqData_SendFax(), Entered
      14:37:33.456|0CFC|FaxSender.cpp(376): CProtSocket::SendPacket(), Sending packet 0
      14:37:33.846|09A4|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
      14:37:33.846|09A4|FaxSender.cpp(635): CProtSocket::RecvData_Version(), Entered
      14:37:33.846|09A4|FaxSender.cpp(649): CProtSocket::RecvData_Version(), Server version: 0
      14:37:33.846|0CFC|FaxSender.cpp(376): CProtSocket::SendPacket(), Sending packet 6
      14:37:33.846|0CFC|FaxSender.cpp(395): CProtSocket::SendPacket(), Sending packet 1 after reconnection
      14:37:34.659|09A4|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
      14:37:34.659|09A4|FaxSender.cpp(657): CProtSocket::RecvData_FaxRequest(), Entered
      14:37:34.659|09A4|FaxSender.cpp(667): CProtSocket::RecvData_FaxRequest(), File request: 0
      14:37:39.784|09A4|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
      14:37:39.784|09A4|FaxSender.cpp(675): CProtSocket::RecvData_FaxNotify(), Entered
      14:37:39.784|09A4|FaxSender.cpp(690): CProtSocket::RecvData_FaxNotify(), Job 8: Event 1 gotten. Error type: 2
      14:37:39.784|09A4|FSP.cpp(70): FaxJob::SetFaxEvent(), Event: 1
      14:37:39.784|09A4|FSP.cpp(80): FaxJob::SetFaxEvent(), Fax failed
      14:37:39.784|0CFC|FSP.cpp(407): FSProv::Send(), Error! Fax to T0383378217 (<0383378217>) failed: FOIP server reported error
      14:37:39.784|0CFC|3CXVirtFax.cpp(117): FaxDevReportStatus(), Entered
      14:37:39.784|0CFC|FSP.cpp(485): FSProv::ReportStat(), Status 0x20000800 returned
      14:37:39.846|0CFC|3CXVirtFax.cpp(93): FaxDevEndJob(), Entered
      14:37:39.846|0CFC|FSP.cpp(310): FSProv::EndJob(), Job 8 ended
      14:37:39.971|09A4|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
      14:37:39.971|09A4|FaxSender.cpp(72): CSocket::ReceiveDataFromSocket(), Socket buffer is empty
      14:37:39.971|09A4|FaxSender.cpp(357): CProtSocket::Close(), Closing socket 640
      14:37:39.971|09A4|FaxSender.cpp(423): CProtSocket::ReceivePacket(), Error! Error of packet receiving.
      14:37:39.971|09A4|FaxSender.cpp(357): CProtSocket::Close(), Closing socket -1
      14:37:39.971|09A4|FaxSender.cpp(486): CProtSocket::ReadResponse(), Error! Packet receiving error
      14:37:39.971|09A4|FaxSender.cpp(751): CFaxSender::SockReadThread::Run(), Disconnect of all sockets detected
     
  6. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,971
    Likes Received:
    278
    We are preparing a new release of the fax server send module in the coming weeks/early january. This will be fully tested with all supported gateways. Please wait for that one...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. bleakcomb

    Joined:
    Feb 7, 2010
    Messages:
    1
    Likes Received:
    0
    Did any fixes or progress for this problem make it into the recent release (8.0.10824)?
     
  8. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    172
    We made an important fix in the registration process of the fax extension.

    It is worth to give it another try with this version yes
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. gjalt

    Joined:
    Aug 21, 2010
    Messages:
    3
    Likes Received:
    0
    I notice that the fax fails, when de phone is ringing, what cold be the problem.

    16:46:49.741|1030|3CXVirtFax.cpp(85): FaxDevStartJob(), Entered
    16:46:49.741|1030|FSP.cpp(291): FSProv::StartJob(), Job 56 registered
    16:46:51.491|029C|3CXVirtFax.cpp(101): FaxDevSend(), Entered
    16:46:51.491|029C|FSP.cpp(359): FSProv::Send(), Fax file: C:\ProgramData\Microsoft\Windows NT\MSFax\Queue\1CB413FAFBE23.FRT
    16:46:51.491|029C|FaxSender.cpp(446): CProtSocket::SendRequest(), Entered
    16:46:51.491|029C|FaxSender.cpp(512): CProtSocket::SendReqData_SendFax(), Entered
    16:46:51.491|029C|FaxSender.cpp(376): CProtSocket::SendPacket(), Sending packet 1
    16:46:52.069|1100|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    16:46:52.069|1100|FaxSender.cpp(657): CProtSocket::RecvData_FaxRequest(), Entered
    16:46:52.069|1100|FaxSender.cpp(667): CProtSocket::RecvData_FaxRequest(), File request: 0
    16:46:59.507|1100|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    16:46:59.507|1100|FaxSender.cpp(675): CProtSocket::RecvData_FaxNotify(), Entered
    16:46:59.507|1100|FaxSender.cpp(690): CProtSocket::RecvData_FaxNotify(), Job 56: Event 1 gotten. Error type: 2
    16:46:59.507|1100|FSP.cpp(70): FaxJob::SetFaxEvent(), Event: 1
    16:46:59.507|1100|FSP.cpp(80): FaxJob::SetFaxEvent(), Fax failed
    16:46:59.507|029C|FSP.cpp(407): FSProv::Send(), Error! Fax to T03xxxxxx (<xxxxxxx7>) failed: FOIP server reported error
    16:46:59.507|029C|3CXVirtFax.cpp(117): FaxDevReportStatus(), Entered
    16:46:59.507|029C|FSP.cpp(485): FSProv::ReportStat(), Status 0x20000800 returned
    16:46:59.522|029C|3CXVirtFax.cpp(93): FaxDevEndJob(), Entered
    16:46:59.522|029C|FSP.cpp(310): FSProv::EndJob(), Job 56 ended
    16:48:42.963|1030|3CXVirtFax.cpp(85): FaxDevStartJob(), Entered
     
  10. gjalt

    Joined:
    Aug 21, 2010
    Messages:
    3
    Likes Received:
    0
    Date Number Voice Transmission
    Duration (*) Remote Site Coding Packets (**) Lost Delay Jitter Burst Miscellaneous
    Outgoing Caller ID:100 (Availability 100%)
    22.08.2010 10:21 888 G.711u 150 (-) - 0 ms 0 ms (0 %) Fax (T.38)
    0:01:04 192.168.178.2 270 (-) - 0 ms 0 ms (0 %)

    On Fritzbox of other side.
     
  11. gjalt

    Joined:
    Aug 21, 2010
    Messages:
    3
    Likes Received:
    0
    11:25:09.999|2AE4|FSP.cpp(359): FSProv::Send(), Fax file: C:\ProgramData\Microsoft\Windows NT\MSFax\Queue\1CB41DBE9B35B.FRT
    11:25:10.000|2AE4|FaxSender.cpp(446): CProtSocket::SendRequest(), Entered
    11:25:10.000|2AE4|FaxSender.cpp(512): CProtSocket::SendReqData_SendFax(), Entered
    11:25:10.000|2AE4|FaxSender.cpp(376): CProtSocket::SendPacket(), Sending packet 0
    11:25:10.180|2FFC|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    11:25:10.180|2FFC|FaxSender.cpp(635): CProtSocket::RecvData_Version(), Entered
    11:25:10.180|2FFC|FaxSender.cpp(649): CProtSocket::RecvData_Version(), Server version: 0
    11:25:10.180|2AE4|FaxSender.cpp(376): CProtSocket::SendPacket(), Sending packet 6
    11:25:10.180|2AE4|FaxSender.cpp(395): CProtSocket::SendPacket(), Sending packet 1 after reconnection
    11:25:10.480|2FFC|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    11:25:10.480|2FFC|FaxSender.cpp(657): CProtSocket::RecvData_FaxRequest(), Entered
    11:25:10.480|2FFC|FaxSender.cpp(667): CProtSocket::RecvData_FaxRequest(), File request: 0
    11:25:17.989|2FFC|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    11:25:17.989|2FFC|FaxSender.cpp(675): CProtSocket::RecvData_FaxNotify(), Entered
    11:25:17.989|2FFC|FaxSender.cpp(690): CProtSocket::RecvData_FaxNotify(), Job 23: Event 0 gotten. Error type: 0
    11:25:17.989|2FFC|FSP.cpp(70): FaxJob::SetFaxEvent(), Event: 0
    11:25:17.989|2FFC|FSP.cpp(75): FaxJob::SetFaxEvent(), Fax is being transmitted
    11:25:53.876|2FFC|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    11:25:53.876|2FFC|FaxSender.cpp(675): CProtSocket::RecvData_FaxNotify(), Entered
    11:25:53.876|2FFC|FaxSender.cpp(690): CProtSocket::RecvData_FaxNotify(), Job 23: Event 1 gotten. Error type: 3
    11:25:53.876|2FFC|FSP.cpp(70): FaxJob::SetFaxEvent(), Event: 1
    11:25:53.876|2FFC|FSP.cpp(80): FaxJob::SetFaxEvent(), Fax failed
    11:25:53.876|2AE4|FSP.cpp(407): FSProv::Send(), Error! Fax to T100 (<100>) failed: FOIP server reported error
    11:25:53.876|2AE4|3CXVirtFax.cpp(117): FaxDevReportStatus(), Entered
    11:25:53.876|2AE4|FSP.cpp(485): FSProv::ReportStat(), Status 0x20000800 returned
    11:25:54.050|2AE4|3CXVirtFax.cpp(93): FaxDevEndJob(), Entered
    11:25:54.050|2AE4|FSP.cpp(310): FSProv::EndJob(), Job 23 ended
    11:27:16.264|2FFC|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    11:27:16.264|2FFC|FaxSender.cpp(72): CSocket::ReceiveDataFromSocket(), Socket buffer is empty
    11:27:16.264|2FFC|FaxSender.cpp(357): CProtSocket::Close(), Closing socket 732
    11:27:16.264|2FFC|FaxSender.cpp(423): CProtSocket::ReceivePacket(), Error! Error of packet receiving.
    11:27:16.264|2FFC|FaxSender.cpp(357): CProtSocket::Close(), Closing socket -1
    11:27:16.264|2FFC|FaxSender.cpp(486): CProtSocket::ReadResponse(), Error! Packet receiving error
    11:27:16.264|2FFC|FaxSender.cpp(751): CFaxSender::SockReadThread::Run(), Disconnect of all sockets detected
    11:27:31.996|2D1C|3CXVirtFax.cpp(85): FaxDevStartJob(), Entered
    11:27:31.997|2D1C|FSP.cpp(291): FSProv::StartJob(), Job 24 registered
    11:27:33.529|29D0|3CXVirtFax.cpp(101): FaxDevSend(), Entered
     
  12. florian.bobelka

    Joined:
    Dec 1, 2010
    Messages:
    2
    Likes Received:
    0
    Hi!

    I have the same problems as you on my Windows 2008 (Windows Small Business Server 2008 (which is x64)), also working with BeroNet as ISDN-Interface and FritzBox as ATA for Fax.

    Do you have some news regarding this issue?

    If not, maybe I have some suggestions for you:
    First you need to separate "Error type: 2" and "Error type: 3"

    "Error type: 3" occours when trying to send fax to internal Fax machine using FritzBox as ATA.
    I figured out, that FritzBox is not happy with V.17 14400kbps fax transfer modus/datarate.
    Setting your Faxserver to a maximum of V.29 9600kpbs should solve that problem.
    You can do this by modifying "C:\ProgramData\3CX\Data\Fax\Cfg\in_session.cfg", setting "T38MaxBitRate [UDP] = 9600" (under [T.38 remote capabilities]) and "max speed = 9600" (under [FAX common]).
    Note that the "3CXFAXSrv" service need to be stopped before and started after the change, as well as running your text editor "as Administrator" to save the changes.

    "Error type: 2" occours when trying to send fax to external recipients.
    There are temporary files (*.t41) which get deleted by the FaxServer BEFORE itself tries to reopen them in order to send them.
    This only happens on my Windows 2008 (x64) machine, on Windows 2003 (x64) its working without problems.
    I discussed this issue a few days ago with "stefanW" from german support team, but he only mentioned that this files would NOT be used and are NOT causing this issue... I'm sure he never read the logs I posted... maybe he thinks of the *.tmp files which really can be deleted before the fax is sent.
    Anyway, I'm willing to get them notice this bug :)

    As a workaround you can "deny" user "System" the "Delete" and "Delete Subfolders and Files" in "C:\ProgramData\3CX\Data\Fax\Temp" - but setting your FaxServer "Retries" to "0" is nescessary, because Windows Fax Service will still get "Error" from 3CXFaxServer, because it can't delete the file after sending it... :)
    But at least - it should send the fax...

    Please let me know if these suggestions are working for you!
     
  13. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    172
    Fax sending is not supported by 3CX.

    You can use another solution with the new section we created for Fax ATA / fax devices - but by all means, if this current solution is working for you, we are more than happy with your progress.

    Thanks for posting your feedback here - it will definitely help other people having problems with this scenario.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. florian.bobelka

    Joined:
    Dec 1, 2010
    Messages:
    2
    Likes Received:
    0
    So then, who is responsible for the FaxServerSendModule?

    What du you mean with "another solution - new section"?
     
  15. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,153
    Likes Received:
    172
    I think you are responsible because you are willing to use it. Apart for the fact that you paid nothing for it.
    We implemented that years ago, works for some - does not work for others. If you are not happy with it, don' t use it.

    In version 9 there is a section developed specifically to remove fax responsibilities away from 3CX. It is called Fax Machines.
    When you add a fax extension, that extension is special because it talks directly to the Fax gateway ata out or in. So if there is a problem, you can troubleshoot the gateway / ata / fax machine logs and not 3CX Logs.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.