Problem occurred while setting port timeouts

Questions, problems, and other issues for Ascendis Caller ID that aren't covered by the other forums.
Post Reply
bwm
Posts: 11
Joined: Tue Sep 15, 2009 9:31 am

Problem occurred while setting port timeouts

Post by bwm »

The Ascendis software has stopped processing incoming calls. All was working fine until I made an outgoing skype call (which was monitored). No calls were logged after that. I can't tell what the triggering cause might have been (skype call, Microsoft black tuesday upgrades at roughly the same time). This is a Win7Enterprise machine.

The modem responds to diagnostic queries under device manager and shows 'this device is working properly'.

A dialog box appears with a 60 second time out when Ascendis starts informing me that:

"A Problem occurred while setting port timeouts: Incorrect function". It is also in the line montor log (below).

Things that haven't worked: Powering everything off and restarting. Rebuilding the device list in Ascendis and selecting only the modem (not skype). Installing current beta software.

Any suggestions on possible causes/solutions?

03/10/2010 18:15:15.792 - Found 6 TAPI lines
03/10/2010 18:15:15.854 - [4168:Zoom v92 Data Fax Voice Modem]
03/10/2010 18:15:15.854 - [4168:Zoom v92 Data Fax Voice Modem] Info for line 0:
03/10/2010 18:15:15.854 - [4168:Zoom v92 Data Fax Voice Modem] Name = Zoom v92 Data Fax Voice Modem
03/10/2010 18:15:15.854 - [4168:Zoom v92 Data Fax Voice Modem] Bearer modes = LINEBEARERMODE_VOICE, LINEBEARERMODE_PASSTHROUGH
03/10/2010 18:15:15.870 - [4168:Zoom v92 Data Fax Voice Modem] Media modes = LINEMEDIAMODE_UNKNOWN, LINEMEDIAMODE_INTERACTIVEVOICE, LINEMEDIAMODE_AUTOMATEDVOICE, LINEMEDIAMODE_DATAMODEM
03/10/2010 18:15:15.870 - [4168:Zoom v92 Data Fax Voice Modem] Addresses = 1
03/10/2010 18:15:15.870 - Will NOT open line id 0 because device will not be accessed via TAPI
03/10/2010 18:15:15.870 - [4168:AgileVPN]
03/10/2010 18:15:15.870 - [4168:AgileVPN] Info for line 1:
03/10/2010 18:15:15.870 - [4168:AgileVPN] Name = AgileVPN
03/10/2010 18:15:15.870 - [4168:AgileVPN] Bearer modes = LINEBEARERMODE_DATA
03/10/2010 18:15:15.870 - [4168:AgileVPN] Media modes = LINEMEDIAMODE_UNKNOWN, LINEMEDIAMODE_DIGITALDATA
03/10/2010 18:15:15.870 - [4168:AgileVPN] Addresses = 1
03/10/2010 18:15:15.870 - Will NOT open line id 1 because options say to skip it
03/10/2010 18:15:15.886 - [4168:WAN Miniport (L2TP)]
03/10/2010 18:15:15.886 - [4168:WAN Miniport (L2TP)] Info for line 2:
03/10/2010 18:15:15.886 - [4168:WAN Miniport (L2TP)] Name = WAN Miniport (L2TP)
03/10/2010 18:15:15.886 - [4168:WAN Miniport (L2TP)] Bearer modes = LINEBEARERMODE_DATA
03/10/2010 18:15:15.886 - [4168:WAN Miniport (L2TP)] Media modes = LINEMEDIAMODE_UNKNOWN, LINEMEDIAMODE_DIGITALDATA
03/10/2010 18:15:15.886 - [4168:WAN Miniport (L2TP)] Addresses = 1
03/10/2010 18:15:15.886 - Will NOT open line id 2 because options say to skip it
03/10/2010 18:15:15.886 - [4168:RAS PPPoE Line]
03/10/2010 18:15:15.886 - [4168:RAS PPPoE Line] Info for line 3:
03/10/2010 18:15:15.886 - [4168:RAS PPPoE Line] Name = RAS PPPoE Line
03/10/2010 18:15:15.886 - [4168:RAS PPPoE Line] Bearer modes = LINEBEARERMODE_DATA
03/10/2010 18:15:15.901 - [4168:RAS PPPoE Line] Media modes = LINEMEDIAMODE_UNKNOWN, LINEMEDIAMODE_DIGITALDATA
03/10/2010 18:15:15.901 - [4168:RAS PPPoE Line] Addresses = 1
03/10/2010 18:15:15.901 - Will NOT open line id 3 because options say to skip it
03/10/2010 18:15:15.901 - [4168:PPTP]
03/10/2010 18:15:15.901 - [4168:PPTP] Info for line 4:
03/10/2010 18:15:15.901 - [4168:PPTP] Name = PPTP
03/10/2010 18:15:15.901 - [4168:PPTP] Bearer modes = LINEBEARERMODE_DATA
03/10/2010 18:15:15.901 - [4168:PPTP] Media modes = LINEMEDIAMODE_UNKNOWN, LINEMEDIAMODE_DIGITALDATA
03/10/2010 18:15:15.901 - [4168:PPTP] Addresses = 1
03/10/2010 18:15:15.901 - Will NOT open line id 4 because options say to skip it
03/10/2010 18:15:15.917 - [4168:SSTP]
03/10/2010 18:15:15.917 - [4168:SSTP] Info for line 5:
03/10/2010 18:15:15.917 - [4168:SSTP] Name = SSTP
03/10/2010 18:15:15.917 - [4168:SSTP] Bearer modes = LINEBEARERMODE_DATA
03/10/2010 18:15:15.917 - [4168:SSTP] Media modes = LINEMEDIAMODE_UNKNOWN, LINEMEDIAMODE_DIGITALDATA
03/10/2010 18:15:15.917 - [4168:SSTP] Addresses = 1
03/10/2010 18:15:15.917 - Will NOT open line id 5 because options say to skip it
03/10/2010 18:15:15.917 -
03/10/2010 18:15:15.917 - Opened 0 of 6 lines through TAPI
03/10/2010 18:15:15.932 -
03/10/2010 18:15:15.932 - Looking for serial mode devices to open
03/10/2010 18:15:15.932 - Found 9 past and current devices
03/10/2010 18:15:15.932 -
03/10/2010 18:15:15.932 - Opening modem "Zoom v92 Data Fax Voice Modem" on COM1
03/10/2010 18:15:15.932 - Opened 1 devices in serial mode
03/10/2010 18:15:15.932 - [5620:Zoom v92 Data Fax Voice Modem:COM1] Problem occurred while setting port timeouts: Incorrect function
03/10/2010 18:15:16.042 - [5620:Zoom v92 Data Fax Voice Modem:COM1] Attempting to enable verbose result codes
Bill Root
Site Admin
Posts: 1025
Joined: Mon Jan 19, 2004 1:29 pm
Location: Perrysburg, OH
Contact:

Re: Problem occurred while setting port timeouts

Post by Bill Root »

03/10/2010 18:15:15.932 - [5620:Zoom v92 Data Fax Voice Modem:COM1] Problem occurred while setting port timeouts: Incorrect function
The code that checks for and reports this error has not been changed in ages, and it's done right after opening the serial port. Because of this, I would suspect a Windows update is the culprit.

Is your serial port a real one or a USB-to-serial converter? If the latter, Windows might have updated the driver. Windows proposed newer drivers for one of mine, but the new driver crashed and took down Windows. (In my case, Windows selected one based on the USB-to-serial converter chipset, instead of the latest one by the device manufacturer, which worked).

In any case I changed the code to continue initializing the modem even if it can't set the comm port timeouts. This might move the failure to a different point, in which case I may need to make more changes. Even if the driver has a problem, if Ascendis Caller ID can be made to work, that may avoid problems for other users.

I will send a link for the new version via email.


Finest regards,
Bill Root
Ascendis Software
bwm
Posts: 11
Joined: Tue Sep 15, 2009 9:31 am

problem not with Ascendis

Post by bwm »

Some further investigation showed the problem was with the installation of some 3rd party software (not Windows update) that wasn't win7 compatible. Ascendis and Win7Enterprise-32bit work just fine.
Post Reply