sangoma vega gateway training presentation

CONNECT WITH SANGOMACONNECT WITH SANGOMA

Vega Gateways:

Training Support PresentationAykut [email protected] İletişim TeknolojileriDist. Of Turkey

Agenda• Introduction

• Portfolio of Gateways

• Use Cases

• Initial Access

• Practical 1 – First Time Access

• WebUI Concepts

• Vega Dial Plans

• Practical 2 – Quick Config

• Maintenance

• Using the CLI

• Debugging

• Further Practicals – Dial Plans & Debugging

• Further Support

© 2011 Sangoma Proprietary

2

A Few Facts About Sangoma

• An industry pioneer, founded in 1984

• Public company (TSX-V: STC)

• Staff of 60 in offices in• Canada: Toronto + Montreal

• USA: New Jersey

• UK: London

• Hong Kong

• Sells product worldwide via an extensive network of distribution partners/resellers

• Acquired VegaStream in 2011 for portfolio of VoIP gateways

• 12/14/2014


3

• Voice Telephony Boards• Analog/digital/hybrid, WAN, ADSL, etc

• Software Applications• NetBorder Express, Call Progress Analyzer…

• Gateways• NetBorder SIP to TDM

• SS7 to SIP

• Wireless Products

• Session Border Controllers

• Microsoft Lync

• Cloud based monitoring

• Fiber connectivity (STM1)

• Transcoding (boards/appliances)

Broad Line of Great Products

• 12/14/2014


4

Vibrant Ecosystem of Clients & Partners

Contact Center OEM Integration with major software suites

Carriers, Cloud, Data NtwksProven Infrastructure Technology

Open Source TelephonyReady to use drivers for Sangoma boards

Proprietary PBX and IVRPlug-in to major soft-PBX and IVRs

12/14/2014


5

Innovation and Interoperability

Indian Army

• 12/14/2014


6

http://www.snom.com/

http://www.snom.com/

http://www.bt.com/

http://www.bt.com/

CONNECT WITH SANGOMA

Recap Vega VoIP GatewaysVega Product Family

Vega Series: Telecom Appliances

• Vega 50• H.323/SIP• Up to 8 port BRI• Up 10 ports FXO/FXS combos

• Vega 5000• H.323/SIP• 24 or 50 FXS• 2 FXO failover to PSTN

• Vega 100G, 200G• 2 E1 ports• 30 or 60 SIP channels

• Vega 400G• 4 T1/E1 (PRI, CAS, R2)• 30, 60, 90 0r 120 channels• Upgradeable via licenses• Power fail hardware, port bypass

© 2014 Sangoma Technologies 8

Vega Gateway Call Limits

Product Model # IF & Channels SIP Calls

Vega 50 4 FXS (+ 2 FXO) 4 Analogue 4

8 FXS (+ 2 FXO) 8 Analogue 8

4 FXO 4 Analogue 4

4 FXO 8 Analogue 8

2 BRI 2 (4) Digital 4

4 BRI 4 (8) Digital 8

Vega 5000 24 Port 24 Analogue 24

50 Port 50 Analogue 50

Vega 100G/200G 100G 2 (48 or 60) T1 / E1 30

200G 2 (48 or 60) T1 / E1 60

Vega 400G Depends on License 4 (120) Depends on License30, 60, 90 & 120


Features – All Gateways

• VoIP Protocols• SIP all models• H323 (Vega 50 and

Vega 5000)• TLS/SRTP for security via

license on Vega 50 and 5000

• Dual LAN + Console Port

• Management• Web GUI• CLI• RADIUS• SNMP• Syslog• Billing logs

• Powerful Routing Capabilities

• Remote Firmware Upgrade

• Vocoding• G.711, G.729, G.723, GSM(1)

• G.168 Hardware Echo Cancellation

• T.38 Fax and Fax Relay

• Enhanced Network Proxy


Fallback Ports in Case of Failure Vega 400G

To/FromTelco

E1/T1 cables

Main Unit

Failover Unit

E1/T1 cables


Fallback Ports in Case of Failure

To/FromTelco

E1/T1 cables

Main Unit

Failover Unit

E1/T1 cablesInternal relay trips to connect to failover ports


Fallback Ports Alternative Use

• Vega gateway inserted between PBX and PSTN

• Completely transparent

• Groom calls to SIP over time

• Resilient in case of failure or maintenance

SIP

ISDNISDN

ITSP


Fallback Ports Alternative Use

T1/E1 cables

Internal relays trip to connect PBX to Telco

To/FromTelco

To/FromPBX

SIP

ISDNISDN

ITSP


Vega 100G & 200G

• Fixed Call Density– No upgrades

• Fixed E1/T1 Pinout– Port 1: TE (Default)

– Port 2: NT (Default)

• Ports are still configurable as NT or TE in config– Need crossover cable


SIP Trunking

PBX, TDMEndpoints

Previous connection to PSTN:Analog/BRI/PRI

ITSPSIP /VoIP


SIP Trunking with Resilience

PBX, TDMEndpoints

AnalogBRIPRI

ITSPSIP /VoIP

PSTN

On SIP / www / WAN failure Vega reroutes all calls via PSTN


Analog Connectivity for IP PBXs

IPBX• Snom• 3CX• Elastix• Asterisk• Cisco• Avaya• Etc.

LAN

SIP/VoIP

PSTN

AnalogBRIPRI

SIP/VoIP

Analog endpoints

FXS FXS FXS


What’s in the box?• Vega 400G:

• Rack mount kit & Quick start guide & License agreement• Power cord (country specific) • 1 x Console cable• 2 x Ethernet cable (2m)• 4 x E1T1 cables (2m)

• Vega 100G & 200G• Rack mount kit & Quick start guide & License agreement• PSU & Power cord (country specific)• 2 x Ethernet cable (2m)• 2 x E1T1 cables (2m)

• Vega 50• Rack mount kit & Quick start guide & License agreement• PSU & Power cord (country specific) • 2 x Ethernet cable (2m)

• 12/14/2014© 2011 Sangoma Proprietary 19


First Time Access

• BEFORE CONFIGURATION CAN START

IP Address Required

• Three methods to access:• Use serial port to view or set IP address

• Use APIPA address if no DHCP and no serial cable

• Via IP address if DHCP enabled and known IP address

• DHCP assigned IP address (Vega Default)

• APIPA compliant connection (Automatic Private IP Address)• 169.254.xx.yy

• MAC is 00 50 58 WW XX YY

• Statically assigned IP address

Vega Initial Access


21

• Connect to the Vega via serial interface:(Using hyperterminal, Qmodem, Putty or similar)

• Speed 115200

• Data Bits 8

• Parity None

• Stop Bits 1

• Flow Control None

• Power up Vega then press ENTER to get username prompt

Serial Port Connection


22

1.Calculate Vega APIPA Address• Take last 2 pairs of digits of LAN 1

• Convert from HEX to decimal

• Use as last two parts of IP Address

• Example: 005058001F20• Hex 1F = Dec 31, Hex 20 = Dec 32

• IP address = 169.254 .31.32

2. Set IP address of PC to same range

3. Connect to Vega using webUI or telnet

4. Configure correct IP address

5. Change PC back to correct IP range (DHCP or static)

6. Connect to Vega on new, correct IP address

APIPA Address


23

View The DHCP Server IP Address...

12/14/2014


24

• At the prompts enter the default:

• Username: admin

• Password: admin

• At the admin prompt enter:

• show banner

... Or Set Static IP Address

12/14/2014


25

• Set basic LAN parameters:

• Allocate IP address or DHCP

• Subnet address

• Gateway address

• Commands:

• set lan.if.1.use_dhcp=0

• set lan.if.1.ip=aaa.bbb.ccc.ddd

• set lan.if.1.subnet=eee.fff.ggg.hhh

• set lan.gateway.ip=iii.jjj.kkk.lll

• set lan.gateway.dhcp_ip=0

• save

• reboot system

The Banner

• 12/14/2014


26

------------------------------------------------------------

---

-- Version: 10.02.08.8 VEGA400 Runtime System

-- Serial #: 005058000630

-- (c) 1998-2012 Sangoma Technologies Inc. All rights

reserved.

------------------------------------------------------------

---

Host name:ITS_v400_London LAN 1 IP:172.19.1.211

LAN 2 IP:0.0.0.0

System licensed for 120 TDM<-->SIP calls

WARNING: Password is set to default value

Username:

Gateway Can Now Be Accessed

12/14/2014


27

• Web browse to the IP address of the Vega

• Enter default username and password (admin / admin)

Vega WebUI



Quick Config

Quick Config

• Vega config individual settings

• Quick Config is a Template

• Template settings appliedon “Submit”

• Submitted One Way • Change in Expert Config ≠

Quick Config


Default Configuration

• All gateways configured for factory defaults will be set to the following:

• Username: admin

• Password: admin

• LAN IP address will be assigned by DHCP or

• APIPA assigned if no response is received from a DHCP server

• Usernames and passwords are common to both console and WebUI


Configuration• Desk to desk communication

DESK 1 IPPBX address 172.16.16.172




DESK 1 connect to Desk 3

DESK 2 connect to Desk 4

Users IP PBX 1 >> 1000-1010

9XXXX > SIP trunk to Vega 100G #1

8XXXX> SIP trunk to Vega 100G #3

Users IP PBX 2 >> 5000-5010

9XXXX > SIP trunk to Vega 100G #2

8XXXX> SIP trunk to Vega 100G #4


Config Example – E1 or T1

• What config is needed?• For Traditional Telephony Interface

• For SIP Interface

• Trunking Based Call Routing

• E1 or T1 TDM Interface• Emulation Mode, Clocking, Protocol

• SIP Interface - SIP trunk to ITSP or SIP PBX• IP address of SIP server

• SIP domain config

• ITSP SIP Registration? (credentials)


Config Example – Analog FXS

• What config is needed?• For Traditional Telephony Interface

• For SIP Interface

• Analog FXS Extensions• Country setting for analog settings

• Analog to FXS extension

• SIP Interface – Hosted IP or SIP PBX• IP address of SIP server

• SIP domain config

• Extension Credentials


Quick Config

• Basic Config• Country Setting

• LAN and IP address settings

• Password

• VoIP Config• SIP Registration

• SIP Server

• SIP Credentials

• Traditional Telephony Config• Trunk Routing “ .* “

• Telephony Interface settings

• Live Screen Example – E1 T1 Gateway



Expert Config

View the DHCP Server IP Address

• At the prompts enter the default:

• Username: admin

• Password: admin

• At the admin prompt enter:

• show banner


Submit and Save

• Each section of configuration has a submit button

• This must be pressed on completion of each section

• Changes will be lost if they are not submitted


Apply or Reboot

• After submitting and saving Apply Changes or Reboot System

• To activate changes, click Apply or Reboot System

• There is a third (unusual) case where changes are hot and are active instantly

• Some Media changes for instance


or


Dial Plan Config

Vega Initial Access

• IP Address Required to Start Configuration• DHCP assigned IP address (Vega Default)

• APIPA compliant connection (Automatic Private IP Address)• 169.254.xx.yy

• MAC is 00 50 58 WW XX YY

• Statically assigned IP address

• Three methods to access:• Via IP address if DHCP enabled and known IP address

• Use serial port to view or set IP address

• Use APIPA address if no DHCP and no serial cable


APIPA Address

• Calculate Vega APIPA Address• Take last 2 pairs of digits of LAN 1• Convert from HEX to decimal• Use as last two parts of IP Address• Example: 005058001F20

• Hex 1F = Dec 31, Hex 20 = Dec 32• IP address = 169.254 .31.32

• Set IP address of PC to same range

• Connect to Vega using webUI or telnet

• Configure correct IP address

• Change PC back to correct IP range (DHCP or static)

• Connect to Vega on new, correct IP address


Dial Plan Concepts: Call Parties

• Call Credentials• Called Party Number = 4001

• Calling Party Number = 3001

• Calling Party Name = Alice


Alice Bob

Alice calls Bob

Alice’s Number: 3001

Bob’s Number: 4001

Dial Plan Concepts: Interfaces

• Interface Details• Calling Interface = FXS 1

• Called Interface = SIP


Alice Bob

Alice calls Bob

Alice TDM User Bob SIP User

FXS SIP

Dial Plan Concepts: Routing


Alice Bob

Alice calls Bob

Incoming Call:Interface: FXS 1

Called Party Num: 4001Calling Party Num: 3001Calling Party Name: Alice

SourceLooks for a match based on Incoming call credentials

DestinationRoutes call to called party

Outgoing Call:Interface: SIP


Vega Interface Syntax

• In Vega dial plans, interfaces are referred to using the “IF:” token


Alice Bob

Alice calls Bob

IF:0101

IF:9901

Alice TDM User Bob SIP User

FXS 1 SIP

SourceIF:0101

DestinationIF:9901

4001

Vega Call Party Syntax

• In Vega dial plans, call parties use the following tokens:• Called Party Number: TEL

• Calling Party Number: TELC

• Calling Party Name: DISP


IF:0101

IF:9901

3001Alice TDM User

4001Bob SIP User

FXS 1 SIP

SourceIF:0101,TEL:4001,TELC:3001,DISP:Alice

DestinationIF:9901,TEL:4001,TELC:3001,DISP:Alice

Multiple Routes

• Every possible route through the Vega must be considered


Bob

Carol calls Bob

IF:0102

IF:9901

FXS 2 SIP

Carol


Called Party Num: 4001Calling Party Num: 3002Calling Party Name: Carol

SourceIF:0101,TEL:4001,TELC:3001,DISP:Alice

3002

Does not match as:Interface does not matchCalling Party Num does not matchCalling Party Name does not match

4001

Multiple Routes: Solution #1

• Add a new route for Carol


Bob

Carol calls Bob

IF:0102

IF:9901

FXS SIP

Carol


Called Party Num: 4001Calling Party Num: 3002Calling Party Name: Carol

SourceIF:0102,TEL:4001,TELC:3002,DISP:Carol

3002

DestinationIF:9901,TEL:4001,TELC:3002,DISP:Carol

4001

Multiple Routes: Solution #2

• Make the source expression more general – wildcards

• Not all tokens have to be used in the source expression


Bob

Carol calls Bob

IF:0102

IF:9901

FXS SIP

Carol

Incoming Call:Interface: FXS


SourceIF:010.,TEL:3002

3003

DestinationIF:9901,TEL:3002

Use the “.” as a wildcard.This will now match calls from Carol and Alice.The calling num and name will be passed through as well.

4001

Routes are NOT Symmetric

• Every possible route through the Vega must be considered

• A new route is required from SIP to FXS


Bob

Bob calls Alice

IF:0101

IF:9901

FXS SIP

Incoming Call:Interface: SIP

Called Party Num: 3001Calling Party Num: 4001Calling Party Name: Bob

3001

Alice

4001

SourceIF:010.,TEL:3002

Does not match as:Interface does not matchCalled party does not match

Routes are NOT Symmetric: Solution

• Every possible route through the Vega gateway must be considered

• A new route is required from SIP to FXS


Bob

Bob calls Alice

IF:0101

IF:9901

FXS SIP

Incoming Call:Interface: SIP

Called Party Num: 3001Calling Party Num: 4001Calling Party Name: Bob

SourceIF:9901,TEL:3001

3001

Alice


4001

Multi Routes: Problem

• Alice wants to call Bob or Dave

• Two routes or dial plans would be required


BobAlice wants to

call Bob or Dave

IF:9901

SIP

3001

Alice

4001


IF:0101

FXS

Dave

4002SourceIF:9901,TEL:4002

Multi Routes: Solution

• Store the dialed number


Bob

IF:9901

SIP

3001

Alice

4001

SourceIF:0101,TEL:<400.>

IF:0101

FXS

Dave

4002DestinationIF:9901,TEL:<1>

The <> operator stores the dialed number.The . is a wildcard for a single digit.

Alice wants to call Bob or Dave

Dial Plan Intro Summary


BobEveryone wants

to talk

IF:9901

SIP

3001

Alice

4001

SourceIF:010.,TEL:<400.>

IF:0101

FXS

Dave

4002DestinationIF:9901,TEL:<1>

Carol

3002





Three dial plan entries are required.

Trunks vs. Endpoints• Multiple calls can be routed via a trunk

• The other end deals with how to distribute calls

• An endpoint is an entity that must be addressed individually

Examples:


SIPIP-PBX

The IP-PBX decides how to route calls

SIPTDM

SIPTDMVega must

route call to each endpoint

individually

One Dial Plan Required

Multiple Dial Plans Required

Interfaces Reference List


Analog Interfaces

FXS Port 1 IF:0101

FXS Port 2 IF:0102

…

FXS Port 50 IF:0150

FXO Port 1 IF:0201

FXO Port 2 IF:0202

…

FXO Port 8 IF:0208

Digital Interfaces

E1T1 Port 1 IF:0401

E1T1 Port 2 IF:0402

…

E1T1Port 8 IF:0408

BRI Port 1 IF:0301

BRI Port 2 IF:0302

…

BRI Port 8 IF:0308

VoIP Interfaces

SIP Int 1 IF:9901

H.323 Int 1 IF:0501

Token Reference List

Source Tokens

IF Source Interface

TEL Called Number

TELC Calling Number

DISP Calling Display name

TAC Calling network address

Tokens for Destination

IF Destination Interface

TEL Called Number

TELC Calling Number

TA Called network address

TAC Calling network address

DISP Calling Display name

QOS QOS profile to use


Advanced Token Reference ListSource TokensNAME Called Name (H323 only)

CHAN Source Channel (Private Wire Only)

Destination TokensNAME Called name (H323 Only)

CHANDestination Channel (Private Wire Only)

QOS QOS profile to use

CAPDESC Codec capability set to use

TYPE/TYPECType of Called/Calling party, one of: supplied, unknown, international, national, network_specific, subscriber, abbreviated

PLAN/PLANCNumbering plan of Called/Calling party, one of: supplied, private, national, unknown, isdn_telephony, data, telex

SCRNCScreening for Calling party, one of: supplied, not_screened, passed, failed, network

PRESCPresentation for Calling party, one of: supplied, allowed, restricted, not_available


Source Regular Expressions• Regular expressions for source:

. A single character

< > Capture the sequence in < > and store as < n >

[abc] A single character within the parenthesis

[x-y] A single character in the range x-y

[^abc] A single character except those within the parenthesis

* The preceding character/expression repeated zero or more times

+ The preceding character/expression repeated one or more times

? The preceding character/expression repeated zero or one times

\ Literalize the following character (e.g. \* = * and not a repeat of the previous character)


Destination Regular Expressions• Regular expressions for destination:

~ FXO only: pause (e.g. waiting for second dial tone)

<n> Insert the nth captured sequence from the source expression

\ Literalize the following character


Dial Plan Rationalization

3001

Calling 4001

E1 Int 1

Incoming Call Source

IF:0401,TEL:4001

Destination

IF:9901,TEL:4001

IF:0401,TEL:.* IF:9901,TEL:4001

IF:0401,TEL:<.*> IF:9901,TEL:<1>

IF:04..,TEL:<.*> IF:9901,TEL:<1>

Allow any dialed number to pass

Remember the dialed number

Allow call from ANY E1 to pass


Source Matching


2001

Calling 5001

FXS 1


1. IF:0101,TEL:5001

2. IF:0101,TEL:5…

3. IF:01..,TEL:(.*)

4. IF:….,TEL:….

5. IF:01..,TEL:.

Which plans match?

Source Matching: Answer

2001

Calling 5001

FXS 1


1. IF:0101,TEL:5001

2. IF:0101,TEL:5…

3. IF:01..,TEL:(.*)

4. IF:….,TEL:….

5. IF:01..,TEL:.

All of them!

Number 5 matches because as soon as the first digit is dialed the call will route –

care required!


Vega Best Match

2001

Calling 5001

FXS 1


1. IF:0101,TEL:5001

2. IF:0101,TEL:5…

3. IF:01..,TEL:(.*)

4. IF:….,TEL:….

5. IF:01..,TEL:.

If they all match, which is used?

Number 5 matches because as soon as the first digit is dialed the call will route –

care required!


Vega Best Match: Answer

2001

Calling 5001

FXS 1


1. IF:0101,TEL:5001

2. IF:0101,TEL:5…

3. IF:01..,TEL:(.*)

4. IF:….,TEL:….

5. IF:01..,TEL:.

If they all match, which is used?

Number 1 will be used as it is the most

specific match


Overriding Best Match• Priorities

e.g.:

IF:01..,TEL:<1234>

IF:01..,TEL:<123.>

IF:01..,TEL:<.*>

Cost 1 - highest priority (first match)

Cost 2

…

Cost 9 - low priority (first match)

Cost 0 - lowest priority (longest match) default


Dial Plans Summary

• Plans and Profiles• Up to 200 plans

• Up to 25 profiles

• Max 50 plans per profile

• Profiles enabled/disabled

• General format:• Source = IF:iiii,further conditions

• Destination = IF:jjjj,further details


Viewing and Testing Dial Plans• Web browser Management page and CLI:

• Show plan

• Lists all plans

• Web browser Management page and CLI:• Show paths

• Shows the plans in the priority order

• Using the CLI:• Try <source address tokens>

• Test out the plans


Dial Plans…Rules1. Use unique numbers for TEL: throughout

2. Configure dial plans for each individual Vega

3. Look at paths for every telephone numberto every other telephone number.Remember:

• telephone ↔ telephone

• telephone ↔ LAN

• LAN ↔ telephone

4. After all rules are available,use wild cards to simplify(to reduce the number ofrules)

99019901

0402

01010102

SIP Soft-phone

192.168.1.106

201 202 401 402

Vega 400

192.168.1.102

501

Vega 50

192.168.1.104


SIP Routing• Calls can be routed to the correct SIP address in two ways:

• Use SIP Proxy – defined on SIP page

• Use TA token in dial plan (unusual)• TA token overrules SIP Proxy definition

• SIP split into up to 5 profiles

• Use different profiles if domain (i.e. ITSP) is different

• Multiple proxy/registrars can be defined per profile

• Separate registrar and proxy

• Refer to SIP profile as 9901, 9902, 9903…in dial plans



Administration and Logging

Vega Firmware

• Stored in FLASH memory

• Vega 100G, 200G, 400G & 5000 have two firmware partitions

• Upgrades:• New firmware loaded to inactive partition

• Partitions switch on reboot

• On initial boot choose partition to run


Firmware Upgrades – webUI• webUI recommended for upgrades

• Available on “System” page

• All steps autonomous


Firmware Upgrades – CLI• Requirements:

• Telnet or RS232 session to the Vega

• (t)ftp server to save/load information (e.g. Pumpkin)

• Procedure• load the firmware (.abs file) to the (t)ftp server

• Stop calls arriving• block calls … wait for message

• Save configuration• put (t)ftp:old_cfg.txt … to (t)ftp server

• Load new firmware• Upgrade

• download enable

• download firmware <filename.abs>

• reboot system

• Vega restarts and runs the new firmware

• Wait for the reboot to complete• factory reset

• get (t)ftp:old_cfg.txt

• save

• reboot system

• Once the Vega has re-booted the upgrade is complete


Examining Vega Status

• “show” command can also be used to examine the status of Vega entities:• “show ports” shows the status of all

interfaces on the Vega

• “show version” shows the loaded firmware

• “show support” dumps the entire config of the Vega

• “show log” dumps the log buffer

• “show dsp” indicates the status of all the DSP resources


admin >show version

--[ System Status ] --

[Overview]:

Hardware Platform : Vega 400

Serial Number : 005058000630

FPGA Version : 2

Boot Loader : Version 3.00 (supports firmware 8.02 upwards)

[ACTIVE]:

Binary File Name : VEGA400_R088S020

Release Date : Nov 23 2012 14:06:21

Versioning Info : SIP Firmware Rev 08.08 for H/W Type 10

Boot Requirements : Boot Loader 02.00

[IMAGE1]: *ACTIVE NEXT BOOT*

Physical Data : v-file FLASH:IMAGE1





[IMAGE2]:

Physical Data : v-file FLASH:IMAGE2





Show Version

Protocol

H – H.323

S – SIP

Firmware version

- Release number

Hardware Platform Sub version level

- sub version

Serial Number


Show Calls

Attempting connection

Disconnecting

Connected

Total calls in progress

Active Interfaces


SIP Specific Commands

• “sip show reg” dumps the registration status of each SIP reg_user

• “sip reg 1” forces sip reg_user 1 to send a new SIP REGISTER request

• “sip reg all” forces all enabled sip reg users to send a new SIP REGISTER request


admin >sip show reg

SIP REG

----------------------------------------------------------------

---------------

SIP Profile 1 - registration expiry = 600s

----------------------------------------------------------------

---------------

SIP REG USER 1

--- address - [email protected]

--- auth user - auth user disabled

--- contact - <sip:[email protected]>

--- state - unregistered (user 1)

--- TTL - 0 seconds

SIP REG USER 2

--- address - [email protected]

--- auth user -

--- contact - <sip:[email protected]>

--- state - unregistered (user 2)

--- TTL - 0 seconds

Syslog

• Standard logging protocol

• Delivery to external computer:

• Logging

• Billing

• Console and web browser activity

• Debug

• QoS

>Up to 5 Syslog sessions

> Each session supports1 or more data streams


SNMP• Mibs

• Mib 2• Vega specific enterprise mib for:

• Network statistics

• Call statistics• Mib definition file on

www.VegaAssist.com

• Enterprise Specific Traps• Autoexec status

• Fallback relay status

• QoS exceptions

• Fan fail/over temperature etc. and recovery

• Sip registration – unregistered, registered, failed

• Lan – link up / down

• Documentation• see SNMP Management

document on wiki.sangoma.com


http://wiki.sangoma.com/

Help• Web browser interface

• GUI

• Command line interface

• help

• help advanced

• help <command>

• set <parameter>=?


Show Support

• SHOW LOG

• SHOW BILL

• SHOW VERSION

• SHOW BANNER

• SHOW STATS

• SHOW TRACE

• SHOW CHECKSUM

• SHOW CALLS

• SHOW PORTS

• SHOW HIGHWAY

• SHOW HOSTS

• SHOW TIME

• SHOW ARP

> SHOW PLAN

> SHOW PATHS

> SHOW POST PATHS

> SHOW GROUPS

> SHOW DSP

> SHOW THIRD PARTY

> SHOW

> STATUS SOCKETS

> STATUS BUFFERS

> SHOW _advanced

> SCHG changes

> ESUP

> SEM

> DUMP LOG



Troubleshooting

Debugging Problems• Main tools:

• log display on

• sip monitor on

• show support

• www.VegaAssist.com

• Debug levels• “debug list” to see active debug

“EF” always enabled

• “debug enable <entity> <level>

Debug examples:debug enable _isdn 89 See all ISDN messagesdebug enable router rs View router (dial plan) infodebug enable _sip t SIP message composition


http://www.vegaassist.com/

Log Display• Dump log buffer - show log

EVENT LOG: enable=ON display=A

LOG: 01/01/1999 00:00:04 DSP (A)Rb3C3c 60 g7231 voice channels (60 licensed)

LOG: 01/01/1999 00:00:06 LAN (I)R00C00 LAN running

LOG: 01/01/1999 00:00:06 POTS (I)R00C00 POTS running

LOG: 01/01/1999 00:00:06 OOB_DTMF (I)R00C00 OOB_DTMF running

LOG: 01/01/1999 00:00:06 LCD (I)R00C00 LCD running

LOG: 01/01/1999 00:00:06 DSP (I)R00C00 DSP running

LOG: 01/01/1999 00:00:08 H323 (I)R00C00 H323 running

LOG: 01/01/1999 00:00:08 LOGGER (I)R00C00 LOGGER running

LOG: 01/01/1999 00:00:08 LAN (A)Rb4C00 LAN link-up (100Mbps)

LOG: 01/01/1999 00:00:09 ISDN (I)R00C00 ISDN running

LOG: 01/01/1999 00:00:09 ROUTER (I)R00C00 ROUTER running

LOG: 01/01/1999 00:00:09 ROUTER (A)RabC00 system ready for use

LOG: 01/01/1999 00:01:56 TELNET (I)R01C01 incoming

srce=200.100.50.70 port 1070

LOG: 01/01/1999 00:14:40 TELNET (I)R01C01 disconnected

LOG: 01/01/1999 14:09:35 LAN (A)Rb5C00 LAN link-down

LOG: 01/01/1999 14:14:03 LAN (A)Rb4C00 LAN link-up (100Mbps)

LOG: 01/01/1999 14:16:24 TELNET (I)R01C01 incoming

srce=200.100.50.70 port 1056

Vega400 >


• Realtime log monitoring – log display on

LOG: 15/06/2005 16:55:03.125 ISDN (I)R01C21 incoming

call ref=[f10002dd] srce=TEL:206 [0]

LOG: 15/06/2005 16:55:05.122 ROUTER (I)R0bC00 FINDROUTE profile:1(ISDN_to_SIP) plan:2

call ref=[f10002dd] <-- ISDN [2,1] dest=TEL:501

--> SIP [1,1] dest=TEL:501,TA:172.19.1.76

LOG: 15/06/2005 16:55:13.967 SIP (I)R03C12 connect g711Ulaw64k

call ref=[f10002dd]

LOG: 15/06/2005 16:55:16.925 SIP (I)R03C12 connect T38

call ref=[f10002dd]

LOG: 15/06/2005 16:55:46.687 SIP (I)R04C12 disconnect(disc ind) 16

call ref=[f10002dd]

LOG: 15/06/2005 16:55:46.695 ISDN (I)R04C21 send disconnect 16

call ref=[f10002dd]

Log Display


SIP Monitor Onadmin >SIP m:0326726 9540 00029<-- RX --- From 136.170.225.225:5060

INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 136.170.225.225:5060

From: port1vega1 <sip:[email protected]:5060>

To: <sip:[email protected]:5060>

Call-ID: [email protected]

CSeq: 1 INVITE

Contact: <sip:[email protected]:5060;maddr=136.170.225.225>

Allow: INVITE,ACK,BYE,CANCEL,INFO,NOTIFY,OPTIONS

Accept-Language:en

Content-Type: application/sdp

Content-Length: 134

v=0

o=Vega50 5 1 IN IP4 136.170.225.225

s=Sip Call

c=IN IP4 136.170.225.225

t=0 0

m=audio 10006 RTP/AVP 0

a=rtpmap:0 PCMU/8000

SIP m:0326762 0036 00030--- TX --> To 136.170.225.225:5060

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 136.170.225.225:5060

From: port1vega1 <sip:[email protected]:5060>

To: <sip:[email protected]:5060>;tag=0010-0002-00D39ED8

Call-ID: [email protected]

CSeq: 1 INVITE

Contact: <sip:[email protected]:5060;maddr=136.170.225.229>

Content-Length: 0


Show Ports• Physical Ports

• Basic Port configuration • Port & Channel Status

• Line Settings

• Port Link Statistics • High light most significant

• System Fan status

• System Temperature status

• User Connections active


Boot Menu• Uses e.g.

• Lost your password

• Swap Boot Partition – revert to previous version of firmware

• Ready system to be redeployed – Remove all sensitive data

• 9600 baud

• Press enter at power on

• At message prompt enter “y” to enter boot menu

• For further details see << boot menu document>>

Note: Clearing the configuration using the boot menu clears the license key.

Ensure that you have the license key value to re-enter in order to restore Vega capabilities.


Boot Menu – Swap Partition • Swap Partition

• Swap Boot Partition – revert to previous version of firmware

• 9600 baud


• At prompt enter “y” to enter boot menu

• Partition swap = option 6• Processed started at key press





Boot Menu – Config Clear• Config Clear – Factory level reset

• Lost your password

• Ready system to be redeployed - Remove all sensitive data

• 9600 baud


• At prompt enter “y” to enter boot menu

• Config Clear = Option 3

• Prompts for user confirmation






Sangoma Documentation

Documentation

• http://wiki.sangoma.com• Frequently updated wiki

• HTML/pdf based documentation

• Includes:• Admin guide

• Step-by-step configuration

• Technical documents

• Firmware

• Vega tools

• How to guides


http://wiki.sangoma.com/

Contacting Sangoma Support

• Preferred method of raising support requests is via online portal at http://support.sangoma.com


http://support.sangoma.com/

Hardware Maintenance

• No ongoing maintenance required• Only moving part is the fan in Vega 100G, 200G & 5000

• No user serviceable parts• Safety/Warranty• Return to base repair only

• Environmental conditions• Keep units in an air conditioned room or office environment

• Basic warranty • 12 months for hardware & software• Return to base repair• 30 days advance replacement

• Extended support plans and warranties available
