8/17/2023 0 Comments Call queue in asterisk![]() ![]() Sales has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s We can now verify that queues are indeed loaded by using the queue show command: geek-university*CLI> queue show Reloading module 'app_queue.so' (True Call Queueing) Module 'app_queue.so' reloaded successfully. This can be done using the following command: geek-university*CLI> module reload app_queue.so Now we can reload the app_queue.so module. We won’t use this file, but it needs to be created in order for the app_queue.so module to load: touch /etc/asterisk/nf There is one more thing we need to do before reloading this module – create an nf file. To apply the configuration, we need to reload the app_queue.so module. wrandom – rings a random members, but uses the member’s penalty as a weight. ![]() linear – rings members in the order specified in the configuration file.rrordered – same as rrmemory, except the queue member order from the config file is preserved.fewestcalls – ring the member with the fewest completed calls.leastrecent – ring the member that was least recently called.ringall – ring all available channels until someone answers.When it gets to the last agent, it will go back to the top. We’ve used the Round Robin with Memory strategy, which will rotate through the members in the queue in sequential order, keep track of which agent got the last call, and present the next call to the next agent. This option distributes calls between members in a queue. The options specified above are mostly self-explanatory, except the strategy option. Ringinuse=no do not ring members when already InUse (prevents multiple calls to a member) Leavewhenempty=yes leave the queue when no members available Joinempty=no a caller may not join the queue when no members are available Strategy=rrmemory uses the Round Robin with Memory strategy Musicclass=default plays the default music on hold We will use a template for the common parameters, and then define the queues: (!) We will work with two queues – the marketing and sales queues. The second option ( shared_lastcall=yes) will make the queue respect the wrapup time for members logged into more than one queue. The first option ( autofill=yes) makes sure that all waiting callers are connecting to available queue members (this was not always the case in the older versions of Asterisk). We will create nf file in the /etc/asterisk directory and add the following configuration for the general section: This file consists of the general section that defines the global options for all queues, and one or more queue sections. Queues that you can assign queue members into are defined in the nf file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |