YAC Caller ID set-up (1 Viewer)

[MrMad]

There are several standards for caller id:

• Bellcore (now Telcordia) is used in Australia, Canada, China, Hong Kong, New Zealand, Singapore and USA
• BT and CCA standards in the UK
• DTMF-based in Brazil, Belgium, Denmark, Finland, Iceland, India, Netherlands, Saudi Arabia, Sweden & Uruguay
• ETSI in Eire, France, Germany, Norway, Italy, Spain, South Africa and Turkey
• NTT standard in Japan
• "USSR ANI-hacking" in the former Soviet Union

I'm guessing your modem does not support the BT or CCA standard but rather the Bellcore standard, that's why you can't get it to work.

 

[HappyTalk]

I'm guessing your modem does not support the BT or CCA standard but rather the Bellcore standard, that's why you can't get it to work.

Yes I have come to the same conclusion. Both modems respond OK to 'AT+VCID=1' following this troubleshooting guide http://www.beiley.com/acallerid/enable.html they report the ringing phone but no caller id info.

Further to this trying to locate a modem that WILL work with BT caller-ID is not easy. Even this caller ID FAQ http://www.ainslie.org.uk/callerid/cli_faq.htm#Q_18 that IS mainly from a UK perspective is pretty vague when it comes to naming names.

In an ideal world I'd plug a modem in and load up an MP plugin that would offer caller-id, act as an answerphone service as well as allowing a PC to record/log ALL calls made/received. If anyone knows any readily available 'cheap' (preferably usb) modems or other devices that can handle BT caller-id (phone call recording would be nice), please let me know

thanks

 

[reado]

I have a US robotics message modem that works great with uk(BT) caller id.
How do you set the YAC server to initialise the caller ID part of the modem, ie make it send AT#CID=1 to the modem when it starts.
I have tried this in hyperterminal and saved it (&W) but it dosent seem to save the caller id settings so it needs to be sent by the program??
Cheers
Paul

 

[marklp77]

HappyTalk, sorry I didn't respond earlier to this post - I didn't get a notification email... Can you provide the link to Moullas's topic - I'll reference that in the Wiki.

You forgot to mention in wiki that you need to set the ip of your MP machine in listeners on Yak. I guessed it after about 30 mins. I then noticed it IS written at top of this topic by Moullas.

You might also want to add to wiki that if you are sending YAK info over your LAN from a different machine then you will probably need to open TCP port 10629 on your firewall. For Windows Firewall, you run SecurityCentre (Start Menu|Programs|Accessories|System Tools|Security Centre) At bottom launch 'Windows Firewall', then goto second tab called exceptions, hit 'Add Port' and set:-
Name = YAC Port 10629
Port = 10629
TCP = On
Then Hit 'Change Scope' and set it to 'My network (subnet) only' as you don't want the whole internet accessing that port.


I cannot get YAC to ID my phone line anyway, tried 2 diff pc's with 2 diff modems, no joy caller id works fine on house phones though. I guess modems dont have caller id, though are pretty modern (one is laptop modem only 1 month old)

 

[HappyTalk]

I have a US robotics message modem that works great with uk(BT) caller id.
How do you set the YAC server to initialise the caller ID part of the modem, ie make it send AT#CID=1 to the modem when it starts.
I have tried this in hyperterminal and saved it (&W) but it dosent seem to save the caller id settings so it needs to be sent by the program??
Cheers
Paul

I would expect you just go to control panel | phone and modem options | modems | properties | advanced | extra initialisation commands and pop it in there.

What is the manufacturers part number for your U.S Robotics message modem? Is it USB or serial? How old is it?

Re Marklp77 - Moullas' was the second post on this thread.

 

[reado]

I have tried adding the extra commands to control panel | phone and modem options | modems | properties | advanced | extra initialisation commands but it didnt seem to work, I will double check again tonight.
The modem is serial I'm afraid, bought it off ebay, as I read somewhere that from about 1998 onwards these modems supported caller ID and as long as it was bought in the UK Should work with BT caller ID, I will post the part number on here for you tonight as well.

Do you know at what stage that initialisation in the extra initialisation commands would get sent to the modem?

Also does YAC recognise UK (BT) caller ID?
Thanks
Paul

 

[reado]

My us robotics message modem that does work with UK (BT) caller ID has on the back..
Assembled in Hungary
138NL8TA0QY7
71-245668-01

 

[HappyTalk]

OK, I got a couple of old us robotics message modems, one of them didn't have caller-id (015625-00), but the one from 1998 did (245625-01). However it took a good 30 hours of googling and reading and finally resorting to random guessing to get it working.

If like me you get some sort of response in hyperterminal by following this guide http://www.beiley.com/acallerid/enable.html but then cannot get Yac to respond for love nor money then maybe this will help. The suggestion after hyperterminal shows the info and YAC doesn't respond then is to manually fix the driver inf file as in this guide http://www.beiley.com/acallerid/fixdriver.html . Now if that still doesn't work then here's how I got it working. I followed that driver fix tutorial but added this instead.

HKR, Responses, "ING<cr><lf><cr><lf>", 1,08,00,00,00,00,00, 00,00,00,00
HKR, Responses,"<cr><lf>TIM", 1,94,0,0,0,0,0,0,0,0,0
HKR, Responses,"ATE = ", 1,93,0,0,0,0,0,0,0,0,0
HKR, Responses,"MBR = ", 1,95,0,0,0,0,0,0,0,0,0

This was based on my modem giving a response like this in the c:\windows\ModemLog_U.S. Robotics 56K Pro Msg Ext.txt file. (this file also has a 'Modem inf path:' line in it that tells you what inf file it's using so you know the one to modify, then reload driver)

11-14-2006 12:30:54.906 - Recv: R
11-14-2006 12:30:54.906 - Unknown Response
11-14-2006 12:30:54.906 - Recv: ING<cr><lf><cr><lf>
11-14-2006 12:30:54.906 - Unknown Response
11-14-2006 12:30:54.921 - Recv: D
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: ATE = 1
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: 1
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: 14<cr><lf>TIM
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: E
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv:  = 1230
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: <cr>
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: <lf>
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: N
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: MBR = 0
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: 7
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: 111-111
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: 1
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:54.921 - Recv: 11<cr><lf>
11-14-2006 12:30:54.921 - Unknown Response
11-14-2006 12:30:56.937 - Recv: <cr><lf>RING<cr><lf>
11-14-2006 12:30:56.937 - Interpreted response: Ring
11-14-2006 12:30:56.937 - TSP(0000): LINEEVENT: LINE_NEWCALL
11-14-2006 12:30:56.937 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
11-14-2006 12:30:56.937 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
11-14-2006 12:30:59.937 - Recv: <cr><lf>RING<cr><lf>
11-14-2006 12:30:59.937 - Interpreted response: Ring
11-14-2006 12:30:59.937 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
11-14-2006 12:31:11.937 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
11-14-2006 12:31:11.937 - TSP(0000): Closing Call

If yours doesn't work by looking at the modem log file you may, like me be able to guess the correct values to insert. It took me forever to guess my way to using these values when I'd all but given up. Having modified the inf file and updated the driver using it I now get this response in the modem log file:-

11-14-2006 18:01:11.015 - Recv: R
11-14-2006 18:01:11.015 - Interpreted response: Informative
11-14-2006 18:01:11.015 - Recv: ING<cr><lf><cr><lf>
11-14-2006 18:01:11.015 - Interpreted response: Ring
11-14-2006 18:01:11.015 - TSP(0000): LINEEVENT: LINE_NEWCALL
11-14-2006 18:01:11.031 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
11-14-2006 18:01:11.031 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
11-14-2006 18:01:11.031 - Recv: DATE =
11-14-2006 18:01:11.031 - Interpreted response: DATE
11-14-2006 18:01:11.031 - Recv:  1114<cr><lf>
11-14-2006 18:01:11.031 - Recv: TIME =
11-14-2006 18:01:11.031 - Interpreted response: TIME
11-14-2006 18:01:11.031 - Recv:  1800<cr><lf>
11-14-2006 18:01:11.031 - Recv: NMBR =
11-14-2006 18:01:11.031 - Interpreted response: NMBR
11-14-2006 18:01:11.031 - Recv:  07111-111111<cr><lf>
11-14-2006 18:01:13.078 - Recv: <cr><lf>RING<cr><lf>
11-14-2006 18:01:13.078 - Interpreted response: Ring
11-14-2006 18:01:13.078 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
11-14-2006 18:01:25.078 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
11-14-2006 18:01:25.078 - TSP(0000): Closing Call

 

[HappyTalk]

Hmmm well after all the time, hassle and hoops jumped through to get it working, the mp yac plugin pops up the caller id about 15 seconds after the phone rings. After much experimentation I tracked this down to the entry in the Yak Listeners dialog which I'd set to localhost which for some reason seems to cause this lag in the Yac plugin message (though the Yac listener itself messages without delay when set to localhost). Setting it to the real IP of the machine (10.0.0.10 in my case) and the lagging problem goes away.

If watching TV when it pops up the message and you have to click ok to clear it, whereupon another window pops up with the channel icon in it? so another remote press of OK is required. The message ought to disappear after about 10 seconds automatically without popping up a second window.

 

[ArnoldGoat]

Is it possible to alter the duration of the YAC pop-up when a call arrives? It's a bit quick for me to read before it disappears!