Unable to recieve or send faxes

Discussion in '3CX Phone System - General' started by jesnofear, Mar 9, 2010.

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

    Joined:
    Jan 17, 2010
    Messages:
    5
    Likes Received:
    0
    Hey everyone!
    I have spent the last 14 hours trying to get this to work, but it still has failed me. I have made progress.
    First let me give you the background, VoIP provider Broadvoice, Firewall Cisco Pix (Setup as a 1:1 associatoin from outside to inside 100% port pass-through right now). Ext IP 68.16x.149.74, Int 192.168.2.7
    I am trying to Fax over IP, and at first when setting up 3cx to recieve faxes over one of my phone lines it would drop the call instantly. i disabled the SRT which gave me some progress, i see a handshake but keeps dropping call due to no ACT recieved. here is the log output i am recieving.

    12:24:09.449 [MS105000] C:5.2: No RTP packets were received:remoteAddr=68.166.149.74:10000,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7008
    12:24:08.902 [CM503008]: Call(5): Call is terminated
    12:24:08.902 [CM503021]: Call(5): ACK is not received
    12:23:36.887 [MS210003] C:5.2:Answer provided. Connection(transcoding mode[unsecure]):127.0.0.1:7008(7009)
    12:23:36.887 [MS210001] C:5.1:Answer received. RTP connection[unsecure]: 147.135.32.248:19318(19319)
    12:23:36.887 Remote SDP is set for legC:5.1
    12:23:36.465 [MS210002] C:5.1:Offer provided. Connection(transcoding mode): 68.16x.149.74:9008(9009)
    12:23:36.465 Remote SDP is set for legC:5.2
    12:23:35.652 Session 3801 of leg C:5.1 is confirmed
    12:23:35.512 [CM503007]: Call(5): Device joined: sip:8888@192.168.2.7:5100;user=phone
    12:23:35.496 [CM503007]: Call(5): Device joined: sip:240xxx3005@sip.broadvoice.com:5060
    12:23:35.496 [MS210003] C:5.1:Answer provided. Connection(transcoding mode[unsecure]):68.16x.149.74:9008(9009)
    12:23:35.496 [MS210001] C:5.2:Answer received. RTP connection[unsecure]: 68.16x.149.74:10000(10001)
    12:23:35.480 Remote SDP is set for legC:5.2
    12:23:35.480 [CM503002]: Call(5): Alerting sip:8888@192.168.2.7:5100;user=phone
    12:23:35.402 [CM503025]: Call(5): Calling @[Dev:sip:8888@192.168.2.7:5100;user=phone]
    12:23:35.402 [MS210002] C:5.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7008(7009)
    12:23:35.387 [CM503004]: Call(5): Route 1: @[Dev:sip:8888@192.168.2.7:5100;user=phone]
    12:23:35.387 [CM503010]: Making route(s) to <sip:8888@192.168.2.7:5060;user=fax>
    12:23:35.387 [MS210000] C:5.1:Offer received. RTP connection: 147.135.32.248:19318(19319)
    12:23:35.387 Remote SDP is set for legC:5.1
    12:23:35.387 [CM505003]: Provider:[BV-3005(FAX)] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:240xxx3005@68.166.149.74:5060]
    12:23:35.355 [CM503001]: Call(5): Incoming call from 301xxx2137@(Ln.10004@BV-3005(FAX)) to <sip:8888@192.168.2.7:5060;user=fax>
    12:23:35.355 [CM503012]: Inbound office hours rule (unnamed) for 10004 forwards to Fax:8888
    12:23:35.355 Looking for inbound target: called=240xxx3005; caller=301xxx2137
    12:23:35.340 [CM500002]: Info on incoming INVITE:
    INVITE sip:240xxx3005@192.168.2.7:5060 SIP/2.0
    Via: SIP/2.0/UDP 147.135.32.221:5060;branch=z9hG4bK-BroadWorks.192.168.0.3-192.168.32.221V5060-0-570030092-1359869359-1268155412502-
    Max-Forwards: 69
    Contact: <sip:301xxx2137@147.135.32.221:5060>
    To: "Jason"<sip:240xxx3005@192.168.2.7>
    From: "Intelsat"<sip:301xxx2137@147.135.32.221;user=phone>;tag=9abc
    Call-ID: 2d802fe-d8@147.135.32.221
    CSeq: 1 INVITE
    Supported: 100rel
    Content-Length: 0



    It dosent seem to look like other loggs i have seen for recieving faxes.
     
  2. KerryG

    KerryG Active Member

    Joined:
    Jun 19, 2009
    Messages:
    960
    Likes Received:
    0
    The first problem is that you are trying to fax over VoIP. It is horribly unreliable and you will continue to suffer extreme bouts of frustration as your users complain about failed faxes.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    The log is slightly strange...
    What is the version of 3CX PBX?

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. jesnofear

    Joined:
    Jan 17, 2010
    Messages:
    5
    Likes Received:
    0
    Thank you for your comments, I have done faxing over voip before, not with 3cx but another pbx with no issues.

    Installed Version:8.0.10116.583

    I am currently using Stun-less setup. Turn off stun server is checked, public ip is listed as 68.16x.149.74 NIC is selected as 192.168.2.7
    I was thinking it was a firewall issue at first as well, i had the ACL's setup to do a 1 to 1 translation, inside 192.168.2.7 is seen by the outside as 68.16x.149.74 and vise versa, and allowed needed ports through, but to remove that out of the equation, i unblocked all ports and still same results.
     
  6. jesnofear

    Joined:
    Jan 17, 2010
    Messages:
    5
    Likes Received:
    0
    also, i just tried faxing to my self and was failing as well,

    here is a log from that as well.

    21:11:50.027 [CM503008]: Call(22): Call is terminated

    21:11:06.012 Session 4102 of leg C:22.1 is confirmed

    21:11:05.949 [CM503007]: Call(22): Device joined: sip:8888@192.168.2.7:5100;user=phone

    21:11:05.933 [CM503007]: Call(22): Device joined: sip:8888@192.168.2.7:5100;user=phone

    21:11:05.933 [MS210007] C:22.1:Answer provided. Connection(by pass mode): 68.166.149.74:0(1)

    21:11:05.933 [MS210007] C:22.1:Answer provided. Connection(by pass mode): 68.166.149.74:0(1)

    21:11:05.933 Remote SDP is set for legC:22.2

    21:11:05.933 [CM503002]: Call(22): Alerting sip:8888@192.168.2.7:5100;user=phone

    21:11:02.308 [CM503025]: Call(22): Calling @[Dev:sip:8888@192.168.2.7:5100;user=phone]

    21:11:02.293 [MS210006] C:22.2:Offer provided. Connection(by pass mode): 68.166.149.74:10002(10003)

    21:11:02.293 [MS210006] C:22.2:Offer provided. Connection(by pass mode): 68.166.149.74:10002(10003)

    21:11:02.262 [CM503004]: Call(22): Route 1: @[Dev:sip:8888@192.168.2.7:5100;user=phone]

    21:11:02.262 [CM503010]: Making route(s) to <sip:8888@192.168.2.7:5060;user=phone>

    21:11:02.262 [MS210000] C:22.1:Offer received. RTP connection: 68.166.149.74:10002(10003)

    21:11:02.262 Remote SDP is set for legC:22.1

    21:11:02.230 [CM503001]: Call(22): Incoming call from Fax.8888 to <sip:8888@192.168.2.7:5060;user=phone>

    21:11:02.230 [CM500002]: Info on incoming INVITE:

    INVITE sip:8888@192.168.2.7:5060;user=phone SIP/2.0

    Via: SIP/2.0/UDP 192.168.2.7:5100;branch=z9hG4bK-462F-109

    Max-Forwards: 70

    Route: <sip:192.168.2.7:5060;lr>

    Contact: <sip:8888@192.168.2.7:5100;user=phone>

    To: <sip:8888@192.168.2.7:5060;user=phone>

    From: <sip:8888@192.168.2.7:5060>;tag=76F8

    Call-ID: 6NU4Yl4xS0Yskif7@192.168.2.7

    CSeq: 256 INVITE

    Allow: INVITE, BYE, ACK, OPTIONS, CANCEL

    Proxy-Authorization: Digest username="8888",realm="3CXPhoneSystem",nonce="414d535c01a790b657:a2057df4ff14baa70476e88facc3a607",uri="sip:8888@192.168.2.7",response="ed0c24aeb4757bf56b14e60a09068a54",algorithm=MD5,cnonce="3A0C",opaque="",nc=00000001

    User-Agent: Netbricks-Sip-T.38IAF/2.01 (PRODUCT ID:5, 05 Jul 2007)

    Content-Length: 0
     
  7. sdavies68

    Joined:
    Jan 26, 2010
    Messages:
    21
    Likes Received:
    0
    It seems there is a bug with version 8 (was not there is version 7.1) which if you are using a SIP trunk the problem becomes evident. It amy occur in other situations.

    When making an inbound call (and only inbound), the SIP Ringing message is incorrectly sent to the provider with the internal IP address of the interface in the Contact field rather than the IP address of the STUN or what you manually set.
     
  8. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    You are trying to use unsupported (fax sending) feature to test FAX receiving.
    In general it is not a problem, but your FAX service is configured to send FAXes outside of the local network.
    In this case you need to have smart network gateway which will detect "loopback" and will return traffic back to local network if destination of outgoing packets is its own extenal address.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.