Is It Safe To Configure SIP/Registry Entries On A Passive Asterisk Node ?
Hello,
I’ve seen that Asterisk stores in ASTDB entries like:
/SIP/Registry/spa3102 : 192.168.64.207:5060:
3600:7013:sip:spa3102@192.168.64.207:5060
1. My understanding is that any peer that sent to Asterisk a REGISTER
message has such entry set. So having these entries present avoid for a starting Asterisk the need to way for incoming REGISTER messages which can be as long as 30mn to come in my use case. Is it roughly correct or am I missing something ?
2. When configuring a passive Asterisk node (waiting for an active node to be manually shutdown), is it safe to copy such SIP/Registry entries from one node to another ?
Both active and passive nodes will get Debian’s packaged Asterisk 13.14.1.
3. How is best to set such SIP/Registry entries ?
Using SQLite load command when asterisk is not running and asterisk -rx
“database put SIP/Registry …” when asterisk is running ?
Cheers
One thought on - Is It Safe To Configure SIP/Registry Entries On A Passive Asterisk Node ?
Le 15/11/2017 à 17:30, Olivier a écrit :
I did something like this in the past. We had a cluster of two nodes sharing a virtual IP address. The whole AstDb file was just copied from the active to the passive node, with a protocol like rsync or something similar. It worked well. Then, is it totally safe ? We did not encounter any particular issue during our tests or in our production environments. Still, you may find theoretical edge cases which could be problematic. For example, copying the file is not an atomic operation, so what happens if Asterisk starts but the file has not been entirely copied ?