Solved PBX Blacklisted the main SIP Trunk IP

[vanguard08]

FYI in case it's new info for anyone.
A few months ago one of our locations changed providers but when the new SIP Trunk info was entered, the IP was not automatically nor manually white-listed. A lesson learned, but possibly helpful to someone else. All inbound calls were dropped until we figured out the main IP of the SIP trunk had been black-listed and corrected it.

 

[AWS2P]

Surely trunk got BL because of too many failed registrer tries before beeing good.

 

[vanguard08]

Yea, that's what caused it to get blacklisted. All it took was a few failed register attempts and someone not paying the proper amount of attention to the logs (me). Just pointing out trunk IP's don't necessarily get automatically white-listed. Of course, now I'm going through all our other locations to ensure they are.

 

[YiannisH_3CX]

Yea, that's what caused it to get blacklisted. All it took was a few failed register attempts and someone not paying the proper amount of attention to the logs (me). Just pointing out trunk IP's don't necessarily get automatically white-listed. Of course, now I'm going through all our other locations to ensure they are.

Trunk IP addresses do not get automatically white-listed by the PBX. This is something that has to done manually if necessary. Also if you change a Blacklist entry to a whitelist entry the timer still applies and the entry will be deleted after the expiry of the timer. It is recommended to delete the Blacklist entry and add a new Whilelist entry to make it permanent.

 

[vanguard08]

Roger, thanks for the verification.