Sip Trunk Weepee

Discussion in '3CX Phone System - General' started by davidm85, Jan 25, 2018.

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

    Joined:
    Jan 15, 2018
    Messages:
    13
    Likes Received:
    0
    Hi,

    I need help configuring my sip trunk.
    I can ping the weepee address from my 3cx server, but when I register a sip trunk in 3cx I can't get connection.

    Error:
    Registration at Weepee has failed. Destination (sip:329909032321@ssw1.brussels.weepee.org:5060) is not reachable, DNS error resolving FQDN, or service is not available.

    Is someone able to help?
    thanks
     
  2. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    519
    Likes Received:
    11
    Did you try ping domain name from 3cx machine, not the IP address,
    C:\>ping ssw1.brussels.weepee.org

    Pinging ssw1.brussels.weepee.org [91.208.12.131] with 32 bytes of data:
    Reply from 91.208.12.131: bytes=32 time=25ms TTL=54
    Reply from 91.208.12.131: bytes=32 time=24ms TTL=54
    Reply from 91.208.12.131: bytes=32 time=25ms TTL=54
     
  3. davidm85

    Joined:
    Jan 15, 2018
    Messages:
    13
    Likes Received:
    0
    yes, and ping was possible without loss
     
  4. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,443
    Likes Received:
    282
    Try an nslookup from the server machine and see if the FQDN resolves correctly. Did you pass the firewall checker of the PBX?
     
  5. davidm85

    Joined:
    Jan 15, 2018
    Messages:
    13
    Likes Received:
    0
    nslookup give the following result.

    Server: router
    Address: 192.168.0.1

    Non-authoritative answer:
    Name: ssw1.brussels.weepee.org
    Address: 91.208.12.131

    The firewall checker within 3cx didn't gave any errors
     
  6. davidm85

    Joined:
    Jan 15, 2018
    Messages:
    13
    Likes Received:
    0
    I've noticed the message has changed to '404 user unknown',
    I will check my credentials
     
  7. davidm85

    Joined:
    Jan 15, 2018
    Messages:
    13
    Likes Received:
    0
    My sip provider informs me that no requests are registered with the sip server. Although I get:

    Call or Registration to Weepee has failed. sip:329909032321@ssw1.brussels.weepee.org:5060 replied: 404 User unknown.; from ...

    now my provider asks a full registration log, where can I find that?
     
  8. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,443
    Likes Received:
    282
    You best bet would be to start a wireshark capture and manually trying to re-register the trunk. Once you do stop the capture, save it and send it to your provider.
     
  9. davidm85

    Joined:
    Jan 15, 2018
    Messages:
    13
    Likes Received:
    0
    I've received an answer from my provider, and they tell me that the destination address is the same then the request address. What could be the reason for this?


    1581 48.952463 192.168.0.200 192.168.0.200 SIP 660 Request: REGISTER sip:ssw1.brussels.weepee.org:5060 (1 binding) |
     
  10. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,443
    Likes Received:
    282
    In order to further troubleshoot your issue we will need to review some configuration files. Please check your inbox as i have sent you a p.m. with details of what we need.
     
  11. davidm85

    Joined:
    Jan 15, 2018
    Messages:
    13
    Likes Received:
    0
    I've had a conversation with one of the 3CX support Team (Thanks for the help), but it seems that I have some kind of loop in the request.

    Does someone know how to resolve this?

    The 3CX is installed on a fresh windows 10 pro computer and I updated my router to a MikroTek hex.


    here is a summary of the capture data:

    After taking a closer look at the new set of files you have sent me i can see something very weird going on. The DNS for Weepee is resolving correctly to IP 91.208.12.131 and the first REGISTER packet is sent to that destination. But then the same packet returns to the PBX from the MAC address the packet was sent to.

    This is the first register message. You can see the packet leaving from IP address 192.168.0.200 which is Dell_e1:e8:10 (your PBX network card as i can see from the files) towards the destination 91.208.12.131 which goes through Routerbo_09:fc:78 (i presume this is the mikrotik).
    [​IMG]

    The next packet is the same packet coming back to the Mac address of the PBX from the mac address of the mikrotik as you can see in the screenshot below. Essentially the packets are in a loop and not reaching the provider. For some reason the Source IP and the destination IP are the same but you can differentiate the sender from the source mac address. And the same procedures continues with the rest of the register messages. [​IMG]
     
Thread Status:
Not open for further replies.