The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: RE: screen capture -> video prog?


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Asterisk progress


  • To: ukha_d@xxxxxxx
  • Subject: Re: Asterisk progress
  • From: "K. C. Li" <li@xxxxxxx>
  • Date: Wed, 7 May 2003 19:47:00 +0100 (BST)
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

On Wed, 7 May 2003, UKHA wrote:

> If you explained what you were trying to achieve and that's what he
said
> then.... that's what we call bollocks in the trade (not that I'm
actually
> in the trade you understand). Ultimately, for what I'm assuming you
want

I think he was trying to explain the flexibility of these phones in a
large commercial environment. He wasn't trying to sell me a proxy server.

> to use this for, a simple proxy like partysip or ser will do you fine.
If however
> you intend to run a service like FWD then Tim is right.

Your assumption is correct.

> then you will be able to call me (and any other proper proxied sip
user),
> and I will be able to call you (as will any other proper proxied
user),
> you will be able to call any FWD user but they wont be able to call
you.

I needed to read that twice to understand it! Basically, you are saying
that FWD can only accept calls from proper proxied SIP users but not
to originate a call to the same. Can you not run both types and cover
everyone?

> Well when the big corps turn to ipv6 maybe the rest of us will get
> more ipv4 ips?

I don't think there is any great rush to move to IPv6 now and the wait
could be long.

Regards,

Kwong Li
li@xxxxxxx
Laser Business Systems Ltd.
http://www.laser.com



Home | Main Index | Thread Index

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.