Administering station or ASAI transfer, conference, or release

Last Updated : Jun 10, 2013 |

Before you begin

Ensure that the field option in the ISDN/SIP Network Call Redirection field on the System-Parameters Customer-Options screen is y.

Procedure

  1. For MCI Network Call Transfer (NCT) or Two Bearer Channel Transfer (TBCT) protocols, use the trunk group with a Bearer (B) channel that has the same Delta (D) channel as the incoming ISDN call to create a second call leg of the call transfer.
  2. For the ETSI Explicit Call Transfer (ECT) protocol, the second leg of the call can be over a different trunk group with a different signaling group than the incoming call leg.
  3. You must also perform the following tasks to administer station or ASAI transfer:
    1. On the ARS Digit Analysis screen, add the PSTN number that a station or ASAI user dials to transfer an incoming call to another PSTN endpoint.
    2. Administer the entry with an Alternate Route Selection (ARS) routing pattern that routes the second call leg to the same trunk group being used for the incoming call.
    3. When you use the MCI NCT feature for the Route Pattern screen associated with the ARS Digit Analysis screen entry, administer the Service/Feature (sdn) and Number Format (lev0-pvt) fields to be consistent with the service-type and dialing-plan configuration of the PSTN trunk.
    4. For the other NCT-type NCR protocols, no administration is required for the Route Pattern screen associated with the ARS Digit Analysis screen entry. NCR call processing automatically causes the Service/Feature and Number Format for the NCR second leg call to be unknown/unknown.
    5. Contact your PSTN service provider to verify the configuration of the PSTN switch used for the NCT operation. Configure the PSTN switch to accept the outgoing digits used by the station or the ASAI application to set up the second leg of the call transfer or conference.