VoIP Mailing List Archives

[schoch+freeswitch.org ...]

I broke our PBX

I upgraded to Debian 11 and FreeSWITCH 1.10.7. I copied all the configuration from the old system but I messed something up and it doesn't register. I get this:



2022-09-23 13:36:42.219720 99.63% [NOTICE] sofia_reg.c:459 Registering flowroute
2022-09-23 13:37:43.299709 99.60% [WARNING] sofia_reg.c:495 Timeout Registering flowroute

2022-09-23 13:37:44.299709 99.27% [WARNING] sofia_reg.c:516 flowroute Failed Registration [908], setting retry to 30 seconds.


Setting sofia global siptrace on doesn't show anything. Sofia status shows this:




                 external profile         sip:mod_sofia@<my_ip>:5080 RUNNING (0)

      external::flowroute gateway   sip:<my_username>@us-west-or.sip.flowroute.com TRYING (retry: 24s)


I don't know where to go from here. Any suggestions?



-- 
Steve

[brian at freeswitch.com]

Do you happen to have a full sip trace? I can only guess at this point, and we don't break things that badly between releases EVER, so could it be a localized issue?

/b




On Fri, Sep 23, 2022 at 4:11 PM Steven Schoch <schoch+freeswitch.org@xwin32.com ([email]schoch%2Bfreeswitch.org@xwin32.com[/email])> wrote:

[schoch+freeswitch.org ...]

Okay, never mind. It's working now. I think it was a DNS issue. When I hardcoded the Google DNS servers in /etc/resolv.conf, it started working.The SIP trace was showing nothing probably because the DNS lookup failed so it couldn't even make the first attempt.


-- 
Steve


On Fri, Sep 23, 2022 at 5:28 PM Steven Schoch <schoch+freeswitch.org@xwin32.com ([email]schoch%2Bfreeswitch.org@xwin32.com[/email])> wrote:

[schoch+freeswitch.org ...]

I don't know how to make it do the sip trace. I typed "sofia global siptrace on", but the only thing I see is what I sent in my original message.Yes, I'm pretty sure it's a localized issue, but I'm trying to figure out what the localized issue is.


To test the DNS, I ran:

$ ping us-west-or.sip.flowroute.com
PING us-west-or.sip.flowroute.com (34.210.91.112) 56(84) bytes of data.
64 bytes from ec2-34-210-91-112.us-west-2.compute.amazonaws.com (34.210.91.112): icmp_seq=1 ttl=28 time=27.5 ms
64 bytes from ec2-34-210-91-112.us-west-2.compute.amazonaws.com (34.210.91.112): icmp_seq=2 ttl=28 time=27.5 ms
64 bytes from ec2-34-210-91-112.us-west-2.compute.amazonaws.com (34.210.91.112): icmp_seq=3 ttl=28 time=27.5 ms


On the old (working) system, I was using port 5080 because that was recommended to avoid attacks on the well-known port 5060. When registering with the provider, any port will work.


-- 
Steve


On Fri, Sep 23, 2022 at 2:34 PM Brian West <brian@freeswitch.com (brian@freeswitch.com)> wrote: