incoming fax only getting partial pages

Discussion in '3CX Phone System - General' started by shaam, Jun 29, 2014.

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

    Joined:
    Jun 29, 2014
    Messages:
    1
    Likes Received:
    0
    When receiving faxes, the pages are coming across as partials and everything is smashed together.

    Setup:
    Patton SN4970 with a T1 for calls to outside world
    3CX 12 SP6 Pro 32 SIm
    Server 2012 R2 VM on VMware 5.5
    fax being sent to a DID that is then being sent to email fax@xxxxxxx.com

    I attached some examples of what they look like and call trace.
    Any Insight would be great


    29-Jun-2014 01:21:00.829 Leg L:337.2[Fax] is terminated: Cause: BYE from 127.0.0.1:5100
    29-Jun-2014 01:19:38.467 [CM503007]: Call(C:337): Fax:8888 has joined, contact <sip:8888@127.0.0.1:5100>
    29-Jun-2014 01:19:38.465 L:337.2[Fax] has joined to L:337.1[Line:10000<<6132493235]
    29-Jun-2014 01:19:38.409 [CM503025]: Call(C:337): Calling T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone] for L:337.1[Line:10000<<6132493235]
    29-Jun-2014 01:19:38.364 [CM503027]: Call(C:337): From: Line:10000<<6132493235 ("Main Fax:" <sip:6132493235@192.168.1.240:5060>) to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone]
    29-Jun-2014 01:19:38.364 [CM503004]: Call(C:337): Route 1: from L:337.1[Line:10000<<6132493235] to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone]

    29-Jun-2014 01:21:00.831 [CM503008]: Call(C:337): Call is terminated
    29-Jun-2014 01:21:00.829 Leg L:337.2[Fax] is terminated: Cause: BYE from 127.0.0.1:5100
    29-Jun-2014 01:20:48.171 Currently active calls - 1: [337]
    29-Jun-2014 01:20:16.169 Currently active calls - 1: [337]
    29-Jun-2014 01:19:46.167 Currently active calls - 1: [337]
    29-Jun-2014 01:19:39.775 [CM506004]: STUN request to STUN server 173.212.195.222:3478 has timed out; used Transport: 192.168.1.240:5060
    29-Jun-2014 01:19:38.467 [CM503007]: Call(C:337): Fax:8888 has joined, contact <sip:8888@127.0.0.1:5100>
    29-Jun-2014 01:19:38.467 [CM503007]: Call(C:337): Line:10000<<6132493235 has joined, contact <sip:10000@192.168.1.15:5060>
    29-Jun-2014 01:19:38.465 L:337.2[Fax] has joined to L:337.1[Line:10000<<6132493235]
    29-Jun-2014 01:19:38.409 [CM503025]: Call(C:337): Calling T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone] for L:337.1[Line:10000<<6132493235]
    29-Jun-2014 01:19:38.364 [CM503027]: Call(C:337): From: Line:10000<<6132493235 ("Main Fax:" <sip:6132493235@192.168.1.240:5060>) to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone]
    29-Jun-2014 01:19:38.364 [CM503004]: Call(C:337): Route 1: from L:337.1[Line:10000<<6132493235] to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone]
    29-Jun-2014 01:19:38.363 [CM503001]: Call(C:337): Incoming call from Line:10000<<6132493235 to <sip:8888@192.168.1.240:5060>
    29-Jun-2014 01:19:38.362 Line limit check: Current # of calls for line Lc:10000(@Patton 4970[<sip:10000@192.168.1.15:5060>]) is 1; limit is 23
    29-Jun-2014 01:19:38.358 [CM503012]: Inbound any hours rule (Main Fax) for 10000 forwards to Fax:8888
     

    Attached Files:

  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    A couple of basic questions:

    1. Are the samples the result of an inside fax at the office being sent back out to the DID, or are they from an outside source on a PTSN line? If from inside and going out via 3CX, this is a possible cause as 3CX does not have t38 on regular extensions, but does on the fax extension 88888 (in your case).

    2. Does the remote fax think that success was achieved, or does it indicate a fail and retry?

    My best suggestion is to contact Patton. They have very good support and I suspect that it could be how the device is set-up relative to the T-1 as you didn't indicate if a T1 or T1 PRI. There are a number of options within the device that can be optimized, but you will likely need to give them more details about what is in front of the device from which it is getting its feed.
     
  3. intellegens

    Joined:
    Jun 19, 2013
    Messages:
    18
    Likes Received:
    0
    Is the PRI providing the timing source? Does your Patton model support high precision clock?
    This is likely a clocking issue but I am not very familiar with Patton implementations. Check and see if there is any way to change the timing settings to sync with the PRI
     
Thread Status:
Not open for further replies.