3CX v16 and SIPTRUNK.com GW1/GW2 issues

[Scot Busby]

Recently, I have been having random issues with my v16 (16.0.8.9) system connecting to gw2 and having calls fail. It seems to reconnect to GW1 eventually, but there have been times where I have had to unregister and reregister the trunks to force it from GW2 to GW1 again. I have the default settings for the trunks and have used the SIPTRUNK.com guide to setup the trunks. Numerous cases with SIPTRUNK.com results in nothing wrong with the setup or their services, so am picking through anything else which might have changed. SIPTRUNK verified the configuration of my trunks in 3CX and reported everything was setup properly and it's been running this way for years without any issues.

I have green all around for the services, firewall, trunks, phones and service extensions and nothing, other than the reported failures (screenshot as an example). I have verified the DNS servers used are the ones SIPTRUNK recommends, but I'm not sure if those are any better than the standard ISP server or 8.8.8.8, 1.1.1.1

I saw an article posted: https://www.3cx.com/community/threa...h-siptrunk-com-and-their-3cx-v18-alpha.82311/ however, they were discussing version 18 and I don't think this was a confirmed solution. I have not removed GW2 from the configuration, as that article suggests.

One last thing to add here is I was having an issue with a firmware update to our router which enabled UDP Flood protection. While the result was similar, these two issues are not the same since that issue has resolved. This is different since the system will disconnect from GW1 and register with GW2 - which, for some reason, causes calls to fail.

Any further suggestions from anyone else who might have experienced this? Thank you!

 

[YiannisH_3CX]

Hi @Scot Busby

GW1 and GW2 should work equally well and are there for redundancy purposes. For the PBX to failover to GW2 however it means that at some point a registration to GW1 failed so the PBX switched to GW2. A thing to note here is that if the PBX established a connection with GW2 it will stay registered to that target until that also fails or until the services are restarted or if some time elapses and you manually re-register the trunk.

Not sure why calls are failing when the PBX registers to GW2 as the Invites from the PBX are exactly the same. From your log it looks that you are receiving an error from SIPTRUNK.com so maybe the question is why are you getting this reply for your calls.

Removing GW2 means that if GW1 fails the PBX will keep trying to connect there and not move to GW2 which might help when the provider is still operational and the loss of registration was caused by something else. But if the server of the provider goes down then your trunk will also go down until GW1 is back online.

 

[Scot Busby]

Thanks @YiannisH_3CX for your reply. I did check with SIPTRUNK.com with regards to the purpose of GW2 if outbound calls from the PBX failed when registered to these trunks and they said that GW2's purpose was for inbound calls only....no outbound calling can run over GW2. This seems to clear up why we are seeing failed call attempts when the trunks are registered to GW2, however, I still need to figure out why we are failing over to GW2 in the first place. When I first configured the trunks for SIPTRUNK.com (years ago), the template did not include using GW2 in the Alternate Proxy field. I also did not use gw.siptrunk.com as the registrar. I have GW1 configured for everything, so there was no failover, but I also never had a problem with the trunks either. It was only when I was troubleshooting the issue with the UDP Flood protection which I re-configured the trunks using the updated SIPTRUNK.com template. I could not tell I had this issue until I resolved the UDP Flood protection and noticed I was failing over to GW2 and learned this was inbound only.

At this point, while it's not the recommended configuration, I might just go back to the way it was configured before - gw1.siptrunk.com for registrar ad outbound proxy and remove the optional proxy.

 

[YiannisH_3CX]

You could try going back to your old configuration and see if that works. Regarding the gw2 registrar only being for inbound calls to the PBX i have a feeling that is not entirely true because when we changed the template configuration it was so we can add gw2 as an alternative proxy for outbound calls and we tested the behavior. The PBX does not care if gw2 is set as an alternative proxy for inbound calls because that is not how it checks inbound calls.
So if you can tell me who you spoke with at SIPTRUNK I will discuss this further with them because if that is the case then we need to change the template back.

 

[Scot Busby]

Hi @YiannisH_3CX,

Thank you for this - I do have the person I spoke with and attached a screenshot of his reply to my question about what was the purpose of GW2. I did set everything back to GW1 for now, until this is resolved. If you need it, the ticket number with SIPTRUNK.com is: REQUEST #479490

Thank you!

 

[YiannisH_3CX]

Thank you for the information. I saved the screenshot but deleted it from the forum as it contained names and numbers and its best kept private.

 

[Scot Busby]

That is fine - thank you for your help. I saw no other way to provide you with specific enough information you could use to make valid inquiries with SIPTRUNK without providing some of that info. Thank you for removing it.