■ On SRX210 devices with Integrated Convergence Services, the call hold feature
does not work for Xlite softphones. [PR/432725]
■ At least one time slot must be configured for data for voice channels on T1 lines
to work. [PR/442932]
■ On SRX240 devices with Integrated Convergence Services, T1 configuration does
not support all the 24 time slots for voice calls. It is limited to 5 time slots or line
channels currently. [PR/442934]
■ The music-on-hold feature is not supported for SIP phones. [PR/443681]
■ 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]
■ 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 daemon to commit runtime T1 configuration changes.
[PR/468594]
■ The SIP-to-SIP simultaneous call capacity is limited to 10 calls. [PR/478485]
Interfaces and Routing
■ On J4350 and J6350 devices, the link status of the onboard Gigabit Ethernet
interfaces (ge-0/0/0 through ge-0/0/3) or the 1-port Gigabit Ethernet ePIM
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 SRX5600 and SRX5800 devices, ping to far-end reth interfaces does not work
for different routing instances. [PR/408500]
■ 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.
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers ■ 151
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers