The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: UK Caller ID into Asterisk


  • Subject: Re: UK Caller ID into Asterisk
  • From: "patrick_o_matic" <patrick@xxxxxxxxxxxx>
  • Date: Mon, 30 Jan 2006 17:13:39 -0000

--- In ukha_d@xxxxxxx, Kevin Hawkins <lists@u...> wrote:
>
> Ok, so I'm probably going to take the plunge with Asterisk - thought I
> might start by playing with a  Sipura 3000 - eventually though I would
> probably need 3 incoming line (FX0) support and maybe 4 or so POTS
> extensions, although maybe will go fully SIP here.  What are my
options
> for incoming PSTN lines  (FX0) that fully support BT Caller ID formats
> ??  I'm thinking the Sipura 3000 doesn't ?  Also are there any devices
> that will onwardly generate a BT compatible CID from Asterisk to my
> existing caller display telephones - eg my DECT ones ?
>

Sipura 3000 *does* support UK CLID, including withheld and unavailable
flags, as from around october last year.

You should find that most equipment that supports UK CLID also
supports US style CLID, so you shouldn't have any problems with US
style presentation on an FXS provided you use a US ring cadence (so
there is sufficient inter-ring delay to pass CID). Again the Sipura 3k
supports UK presentation when appropriately configured on the FXS port.

The massive thing in favour of the Sipura 3k solution is that it gives
you fail over in the event that your asterisk box fails for any
reason. I'd also recommend considering installing asterisk under
vmware or similar, so that you can reinstate the image on available
server at short notice in the event of hardware failure.

HTH
Patrick







UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.