Environment:
- Debian 13 Trixie
- postgresql-18-yeti 1.14.1
- sems 1.192.0 / sems-modules-yeti 1.14.39core192
- yeti-web 1.14.79-1
Problem:
yeti-web 1.14.79 initializes switch22.route_release with 32 arguments:
i_node_id, i_pop_id, i_protocol_id, i_remote_ip, i_remote_port, i_local_ip,
i_local_port, i_from_dsp, i_from_name, i_from_domain, i_from_port, i_to_name,
i_to_domain, i_to_port, i_contact_name, i_contact_domain, i_contact_port,
i_uri_name, i_uri_domain, i_auth_id, i_identity_data, i_interface,
i_x_yeti_auth, i_diversion, i_x_orig_ip, i_x_orig_port, i_x_orig_protocol_id,
i_pai, i_ppi, i_privacy, i_rpid, i_rpid_privacy
sems-modules-yeti 1.14.39 calls route_release with only 22 arguments.
Error: function route_release(…22 args…) does not exist (42883)
I found a post in this forum mentioning adding a headers{} block to sems.conf:
headers {
header(x-yeti-auth)
header(diversion, json, uri_json_array)
…
}
But sems 1.14.39 returns: “no such option ‘headers’” and fails to start.
The sems-yeti GitHub repo ( GitHub - yeti-switch/sems-yeti: YETI application for SEMS core · GitHub )
latest tag is also v1.14.39 — same version, no headers support.
Questions:
- What version of sems-modules-yeti supports the headers{} block in routing?
- Is there a newer binary or branch to compile from?
- Is there a compatible yeti-web version for sems-modules-yeti 1.14.39?