Inbound Calls "doesn't match any known extension number"

Discussion in '3CX Phone System - General' started by Robertos, Mar 16, 2018.

  1. Robertos

    Joined:
    Mar 16, 2018
    Messages:
    3
    Likes Received:
    0
    Calling into my a new system v15 on Windows and incoming calls not working..

    For some reason inbound trunk calls from 61444112233 calls ,mapped to my DID on trunk to my extension 109 on Yealink T46S are not working and call fails.

    109 can call out and other internal phones can call him. Tried another phone 106 and same result.

    Any ideas?



    03/16/2018 5:24:05 PM - Leg L:37.1[Line:10000<<61444112233] is terminated: Cause: BYE from PBX
    03/16/2018 5:24:05 PM - [CM503020]: Call(C:37): Normal call termination. Call originator: Line:10000<<61444112233. Reason: Not found
    03/16/2018 5:24:05 PM - [CM503014]: Call(C:37): No known route from Line:10000<<61444112233 to target: <sip:109@0.0.0.0:5060>
    03/16/2018 5:24:05 PM - Call(C:37): from Line:10000<<61444112233 to 109 doesn't match any known extension number.
    03/16/2018 5:24:05 PM - [CM503010]: Call(C:37): Making route(s) from Line:10000<<61444112233 to <sip:109@0.0.0.0:5060>
    03/16/2018 5:24:05 PM - [CM505003]: Provider:[Rabs Maintenance 1300] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] PBX contact: [sip:61299998888@210.8.71.74:5060]
    03/16/2018 5:24:05 PM - [CM500002]: Call(C:37): Info on incoming INVITE from Line:10000<<61444112233:
    Invite-IN Recv Req INVITE from 203.1.8.75:5060 tid=02c183192f39e062 Call-ID=5066-413-21620186246-img06-gsy1-6-59.86.190.106:
    INVITE sip:61299998888@210.8.71.74:1024;rinstance=ead21335421c3bcd;transport=UDP SIP/2.0
    Via: SIP/2.0/UDP 203.1.8.75:5060;branch=z9hG4bK-524287-1---02c183192f39e062;rport=5060
    Via: SIP/2.0/UDP 203.1.8.75:5061;branch=z9hG4bK-xtqmrjs33vdabv2b;rport=5061
    Max-Forwards: 69
    Record-Route: <sip:203.1.8.75:5060;transport=UDP;lr>
    Contact: <sip:203.1.8.75:5061>
    To: <sip:61299998888@203.1.8.75>
     
    #1 Robertos, Mar 16, 2018
    Last edited: Mar 16, 2018
  2. Robertos

    Joined:
    Mar 16, 2018
    Messages:
    3
    Likes Received:
    0
    OK it's working now. Running the FW Check fixed it...

    Don't know how because i restarted server earlier too. A bit buggy ...
     
  3. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    3,525
    Likes Received:
    240
    Hello @Robertos

    Can you tell exactly the build version of the PBX you are running? You can see this on the Dashboard under the Information column next to the licence. This could be related to a known issue that we are currently working on.
     
  4. Robertos

    Joined:
    Mar 16, 2018
    Messages:
    3
    Likes Received:
    0
    hi Yiannis

    Professional Perpetual 15.5.9348.3

    Running on Windows Server 2012 R2
     
  5. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    3,525
    Likes Received:
    240
    Please check your inbox as i have sent you a p.m. with steps necessary to fix your issue.
     
  6. Tim Aitken

    Joined:
    Apr 10, 2018
    Messages:
    3
    Likes Received:
    1
    Hello,

    I have come across this exact same problem and the fix that Robertos used, running the firewall checker, has resolved the problem.

    We have been using 3cx for a number of years and have never come across this before.

    YiannisH_3CX, would you be able to share your secret fix so we don't come across this again.

    Thanks

    Tim
     
  7. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    3,525
    Likes Received:
    240
    Hello @Tim Aitken

    Can you please tell me what PBX version you are running and if its a windows or a linux installation?
    You can see this on the Dashboard under the Information column next to the licence.
     
  8. Tim Aitken

    Joined:
    Apr 10, 2018
    Messages:
    3
    Likes Received:
    1
    Hi Yiannish,

    We are using Version 15.0.62928.5 and it is running on Windows Server 2012 R2.

    Cheers,

    Tim
     
  9. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    3,525
    Likes Received:
    240
    The fix for the issue Robertos was facing is included in the latest service pack release which is version 15.5.10244.4 so i would recommend upgrading to that version to fix your issue
     
  10. Tim Aitken

    Joined:
    Apr 10, 2018
    Messages:
    3
    Likes Received:
    1
    Thanks YiannisH_3CX, that is good to know as we were planning on doing the upgrade.

    Cheers,

    Tim
     
    YiannisH_3CX likes this.