The yeti softswitch does not route calls. I’ve completely reinstalled it due to the weak setup previous time to exclude such errors. No errors occurred during the installation (https://yeti-switch.org/docs/en/installation/repositories.html) and configuration (https://yeti-switch.org/docs/en/quick_start.html).
When I run TCP dump I can see a trace come in from our PBX, our PBX also keeps resending it. However, yeti-switch does not respond.
Running a routing simulation results in 2 rows; bottom row provides ‘[0.404 - No routes]’ while the top row shows a correct routing (I can post this if needed?).
Interestingly the CDR history also does not record anything, probably because no response is sent (due to it not being detected?). sems has been started on the only interface at port 5060.
What am I missing here?
22:11:58.561176 IP (tos 0x0, ttl 115, id 18425, offset 0, flags [none], proto UDP (17), length 978)
source.dns.sip > dest.ip.sip: [udp sum ok] SIP, length: 950
INVITE sip:DESTNR@dest.dns:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.2:5060;branch=z9hG4bK-524287-1—a92c23196b330d66;rport
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Supported: replaces, timer