SafeBoy

Sadly ... the former is the case. The incoming call itself is cutting off after this short period of 24-26 seconds ... I *sometimes* can get 44sec but this is an anomaly, rather than a pattern. After making "simulations" that work perfectly and will record past this, and then a real incoming voip call only lasting only this short time ... is very frustrating. I have now made approximately 50 calls to myself - *sigh* - to get this problem nailed ... but not having any success ... In addition to this ... I had this on a call log from today ... *MY* test call ... 03:32:39 Command - Leave Message 03:32:39 Leave Message for Mailbox: Gang Show 03:32:39 Play system prompt: RecordTone 03:32:39 Recording File: C:\Documents and Settings\All Users\Application Data\NCH Swift Sound\IVM\MailBoxes\Gang Show ICM000085.wav 03:33:04 Caller pressed key 03:33:04 Call has disconnected 03:33:05 Call disconnected 03:33:05 Sending Email to: Pressed Key ... HUH ??? ... what the dickens ... I had the phone sitting in front of the tv ... NOBODY pressed any key... NCH ... PLEASE FIX THIS PROBLEM ?? And as a final check ... if I make an incoming call without the IVM running .. yes I can talk as long as I want to ... Any ideas on this would be appreciated ... I have even adjusted the setting for this (to -40db) in the registry ... all to no avail ...

Ok ... I've used this program for a while now ... I would go so far as to say, I"m comfortable in its use even ... I've made multiple numbers of real test calls from my pstn number to my voip number (which the ivm software is installed to take those calls at my pc) .. via a router box ... I'm tired now ... I just want a solution that works ... I'll even edit the registry, or ini files ... but I WANT MORE THAN 25sec of recorded message time for an incoming call ... I'm losing money in my business bcs of it and I need a fix ... real bad ... I've adjusted and fiddled and messed around with ... and I cannot make it give the incoming call more than 24-26sec ... HEEEEEEEEELLLLLLLLLLLPPPPPPPPPP!!!!!!!!!!!!! ... I'm going madd ... Please ...

woah .... talk about a FAST reply ... I am retrying all combinations of these advanced settings, including reset the router to a STATIC ip ... which I found was a little more techy than I thought ... I'll update as soon as I get it figured ... esentially, it seems to be a "port forwarding" issue ... as outlined in another post ... but we will see how it all goes Tas

I'm recving this message, unable to auto detect ... and it is beginning to bug the irrits out of me Your solution, though helpful in parts, isn't detailed enough ... ... if anybody else has a detailed solution to this issue, it would be HEAPS appreciated Cheers!