Juniper JUNOS OS 10.4 - RELEASE NOTES REV 5 Release Note page 160

JUNOS OS 10.4 Release Notes
160
On SRX240 devices with Integrated Convergence Services, the call-pickup feature
does not work in survivable mode. If an analog station in a station group rings, another
analog phone belonging to the same station group cannot pick up the call. As a
workaround, configure three SIP phones (S1, S2, and S3), and add them to the pickup
group (use a station group with S1, S2, and S3) because the pickup group works for
SIP phones, but it does not work for analog phones. [PR/505237]
On SRX210 and SRX240 devices with Integrated Convergence Services, if the transport
method for the peer call server is TCP, the SRX Series devices do not support SIP
messages of more than 2048 bytes. [PR/510291]
On SRX210 and SRX240 devices with voice capability, the T1PRI calls do not work
when multiple trunk-groups or trunks are created. [PR/514784]
On SRX210 and SRX240 devices with voice capability, the caller ID of the calling party
is displayed as a four-digit local extension number instead of a 7-or 10-digit local or
international number for outgoing calls from PRI. [PR/516021]
On SRX210 and SRX240 devices with Integrated Convergence Services, if you have
the accounting feature configured (Services>Convergence services>Features), you
cannot configure the account code on a per-station basis. [PR/516681]
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
command is required after
restart rtdm
restart rtdm command is required to
Copyright © 2011, Juniper Networks, Inc.