2A STRA

  How to configure MVB SIP trunk towards PBX (MX-ONE) and diagnostics commands. Please download slides -> pdf Thank you.

How to configure multi-level auto-attendant on MiVoice Bussines PBX, in case if you have several incoming called numbers with different IVR menus. Please download slides ->  pdf Thank you.

How connect to office separated lab network and register SIP-phones from remote location using OpenVPN. Create keys: # OpenVPN / Easy-RSA 3.0 mkdir easy-rsa cp /usr/share/easy-rsa/* ~/easy-rsa/ cd /etc/openvpn/easy-rsa/ ./easyrsa init-pki # CA key ./easyrsa build-ca # Server keys ./easyrsa build-server-full Demo ./easyrsa gen-dh openvpn --genkey --secret ta.key # Client key ./easyrsa build-client-full student1 nopass Server config: persist-key persist-tun ca /etc/openvpn/ssl/ca.crt cert /etc/openvpn/ssl/Demo.crt ;comp-lzo adaptive dev tun dh /etc/openvpn/ssl/dh.pem ifconfig-pool-persist server-ipp.txt 0 keepalive 10 120 key /etc/openvpn/ssl/Demo.key tls-auth /etc/openvpn/ssl/ta.key 0 cipher AES-256-CBC auth SHA512 tls-version-min 1.2 tls-cipher TLS-DHE-RSA-WITH-AES-256-GCM-SHA384 log /var/log/openvpn/server.log port 1194 proto tcp server 10.7.0.0 255.255.255.0 verb 3 crl-verify /etc/openvpn/ssl/crl.pem push "route 10.130.0.0 255.255.255.0" client-config-dir ccd route 192.168....

In this video I will explain and demonstrate how to restore MX-ONE from backup files including Provisioning Manager. Commands to make backup: data_backup config_mirror -s su - mp_config backup_database Then you need to copy 'config mirror', 'safety backup' and 'mpManagerDump' files to local PC. Upload these backup files to new system and run `net_setup` command for initial setup. Continue on LIM1 with `mxone_maintenance` to repair failed server. If you need to restore Provisioning Manages as well, install it first on new server and run `mp_config` to restore database from backup.   Please download slides -> pdf Thank you.

MX-ONE initial setup, packages installation and SIP extensions / SIP trunk configuration takes about 18 minutes on VMware VM (4vCPU, 16GB RAM). In a video below I will go through this process with some additional explanations.   Configuration: # SIP extensions number_initiate -number 1000..1010 -numbertype ex number_print extension_profile -i --csp 0 --ext-traf 1103151515 --ext-serv 200000110001000000000000100200 --ext-cdiv 110000001000000 --ext-roc 000001  --ext-npres 0001000 --csp-name "CSP0" extension_profile -p extension -i -d 1000 --csp 0 -l 1 --max-terminals 4 --third-party-client yes extension -i -d 1001 --csp 0 -l 1 --max-terminals 4 --third-party-client yes extension -p ip_extension -i -d 1000 --protocol sip ip_extension -i -d 1001 --protocol sip ip_extension_info media_gateway_config -i -m 1a --mgw-type MS --cidr 10.130.10.10/24 --default-gateway 10.130.10.1 media_gateway_interface -i --media-gateway 1a --cidr 10.130.10.10/24 --default-gateway 10.130.10.1 # SIP-trun...

In this video I will configure SIP-trunk through Service Node Manager web interface and the same over MX-ONE Linux console. After that start test calls and troubleshooting tools. Configure SIP-trunk from console: number_initiate -number 7 -numbertype ed number_print sip_route -set -route 7 -profile Default -uristring0 "sip:?@10.130.0.3" -accept REMOTE_IP -match 10.130.0.3 mdsh MDSH> rocai:rou=7,sel=7110000000000010,serv=3110000001,traf=03151515,sig=1111110000A0,trm=4; MDSH> rodai:rou=7,type=tl66,varc=00000000,vari=00000000,varo=00000000; MDSH> roeqi:rou=7,tru=1-1&&1-10; MDSH> roddi:dest=7,rou=7,srt=2; Check configuration: sip_route -print -route 7 -short MDSH> rocap:rou=all; MDSH> rodap:rou=all; MDSH> roddp:dest=all; Diagnostics commands: call_trace -d 1000 resource_status --externals --route-number 7 --trunk-number all --list --traffic-status sudo tcpdump -i eth0 udp port 5060 and host 10.130.0.3 sudo tcpdump -i any -s 0 udp port 5060 -w sip.pcap...