User Support Level 2

Note	The features and/or parameters listed in this article may not be available from your telephone service provider.

Home Support

Download PDF

Introduction

The supporter finds here instructions how to handle a user's level 2 telephony problems:

• Best Practice for Handling an User Problem
• Record the Customer's Data and Problem Description
• Analyzing the Customer Problem
• Solving the Customer Problem

→ Top

Introduction Support Level 2

The level 2 support is the first instance where the user's telephony problems are handled that a user cannot solve himself. Additionally the level 2 supporter must be able to detect if the user problem is a "single" problem or if there is a large scale problem, that produces the same problem for multiple customers, e.g. data transfer problems in the Internet so that no VoIP call signaling is possible.

The level 2 supporter must be aware of the complexity of a VoIP system and the multitude of telephony solutions on the user side. Further he needs an understanding of:

• IP networking
• VoIP protocols SIP for signaling, SDP and RTP for speech transmission.

Overview of a VoIP system and the multitude of user telephony solutions:

The level 2 supporter faces problems with the following layers:

1. Equipment
2. IP data transfer
3. Telephony service

And each of this layer can be located into the following raw areas:

1. Customer/User site
2. Internet Service Provider ISP
3. Telephony Provider

This layer and dividing into areas produces a "3x3 Support Matrix":

Within this "3x3 Support Matrix" the supporter can:

• advice the customer what to do when the problem is located in the nodes 1-T, 1-D and 1-E
• check the customer configurations on the VoIP Switch, node 3-T, and, if he has operator rights, adjust configurations.

For the other cases the level 2 supporter must be able to identify if:

• the user must contact his ISP, due to possible Internet access problems
• the VoIP System administrator must be involved, due to possible telephony service problems

Hint:

These cases indicate mostly large scale problems within the VoIP system!

→ Top

Best Practice for Handling an User Problem

Best Practice

Record the customer's data and problem description: Get the customer data Get the customers use case Get the problem description from the customer Show me how ...   Cross check the user input against the VoIP switch configuration and logs. Via ConfigCenter check the users account configuration: Telephone number registration TopStop RuleSet Consult the "Call Data" for the last connection attempts and connections longer than 2min Show me how ...   Check the big picture: If you are sure that the problem is "single" one continue with the next step "Solve the customer problem" If you suspect that the customer is not the only one with this problem within a short time range, e.g. 30min, then contact the VoIP switch administrator/operator if there is known issue in the VoIP system that causes this type of problem. Show me how ...   Solve the customer's problem: You have now enough basic information for solving the customer's problem Show me how ...   If you are not able to solve this problem then contact the provider support. Have ready all collected information and what you have done and found out until now.

→ Top

Record the Customer's Data and Problem Description

→ Top

Get the Customer's Data

From the customer get:

• Name of the caller
• Telephone number of the caller
• if applicable the company name

→ Top

Identify the Customer's Use Case

From the customer get if it is a:

• Residential user
• Business "Legacy ISDN PBX"
• Business "IP PBX with SBC"
• Business "SIP Trunk / IP PBX"
• "vPBX"
• etc

If the customer doesn't know then identify via the ConfigCenter the telephone number and its associated account.

→ Top

Note the Customer's Problem Description

From the customer get:

• Date and time of the issue
• The involved telephone numbers
• The problem description

If the customer doesn't know then identify via the ConfigCenter the telephone number and its associated account.

→ Top

Cross Check the User Inputs

With this cross check the supporter can validate the user information, gets an impression of the state of the account and will probably find the reason for the user problem...

Via ConfigCenter check the users status and account configuration on the VoIP Switch:

1. Check the telephone number registration status.

   If there is no registration you can proceed directly with The user device is not registered ...

2. Check "TopStop":

   Check if a TopStop in the account or address prevents the user from doing outgoing calls.

3. Check "RuleSet":

   Check if a RuleSet in the account or address prevents the user from doing outgoing or receiving calls.

4. Check "Call Forwards" or "Call Rejecting":

   Check if a "Call Forwards" or "Call Rejecting" in the account prevents the user from doing outgoing or receiving calls.

5. Check "Call Data":

   Consult the "Call Data" for the last connection attempts and connections longer than 2min of the user.

→ Top

Check the Big Picture

At this point the supporter should get aware if the problem is limited to this user or if it could be large scale problem within the VoIP System.

If the supporter suspects a large scale problem, due to a great amount of the same ore similar user complains then he should contact the telephony provider support or emergency organization.

If the supporter has enough privileges he can check:

1. The VoIP Switch component status

   This will show if the VoIP Switch itself hat a problem.

2. The VoIP System monitor

   Here you can check if:

   • The registrations dropped in a large scale
   • The calls dropped in a large scale
   • The IP connectivity somewhere in the VoIP system failled

At any rate the supporter must inform the VoIP system administrator!

→ Top

Analyzing the Customer Problem

During this first step the supporter shall identify the user's problem.

By interviewing and checking the facts the supporter must be able to collect all basic information:

By identify the user's use case the supporter can selectively optimize the questioning.

→ Top

Use Case "Residential" Questioning

Use Case Residential

→ Top

Solving the Customer Problem

→ Top

Solve Problem: The User Device does not Register

1 Check: Review the account and telephone number configuration

	Customer	Internet ISP	Telephony Provider
Telephony			Check via ConfigCenter: Does the telephone number exist? Is the telephone number valid? Is the user account valid? Actions: Check why the account, telephone number doesn't exist or is disabled and activate if allowed.
Data Transfer
Equipment

2 Check: Where REGISTER messages received from the device on the VoIP Switch?

	Customer	Internet ISP	Telephony Provider
Telephony			In the "Support Log" search for the device registration in the present and past time. Set the "Support Log" filters Insert at "Text" the account name Insert at "From" - "Until" a reasonable time span where registrations could be expected Select the category: "Registration" Start the search and find out according the results what is going wrong. If needed repeat the search with the telephone number in the "Text" or other time spans
Data Transfer
Equipment

Failed registrations due to disabled account or address:

2017-09-15-07:56:49.553 Registration failed, disabled account aan1-00093 tried to register number 0449980010

Actions:

• Check why the account is disabled and activate if allowed.

Failed registrations due to wrong SIP credentials:

2017-09-15-08:05:38.117 Registration failed, invalid credentials for account acc-01 2017-09-15-08:05:39.112 Registration failed, unknown username 'myusername' tried to register '0123456789' 2017-09-15-08:05:38.377 Registration failed, unknown number '0987654321' tried to register for account acc-01

Actions:

• The user must manually adjust the SIP credentials on the device
• The user must re-configure the device via AdminCenter

The device didn't refresh its registration:

2017-09-15-07:59:00.862 RegID989961 ended for 0987654321 ip=111.111.111.111:65398 ua=my-device v1.0

Actions:

• Check if the device is really on-line! Device defect? power? patch? IP address? → see below

For information a successful registration:

2017-09-15-07:59:30.383 RegID989965 started for 0987654321 ip=111.111.111.111:65398 ua=my-device v1.0

Hint:
The supporter might try to find REGISTER messages from the device in the "Trace" . This gives the certainty that the message was received by the VoIP switch. The supporter can filter for the telephone number. If the IP address is needed then the customer must be able to tell or evaluate it, e.g.:

https://www.whatismyip.com/

3 Check: Is the device is correctly configured for registration?

	Customer	Internet ISP	Telephony Provider
Telephony	Check that the device has the correct configuration for: Telephone number SIP credentials VoIP Switch domain configuration Actions: The user must manually adjust the SIP credentials on the device The user must re-configure the device via AdminCenter
Data Transfer
Equipment

4 Check: Is the device is powered on, not defect, connected to the IP network?

	Customer	Internet ISP	Telephony Provider
Telephony
Data Transfer
Equipment	Is the device correctly powered? Does the device show power on indication, e.g. display on, LED on? Actions: The user must check the power cable and if it is correctly plugged in → replace the power cable → replace defect device if the powering is ok but no working indication is displayed Is the device correctly connected to the IP network? Are there LED flashing or glow next to the network plug on the device or at the peer device (access router, IP switch)? Actions: The user must check the patch cable and if it is correctly plugged in → replace the patch cable → plug in the patch cable at a different port at the peer device (access router, IP switch)

5 Check: Has the device an IP address and can access the Internet?

	Customer	Internet ISP	Telephony Provider
Telephony
Data Transfer	Has the device got an IP address? Check on the device if it has received an IP address, e.g. via display or maintenance GUI. Actions: If no IP address was assigned the user must: → Check if the device is really connected to the IP network → if the DHCP service in the IP network is running If the user cannot check the DHCP service he must contact the company IT responsible or the responsible of maintaining the access router.
Equipment

2. Was the device registered in the past?
3. Where outgoing and/or incoming calls possible in the past?

→ Top

Solve Problem: Incoming Connections are Failing

Instruction how to solve failing incomming connections, e.g.:

• User device not correctly registered
• Wrong calling number
• User device not correct configured

→ Top

Solve Problem: Outgoing Connections are Failing

Instruction how to solve failing outgoing connections, e.g.:

• User device not correctly registered
• Wrong called number
• User device not correct configured

→ Top

Solve Problem: Irregular Connection Release

Instruction how to solve irregularly released user connections, e.g.:

• Failing Session Timer

→ Top

Solve Problem: Disturbed Speech Transmission

Instruction how to solve disturbed speech transmission, e.g.:

• Short interruptions during the connection
• No transmission in one direction from the beginning of the connection
• No transmission in both directions from the beginning of the connection

→ Top

Solve Problem: Disturbed FAX Transmission

Instruction how to solve interrupted FAX transmission, e.g.:

• Fax transmission doesn't start
• Not all pages are transmitted

→ Top

Solve Problem: DECT Multi-Cell Handsets are not Working

Instruction how to solve problems with DECT Multi-Cell handsets, e.g.:

• Hand over from cell to cell not working
• Bad speech quality

→ Top

---

© Aarenet Inc 2018

Version: 3.0     Author:  Aarenet     Date: May 2017