[misterhouse-users] Strange CallerID Behaviour (Australia)

[Martin C. <mc...@ar...>]

Dear List Readers,

I have an unusual (but explainable) problem with the callerid module.  I
have a rockwell based modem and I am in Australia.  It may have also
frustrated others.

It works OK if I call from a mobile, but (perhaps because the NAME=
field is missed) it does not work from a land line.

>From the print log (with xxxx s to protect privacy).

16/09/2003 17:58:38 Callerid: MOBILE 08xxxxxxxx
16/09/2003 17:58:38 CID Lookup searching for: 08xxxxxxxx, MOBILE, N
16/09/2003 17:58:38 Callerid: ATE1V1X4&C1&D2S0=0#CID=1 OK RING DATE =
0916 TIME = 1756 NMBR = 08xxxxxxxx RING RING RING RING DATE = 0916 TIME
= 1758 NMBR = 04xxxxxxxx NAME = MOBILE

The code seems to only parse when the name field is present and when it
is absent it 'waits' and then returns the previous number when a
(second) mobile call comes in- presumably after the NAME matches in the
string.  I miss a call in the log and then get it as the wrong info
later.   It looks like our carrier (Telstra) generally omits the NAME=
field unless it is a mobile call in which case it tells us 'MOBILE'.

Is there a settings solution to this or does a mod have to be made to
the library or common code to fix this?  Any hints?

Best regards,

Martin