CallerID problem with a USR modem

[Krass]

I was in a thread with someone trying to help me out....
http://www.vbforums.com/showthread.p...59#post3438959

...Thought I'd post here to reach more people. Maybe someone with the same hardware as me.

This is my brand new internal PCI modem:
http://www.usr.com/download/datasheets/oem/3092-ds.pdf

I've loaded HyperTerminal, typed 'AT', echoed "OK". Typed AT+VCID=1, echoed "OK", but then when phone call comes in, I only get the "RING"s echoed. (same problem as many ppl, it seems).

I tried AT+VCID=? to display Caller ID settings available and it echoed "+VCID: 0,1,2". I tried =0, =1 and =2, all echoed "RING"s only.

If anyone has an idea of what's going wrong, I'd greatly appreciate some help. I HyperTerminal session was configured to use COM3, which is the good COM using the modem.

Thanks for any comment.

(Edit: The phone cable going to my modem is passing through a phone-line filter like all my other phones receiving callerid information. This is needed since I'm using a DSL isp. Should I try my luck and avoid using the filter???)

(Edit2: Tried changing country settings of the modem to United States - didn't help (was Canada))

[Krass]

...looks like hours of googl'ing didn't help me out.

(yup, that's a *bump*)

[westconn1]

here at least caller id (for landlines) is a feature provided by the telcos at extra cost, so i at least don't have it, 2 points from that, i assume that you do have caller id enabled? and i can not test any caller id settings

seems like you should be in a modems forum to get more help with this problem

[CDRIVE]

I followed your last thread on this topic but I sat on the sidelines as a spectator. I usually help people with MSComm questions but I don't have caller ID so I can't test any Comm code for CID.

Here's a question for you. Have you talked to anyone that has actually printed caller ID to a Hyper Terminal console? Your Modem may be Caller ID compatible but is Hyper Terminal? This is a TAPI Caller ID OCX to use with VB and probably MSComm. You may also want to google caller id using visual basic.

[CDRIVE]

I found this on PSC.

[Krass]

I already tried that one from PSC. Unfortunately, the .ocx was not packaged in and is missing. Many people seems to have complained about it.

I havn't talked to anyone actually printed callerid info to hyperterminal. But on all the sites I've visited, it looks like many people have success this way.

The link you provided didn't seem to work neither. (the link yes, the app no)

I'm starting to think I might need to know the exact codes emitted by my phone line (actually, by my phone distributor).

I am of course callerid enabled. All my phones are showing the informations.

Not too sure where to aim next. Maybe I'll give it a try in a modem forum.

(Edit: my phone provider is BELL CANADA, region of montreal, if that can be of any help)

[westconn1]

I already tried that one from PSC. Unfortunately, the .ocx was not packaged in and is missing. Many people seems to have complained about i

the missing ocx were not required for caller id, just take them out or
add from components (yours are just a different version)
i can run the project (with some errors), but i can not test the for caller id, none of the feedback on psc said it did not work

[CDRIVE]

I don't know what the author PSC CID was thinking when he/she wrote this

Private Sub Command2_Click()
   End
End Sub

but you're going to want to re-write it properly!

[Krass]

I was able to test that piece of code from PSC. It didn't work. Like all others apps I tried out there.

Anyway, everyone suggests to start by making it work in hyperterminal since we don't have to suspect malfunctionning code or else. This seems to be a 'go' for most people. I've been told that by using hyperterminal, it won't even deal with the .inf of the hardware and will simply echo everything that's received.

On my side, I still only get "RING"s. I even took off all those splitters/filters and run the line straight in my modem (DSL filters on and off).

I do pay for the service and it does work on my regular phones.
That particular modem is confirmed to be CallerId enabled. (the initializing string does work anyway)

I'm beginning to think my questions should be forwarded to my phone company, but I don't think I should expect an answer from those guys at 'Bell Canada'.

... and I thought this was going to be 'plug-n-play'

[CDRIVE]

I was able to test that piece of code from PSC. It didn't work. Like all others apps I tried out there.

"Didn't work" isn't descriptive enough. Please elaborate.
EDIT: Have you tried using 'Advanced Initialization Commands' in the device mgr/modem?

[Krass]

Well, it's actually the same behaviour as in hyperterminal. It notices there's a phone call coming in, but won't give any callerid info.

Again, in the application, the com port and the CID initiliazation string are confimed to work (+VCID=1 - "OK").

The product description (see first post) confirms this modem handles Callerid (probably most new modems does).

I read somewhere that callerid info is a chunk of digital information (?) sent between the 1st and the 2nd ring. Maybe is my phone distributor handling/using/sending that information a different way ?!... (remember that all my phones shows CID efficiently).

Bell Canada. Montreal.

Thanks.

[CDRIVE]

I edited my last post. Please read.

[Krass]

I did try "AT+VCID=1" in there.

Didn't help at all. And I didn't know what other 'Advanced Initialization Commands' I could have tried there.

Preferences:
Port speed: 115200
Data Protocol: Standard EC --- (Disabled, Forced EC avail)
Compression: Enabled --- (disabled)
Flow control: Hardware --- (Xon/Xoff, None)

In advanced settings for Com3, I got this enabled:
"Use FIFO buffers (requires 16550 compatible UART)" - I don't know much about that but I have the feeling that ain't very useful to my problem

Thanks for replying...

[Krass]

I think the problem might be out of reach for me.

The reason I'm saying this is that I had a dell laptop and an hp laptop near me and I tried the callerid on both. HyperTerminal only echoed "OK" on all RINGS. And on both laptops, the "CID" initializating strings was received well and echoed "OK".

Could I have had 2 modems that didn't handle CID? Unlikely if you ask me. And the 3rd one I just bought also not working even tho its description mentions it handles CID..

.... Trying to narrow possibilities here ....

[CDRIVE]

I sincerely wish I could help you more but being without CID service I'm helpless to test any code or ideas. FYI,(PSC app): When you strip away all the superfluous and unrelated code that's not related to MSComm you will see that the Comm code is SOP and basic. The only item in there related to CID is the CID AT Commands found in Option1 through 3 events.

Warning to others using that code from PSC: The author used '+' in some of his code where '&' should have been used. He also used the verboten 'End' statement and he did not write any code in the Query_ Unload or Unload Events to close the port when the program is closed! Bad, Bad, Bad and exceedingly BAD!

[CDRIVE]

Maybe it's a Canadian thing ...Aeh?

[westconn1]

contact usr

[westconn1]

i found this when i was doing some research, on other telephony product

Caller ID Scheme Select the Caller ID Scheme to suit the standard of different area.
• Bellcore (North America)
• CID (Canada)
• DTMF (Brazil)
• DTMF (Denmark)
• DTMF (Sweden)
• ETSI-FSK (France, Germany, Norway, Taiwan, UK-CCA)
• ETSI-DTMF (Finland, Sweden)

not sure what it means exactly, but could be relevant

[CDRIVE]

ETSI: ( European Telecommunications Standards Institute ).
DTMF: ( Dual Tone Multi Frequency ) This is the dialing standard that replaced the rotary dial which was actually an early primitive digital technique. This would mean that this CID standard would send DTMF in between the ring signals. If that's the case, any DTMF decoder could read the CID. This would also be audible on the phone line (between the ring signals) just like when you dial a phone.
FSK: ( Frequency Shift Keying ). Used in the USA for FAX and Radio Teletype. Dates back to the Electromechanical Teletype machines.

Here's some info that makes reference to Canadian standards and how to setup your modem . Read!

EDIT: In case you can't find it on the page, it says they recommend setting a US made modem used in Canada to ETSI.

[yosef_mreh]

try to use teletext OCX.
it is not free but u can download demo OCX

[plawlor]

I hate to break this to you, but your modem supports "Type 2" Caller ID only. I have the exact same setup as you and am a Bell Canada customer in PEI. After 2 days of searching the web, I finally found this info:

http://www.usr.com/download/datashee...70/5670-ds.pdf

Look in the fine print on the last page. We need "Type 1" Caller ID. I'm having a hell of a time finding a modem that actually supports "Type 1". If I find one, I'll let you know.

Peter