QUEUE Operators in unavailable/invalid state
Hi all.
I search in all the topic but i not can find nothing about.
I buy FOP2 and i use in 2 Elastix installation.
I manage 4 queue for any installation and all works good, i really apreciate this product.
What is strange, is that after some hours that i put new member in queue, i can see a change in their state and a red circle appears un the operators icon.
Usually the queue continue answare at in-calls, but sometimes, when this state appears on the operators, the extension in the queue not ring.
Now, why the operators in the queue go in unavailable/invalid state? (like the FOP2 documentation describe this status icon).
Thank all right now,
regards,
Mauro.
I search in all the topic but i not can find nothing about.
I buy FOP2 and i use in 2 Elastix installation.
I manage 4 queue for any installation and all works good, i really apreciate this product.
What is strange, is that after some hours that i put new member in queue, i can see a change in their state and a red circle appears un the operators icon.
Usually the queue continue answare at in-calls, but sometimes, when this state appears on the operators, the extension in the queue not ring.
Now, why the operators in the queue go in unavailable/invalid state? (like the FOP2 documentation describe this status icon).
Thank all right now,
regards,
Mauro.
Comments
The invalid stated is set by asterisk, not FOP2. I am not sure about all the possible reasons a queue member might become invalid, I know that a Local type member pointing to an unexistent extension@context might be displayed as invalid, but there might be other reasons too. Perhaps the problem might become apparent if you run "queue show" from the asterisk cli and look at the output there....
Best regards,