Http SMS Gateway not triggered

Question
1

Hello fellow PI-Community

I just started with PI, installed the latest Version 3.11.4 on a Debian Bookworm with python/venv.
I created some policies in the webui and setup our SMS-Gateway. The LDAP-Resolver is also set and works, I can see all users from AD. Then I created a SMS-Token for my AD-User but when I login with my AD-User to PI-webui no SMS is being triggered/send and I just get logged in normally with AD-PW.

Am I misunderstanding a concept here or what might be the issue? Manually firing a curl POST from PI-Server to our smsgw works. The pi-log is crazy flooded with policies output and is hard to read/track. But grepping for any sms gateway / identifier / provider related stuff does not give me a hint what is wrong. I can see that the sms.identifier matches my SMS Gateway I created in webui. I even recreated the SMS GW but didn’t work.

sms_token
sms_token1725×1321 148 KB

sms_token_settings
sms_token_settings2649×990 154 KB

policies
policies2024×694 79.8 KB

ldap_resolver_mappings
ldap_resolver_mappings1967×773 45.3 KB

sms_gw_1
sms_gw_12007×1396 147 KB

sms_gw_2
sms_gw_21879×1375 124 KB

Thanks in advance for helping.
Best Regards

2

After further testing and running curl POSTs against REST Api /validate/check I have found what the problem was. My SMSGW in webui was misconfigured. I had to remove User/Pw and switch to Header Token (in the options below).

curl -k -X POST "https://your-pi-server/validate/check"   -d "user=ad_user"   -d "pass=xxxxxxx"

Also my RETURN_SUCCESS was wrong.
My SMS gateway returns an HTTP 200, but the body of the JSON response is actually:
“state”:“waiting” so thats also the correct value I had to place in webui.

I wanted to test the SMSGW by activating it on webui logins, but this is not needed anymore.

Therefore topic CLOSED!