Problem with fax with 3CX + LinkSys SPA 2102 + Fax Server

Discussion in '3CX Phone System - General' started by cibernetica.it, Dec 23, 2010.

Thread Status:
Not open for further replies.
  1. cibernetica.it

    Joined:
    Dec 23, 2010
    Messages:
    7
    Likes Received:
    0
    Hi, i'm at the first configuration of a 3CX, with a linksyst phone adapter SPA 2102 for the fax line, and a Patton for the isdn line.

    i have 3CX Pro on running on a machine. The same machine (Windows 2003 server) act as fax server.
    on the 3cx i've created the fax machine and the incoming rule to redirect the calls on the fax number to the correct trunk.
    on the linksys spa2102, i've configurated the static ip, the rtp packet size to 0.30, the proxy and outbounding proxy to the 3cx machine, the subscriber info according to the fax account created on the 3cx server, the sip port to 5060.
    (for some parameters i've followed this guide: http: //www.3cx.com/voip-gateways/linksys-3102/ - NO LONGER AVAILABLE

    The isdn line works fine: it's possible to make and receive calls. but i can't get fax working fine:
    - i receive fax with one page corretly
    - but i can't receive fax with multiple pages, in fax console windows the status is 'Partially Received', or 'the remote fax has not answered within the timeout and the call has been terminated'
    - i can't send both one and multiple pages fax

    any suggestions please?
    thanks in advance
     
  2. cibernetica.it

    Joined:
    Dec 23, 2010
    Messages:
    7
    Likes Received:
    0
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    the log:

    16:43:04.140 [CM503020]: Normal call termination. Reason: Not available
    16:43:04.140 [CM503016]: Call(153): Attempt to reach <sip:889@192.168.0.111:5060;user=fax> failed. Reason: Temporarily Unavailable
    16:43:04.140 [CM503003]: Call(153): Call to sip:889@192.168.0.111:5060 has failed; Cause: 480 Temporarily not available; from IP:192.168.0.211:5060
    16:42:40.500 Currently active calls - 1: [153]
    16:42:08.500 Currently active calls - 1: [153]
    16:42:04.156 [CM503002]: Call(153): Alerting sip:889@192.168.0.211:5060
    16:42:04.078 [CM503025]: Call(153): Calling @[Dev:sip:889@192.168.0.211:5060]
    16:42:04.031 [CM503004]: Call(153): Route 1: @[Dev:sip:889@192.168.0.211:5060]
    16:42:04.031 [CM503010]: Making route(s) to <sip:889@192.168.0.111:5060;user=fax>
    16:42:04.031 [CM503001]: Call(153): Incoming call from XXXXXXXXXX@(Ln.10000@GW-Patton) to <sip:889@192.168.0.111:5060;user=fax>
    16:42:04.031 [CM503012]: Inbound any hours rule (*) for 10000 forwards to Fax:889
    16:41:03.375 [CM503020]: Normal call termination. Reason: Not available
    16:41:03.375 [CM503016]: Call(152): Attempt to reach <sip:889@192.168.0.111:5060;user=fax> failed. Reason: Temporarily Unavailable
    16:41:03.375 [CM503003]: Call(152): Call to sip:889@192.168.0.111:5060 has failed; Cause: 480 Temporarily not available; from IP:192.168.0.211:5060
    16:40:47.093 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.0.111:5060
    16:40:32.500 Currently active calls - 1: [152]
    16:40:03.390 [CM503002]: Call(152): Alerting sip:889@192.168.0.211:5060
    16:40:03.312 [CM503025]: Call(152): Calling @[Dev:sip:889@192.168.0.211:5060]
    16:40:03.265 [CM503004]: Call(152): Route 1: @[Dev:sip:889@192.168.0.211:5060]
    16:40:03.265 [CM503010]: Making route(s) to <sip:889@192.168.0.111:5060;user=fax>
    16:40:03.265 [CM503001]: Call(152): Incoming call from XXXXXXXXXX@(Ln.10000@GW-Patton) to <sip:889@192.168.0.111:5060;user=fax>
    16:40:03.265 [CM503012]: Inbound any hours rule (*) for 10000 forwards to Fax:889
    16:39:34.125 [CM503008]: Call(151): Call is terminated
    16:39:28.500 Currently active calls - 1: [151]
    16:38:56.500 Currently active calls - 1: [151]
    16:38:28.156 [CM503007]: Call(151): Device joined: sip:10000@192.168.0.210:5060
    16:38:28.156 [CM503007]: Call(151): Device joined: sip:889@192.168.0.211:5060
    16:38:27.156 [CM503002]: Call(151): Alerting sip:10000@192.168.0.210:5060
    16:38:25.843 [CM503025]: Call(151): Calling Unknown:XXXXXXXXXX@(Ln.10000@GW-Patton)@[Dev:sip:10000@192.168.0.210:5060]
    16:38:25.796 [CM503004]: Call(151): Route 1: Unknown:XXXXXXXXXX@(Ln.10000@GW-Patton)@[Dev:sip:10000@192.168.0.210:5060,Dev:sip:10001@192.168.0.210:5062]
    16:38:25.781 [CM503010]: Making route(s) to <sip:XXXXXXXXXX@192.168.0.111>
    16:38:25.781 [CM503001]: Call(151): Incoming call from Fax.889 to <sip:XXXXXXXXXX@192.168.0.111>
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,357
    Likes Received:
    224
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    The guide says to... " In the "RTP Parameters" set the "RTP Packet Size" to "0.020".

    Don't know if that will make a difference.
     
  4. cibernetica.it

    Joined:
    Dec 23, 2010
    Messages:
    7
    Likes Received:
    0
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    thanks, but both 0.020 and 0.030 make no difference
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,357
    Likes Received:
    224
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    You certainly aren't the first person to have problems with fax over VoIP. Go back through the forums, there are many cases of it "sort of working", but not quite. It really is hit and miss, trial and error making sure that all of the settings in all devices are set to give fax the best chance of working. Even then....
     
  6. cibernetica.it

    Joined:
    Dec 23, 2010
    Messages:
    7
    Likes Received:
    0
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    but i've not a Voip solution. it's a normal analogic telephone line. however i'll try the workaround for the voip solutions... i will post news as soon as possible

    thanks
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,357
    Likes Received:
    224
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    But using an ATA and gateway converts the analog signal to VoIP in between the two, and that can cause a problem, as you've discovered.
     
  8. jtrollen

    Joined:
    May 17, 2010
    Messages:
    21
    Likes Received:
    0
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    I had similar problems with a 2102 and for reasons that I don't understand I had to set "Fax Enable T38" to "No" and "FAX Passthru Method:" to "NSE". Give it a try and see if it works.
     
  9. cibernetica.it

    Joined:
    Dec 23, 2010
    Messages:
    7
    Likes Received:
    0
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    i've tried but nothing...
    here in italy we must use the t38...
    If i change FAX Passthru Method i can't totally receive fax...
     
  10. cibernetica.it

    Joined:
    Dec 23, 2010
    Messages:
    7
    Likes Received:
    0
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    today i've tried this:
    inseat of connecting the linksys spa to the pc with windows server 2003 + 3cx server + windows fax server, i've connected the linksys spa to a fax machine (a printer with builtin fax) and ALL WORKS!!!

    so i ask you if there is a particular configuration to do in windows server 2003 machine fax server. (on the same machine run the 3cx server and the windows fax server)...

    thanks
     
  11. cibernetica.it

    Joined:
    Dec 23, 2010
    Messages:
    7
    Likes Received:
    0
    Re: Problem with fax with 3CX + LinkSys SPA 2102 + Fax Serve

    Someone told me ATA was born to connect real fax machine like Multifunction printer,... and may be not compatible with pc connected through modem...

    so, are pc-modem (usb and pci) compatibile/supported by ata?
     
Thread Status:
Not open for further replies.