Re: Transporting Caller ID data to TAPI
From: kitchenman (worktops_at_ATkitchenman.co.uk)
Date: 07/07/04
- Next message: Sub: "Re: Premature Disconnection"
- Previous message: Riber: "Re: Caller ID in C#"
- In reply to:(deleted message) Pete: "Re: Transporting Caller ID data to TAPI"
- Next in thread: Pete: "Re: Transporting Caller ID data to TAPI"
- Reply:(deleted message) Pete: "Re: Transporting Caller ID data to TAPI"
- Reply:(deleted message) Pete: "Re: Transporting Caller ID data to TAPI"
- Reply: Riber: "Re: Transporting Caller ID data to TAPI"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 07 Jul 2004 23:00:48 GMT
Pete,
I missed the start of this thread
I am having real problems with CLI & BT & W2000
Is there a modem in UK the really work, I have Zoom 3025 & USR 56K message,
neither work under TAPI
-- regards dave batter www.kitchenman.co.uk www.sxmitres.info www.marks-family.co.uk www.essex-sandivers.info http://oneandone.co.uk/xml/init?k_id5568652 "Pete" <nospam@me.nut> wrote in message news:39dme09ap4uvpgvgepvok024chl836ksb3@4ax.com... > On Tue, 6 Jul 2004 16:40:49 +1000, "Riber" <riber @ > RemoveSpacesAndThis mail.com> wrote: > > >Here's an example of a Bellcore string coming in after being decoded by the > >modem 800D0108303630313132333004015088. > > I am not TAPI savey as I am here trying to find a modem that will do > (belcore) caller ID on my local telco to eventually fit into a > mini-ITX pc (as a fanless server \ answer machine \ media \ pvr \ > everything machine.) > > Are you saying that TAPI will not pass on in the NMBR or NAME field > the raw unformatted integer from which your software could then > interpret the *50 *88? > > >I find it interesting that the BT system also use the Name = P > >In the North America they get > >Nmbr = P > >Name = P > > There are advantages to the BT system but sometimes its better to go > for universality... > > >In a couple of weeks I hope to get an Intel 537EPG modem, that feature > >Global Caller ID compatibility. I very much look forward to see if this may > >make any difference at all. > > 537EPG. That sounds interesting I'll put it on my possible list. In my > case Conexant based modems look the most possible for my slightly > different belcore local exchange. > > Take a look at the Zoom External 3049C. It has 14 caller ID zones that > can be set: http://www.zoom.com/techsupport/dial_up/v92conexant.shtml > > I'm a bit warey after my own (win2k) experience with a 3025c zoom > internal but it was the only modem so far that did caller ID here > without any adjustments. > > However it is highly unusual for a modem manufacturer to give extended > information about caller ID so zoom have to be credited for this. > > See: Caller ID Command Reference: > http://www.zoom.com/documentation/dial_up/CallerID.pdf > > I suspect more 'known' brand dial-up modem manufacturers will be doing > this as well as developing independent external modems as they see > their market for dial-up slowly dwindling in the face of broadband. > > I also suspect TAPI and general modem software will have to make > significant changes to keep up (at least for the western consumers.) > > Pete --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004
- Next message: Sub: "Re: Premature Disconnection"
- Previous message: Riber: "Re: Caller ID in C#"
- In reply to:(deleted message) Pete: "Re: Transporting Caller ID data to TAPI"
- Next in thread: Pete: "Re: Transporting Caller ID data to TAPI"
- Reply:(deleted message) Pete: "Re: Transporting Caller ID data to TAPI"
- Reply:(deleted message) Pete: "Re: Transporting Caller ID data to TAPI"
- Reply: Riber: "Re: Transporting Caller ID data to TAPI"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|