Certain aspects of CF (Call Forwarding) services are controlled on a systemwide basis by RTP (Resilient Telco Platform) system parameters. Any changes made to these parameters affect all business groups and their members. Typically, these parameters are set during initial system configuration, to enforce global system policies and ensure proper feature interworking.
For example, the following properties can be modified by setting RTP system parameters:
While some of these parameters affect all types of CF services, others control only certain types.
The following table presents the CF related RTP system parameters. Default values are shown in bold type.
|This parameter defines the confirmation type (tone or announcement) the subscriber hears after activating any call forwarding service.||all station-controllableCF services|
|This parameter defines the confirmation type (tone or announcement) the subscriber hears after deactivating any call forwarding service.||all station-controllableCF services|
(CF Max Diversions)
|1,2,3,4,5||This parameter limits the number of times a call can be forwarded.||all CF services|
|This parameter defines whether calls received are forwarded or directed to intercept treatment.|
When set to True, calls are forwarded to the configured destinations.
When set to False, calls are directed to intercept treatment.
|CFSIE - DND|
|This parameter indicates whether CF - Busy, CF - No Reply, or both can be assigned to a subscriber at the same time CF - Voice Mail is subscribed (for compatibility with older versions).|
When set to True:
CF - Busy and CF - Voice Mail can be assigned to a subscriber. When both are assigned and active, CF- Busy takes precedence in a busy-line situation.When set to False, only CF - Voice Mail can be assigned to a subscriber.
CF - No Reply and CF - Voice Mail can be assigned to a subscriber. When both are assigned and active, CF - No Reply takes precedence in a no-answer situation because the no-answer timer for CF - Voice Mail does not start.
|CF - |
|This parameter defines whether an MWI (Message Waiting Indication) is accepted for a voice mail subscriber when call forwarding to voice mail is not active.|
When set to True, an MWI indication is accepted and processed.
When set to False, an MWI indication is ignored.
|CF - Voice Mail in combination with CFSIE|
|This parameter defines the confirmation type (tone or announcement) the subscriber hears after remotely activating Unconditional CF||CF - Remote Activation|
|Srx/Main/SRCFDATimeout||0 - 30 seconds||When Simultaneous Ringing is active, this parameter is used to extend the value you specify in the Ring Duration field for the related CF services. This additional time interval provides the time necessary for calls to progress - for example, the next destination to be rung on a serial ringing list - so the call is not forwarded too soon.|
For example, assume the following:
The Ring Duration is defined as 20 seconds.The two time intervals are added together, resulting in a total time interval of 30 seconds before a call is forwarded to the destination this service specifies.
This RTP parameter is defined as 10 seconds.
|CF - |
|Srx/Main/UseBglExtension OnCFToVoiceMail||RTPTrue (True)|
|This parameter indicates whether extensions should be used in redirecting numbers sent to the voice mail DN.|
When set to True, the BGL extension is used for the Original Called Party Number or Redirecting Number field in the Setup message.
When set to False, the E.164 DN is used instead.
|CF - Voice Mail|
|Srx/Main/VoiceMailDnList ForBglExtensions||string (blank)||This parameter is relevant only if the previous parameter is set to True. It contains the Voice Mail DN(s) that require the use of BGL extensions when redirecting numbers sent to the voice mail DN.|
The string must be in the form DN1::DN2::...::DNlast. If the BGL extension associated with the called party DN appears in this string, that extension is sent in the Diversion Header rather than the E.164 DN.
|CF - Voice Mail|