I’m in one step of running Asterisk Realtime.
I’m setting up connection with PostgreSQL via ODBC. Asterisk 1.8.13.
In general, everything works - sip peers are stored in the database. I just wonder if it is normal - when I change the password for my sip-phone in the database, the phone still works well; then I tried to do ‘sip reload’. The phone still works well, even when the ‘sip show users’ showed the new password.
The phone stopped working only after reboot (or , as I think, after re-registration, but I haven’t tried because of much time to wait before it re-registers).
I just compare all these with static text file configuration: when you change peer’s password and do ‘sip reload’, the phone will not work. And now - I have to wait for some time, right ?
ADDED: re-registration haven’t changed anything, the phone still works despite changing the secret in Postgres database. But if I reboot it, it will detect that the passord inside it differs from the password, specified in the database.
All in all, everything is not so bad, but only one thing.
If I need to disable some account, I don’t have an opportunity to do it quickly. I will change a secret in database. I can do ‘sip reload’. But the phone will still work, until being rebooted.
If to compare this with a traditional configuration from text files, it seemes to be not so nice: it’s enough to do ‘sip reload’ after editing sip.conf to quickly disable some phone account.
Does it all mean that I’m mistaken somewhere?