Solved Bridge stay disconnected

[AWS2P]

Hi
From 2 PBxs in latest V18 , one on OVH cloud (master side) , second on premise (fiber ). I have a bridge running since years and tonight connection is lost and it's impossible to have it up.

Nothing changed on both side, FQDN are the same and public IP too. No blacklisted IP on both side. In bridge settings pbx were set with public IP, I try to switch to FQDN on both side with no more connection.

What do you advice me to check ?

 

[Evolute IT]

Check the activity log to make sure nothing changed.

 

[AWS2P]

Well, explaination is found now and problem fixed, customer moved to another location without letting me know , so Public IP has changed on ISP side and then everything went down, because there's also a security on SIP provider allowing only registred IP set on their console to register the trunk.
For the bridge it was a problem with public IP's and also the new range of ports affected by ISP was not full, but only 25% so 5090 was no more in the range, so I needed to change to a full stack on ISP portal to retrieve full range of port and this caused a public IP change again.
So now all is stable, I switched also from IPs in bridge settings to FQDN.

This can be set to solved