I know this is an old message to respond to but perhaps the web interface of your ATA spits out the last caller. I have a PAP2 and was able to whip up something in bash that spat out the last incoming call caller id. 

On Oct 26, 2012, at 11:37 AM, Ben Griffith wrote:

I also have the HT-486, but I haven't tried to integrate it into MH.  It has the capability to log to a log server.  I have a Linux computer set up as a log server and both my HT-486 and my router (running openwrt) send their logs there.  Caller-ID info is logged in a format that is human readable.  I don't know how the format compares to what MH is expecting, but this might be a better alternative than using a modem.

-Ben


On Thu, Oct 25, 2012 at 9:36 AM, H Plato <hplato@gmail.com> wrote:
Its weird that it seems to work once on startup. I'm going to try and
resend the modem init commands after a successful speech event and see
if that helps.

Sent from my mobile device.

On 2012-10-23, at 1:02 PM, Lieven Hollevoet <lieven@lika.be> wrote:

> Hi,
>
> I don't think adding more debugging printing to the interface code will help you. As far as my experience goes, the number info is never output from the modem because for one reason or the other the modem does not pickup the CID info (as you can see in the debug output indeed).
>
> Kind regards,
> Lieven.
>
> Op 23-okt.-2012, om 04:58 heeft H Plato <hplato@gmail.com> het volgende geschreven:
>
>> I changed the CID type to Bellcore (NorthAmerica), called with my cell phone, and got an announcement!  Then an hour later, another call came through with no data. Arrr.
>>
>> To try and see more data, I added prints to  my local Telephone_Interface.pm:
>>
>> sub check_for_data {
>>   for my $port (@list_ports) {
>>       if (my $data = $main::Serial_Ports{$port}{data_record}) {
>>           $main::Serial_Ports{$port}{data_record} = undef;
>>                               # Ignore garbage data (ascii is between ! thru ~)
>> print "Phone raw data: $data.\n" if $main::Debug{phone};
>> print "Caller_id_data{$port} raw data: $caller_id_data{$port}" if $main::Debug{phone};
>>           $data = '' if $data !~ /^[\n\r\t !-~]+$/;
>>           $caller_id_data{$port} .= ' ' . $data;
>>           print "Phone data: $data.\n" if $main::Debug{phone};
>> print "Caller_id_data{$port} data: $caller_id_data{$port}" if $main::Debug{phone};
>>
>> .hone raw data:
>> .RINGPhone data: ne1} raw data:  ATE1V1X4&C1&D2S0=0#CID=1 OK
>> Phone raw data: RING. data:  ATE1V1X4&C1&D2S0=0#CID=1 OK
>> Phone data: RING.ne1} raw data:  ATE1V1X4&C1&D2S0=0#CID=1 OK
>> RINGSetting Telephony_Interface object Line1 to ring.OK
>> .hone raw data:
>> .RINGPhone data: ne1} raw data:  ATE1V1X4&C1&D2S0=0#CID=1 OK
>> Phone raw data: DATE = 1022. ATE1V1X4&C1&D2S0=0#CID=1 OK
>> Phone data: DATE = 1022.w data:  ATE1V1X4&C1&D2S0=0#CID=1 OK
>> DATE = 1022Phone raw data: TIME = 1907.&D2S0=0#CID=1 OK
>> DATE = 1022Phone data: TIME = 1907.1V1X4&C1&D2S0=0#CID=1 OK
>> DATE = 1022 TIME = 1907Phone raw data: NMBR = XXXXXXXXX.
>> DATE = 1022 TIME = 1907Phone data: NMBR = XXXXXXXXXX.D=1 OK
>> DATE = 1022 TIME = 1907 NMBR = XXXXXXXXXXPhone raw data: NAME = XXXXXXXXXX.
>> DATE = 1022 TIME = 1907 NMBR = XXXXXXXXXXPhone data: NAME = XXXXXXXXXX.
>> DATE = 1022 TIME = 1907 NMBR = XXXXXXXXXX NAME = XXXXXXXXXX10/22/12 07:07:14 PM Callerid:  ATE1 DATE = 1022 TIME = 1907 NMBR = XXXXXXXXXX NAME = XXXXXXXXXX
>> Callerid data: port=Line1 type=rockwell cid_type=N name=unknown number=XXXXXXXXXX date=1022 time=1907
>>  data= ATE1V1X4&C1&D2S0=0#CID=1 OK  RING  RING  RING  RING  RING  RING  DATE = 1022 TIME = 1907 NMBR = 4038758079 NAME = XXXXXXXXXX.
>> 10/22/12 07:07:14 PM CID Lookup searching for: XXXXXXXXXX, unknown, N
>>
>> When it fails:
>> .hone raw data:
>> .RINGPhone data: ne1} raw data:
>> Phone raw data: RING. data:
>> Phone data: RING.ne1} raw data:
>> RINGSetting Telephony_Interface object Line1 to ring.
>> .hone raw data:
>> .RINGPhone data: ne1} raw data:
>> Phone raw data: RING. data:
>> Phone data: RING.ne1} raw data:
>> RINGSetting Telephony_Interface object Line1 to ring.
>> .hone raw data:
>> .RINGPhone data: ne1} raw data:
>> Phone raw data: RING. data:
>> Phone data: RING.ne1} raw data:
>> RINGSetting Telephony_Interface object Line1 to ring.
>> .hone raw data:
>> .RINGPhone data: ne1} raw data:
>> Phone raw data: RING. data:
>> Phone data: RING.ne1} raw data:
>> RINGSetting Telephony_Interface object Line1 to ring.
>>
>>
>> On 2012-10-22, at 12:14 PM, Lieven Hollevoet <lieven@lika.be> wrote:
>>
>>>
>>> Op 22-okt.-2012, om 05:06 heeft H Plato <hplato@gmail.com> het volgende geschreven:
>>>
>>>> Hello,
>>>>
>>>> I have a bit of an esoteric question.  I've been using the stock callerid modem notifications for the past two years or so. With a land line, this has been working flawless for the past few years.  Switching to voip, it seems like this doens't work quite as well. Here are my MH.ini settings:
>>>>
>>>> caller_port = /dev/ttyACM0
>>>> callerid_type = rockwell
>>>> callerid_name = Line1
>>>> callerid_format = 2
>>>> caller_id_file = $config_parms{data_dir}/phone/phone.caller_id.list
>>>> area_code_file = $config_parms{data_dir}/phone/phone.area_codes.list
>>>>
>>>> I don't know if the issue is with the service (I have upgraded to premium routing to see if that would solve the problem), the GrandStream Handytone 486 ATA, or the modem.  I started up minicom so I can see what data is coming in from the modem. It looks like only a subset of data (I've scrubbed some of the details with X). If anyone has any ideas, I'd appreciate it.
>>>
>>> Hi,
>>>
>>> getting callerid extraction to work reliably between a modem and an ATA can require quite some fiddling to get the settings correct. In the Grandstream you can select different caller-id types, are you sure they match with the type you defined for the modem?
>>>
>>> I tried to get caller-id recognition work with the cable-modem of my provider (the cable-modem has 2 built-in ports where you can connect a phone to, so I basically tried to do the inverse you did, but the principle is the same). Result: extracting the info did work sometimes on a Linksys SPA3102, most of the times on a Grandstream HT503, and always with the built-in modem of a laptop. The required settings for all devices I tried out were the same, so I guess it is really a matter of being lucky that the recognition works fine.
>>>
>>> In your case you might want to try out different variations of the following settings under 'advanced settings 2' of the HT486: FXS impedance, caller-id scheme, onhook voltage and polarity reversal. The last two should not really make a difference but if nothing else works you might still try changing these to see if the detection works better...
>>>
>>> Good luck,
>>> Lieven.
>>> ------------------------------------------------------------------------------
>>> Everyone hates slow websites. So do we.
>>> Make your web apps faster with AppDynamics
>>> Download AppDynamics Lite for free today:
>>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>>> ________________________________________________________
>>> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> ________________________________________________________
>> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365


------------------------------------------------------------------------------
The Windows 8 Center
In partnership with Sourceforge
Your idea - your app - 30 days. Get started!
http://windows8center.sourceforge.net/
what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365