![error opening channel to lst server error opening channel to lst server](https://documentation.suse.com/sles/15-SP3/single-html/SLES-virtualization/images/libvirt_vmm_usb_redirector.png)
If you are concerned about this, you can see itsĬurrent impact by monitoring how often the status LIMITED BY TRUNK RATE appears on Using a lower CPS limit does not usually affect so much the speed of your campaigns in real-life, as WD will onlyĮffectively "spread out" the calls to be dialed over a few seconds. When a new trunk isĬreated, its default is 100 calls per 1000 ms, that is a value high enough to mean "no CPS limits" for most scenarios. Rate limiting is expressed in terms of a maximum number of calls per a specific period in milliseconds.
![error opening channel to lst server error opening channel to lst server](https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,c_fill,w_720/https://ubuntu.com/wp-content/uploads/1270/image.png)
![error opening channel to lst server error opening channel to lst server](https://ars.els-cdn.com/content/image/3-s2.0-B9780750689717000093-gr11.jpg)
The Trunk will keep track of the number of calls just placed within the last time period, so if the trunk has (say) 50 channels free,īut in the last second 10 calls have been requested and the maximum CPS is 30, it will report back that it In order to implement CPS limiting, what happens is that when Wombat inquires for the number of empty channels on a Trunk, Than the combined CPS while if you have a campaign with two separate trunks, the maximum CPS So the following ones are valid examples:Īs this check is enforced per trunk, if you have multiple campaigns sharing a trunk, no campaign can dial faster Then you can assignĮach (or even both) to campaigns to control the maximum number of parallel outgoing calls.Ī note on the dial string: it must be a valid Asterisk channel name, and the string $ is replaced The example you have a 15-channel trunk, you might define it as two trunks in WD, one having 10 channelsĪnd another having 5. It is also perfectly legal to define a physical trunk multiple times, splitting its capacity: again in So that you can use the rest with your PBX without any special rule. ForĮxample, if you have a 15-channel E1 to your telco, you might define the trunk in WD as being a 10-channel one,
#ERROR OPENING CHANNEL TO LST SERVER FULL#
You do not need to define all the trunks that are on your PBX, or to define them to their full capacity. Security key is the key that will protect this resource.Max calls per period (number) and Period length (milliseconds): the maximum CPS rate limiter (see below).Capacity: is the number of parallel calls that WD can dial.Dial string: is the actual Asterisk channel name that WD will invoke (see below).Ĭlose to the Dial string, there is the Test Connection icon button (see below).Name: is a logical name for the trunk to appear in WD.Asterisk server: is the name of the PBX on which this trunk is located.The HTTP Notifications section Section 8.6, “HTTP/S life-cycle notifications of calls”), withoutīoth the dialer and the GUI use a persistence layer that reads and writes to the MySQL database used for long-term The dialer also spawns a helper thread that is meant to run long operations, e.g. In case of errors, each AMI handler will automatically retry until a connection is established. If a PBXĬrashes, the rest of the system keeps on working and if one PBX is delayed or loses connection, this does not Each of them runs asĪ separate thread and connects to a PBX through its Asterisk Manager Interface (AMI). When the dialer is running, it creates separate AMI handlers for each Asterisk PBX. To the state of an external PBX, during the restart phase calls might not be placed for a few seconds but existingĬalls will be preserved and tracked correctly. When the dialer runs, an associated watchdog process runs - if the dialer process is to terminate for an unexpectedĮrror, the watchdog is supposed to log the error on the system log and restart it.
![error opening channel to lst server error opening channel to lst server](http://3.bp.blogspot.com/-xM7rh_fhBVY/UZS1FIoqp9I/AAAAAAAAPYM/m3M0P9L2fjk/w1200-h630-p-k-no-nu/dhcp_error1.png)
The dialer itself is controlled by the GUI Server - this way you can start and stop the dialer process from the GUI. byĬontrolling runs, adding new numbers to dial and creating new campaigns. APIs are meant for external programs to control the behavior of the dialer, e.g. Run reports) or through APIs (see the HTTP API section Section 8.3, “Controlling WD over HTTP”). Understanding which ones they areĪnd what they are for will make understanding the whole product easier.Īs a first thing, WombatDialer can be accessed through its GUI Client (in order to configure it, view what it is doing and WombatDialer is a complex system that is built out of different subsystems.