[RESOLVED] Modem, <DLE> Data-Link Encapsulation
I'm programming in VB6, I'm trying to make an ansering machine.
I have a modem that keeps giving me problems:
AOpen FM56-PX 56K V.92 PCI Modem
http://www.vbforums.com/
It supports Caller ID, and Voice.
After I installed it, Caller ID would not work, and it would not even detect the phone ring... Voice worked fine, and <DLE> worked fine.
FYI: <DLE> (Data-Link Encapsulation, or Data Link Escape) is a byte delimiter (ASCII 16) that the modem returns in Voice mode telling me a special message (detection of dial tone, detection of phone numbers, basically all phone sounds). I used to get "<DLE>1<DLE>~" characters when you press #1 on the phone for example.
So, Caller ID did not work, and it would not report "RING" when I was getting a phone call.
I got upset, I bought a new modem US Robotics, but unfortunatelly it did not had voice (the seller people told me it had voice), so I returned it.
I put back the old AOpen modem... and all of a sudden Caller ID works !!
It detects Caller ID ! ... cool... guess what.... now I don't get <DLE> reporting !
Arggg :mad: :( stupid modem !!!
So, anyone knows maybe there is a setting to enable <DLE> reporting ?
Anyone had this problem ?
how to fix it ??
I'm trying to get this modem to work (perfectly) for like 3-4 weeks now....
Re: Modem, <DLE> Data-Link Encapsulation
http://vip.aopen.com.tw/forum/viewme...essageID=77292
http://vip.aopen.com.tw/forum/viewme...essageID=47449
Thats about all I could find about it, and it won't be much help. Read a few places where people have been having trouble with it on XP systems, but nothing too specific to this, just dialing up to a remote ISP...
P.S. I hate working with modems... hard to find good documentation for them...
Re: Modem, <DLE> Data-Link Encapsulation
I got it to work
Before for some reason I always got the <DLE> at the beginning of the buffer, and I made my program check if the first character is the <DLE>.
Now, it's mixed with everything else, so I have to do an InStr to search if there is a <DLE> character in the data.
Took me a while to figure it out...