AudioCodes SBC

Advanced Teams

Practical Exam

AudioCodes Academy
https://www.audiocodes.com/services-support/audiocodes-academy
General information
• 3 Softphones and Mediant SBC are connected according to the setup in the next pages
• You are requested to configure your Mediant acting as an SBC and make test calls based on
the instructions defined in the next pages
• The configuration consists of several steps. Every step successfully accomplished will be
considered for the final score you will receive at the end of the exam
• The exam duration will be 3 hours. After this time you will be requested to stop the
configuration and tests and :
1. Save the configuration file (ini file) on the lab PC desktop. Use your name as the file name.
2. Send the file to by mail to the Instructor .
• Allowed documents to be used – AudioCodes User Manuals and training presentations

Good Luck
2
Introduction TK5
• The exam is based on a remote online environment and will be accessed by using a PC/Laptop running the
TeamViewer application to logon remotely to a Virtual PC running in the Lab Environment
• The following information is going to be used to access the different entities:

Lab Environment Training Kit 5

Student Mazin Ahmed Sebastian Shaun Kreyan
ID 1177 865 695 1401 777 728 1177 415 028 1185 876 857 1185 876 682
TeamViewer ID
Password AUDC12$
PC Name PC01 PC02 PC03 PC04 PC05
Username User1 User2 User3 User4 User5
Virtual PC
Password 123456
IP Address 10.15.11.20 10.15.12.20 10.15.13.20 10.15.14.20 10.15.15.20
Username Admin
SBC Password Admin
IP Address 10.15.11.1 10.15.12.1 10.15.13.1 10.15.14.1 10.15.15.1

• NOTE: Wherever you see an x (red x) please replace it with the Student number o which you have been assigned
3
Introduction TK5
• In every Virtual PC you will find the 3 following softphones with the configured characteristics:

User Name /
SoftPhone Transport Port
Phone Number

Teams TLS 5061 +xxxx555x005

Linphone TCP 5068 xxxx555x201

MicroSIP UDP 5060 xxxx555x101

Note the ‘x’ has to be replaced by the group number

4
Introduction TK6
• The exam is based on a remote online environment and will be accessed by using a PC/Laptop running the
TeamViewer application to logon remotely to a Virtual PC running in the Lab Environment
• The following information is going to be used to access the different entities:

Lab Environment Training Kit 6

Student Wojciech Satheesh Gift Jarrod
ID 1497629219 1493862905 1496211036 1496211246
TeamViewer ID
Password AUDC12$
PC Name PC1 PC2 PC3 PC4 PC5
Username User User User User User
Virtual PC
Password 123456
IP Address 10.15.111.20 10.15.112.20 10.15.113.20 10.15.114.20 10.15.115.20
Username Admin
SBC Password Admin
IP Address 10.15.111.1 10.15.112.1 10.15.113.1 10.15.114.1 10.15.115.1
• NOTE: Wherever you see an x (red x) please replace it with the Student number o which you have been assigned
5
Introduction TK6
In every Virtual PC you will find the 3 following softphones with the configured characteristics:

User Name /
SoftPhone Company Transport Port
Phone Number

Teams Microsoft ® TLS 5061 +xxxx777x005

Linphone Linphone ® TCP 5068 xxxx777x201

MicroSIP MicroSIP ® UDP 5060 xxxx777x101

Note: The ‘x’ has to be replaced by the group number

6
Lab Environment – TK5
Teams Direct Routing
FQDN: according to
MSFT requirement Internet
Transport Type: TLS
Listening Port: 5061
Coder: SILK only
SRTP Only Firewall
Allows DTMF as RFC
2833 only DMZ: 195.189.192.25x/25

Mediant SBC LAN: 10.15.1x.1/16

Teams Public Provider Emulation
(not to be configured by the student)
+xxxx555x005 ITSP
LAN
10.15.10.5/16
Transport Type: TCP
IP-PBX
Listening Port: 5068
10.15.1x.20/16
Transport Type: UDP MicroSIP Coder: G.723.1 only
Linphone RTP Only
Listening Port: 5060
Sends DTMF as INFO
Coder: OPUS only xxxx555x101 Messages
RTP Only xxxx555x201

7
Lab Environment – TK6
Teams Direct Routing
FQDN: according to
MSFT requirement Internet
Transport Type: TLS
Listening Port: 5061
Coder: SILK only
SRTP Only Firewall
Allows DTMF as RFC
2833 only DMZ: 195.189.192.14x/25

Mediant SBC LAN: 10.15.11x.1/16

Teams Public Provider Emulation
(not to be configured by the student)
+xxxx777x005 ITSP
LAN
10.15.10.6/16
Transport Type: TCP
IP-PBX
Listening Port: 5068
10.15.1x.20/16
Transport Type: UDP MicroSIP Coder: G.723.1 only
Linphone RTP Only
Listening Port: 5060
Sends DTMF as INFO
Coder: OPUS only xxxx777x101 Messages
RTP Only xxxx777x201

8
Instructions

• Procedure
1. Configure the Mediant SBC
2. Make calls between all the entities
3. Open Syslog and verify the connection was established as requested

Note:
• The only device that you need to configure is the SBC (10.15.1x.1) or
(10.15.11x.1)
• Don’t upload any LAB ini File

9
Teams Information
• Teams
• Based on Microsoft Teams Direct Routing
• FQDN: according to MSFT requirement
• Transport Type: TLS
• Listening Port: 5061
• Coders: Silk Only Teams
• SRTP only
• InBand DTMF based on RFC 2833
• Start Media Port: 9000
• Number Of Media Session Legs: 30

• The Teams Client allows calls based on:

• The specific number: +xxxx555/777x005
• Working based on full E.164 number standard (for outbound and inbound calls)
• Format: +[Country Code][National Area Code][subscriber number]
10
ITSP Information

• ITSP SIP Trunking Server:

• Based on Mediant SBC with a Linphone Softphone
Public Provider Emulation
• IP address: 10.15.10.5 (not to be configured by the student)

• Transport Type: TCP

• Listening Port: 5068
• Coder: G.723.1 only
• RTP Only Linphone
• Sends DTMF as INFO Messages
• Start Media Port: 8000
• Number Of Media Session Legs: 30
• ITSP doesn’t accept OPTIONS messages

• The ITSP’s attached Linphone will ring when the following number is dialed:
• The ITSP DID: xxxx555/777x201

11
ITSP Information

• The ITSP allows calls only based on the following:

• Calls coming from any place (Teams or MicroSIP):
• Should have a Source Host = “Customerx.Provider” and a Destination Host = “Provider.COM”

• For calls coming from Teams

• The Name of the From Header as well as the username on the origin line (o=) of the SDP should be
“tr-userx”
• Incoming calls have 2 P-asserted-identity headers. Only the sip: is accepted

• For calls coming from the IP-PBX (MicroSIP)

• The Name of the From Header as well as the username on the origin line (o=) of the SDP should be
“IP-PBX-User”
• A P-Asserted-Identity header should be added

12
ITSP Information

• Example of allowed calls coming from Teams:

13
ITSP Information

• Example of allowed calls coming from IP-PBX (MicroSIP):

14
IP-PBX Information

• IP-PBX Server:
• Based on MicroSIP Softphone
• IP address: 10.15.1x.20
• Transport Type: UDP
• Listening Port: 5060 MicroSIP

• Coder: OPUS Only

• RTP Only
• InBand DTMF based on RFC 2833
• Start Media Port: 7000
• Number Of Media Session Legs: 20

• The IP-PBX’s MicroSIP will ring when the following number is dialed:
• The ITSP DID: xxxx555/777x101
15
Instructions for the configuration

• Configure the following parameters on the SBC according to the instructions in the
next page:
• Basic Core Components
• Routing Rules
• Classification and Condition Rules
• Transcoding
• Message and Number Manipulation Rules
• Anything else you might need

16
Instructions for the configuration
• For all external connections don’t classify by Proxy Set (Teams, ITSP, IP-PBX)
• Check the following entities and/or existing headers for their following values (total or
partial) and classify by Classification Table:

Classify by For Teams For ITSP For IP-PBX

Source SIP Interface: Related to Teams
Source IP Address: 52.*.*.* 10.15.10.5/6
Destination Host: tr-sbcX.audctrunk.aceducation.info
Contact Header pstnhub.microsoft.com
Header User-Agent Mediant MicroSIP
Session on SDP (s=) Talk pjmedia

Note – TK6 → tr-sbc1x. audctrunk.aceducation.info

17
Test Calls

• Call from Teams:

• To ITSP (Linphone) – Phone: +xxxx555/777x201
• To IP-PBX (MicroSIP) – Phone: +xxxx555/777x101

• Call from ITSP (Linphone):

• To Teams – Phone: xxxx555/777x005
• To IP-PBX (MicroSIP) – Phone: xxxx555/777x101

• Call from IP-PBX (MicroSIP):

• To Teams – Phone: xxxx555/777x005
• To ITSP (Linphone) – Phone: xxxx555/777x201

• Open Syslog and verify the connection was established as requested

18
 Good Luck

Stay in the loop