Configuration File Parameter Guide
403
ET685 Administrator and Provisioning Manual
Description:
If this setting is "on" the server will be responsible for handling the global
forwarding functionality. From the call perspective the phone will act as if
no forwarding was set (all is managed by the server).
since 8.7.4:
The PUI will show the current setup if the server synchronizes it's values
with those on the phone (settings fwd_all_enabled and fwd_all_target).
This setting does not specify how the server changes the redirection
values nor how the phone updates them. (it may be done via TR69, DFKS
or starcodes).
before 8.7.4:
The phone user will see the value from settings
server_managed_fwd_all_state and server_managed_fwd_all_nr as the
current global forwarding state, and this value can be changed at anytime
by the server.
This setting does not specify how the server changes the value of setting
server_managed_dnd_state nor how the phone updates them (it may be
done via TR69).
Values:
on, off
Default:
off
Setting:
using_server_managed_fwd_busy
Description:
If this setting is "on" the server will be responsible for handling the redirect
on busy functionality. From the call perspective the phone will act as if no
redirect was set (all is managed by the server).
since 8.7.4:
The PUI will show the current setup if the server synchronizes it's values
with those on the phone (settings fwd_all_enabled and fwd_all_target).
This setting does not specify how the server changes the redirection
values nor how the phone updates them. (it may be done via TR69, DFKS
or starcodes).
before 8.7.4:
The phone user will see the value from settings
server_managed_fwd_busy_state and server_managed_fwd_busy_nr as
the current redirect on busy state, and this value can be changed at
anytime by the server.
This setting does not specify how the server changes the value of settings
server_managed_fwd_busy_state and server_managed_fwd_busy_nr
nor how the phone updates them (it may be done via TR69).
