Branch PSTN call routing examples to those calls.

7. Click OK.

8. Select File > Save Configuration.

PSTN trunk fallback

In branch scenarios where centralized call control and trunking (see Centralized call control

on page 291) has been configured for certain calls, loss of the Avaya Aura

®

Session Manager line connection will impact making those calls. For instance, in our example where all branch national and international calls are routed via the headquarters site, loss of the Avaya Aura ®

Session Manager line will leave the branch users only able to make local calls.

Since loss of the Avaya Aura

®

Session Manager line should only be an infrequent and temporary condition, some restriction during that state may be acceptable. However the following options can be used to allow continued branch operation:

• If the headquarters site has multiple Avaya Aura ® Session Managers for redundancy, each branch can also be configured with multiple Avaya Aura ® Session Manager lines. See

Avaya Aura Session Manager line redundancy on page 152 for more information.

• As in our example business, centralized call control has not been applied to all branch local calls. Therefore local calls are still available without any additional configuration for the loss of the Avaya Aura ® Session Manager line connection.

• Since loss of the Avaya Aura

®

Session Manager line should be infrequent and temporary, the loss of some services may be tolerable until the Avaya Aura ® Session Manager line issue is resolved. However, even if that is the case, it may be recommended to configure

296 Implementing B5800 Branch Gateway for a CS 1000 Configuration

Comments? [email protected]

October 2012

PSTN trunk fallback a headquarters PSTN number that can be dialed to report the Avaya Aura

®

Session

Manager line issue. See Branch PSTN override

on page 294 for more information.

• Provide PSTN trunk fallback within the branch configuration. See Configuring PSTN trunk fallback

on page 297. Note however that PSTN fallback will also occur when the number of external calls exceeds the available SIP trunk licenses.

Note:

If you want to have long distance routing on local trunks, be sure that the appropriate trunks have been ordered from the local provider. Do not create a route for international phone calls if you do not have that service.

Configuring PSTN trunk fallback

About this task

Use this procedure to provide PSTN trunk fallback with the branch configuration.

Procedure

1. Start Manager and connect to the B5800 Branch Gateway system.

2. In the left navigation pane, click ARS.

3. Click the New icon and select ARS.

4. Enter a Route Name, for example PSTN.

5. To add a short code click the Add... button.

A short code is required that will send the national calls to the branch's own PSTN.

Enter the normal defaults for such a short code as follows:

6. Make the changes as follows: a.

In the Code field, enter 1N;. For this example, 1N; will match any national number dialing.

b.

In the Feature field, leave the entry set as Dial3K1.

c.

In the Telephone Number field, enter 1N. For this example 1N will match the number dialed by the user after the dial 9 prefix.

d.

In the Line Group Id drop-down box, select the line group used for the B5800

Branch Gateway system's external trunks. The default is 0.

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 297

Branch PSTN call routing examples

7. Click OK.

8. Click OK.

9. Double click on the existing default ARS that was reconfigured to send all branch national and international calls to the Avaya Aura ® Session Manager line.

10. In the Additional Route drop-down box , select the PSTN ARS form just created above.

The form is now set such that, if the Avaya Aura ® Session Manager line is not available (out of service or all licensed channels busy) calls can be checked for a dialing match in the PSTN ARS form. This works as follows:

• The Alternate Route Priority Level controls which users are able to use the alternate route immediately, ie. those user's whose priority is equal or higher than this setting. The default priority for users is 5.

298 Implementing B5800 Branch Gateway for a CS 1000 Configuration

Comments? [email protected]

October 2012

PSTN trunk fallback

• The Alternate Route Wait Time is used for caller's whose priority is not sufficient to use the alternate route immediately. The default setting is 30 seconds. However, you may want to adjust this setting to one that meets your requirements.

• Since the only short code match in the alternate route in our example is for national calls, international calls will continue to wait for the Avaya Aura

®

Session Manager line.

11. Select File > Save Configuration.

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 299

Branch PSTN call routing examples

300 Implementing B5800 Branch Gateway for a CS 1000 Configuration

Comments? [email protected]

October 2012

Appendix D: Authorization codes

Authorization codes are not shown by default. IP Office Manager must be modified in order to support authorization codes. Each authorization code is associated with a particular user or user rights set. The user or users associated with the user rights can then dial numbers which are set to trigger forced authorization code entry. Once a code is entered, the short code settings of the user or user rights with which the code is associated are used to complete the call. This allows authorized users to make otherwise restricted calls from any extension without first having to log in to that extension and then log out after the call.

How authorization codes work

• A user dials a number that matches a short code set to Force Authorization Code.

• The user is prompted to enter an authorization code.

• They dial their authorization code. If a matching entry is found in Authorization Codes entries, the system checks the corresponding user or user rights (in that order). Note that the user or user rights checked does not necessarily need to be connected with the user dialing or the user whose extension is being used to make the call.

- The dial string is checked against the short codes with the matching user or user rights.

- If it matches a dial short code or no short code, the call is allowed. Otherwise, it is blocked. Note that the short code is not processed, it is just checked for a match.

- If multi-tier authorization codes are required, there must be blocking (busy) short codes (or a wild card '?' )

Example

A restaurant has a number of phones in publicly accessible areas and wants to control what calls can be made from these phones. They want these phones to allow anyone to make local calls, restrict restaurant staff to local and cell phone numbers (044...), and allow the manager to also be able to call long distance numbers (01...). The following table shows how this is configured.

ARS Table

In the Main (50) ARS table, the following short codes are added:

• 044XXXXXXXXXX / 044N / Dial / Force Auth Code

• 01XXXXXXXXXX / 01N / Dial / Force Auth Code

Authorization Codes

The following two authorization codes are configured:

• 2008 is associated with a set of User

Rights called Cell.

• 1983 is associate with a set of User Rights called LDandCell.

User Rights

Cell LCandCell

Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 301