Suddenly calls started failing with no changes to server in months

5

5280pbx

Member
Feb 4, 2019
86
1
8
41
Hi, we have 3 FusionPBX servers cloned from each other, all have worked fine since 2015. About 1 year ago, I upgraded one of the servers to FS PBX. Everything's been great, but randomly calls just stopped working (only on FS PBX server, other 2 servers are still fine). Outbound beeps busy. IVR's will play the greeting until I press and ext and it beeps busy then. Inbound sounds fine and rings, but phones don't ring. All exts on 2 deskphones and Ringotel app are registered fine and show in registration status. Yesterday I updated FS PBX to the latest, but still the same issue
 
Calls failing are usually a Freeswitch or dialplan issue. Please post your FS CLI log when making a call, and I'll try to help you.
 
There are 59000 lines in this log. Please isolate the log for one call. I can't possibly read all of those lines. Turn on FS CLI right before the call and turn it off after the call ends. Then copy and paste only those lines.
 
It's fine to use the log viewer, but just don't paste all 59000 lines. The log rotates when it fills up, allowing it to store weeks' worth of calls. If you can isolate just the call in question and paste it here, it would be best. I personally prefer FS CLI because I can start it before the call and end right after the call. Then all I see is just what happened during that time
 
This is a public forum. Don't post your credentials here.
Remote sessions are reserved for customers subscribed to a support plan.

I'm happy to do best effort support on the forum for free, but you need to provide the required logs.
 
Fixed.
1) internal profile and external profile use the same port 5060, internal profile was down
2) in internal profile set auth-calls=true it was false before
 
It turns out outbound only works now. Inbound does not. I woke up to a message from the guy who was working on it, who said "please ask the carrier to deliver call to udp 5080, it's the external profile port"

Which is super annoying. Again, since other 2 servers still are perfect on Skyetel. Also, it was configured with Skyetel in a click during FusionPBX install since they're recommended carrier partner.
 
FusionPBX and FS PBX are exactly the same when it comes to SIP profiles. As a matter of fact, SIP profiles are a Freeswitch thing and have nothing to do with either FS PBX or FusionPBX. By default, your external profile uses port 5080 unless you change it. Adrian is correct in pointing out that you should ensure external and internal profiles do not use the same port. If you make any changes to them but never flush the cache and restart Freeswitch, they will continue to work with the old settings. Perhaps one of your boxes was rebooted.
If the provider supports FusionPBX, it supports FS PBX too. There are no changes to how Freeswitch and SIP profiles work.
 
You must log in or register to reply here.
Top Bottom