Free PBX outbound calls failing.
-
I have been dealing with a customer having occasional failed outbound calls on their Free PBX system. We have looked at details like system resources on the server, general network traffic, and even migrated a bunch of VM's onto a new server to split the load up. One of the primary thoughts is that they may be hitting their SIP trunk's concurrent call limit. The main reason for this thoughts are these: 1. the limit is only 10 calls, and they have something like 50 registered extensions, and 2. users have reported receiving an "all busy" message when a dialed call fails to connect. I did notice that the "normal congestion" setting looks like it will play exactly that message in the case of congestion, whatever that means definitively. Also, it seems to me, logically, that a network traffic bottleneck would simply cause the call to "fail" and not prompt a system-originated message to play in response to the drop.
What are your thoughts? To be clear, we're talking about Asterix and Vitelity (SIP provider). -
Can Vitelity tell you if they reached their 10 concurrent call max?
-
50 extensions with only 10 lines.
I'd have to agree with your initial idea that all of the lines are in use. Are there any reports you can run against the system to see what lines, extension, and duration of the call?
-
LOL - we had 80+ extensions with 65 users and only 12 lines when I first started. We upgraded from 12 POTS lines to a PRI, and the influx of calls overwhelmed us.
-
I've been watching the System Status dashboard for a while, hoping to see a spike that puts confidence in what I am suspecting. I'm not exactly an "expert" in Free PBX just yet, and I've yet to find a useful report to address this. Vitelity does not have a report for this, either.
-
@art_of_shred said:
I've been watching the System Status dashboard for a while, hoping to see a spike that puts confidence in what I am suspecting. I'm not exactly an "expert" in Free PBX just yet, and I've yet to find a useful report to address this. Vitelity does not have a report for this, either.
Does Vitelity have a Call usage report that you could use critical thinking (many vendors don't do this) and say "oh hey we did have 10 calls at 10:00AM that day"
-
huh, Seems like someone somewhere should have console that shows the number of concurrent calls.
Does FreePBX offer any reports that would show the number of concurrent calls at a given time?
Sounds pretty useful if they don't.
-
Someone did add something, but it apparently never took off. It does work, but is not pretty.
I just installed the latest version of POSSA/freepbx-Call-Statistics (github link)
Download link: http://pbxossa.org/files/callstatistics/
-
@art_of_shred it looks like this
-
That's exactly what he needs though. But will it show events prior to it being installed?
-
@DustinB3403 said:
That's exactly what he needs though. But will it show events prior to it being installed?
Depends on where it gets it's data.
-
Note, I said I just installed it.
For the record though, it uses the FreePBX CDR data.
-
@JaredBusch said:
Note, I said I just installed it.
For the record though, it uses the FreePBX CDR data.
That makes sense, and it is what I really need. Thanks!
-
@JaredBusch said:
Note, I said I just installed it.
For the record though, it uses the FreePBX CDR data.
So where you able to see time lines for times before you installed it?
-
Does Vitelity have a limit on the number of calls per time unit that can be placed? Like 3-5 calls per second but you can have 10 simultaneous calls? I don't remember seeing that in the fine print but it may very well be the case.
-
I am only aware of the 10 call limit, no time restraint.
-
@Minion-Queen just informed me that the time constraint is a Voice Pulse thing, not Vitelity... part of why she likes Vitelity better.
-
@coliver said:
Does Vitelity have a limit on the number of calls per time unit that can be placed? Like 3-5 calls per second but you can have 10 simultaneous calls? I don't remember seeing that in the fine print but it may very well be the case.
Man, that could be a big deal in a large organization.
-
@art_of_shred said:
@Minion-Queen just informed me that the time constraint is a Voice Pulse thing, not Vitelity... part of why she likes Vitelity better.
Ah, I knew I saw that when researching SIP Trunks. Wasn't sure which company did it though.
-
@Dashrender said:
So where you able to see time lines for times before you installed it?
/me looks at the date range in the pretty picture...
