Jump to content

kpilcher

Members
  • Posts

    15
  • Joined

  • Last visited

kpilcher's Achievements

Casual

Casual (2/7)

0

Reputation

  1. False key presses are still a problem in 4.13 using VOIP.
  2. I'm testing version 4.13 and have found that it still has the same old problems as previous versions when using VOIP. Specifically annoying for me are the following: 1. Automatically disconnects after 5 minutes and approximately 40 seconds of continuous dictation when using Callcentric VOIP provider (this was supposed to be fixed in 4.13). This is a known issue, DialDictate must provide RTP packets back to Callcentric even though there is no audio generated by DialDictate during continuous dictation. If no RTP packets are received by Callcentric, they assume DialDictate has dropped the call so they disconnect. 2. Randomly detects key presses when no key has been pressed. Probably poor DTMF detection. As you can imagine, dictation users will not put up with such problems. Have any of you been able to confirm these or other issues.
  3. I was using plain old VOIP and it was happening to me too.
  4. I was working with NCH for months, well waiting for them to help me... They finally sent me some test software which did not work. Sadly I gave up at that point. I was evaluating their software for a fairly large purchase. While I was going round and round with them I lost my opportunity The issue is relatively simple. Since the dictation conversation is one sided, ie. there is no voice activity from dialdictate. CallCentric sees this inactivity from dialdictate as a probable failure and disconnects the call after a specific time period. This is typical call handling from a lot of VOIP providers. NCH is well aware of this. It is typical for a VOIP software providers like NCH to implement one a number of defacto standard keep alive techniques to prevent this. NCH has chosen to ignore this reality, so here we are...
  5. Sorry for the delay. I'm using VOIP. No voice card.
  6. I have been testing DialDictate and have seen it, on a number of occasions during dictation, translate my voice into false key presses. Has anyone else had this problem? Is there any known solution for it? Thanks
  7. I had similar problems with DialDictate behind a Sonicwall firewall. Even though the firewall was setup correctly I got very intermittent results. DialDictate would answer sometimes and sometimes not. I finally gave up and decided to connect the DialDictate box in front of the firewall. As soon as I did, everything worked fine. The only thing I can attribute this to is that the firewall is pretty old and may not support VOIP very well. Well, and it's a Sonicwall...
  8. Sorry, correction, what happens when the dictator stops speaking for 2 minutes?
  9. What happens when the dictator pauses for 2 minutes? I believe it continues to record the silence. Not a good solution.
  10. VOIP for me. I believe this is a VOIP only problem. It seems to be due to lack of RTP keep-alive packets from DialDictate during dictation and the VOIP provider is dropping the call.
  11. After a lot of testing I have found that if the dictator periodically presses 9 (start dictating from current location) during dictation that the call will not disconnect. The people dictating won't like it but it's better than being disconnected. Let's just hope there is a real solution soon.
  12. After a lot of testing I have found that if the dictator periodically presses 9 (start dictating from current location) during dictation that the call will not disconnect. The people dictating won't like it but it's better than being disconnected. Let's just hope there is a real solution soon.
  13. I understand that a test should be a tool to provide information that could help you determine the error mode. However, the suggestion that setting all the timers to their maximum value and setting the recording threshold to the minumum value might somehow resolve the issue is not acceptable to anyone. I had a test run from the Callcentric side and they informed me that the absense of RTP packets coming back to them during dictation is the problem. They say that VOIP systems typically disconnect if one or both sides of the conversation is silent (no RTP packes) for too long. They suggest "keepalive" RTP packets or "comfort noise" to keep the connection alive. I hope that we can move forward armed with this information and get the issue resolved. It would make a lot of people very happy with your product.
  14. I am having the same issue too . I've traced the VOIP log and it is clear that Dialdictate is unilaterally dropping the call at 5 minutes and 53 or 54 seconds. I've been working with NCH support on this with no success. They are giving me the run-around asking me to perform silly tests and have silly suggestions to try to make it work. They actually suggested that I max out all the timers and remove the voice threshold! That won't fly with my customer or my MT's. I sure hope someone finds the solution soon or I'll be forced to move to another dictation platform.
×
×
  • Create New...