[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
Re: OT. Olympus Olycom m2280 PBX
- To: ukha_d@xxxxxxx
- Subject: Re: OT. Olympus Olycom m2280 PBX
- From: patrickl@xxxxxxx
- Date: Sat, 03 Nov 2001 10:21:37 -0000
- Delivered-to: mailing list ukha_d@xxxxxxx
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
--- In ukha_d@y..., "Brian G. Reynolds"
<brian.g.reynolds@n...> wrote:
> Thanks Patrick, just reading my mails now! been a long week.
>
> At the moment I have got an extension lead from the main in box
through a
> door jam (cannot close the door!) and onto the Meteor, and this
works.
>
> What I did before I bought the PBX was to run phone cable round the
house
> and fit outlets where ever I could be bothered to, I now have the
PBX
> plugged into one of these outlets but when I fitted a
"splitter"
and plugged
> both the Meteor and the PBX into the same socket the Meteor did not
work, I
> thought this to be strange as the Meteor is still between the
master socket
> and the PBX.
This is strange, it should certainly work in the configuration you
have described.
> What I was hoping was that the PBX designers were smart enough to
think of
> this use at the design stage and devise a way to access the CID
>from
> unit.
The problem arises from the requirement to pass the CID datastream to
all extensions before the incoming line rings - it's technically a
bit involved and the requirement is specific to the UK market. AFAIK
there are no 2+8 analogue PBXs that pass CID to extensions - although
there are a couple of 1+4 that do.
Patrick
For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe: ukha_d-subscribe@xxxxxxx
Unsubscribe: ukha_d-unsubscribe@xxxxxxx
List owner: ukha_d-owner@xxxxxxx
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Home |
Main Index |
Thread Index
|