Juniper JUNOS 10.1 - RELEASE NOTES 5-13-2010 Release Note page 146

JUNOS 10.1 Software Release Notes
Interfaces and Routing
146
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
The peer call server configuration for the media gateway page in J-Web does not
correctly display the port number field when TCP is used as the transport.
[PR/445734]
When you click the trunk-group field in J-Web, the configured trunk values are
not displayed. [PR/445765]
Comfort noise packets are not generated when both voice activity detection
(VAD) and comfort noise generation are enabled for an FXS station. [PR/448191]
In J-Web, if you do not configure the class of restriction and a station template,
you cannot configure a station. [PR/452439]
J-Web does not provide support for the SIP template extension inheritance feature.
[PR/455787]
SNMP does not provide support for survivable call server (SRX Series SCS)
statistics. [PR/456454]
Consecutive G.711 faxes pass through between two FXS ports fails when
originating and terminating sides alternate. [PR/465775]
When T1 lines for stations or trunks are configured, you might hear a momentary
burst of noise on the phone. [PR/467334]
You must restart the
flow
[PR/468594]
The SIP-to-SIP simultaneous call capacity is limited to 10 calls. [PR/478485]
On J4350 and J6350 devices, the link status of the onboard Gigabit Ethernet
interfaces ( through
ge-0/0/0
interface fails when you configure these interfaces in loopback mode. [PR/72381]
On J Series Routers, asymmetric routing, such as tracing a route to a destination
behind J Series devices with Virtual Router Redundancy Protocol (VRRP), does
not work. [PR/237589]
On J2320 devices, when you enable the DHCP client, the default route is not
added to the route table. [PR/296469]
On SRX5600 and SRX5800 devices, ping to far-end
for different routing instances. [PR/408500]
On SRX240 devices, drops in out-of-profile LLQ packets might be seen in the
presence of data traffic, even when the combined (data+LLQ) traffic does not
oversubscribe the multilink bundle. [PR/417474]
On SRX240 and SRX650 devices, when you are configuring the link options on
an interface, only the following scenarios are supported:
Autonegotiation is enabled on both sides.
Autonegotiation is disabled on both sides (forced speed), and both sides are
set to the same speed and duplex.
If one side is set to autonegotiation mode and the other side is set to forced
speed, the behavior is indeterminate and not supported. [PR/423632]
daemon to commit runtime T1 configuration changes.
) or the 1-port Gigabit Ethernet ePIM
ge-0/0/3
interfaces does not work
reth