search for: agentno

...----------------------------------------------------------------------------- "This patch adds quite a few new features into __login_exec () of channels/chan_agent.c for AgentLogin() and AgentCallbackLogin(). Only one option ('s') existed previously. Syntax/Documentation: AgentLogin([AgentNo][|options]): Asks the agent to login to the system. Always returns -1. While logged in, the agent can receive calls and will hear a 'beep' when a new call comes in. The agent can dump the call by pressing the star key. The option string may contain zero or more of the following characters:...

...for agentlogin instance and dial instance. Is there a variable that is common for both instance or is there a way that I can pass variables across. My context and AGI's are given below. [specqueuestat] exten => _10XX,1,AGI(agi_agentlogin.sh|${EXTEN}) exten => _10XX,2,AgentCallbackLogin(${agentno}||${sip_id}@specqueuestat) exten => _8XXX,1,AGI(agi_qdial.sh|${EXTEN}|${CALLERIDNUM}) --agi_agentlogin.sh *declare -a array while read -e ARG && [ "$ARG" ] ; do array=(` echo $ARG | sed -e 's/://'`) echo ${array[0]} = ${array[1]} >>$LOG_FILE...

I know I must be being daft, but is there a way to set which context the queuing system uses when it dials the operators/agents? By default it appears to use the default context. I've looked through voip-info.org and can't find anything, someone please put me out of my misery.

Hi, I am doing an AGI that logs to a database every Agent login/logoff. My idea is to be able to go to this database and check which agents where logged so that I can force their login in case Asterisk goes down for some reason. The problem is that I would need to reload their status from this AGI when Asterisk initializes. Is there a way to do this? One idea I had was to make safe_asterisk to

Hello all, I am building a software based on asterisk to handle incoming answering service calls. I have one problem that I have not been able to figure out a reasonably priced solution to: The goal of this software is to allow the agent to be able to do their entire job from the desktop. The only thing that seems to be a problem is getting the operator (agents) headset logged on to the