Howto:IQM in large PBXs
If an iQM works on large PBX the start-up time will be long and annoying and cause also heavy workload for both, the PC and the PBX.
From Build 80087 on it is possible to start-up the iQM very quickly even on huge PBX. Here is how.
This information applies to
iQM Build 80087 or higher
Some customer operates a huge PBX (many hundreds of user) and a relative small group of Agent. For example 1000 user in the PBX but there are just 5 Agents for a special queue with an iQM.
Instead of reading out all the PBX it is possible to define the Agent in a simple text file. The iQM will detect if a file named “iQMagentlist.txt” is in the directory where the log files are.
Note: Check the right directory following the link in the iQM setup.
If such a file is found it will be opened and if at least one entry is found the agent list will not be detected in the PBX but the iQM assumes that this file contains the name of the agent.
Therefore in this file should be all the Long Names of the Agent.
The best way to setup this is open the text editor and copy from the PBX the Long names of the agents in the file, one name each line.
Then save that file with the name “iQMagentlist” in text format.
In the setup of an iQM just the name of the waiting queue is defined. So the iQM after start-up has no idea about the group name and the agents. The iQM reads out form the PBX the Queue object and now knows the queue group name. Than the iQM read out all object from the pbx, and if an object is a user or executive object and match with the group name of the queue an agent is detected. The reading of the objects can’t be done very quick because the pbx could trap. Therefore the reading about is a relative slow process. Not a real problem if the number of objects in a PBX is limited, but on very huge PBX there is a long time to wait until the iQM is ready after a restart.
The iQM has to know the Long Names of the Agents, because he must initialise them in the PBX. Initializing for example 5 agents is a question of few seconds while rending out 1000 user a question of minutes.
If the iQM detect the file “iQMagentlist.txt” he opened the file and read out one name after the other. If the first read out is fine he will no longer try to read out the PBX. That means also that if no file is detected (or the file is empty) the “normal” operating way is done. There is no setup to do, the file and his entry will switch from one operating mode to the other. The iQM after reading out the name in the file entry ask the PBX if such an object with this name is in the PBX. If not the next entry will be processed, therefore if you do not find an agent in the agent list probably the name is wrong.
If the object is found the iQM check if this is an user or executive object. If not the object will be skipped and in the log you will be find the entry “WARNING: Agent is not a User or Executive object:”.
Note: in the list should just be agent long names, no Queue or SOAP name or similar.
If the user is fine but not in the group the agent is skipped and in the log you will find the entry “WARNING: Agent is not in group:“
Note: After all the initializing stuff the iQM require some seconds to establish a fully operating SOAP connections and if that is up the message “running session xx on queue yyyy” is displayed as usual in the iQM server main window.