Los éxitos de Peter Szendy 108

The Auto Recall (Last Call Return) section of [RST TR] applies to BSS, with the following additions.

Multiple UEs with the same public user identity may be registered. In this case, if one of the UEs executes AR, then that UE uses the calling address received at that UE if the last received call was not anonymous. If the last call received was anonymous, the AR target address is the address (network stored) of the caller associated with the last received call at this UE.

6.7.1.1 Feature Interactions

The feature interactions of Automatic Recall feature are specified in [GR 227]. Calling Name Delivery

When AR is used with the CNAM feature, the called station's name need not be delivered to the customer when special ringing is applied. This differs from the requirements of [GR 227].

Caller ID Blocking

An AR request to a target which previously withheld their number is possible; details of the anonymous target are not revealed to the AR requestor.

Call Forwarding

An AR request to a target with Call Forwarding (see Section 6.4) active is should be rejected instead of being forwarded. The call to the line which originated the AR request (with the special ringing pattern) rings the line without being forwarded.

Call Rejection

A call which is rejected is not classified as the last incoming call.

An AR request to a target with a service which rejects calls (e.g., Anonymous Call Rejection, Do Not Disturb) is rejected if a normal call from the subscriber to the target would be rejected. The call to the line which originated the AR request (with the special ringing pattern) is not rejected by any Call Rejection service.

Auto Callback

Concurrent AR and AC requests from a user to the same target may be treated as one request. Simultaneous/Sequential Ring

If the AR target is a Simultaneous or Sequential Ring subscriber, busy/idle monitoring only occurs on the subscriber's own line and not any of the other Simultaneous/Sequential ring destinations.

Account/Authorization Codes

The call type assigned to AR calls will typically have the same classification as a normal call to the target and so may require an Account/Authorization code to be provided.

Hunt Groups

Multiple activations from different lines in a Hunt Group to the same target are allowed and are treated as separate AR requests. The call to the line which originated the AR request (with the special ringing pattern) does not alert other lines in the hunt group. It is an implementation choice whether AR requests which target a Hunt Group are accepted or rejected.

Call Pickup

The call to the line which originated the AR request (with the special ringing pattern) cannot be picked up from another line using Call Pickup. The call to the AR target can be picked up.

Outbound Call Blocking/Call Restriction

The call type assigned to AR calls will typically have the same classification as a normal call to the target and so may be denied by the Outbound Call Blocking/Restriction service.

6.7.2 Auto Callback

Multiple UEs with the same public user identity may be registered. In this case, if one of the UEs executes AC, then that UE uses the calling address received at that UE if the last received call was not anonymous. If the last call received was anonymous, the AR target address is the address (network stored) of the caller associated with the last received call at this UE.

6.7.2.1 Feature Interactions

The feature interactions of Automatic Callback feature are specified in [GR 215]. Calling Name Delivery

When AC is used with the CNAM feature, the called station's name need not be delivered to the customer when special ringing is applied. This differs from the requirements of [GR 215].

Call Forwarding

An AC request to a target with Call Forwarding (see Section 6.4) active should be rejected instead of being forwarded. The call to the line which originated the AC request (with the special ringing pattern) rings the line and is not forwarded.

Call Rejection

An AC request to a target with a service which rejects calls (e.g., Anonymous Call Rejection, Do Not Disturb) is rejected if a normal call from the subscriber to the target would be rejected. The call to the line which originated the AC request (with the special ringing pattern) is not rejected by any Call Rejection service.

Auto Recall

AC can be used to establish a call to the last AR target. Concurrent AR and AC requests from a user to the same target may be treated as one request.

Simultaneous/Sequential Ring

If the AC target is a Simultaneous or Sequential Ring subscriber, busy/idle monitoring only occurs on the subscriber's own line and not any of the other Simultaneous/Sequential ring destinations.

Hunt Groups

Multiple activations from different lines in a Hunt Group to the same target are allowed and are treated as separate AC requests. The call to the line which originated the AC request (with the special ringing pattern) does not alert other lines in the hunt group. It is an implementation choice whether AC requests which target a Hunt Group are accepted or rejected.

Call Pickup

The call to the line which originated the AC request (with the special ringing pattern) cannot be picked up from another line using Call Pickup. The call to the AC target can be picked up.

Outbound Call Blocking/Call Restriction

The call type assigned to AC calls will typically have the same classification as a normal call to the target and so may be denied by the Outbound Call Blocking/Restriction service.

6.7.3 Last Number Redial

The Last Number Redial feature enables a user to automatically redial the last called number by pressing a redial button on their telephone set. Alternatively, this feature could be invoked by dialing a Feature Activation Code. Last Number Redial is distinguished from the Auto Callback feature described in Section 6.7.2 in that if the target public user identity is busy, Auto Callback performs camp-on processing, while Last Number Redial simply returns busy treatment to the originating user. As such, BSS does not support the option to activate Last Number Redial via feature activation code, since the Auto Callback feature provides the same functionality plus more. The client-based version of Last Number Redial is supported, although its operation is trivial and is not specified in PacketCable documents.

6.7.3.1 Feature Interactions

Network-based features are unable to distinguish between a user invoking the Last Number Redial feature and the user manually redialing the last number.