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.

Fax-Server: No rtp Packetes received

Discussion in '3CX Phone System - General' started by sunics, Jun 24, 2015.

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

    Joined:
    Jan 9, 2014
    Messages:
    3
    Likes Received:
    0
    Hello everybody,

    i've a problem with the Fax-Server on the 3cx Phone Systems v12 SP1.
    till two or three days the Fax works normally.
    But now we can't received any fax. On the Settings or Phone Systems nothing would be changed.

    here is the Log:

    24-Jun-2015 07:03:45.687 [MS105000] C:1.2: No RTP packets were received:remoteAddr=127.0.0.1:10002,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7000
    24-Jun-2015 07:03:44.509 Leg L:1.1[Line:10008<<XXXXXXXXX] is terminated: Cause: BYE from PBX
    24-Jun-2015 07:03:44.509 [CM503008]: Call(C:1): Call is terminated
    24-Jun-2015 07:03:44.495 Leg L:1.2[Fax] is terminated: Cause: BYE from 127.0.0.1:5100
    24-Jun-2015 07:03:37.188 Currently active calls - 1: [1]
    24-Jun-2015 07:03:10.321 [CM503007]: Call(C:1): Fax:8888 has joined, contact <sip:8888@127.0.0.1:5100>
    24-Jun-2015 07:03:10.319 [CM503007]: Call(C:1): Line:10008<<XXXXXXXX has joined, contact <sip:XXXXXXXX@business2.voipgateway.org:5060>
    24-Jun-2015 07:03:10.314 L:1.2[Fax] has joined to L:1.1[Line:10008<<0279231818]
    24-Jun-2015 07:03:10.296 [CM503025]: Call(C:1): Calling T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone] for L:1.1[Line:10008<<XXXXXXXX]
    24-Jun-2015 07:03:10.176 [CM503027]: Call(C:1): From: Line:10008<<XXXXXXXX ("XXXXXXXX" <sip:0279231818@xxxx.dyndns.org:5060>) to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone]
    24-Jun-2015 07:03:10.176 [CM503004]: Call(C:1): Route 1: from L:1.1[Line:10008<<XXXXXXXX] to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5100;user=phone]
    24-Jun-2015 07:03:10.175 [CM505003]: Provider:[SipCall - Faxnumber] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] PBX contact: [sip:XXXXX@213.221.231.147:5060]
    24-Jun-2015 07:03:10.173 [CM503001]: Call(C:1): Incoming call from Line:10008<<XXXXXXXX to <sip:1000@192.168.1.13:5060>
    24-Jun-2015 07:03:10.172 Line limit check: Current # of calls for line Lc:10008(@SipCall - Faxnumber[<sip:XXXXX@business2.voipgateway.org:5060>]) is 1; limit is 5
    24-Jun-2015 07:03:09.395 [CM503012]: Inbound specific hours w/o holidays rule (unnamed) for 10008 forwards to Fax:1000


    any ideas or suggestions?
     
  2. cobaltit

    cobaltit Well-Known Member

    Joined:
    Mar 22, 2012
    Messages:
    1,580
    Likes Received:
    237
    I think I only have one customer that uses it, and I have a scheduled task to restart the fax service everyday. Seems to keep that issue under control. Not sure if I had the exact error message as I didn't have time to troubleshoot it.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. sunics

    Joined:
    Jan 9, 2014
    Messages:
    3
    Likes Received:
    0
    Hello

    thanks for your answer. The fax still not works after a restart of the Fax server or the hole Phone System.
     
  4. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    64
    Before you get too involved, you need to update your V12 version to the latest service pack release to the latest 12.5 version. Please review the BLOG for info about the issues involving SHA-1.

    You may want to approach this one step at a time -
    1. Make certain that the fax module is running
    2. Ensure that the provider is using t.38 as this is the only protocol that the fax server media supports. you will need wireshark.
    3. Turn off any software or Windows firewall that may be running (I have had a couple of occasions when a software update to a NIC card or other has caused the firewall to sense a change in the connection and revert to a default or public setting rather than the one I had configured)
    4. Validate that the router coincides with 3CX settings as far as port forwarding of UDP streams. It used to be that the ports used for faxing were different for earlier versions of the product. 3CX changed this to use the same ports as used by the voice streams and it was 9000-9049 as a default and they changed again to widen the range when the webRTC function emerged.
     
Thread Status:
Not open for further replies.