3/19/2024 0 Comments Queue twr meaning asterisk![]() ![]() If GROUP_COUNT returns 1, then the busy() is returned without actually trying to dial the agent. The advantage of this method is that the user could log in from any place and phone, which is connected with the Asterisk PBX.You can see a screenshot below.In the above, the variables $ variable on a subsequent call should return "1" for that group. The user has to log in itself in the queue, manually. ![]() This is necessary, because unlike the "static" method, here is not enough just to turn on your phone. If you decide to use this method you have to add in your dialplan either the AgentLogin or the AgentCallbackLogin application. This means that we want the agent with number 8888, to answer the incoming calls in the queue test. In our example we have written the following: member => Agent/8888. Unlike the static method, here we have to write not the name of the user, but the number of the agent, as written in the nf file. In the section nf Configurations we will show you the configurations in it and here we will explain you the configurations in nf file. For this configuration you will need the nf file. The other way is the so called "dynamic" way. That is why the method is called "static". The disadvantage is that this user can use, only the phone, on which it is registered. It will be logged in automatically, when it turns on its phone. The advantage of this method, is that you do not have to use the AgentLogin or the AgentCallbackLogin applications in order to log the user in the queue. However in our case we will have only one user. In the same way you can add even more than one user, which you would like to answer in this queue. This means that this user( operator) will be responsible for the answering of the incoming calls in the queue test. In this context we have written the following: member => SIP/operator. In our example, we have created a context with the name. You will say directly, which users to answer the incoming call. For this configuration you do not need the nf file. The first one, is the so called "static" way. There are two possible ways to configure the settings in this file. More about the features of this configuration file, you can learn in our tutorial about the nf file. In other words, which users or agents will be responsible for the answer of an incoming call. That has no impact within this, since it’s calculated using the RTCP. The value is presented in seconds I believe in the output. Specifically using embedded timestamps in the RTCP packets and calculated delays. In this file you have to say which users or agents will participate in your queue. The value is calculated according to the logic in the RFC 1. Otherwise, if you write the disallow option after the allow options, no codecs will be supported by the line. First you write the disallow=all option and then the allow options. It is important to write the options exactly in this order. This means that the line will support these three codecs - ulaw, alaw and gsm. However, below this option we have allow=ulaw, allow=alaw and allow=gsm. This means that the line will not support any codecs. In the sip.conf file you can see the following option: disallow=all. Context=test - this shows that this user is working with the extensions in this context of the configuration file nf. Allow=all means that the line which this user will use, could support all audio codecs. Host=dynamic means that the IP is not static but dynamic through a DHCP server. Type=friend means that this user can make and receive calls. ![]() So, we have registered the user user1 in the iax.conf file and the user operator in the sip.conf file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |