|
Home > Archive > Voice over IP Cisco > November 2007 > So is the Lifesize H.320 gateway actually a 3545?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
So is the Lifesize H.320 gateway actually a 3545?
|
|
| Robert Kulagowski 2007-11-29, 7:11 pm |
| Or is the 3545 a Lifesize Gateway? The features seem to be =
word-for-word, with the exception that someone did a global search and =
replace and either inserted/removed Lifesize or cisco as necessary. =
Look at "Downspeeding" as an example...
Here's what the 3545 feature details have: =
http://www.cisco.com/en/US/docs/vid...y/3545/install=
ation/guide/all_gw_functionality.html
Dual video
The gateway supports H.239 standards-based dual video and TANDBERG =
DuoVideo technology. Dual video streams enable a screen to carry video =
images from one source while simultaneously displaying images from a =
second source.
Hot swap
The gateway features hot swap functionality that you can use to remove =
and replace gateway cards under power.
Conceal caller ID
The gateway supports a conceal caller ID feature that instructs the =
gatekeeper to conceal the identity of the calling endpoint on the IP or =
ISDN network, whether the presentation restricted feature is enabled or not.
H.323 fast start
The gateway H.323 fast start feature enables endpoints to join a voice =
conference in the gateway more quickly.
ISDN rollover (available in cisco Unified Videoconferencing 3545 PRI =
Gateway only)
The gateway features ISDN rollover. In this feature, the gateway sends a =
"busy out" channel request to the PSTN switch when the current PRI =
connection is left with less than a predefined number of available B =
channels. The PSTN switch "rolls over" to the next available gateway.
Network Specific Facility (available in cisco Unified Videoconferencing =
3545 PRI Gateway only)
The gateway provides support for Network Specific Facility Information =
Elements (NSF IEs) which enable system administrators to specify to =
service providers the equipment, service, or network through which they =
want a call routed.
ISDN connection failure
The gateway responds to ISDN connection failure events, by unregistering =
from its gatekeeper. The gatekeeper is forced to send new IP-to-ISDN =
calls through a different gateway, thus ensuring high call completion =
rates. The gateway re-registers to the gatekeeper when the ISDN =
connection is restored.
Downspeeding
The gateway features downspeeding functionality. In the downspeeding =
feature, the gateway attempts to reconnect a disconnected video call =
either at a lower bandwidth or as a voice call. Downspeeding contributes =
to a higher percentage of call completion on the network. The gateway =
supports downspeeding at call setup and in mid-call.
Multiple trap server support
The gateway supports up to three SNMP trap servers.
Here's the Lifesize gateway features:
Dual video
The LifeSize Gateway supports H.239 standards-based
dual video and TANDBERG DuoVideo technology.
Dual video streams enable a screen to carry video images
from one source while simultaneously displaying images
from a second source.
Conceal caller ID
The LifeSize Gateway supports a conceal caller ID
feature that instructs the gatekeeper to conceal the
identity of the calling endpoint on the IP or ISDN
network, whether the presentation restricted feature is
enabled or not.
H.323 fast start
The LifeSize Gateway H.323 fast start feature enables
endpoints to join a voice conference in the LifeSize
Gateway more quickly.
ISDN rollover (available in
Gateway-PRI only)
The LifeSize Gateway features ISDN rollover. In this
feature, the LifeSize Gateway sends a =93busy out=94 channel
request to the PSTN switch when the current PRI
connection is left with less than a predefined number of
available B channels. The PSTN switch =93rolls over=94 to
the next available gateway.
Network Specific Facility
(available in Gateway-PRI only)
The LifeSize Gateway provides support for Network
Specific Facility Information Elements (NSF IEs) which
enable system administrators to specify to service
providers the equipment, service, or network through
which they want a call routed.
ISDN connection failure
The LifeSize Gateway responds to ISDN connection
failure events, by unregistering from its gatekeeper. The
gatekeeper is forced to send new IP-to-ISDN calls
through a different gateway, thus ensuring high call
completion rates. The LifeSize Gateway re-registers to
the gatekeeper when the ISDN connection is restored.
Downspeeding
The LifeSize Gateway features downspeeding
functionality. In the downspeeding feature, the LifeSize
Gateway attempts to reconnect a disconnected video call
either at a lower bandwidth or as a voice call.
Downspeeding contributes to a higher percentage of call
completion on the network. The LifeSize Gateway
supports downspeeding at call setup and in mid-call.
Multiple trap server support
The LifeSize Gateway supports up to three SNMP trap
servers.
| |
| Bernhard Albler 2007-11-29, 7:11 pm |
| Well, they actually are both OEMs, namely from radvision. Look at the scopia platform...
really nice hardware in my opinion btw.
regards
bernhard
| |
| Robert Kulagowski 2007-11-30, 1:11 pm |
| Bernhard Albler wrote:
> Well, they actually are both OEMs, namely from radvision. Look at the scopia platform...
>
> really nice hardware in my opinion btw.
We're looking at deploying video more widely this year, and I'm still
trying to wrap my head around certain concepts. Like why CM can't act
as a full gatekeeper and instead it looks like I need an external one.
Our existing video gear is primarily Polycoms EX and FX with 3xBRI
(obtained from the phone company). I've messed around a little bit with
setting them up as a H.323 device in CM 4.1.3, but that will probably
only let me use IP internally, because I would still need something to
go H.323 to H.320 to connect to the outside world. But associating them
with CM should allow me to use our internal dial-plan, correct?
The other "Crap, now I need another box" aspect of this is that IOS
almost has a useful feature where it will do H.320 to H.323, but you
can't do more than 128K.
Integrating Data, Voice, and Video Services for ISDN Interfaces
http://www.cisco.com/en/US/products...0080788070.html
Of course, you don't find out that you can't do more than 128K until
you've been working on it for 5 days with TAC and they finally admit
that the docs are misleading.
"H.320 calls are limited to 16 B-channels." is what the docs say, except
they're actually limited to 2 B-channels, so a bit useless.
|
|
|
|
|