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.

3CX fax and VOIP Providers

Discussion in '3CX Phone System - General' started by commvisi, May 18, 2011.

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

    Aug 28, 2009
    Likes Received:

    I have been reading FAQ’s etc. and am still confused regarding 3CX Fax with VOIP providers.

    We are currently a licenced v9 customer and I have had attempted allocating one of our VOIP lines to the built in extension 888 Fax Server. If I look at Port/Trunks Status when I call in I can see the destination flash up as 888, but then the call is dropped.

    Does 3CX handle SIP trunks directly to the inbuilt fax server, or do I need some middle ware or physical device to connect the inbound fax, then relay this to 3CX.

    3CX log for my inbound fax call
    09:07:27.466  [CM503008]: Call(17): Call is terminated
    09:07:27.139  Remote SDP is set for legC:17.2
    09:07:25.833  Session 13388 of leg C:17.1 is confirmed
    09:07:25.680  [CM503007]: Call(17): Device joined: sip:888@;user=phone
    09:07:25.674  [CM503007]: Call(17): Device joined: sip:xxxxxxxxx@sipprovider:5060
    09:07:25.673  [MS210007] C:17.1:Answer provided. Connection(by pass mode):
    09:07:25.671  [MS210001] C:17.2:Answer received. RTP connection[unsecure]:
    09:07:25.669  Remote SDP is set for legC:17.2
    09:07:25.669  [CM503002]: Call(17): Alerting sip:888@;user=phone
    09:07:25.607  [CM503025]: Call(17): Calling @[Dev:sip:888@;user=phone]
    09:07:25.606  [MS210006] C:17.2:Offer provided. Connection(by pass mode): x.x.x.x:39898(39899)
    09:07:25.561  [CM503004]: Call(17): Route 1: @[Dev:sip:888@;user=phone]
    09:07:25.560  [CM503010]: Making route(s) to <sip:888@;user=fax>
    09:07:25.560  [MS210000] C:17.1:Offer received. RTP connection: x.x.x.x:39898(39899)
    09:07:25.559  Remote SDP is set for legC:17.1
    09:07:25.559  [CM505003]: Provider:[sip provider] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:xxxxxxxx@x.x.x.x:40691]
    09:07:25.550  [CM503001]: Call(17): Incoming call from xxxxxxxxx@(Ln.10005@sip provider) to <sip:888@;user=fax>
    09:07:25.247  [CM503012]: Inbound office hours rule (unnamed) for 10005 forwards to Fax:888
    09:07:25.245  Looking for inbound target: called=xxxxxxx; caller=xxxxxxx
  2. davidbenwell

    davidbenwell Active Member

    Apr 27, 2010
    Likes Received:
    Hi, 3CX can receive incoming faxes directly, however your VoIP Provider MUST support T.38 for this to work
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. dannybrook

    Feb 24, 2010
    Likes Received:
    I am having the same problem right now with Nexvortex, who is supposed to support T.38 faxing with 3CX.
Thread Status:
Not open for further replies.