https required for recordings over 2 minutes
Posted: Sat Jun 02, 2007 5:56 am
We are in the process of developing a phone-in dictation application (for doctors and lawyers) using your platform in the development environment. We're using Microsoft IIS 6 web server and "classic" Active Server Pages (ASP) scripting. Recently we experienced something strange that I thought we would run by you to see if you might have an explanation.
For weeks we were having a problem where we could do up to
a two minute recording but anything above two minutes timed out. We spent nearly four weeks and tried everything to resolve the issue, but were unsuccessful. Finally we tried changing all of the paths in our XML files to use the secure protocol, https, instead of http. This seems to have fixed the problem. This now brings up a few questions in my mind...
1. Do you have any idea why this may have solved the issue? That is, why would it record for under two minutes using http paths, but anything over two minutes needed to be secure, https?
2. We tried to set the start page (via your interface) to https, but
your interface would not accept an https URL. Why is that? This doesn't appear to be a problem though; I'm just curious.
3. We've noticed that the authority for our SSL certificate does not
show up on your certificate authority listing; and yet it is indeed
working (in development environment, at least). Do you think this might present a problem for us once we promote to production? We purchased the SSL certificate through GoDaddy.com and they use a company called Starfield Secure Certificate Authority. Will that hinder us in production? If so, would you be able to make a change on your end to support this type of certificate or is that a big deal? (That would save us the headaches and expense of getting a new certificate).
Thanks for the help.
For weeks we were having a problem where we could do up to
a two minute recording but anything above two minutes timed out. We spent nearly four weeks and tried everything to resolve the issue, but were unsuccessful. Finally we tried changing all of the paths in our XML files to use the secure protocol, https, instead of http. This seems to have fixed the problem. This now brings up a few questions in my mind...
1. Do you have any idea why this may have solved the issue? That is, why would it record for under two minutes using http paths, but anything over two minutes needed to be secure, https?
2. We tried to set the start page (via your interface) to https, but
your interface would not accept an https URL. Why is that? This doesn't appear to be a problem though; I'm just curious.
3. We've noticed that the authority for our SSL certificate does not
show up on your certificate authority listing; and yet it is indeed
working (in development environment, at least). Do you think this might present a problem for us once we promote to production? We purchased the SSL certificate through GoDaddy.com and they use a company called Starfield Secure Certificate Authority. Will that hinder us in production? If so, would you be able to make a change on your end to support this type of certificate or is that a big deal? (That would save us the headaches and expense of getting a new certificate).
Thanks for the help.