ISDN conectivity via AnywhereUSB

Hello

We’ve tested to connect ISDN Modem miniVigor128 from Draytek to an AnywhereUSB5 box. But it doesn’t work.
What are the problem with connecting Modems or ISDN TAs to the AnyweherUSB box?

I found only 2 analog modems working correctly with AnywhereUSB but no ISDN Solution?

Is there a know ISDN Solution that my work with virtual mashines (VMware or Hyper-V)?

Regrads, Thomas

Download and run the AnywhereUSB Check Utility from the PC that has the ISDN Modem miniVigor128 from Draytek attached to it (directly, not through the AnywhereUSB) and let me know if it’s listed as Compatible or not.

http://ftp1.digi.com/support/utilities/awusbcheck.exe

hi,
3 USB devices found.
No incompatible devices found.
Compatible devices found:
DrayTek miniVigor for Windows X64-based systems VID = 0x0675 PID = 0x1688
DrayTek miniVigor for Windows X64-based systems VID = 0x0675 PID = 0x1688
USB Composite Device VID = 0x413C PID = 0x0000

The checktool found that modems should be compatible. But if I connect it via the AnywhereUSB box, I got this bluescreen error

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 14.09.2009 15:56:30
Event ID: 1001
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80001a834d8, 0xfffff880021d1748, 0xfffff880021d0fa0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 091409-15787-01.
Event Xml:

With the DrayTek miniVigor connected directly to the PC, run the AnywhereUSB Viewer Utility, maximize that window, highlight the DrayTek miniVigor on the left, and upload a screen capture. If all of the information on the right isn’t shown, scroll down and take another screen capture, if needed.

Here is the capture of AnywhereUSB viewer for DrayTek miniVigor (a screen print is attached as jpg file).

Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x02
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0675
idProduct: 0x1688
bcdDevice: 0x0100
iManufacturer: 0x01
iProduct: 0x01
iSerialNumber: 0x01
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: Full
Device Address: 0x01
Open Pipes: 7

Endpoint Descriptor:
bEndpointAddress: 0x01
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x81
Transfer Type: Interrupt
wMaxPacketSize: 0x0040 (64)
bInterval: 0x04

Endpoint Descriptor:
bEndpointAddress: 0x02
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x82
Transfer Type: Interrupt
wMaxPacketSize: 0x0040 (64)
bInterval: 0x04

Endpoint Descriptor:
bEndpointAddress: 0x03
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x83
Transfer Type: Interrupt
wMaxPacketSize: 0x0040 (64)
bInterval: 0x10

Endpoint Descriptor:
bEndpointAddress: 0x84
Transfer Type: Interrupt
wMaxPacketSize: 0x0040 (64)
bInterval: 0x04

Well, it looks like that modem is compatible in the sense that’s it’s not an “isochronous” device like I suspected it might be.

The source of the problem is something else, apparently.

Tell me, exactly when does the bluescreen happen? As soon as you connect the modem to the AnywhereUSB? Or during the driver installation procedure? Also, what is the frequency of the bluescreen? Does it always happen, or only sometimes?

Yes, please upload the memory dump to our FTP site. Create a new folder called “vadtho” and upload it there.

Host name: ftp://ftp1.digi.com
Username: austin
Password: !15st3n!

Be sure the system is configured for a “Complete” memory dump.

Frist of all, many thanks for your assistant in this case.

I’ve recraeted the bluescreen. It happens when connecting the Modem to the AnywhereUSB box to an running System or if you connect the AnywhereUSB Box to the System with already attached Modems at it’s ports.

I’ve uploaded the memory dumps to your ftp site the file name is vadtho_dump_sysdata.zip

Here are more other details systemlog error and capture of AnywhereUSB viewer for DrayTek miniVigor connected to AnywhereUSB box (a screen print is attached as jpg file).

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.18.10
Locale ID: 2055

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80001AEAA83
OS Version: 6_1_7600
Service Pack: 0_0
Product: 18_3

Files that help describe the problem:
C:\Windows\Minidump\091709-11746-01.dmp
C:\Users\lagadmin\AppData\Local\Temp\2\WER-91868-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Log Name: System
Source: Application Popup
Date: 17.09.2009 13:03:56
Event ID: 56
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: CH-BiCAAP02.lag.wan
Description:
Driver AWUSB returned invalid ID for a child device (USB_ISDN_TA_____).
Event Xml:

56
2
0
0x80000000000000

4290
System
CH-BiCAAP02.lag.wan





AWUSB
USB_ISDN_TA_____
000000000300280000000000380004C000000000380004C000000000000000000000000000000000

Regrads, Thomas

AnywhereUSB viewer if DrayTek miniVigor connected to AnywhereUSB box:

Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x02
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0675
idProduct: 0x1688
bcdDevice: 0x0100
iManufacturer: 0x01
iProduct: 0x01
iSerialNumber: 0x01
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed: Full
Device Address: 0x02
Open Pipes: 1

Endpoint Descriptor:
bEndpointAddress: 0x00
Transfer Type: Control
wMaxPacketSize: 0x0008 (8)
wInterval: 0x0000
bSyncAddress: 0x00

Hello Jeremy

Could you see what is causing the problem in the dumpfiles?

I have a contact from draytek support if it may help to communicate directly with the manufacture of the miniVigor128 ISDN modem?

Do you see a chance to get this problem fixed or shuld we’ve a look for an other solution?

Thanks and Regards, Thomas

Thomas,

I will e-mail you about this shortly.