I don’t think it’s interesting to set the use of failover gateway as mandatory, the provider doesn’t always have a failover gateway, and from the performance point of view, each call will be made twice, which increases the call processing time.
Well it’s just an opinion of course.
I agree on that! It seems like an error in logic since it really does not make very much sense to be mandatory setting.
April 4, 2022, 1:55pm
However, people making calls will want them to complete. The alternative is to use another provider to make sure a call can be made.
Carriers > Trunks having failover gateways configs is optional anyway.
Hello, I don’t think is optional. It will not save the data if a Failover GW Name
#1 is not selected. Please see screenshot of the actual demo on ASTPP website
@koki.roul for clarifying; we are making failover gateway optional, you please log the concern at https://jira.astppbilling.org
I thought it was on purpose, how wonderful then!
Currently, I have fixed this by updating the trunks table
April 7, 2022, 5:43pm
I guess a workaround is to put the same provider in the failover
Yes, but in my tests it tries 2x on the same provider, which is little for a call, but when we talk about a large number of calls, the ideal is to save processing.
April 8, 2022, 2:58am
If you have such a large number f calls, then probably a backup provider would be in your interest in case your sole one does go down for outbound calls.
April 26, 2022, 1:14pm
This issue is resolved in below PR request
Also ref ticket number -