VDN Return Destination Considerations

VDN Return Destination

Considerations

The VDN Return Destination feature allows an incoming trunk call to be placed back in vector processing after all parties, except the originator, drop. This feature is activated through switch administration of the VDN form. It is an optional system feature, and as such, it must be optioned on the System- Parameters/Customer-Options form.

A new field added to the VDN form will allow the user to enter a VDN extension as a Return Destination. In this section, the VDN which has the Return Destination field administered will be called the "VDN with this feature active." The Return Destination VDN (the one specified in the new field) will be referred to as the "Return Destination."

Every incoming trunk call which is processed through a VDN with this feature active will be placed back in vector processing when all parties on the call, except the originator, drop. For this feature, the "originator" is the incoming party which originated the call at the time the call entered the VDN with this feature active.

The VDN that the call will be placed in (when the originator is the only remaining party) is determined by the "Return Destination". This VDN may be the same or different than the original VDN.

This feature is used to keep the call active and give the caller the opportunity to signal the need for sequence dialing (by entering a "#"). There are two ways this can happen:

1.When the destination drops on its own (after having answered), the call will go to the Return Destination which will have a "collect digits" vector step. This step will try to collect the "#" sign entered by the caller.

2.When the call is not answered, the caller enters the "#" to request sequence calling (this "#" will be collected by the ASAI-Requested Digit Collection feature). This "#" is reported to the adjunct. The adjunct requests the third_party_drop (or third_party_end_call) for the destination, and at that point the call goes to the Return Destination.

The VDN Return Destination and ASAI-Requested Digit Collection features may be used independently, with the following rules:

1.If there is no ASAI request to collect digits, but a Return Destination is provided: when all parties, except the originator, drop, the switch will route the call with only one party active (the caller) to the Return Destination. At this point, the call enters vector processing for the VDN specified by the Return Destination.

2.If a request is made to collect digits but there is no Return Destination provided: the switch will collect the digits and pass them on to the ASAI adjunct. It will be up to the adjunct to take action. However, if the action

Issue 4 September 1995 C-5

Page 307
Image 307
AT&T 555-230-520 manual VDN Return Destination Considerations