Goautodial on tablets

[myaddressis]

Hi,
First post here. We're playing around with GAD and have good progress so far on PC's and laptops. Calls are successful, progress indicators display correctly on the web interface, etc etc, in short everything works as advertised.

Now of course being the progressive bunch of people that we are, we're trying to use the project on IPads and HTC Flyers but there seems to be a browser/technology issue with them when trying to enter the disposition of the call after hanging up (the green block doesn't disappear after submitting), also a small glitch on the call progress once answered in the default agent screen (Doesn't update the status after the call has been answered). Has anyone else had experience in this? At first I was cursing the Ipad, then swallowed my tongue when the same happened on the HTC.

Here's what we've learned so far:
- The pads all connect via Wifi at the moment and we're sitting in the same location as the server so that eliminates bandwidth constraints.
- We've tried multiple browser packages on both the Ipad and Flyer, all come back with the same disability, leads me to believe that it's something inherent in the technology.

GoautodialCE 2.1 from .iso | Vicidial 2.4-325c Build 110430-1924 | Asterisk 1.4.39.1-vici | Single Server | No Digium/Sangoma Hardware | Queuemetrics after installation

[williamconley]

We've tried multiple browser packages on both the Ipad and Flyer

There is an inherent flaw in that logic. Did you try this with non-tablet browser packages? Since this works marvelously in Firefox and IE on virtually any Windows or Linux PC, the technology checks out perfectly. However, since these browsers do not share technical code with tablet browsers ... the problem lies in those browsers (and their lack of compatibility with their non-tablet counterparts).

AJAX is a complex technology and is heavily relied upon for the agent screen. This could certainly be modified to fix your purpose (to become compatible with a specific tablet browser). I have honestly never tried it on my Galaxy Tab, but I would expect the same results. Remember that tablet browsers are NOT identical to desktop browsers (support for each technology must be "built-in" by the makers of that browser ...).

I do like where you are going, though. Brilliant. Are you also using soft phones on the tablets with Bluetooth for the agents?