SOP: TTC Support
For Avaya IP Office – Tier 1 & Tier 2
VPN, ScreenConnect, and 8x8 (for calls to customers to look like they are coming from TTC rather than appearing as spam) login information can be found in 1Password. Some TTC customers are already used to dealing with Aura and have Chad on Teams chat. To access ScreenConnect for TTC support, please follow the steps below:
1. Go to https://alltrust.screenconnect.com/
2. On the upper right, select "Login"
3. Enter the username and password information. This is located in 1Password.
4. A temporary code will be sent to HubSpot as a ticket. Enter the code provided.
5. Close the ticket
Please see below for steps to complete common support tasks. Please note all time spent on ticket support needs to be tracked in 15 minute increments on Timeneye. It is best practice to immediately log any activity once a ticket is resolved.
1. Adding a New User and Extension
Objective: To add and configure a new user and extension in Avaya IP Office.
Scope: Applies to Tier 1 support configuring new users in IP Office Manager.
Prerequisites:
- IP Office Manager installed
- Admin credentials
- Available extension number
- User details (name, login code)
Procedure:
- Launch IP Office Manager and connect to the control unit.
- Retrieve the configuration (File > Open Configuration).
- Navigate to 'Extension' and create a new extension with appropriate type.
- Go to 'User' and create a new user.
- Link the user to the extension and assign login code.
- Configure voicemail options if required.
- Save and merge the configuration.
Validation: Users can log in to the phone, and voicemail is accessible.
Escalation Criteria:
- Extension not registering
- Voicemail not activating
- Configuration upload fails
2. Creating and Assigning a Hunt Group
Objective: To create a hunt group and assign users for shared call distribution.
Scope: Tier 1 task to configure call groups.
Prerequisites:
- IP Office Manager access
- List of extensions for group
Procedure:
- Open IP Office Manager and retrieve configuration.
- Go to 'Hunt Group' > Right-click > New.
- Enter name, extension, ring mode (e.g., rotary, group).
- Add members from available users.
- Set voicemail and overflow if needed.
- Save and merge configuration.
Validation: Test inbound call to the group. Confirm phones ring as configured.
Escalation Criteria:
- Members not receiving calls
- Overflows not working properly
3. Building an Auto Attendant in Voicemail Pro
Objective: To build an automated call menu for routing.
Scope: Tier 1 and Tier 2 support building and maintaining AA flows.
Prerequisites:
- Voicemail Pro client access
- Module names and menu prompts
Procedure:
- Launch Voicemail Pro Client.
- Connect to the correct voicemail server.
- Create a new module (e.g., MainAA).
- Add a 'Menu' action with options (1 for Sales, 2 for Support).
- Use 'Transfer' actions to route to destinations.
- Save and test module.
- Link it via Incoming Call Route in IP Office Manager.
Validation: Call into the system and navigate menu options successfully.
Escalation Criteria:
- Menu fails to load
- Call transfers to wrong location
4. Configuring a SIP Trunk
Objective: To configure SIP trunk for inbound and outbound calling.
Scope: Tier 2 supports configuring external carrier trunking.
Prerequisites:
- ITSP credentials
- SIP domain and IP address
- IP Office Manager access
Procedure:
- Go to Line > New > SIP Line.
- Input carrier IP and domain.
- Configure Transport settings (UDP, TCP, TLS).
- Set SIP URI parameters.
- Create inbound and outbound routes.
- Save and merge.
Validation: Make inbound and outbound test calls successfully.
Escalation Criteria:
- SIP trunk not registering
- One-way audio or failed calls
5. Performing a Backup of System Configuration
Objective: To save and secure IP Office configuration.
Scope: Tier 1 and Tier 2 perform regular backups.
Prerequisites:
- IP Office Manager access
- Config file storage location
Procedure:
- Launch IP Office Manager.
- Connect and retrieve configuration.
- Go to File > Save As.
- Save with clear filename and date.
- Store file securely.
Validation: File is saved and can be opened without error.
Escalation Criteria:
- Config file fails to save
- Incorrect or outdated file saved
6. Upgrading IP Office Firmware
Objective: To upgrade IP Office firmware for feature or patch purposes.
Scope: Tier 2 planned maintenance activity.
Prerequisites:
- Firmware files from Avaya
- Maintenance window
- Backup of current config
Procedure:
- Use IP Office Manager to verify current version.
- Download matching upgrade file.
- Use Upgrade Wizard or Advanced > Upgrade.
- Select unit and apply update.
- Reboot system and verify new version.
Validation: System boots cleanly with new version number.
Escalation Criteria
- Upgrade failure
- Devices fail to register post-upgrade
7. Troubleshooting No Dial Tone
Objective: To resolve cases where phones show no dial tone.
Scope: Tier 1 issue investigation.
Prerequisites:
- Phone access
- System Status App (SSA)
Procedure:
- Confirm phone is powered and connected.
- Check extension mapping in Manager.
- Use SSA to verify registration status.
- Move phone to known-good port for testing.
- Restart phone or extension if needed.
Validation: Dial tone is restored, and calls are possible.
Escalation Criteria:
- Hardware failure suspected
- SSA shows line/channel errors
8. Capturing SIP Traces with Avaya Monitor
Objective: To gather SIP logs for troubleshooting call failures.
Scope: Tier 2 advanced diagnostics.
Prerequisites:
- Monitor tool installed
- Admin access to system
Procedure:
- Launch Avaya Monitor.
- Select filters: SIP, H.323, Call.
- Reproduce the issue.
- Observe SIP messages (INVITE, TRYING, 200 OK).
- Save log to file for analysis.
Validation: Call traces show expected signaling. Useful log collected for issue analysis.
Escalation Criteria:
- Logs show carrier-side failures
- Need for packet capture beyond SIP layer
9. Resolving Licensing Errors (PLDS)
Objective: To identify and resolve IP Office licensing issues.
Scope: Tier 2 support with Manager or Web Manager.
Prerequisites:
- PLDS license files
- Control unit serial number
Procedure:
- Open IP Office Manager > License tab.
- Check for missing/expired licenses.
- Log in to PLDS and generate license XML.
- Import into Manager.
- Save and merge.
Validation: System no longer shows 'License Error' and all features function.
Escalation Criteria:
- Mismatched serial numbers
- PLDS portal errors
10. Creating Custom Time-Based Call Routing
Objective: Building call flows based on business hours or holidays.
Scope: Tier 2 using Voicemail Pro.
Prerequisites:
- Time profile definitions
- Voicemail Pro access
Procedure:
- Open Voicemail Pro client.
- Create new time profile (e.g., Mon–Fri 9am–5pm).
- Add 'Condition' action and select time profile.
- Route calls differently for open/closed hours.
- Save and test.
Validation: Calls follow correct paths based on time of day.
Escalation Criteria:
- Profiles not triggering
- Errors in schedule logic