Operating the astguiclient 100% from API within my CRM
Posted: Wed Apr 22, 2015 7:52 pm
Hi,
We are using vicidial with our custom CRM. The way it works is, when user logs into our crm, they enter the extension # that they are sitting at. Then when they login, we automatically launch another tab to vicidial astguiclient, automating the login process by manipulating the login querystring to the Agent Console. For the rest of the session we don't use the Agent Console at all. In fact, we actually have a DIV that covers up the entire astguiclient tab that says "USE CRM ONLY. DONT CLOSE TAB". All of the commands are controlled from within the CRM it self, the agent never touches the astguiclient window. We have a javascript that communicates every 5 secs with the agent API st_get_agent_active_lead & recording&value=status commands in order to determine the state of the call, and offer the appropriate buttons like resume/pause, hold, dial new number, login to queue, etc. We dispo the call and everything directly within our crm.
I am trying to find a way to ditch the need to login to the astguiclient alltogether (our second tab), by somehow logging in via the API or by other means. Is this possible? When I first did the integration I Just did it quick, but now I'm seeing more load on my database server than I can handle so I'm looking to optimize how I did this. To start, I'm currently considering changing the refresh_interval for the astguiclient from 1000ms to 5000ms. But I am wondering if this will affect my API commands execution time at all. Any reason I couldn't set the refresh_interval to 30,000ms for example, since we don't care about the data that is displayed to the agent in the agent console, as they are not using it.
From what I have tested, the only reason I need to log them into the agent console is to trigger the actual login event, and then keep telling vicidial that the window is still open so it doesn't auto terminate the session. Any ideas on what route I should pursue to eliminate the astguiclient window completely, by inserting into the db and otherwise emulating its login process?
We are using vicidial with our custom CRM. The way it works is, when user logs into our crm, they enter the extension # that they are sitting at. Then when they login, we automatically launch another tab to vicidial astguiclient, automating the login process by manipulating the login querystring to the Agent Console. For the rest of the session we don't use the Agent Console at all. In fact, we actually have a DIV that covers up the entire astguiclient tab that says "USE CRM ONLY. DONT CLOSE TAB". All of the commands are controlled from within the CRM it self, the agent never touches the astguiclient window. We have a javascript that communicates every 5 secs with the agent API st_get_agent_active_lead & recording&value=status commands in order to determine the state of the call, and offer the appropriate buttons like resume/pause, hold, dial new number, login to queue, etc. We dispo the call and everything directly within our crm.
I am trying to find a way to ditch the need to login to the astguiclient alltogether (our second tab), by somehow logging in via the API or by other means. Is this possible? When I first did the integration I Just did it quick, but now I'm seeing more load on my database server than I can handle so I'm looking to optimize how I did this. To start, I'm currently considering changing the refresh_interval for the astguiclient from 1000ms to 5000ms. But I am wondering if this will affect my API commands execution time at all. Any reason I couldn't set the refresh_interval to 30,000ms for example, since we don't care about the data that is displayed to the agent in the agent console, as they are not using it.
From what I have tested, the only reason I need to log them into the agent console is to trigger the actual login event, and then keep telling vicidial that the window is still open so it doesn't auto terminate the session. Any ideas on what route I should pursue to eliminate the astguiclient window completely, by inserting into the db and otherwise emulating its login process?