Page 1 of 1

api.php, transfer_conf, agent_user does not have a live call

PostPosted: Tue Oct 11, 2011 1:37 pm
by randy_delgado_03
Good Day Vicidial Group,

All is well on our current version except for the API. we're using api.php with the transfer_conf function, most of the time its working but there are many instances that it fails. When we check the vicidial_api_log table, we saw this on the result: agent_user does not have a live call but when we double check on the agent, it has live call.

My question is, why is that the API detected that the agent does'nt have live call while the agent is indeed have live call?

Anyone encountered this scenario?

PostPosted: Tue Oct 11, 2011 2:51 pm
by mflorell
First, I would suggest upgrading to a more recent svn/trunk version.

Second, is this repeatable?

Third, how frequently is this happening?

Fourth, what application is sending these API commands, and are you logging the responses?

PostPosted: Tue Oct 11, 2011 3:37 pm
by randy_delgado_03
Hi Matt,
First, I would suggest upgrading to a more recent svn/trunk version.

This will be our last option since we need a downtime to do this.

Second, is this repeatable?

This is dynamic but as of now recurring.

Third, how frequently is this happening?

Around 20% of our transfers using the api.php with transfer_conference function.

Fourth, what application is sending these API commands, and are you logging the responses?

We're using PHP from a WAMP Server and responses are SUCESS from the API.

But when we check the vicidial_api_log table, we see that the RESULT field is ERROR and RESULT_REASON is agent_user does not have a live call.

PostPosted: Tue Oct 11, 2011 3:46 pm
by mflorell
The API can't send a SUCCESS and log an ERROR, it doesn't work that way.

Upgrading should not cause much downtime at all, is this a 24/7 callcenter?

PostPosted: Tue Oct 11, 2011 3:51 pm
by randy_delgado_03
The API can't send a SUCCESS and log an ERROR, it doesn't work that way.

That's also what we thought but API is returing SUCCESS and logging on the DB as ERROR.

Upgrading should not cause much downtime at all, is this a 24/7 callcenter?

No, but we have a 24/7 IVR that our clients are connecting during and off office hours.

Any other ideas why this occurs on the API? I mean, what are the factors that can affect resulting this?

Thanks Matt...

PostPosted: Tue Oct 11, 2011 4:15 pm
by mflorell
I can't think of any reason that would be happening, we have clients doing transfers using the API at a rate of thousands a day without that issue coming up.

PostPosted: Tue Oct 11, 2011 4:19 pm
by randy_delgado_03
Can i ask what application do they use to send commands on the API?

Because now we're using WAMP Server and PHP Script to send commands to API and embed the PHP URL on the IFrame.

PostPosted: Tue Oct 11, 2011 4:31 pm
by mflorell
One client is using customized PHP scripts as part of their existing CRM, another is using functions inside of their ASP.net CRM.