SIP response codes: SIP codes. Email errors: SMTP codes. Provider settings: SIP trunks.
VoIP & telephony
Error reference
The log messages people search for most: No matching endpoint found, Failed to authenticate, Handshake did not complete, login failure and more, with causes and step-by-step fixes.
Asterisk errors
Request 'INVITE' from '<sip:…>' failed for '203.0.113.5:5060' - No matching endpoint foundAsterisk got a SIP request and could not tie it to any configured endpoint, so it rejected it (401 or 403 back to the sender).Request 'REGISTER' from '<sip:101@…>' failed for '198.51.100.7:5060' - Failed to authenticateA device (or someone) tried to register or call with a username that exists but a wrong password.Call from 'trunk' (UDP:203.0.113.5:5060) to extension '74951234567' rejected because extension not found in coThe call reached Asterisk and was matched to an endpoint, but the dialplan context of that endpoint has no extension for the dialled number.Contact 101/sip:101@192.168.1.50:5060;ob is now Unreachable. RTT: 0.000 msecAsterisk sends OPTIONS (qualify) to the device or provider and got no answer, so it considers the contact unreachable and stops sending calls there.No response received from 'sip:sip.provider.com' on registration attempt to 'sip:74951234567@sip.provider.com'Asterisk sends REGISTER to the provider and gets nothing back at all.Fatal response '403' received from 'sip:sip.provider.com' on registration attempt to 'sip:74951234567@sip.provThe provider refused the registration outright, and Asterisk stopped trying.Retransmission timeout reached on transmission 1a2b3c@203.0.113.5 for seqno 102 (Critical Request) -- See httpAsterisk resent a SIP request for 32 seconds and never got a reply: the other side or the path is gone.No joint capabilities for 'audio' media stream between our configuration(alaw) and incoming SDP(ulaw|telephoneThe other side offered codecs, none of which is allowed on this endpoint, so the call fails with 488 Not Acceptable Here.Unable to retrieve PJSIP transport 'transport-udp'An endpoint or registration refers to a transport section that does not exist (or failed to load).
FreeSWITCH errors
mygateway Failed Registration with status Forbidden [403]. failure #3The gateway’s REGISTER was refused by the provider.IP 203.0.113.5 Rejected by acl "domains". Falling back to Digest auth.The source IP is not in the ACL used for IP authentication, so FreeSWITCH asks for a password instead.No route, AbortingThe dialplan context processed the call and no extension matched, so the call is dropped (often with NO_ROUTE_DESTINATION).Can't find user [1000@203.0.113.10] from 198.51.100.7A REGISTER or INVITE came for a user that does not exist in the directory for that domain.Hangup sofia/external/74951234567 [CS_EXCHANGE_MEDIA] [INCOMPATIBLE_DESTINATION]The call ended because the two sides could not agree on media: no common codec or unsupported SDP (Q.850 cause 88, SIP 488).Hangup sofia/internal/101@pbx.example [CS_EXCHANGE_MEDIA] [MEDIA_TIMEOUT]FreeSWITCH stopped receiving RTP from the other side for longer than rtp-timeout-sec and hung up.
MikroTik log messages
login failure for user admin from 198.51.100.7 via sshSomeone tried to log in to the router with a wrong password, here over SSH (also winbox, web, telnet, api).pppoe-out1: terminating... - authentication failedThe PPPoE server of your ISP rejected the username or password.pppoe-out1: terminating... - peer is not respondingThe router sent PPPoE discovery or LCP echo and the ISP side did not answer.ether2: bridge port received packet with own address as source address (64:d1:54:00:00:01), probably loopThe router saw its own frames coming back through a bridge port: there is a loop in the network.dhcp1 offering lease 192.168.88.254 for 00:11:22:33:44:55 without successThe DHCP server offered an address but the client never accepted it.dhcp-client on ether1 lost IP address 203.0.113.25 - received NAK from dhcp server 203.0.113.1The ISP’s DHCP server refused to renew the address, so the router lost internet until it gets a new lease.
WireGuard errors
Handshake for peer 1 (203.0.113.10:51820) did not complete after 5 seconds, retrying (try 2)The client sends handshake initiations to the server and gets no answer.Packet has unallowed src IP (10.0.0.7) from peer 3 (198.51.100.20:43210)A packet came through the tunnel from an address that is not in that peer’s AllowedIPs on this side, so WireGuard dropped it.RTNETLINK answers: Operation not supported / Unable to access interface: Protocol not supportedwg-quick could not create the wg interface: the kernel has no WireGuard support loaded./usr/bin/wg-quick: line 32: resolvconf: command not foundwg-quick tried to apply the DNS = line from the config and the system has no resolvconf.Key is not the correct length or format: `abc…`A PrivateKey, PublicKey or PresharedKey in the config is not a valid 32-byte base64 key.Unable to modify interface: Address already in useThe ListenPort of this interface is already taken by another process or another WireGuard interface.Name or service not known: `vpn.example.com:51820' / Configuration parsing errorwg-quick could not resolve the Endpoint host name when bringing the tunnel up.
Nothing found. Ask the AI engineer.