Alcatel-Lucent 7330 - Page 377

5 — VoIP overview
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7360 ISAM FX ONT R04.06.02 November 2013 5-31
3FE 55873 AAAA TCZZA Edition 01
ONT Product Information Guide
follow_regis
tration
The parameter controls whether all
SIP signalling follows the registration
(i.e. be sent via the IP address
through which the current
registration was sent) or not.
The parameter is only supported in
GSIP 4.5
If this parameter set to “true” or
“yes” and if RegistrarRoute and
OutboundProxy (or
RegistrarRouteSec and
OutboundProxySec) are both
non-empty and set to the same value
then, all SIP signaling will strictly
follow registration.
If this parameter set to “false” or
“no” or if RegistrarRoute and
OutboundProxy (or
RegistrarRouteSec and
OutboundProxySec) are configured
as different values then, all SIP
signalling may or may not follow
registration.
The default value is false in ftp mode
and true in iConfig mode.
YYPackage
A, B, H,
I-240W-
S only
No, value
is derived
from
FTP/defau
lt line
profile.
N/A
call_waiting
_ringing_ind
ication
The parameter determines how the
ONT provisionally responds to a call
waiting request using either the 180,
180_alert_info or 182 responses.
For 180_alert_info, the ONT sends
out a 180 response with a extra
header with Alert-Info:
<urn:alert:service:call-waiting>. By
default, the ONT sends the normal
180 ringing response as the call
waiting ringing indication. However
some customers require that a
specific 18x response for the call
waiting ringing signal so that the
SS/AS can differentiate it from
normal ringing and to generate a
specific announcement to the calling
party. The possible specific 18x
messages include the following two
cases:
• 1. CMCC requires that a 182
response shall be generated in
this case;
• 2. 3GPP 24.615 requires 180, but
that 180 shall have a specific
header Alert-Info:
<urn:alert:service:call-waiting>
The default is the 180 signalling
method.
YYPackage
A, B, H,
I-240W-
S only
No, value
is derived
from
FTP/defau
lt line
profile.
N/A
Parameter Description Mode
1
Mode
2
Device OMCIv2
support?
TL1 and CLI
parameters
(6 of 7)