4 Commits (e2849d47702f3b50f76c97dcf70f83f48d40a6b9)

Author	SHA1	Message	Date
Kirill Solomko	e2849d4770	Revert "MT#61351 change 15783.up to not_replicated" ... This reverts commit 0afdb6cf33. Reason for revert: wrong not_replicated filename Change-Id: Icb12810febed0eaa7940fa374b518ae7566a16e9	6 months ago
Kirill Solomko	0afdb6cf33	MT#61351 change 15783.up to not_replicated ... * reason for this change is because the related changes in the kamailio table get replicated to the active node during the upgrade and that breaks outbound peer provisioning / selection by running kamailio there Change-Id: I69416b5737cf05695cbfd1c2e4544faa8b1a2ab0	6 months ago
Kirill Solomko	12ab0a6618	MT#58547 fix voip_peer_host triggers lcr_rule_target ... * use NEW.id instead of LAST_INSERT_ID() for INSERTs into kamailio.lcr_rule_target as lcr_gw.id is now equal to voip_peer_hosts.id Change-Id: I5d905ddcc15cff2e72b64555a7393ec0c6dfea04	2 years ago
Kirill Solomko	aec9db0018	MT#58547 provisioning<>kamailio.lcr_gw use id instead of flags ... * the relation between provisioning.voip_peer_hosts and kamailio.lcr_gw is now based on id<>id instead of id<>flags. That is to address an issue where code/components that queries kamailio.lcr_gw or related tables like sems_registrations use voip_peer_hosts.id and fail because there is no such record, that also frees up lcr_gw.flags for the intended use to define peereing server attributes and can be used in the future development. * adjust voip_phost_crepl/urepl/drepl triggers that maintain kamailio.lcr_gw table state to INSERT new records into lcr_gw with forced 'id' as NEW.id, use lcr.gw in UPDATE/DELETE and no longer change the lcr_gw.flags column * update kamailio.lcr_gw.id to be equal 'flags' (where flags != 0) * update kamailio.lcr_gw.flags set all to 0 Change-Id: Ied6843ef2aaa7b25af2627797f0d57c75d8f6094	2 years ago