Intermittent Inbound Issue

Discussion in '3CX Phone System - General' started by Help Desk, Feb 22, 2018.

Thread Status:
Not open for further replies.
  1. Help Desk

    Joined:
    Jan 17, 2017
    Messages:
    11
    Likes Received:
    1
    Hello,

    We're having this strange, intermittent issue happening, usually twice/week, where we can't accept inbound calls. This affects not only our 800#, but our DID's as well.

    I've FINALLY found the fix for it by restarting the SIP Server service (which also restarts the Queue Manager Server and IVR Server along with it), but this only fixes everything for a few days and am looking for a more permanent solution.

    Something to note, I am getting failures on the Firewall check, but we've never made a change to anythin 3CX-related in the firewall in at least two years.

    Below is the output from the Firewall Check:

    •resolving 'stun.3cx.com'... done
    •resolving 'stun2.3cx.com'... done
    •resolving 'stun3.3cx.com'... done
    •resolving 'sip-alg-detector.3cx.com'... done
    •testing 3CX SIP Server... failed (How to resolve?)
    ◦stopping service... done
    ◦detecting SIP ALG... not detected
    ◦testing port 5060... Mapping does not match 5060. Mapping is 13704. (How to resolve?)
    ◦starting service... done

    •testing 3CX Tunneling Proxy... failed (How to resolve?)
    ◦stopping service... done
    ◦testing port 5090... Mapping does not match 5090. Mapping is 13734. (How to resolve?)
    ◦starting service... done

    •testing 3CX Media Server... failed (How to resolve?)
    ◦stopping service... done
    ◦testing ports [9000..9255]... failed (How to resolve?)
    ◾testing port 9000... Mapping does not match 9000. Mapping is 17644. (How to resolve?)
    ◾testing port 9001... Mapping does not match 9001. Mapping is 17645. (How to resolve?)
    ◾testing port 9002... Mapping does not match 9002. Mapping is 17646. (How to resolve?)
    ◾testing port 9003... Mapping does not match 9003. Mapping is 17647. (How to resolve?)
    ◾testing port 9004... Mapping does not match 9004. Mapping is 17648. (How to resolve?)
    ◾testing port 9005... Mapping does not match 9005. Mapping is 17649. (How to resolve?)
    ◾testing port 9006... Mapping does not match 9006. Mapping is 17650. (How to resolve?)
    ◾testing port 9007... Mapping does not match 9007. Mapping is 17651. (How to resolve?)
    ◾testing port 9008... Mapping does not match 9008. Mapping is 17652. (How to resolve?)
    ◾testing port 9009... Mapping does not match 9009. Mapping is 17653. (How to resolve?)
    --- this continues on down to here ---
    ◾testing port 9255... Mapping does not match 9255. Mapping is 17899. (How to resolve?)

    ◦starting service... done


    And if it's failing, then why do the phones work fine until this intermittent thing happens? I could setup a Task Scheduler job that just restarts this daily, in the early morning or something, but would prefer to not band-aid it.


    Thanks in advance.
     
    #1 Help Desk, Feb 22, 2018
    Last edited: Feb 22, 2018
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,284
    Likes Received:
    246
    you say nothing 3cx changed in 2 years- have you changed ISP or routers? Antivirus?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Help Desk

    Joined:
    Jan 17, 2017
    Messages:
    11
    Likes Received:
    1
    ISP: No. Firewall: Yes, upgraded, but same brand so just imported the settings. This was almost a year ago, though, since it was upgraded.

    However, we never did run the Firewall Checker until just now when this started happening.

    It's a Windows 7 box running Microsoft Security Essentials.

    It's just weird the phones all work perfectly fine, regardless of the Firewall Checker results, but the above thing just happens out of nowhere. Not sure if the issue cropped up since we upgraded to SP2 or SP3.

    Note: Additionally, we have a remote office that the phones get their connection/config from this server and those work fine, too, over the Site to Site on port 5060.
     
    #3 Help Desk, Feb 22, 2018
    Last edited: Feb 22, 2018
Thread Status:
Not open for further replies.