Recent content by Msquared

Of course it would be that easy. Sometimes I think I must some German engineering somewhere in my blood-line. LoL Thank you for the info!

@DigitalDaz Running 2 servers with BDR for fail over and Route 53 to handle the DNS, what do you use for the Route 53 health checks? I thought about just setting health checks for HTTP/HTTPS but I'd rather check the status of the Freeswitch service. I was thinking maybe a custom script...

Changing the Outbound Routes Dialplan bridge to add @us-west-wa.sip.flowroute.com:5060 seems to fix the issue (the port # on the end is what worked for me). My old bridge looked like: sofia/gateway/flowroute/123456*1$1 I changed it to look like...

Thank you for the reply! That did provide a better insight (and a ton of noise). So if I am reading this correctly, DNS is being resolved, NAPTR SRV records are being returned but it's not able to reach the SIP provider? I did a dig on that record from my server and found the IP it resolves...

I am not finding any issues with sofia/internal, I can see where it changes call_direction to an outbound call and opens a new channel on sofia/external and routing starts but immediately terminates with 503. 2020-10-07 00:36:29.682231 [DEBUG] sofia.c:7290 Channel...

Thank you for the reply DigitalDaz. The 503 is coming from FreeSwitch before it ever reaches out to the carrier. Any idea why? I've tried deleting the FlowRoute Gateway & Outbound Route from Fusion and recreating it, but it did not help. I have a fairly default Dialplan, the only change...

I've banged my head against the wall all weekend reading various forums about this error, any help is much appreciated! Background: I've had FusionPBX up and running on an AWS instance for almost a year now without issue. I have a static IP assigned to my instance and I'm using a domain pointed...

I ran into this same issue when following the FusionPBX Docs. What worked for me was to follow the first half of the documentation to create a single SSL Cert for my primary domain (domain.com), confirm you receive the output: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok...