SIP Registration with Avaya
| Site: | QSC |
| Course: | Q-SYS Quantum Level 1 Training (Online) |
| Book: | SIP Registration with Avaya |
| Printed by: | Guest user |
| Date: | Wednesday, 4 December 2024, 12:02 AM |
Description
Transcript
00:00
[Music]
00:08
Hi everyone, today our topic with be SIP telephony and some basic scenarios.
00:13
In the Quantum ‘Introduction to SIP Telephony’ topic,
00:16
we discussed the underlying technology of SIP telephony,
00:19
but in this section we’ll look at SIP telephony specifically integrating to an Avaya system.
00:24
We’ll go through the setup of a typical connection to an Avaya system
00:28
and how it works with the Q-Sys core.
00:31
In this particular case,
00:32
we’ll explore the methods for integrating the Q-SYS softphone to an Avaya system.
00:37
An Avaya system typically consists of two components – a session manager or SM,
00:43
and a communication manager, or SM.
00:46
SIP Endpoints register to the session manager and the communication manager handles
00:51
other functions including communication to the larger PSTN network.
00:55
We’ll test this integration by making test calls to and from Q-SYS
00:59
from a softphone application running on a PC.
01:03
Keep in mind the topology here is greatly simplified from an
01:06
actual enterprise VoIP deployment,
01:08
but the basic concepts shown here should apply to any running Avaya implementation.
01:14
In your network you may have additional devices like routers and firewalls,
01:17
and switches not pictured here.
01:19
The steps will be as follows:
01:20
In this case, devices attempt to register to the session manager.
01:24
It checks the credentials of each endpoint and responds accordingly.
01:28
The endpoints can make calls when and only when they’re registered with the session manager.
01:33
There are two different methods required to interface Q-SYS to Avaya
01:37
depending on the number of Q-SYS
01:39
softphones required in your project and your preferred setup.
01:42
In this workshop we are going to focus on softphone registration.
01:46
The scenarios described here are specific to Avaya.
01:50
Other systems have different ways of handling
01:52
these implementations and will be discussed in other trainings.
01:56
The steps to configure an account in Avaya for the Q-SYS Softphone are as follows:
02:01
First we create a User profile that will be used for the Softphone.
02:05
This will contain the authentication credentials.
02:08
Next we create a Communication Address that includes the extension and an optional domain.
02:15
Third we configure an Application Sequence that includes the Session Manager(s)
02:19
being used and specifying that sip users will be using it.
02:24
Last we configure an Endpoint Profile which assigns the extension to an endpoint
02:29
and specifies items like the phone type.
02:32
Let’s take a look at each of these in detail.
02:35
Navigate to Home→Users→User Management→Manage
02:41
Users and we see a few fields we need to configure.
02:44
This configuration is automatically synchronized with Communication Manger.
02:49
Let’s see what needs to be in those fields for a new user profile.
02:53
Fill in the fields on the previous screen as shown above to configure a New User Profile.
02:59
These credentials will be the ones we eventually use
03:01
to configure the softphone in core manager later.
03:05
Click the Communication Profile tab, then click
03:09
New to define a Communication Address for the new SIP user.
03:14
After you click ‘New’ you will see this screen. Select ‘Avaya SIP’ as the type.
03:19
This is the default as well. Then put in the extension number and sip domain. Then click ‘OK’.
03:26
Next, in the Session Manager Profile section, specify the Session Manager(s) and assign the
03:32
Application Sequence to both the Originating Sequence and Termination Sequence fields.
03:37
Think back to our SIP messages. In the Register message we had a ‘Contact’ header.
03:38
In other SIP messages we recall that they contain SDP which has the parameters to set up our audio.
03:38
Our last step is to configure an Endpoint Profile.
03:42
System: Select the managed element corresponding to Communication Manager
03:47
Profile Type: Select Endpoint
03:51
Use Existing Stations:
03:53
If field is not selected, the station will automatically be added in Communication Manager
03:59
Extension: Enter extension number of the SIP user
04:03
Template: Select a template for the type of SIP phone
04:07
That’s it on the Avaya side.
04:09
Let’s move on to the core manager side and see how things correspond to what we have done here.
04:15
Now that the account is set up in Avaya, we turn our attention to the setup in Q-SYS Core Manager.
04:21
First and foremost we must confirm the core network configuration…
04:25
we want to make sure the correct Q-SYS NIC is connected to the VoIP network
04:29
and the correct IP address options are chosen.
04:32
We spent a substantial amount of time on this in the networking sections of Quantum training,
04:36
so we’ll trust that we know how to accomplish this.
04:39
The next step is to confirm the shared settings for all softphones.
04:44
In this setup we will use LAN A as the VoIP interface.
04:48
The SIP signaling port is set to 5060, which again is the default.
04:53
This is the SIP signaling port for the core and is used for incoming calls to the core.
04:58
The port used for outgoing calls to talk to Avaya is set later.
05:03
SIP logging is enabled, which will be a useful troubleshooting tool if we run into problems.
05:08
The rest of the shared settings we covered in Quantum training before
05:11
but a quick refresh of the typical settings is shown.
05:15
SRTP is normally disabled. DTMF INFO is disabled as well.
05:20
Avaya does not typically use this method. The DTMF type is also fine for this application.
05:26
STUN is also disabled.
05:28
This applies mostly to hosted SIP solutions when
05:31
the core is behind a firewall which is not the case here.
05:35
Now let’s look at the individual Softphone settings.
05:38
The ‘proxy’ field specifies the address of the Avaya session manager server.
05:43
In some scenarios a network can have more than one Avaya server.
05:46
In redundant proxy applications, there’s a ‘Backup Proxy’ field to point to the secondary unit.
05:52
By default the proxy is using port 5060 but if you
05:56
need a different port you can append it to the proxy ip with a ‘:’.
06:01
In this case we do want to register with the proxy. Most systems require
06:07
this level of security, including this one.
06:09
The transport setting selects the method of SIP communication required for Avaya.
06:14
In this case, Avaya is set to UDP.
06:18
We now move to the individual account settings we set in Avaya.
06:22
The ‘Username’ field represents the extension number assigned in Avaya.
06:26
These two fields must match or we will not register.
06:29
The Authentication ID represents the login name in the Avaya setup that we configured earlier.
06:35
In this case it will match the extension but it could
06:38
be configured differently depending on how the Avaya side was configured.
06:42
At this point we should be able to go to our softphone block in our design
06:46
and see the softphone successfully registered.
06:48
If more than one extension is needed go back and repeat the process for another softphone.
06:54
That’s it for Avaya setup.
06:56
In future sessions we’ll take a look at connecting to other types of systems
07:00
and some further information on advanced SIP features on the core.