When creating Grandstream FXS “physical” extensions using the cleartext template, the rest_devices_phones.srtp field is stored as NULL. It should be 0 for cleartext and 1 for TLS. Toggling SRTP/TLS in the UI (disable/enable) fixes the value afterwards.
Steps to reproduce
- Configure a Grandstream FXS from the wizard / create a “physical” device using the cleartext template.
- Query the database for the created record in
rest_devices_phones.
- Observe the
srtp column value.
- In the UI, toggle encryption (disable/enable) for the same extension.
- Query the database again and observe the corrected
srtp value.
Expected behavior
- For cleartext template:
rest_devices_phones.srtp is set to 0.
- For TLS template:
rest_devices_phones.srtp is set to 1.
Actual behavior
When creating Grandstream FXS “physical” extensions using the cleartext template, the
rest_devices_phones.srtpfield is stored asNULL. It should be0for cleartext and1for TLS. Toggling SRTP/TLS in the UI (disable/enable) fixes the value afterwards.Steps to reproduce
rest_devices_phones.srtpcolumn value.srtpvalue.Expected behavior
rest_devices_phones.srtpis set to0.rest_devices_phones.srtpis set to1.Actual behavior
For cleartext template,
rest_devices_phones.srtpis sometimesNULLat creation time (then becomes correct after toggling in the UI).This can break logic relying on
srtp = 0filters, e.g.:Example (sanitized):
See also: [Extensions created for Grandstream FXS are created without encryption · Issue #7602](Extensions created for Grandstream FXS are created without encryption #7602)