B
UGS
F
IXED FOR
V
ERSION
7
1.
Registration.
Advancing the local server clock causes all registered endpoints to be
temporarily unregistered and all current active calls to be disconnected. However,
the endpoints will re-register again with the full registrations (RRQ) within the
default TTL timeout of 60 seconds. All force-online registrants will remain unaffected.
Now, endpoints do not go offline and calls are not disconnected.
2.
Conference On Demand.
When dialing Conference On Demand from the
ViewStation FX interface using the address book (local or Global), PathNavigator will
show the bit rate as the bit rate dialed times the number of participants. e.g., a user
dials 3 participants using Conference on Demand using 128kbps. The Active Calls will
show the initiator dialed with a bit rate of 384kbps. This makes video switching from
a ViewStation FX problematic. PathNavigator now shows the correct bit rate for the
initiator.
3.
Simplified Dialing.
If using an MGC that has no gateway resources available (I.E.
no MUX resources available) PathNavigator will not route the call to the next physical
MGC. It will, however, try to route the call on multiple H.323 cards on the same
MGC. When the MUX resource is used up on one MGC, PathNavigator will look to see
if another MGC has resources available for use.
4.
H.239 limitation.
When PathNavigator was in routed mode, the V-Series (VSX
models) endpoints could not use H.239 with PathNavigator 7.0 because calls cannot
be processed. Calls originating from V-Series models with H.239 enabled can now be
processed by PathNavigator.
5.
Bandwidth Authorization for Polycom Conference Suite.
Polycom Conference
Suite can authorize up to a maximum of 5 calls per second before the performance
of PathNavigator is adversely affected. This is now fixed and PathNavigator’s
performance will not be adversely affected when using Bandwidth Authorization.
K
NOWN
I
SSUES FOR
V
ERSION
7
1.
Forward No Answer.
If two endpoints are registered to the same PathNavigator
and one of the endpoints has configured a Forward No Answer to an address
belonging to an endpoint registered with a neighbor PathNavigator, a call between
the two registered endpoints will not connect using the following aliases, E.164 or an
H.323 ID. The call between these two registered endpoints can only connect if the
forwarded endpoint is physically powered off.
2.
Conference On Demand.
If the login information is changed on the MGC and
PathNavigator is logged in for the Conference On Demand service, PathNavigator
remains logged on with the previous login credentials. However, the next time
PathNavigator logs back into the MGC (after restarting PathNavigator), it will log in
with the new login information.
3.
Neighbor Gatekeeper.
There is memory leak when placing calls through
hierarchical gatekeepers. This occurs if Microsoft Access is the chosen database. A
work around is to use Microsoft SQL as PathNavigator’s database.
Copyright (c) 2004 Polycom Incorporated. All rights reserved.
Polycom, the Polycom logo design and ViewStation are registered trademarks, PathNavigator, Global Management System, and
iPower are trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of
respective owners
14
