Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

SBC Essentials & Configuration Student Lab Guide

Download as pdf or txt
Download as pdf or txt
You are on page 1of 82

AudioCodes SBC Essentials & Configuration (7.2.

200)
Student Lab Guide

AudioCodes Academy
https://www.audiocodes.com/services-support/audiocodes-academy
Introduction

• Five exercises highlight the features and functions of AudioCodes SBC Application
• Use this presentation and the User Manuals to complete the exercises
• After completing, work on your installed AudioCodes products (recommended)
• Hands-on experience is the best way to:
• Master a technology
• Leverage its uses
• Leverage your ability to troubleshoot and assist your customers

2
Introduction (cont.)
• All the labs are based on a remote online environment
• The course is divided into 5 groups and each group has a PC/Laptop to logon to the remote environment
• The PC runs the TeamViewer application to be used to logon remotely to a Virtual PC running in the Lab
Environment
• The following information is going to be used per group:

Group 1 Group 2 Group 3 Group 4 Group 5 Group 6


ID 1327421954 1327421989 1041293686 1041292615 1265583159 1107183062
TeamViewer ID
Password audiocodesblue22 audiocodesblue22 audiocodesblue22 audiocodesblue22 audiocodesblue22 audiocodesblue22
PC Name PC01 PC02 PC03 PC04 PC05 PC06
Username User1 User2 User3 User4 User5 User6
Virtual PC
Password 1234 1234 1234 1234 1234 1234
IP Address 10.15.11.20 10.15.12.20 10.15.13.20 10.15.14.20 10.15.15.20 10.15.16.20
Username Admin
Gateway/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 10.15.16.1
3
Introduction (cont.)
• In every Virtual PC you will find the 3 following softphones with the configured characteristics:

User Name /
SoftPhone Company Transport Port
Phone Number

Skype for
Microsoft ® TCP 5068 xxxx555x005
Business

Linphone Linphone ® TCP 5070 xxxx555x101

MicroSIP MicroSIP ® UDP 5060 xxxx555x101

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


Note 2: The User Name/Phone Number on Linphone and MicroSIP are the same (Needed for Lab 4 – Survivability)

4
Labs Exercises

• Lab 1 – Management Interface Usage


• Getting used to the management interface
• Lab 2 – SBC Routing
• Basic SIP Trunk Configuration
• Lab 3 – SBC Transcoding
• Demonstration of the Transcoding capability
• Lab 4 – SIP Message Manipulation
• Demonstration of the MMS Mechanism
• Lab 5 – SBC Survivability
• Demonstration of the Alternative Routing and PSTN Fallback

5
Hands-on Lab 1

Management Interface Usage


Accessing the system

• Access the system using TeamViewer using the credentials assigned to your Group

• Logon to your assigned virtual PC using the credentials assigned to your Group

• On your virtual PC, run a Web Browser and access your assigned SBC by typing the
address 10.15.1X.1 (being X your Group number)

• Logon to the system using the default User Name and Password (Admin/Admin)

7
GUI based configuration and navigation

• Under the Setup menu go to the IP Network Tab


• Choose the Network View option and take a look at your core networking entities
• Choose the Core Entities option and open the IP Interfaces page
• Change the Default Gateway to 10.15.100.1
• Change the Primary DNS Server to 10.15.10.100
• Save your configuration
• Choose the Physical Ports option and take a look at the status of your Ethernet Ports
• Check the possible values for Speed/Duplex, keep it as Auto Negotiation
• Under the Setup menu go to the Signaling & Media Tab
• Choose the Topology View option and take a look at your core networking entities
• Without changing any value navigate through the different options to get used to them

8
GUI based configuration and navigation

• Under the Setup menu go to the Administration Tab


• Choose the Web & CLI option and take a look at the following
• Currently defined local users
• Web and CLI settings (don’t modify any of those parameters)
• Choose the Maintenance option and check how can you do the following:
• Saving and Loading an INI file
• Uploading auxiliary files (check which auxiliary files)
• Resetting the device
• Checking your current license key
• Upgrading your software (please don’t start this process)

Tip: Is there another way of accessing those pages?

9
GUI based configuration and navigation

• Under the Monitor menu go to the Monitor Tab


• Choose the Monitor View option and take a look at your device information
• Choose the Device Information option and find the following:
• MAC Address
• Serial Number
• Firmware version
• Uploaded files
• Choose both Alarm options and check your active and history alarms

Tip: Is there another way of accessing the Active Alarms page?

10
CLI based configuration
• Access the SBC using Telnet
(use PuTTY, located in the Utilities folder on the desktop)
• Logon to the system
• At the CLI prompt, type the username (case sensitive):
• Username: Admin
• At the prompt, type the password (case sensitive):
• Password: Admin
• At the prompt, type the following:
• enable
• At the prompt, type the password again:

• Password: Admin

11
CLI based configuration
• Show the available commands
• At the prompt, type the following and then press Enter
• ?
• To scroll down and see more pages, press the space bar
• Show the available parameters under the Show command
• At the prompt, type the following and then press Enter
• show ?
• Show your Running Configuration
• At the prompt, type the following and then press Enter
• sh ru
• Take a look at your current configuration and find
similarities with the GUI in the structure
• To scroll down and see more pages, press the space bar

12
CLI based configuration
• Access the network configuration mode:
• # configure network
• Access the Interface table:
• (config-network)# interface network-if 0
• Configure the Default Gateway address:
• (network-if-0)# gateway 10.15.0.1
• Configure the Primary DNS:
• (network-if-0)# primary-dns 10.15.10.1
• Exit the Interface table:
• (network-if-0)# exit
• Exit the network configuration mode:
• (config-network)# exit

Tip: Use the ? at any time to get help for allowed commands and/or parameters
13
AdminPage based configuration
• Run a Web Browser and access your assigned SBC by typing the address 10.15.1x.1
(every x should be replaced with your Group number)
• Logon to the system using the default User Name and Password (Admin/Admin)
• To access the AdminPage use the following URL in your browser
• 10.15.1x.1/AdminPage
• Choose the option ini parameters on the left side menu
• To override the Company Logo Image, use the following parameter
• USEWEBLOGO with a value of 1
• To replaces default AudioCodes logo image with your own text, use the following parameter
• WEBLOGOTEXT with a value of “Group x”

Note: These parameters can only be changed using the AdminPage or by editing and uploading
an ini file
14
ini File based configuration
• While in the AdminPage, go back to the main page by choosing the option Back to Main
• Use either the Actions tab or the Configuration option under the Administration tab to save your configuration
file (ini file)

this

or this

15
ini File based configuration
• Open the saved file by using the INI Viewer&Editor utility and take a look at your configured parameters
• Add a Welcome Message to your SBC, something like this:

Welcome Group x

• Using the supplied documentation, open the Mediant’s user manual and find out what has to be done to add
the mentioned message
• In a similar way as the file was saved, upload the new ini file to your system and see your Welcome Message

Tip: You can upload an INI Incremental file using the Auxiliary Files option. What is the benefit of this?

Result example for Group 1

16
Empty INI file
• Open Notepad
• Don’t enter anything in the file
• Save the file as Empty.ini
• Upload the new ini file to your system
• Is the Company Logo Image switch back
to logo?

17
Auxiliary Files – Incremental INI
• Open Notepad
• Enter the follow to the file:
• USEWEBLOGO = 0
• WEBLOGOTEXT = (= to empty)

• Save the file as Test.ini


• Upload the ini from the Auxiliary Files page
• Is the Company Logo Image switch back
to logo?

18
Hands-on Lab 2

E-SBC Routing
Lab Environment

Mediant – SBC
10.15.1x.1/16

IP-PBX ITSP
10.15.10.2/16 10.15.1x.20/16
Transport Type: TCP Skype for Transport Type: UDP
Listening Port: 5068 IP MicroSIP Listening Port: 5060
50 Media Session Legs Business 50 Media Session Legs
starts from 7000 starts from 8000
+xxxx555x005 xxxx555x101

20
The Goal of the Lab

• Configure all entities for proper routing calls from IP-PBX to ITSP and vice versa

21
Pre Configuration

• IP Interface Table
• Check that the IP Interface: 10.15.1x.1 /16
(don’t change, it is already pre-configured)

22
Media Realm Table

• You can use the default Media Realm (Index 0), but modify the ports
• Configure 2 Media Realms:
• MR-IPPBX:
• IPv4 Interface Name: #0 [Voice]
• From media port: 7000
• Number Of Media Session Legs: 50
• MR-ITSP:
• IPv4 Interface Name: #0 [Voice]
• From media port: 8000
• Number Of Media Session Legs: 50

23
SIP Interface Table

• You can use the default SIP Interface (Index 0), but modify the ports
• Configure 2 SIP Interfaces:
• SIP-IPPBX:
• Network Interface: #0 [Voice]
• Application Type: SBC
• UDP Port: 0
• TCP Port: 5068
• TLS Port: 0
• Media Realm: MR-IPPBX
• SIP-ITSP:
• Network Interface: #0 [Voice]
• Application Type: SBC
• UDP Port: 5060
• TCP Port: 0
• TLS Port: 0
• Media Realm: MR-ITSP
24
Proxy Sets Table

• Don’t delete the Default Proxy Set


• Configure 2 Proxy Sets:
• PS-IPPBX:
• SBC IPv4 SIP Interface: SIP-IPPBX
• Proxy Keep-Alive: Options
• Proxy Address: 10.15.10.2:5068 (in the child table)
• Transport Type: TCP (in the child table)
• PS-ITSP:
• SBC IPv4 SIP Interface: SIP-ITSP
• Proxy Keep-Alive: Options
• Proxy Address: 10.15.1X.20:5060 (in the child table)
• Transport Type: UDP (in the child table)

25
IP Group Table

• Don’t delete the Default IP Group (Index 0)


• Configure 2 IP Groups:
• IPG-IPPBX:
• Type: Server
• Proxy Set: PS-IPPBX
• Media Realm: MR-IPPBX
• Classify By Proxy Set: Enable
• IPG-ITSP:
• Type: Server
• Proxy Set: PS-ITSP
• Media Realm: MR-ITSP
• Classify By Proxy Set: Enable

26
IP to IP Routing Table

• Create the following rules:


• Options termination:
• Source IP Group: Any
• Request Type: OPTIONS
• Destination Type: Internal
• Internal Action: Reply (Response=‘200’)
• ITSP to IP-PBX:
• Source IP Group: IPG-ITSP
• Request Type: All
• Destination Type: IP Group
• Destination IP Group: IPG-IPPBX
• IP-PBX to ITSP:
• Source IP Group: IPG-IPPBX
• Request Type: All
• Destination Type: IP Group
• Destination IP Group: IPG-ITSP 27
Syslog

• Enable Syslog for troubleshooting:


• Enable Syslog: Enable
• Syslog Server IP: 10.15.1X.20 (Your PC IP address)
• Debug Level: Detailed

28
Test calls

• From the ITSP (MicroSIP) call to +xxxx555x005


• Main IP-PBX (SfB) should ring
• From the IP-PBX (SfB) call to +xxxx555x101
• ITSP (MicroSIP) telephone should ring

• Open syslog (It is already installed on the remote PC)


• Verify that the SBC performs the right routing decisions

• Save configuration to Flash


• Save configuration on the Desktop

29
Expected results
ITSP IPPBX
IPPBX ITSP SBC
SBC (MicroSIP) (SfB)
(SfB) (MicroSIP)

30
SBC Wizard (Optional)

• Save the configuration file on your virtual PC


• Restore Factory defaults with
(Preserve Network and Users configuration)
• Make the same SBC configuration that was
done in the previous pages by using the SBC
Configuration wizard integrated in the device
• Apply & Reset
• Perform call tests

31
Hands-on Lab 3

E-SBC Transcoding
Lab Environment

Mediant – SBC
10.15.1x.1/16

IP-PBX ITSP
10.15.10.2/16 10.15.1x.20/16
Transport Type: TCP Transport Type: UDP
Skype for IP
Listening Port: 5068 MicroSIP Listening Port: 5060
Coder: G.711Alaw Business Coder: G.722
+xxxx555x005 xxxx555x101

Continue with configuration from previous Lab applying the codec changes

33
The Goal of the Lab

• Configure appropriated entities for transcoding from


G.711A-law (IP-PBX) to G.722 (ITSP) and vice versa

34
Transcoding – Instructions (See steps in the next slides)

• Coders:
• Change the ITSP (MicroSIP) coders list and enable only G.722, according to the nex pages
(if you need the instructor can do this for you)
• Update ITSP (MicroSIP) & IP PBX (Skype for Business) IP profiles

Note: If Codec G.722 doesn’t appear on your list of codecs, change the DSP template on the SBC to “6”

• Make calls in both directions

35
MicroSIP Settings Configuration for Transcoding

• Mark on the Enabled Codecs column the required codec and


remove it from the list by pressing the left arrow
• Mark on the Available Codecs column the required codec and
add it to the Enable Codecs list by pressing the right arrow
• The final result should be the one shown in the picture
• Press the Save button

36
Pre Configuration

• Change the DSP Template


• Relevant just for Mediant 1000B SBC (If Codec G.722 doesn’t appear on your list of
codecs)
• Change the DSP template on the SBC form “0” to “6”
• Reboot required

37
Coder Groups

• Create new Coder Group and select the following coders:


• G.711A-law
• G722
• Create new Allow Coder Group:
• Allowed-IPPBX:
• In the child table select G.711A-law
• Allowed-ITSP:
• In the child table select G.722

38
IP Profile Table

• Configure 2 IP Profiles:
• Profile-IPPBX:
• Extension Coders Group: Create Coder Group contenting the G.711A-law and G722 coders
• Allowed Audio Coders: Allowed-IPPBX
• Profile-ITSP:
• Extension Coders Group: Create Coder Group contenting the G.711A-law and G722 coders
• Allowed Audio Coders : Allowed-ITSP

39
IP Group Table

• Assign the new IP Profiles to IP Groups:


• Edit IPG-IPPBX IP Groups:
• IP Profile: Profile-IPPBX
• Edit IPG-ITSP IP Groups:
• IP Profile: Profile-ITSP

40
Test calls

• From the MicroSIP call to +xxxx555x005


• Main IP-PBX (SfB) should ring
• From the SfB call to +xxxx555x101
• ITSP (MicroSIP) should ring

• Open syslog
• Verify that the SBC performs the right routing decisions
• Verify that the SBC performs the required transcoding

• Save configuration to Flash


• Save configuration on the Desktop
41
Configuration Result

Skype for
MicroSIP
Business
“IP-PBX” E-SBC “ITSP”
G.711A
Added
G.722

Removed
G.711A
G.722

G.722
Transcoding
G.711A

42
Expected results

IPPBX ITSP
SBC
(SfB) (MicroSIP

43
Expected results (incoming Invite)

IPPBX ITSP
SBC
(SfB) (MicroSIP

44
Expected results (outgoing Invite)

IPPBX ITSP
SBC
(SfB) (MicroSIP

45
Hands-on Lab 4

SIP Header Manipulation


Lab Environment

Mediant – SBC
10.15.1x.1/16

IP-PBX ITSP
10.15.10.2/16 10.15.1x.20/16
Transport Type: TCP Transport Type: UDP
Skype for IP
Listening Port: 5068 MicroSIP Listening Port: 5060
Coder: G.711Alaw Business Coder: G.722
+xxxx555x005 xxxx555x101

Continue with configuration from previous Lab

47
The Goal of the Lab

• Performing Message Manipulations on the existing setup

48
Pre Configuration

• Assign Message Manipulation Set to IP Groups


• IPG-IPPBX:
• Inbound Message Manipulation Set: 1
• Outbound Message Manipulation Set: 2
• IPG-ITSP:
• Inbound Message Manipulation Set: 3
• Outbound Message Manipulation Set: 4

49
Exercise 1: “From” Header Modification

• For all IP-PBX Outgoing messages modify the User part of the “From” header to 999
• Name: Change From Header to 999
• Manipulation Set ID: 1
• Action Subject: Header.From.URL.User
• Action Type: Modify
• Action Value: ‘999’

• From the SfB call to +xxxx555x101 the ITSP (MicroSIP) should ring
• Open syslog/wireshark
• Verify that the SBC performs the right routing decisions
• Verify that the SBC performs the required transcoding
• Verify that the ITSP’s requirements described in the next pages are accomplished
(see the expected results in the next pages)

50
Exercise 1: Expected Result

51
Exercise 2: Add an “Source IP Group” Header

• For Invite messages to IP-PBX add a header called SRC-IPG that will contain the
Source IP Group Name
• Name: Add SRC-IPG
• Manipulation Set ID: 2
• Message Type: Invite
• Action Subject: header.SRC-IPG
• Action Type: Add
• Action Value: Param.IPG.Src.Name

• From the ITSP (MicroSIP) call to +xxxx555x005 the IP-PBX (SfB) should ring
• Open syslog/wireshark
• Verify that the SBC performs the right routing decisions
• Verify that the SBC performs the required transcoding
• Verify that the ITSP’s requirements described in the next pages are accomplished
(see the expected results in the next pages)
52
Exercise 2: Expected Result

53
Exercise 3: Change the Host of the To Header

• For all Invite request that send to the ITSP modify the Host part of the To header
to ITSP.com
• Name: Change To header
• Manipulation Set ID: 4
• Message Type: Invite.Request
• Action Subject: Header.To.URL.Host
• Action Type: Modify
• Action Value: 'ITSP.com’

• From the SfB call to +xxxx555x101 the ITSP (MicroSIP) should ring
• Open syslog/wireshark
• Verify that the SBC performs the right routing decisions
• Verify that the SBC performs the required transcoding
• Verify that the ITSP’s requirements described in the next pages are accomplished
(see the expected results in the next pages)
54
Exercise 3: Expected Result

Tip: Look for a different way to achieve the same but without the need of configuring manipulations
55
Exercise 4: Change the Response Type

• For all 183 Session Progress Responses to Invites from ITSP modify the Response
to 180 Ringing
• Name: Change Response Type 183 to 180
• Manipulation Set ID: 4
• Message Type: Invite.Response.183
• Action Subject: Header.Request-URI.MethodType
• Action Type: Modify
• Action Value: '180’

• From the ITSP (MicroSIP) call to +xxxx555x005 the IP-PBX (SfB) should ring
• Open syslog/wireshark
• Verify that the SBC performs the right routing decisions
• Verify that the SBC performs the required transcoding
• Verify that the ITSP’s requirements described in the next pages are accomplished
(see the expected results in the next pages)
56
Exercise 4: Expected Result
Before manipulation After manipulation
ITSP IPPBX ITSP IPPBX
SBC SBC
(MicroSIP (SfB) (MicroSIP (SfB)

57
Exercise 5: Normalize SDP

• Normalize the SDP headers before send it to ITSP


• Name: Normalize SDP to ITSP
• Manipulation Set ID: 4
• Action Subject: Body.sdp
• Action Type: Normalize

• From the SfB call to +xxxx555x101 the ITSP (MicroSIP) should ring
• Open syslog/wireshark
• Verify that the SBC performs the right routing decisions
• Verify that the SBC performs the required transcoding
• Verify that the ITSP’s requirements described in the next pages are accomplished
(see the expected results in the next pages)

58
Exercise 5: Expected Result
IPPBX ITSP
SBC
(SfB) (MicroSIP)
Before normalization After normalization
v=0 v=0
o=- 1664296908 974699873 IN IP4 o=- 1505015767 279548746 IN IP4
10.15.13.1 10.15.13.1
s=session s=session
c=IN IP4 10.15.13.1 c=IN IP4 10.15.13.1
b=CT:1000 t=0 0
t=0 0 m=audio 8090 RTP/AVP 97 9 101 13
m=audio 8095 RTP/AVP 97 9 101 13 c=IN IP4 10.15.13.1
c=IN IP4 10.15.13.1 a=rtcp:8091
a=rtcp:8096 a=label:Audio
a=label:Audio a=sendrecv
a=sendrecv a=ptime:20
a=rtpmap:97 RED/8000 a=rtpmap:97 RED/8000
a=rtpmap:101 telephone-event/8000 a=rtpmap:9 G722/8000
a=fmtp:101 0-16 a=rtpmap:101 telephone-event/8000
a=rtpmap:13 CN/8000 a=fmtp:101 0-15
a=ptime:20 a=rtpmap:13 CN/8000
a=rtpmap:9 G722/8000

59
Exercise 6: Number Manipulations

• Calls from the ITSP to the IP-PBX are arrived with area code and number only
(0x555xxxx)
• Name: Add “+” and Country Code
• Destination IP Group: IPG-IPPBX
• Destination Username Pattern: 0
• Manipulated Item: Destination URI
• Remove From Left: 1
• Prefix to Add: +xxx

• From the ITSP (MicroSIP) call to 0x555x005 the IP-PBX (SfB) should ring
• Open Syslog:
• Verify that the SBC performs the right routing decisions
• Verify that the SBC performs the required transcoding
• Verify that the ITSP’s requirements described in the next pages are accomplished
(see the expected results in the next pages)
60
Exercise 6: Expected Result

Incoming call to
the SBC before
manipulations

Outgoing call from


the SBC after
manipulations

Tip: Can you achieve a similar result using message manipulations instead of number manipulations? How?
What will be the difference? 61
Hands-on Lab 5

SBC Survivability
Lab Environment

Mediant – SBC
10.15.1x.1/16
User PSTN
E1 Euro ISDN

IP-PBX
10.15.10.2/16 PSTN
Transport Type: TCP
Skype for IP
Listening Port: 5068
50 Media Session Legs Business
starts from 7000 ITSP2/PSTN
xxxx555x005 Fallback
Mediant SBC
10.15.10.5/16 Network
ITSP1
10.15.1x.20/16 MicroSIP
Transport Type: UDP
Listening Port: 5060
xxxx555x101 Linphone
50 Media Session
Legs starts from 8000
xxxx555x101
Public Provider Emulation
(not to be configured by the student)

63
The Goal of the Lab

• Configure all entities for proper routing calls from IP-PBX to ITSP1 and vice versa
• Add alternative route to ITSP2 in case of ITSP1 failure
• Add alternative route to PSTN in case of ITSP2 failure

64
SBC – Restore Defaults

65
SBC Basic Configuration

• Core Entities
• IP: 10.15.1x.1 /16 (don’t change, it is already pre-configured)
• MR1
• MR2
• DefaultSRD (don’t need to configure)
• SIP Interface 1: TCP port 5068
• SIP Interface 2: UDP port 5060
• Proxy Set 1 for IP-PBX (Skype for Business): 10.15.10.2:5068 - TCP
• Proxy Set 2 for ITSP1 (MicroSIP): 10.15.1x.20:5060 - UDP
• Proxy Set 3 for ITSP2-PSTN (Mediant SBC): 10.15.10.5:5060 - UDP
• IP Group 1 related to Proxy Set 1
• IP Group 2 related to Proxy Set 2
• IP Group 3 related to Proxy Set 3

66
SBC Trunk and Routing Tables Configuration
• Trunk E1: TDM and PSTN (Euro ISDN, User Side, Clock Recovered, E1 Framing MFF CRC4 Ext)
• Trunk Group for PSTN Fallback with Channel Cyclic Ascending assignment
• Routing Tables:
• Tel to IP:
1. * to IP-PBX IP Group (1)
• IP to Tel:
1. * to Trunk Group 1
• IP to IP:
1. IP-PBX IP Group (1) to ITSP1 IP Group (2) route row
2. IP-PBX IP Group (1) to ITSP2-PSTN IP Group (3) alternative route ignore inputs
3. IP-PBX IP Group (1) to Gateway alternative route ignore inputs
• Reasons for switching to alternative route: 4xx, 5xx and 6xx

67
Linphone Configuration

68
Linphone Configuration

69
Linphone Configuration – SIP Account Configuration

70
Linphone Configuration – SIP Account Configuration

<sip:xxxx555x101@10.15.10.5:5070>
<sip:10.15.10.5:5070;transport=tcp>

71
Linphone Configuration – Network Settings

10.15.1X.20 Your Group PC

72
Check Linphone Registration

sip:xxxx555x101@10.15.10.5:5070
Example for Group 1
73
Test calls

• Open Syslog and verify that the SBC performs the right routing decisions
• Test calls:
1. Routing to “ITSP 1” – Primary route
• From the IP-PBX (SfB) call to +xxxx555x101
• ITSP (MicroSIP) should ring
2. Routing to “ITSP 2” – First alternative
• Close the MicroSIP (in order to simulate it’s unavailability)
• From the IP-PBX (SfB) call to +xxxx555x101
• ITSP2-PSTN (Linphone) should ring
3. Routing to PSTN (Fallback) – Second alternative
• Change the Proxy Port to 5095
• From the IP-PBX (SfB) call to +xxxx555x101
• ITSP2-PSTN (Linphone) should ring

74
Routing to “ITSP 1” – Primary route

• From syslog verify the SIP Flow diagram


IPPBX ITSP1
SBC
(SfB) (MicroSIP)

75
Routing to “ITSP 2” – 1st Alternative

• To emulate a problem on the ITSP, close the MicroSIP application.


• Make the call again and verify IPPBX ITSP-2
SBC
call re-routing as below: (SfB) Mediant

76
Routing to “PSTN” (fallback) – 2nd Alternative (3)

Inside the E-SBC Inside the ITSP2/PSTN


ITSP2/PSTN ITSP2/PSTN
IPPBX PSTN E1/T1 PSTN SBC Phone
SBC Trunk GW (Linphone)
(SfB) Trunk Cable

77
MicroSIP softphone Configuration
(For reference only)

78
MicroSIP Configuration

79
MicroSIP Account Configuration

Userx

10.15.1x.1:5060

xxxx555x101

TR.local

10.15.1x.20

80
MicroSIP Settings Configuration

81
MicroSIP Settings Configuration for Transcoding

82

You might also like