On Feb 15, 12:35 am, "DGB" <m...@ntlworld.invalid> wrote:
> Innews:mn.75587d723f978cfe.48968@blueyonder.invalid,
> Jono <notha...@blueyonder.invalid> typed:
>
>
> 
> 
> 
> 
>
> That's interesting.  I haven't actually tried to get CLI from a BT line
> plugged into the PSTN port of my Grandstream 486, since I already have sta
nd
> alone caller display units directly connected to the BT incoming line (one
> of which also indicates CLI of calls waiting).  What I have found, though,
> is that the facility on the 486 to access the PSTN line only works properl
y
> when you have a "real" PSTN line connected, and not a PABX extension, whic
h
> is how I first tried configuring it.  I think it must be something to do
> with ATA needing a full 50v line rather than the 24v it gets from the PABX
.
> The 486 also senses when no line is connected to the PSTN port, in which
> case dialling ** gives an engaged tone.
> --
> Don

I have caller ID on my 2 lines on a Linksys spa2102 and it works fine.
make sure the caller ID method is set to:
etsi Fsk With PR (UK)
on default mine was set to something else

[ Post a follow-up to this message ]