Sending Faxes

Discussion in '3CX Phone System - General' started by ablesoft, May 10, 2010.

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

    Joined:
    Mar 29, 2010
    Messages:
    2
    Likes Received:
    0
    Hello,
    Receiving works fine. Windows Fax & Scan connects to the server. When I try to send a fax, Fax & Scan hits 'Fatal Error' and then it keeps trying to send it. On the server, the Event Log is showing that fax not going and I can confirm that the faxes are residing in the queue folder. Here's what show up in the 3CX Server Log:

    Code:
    13:35:19.679  [CM503008]: Call(515): Call is terminated
    13:35:17.402  [CM503007]: Call(515): Device joined: sip:ablesoftsolutions@66.23.129.253:5060
    13:35:17.402  [CM503007]: Call(515): Device joined: sip:88@172.16.10.83:5100;user=phone
    13:35:17.402  [CM505003]: Provider:[Nexvortex - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:ablesoftsolutions@96.230.135.18:5060]
    13:35:17.402  [CM503002]: Call(515): Alerting sip:ablesoftsolutions@66.23.129.253:5060
    13:35:15.062  [CM503025]: Call(515): Calling VoIPline:18888771655@(Ln.10000@Nexvortex - US)@[Dev:sip:ablesoftsolutions@66.23.129.253:5060]
    13:35:14.999  [CM503004]: Call(515): Route 1: VoIPline:18888771655@(Ln.10000@Nexvortex - US)@[Dev:sip:ablesoftsolutions@66.23.129.253:5060]
    13:35:14.999  [CM503010]: Making route(s) to <sip:18888771655@172.16.10.83:5060;user=phone>
    13:35:14.999  [CM503001]: Call(515): Incoming call from Fax.88 to <sip:18888771655@172.16.10.83:5060;user=phone>
    
    There's also things be written to the 3cxvirtlog.log file in the 3CXFaxServer folder:

    Code:
    13:35:14.812|141C|3CXVirtFax.cpp(85): FaxDevStartJob(), Entered
    13:35:14.812|141C|FSP.cpp(291): FSProv::StartJob(), Job 11 registered
    13:35:14.812|04C8|3CXVirtFax.cpp(101): FaxDevSend(), Entered
    13:35:14.812|04C8|FSP.cpp(359): FSProv::Send(), Fax file: C:\ProgramData\Microsoft\Windows NT\MSFax\Queue\1CAF06F880DC3.FRT
    13:35:14.812|04C8|FaxSender.cpp(446): CProtSocket::SendRequest(), Entered
    13:35:14.812|04C8|FaxSender.cpp(512): CProtSocket::SendReqData_SendFax(), Entered
    13:35:14.812|04C8|FaxSender.cpp(376): CProtSocket::SendPacket(), Sending packet 1
    13:35:14.828|0830|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    13:35:14.828|0830|FaxSender.cpp(657): CProtSocket::RecvData_FaxRequest(), Entered
    13:35:14.828|0830|FaxSender.cpp(667): CProtSocket::RecvData_FaxRequest(), File request: 0
    13:35:18.993|0830|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    13:35:18.993|0830|FaxSender.cpp(675): CProtSocket::RecvData_FaxNotify(), Entered
    13:35:18.993|0830|FaxSender.cpp(690): CProtSocket::RecvData_FaxNotify(), Job 11: Event 0 gotten. Error type: 0
    13:35:18.993|0830|FSP.cpp(70): FaxJob::SetFaxEvent(), Event: 0
    13:35:18.993|0830|FSP.cpp(75): FaxJob::SetFaxEvent(), Fax is being transmitted
    13:35:19.788|0830|FaxSender.cpp(465): CProtSocket::ReadResponse(), Entered
    13:35:19.788|0830|FaxSender.cpp(675): CProtSocket::RecvData_FaxNotify(), Entered
    13:35:19.788|0830|FaxSender.cpp(690): CProtSocket::RecvData_FaxNotify(), Job 11: Event 1 gotten. Error type: 3
    13:35:19.788|0830|FSP.cpp(70): FaxJob::SetFaxEvent(), Event: 1
    13:35:19.788|0830|FSP.cpp(80): FaxJob::SetFaxEvent(), Fax failed
    13:35:19.788|04C8|FSP.cpp(407): FSProv::Send(), Error! Fax to T 18888771655 (Fax Toy<+1 (888) 8771655>) failed: FOIP server reported error
    Fax Toy (18888771655) is the website I'm trying to test with.

    I can also confirm that nexVortex is registering these outbound calls but they are very short. I'm assuming this is because the call is being dropped right away. I have done quite a bit of searching online and haven't been able to come up with anything. I also don't know if this is the client, the fax server, 3cx, or nexVortex that's the problem here with sending faxes.

    Any input is appreciated.
     
  2. support@nexvortex

    Joined:
    Aug 30, 2007
    Messages:
    6
    Likes Received:
    0
    Hello,

    Your calls are not being setup in G.711u before being renegotiated to T.38, so there is no valid audio channel. The call attempts are being initiated with T38 directly which is resulting in the PSTN gateway disconnecting the calls shortly after connection.

    Please update your configuration to initiate call attempts in G.711u and then renegotiate to T.38 for outbound faxing. This is the only way T38 is supported on the nexVortex service when terminating to the PSTN.

    Thanks,
    nV Support
     
  3. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Why negotiation of T38 should require preliminary negotiation of audio channel with G711?
    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. support@nexvortex

    Joined:
    Aug 30, 2007
    Messages:
    6
    Likes Received:
    0
    Because this is how our PSTN gateways are configured. Calls must be setup in G.711u and renegotiated to T.38.

    Thanks,
    nV Support
     
  5. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Hi,

    Does gateway renegotiate "audio" AND "image" media or only "image"?
    What is the condition of renegotiations? Does gateway renegotiate media only in case if "FAX tone" is detected on the line?
    Does gateway renegotiate audio AND image or only image media?
    Can it be enough to offer "audio" AND "image" medias to avoid renegotiations?

    Thanks a lot for information.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.