Outbound faxing with Windows 2008 doesn't work

Discussion in '3CX Phone System - General' started by mbaltus, Jun 15, 2009.

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

    Joined:
    Dec 12, 2008
    Messages:
    66
    Likes Received:
    0
    When trying to fax using Windows 2008 fax server and the 3CX Fax Server plug in, the fax fails.
    This pertains to the latest 3CX v7.1 on a Windows 2008 Standard server.

    According to the log, there is no route to the number, but if I try that number directly from a phone, I can reach it.

    any hints?

    The log of 3CX says (anonimized):

    Code:
    
    18:47:51.558  [CM503008]: Call(5): Call is terminated
    18:47:51.542  [CM503015]: Call(5): Attempt to reach <sip:xxxxxxxxxxx@192.168.10.5:5060;user=phone> failed. Reason: Not Found
    18:47:51.542  [CM503014]: Call(5): No known route to target: <sip:xxxxxxxxxxx@192.168.10.5:5060;user=phone>
    18:47:51.527  [CM503010]: Making route(s) to <sip:xxxxxxxxxxx@192.168.10.5:5060;user=phone>
    18:47:51.527  [MS210000] C:5.1:Offer received. RTP connection: 192.168.10.5:10002(10003)
    18:47:51.527  Remote SDP is set for legC:5.1
    18:47:51.527  [CM503001]: Call(5): Incoming call from Fax.888 to <sip:xxxxxxxxxxx@192.168.10.5:5060;user=phone>
    18:47:51.527  [CM500002]: Info on incoming INVITE:
      INVITE sip:xxxxxxxxxxx@192.168.10.5:5060;user=phone SIP/2.0
      Via: SIP/2.0/UDP 192.168.10.5:5100;branch=z9hG4bK-64EB-11
      Max-Forwards: 70
      Route: <sip:192.168.10.5:5060;lr>
      Contact: <sip:888@192.168.10.5:5100;user=phone>
      To: <sip:xxxxxxxxxxx@192.168.10.5:5060;user=phone>
      From: <sip:888@192.168.10.5:5060>;tag=5BF9
      Call-ID: uKx-DmBd8aoNmt8K@192.168.10.5
      CSeq: 16 INVITE
      Allow: INVITE, BYE, ACK, OPTIONS, CANCEL
      Proxy-Authorization: Digest username="888",realm="3CXPhoneSystem",nonce="414d535c00470c3719:b819acf6be5d8405e4f86cf180c8af24",uri="sip:xxxxxxxxxxx@192.168.10.5",response="225181cabdc10c8fd0d50f639b2eb67e",algorithm=MD5,cnonce="37CB",opaque="",nc=00000001
    
      User-Agent: Netbricks-Sip-T.38IAF/2.01 (PRODUCT ID:5, 05 Jul 2007)
      Content-Length: 0
    
    
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. bluetel2

    bluetel2 Member

    Joined:
    Oct 16, 2008
    Messages:
    377
    Likes Received:
    5
    hello,

    hmm outbound or inbound ?

    are you sure your sda is configured ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mbaltus

    Joined:
    Dec 12, 2008
    Messages:
    66
    Likes Received:
    0
    Outbound naturally, since inbound is not supported.

    SDA is?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    What is destination of your call?

    BTW, What do you mean "inbound is not supported"?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. mbaltus

    Joined:
    Dec 12, 2008
    Messages:
    66
    Likes Received:
    0
    Using the Windows Fax Service. As far as I understoord, receiving faxes using the fax service is not supported.

    The destination is an external fax. I use an application (e.g. Notepad) and fax to the fax driver. To make sure there are no rights issues, I even used the administrator account, but to no avail.
    Calling the number (using one of the regular extensions) is not a problem, so there should not be any routing issues.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    FYI, we have our own fax service for inbound faxes.

    Analogue fax machine on ATA? If ATA doesn't support T.38 - it will not work.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mbaltus

    Joined:
    Dec 12, 2008
    Messages:
    66
    Likes Received:
    0
    What I'm trying to accomplish is using the Windows 2008 fax server to send faxes using 3CX and a Patton 4960 E1 Gateway. Using that I try to fax to an analog fax machine at the other end. Outbound calls to that fax machine or no problem (but rather useless :) ), but faxing gives the mentioned error in the log. For some reason the 3CX Faxserver cannot route correctly, so it seems.

    (btw: I know that inbound faxing is supported on 3CX, although having some issues with that as well. But that's stuff for a different topic).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Set FAXDIRECTSDP = 1 in custom parameters.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. mbaltus

    Joined:
    Dec 12, 2008
    Messages:
    66
    Likes Received:
    0
    I'll try what that does tonight.
    I assume I need to restart services?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    No, this setting has immediate effect.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.