Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 151

Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
On SRX240 devices with voice capability, the
changing the Max-concurrent-value from x to 0, to allow unlimited calls through SIP
trunk or PCS. [PR/536849]
On SRX240 devices with voice capability, the
make PRI calls successful when both PRI and T1CAS lines are active. [PR/537551]
Interfaces and Routing
On SRX650 devices, the following loopback features are not implemented for quad
T1/E1 GPIMs:
Line
FDL payload
In-band line
In-band payload
[PR/425040]
On SRX650 devices, configuring dual and quad T1/E1 framing at the chassis level has
no effect. [PR/432071]
On SRX Series devices, incorrect Layer 2 circuit replication on the backup Routing
Engine might occur when you:
Configure nonstop active routing (NSR) and Layer 2 circuit standby simultaneously
and commit them
Delete the NSR configuration and then add the configuration back when both the
NSR and the Layer 2 circuits are up
As a workaround:
Configure the Layer 2 circuit for a nonstandby connection.
1.
Change the configuration to a standby connection.
2.
Add the NSR configuration.
3.
[PR/440743]
On SRX210 Low Memory devices, the E1 interface flaps and traffic does not pass through
the interface if you restart forwarding while traffic is passing through the interface.
[PR/441312]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, when you configure the
SAP listen option using the
both sparse and sparse-dense modes. [PR/441833]
On J Series devices, one member link goes down in a Multilink (ML) bundle during
bidirectional traffic with Multilink Frame Relay (MFR). [PR/445679]
On SRX210 devices, the modem moves to the dial-out pending state while connecting
or disconnecting the call. [PR/454996]
restart rtdm
restart rtdm
command in the CLI, listening fails in
protocol sap listen
command is required after
command is required to
151