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.

Incoming/Outgoing Fax - M-ATA/Broadvox

Discussion in '3CX Phone System - General' started by brianoakes, Aug 30, 2012.

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

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    Howdy Everyone,

    I know this has been addresses before, and frankly I have probably read all of the posts. However I can't seem to get this issue resolved. We have multiple MFC copiers (the big ones) and the users use them to send/recieve faxes. In this case, we simply want to use the Patton M-ATA as our device to connect it to the PBX for send/recieve purposes. At this point I have tried just about every config option I can think of, and saw as a suggestion but for whatever reason I still can't get it to work. Now, incoming seems to work decent, however outgoing, I usually get a business signal but that can change.

    Would it be possible for someone to post all of their suggestions on how they have it work. I would apprecaite the help!

    I would like to know the whole/end set of settings. My users are getting pissy, I am running out of options. :) Thanks!
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    65
    If you are getting a busy signal then that more likely indicates a problem in how the outbound rule is setup. It could be that the call is making it to the carrier and the carrier is providing the busy signal as an indication that it does not understand your dial string. Are users inputting a 9, for instance, and perhaps that is not getting stripped? Can you post a log of an attempted send fax?
     
  3. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    Working on getting a log. Thanks for the help!

    Right now, we have no outbound rule other use the GoAnywhere trunk. In the case of me testing, I was simply dialing the an 888 # and a 817 (local) #. If I dial the same # from a phone (polycom, another extension) it connects and starts tones. If I do the same thing from the fax plugged into the m-ata. I hear rings, then it goes to busy.
     
  4. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    Here is the log. It was my last test, last night. From the fax machine, I dialed 8883169121 just like that. It connected, then went busy. I didn't scrub the data for IPs so... hopefully I am not giving away the farm :)

    30-08-2012 02:16:21.298 L:2070.1[Extn]: Terminating targets, reason:
    30-08-2012 02:16:21.297 Leg L:2070.1[Extn] is terminated: Cause: 200 BYE from PBX
    30-08-2012 02:16:21.297 L:2070.1[Extn] Sending: OnSendReq Send Req BYE from 0.0.0.0:0 tid=a05d100b695e0b15 Call-ID=NTWHG-l8htF0f2@192.168.20.12:
    BYE sip:7201@192.168.20.56:5060 SIP/2.0
    Via: SIP/2.0/ ;branch=z9hG4bK-d8754z-a05d100b695e0b15-1---d8754z-;rport
    Max-Forwards: 70
    Contact: <sip:8883169121@192.168.20.12:5060>
    To: "4698927201"<sip:7201@192.168.20.12>;tag=dkMf2-EIvNE
    From: <sip:8883169121@192.168.20.12>;tag=9656cc51
    Call-ID: NTWHG-l8htF0f2@192.168.20.12
    CSeq: 2 BYE
    Content-Length: 0
    30-08-2012 02:16:21.297 L:2070.1[Extn]: Terminating targets, reason: SIP ;cause=200 ;text="Call terminated on user request"
    30-08-2012 02:15:47.552 Answer to offerer immediateily, other party (L:2070.1[Extn]) doesn't support re-invite
    30-08-2012 02:15:45.184 L:2070.1[Extn] Sending: OnSendResp Send 200/INVITE from 0.0.0.0:0 tid=xU1f2-WEuDQCL Call-ID=NTWHG-l8htF0f2@192.168.20.12:
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.20.56:5060;branch=z9hG4bKxU1f2-WEuDQCL
    Contact: <sip:8883169121@192.168.20.12:5060>
    To: <sip:8883169121@192.168.20.12>;tag=9656cc51
    From: "4698927201"<sip:7201@192.168.20.12>;tag=dkMf2-EIvNE
    Call-ID: NTWHG-l8htF0f2@192.168.20.12
    CSeq: 27 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    User-Agent: 3CXPhoneSystem 11.0.25940.0
    Content-Length: 267

    v=0
    o=3cxPS 64323846144 73165438978 IN IP4 192.168.20.12
    s=3cxPS Audio call
    c=IN IP4 192.168.20.12
    t=0 0
    m=image 0 udptl t38
    a=T38FaxVersion:0
    a=T38MaxBitRate:14400
    a=T38FaxMaxBuffer:400
    a=T38FaxUdpEc:t38UDPRedundancy
    a=T38FaxRateManagement:transferredTCF
    30-08-2012 02:15:45.182 Reneg. from L:2070.1[Extn], offer
    30-08-2012 02:15:45.182 Leg L:2070.1[Extn] raised event RecvdRemoteSdp
    30-08-2012 02:15:45.182 Remote SDP is set for leg L:2070.1[Extn]
    30-08-2012 02:15:44.795 Session 130740 of leg L:2070.1[Extn] is confirmed
    30-08-2012 02:15:44.795 L:2070.1[Extn] got Confirmed Confirmed Recv Req ACK from 192.168.20.56:5060 tid=xU1f2-EWunu0ldQ Call-ID=NTWHG-l8htF0f2@192.168.20.12:
    ACK sip:8883169121@192.168.20.12:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.20.56:5060;branch=z9hG4bKxU1f2-EWunu0ldQ
    Max-Forwards: 70
    Contact: "4698927201"<sip:7201@192.168.20.56:5060>
    To: <sip:8883169121@192.168.20.12>;tag=9656cc51
    From: "4698927201"<sip:7201@192.168.20.12>;tag=dkMf2-EIvNE
    Call-ID: NTWHG-l8htF0f2@192.168.20.12
    CSeq: 25 ACK
    User-Agent: Myson Century/VR4.2 Nov 2 2009
    Content-Length: 0
    30-08-2012 02:15:44.597 [CM503007]: Call(C:2070): Extn:7201 has joined, contact <sip:7201@192.168.20.56:5060>
    30-08-2012 02:15:44.596 Session 130740 of leg L:2070.1[Extn] is connected
    30-08-2012 02:15:44.596 L:2070.1[Extn] got Connected Connected Send 200/INVITE from 0.0.0.0:0 tid=xU1f2-bBJC607rL Call-ID=NTWHG-l8htF0f2@192.168.20.12:
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.20.56:5060;branch=z9hG4bKxU1f2-bBJC607rL
    Contact: <sip:8883169121@192.168.20.12:5060>
    To: <sip:8883169121@192.168.20.12>;tag=9656cc51
    From: "4698927201"<sip:7201@192.168.20.12>;tag=dkMf2-EIvNE
    Call-ID: NTWHG-l8htF0f2@192.168.20.12
    CSeq: 25 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    User-Agent: 3CXPhoneSystem 11.0.25940.0
    Content-Length: 279

    v=0
    o=3cxPS 64323846144 73165438977 IN IP4 192.168.20.12
    s=3cxPS Audio call
    c=IN IP4 192.168.20.12
    t=0 0
    m=audio 7040 RTP/AVP 18 0 8 13 96
    a=rtpmap:18 G729/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:96 telephone-event/8000
    a=sendrecv
    30-08-2012 02:15:44.596 L:2070.1[Extn] Sending: OnSendResp Send 200/INVITE from 0.0.0.0:0 tid=xU1f2-bBJC607rL Call-ID=NTWHG-l8htF0f2@192.168.20.12:
    SIP/2.0 200 OK
    Via: SIP/2.0/UDP 192.168.20.56:5060;branch=z9hG4bKxU1f2-bBJC607rL
    Contact: <sip:8883169121@192.168.20.12:5060>
    To: <sip:8883169121@192.168.20.12>;tag=9656cc51
    From: "4698927201"<sip:7201@192.168.20.12>;tag=dkMf2-EIvNE
    Call-ID: NTWHG-l8htF0f2@192.168.20.12
    CSeq: 25 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Content-Type: application/sdp
    Supported: replaces
    Content-Length: 279

    v=0
    o=3cxPS 64323846144 73165438977 IN IP4 192.168.20.12
    s=3cxPS Audio call
    c=IN IP4 192.168.20.12
    t=0 0
    m=audio 7040 RTP/AVP 18 0 8 13 96
    a=rtpmap:18 G729/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:96 telephone-event/8000
    a=sendrecv
    30-08-2012 02:15:44.596 L:2070.1[Extn]: Terminating targets, reason: SIP ;cause=200 ;text="Call completed elsewhere"
    30-08-2012 02:15:44.505 L:2070.1[Extn] Sending: OnSendResp Send 183/INVITE from 0.0.0.0:0 tid=xU1f2-bBJC607rL Call-ID=NTWHG-l8htF0f2@192.168.20.12:
    SIP/2.0 183 Session Progress
    Via: SIP/2.0/UDP 192.168.20.56:5060;branch=z9hG4bKxU1f2-bBJC607rL
    Contact: <sip:8883169121@192.168.20.12>
    To: <sip:8883169121@192.168.20.12>;tag=9656cc51
    From: "4698927201"<sip:7201@192.168.20.12>;tag=dkMf2-EIvNE
    Call-ID: NTWHG-l8htF0f2@192.168.20.12
    CSeq: 25 INVITE
    Content-Type: application/sdp
    Content-Length: 279

    v=0
    o=3cxPS 64323846144 73165438977 IN IP4 192.168.20.12
    s=3cxPS Audio call
    c=IN IP4 192.168.20.12
    t=0 0
    m=audio 7040 RTP/AVP 18 0 8 13 96
    a=rtpmap:18 G729/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:96 telephone-event/8000
    a=sendrecv
    30-08-2012 02:15:41.810 [Flow] Call(C:2070): making call from L:2070.1[Extn] to T:Line:10003>>8883169121@[Dev:sip:4692423742@dl01-05.fs.broadvox.net:5060]
    30-08-2012 02:15:41.810 [CM503027]: Call(C:2070): From: Extn:7201 ("4698927201" <sip:7201@192.168.20.12:5060>) to T:Line:10003>>8883169121@[Dev:sip:4692423742@dl01-05.fs.broadvox.net:5060]
    30-08-2012 02:15:41.810 [Flow] Call(C:2070): making call from L:2070.1[Extn] to T:Line:10003>>8883169121@[Dev:sip:4692423742@dl01-05.fs.broadvox.net:5060]
    30-08-2012 02:15:41.810 [CM503027]: Call(C:2070): From: Extn:7201 ("4698927201" <sip:7201@192.168.20.12:5060>) to T:Line:10003>>8883169121@[Dev:sip:4692423742@dl01-05.fs.broadvox.net:5060]
    30-08-2012 02:15:41.810 [Flow] Call(C:2070): making call from L:2070.1[Extn] to T:Line:10003>>8883169121@[Dev:sip:4692423742@dl01-05.fs.broadvox.net:5060]
    30-08-2012 02:15:41.810 [CM503027]: Call(C:2070): From: Extn:7201 ("4698927201" <sip:7201@192.168.20.12:5060>) to T:Line:10003>>8883169121@[Dev:sip:4692423742@dl01-05.fs.broadvox.net:5060]
    30-08-2012 02:15:41.810 [CM503010]: Call(C:2070): Making route(s) from Extn:7201 to <sip:8883169121@192.168.20.12:5060>
    30-08-2012 02:15:41.810 Remote SDP is set for leg L:2070.1[Extn]
    30-08-2012 02:15:41.810 [CM505001]: Endpoint Extn:7201: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Myson Century/VR4.2 Nov 2 2009] PBX contact: [sip:7201@192.168.20.12:5060]
    30-08-2012 02:15:41.809 [CM500002]: Call(C:2070): Info on incoming INVITE from Extn:7201:
    Invite-IN Recv Req INVITE from 192.168.20.56:5060 tid=xU1f2-bBJC607rL Call-ID=NTWHG-l8htF0f2@192.168.20.12:
    INVITE sip:8883169121@192.168.20.12 SIP/2.0
    Via: SIP/2.0/UDP 192.168.20.56:5060;branch=z9hG4bKxU1f2-bBJC607rL
    Max-Forwards: 70
    Contact: "4698927201"<sip:7201@192.168.20.56:5060>
    To: <sip:8883169121@192.168.20.12>
    From: "4698927201"<sip:7201@192.168.20.12>;tag=dkMf2-EIvNE
    Call-ID: NTWHG-l8htF0f2@192.168.20.12
    CSeq: 25 INVITE
    Allow: INVITE, BYE, CANCEL, OPTIONS, PRACK, NOTIFY, UPDATE, REFER
    Content-Type: application/sdp
    Proxy-Authorization: Digest username="7201",realm="3CXPhoneSystem",uri="sip:8883169121@192.168.20.12",response="327ee6d89adca1be5ecd26f8e8fc2bec",algorithm=MD5,nonce="414d535c064fa41d67:a1a5cd2923db18ae6ea777ff46c045dd"
    Supported: timer, replaces
    User-Agent: Myson Century/VR4.2 Nov 2 2009
    Content-Length: 247

    v=0
    o=7201 15568 1 IN IP4 192.168.20.56
    s=-
    c=IN IP4 192.168.20.56
    t=0 0
    m=audio 8002 RTP/AVP 18 0 8 96 13
    a=rtpmap:18 G729/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:96 telephone-event/8000
    a=rtpmap:13 CN/8000
    a=ptime:10
    30-08-2012 02:15:41.808 [CM503001]: Call(C:2070): Incoming call from Extn:7201 to <sip:8883169121@192.168.20.12:5060>
     
  5. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    65
    A few things to try.

    Take a look at the codec settings. Reorder them all (ATA if available) as well as the extensions for the fax to use G711U, G771A and then G729.

    I am not certain that dialing from one internal phone extension to another internal extension with a fax is a viable test due to the media negotiation that takes place. You will be better served to use an external fax machine connected to a PTSN line to do both in-bound and outbound test faxing to one of you machines.

    I don't believe that you can effectively/reliably use 888, which is the default 3CX fax server number. In most cases that I have heard about, people are setting up the fax as a normal phone extension and letting their ATA handle the negotiation as the DID is directed to the extension of interest. This also implies that the 3CX fax server should be turned off. 3CX really only supports inbound fax receiving through their fax server module. They do not support fax sending. Several have reported success using the above described scenario, more or less, but to varying degrees. Many have never been successful. It the ATA supports T38 you may need to try the setting both off and on. You may also need to turn off PBX provides audio on the extension and then you may also need to turn on supports re-invites. These will be the more critical settings and again use an external fax to do testing as you know that at least one end of the line is a known working unit without having to worrying about changing the setting on two machines at the same time.
     
  6. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    Just to clarify:

    7201 is a normal extension. Not a Fax extension.
    Phone Provisioning: Cisco SPA - There is no Patton M-ATA (that is what I am running)
    Preferred Codec G711u
    Sec Codec: G711a
    Third Codec: G722a
    PBX Delivers Audio: Checked
    Supports Re-Invite: UnChecked
    Inbound Route for 469-892-7201 --> Exterion 7201

    Inside the Patton M-ATA here is what I have set.

    RTP Telephon Event Config:
    Send DTMF Events: In-Band & OOB
    RFC2833 Signalling using payload value: 96
    Regenerate OOB DMTF Tone: Checked
    G711u - Silence Supression - Off - Preferred Codec
    G711a - Silence Supression - Off
    G729 - Silence Supression - Off

    FAX without T.38 (Use G.711 fax) - Checked

    The action was to from the fax machine, dial the 8883169121 number since that is an efax I know is online as an outbound call. Inbound to 469-892-7201 appears to work.

    We run a 4 digit extension system, so our default fax is 8888 but we don't use any of the fax services. We got the Patton M-ATAs so we could plug in a fax and be done with it.

    We are using Broadvox as our provider. The question is really, where to start looking on this one. I "think" I have it all configured correctly... or I am missing a big elephant in the room. :) Appreciate the help!
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,126
    Likes Received:
    330
    So...you have T.38 turned on, or off?

    Without T.38 being supported, at least until it leaves a VoIP provider and is converted back to analogue, you may be out of luck.

    Some have tried running 2400 bps modems over G711 with unfavourable results, and fax machines tend to want to send at a higher speed than that.

    What you might try, if possible, just for a test, is register the ATA you are using , directly with your VoIP provider, if that doesn't work, then you have no hope of getting it to work through 3CX.

    If it does work, then at least, you may not be wasting your time in continuing.

    Over the next couple of months I am going to be attempting to run my fax machine through 3CX, to see how it goes. If it doesn't, then it will be connected directly to a PSTN line.
     
  8. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    T.38 is turned off. The logic was that we just wanted to convert it to as plain jane fax as possible. Speed, who cares it's a fax. :) (well that's my logic).

    Think we might have an issue at Broadvox or something I need to tell them toi turn on/off. According to the site, they support with/without T.38 so I was hoping it wouldn't make a differnece.

    In our case, we have NO option for PSTN lines :( hence, I why i am loosing sleep futzing around with it.
     
  9. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,126
    Likes Received:
    330
    If it will work using G711 (and I see that it is a fall-back for Broadvox), then great, however, I think you will probably have better luck (more reliable service) enabling T.38 as it was developed to "get around" the "issues" that fax machines can create.
     
  10. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    I have enabled T.38 inside the M-ATA, and the same behavior. Incoming appears to be ok. Dialing out, same issue it appears to connect, then I hear a busy signal.

    I will pull a log in a sec and see if it looks the same. Kinda perplexed on this one. Doesn't make sense.
     
  11. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    65
    Turn re-invites on.
     
  12. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    Howdy Guys,

    i am still hving the same problem. I need to get faxes working through 3CX to Broadvox for Incoming/Outgoing. I am running 3CX 11sp1, and Broadvox has indicated they have made changes on their end to resolve issues. I have tried Patton M-ATAs and Cisco SPA-3102's and they both behave the same. I just need incoming/outgoing for a few fax machines. I am out doing T.38 or Not. To me is doesn't matter.

    Did anyone ever get this working through Broadvox?

    -BrianO
     
  13. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    I have two locations using Broadvox and SPA 112 with no issues now, though I have had issues with faxing and Broadvox in the past. I do know there were some issues with Broadvox and T-38 though that bug was supposed to have been fixed a few months ago, have you reached out to Patton for assistance as of yet?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    Nope I haven't had the chance to call Patton. It's just frustrating because no one can say for sure use x/y and it will work. We are going to try GXW4004 on the recomendation of 3CX support. So we'll see if they work. :(
     
  15. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    If I were you before I purchased that Grandstream I'd highly urge you to contacts Patton support they are very good, and very helpful.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. brianoakes

    Joined:
    May 12, 2012
    Messages:
    95
    Likes Received:
    0
    Will do. I have the SPA 3102 and the Patton M-ATA and I captured netowrk traces, for Broadvox. Supposesly they were captuing at the same time. Tomorrow we will check into it and see.

    If anyone has any pointers/sugeestions on how to make this work, I'd appreciate. Once the faxes are resolved then we can finally 100% our old phone company. :)
     
Thread Status:
Not open for further replies.