Incoming calls problem

Discussion in '3CX Phone System - General' started by orlandoal, Oct 22, 2012.

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

    Joined:
    Feb 12, 2012
    Messages:
    7
    Likes Received:
    0
    Hi All,

    I seem to be having a problem with incoming calls, in as much as that the line/s ring when a call is coming in but the caller keeps getting ring tone after we have answered the call.

    I am running 3cx on a windows 7 machine, only changes made are the usual windows updates, I have made no changes to the 3cx settings or my router.

    Strange thing is that I can make outgoing calls without any problems.

    The only thing I can see in the logs that might be responsible for the problems are the following:
    15:18:46.080 [MS105000] C:1.1: No RTP packets were received:remoteAddr=147.135.2.240:12092,extAddr=xx.xxx.xx.193:9000,localAddr=xx.xxx.xx.193:9000

    The line above is after I have answered an incoming call and hung up from the phone I was testing from.

    If I do not answer the incoming call but let it go to voicemail, I keep getting the ringtone in the calling handset although the 3cx system has forwarded to voicemail, I get an email with a voicemail attachment which is obviously silence and I get the following from the log file:
    15:27:22.225 [MS105000] C:3.1: No RTP packets were received:remoteAddr=147.135.2.240:12314,extAddr=xx.xxx.xx.193:9004,localAddr=xx.xxx.xx.193:9004
    15:27:21.367 [CM503008]: Call(3): Call is terminated
    15:27:21.364 [CM503021]: Call(3): ACK is not received

    I have rebooted my ISP modem and my router.

    Any pointers or help greatly appreciated as this is driving me nuts.

    Thanks in advance

    Alan
     
  2. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    519
    Likes Received:
    11
    Can you run firewall checker and post the results here? Management Console-Settings-Firewall checker
     
  3. orlandoal

    Joined:
    Feb 12, 2012
    Messages:
    7
    Likes Received:
    0
    Hi mixig,

    Thanks for the prompt reply. Firewall checker results as requested:
    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <16:02:24>: Phase 1, checking servers connection, please wait...
    <16:02:24>: Stun Checker service is reachable. Phase 1 check passed.
    <16:02:24>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <16:02:24>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.

    <16:02:24>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <16:02:24>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.

    <16:02:24>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <16:02:24>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

    <16:02:24>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <16:02:29>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <16:02:29>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <16:02:29>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <16:02:29>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <16:02:29>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <16:02:29>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <16:02:29>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <16:02:29>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <16:02:29>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <16:02:29>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <16:02:29>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <16:02:29>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <16:02:29>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <16:02:29>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <16:02:29>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <16:02:29>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <16:02:29>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <16:02:29>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <16:02:29>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <16:02:29>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <16:02:29>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <16:02:29>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <16:02:29>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <16:02:29>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <16:02:29>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <16:02:29>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <16:02:29>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <16:02:29>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <16:02:29>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <16:02:29>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <16:02:29>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <16:02:29>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <16:02:29>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <16:02:29>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <16:02:29>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <16:02:29>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
    <16:02:29>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
    <16:02:29>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
    <16:02:29>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
    <16:02:29>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
    <16:02:29>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
    <16:02:29>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
    <16:02:29>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
    <16:02:29>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
    <16:02:29>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
    <16:02:29>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
    <16:02:29>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
    <16:02:29>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
    <16:02:29>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
    <16:02:29>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.


    Application exit code is 0
     
  4. 3CXfoxhallsolutions

    3CXfoxhallsolutions New Member

    Joined:
    Sep 8, 2012
    Messages:
    211
    Likes Received:
    0
    What kind of lines / gateway are you terminating on 3CX???
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. orlandoal

    Joined:
    Feb 12, 2012
    Messages:
    7
    Likes Received:
    0
    OK this is where you guys give me a kick in LOL. I am using Broadvoice lines I have two of them and they have worked perfectly up until a couple of days ago.

    So lines are configured directly in VOIP Providors section, using Broadvoices SIP details that are attached to my account.

    As I say I can make outgoing calls without any issues.

    When I have had RTP packet issues in the past I have normally cleared it by rebooting my modem & router.
     
  6. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    Are you using Stun? Do you have a fixed ip? If fixed, try turning off stun. If no success, then try PBX provides voice along with re-invite.
     
  7. orlandoal

    Joined:
    Feb 12, 2012
    Messages:
    7
    Likes Received:
    0
    I am not using stun, that is off, I do not have a fixed IP and I am already using PBX provides Audio and supports re-invite

    Been doing a bit more testing and I also have a UK line, which if I call from my cell phone I can answer and has a both ways transmission path.

    So it looks like this may well be a Broadvoice issue rather than anything on the 3cx software.
     
  8. orlandoal

    Joined:
    Feb 12, 2012
    Messages:
    7
    Likes Received:
    0
    Re: Incoming calls problem - RESOLVED

    Hi Guy's,

    Thanks for the feedback from those that replied.

    It seems that there was an issue with Broadvoices proxy. I had really good support from Broadvoices second line tech support who managed to help resolve my problem.

    For those that use Broadvoice there are a bunch of proxy servers which I am posting below just in case Broadvoice users are not aware of them. The proxy I was having issues with is in RED.

    proxy.lax.broadvoice.com
    proxy.dca.broadvoice.com
    proxy.mia.broadvoice.com
    proxy.atl.broadvoice.com
    proxy.chi.broadvoice.com
    proxy.bos.broadvoice.com
    proxy.nyc.broadvoice.com

    Cheers
     
  9. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    You indicated that you do not have a fixed IP. If all is working OK as it seems to be now, then I guess you may be fine, but you may need to enable STUN in order to better accommodate changing IP down the road. In any event, glad you got it sorted out.
     
  10. orlandoal

    Joined:
    Feb 12, 2012
    Messages:
    7
    Likes Received:
    0
    Ineblett,

    Sorry the local stun server is turned off as I have no fixed IP, but I am using the stun.3cx.com servers.

    Apologies for the confusion, I bet you were scratching your head a little there. :oops:
     
Thread Status:
Not open for further replies.