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.

No Incoming Calls

Discussion in '3CX Phone System - General' started by BeagleBen, Nov 2, 2010.

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

    Joined:
    Nov 2, 2010
    Messages:
    4
    Likes Received:
    0
    We have 3 SIP Accounts with the same provider, one account can receive calls fine, the other 2 cannot the is a long pause and the a dead tone, can anyone help.
    We can dial out on all lines but can only receive incoming calls on one

    Beagle
     
  2. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    http://www.3cx.com/forums/forum-rules-read-to-get-answers-93.html

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. BeagleBen

    Joined:
    Nov 2, 2010
    Messages:
    4
    Likes Received:
    0
    Thanks

    our sip provider is voip-unlimited, we are behind a draytek vigor 2950 router with correct port forwarding, the logs don't show the incoming calls getting to the pbx because there are no errors so my guess its a firewall problem, but one sip account works fine so stumped here.
    When we move back to our asterix pbx all is well

    Beagle
     
  4. DXS_Matt

    Joined:
    Feb 12, 2009
    Messages:
    41
    Likes Received:
    0
    You've run the firewall checker and have no issues there?
     
  5. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    The log of PBX reflects all incoming requests.
    Do you have any ideas why nothing is coming to PBX host?

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. BeagleBen

    Joined:
    Nov 2, 2010
    Messages:
    4
    Likes Received:
    0
    It is very bizarre, one sip channel works fine, the other 2 dont, the sip provider could not sending invites out to our ip address but did not get any response, will try on a different 3CX pbx
     
  7. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    The definition "It is very bizarre" is "very soft"...
    The request doesn't reach the destination. Why can it happen?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. BeagleBen

    Joined:
    Nov 2, 2010
    Messages:
    4
    Likes Received:
    0
    Just tried on a different PBX running XP rather than 7, still no incoming,

    firewall ports are
    5060 tcp / udp
    5090 tcp / udp
    9000 -9049 udp
    10000 udp
     
  9. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    As far as one of the accounts receives calls, the firewall should not be the problem.
    Are you sure that other two accounts are not used(registered) from somewhere else? (another PBX, soft phone etc.)
    Try to refresh registration of accounts which are not receive incoming calls (button "Refresh registration" is on the top of page which shows the list of VoIP providers). Check PBX log. It should say that the account is registered successfully.
    Then try to make incoming calls to all three accounts. Do they start to receive incoming calls?

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    How are you connected to the internet?

    Single ip address? If so can your provider handle multiple registrations on the same port from the same ip or are they overwriting each other on their system and kicking off the other registrations?

    If you look at the logs is it the first (or last) registration that is successfully getting the calls?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. jjd

    jjd

    Joined:
    Jun 27, 2010
    Messages:
    3
    Likes Received:
    0
    Hi Guys,

    We are seeing similar at site.

    We are running latest Version: 9 sp3 with all patches applied on a SBS2003 SP2 machine.

    All ports are correctly forwarded to pbx.

    UDP 5060 is directly NATTED to PBX ip address using NATP
    UDP 9000-9049 is directly NATTED to PBX ip address NATP.

    Outbound calls work fine with all SIP and RTP traffic routing correctly.
    RTP heads out from port 7102 -->

    However inbound calls fail to arrive.

    We can see on wireshark sip part of calls incoming from VOIP provider.

    2010-11-09 11:54:55.034263 195.189.173.10 192.168.1.254 SIP/SDP Request: INVITE sip:30146115@188.223.85.148:5060, with session description

    But no response coming back from PBX. We have found on occasion that a pbx restart clears the issue and all works ok.
    We only know when it stops working because our VOIP provider forwards us a voicemail, and when we go onto the PBX it starts to show the same INVITE and nothing else.

    When we get it to work again we see:-
    7 2010-11-09 11:54:55.135020 192.168.1.254 195.189.173.10 SIP Status: 100 Trying
    Coming back from the PBX and then:-
    8 2010-11-09 11:54:55.236231 192.168.1.254 192.168.1.19 SIP/SDP Request: INVITE sip:11@192.168.1.19:1024;line=quex4i6f, with session description

    Our extensions get called and all is ok.

    On appearance the PBX when not working does not listen or have any UDP endpoints open on the 9000-9049 ports.

    UDP 0.0.0.0:8936 *:*
    UDP 0.0.0.0:8958 *:*
    UDP 0.0.0.0:9051 *:*

    UDP 0.0.0.0:9111 *:*

    Surely this is not correct and would appear to be the issue?

    I have a capture of the logs if anyone could shed some light as where to hunt next.

    Thanks
    Best Regards
    Joe.
     
Thread Status:
Not open for further replies.