![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| ||||
| ||||
|
|
An interesting idea but am I understanding this correctly? You appear to be suggesting that I can do all of the things listed in your blog via a normal landline phone with no additional equipment. This seems to imply that it is all by decoding DTMF tones which is in itself easy but I have trouble seeing how I would use it. |
|
Picking a couple of examples from your list... Clearing locks. I would need to be able to review the current situation to know that I had a problem and which lock to clear. Are you suggesting that the system would provide voice output of the current state? |
|
Writing and running simple programs Even more so I need to see what I am doing. Think of the havoc from the odd typo if I am programming blind. |
|
I like the idea but it needs a little more flesh on the bones to understand how you see this working. Martin Phillips |
#4
| |||
| |||
|
|
Martin Phillips wrote: An interesting idea but am I understanding this correctly? You appear to be suggesting that I can do all of the things listed in your blog via a normal landline phone with no additional equipment. This seems to imply that it is all by decoding DTMF tones which is in itself easy but I have trouble seeing how I would use it. Numeric keypad entry is mostly used for menu selections: "Press 1 for backup and restore operations, 2 for system restart options, 3 for system status, 4 for business operations." It can also be used to enter order numbers, part numbers (where of course this fits with the application), quantities, etc. For this specific offering I'm not accepting voice for commands. *That can certainly be done but it's limited by available technology and I'm not trying to break any new ground here. *(Some people here might remember that ten years ago I did a demos at the Pick Systems World User Conference, controlling D3 by voice and getting voice responses from a mock application.) *However I can accept voice notes which are transcribed for storage in the DBMS, and audio can be stored with a link passed back to the application as well. *(MV-based voice mail app?) How would you use it? *All I'm doing is making it easy for MV people to do exactly what everyone else is doing. *Remember though that some people might want to use this for Support and others might be interested purely for consumer-facing end-user applications. *I'd guess that for every VAR interested in support there may be 50 end-users who recognize this as something they use every day and they might want it for their own system. Picking a couple of examples from your list... Clearing locks. I would need to be able to review the current situation to know that I had a problem and which lock to clear. Are you suggesting that the system would provide voice output of the current state? Yes. *How it does this would be DBMS-specific and modifyable by anyone who has the package. Writing and running simple programs Even more so I need to see what I am doing. Think of the havoc from the odd typo if I am programming blind. Yes typos need to be avoided. *I did say "simple". *And this would not be an exercise to undertake by numbers-only keypad or voice. Being able to write and run something simple by SMS is far better than having no access at all. *This is a just way to do something more complex than a few command-line statements as part of some quick support operation. *It's not a mechanism to write application software. I like the idea but it needs a little more flesh on the bones to understand how you see this working. Martin Phillips This is really quite simple. *For providing Support, some operations are well suited to quick commands, others are not. *It's easy to reboot a system with a single command. *That can be issued by SMS or voice. *The raison d'�tre of *this new interface is to give people a mechanism for doing things that we can't do without a laptop, dialup, VPN, going into the office, or getting someone who's in the office on the phone. *It's just another option, not a panacea, and not stretching current technologies. *But it is something that no one else seems to offer - so here we are. For end-user applications this is actually a spin off of some development I've been doing. *I'm using my phone as described every day anyway, and giving ordinary consumers access to MV data by phone. I figured other MV developers might be interested in that aspect, and the system support aspect is just a bonus. Best, T |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
For operations like those listed, I would get more frustrated using the phone than I would with a PC or terminal. A phone application with a clean, simple user interface that monitors the status of services, alerts, and able to execute simple commands would be better. I know there are times where, for whatever reason ODBC had shutdown, and such an app would have been useful. |
#7
| |||
| |||
|
|
If you WERE talking about a "smartphone", or even an iPhone, I'd probably just opt for RDP .... even if the RDP connection was back to the office to a support server, and then from there access any client (provided that no-one turned off the internet of course :-) Like Martin, I'm not seeing how I could make a compelling business case for this ... |
#8
| |||
| |||
|
|
New blog: nospamNebula-RnD.com/blog/tech/mv/2010/11/mv-by-phone1.html (Remove the nospam prefix above) Comments and inquiries welcome. Thanks, Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com remove.pleaseNebula-RnD.com/blog Visit PickWiki.com! Contribute!http://Twitter.com/TonyGravagno |
#9
| |||
| |||
|
#10
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |