Fax service stops working after a few hours

Discussion in '3CX Phone System - General' started by voiper, Jun 2, 2008.

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

    Joined:
    Mar 24, 2008
    Messages:
    29
    Likes Received:
    0
    Hello,

    the 3CX software runs in the meantime quite smooth. As far I can see all function are working well. I use the following equipment:

    3CX Phone System (Version 5.1.4510.0 and to test Version 6.0.381.0)
    Patton SN4552/2BIS/EUI
    Hardware Version 2.1
    Software Version R4.2 2008-01-17 SIP
    and updated Templates.

    There is a ISDN line connected to the Patton SN4552 for all incoming and outgoing calls. A SIP-Provider also exists (sipgate.de) but is currently not in use.

    I added a DID in the line section for the ISDN-based fax number which is 979899. This DID is specified as "Which calls are faxes - All calls". If there is a (fax-)call, the 3CX system will pick it correctly, but, how strange, immediately hang up (Call::Terminate [CM503008]: Call(81): Call is terminated ).

    Here is a copy from the protocol:

    08:07:25.065 Call::Terminate [CM503008]: Call(7): Call is terminated
    08:07:25.034 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    08:07:25.034 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:anonymous@xxxconnect.ath.cx:5060 to 979817
    08:07:25.034 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    08:07:25.034 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:anonymous@xxxconnect.ath.cx:5060 to 979817
    08:07:25.034 Call::RouteFailed [CM503014]: Call(7): Attempt to reach [sip:888@xxxconnect.ath.cx:5060;user=fax] failed. Reason: Not Registered
    08:07:25.002 Call::RouteFailed [CM503014]: Call(7): Attempt to reach [sip:888@xxxconnect.ath.cx:5060;user=fax] failed. Reason: Not Registered
    08:07:25.002 CallCtrl::eek:nSelectRouteReq [CM503015]: Call(7): Target is not registered:
    08:07:25.002 Line::printEndpointInfo [CM505002]: Gateway:[Patton SN 4552] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4552 2BIS EUI MxSF v3.2.8.45 00a0ba014af7 R4.2 2008-01-17 SIP] Transport: [sip:192.168.100.250:5060]
    08:07:25.002 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    08:07:25.002 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:anonymous@xxxconnect.ath.cx:5060 to 979817
    08:07:24.924 CallCtrl::eek:nIncomingCall [CM503001]: Call(7): Incoming call from anonymous@(Ln.10001@Patton SN 4552) to [sip:888@xxxconnect.ath.cx:5060;user=fax]
    08:07:24.909 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    08:07:24.909 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:anonymous@xxxconnect.ath.cx:5060 to 979817

    18:23:13.710 MediaServerReporting::RTPReceiver [MS105000] C:81.2: No RTP packets were received:remoteAddr=192.168.100.250:10004,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7370
    18:23:13.710 Call::Terminate [CM503008]: Call(81): Call is terminated
    18:23:13.663 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    18:23:13.663 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:xxx6940500@mydomain.ath.cx:5060 to 979899
    18:23:13.663 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    18:23:13.663 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:xxx6940500@mydomain.ath.cx:5060 to 979899
    18:23:13.648 Call::Terminate [CM503008]: Call(81): Call is terminated
    18:23:13.648 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    18:23:13.648 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:xxx6940500@mydomain.ath.cx:5060 to 979899
    18:23:12.398 CallCtrl::eek:nLegConnected [CM503007]: Call(81): Device joined: sip:888@192.168.100.250:5100;user=phone
    18:23:12.398 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    18:23:12.398 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:xxx6940500@mydomain.ath.cx:5060 to 979899
    18:23:12.382 CallCtrl::eek:nLegConnected [CM503007]: Call(81): Device joined: sip:10001@192.168.100.200:5060
    18:23:12.273 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(81): Calling: FaxBox:888@[Dev:sip:888@192.168.100.250:5100;user=phone]
    18:23:12.273 Line::printEndpointInfo [CM505002]: Gateway:[SN4552] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4552 2BIS EUI MxSF v3.2.8.45 00a0ba014af7 R4.2 2008-01-17 SIP] Transport: [sip:192.168.100.250:5060]
    18:23:12.273 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    18:23:12.273 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:xxx6940500@mydomain.ath.cx:5060 to 979899
    18:23:12.210 CallCtrl::eek:nIncomingCall [CM503001]: Call(81): Incoming call from xxx6940500@(Ln.10001@SN4552) to [sip:888@mydomain.ath.cx:5060;user=fax]
    18:23:12.210 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for DID:Fax forwards to Fax:888
    18:23:12.210 LineCfg::getInboundTarget [CM503009]: DID rule (Fax) is applied to call from sip:xxx6940500@mydomain.ath.cx:5060 to 979899

    It's my understanding, that a fax call by the ISDN line should be taken from the Patton SN4552 and processed by the 3CX Software, am I right? Hmmm, but why are all fax calls immediately terminated?

    Strange: This behaviour appears in the Version 5.x as well as in the beta 6.x after a full new install. The 3CX faxservice itself will be NOT terminated. But after a restart of this service, the fax function will work for a certain time (some hours) before it will stop again. The license seems to be properly activated.

    Thanks in advance!
     
  2. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    Thanks for your post.

    We are attempting to reproduce this issue, however at this point without getting the same results.

    We shall keep on running various tests and will get back to you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. einkauf@someware.de

    Joined:
    Jun 16, 2008
    Messages:
    10
    Likes Received:
    0
    Hi,
    we have exactly the same problem... We are using 3CX Version 5.1 withe an Patton SN4638 and are getting the same error message:
    "Attempt to reach [sip:888@xxxconnect.ath.cx:5060;user=fax] failed. Reason: Not Registered"

    Are there any news to this issue?
    Thanks in advance!
    - Tobias.
     
  4. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,939
    Likes Received:
    250
    I suggest upgrading to version 6, this has an improved fax service....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Wompipomp

    Joined:
    Jun 22, 2008
    Messages:
    1
    Likes Received:
    0
    Hi,

    we have the same issue with the same setup as above. (3CX 5.1 and Patton SN 4638)

    Any news? We don´t want to upgrade yet to Version 6 due to RC1.

    Greets
    Wompipomp
     
  6. fgourlaouen

    Joined:
    Sep 17, 2008
    Messages:
    1
    Likes Received:
    0
    Hi,

    We had the same issue about fax reception: "Attempt to reach [sip:xxxxxxxxxxxxxxxxxxxxxx;user=fax] failed. Reason: Not Registered" with the patton 4638 Gateway.

    We have changed the fax configuration in Général Settings (change 888 to 300 for exemple), restart the Fax server service and re-changed the fax configuration (in my example 300 to 888).

    After a final restarting of Fax server service, the reception works well and there are no error message about the registration.

    Bizarre but it's ok for us.
     
  7. Ramona1234

    Joined:
    Oct 18, 2008
    Messages:
    1
    Likes Received:
    0
    Hi guys, machines like PCs, cordless phones and fax machines on standby consume hundreds of megawatts of power. It only takes a couple of seconds for a fax machine or cordless phone to be ready for use when you turn it on. So why don't we have cordless phone base stations and fax machines that consume no power while waiting for an incoming signal, and turn themselves on when one arrives?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.