4 Commits (09b589738df7c0d028a93bb4cb83bf17ddaae44a)

Author	SHA1	Message	Date
Kirill Solomko	4554155627	TT#167400 change call forwardings preference to be distinct ... * Call forwardings related internal usr preferences are now distinct per call forward type (maximum 1 record per call forward type, if at least one forwarding for this type exists). This change is meant to address the issue when there are >1000 call forwardings per subscriber, which leads to performance issues. Other components (kamailio) only uses this preference as a boolean to check if there are call forwardings at all per type, therefore, more than one preference, per type, per subscriber is not needed. Change-Id: Iffa475700a74f56eff67400ce9b57092018a14a0	3 years ago
Rene Krenn	2441d05642	TT#81004 fix exports for check CF destinations ... Change-Id: Ia241779d0c1b384f3ca7f6804e5bbcdc462e963a	3 years ago
Rene Krenn	b61d5c9735	TT#81004 fix check CF destination with "timeout" or "priority" vals ... Change-Id: I4757f399baa4f6c804a4c636b722677318189c2d	3 years ago
Rene Krenn	b05628db60	TT#81004 support callforwards in provisioning templates ... provisioning templates can now include configuration of callforward mappings, eg.: cf_mappings: cfu: [] cfb: - enabled: 1 destinationset: name: "test" destinations: - destination: "123" cft: [] cfna: [] cfs: [] cfr: [] cfo: [] Change-Id: I8073322630d63e5ef23e7a9f8c299a6010cb4866	3 years ago