LISTSERV mailing list manager LISTSERV 16.0

Help for LINUX-L Archives


LINUX-L Archives

LINUX-L Archives


LINUX-L@LISTS.UFL.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

LINUX-L Home

LINUX-L Home

LINUX-L  2007

LINUX-L 2007

Subject:

Re: peer-to-peer VOIP?

From:

Mark Oden <[log in to unmask]>

Reply-To:

Platform Independent Linux List! <[log in to unmask]>

Date:

Tue, 11 Sep 2007 22:40:10 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (45 lines)

Cisco's Linux version of the Call Manager is released (Version 6.0), but
it is considered in the "Early Adopter" phase right now.

~Mark Oden

Avi Baumstein wrote:
> On Tue, 2007-09-11 at 16:21 -0400, Brian Bartholomew wrote:
>
>
>> If you have a building full of the UF-recommended brand of VOIP phones
>> on the same LAN, can they talk to each other without involving any
>> additional central points of failure? I'm not asking for conference
>> calls, voicemail, recordings with beeps, queues, forwarding, or
>> whatever. Just using the last quad of the IP as an extension number.
>>
>
> The server piece in a Cisco IP phone solution is a 'Call Manager' which
> would be the central point of failure you refer to. After the Call
> Manager sets up a call (looks up the number you dialed, cross refs with
> it's IP, rings the phone, then passes it off), the actual voice
> connection is directly between the two phones (if within the same phone
> system) or between your phone and the gateway if one end crosses the
> telco. If the Call Manager takes a dive during a call, the call should
> not be interrupted.
>
> The bad news (since this is the Linux list :) is that the Call Manager
> runs on Windows (in the current version, next version is Linux). The
> good news is that Cisco recommends (and I understand CNS has
> implemented) multiple redundant Call Managers, so that the system can
> tolerate failures of individual pieces.
>
> I'm also fairly certain that the CNS VoIP implementation is using SCCP
> ('Cisco Skinny'), so the SIP dial-by-IP functionality isn't present.
>
> All the same goes for the Health Science Center VoIP system, of which
> I'm much more familiar. I will say that in the 6 or so years we've been
> running the Cisco phone system in the HSC, it has been extremely
> reliable, give or take a few times Bellsouth has screwed up a PRI (which
> actually isn't much of a problem as long as there is capacity on
> non-screwed-up PRIs). Yes, parts have died, but service outages have
> been prevented by the built in redundancy.
>
> -avi
>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997

ATOM RSS1 RSS2



LISTS.UFL.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager