404 not found -- using internal IP address?

I put Asterisk on a digital ocean droplet so that it’s up 24x7. There looks to be a misconfiguration with regards to ip addresses?

What was the 404 “Not Found” unable to find below?

<— SIP read from UDP:<my.external.ip.address>:5060 —>
SIP/2.0 404 Not Found
To: sip:thufir@;tag=470632d69d55b230i0
From: “Anonymous” sip:anonymous@anonymous.invalid;tag=as285c7b45
Call-ID: 3c33e3ac0d9ed3030eb02d397089367a@<<droplet.floating.ip>>:5060
CSeq: 102 INVITE
Via: SIP/2.0/UDP <<droplet.floating.ip>>:5060;branch=z9hG4bK4fff4bef
Server: Linksys/SPA942-6.1.5(a)
Content-Length: 0

full sip trace:


While the peers all show as “ok”, they’re not:

dur*CLI> sip show peers
Name/username             Host                                    Dyn Forcerport ACL Port     Status      Description                      
TELNYX/TELNYX                                                   5060     OK (77 ms)                                   
demo_alice                <my.external.ip>                                             5060     OK (46 ms)                                   
demo_bob                  <my.external.ip>                                             5060     OK (47 ms)                                   
hawat                     <my.external.ip>                                             5060     OK (45 ms)                                   
piter/piter               <my.external.ip>                                             5060     OK (69 ms)                                   
thufir/thufir             <my.external.ip>                                             5060     OK (51 ms)                                   
6 sip peers [Monitored: 6 online, 0 offline Unmonitored: 0 online, 0 offline]

The invite:

INVITE sip:thufir@ SIP/2.0

should be to my external ip, should it not?


First of all, to get any help here, you should describe your design, configuration and issue in a clear way.
Second - the address here might be either internal or external (since no-one knows where the called party resides - in intranet or Internet), but it should be accessible from your Asterisk server.

Third - as you get 404 as a response, it means that the IP is accessible, but the remote system is not properly configured.

Could also mean the local system is not properly configured, or the user mis-keyed.

You seem to be opening multiple threads for the same question, which is one that should easily be answered from standard references, as pointed out in that other thread.

Fair enough.

got it working locally:

Although I’d like to get that also working on a virtual server with digital ocean.