# Advanced Analog Networking Programming

In the ARS Digit Modification Plans form, ( ) identify the information that you want to outpulse on the appropriate trunk type whenever an outgoing call is made on a system equipped with the AAN feature.

The following information elements are specific to the AAN feature:

- <E> where E specifies the caller's extension number

- <d> where d is the caller's dialed or default account code

- <N> where N is the system Node ID

- <R> where R is the Call Forward reason

- <F> where F is the Call Forwarder's extension number.

For more information, refer to the ARS Digit Modification Plans form.

## Examples

### Network Calls

When you connect two systems, AAN lets you display the calling party's extension on the receiving node's telephones and attendant consoles, provide a new COS and COR to the call, and provide centralized SMDR.

For example, complete the ARS Digit Modification Plans form ( ) as follows:

ARS Digit Modification Plans
Digit Modification Number | Number of Digits to Absorb | Digits to be inserted | Final Tone Plan/ Information Marker
1 | -- | **3<E>#**2<N><E># | --
2 | -- | **2<N><E>#**1<D># | --

In the example, the Node ID is 1234, and the following access codes are pre-programmed onto the receiving node:

Independent Account Code | **1
Trunk Calling Party Identification | **2
Non-verified account code | **3

According to Digit Modification Number 1, if extension 3000 on system A calls extension 4000 on system B, the following digits are outpulsed to system B: **33000#**212343000#4000.

### Display the Calling Party Extension

When the string **2< N><E># is separated out of the digit string at the receiving node, the receiving node realizes that the string between the **2 feature access code (trunk calling party identification) and the "#" character contains the identity of the party calling in on the trunk. The receiving node can then display this information at the receiving console or set.

NOTE: The incoming trunks using the AAN feature must have the Trunk Calling Party Identification option enabled in their Class of Service.

### Set Up Voice Mail

For example, complete the ARS Digit Modification Plans form ( ) as follows:

ARS Digit Modification Plans
Digit Modification Number | Number of Digits to Absorb | Digits to be inserted | Final Tone Plan/ Information Marker
1 | -- | *77<R>#<E>#<F># |

In the example, the following access codes are pre-programmed onto the receiving node:

Call Forwarding - Busy (External Source) | 60
Call Forwarding - Busy (Internal Source) | 62
Call Forwarding - Follow Me | 64
Call Forwarding - No Answer (External Source) | 66
Call Forwarding - No Answer (Internal Source) | 68

The digits to be outpulsed are:

- *77 followed by one of 60,62,64,66,68 if the call is a forwarded call

- followed by a # sign

- followed by the original caller's extension number <E>

- followed by another # sign

- followed by the originally called extension which has call forwarding programmed <F>

- followed by a # sign.

NOTES

- The # is used as a delimiter.

- Information marker <E> works as it does currently. For example, if in the case of a trunk call no digits is received, then no digits will be outpulsed to the voice mail.

### Provide a New COS and COR to a call

In the string **1<D>#, **1 is the programmed feature access code for an independent verifiable account code. Inserting <D> in the string ensures that the caller's dialed or default account code is used to make the call. Depending on the type of account code access code chosen (verified or non-verified), the COS/COR can be used to implement travelling class marks. Verified account codes modify the COS and/or COR of the calling station. Non-verified account codes do not affect the COS/COR and are used exclusively for call accounting purposes. In any case, the incoming account code, verified or non-verified, is stored in the SMDR record. Note that the "#" character must be used to terminate the string.

NOTE: In situations where AAN is not used, an outgoing call uses the COS and COR assigned to the trunk. In a networking situation, every outgoing call from a system has the same COS and COR at the receiving node. The AAN feature enhances the features of the network by providing Travelling Class Marks that provide users with a different COS and COR at the receiving node in the network.

### Provide Centralized SMDR

Because both the system Node ID (< N>), and caller's extension number (<E>), reach the receiving node, the receiving node can place this information in the SMDR record for the call.

### Account Codes over ISDN

Tone plans with a time-out action of "outpulse dtmf" and no tones to detect may be used to switch from sending digits in D channel over ISDN trunks to sending DTMF account codes in B channel.

For example, complete the Call Progress Tone Detection form ( ) as follows:

Call Progress Tone Detection Plan Assignment
Tone Plan Number: 01 | Maximum Wait for a Tone (0-99 Secs) 0 Action on Time-Out: Outpulse DTMF
Tone To Detect | Action to Take

Call Progress Tone Detection Plan Assignment
Tone Plan Number: 02 | Maximum Wait For A Tone (0-99 Secs): 3 Action on Time-Out: Outpulse default
Tone To Detect | Action To Take

In addition, insert the tone plan in the ARS Digit Modification Plans form ( ) as follows:

ARS Digit Modification Plans
Digit Modification Number | Number of Digits to Absorb | Digits to be Inserted | Final Tone Plan/ Information Marker
1 2 3 | 1 | -- | <T01><T02><A01>

In the above example:

- <T01> is the instruction to switch from D channel to B channel.

- <T02> is the instruction to insert a 3-second pause.

- <A01> contains the PIN or account code, which can be replaced by <D> if AAN is used.

Related Topics

- Advanced Analog Networking Description

- Advanced Analog Networking Conditions