Vicidial/Asterisk calls dropping

512k will do 20 calls using g729. The calc you provided does look like it includes some overhead because 8x20 only gets you to 160k

View attachment 297686

In any event it should be easy for the ISP to provide graphs showing that the link is saturated. The SIP provider should also be able to provide stats on concurrent calls.

Why should overheads etc. be excluded from the calc, surely in the real world they influence the bandwidth consumption?

Here is my real world example:
- Asterisk -> Mikrotik -> ADSL -> ISP -> SIP provider
- Used calc (http://www.asteriskguru.com/tools/bandwidth_calculator.php) to calculate 1 call using G729
- 1callg729.JPG
- Checking bandwidth consumption on MK my results are pretty close to calc
- 1 Call 48.2kbps
- 1callg729-2.JPG
- 2 Calls 96.6kbps
-1callg729-3.JPG

Cheers
 
Why should overheads etc. be excluded from the calc, surely in the real world they influence the bandwidth consumption?

I think the confusion comes in with the disclaimer on that calc "SIP overhead is disregarded", but I suppose what that really means is the calc is showing you the RTP stream with all its overhead and the initiation of the call over SIP and subsequent chatter is excluded (but it's minor anyway).

Got to love queue trees in RouterOS :D
 
Hi, everything been a bit stable but asked another independent person to have a look and he said the extensions are de-registering a lot and it could be the agents doing or the auto dialer (zoiper)
 
Hi, everything been a bit stable but asked another independent person to have a look and he said the extensions are de-registering a lot and it could be the agents doing or the auto dialer (zoiper)

[2015-10-05 08:00:06] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 12
[2015-10-05 08:05:14] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 15
[2015-10-05 08:23:37] NOTICE[3793] chan_sip.c: Peer '7000' is now UNREACHABLE! Last qualify: 3
[2015-10-05 08:27:31] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 10
[2015-10-05 08:30:24] NOTICE[3793] chan_sip.c: Peer '7000' is now UNREACHABLE! Last qualify: 7
[2015-10-05 08:32:43] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 5
[2015-10-05 08:36:08] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 6
[2015-10-05 08:41:50] NOTICE[3793] chan_sip.c: Peer '7023' is now UNREACHABLE! Last qualify: 4
[2015-10-05 08:42:26] NOTICE[3793] chan_sip.c: Peer '7055' is now UNREACHABLE! Last qualify: 23
[2015-10-05 08:50:42] NOTICE[3793] chan_sip.c: Peer '7054' is now UNREACHABLE! Last qualify: 4
[2015-10-05 08:53:13] NOTICE[3793] chan_sip.c: Peer '7007' is now UNREACHABLE! Last qualify: 6
[2015-10-05 08:59:14] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 7
[2015-10-05 09:08:35] NOTICE[3793] chan_sip.c: Peer '7055' is now UNREACHABLE! Last qualify: 18
[2015-10-05 09:18:29] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 13
[2015-10-05 09:23:24] NOTICE[3793] chan_sip.c: Peer '7000' is now UNREACHABLE! Last qualify: 4
[2015-10-05 09:27:26] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 16
[2015-10-05 09:30:04] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 15
[2015-10-05 09:34:54] NOTICE[3793] chan_sip.c: Peer '7000' is now UNREACHABLE! Last qualify: 3
[2015-10-05 09:37:12] NOTICE[3793] chan_sip.c: Peer '7038' is now UNREACHABLE! Last qualify: 17
[2015-10-05 09:37:49] NOTICE[3793] chan_sip.c: Peer '7010' is now UNREACHABLE! Last qualify: 54
 
Hi, everything been a bit stable but asked another independent person to have a look and he said the extensions are de-registering a lot and it could be the agents doing or the auto dialer (zoiper)

That generally Indicates either LAN issues or agent issues. Based on the fact that its individual peers at different times I would start with a visit to the agent. Maybe they have issues causing them to reboot or zoiper is crashing.

Would be nice to have some feedback and what has happened thus far, you were looking at server resources and link sizes, what has changed to get things stable?
 
The Vicidial server guys don't tell us much that's why we're planning on replacing them, looks like they want us to be dependent on them. They are also increase the monthly maintenance fee by over 100%
 
been following this thread and two things I think you have not checked which could also cause some issues:
1. have you checked what the SP has set your allowed concurrent channels to?
2. have you purchased the g729 licenses if yes, have you got enough licenses to cater for the amount of users / channels you have
 
The Vicidial server guys don't tell us much that's why we're planning on replacing them, looks like they want us to be dependent on them. They are also increase the monthly maintenance fee by over 100%

Happy to help in that aspect. Feel free to drop me a PM if you want to have a more formal discussion.
 
Good Day ,

Looking at your specs your are running a single vicidial server with 20 agents , assuming you on manual dail and just started going auto dial or changed the dialing ratio on the campaign . The first issue that comes up is that the server is under spec's on the cpu , vicidial is very resource hungry as its an automated dialing system ,its not only running asterisk but its making use of apache webserver and also mysql db . when users are being kicked out on a single system that means the server can not handle the amount of resources its been given . run command htop and send us the output , lets see how hard the cpu's are working . We currently have over 600 agents split on vicidial clusters running with no issues for the past 3 years
 
Top
Sign up to the MyBroadband newsletter
X