SMG-1016M 2016 3016 User Manual 3.20.5

Translated from Russian to English - www.onlinedoctranslator.
com
Digital Gateways
SMG-1016M, SMG-2016, SMG-3016

User manual Software version
3.20.5
Digital GatewaysSMG-1016M, SMG-2016, SMG-3016
Content
1 History of changes ................................................................ ................................................. ..........eleven
2 Conventions and target audience ............................................................... .................23

2.1 Conventions .................................................................. ................................................. .................23
2.2 Hints, notes and warnings .................................................................. ....................................24
2.3 The target audience................................................ ................................................. .........................24
3 Description of products .................................................. ................................................. ............25

3.1 Introduction ................................................. ................................................. ................................................25
3.2 Product description .................................................. ................................................. .........................25

3.2.1 Purpose ................................................. ................................................. ................................................. ..25
3.2.2 Typical application schemes ............................................................... ................................................. .........................27
3.2.2.1 Conjugation of signaling and media streamsTDM and VoIP networks ............................................... ................... 27
3.2.2.2 MiniIP PBX ............................................... ................................................. ................................................. ... 28

3.2.2.3 Subscriber removal according to the protocolV5.2 ............................................... ................................................. ........ thirty
3.2.3 Structure and principle of operation of the product .............................................. ................................................. ...........31
3.2.3.1 StructureSMG-1016M ............................................... ................................................. ................................... 31

3.2.3.2 StructureSMG-2016............................................... ................................................. ............................................... 32
3.2.3.3 StructureSMG-3016............................................... ................................................. ............................................... 33
3.2.3.4 Principle of operationSMG ................................................. ................................................. ................................... 34
3.2.4 Main technical parameters ............................................... ................................................. ..............35

3.2.5 Design .................................................................................. ................................................. .........................41
3.2.5.1 SMG-1016M ............................................... ................................................. ................................................. ...... 41
3.2.5.2 SMG-2016............................................... ................................................. ................................................. ........... 42
3.2.5.3 SMG-3016............................................... ................................................. ................................................. ........... 44
3.2.6 Light indication ............................................... ................................................. ......................................46
3.2.6.1 Light indication of the device in working condition .............................................. .................................46
3.2.6.2 Light indication of the state of flows E1 ................................................. ............................................... 50
3.2.6.3 Light indication of interfacesEthernet 1000/100.............................................. ................................. 51
3.2.6.4 Light indication during loading and resetting to factory settings .............................................................. ...........52
3.2.6.5 Light indication of accidents .............................................. ................................................. .........................54

3.2.7 Using the function button "F" ................................................. ............................................... 55
3.2.8 Saving the factory configuration .................................................... ................................................. .........56
3.2.9 Password recovery .................................................................. ................................................. ................................56
3.2.9.1 Password recoveryCLI ................................................. ................................................. ......................... 56

3.2.9.2 Password recoveryweb................................................. ................................................. ....................... 57
3.2.10 Contents of delivery ................................................ ................................................. .........................................58
3.2.10.1 SMG-1016M ............................................... ................................................. ................................................. ...... 58
3.2.10.2 SMG-2016............................................... ................................................. ................................................. ........... 59
3.2.10.3 SMG-3016............................................... ................................................. ................................................. ........... 59

3.2.11 Safety Instructions ............................................................... ................................................. ...........59

3.2.11.1 General information ............................................... ................................................. ................................................... 59
3.2.11.2 Electrical safety requirements............................................................... ................................................. ................. 59
3.2.11.3 Precautions in the presence of static electricity .............................................................. ....................... 60

3.2.11.4 Power requirements .............................................................. ................................................. ......................... 60
3.2.12 InstallationSMG ................................................. ................................................. ............................................. 62
3.2.12.1 Switching order ............................................... ................................................. ......................................... 62
3.2.12.2 Fixing the brackets .................................................. ................................................. ................................. 63
3.2.12.3 Installing the device in a rack .................................................. ................................................. ......................... 63
3.2.12.4 Installing power modules .................................................................. ................................................. .............................. 64
3.2.12.5 Opening the housing ............................................... ................................................. ............................................. 65
3.2.12.6 Installing submodules .................................................. ................................................. ................................... 67

3.2.12.7 Installation of ventilation units .................................................. ................................................. ......................... 71
3.2.12.8 Installing SSDs for SMG-1016M.................................................................. ................................................. ..... 73
3.2.12.9 Installing SATA drives for SMG-2016, SMG-3016 ................................... ................................................. 74

3.2.12.10 Replacing the battery of the real time clock .................................................. ................................................. .75
3.3 General recommendations when working with the gateway .................................................. ................................77
4 Device configuration .................................................................. ................................................78

4.1 SettingSMG via web configurator .............................................. ...............................................78
4.1.1 System settings ................................................................ ................................................. .................................82
4.1.2 Monitoring .................................................. ................................................. ................................................. ..88

4.1.2.1 Telemetry ................................................... ................................................. ................................................. ..88
4.1.2.2 Flow MonitoringE1 ................................................... ................................................. ................................. 90
4.1.2.3 Channel monitoringE1................................................. ................................................. ................................. 91
4.1.2.4 Processor Load Graph ............................................................... ................................................. .........................96
4.1.2.5 MonitoringSFP modules.................................................................... ................................................. ............................... 96
4.1.2.6 Monitoringswitch front ports ............................................... ................................................. .........97

4.1.2.7 MonitoringVoIP submodules ............................................... ................................................. ....................... 98
4.1.2.8 Alarms about accidents. Alarm log .............................................................................. .........................101
4.1.2.9 Interface monitoring .................................................................. ................................................. ......................104
4.1.2.10 Drive information .............................................................. ................................................. .........................105

4.1.2.11 Interfaces V5.2 .............................................. ................................................. .............................................106
4.1.2.12 Queue statistics.................................................... ................................................. ......................................106
4.1.2.13 Tasks of the SSS (the section is available with an SMG-VNS license) .................................................. .......................107
4.1.3 Flows E1 ................................................. ................................................. ................................................. ...107

4.1.3.1 Synchronization sources .................................................................. ................................................. .........................107
4.1.3.2 Selecting the signaling protocol .................................................. ................................................. .................109
4.1.3.3 Setting physical parameters .................................................................. ................................................. ...........109
4.1.3.4 Setting the signaling protocolDSS1/EDSS1 (ISDN PRI Q.931) .............................................. ...............111
4.1.3.5 Setting up the SS-signaling protocol7 (SS7) ............................................... ...............................................115

4.1.3.6 Protocol settingV5.2 ............................................... ................................................. ......................117
4.1.3.7 Configuring the SORM signaling protocol ............................................... ..................................................118
4.1.4 Numbering plan .............................................................. ................................................. ............................................120
4.1.4.1 Creating a dial plan prefix .................................................................. ................................................. .....122

4.1.4.2 Description of the number mask and its syntax ............................................... ................................................. ......127
4.1.4.3 Examples of how the mask works .............................................................. ................................................. ................................128
4.1.4.4 Example of how timers work .............................................................. ................................................. ...............................129
4.1.4.5 An example of setting up a prefix with the "Subscriber capacity" type .............................................................. ...................129
4.1.5 Routing ................................................... ................................................. ............................................131

4.1.5.1 Trunk groups ................................................................ ................................................. ................................................131
4.1.5.2 OKS-line groups7 ................................................. ................................................. ...................................135

4.1.5.3 InterfacesSIP/SIP-T/SIP-I, SIP profiles .............................................. ................................................. ..........142
4.1.5.4 InterfacesH323.............................................. ................................................. ...............................................169
4.1.5.5 Trunk directions .................................................. ................................................. ...............................180
4.1.5.6 InterfacesV5.2 ............................................... ................................................. .........................................182
4.1.5.7 Registration ................................................. ................................................. ..................................................184
4.1.6 Subscribers .................................................. ................................................. ................................................. ....185
4.1.6.1 SIP subscribers.................................................... ................................................. ................................................. ...185
4.1.6.2 PRI profiles............................................... ................................................. ................................................. ....197

4.1.6.3 Dynamic caller groups .................................................................. ................................................. ...............199
4.1.6.4 V5.2 subscribers................................................... ................................................. ................................................. ..205
4.1.6.5 PRI subscribers.................................................... ................................................. ................................................. ...211
4.1.7 Internal resources .................................................................. ................................................. ....................................213
4.1.7.1 CDR records .................................................. ................................................. ................................................. ......213
4.1.7.2 Categories of ACS .......................................................... ................................................. ...............................................227
4.1.7.3 Access categories .................................................................. ................................................. ................................................228
4.1.7.4 Routing by access category .............................................................. ................................................. .......231

4.1.7.5 PBX profiles .............................................. ................................................. ................................................. ..232
4.1.7.6 Modifier tables................................................................... ................................................. ...............................235
4.1.7.7 TimersQ.931.............................................. ................................................. ...............................................242

4.1.7.8 Timers OKS-7 ................................................. ................................................. ..............................243
4.1.7.9 Clearance Cause Correspondence TableQ.850-cause and SIP-reply response code .............................................. ...247
4.1.7.10 Scheduled Routing .......................................................... ................................................. ....................248

4.1.7.11 Time routing .................................................................. ................................................. .........................250
4.1.7.12 Call Groups .................................................. ................................................. .................................................250
4.1.7.13 Pickup groups............................................................... ................................................. ...............................................257
4.1.7.14 Voice messages ........................................................ ................................................. ...................................258

4.1.7.15 List of SIP responses for failover trunk group .................................................................. ................259
4.1.7.16 Q.850 clear cause list .................................................. ................................................. ...............................260
4.1.7.17 List of Q.850 recovery reasons .............................................. ................................................. .............261

4.1.8 Public address system .................................................................. ................................................. ...............261
4.1.8.1 Voice messages ................................................................ ................................................. ................................264
4.1.8.2 Alert tasks.................................................................... ................................................. ................................................265
4.1.8.3 List of rooms .............................................................. ................................................. ...............................................267
4.1.8.4 Reports ................................................. ................................................. ................................................. ........269
4.1.8.5 Alert Records .................................................................. ................................................. ................................................270
4.1.9 LocalLDAP server ............................................... ................................................. ...............................271

4.1.9.1 ListLDAP storage.................................................................... ................................................. ...................................271
4.1.10 Voice mail ................................................ ................................................. ............................................272

4.1.10.1 Voice mail options............................................... ................................................. .........................272
4.1.10.2 Voice messages .......................................................... ................................................. ...................................273
4.1.11 IVR.............................................. ................................................. ................................................. ...................273
4.1.11.1 List of scenarios ............................................... ................................................. ..............................274
4.1.11.2 List of IVR sounds............................................... ................................................. .............................................288
4.1.11.3 Call Recordings (IVR) .............................................. ................................................. ....................................289
4.1.12 Recording conversations .................................................. ................................................. ...............................................292
4.1.12.1 Recording options ............................................... ................................................. .........................................293

4.1.12.2 Recordings of conversations (the section is not available when using only the SMG-VNS license) .................................................296
4.1.12.3 Group Notification Entries (not available with SMG-VNS license only)...298
4.1.12.4 Categories of call recordings.................................................... ................................................. .......................299
4.1.13 SettingsTCP/IP ............................................................... ................................................. .........................................303
4.1.13.1 Routing table............................................................... ................................................. ................................304

4.1.13.2 Network parameters ............................................... ................................................. ...............................................305
4.1.13.3 Network interfaces.................................................... ................................................. ....................................306

4.1.13.4 Range of RTP ports............................................... ................................................. ................................................310
4.1.14 Network Services ................................................................ ................................................. .........................................310
4.1.14.1 NTP ............................................... ................................................. ................................................. .................310

4.1.14.2 SNMP settings ............................................... ................................................. .............................................311
4.1.14.3 SNMPv3.................................................... ................................................. ................................................. ..........312
4.1.14.4 Configuring trap (SNMP trap) .............................................. ................................................. .........................312

4.1.14.5 DHCP server settings .............................................. ................................................. ................................314
4.1.14.6 FTP server ............................................... ................................................. ................................................. ......317
4.1.15 Network Utilities ................................................................ ................................................. .........................................318
4.1.15.1 PING.................................................... ................................................. ................................................. ................318
4.1.15.2 TRACEROUTE ............................................... ................................................. ................................................. .320

4.1.16 Safety ................................................. ................................................. ...............................................321
4.1.16.1 Configuring SSL/TLS .................................................. ................................................. ..............................321
4.1.16.2 Dynamic firewall .................................................................. ................................................. ...............................322
4.1.16.3 Blocked addresses log .......................................................... ................................................. ...............323

4.1.16.4 Static firewall .............................................................. ................................................. ...............................325

4.1.16.5 List of allowed IP addresses............................................... ................................................. ...................329
4.1.16.6 SMG network protection scheme .......................................................... ................................................. ..............330
4.1.16.7 Ensuring typical SMG network security tasks .............................................................. ................................................330
4.1.17 SettingRADIUS.............................................. ................................................. .......................................331

4.1.17.1 RADIUS servers............................................... ................................................. .............................................331
4.1.17.2 List of profiles............................................... ................................................. ...............................................332
4.1.17.3 Correspondence tables of RADIUS responses and voice messages. ................................................. ......338
4.1.17.4 RADIUS Packet Format .............................................. ................................................. .................................339
4.1.17.5 Description of variables ............................................... ................................................. ...................................342
4.1.17.6 Authorization by callback .............................................................. ................................................. ...................344
4.1.18 Traces .................................................. ................................................. ..................................................347

4.1.18.1 PCAP traces ............................................... ................................................. ..............................347
4.1.18.2 PBX trace ............................................................... ................................................. .............................................351
4.1.18.3 SYSLOG settings.................................................... ................................................. .........................................354

4.1.19 Switch ................................................................ ................................................. .................................................356
4.1.19.1 LACP Settings............................................... ................................................. ...............................................356

4.1.19.2 Configuring Switch Ports .................................................. ................................................. ...................358
4.1.19.3 802.1q............................................... ................................................. ................................................. ..............360
4.1.19.4 QoS and bandwidth control .............................................................. ................................................. ..............362
4.1.19.5 Prioritization ............................................................... ................................................. .........................364

4.1.20 Working with objects and the "Objects" menu .......................................................... ................................................. .........365
4.1.21 Saving the configuration and the "Service" menu .................................................. ................................................365
4.1.22 Setting the date and time............................................................... ................................................. ......................366
4.1.23 Software update viaweb configurator ............................................... ................................................. 366

4.1.24 Licenses................................................... ................................................. ................................................. .....367
4.1.25 Help menu .............................................................. ................................................. ...............................................369
4.1.26 Control Menu .............................................................. ................................................. ...............................................370
4.1.27 Viewing Factory Settings and System Information............................................................... .........................372
4.1.28 Exiting the configurator............................................................... ................................................. ...............................372
4.2 Command ReferenceCLI (SMG) ............................................... ................................................. .....373

4.2.1 Command line in debug mode, list of supported commands and switches ..............................................373
4.2.1.1 Trace commands available through the debug port............................................................... .........................376
4.2.2 SettingSMG via Telnet, SSH or RS-232 .......................................... ................................................. 377

4.2.2.1 Command listCLI ................................................. ................................................. .................................378
4.2.2.2 Change the password for accessing the device throughCLI ................................................. .................................382
4.2.2.3 "Statistics" mode ............................................... ................................................. ......................................382

4.2.2.4 Control mode .................................................. ................................................. ...............................................388
4.2.2.5 Port mirroring parameter configuration mode............................................................... ...............391

4.2.2.6 Device General Parameters Configuration Mode .................................................................. .........................392
4.2.2.7 Parameter configuration modeCDR ................................................. .............................................398

4.2.2.8 Field ListCDR ................................................. ................................................. ...............................................402
4.2.2.9 Access category configuration mode .............................................................. ...............................................405
4.2.2.10 E1 stream configuration mode .............................................. ................................................. .............406

4.2.2.11 Dynamic firewall parameter configuration mode .............................................................. ........415
4.2.2.12 Static firewall parameter configuration mode .............................................................. ............419
4.2.2.13 FTP parameter configuration mode .............................................................. ................................................. ..430
4.2.2.14 H.323 protocol parameter configuration mode .............................................. ................................432

4.2.2.15 H.323 interfaces parameter configuration mode .............................................. ...............................434
4.2.2.16 Call group configuration mode .............................................................. ................................................. .....440
4.2.2.17 SS-7 line group configuration mode .............................................. ...............................................441
4.2.2.18 SS-7 timers configuration mode .............................................. ................................................. ...445
4.2.2.19 Submodule usage configuration mode .................................................................. ................................448
4.2.2.20 Modifier table configuration mode .............................................................. ....................................448
4.2.2.21 Network parameter configuration mode .................................................. ...............................................454
4.2.2.22 Dial plan configuration mode .............................................................. .................................................468
4.2.2.23 Pickup group configuration mode .............................................................. .................................................476
4.2.2.24 PBX profile configuration mode .............................................................. ................................................. ......477
4.2.2.25 Q.931 timer configuration mode .............................................. ................................................. .....480

4.2.2.26 RADIUS configuration mode .............................................. ................................................. ................481
4.2.2.27 Callback Authorization Configuration Mode .............................................................. .........................492
4.2.2.28 Configuration mode of call recording settings .............................................. ................................494
4.2.2.29 Mode for configuring call recording masks .............................................................. ...................................496
4.2.2.30 Static route configuration mode .............................................................. ...............................................497
4.2.2.31 Configuring the Q.850 release reason list .............................................................. ................................................498
4.2.2.32 SIP/SIP-T general settings editing mode .............................................................. ...............................................499
4.2.2.33 SIP/SIP-T interface parameter configuration mode .............................................................. .........................501
4.2.2.34 Configuration mode of parameters of subscriber registration of interfaces .............................................................513
4.2.2.35 SIP subscriber parameters configuration mode .............................................................. .................................514
4.2.2.36 VAS configuration mode for a group of subscribers.................................................................. .........................................527
4.2.2.37 PRI-subscriber parameters configuration mode .............................................................. ...................................529
4.2.2.38 VAS PRI configuration mode .............................................................. ...................................................532

4.2.2.39 PRI profile configuration mode .............................................................. ................................................. ......533
4.2.2.40 SS-7 category conversion configuration mode .............................................................. .........................536
4.2.2.41 Switch parameter configuration mode .............................................. ...............................................537
4.2.2.42 syslog parameter configuration mode .............................................................. ...................................................551
4.2.2.43 Voice message file management configuration mode .............................................................. ....553

4.2.2.44 IVR function configuration mode .............................................................. ................................................. .........555
4.2.2.45 Trunk group configuration mode .............................................................. ................................................. .556

4.2.2.46 Trunk Direction Configuration Mode .............................................................. .................................559

4.2.3 Switch ConfigurationSMG-2016/3016 ............................................... ................................................. ....560
4.2.3.1 Switch structure .............................................................. ................................................. ...............................560
4.2.3.2 Switch Interface Control CommandsSMG-2016/3016............................................... ........562

4.2.3.3 Commands for configuring aggregation groups ............................................... ................................................. ..........568
4.2.3.4 Interface Control CommandsVLAN of the SMG-2016 board ............................................... ...................570

4.2.3.5 Configuration CommandsSTP/RSTP.................................................... ................................................. ....................571
4.2.3.6 MAC Table Configuration Commands............................................................... ................................................. ...............574
4.2.3.7 Commands for configuring port mirroring .................................................................. ................................................575
4.2.3.8 Commands for setting the functionSELECTIVE Q-IN-Q............................................... ....................................578
4.2.3.9 Protocol settingDUAL HOMING .................................................... ................................................. ........580

4.2.3.10 Configuring the LLDP protocol............................................... ................................................. ...............................583
4.2.3.11 QOS setting ............................................... ................................................. ................................................590

4.2.3.12 Configuration commands .................................................................. ................................................. ................593
4.2.3.13 Other commands............................................... ................................................. .............................................594
5 Applications (SMG)................................................. ................................................. ......... 596

5.1 Appendix A. Assignment of cable connector pins .............................................. .............596
5.1.1 ForSMG-2016, SMG-3016............................................. ................................................. .................................596
5.1.2 ForSMG-1016M............................................... ................................................. .............................................598
5.1.3 Correspondence tables for wire color and connector contactE1 line .................................................. .......599
5.2 Appendix B. Backup Firmware Update .................................................................. .............602

5.2.1 Backup device firmware update viaRS-232.............................................. .........602
5.2.2 Backup device firmware update fromUSB flash drive ...........................................604
5.3 Appendix C. Examples of how modifiers work and device settings viaCLI.......605
5.3.1 Examples of how modifiers work ............................................................... ................................................. ..............605
5.3.1.1 The order of applying modifiers on the incoming connection .................................................. .........................605
5.3.1.2 The order of applying modifiers on outgoing communication .............................................. .......................605
5.3.1.3 Task1................................................. ................................................. ................................................. ......605

5.3.1.4 Task2................................................. ................................................. ................................................. ......607
5.3.2 Example of setting up a device viaCLI ................................................. ................................................. 608
5.3.2.1 Task................................................. ................................................. ................................................. .........608
5.3.2.2 Initial data ................................................ ................................................. ................................................608
5.3.2.3 Setting viaCLI ................................................. ................................................. ...................................608
5.4 Appendix D. Transferring VDO settings fromRADIUS servers for dynamic
subscribers ............................................... ................................................. ................................................616
5.4.1 Query Syntax .................................................................. ................................................. ................................................617
5.4.2 Examples of service connection .............................................................. ................................................. ......................618
5.5 Appendix D. SORM function settings .............................................................. ...................................618

5.5.1 Calculation of the required number of submodules when using SORM .............................................................. ........620
5.5.2 The logic of the operation of setting up for control and interception of calls SORM .................................................. ........621
5.5.3 Tuning MethodSMG for the delivery of the SORM protocol in accordance with the Order of the Ministry of Communications of the
Russian Federation from11/19/2012 N 268............................................. ................................................. .........................................622
5.5.4 Setting exampleSMG for delivery under the SORM protocol Order of the Ministry of Telecom and Mass Communications of the Russian
Federation dated 11/19/2012No. 268 without the use of modifiers on the SORM stream .............................................. ......................623
5.5.4.1 Setting up the numbering plan in accordance with the requirements of the Order of the Ministry of Communications of the Russian Federation dated
11/19/2012 N 268: .............................................. ................................................. .............................................624
5.5.4.2 SettingSIP subscribers ............................................... ................................................. ..............625

5.5.4.3 Setting up incoming and outgoing modifiers for numbers A and B .................................................. ...............627
5.5.4.4 Assigning numbers for control ............................................... ................................................. .............633

5.5.5 Designations and codes of fields in SORM messages .............................................. .........................................635
5.5.5.1 Designations and codes of alarms .......................................................... ................................................. .........................635
5.5.5.2 Designations and codes of supplementary services .................................................................. ............636

5.5.5.3 Reasons for non-acceptance and non-execution of commands .............................................. ...............................................637
5.5.5.4 Information about the state of the subscriber set in message No.3................................................. .640
5.5.6 Description of the operation of the option “Analysis of the operator selection code” .............................................................. .........................641
5.6 Appendix E. Interaction of the device with monitoring systems...............................................643

5.7 Appendix G: Voice Messages and Music on HoldMOH.................................646
5.8 Appendix H. Working with VET services .............................................. .........................................647
5.8.1 Working with the services "Call Hold", "Call Transfer" and "Three-party Conference" .....649
5.8.2 Working with the "Call Forwarding" service .............................................................. ................................................. .649
5.8.2.1 Forward unconditional (CF Unconditional): .............................................. .................................................650

5.8.2.2 Forward on Busy (C.F. Busy): ............................................... ................................................. ....650
5.8.2.3 Forward on no answer - (CF No reply). ................................................. .................................................650
5.8.2.4 Redirect on unavailability (CF Out Of Service) ............................................... .................................650
5.8.2.5 Forward by time (CF Time) ............................................... ................................................. ......650
5.8.3 Conferencing with sequential gathering of participants .............................................. .......................652
5.8.4 Call pickup ................................................................ ................................................. .........................................653
5.8.5 Intercom and Paging Calls .............................................................. ................................................. .............653
5.8.6 Activation/deactivation of the password, outgoing communication by password .......................................................... ......................653
5.8.7 Changing the passcode .............................................................. ................................................. .........................................654
5.8.8 Restriction of outgoing communication .................................................... ................................................. ...................654
5.8.9 Do not disturb................................................ ................................................. ...............................................655

5.8.10 Cancellation of all services.............................................. ................................................. .........................................656
5.8.11 Follow me (Follow me) ............................................... ................................................. .........................656

5.8.12 Follow me on no answerFollow me no response)....................................... .................................657
5.8.13 Call Park ................................................................ ................................................. .........................................658
5.8.14 Voice mail ................................................ ................................................. ............................................659
5.8.15 Call Recording on Demand ....................................................... ................................................. ................662
5.9 Annex I. ServiceRADIUS CALL MANAGEMENT............................................... .................662
5.9.1 Number Modification Request SyntaxCgPN and CdPN ............................................... .................663

5.9.2 Call Routing Management .................................................................. ................................................. .......664
5.9.3 Call category management .................................................................. ................................................. ................665
5.9.4 Managing dynamic subscriber settings .................................................................. ................................666

5.10 Appendix K. Control and monitoring by protocolSNMP ...............................................667
5.10.1 DescriptionOID from ELTEX-SMG MIB .............................................. ................................................. .................668
5.10.2 Monitoring and configurationSIP subscribers (static subscribers) .........................................................699

5.10.2.1 Monitoring ............................................... ................................................. ................................................. ...699
5.10.2.2 Index search example .............................................................. ................................................. ..............................699
5.10.2.3 Dial plan and number search example .............................................................. .................................................700
5.10.2.4 Dial Plan and Partial Number Search Example .............................................................. ...............................701
5.10.2.5 Viewing information without using search .............................................................. ................................................703
5.10.2.6 Configuration............................................................... ................................................. .........................................703
5.10.2.7 Example of creating a new subscriber .............................................. ................................................. ................704

5.10.2.8 Example of viewing settings ............................................... ................................................. .........................704
5.10.2.9 Example of editing settings .............................................. ................................................. ................704
5.10.2.10 Example of deleting a subscriber ............................................... ................................................. ......................705
5.10.3 Monitoring and configuring groups of dynamic subscribers.................................................................... ............715
5.10.3.1 Monitoring ............................................... ................................................. ................................................. ...715

5.10.3.2 Index search example .............................................................. ................................................. ...............................716
5.10.3.3 Example of searching by subscriber ID .......................................................... ................................................. .........................716
5.10.3.4 Example of searching by numbering plan and partial number .............................................................. ...............................717
5.10.3.5 Viewing information without using search .............................................................. ................................................717
5.10.3.6 Configuration............................................................... ................................................. .........................................718

5.10.3.7 Example of creating a new group............................................................... ................................................. ......................719
5.10.3.8 Example of viewing settings ............................................... ................................................. .........................719

5.10.3.9 Example of editing settings .............................................. ................................................. ................719
5.10.3.10 Example of deleting a group....................................................... ................................................. ................................719
5.10.3.11 Obsolete OIDs ............................................... ................................................. ...............................................731

5.10.3.12 MIB-2 OID support (1.3.6.1.2.1) .................................. ................................................. .........................732
5.11 Appendix K. Provision of the redundancy functionSMG .................................................732
5.12 Appendix M. Safety Recommendations .................................................................. .........................738
5.12.1 Changing passwords toWEB and CLI ............................................... ................................................. ......................739
5.12.2 Creating Limited Accounts............................................................... ................................................. .740

5.12.3 Restricting access to signaling and control interfaces .................................................................. ...........740
5.12.4 Setting up a static firewall............................................................... ................................................. .......741
5.12.5 Configuring a Dynamic Firewall............................................................... ................................................. ...741
1 History of changes
Software version:V.3.20.5
Version Version Date of issue Content of changes

document BY
Version4.6 V.3.20.5 03/31/2023 Added:
• Option "Transit ISUP Location Number";

• QSIG-NA name transfer method (Ericsson);
• Monitoring of trunk groups via SNMP;
• Monitoring of licenses via SNMP;
• Monitoring the number of installed modules С4Е1, SMVP through
SNMP;
• "Send DisplayName in Remote-Party-ID header" option.
Changed:
• Expanded the functionality of the SSS;

• Removed the need for a recording license
conversations for the work of the SGO.
Version4.5 V.3.20.3 11/14/2022 Added:
• Option “DTE/DCE mode adjustment” for SORM protocol;

• The option "Notify me when a call ends in (sec)" on prefix
in the numbering plan;
• Ability to upload cdr files using the SCP protocol;
• Option "Substitute characters '?' to 'D' in CgPN" for Q.931 protocol;
• Option "Cisco 1700 adaptation" for H.323 interfaces.
Changed:
• Removed the option "VAT reset timeout" for dynamic

subscribers.
eleven
Version4.4 V.3.20.0 07/31/2022 Added:
• VDO "Recording of conversations on demand";

• End call mode "Quiet" for call groups;
• Disk monitoring via SNMP;
• Modification of RedirPN for RADIUS;
• Logic "AND" in the numbering plan;
• Name transfer method for H323 interfaces;
• Possibility to clear queue statistics;
• The option "Call back the rejected call in the Group call";
• Option "Allow inband DTMF";

• Option "Order of occupation of streams by SLC";
• SNMP request to get the value of the IP address from the
network interface;
• Call group callback settings when using queues;
• Reset configuration via cli;

• Monitoring of active sessions of the web-interface;
• Outgoing communication modifiers in the PRI profile;
• Performance monitoring of KPD1 KPD2 when implementing
TCP;
• Operation of the OOV port on SMG-3016;
• Switch port counter reset button for SMG-1016M.
Changed:
• Reworked removal of logs;

• Increased the number of consecutive redirects up to 10;
• Extended indication of external source states sync for

portssync;
• For SMG-1016m, the maximum number of subscriptions
500;
• Expanded the functionality of the SSS;
• Increased the number of accounts in the web interface up to 100
pcs.
12
Version4.3 V.3.19.0 05/13/2021 Added:
• Multiple registration (SIP-forking);

• Voice notification system;
• Routing by access category;
• Transfer "real ip" to RADIUS-Accounting;
• Switch setting for SMG-3016;
• Redundancy SMG-3016;
• Statistics of Radius requests via SNMP;
• Listening to conversation recordings without the possibility
downloads;
• Auto-enable logging after restart gateway;
• Sending Dispay name when calling through a call group;

• Voice mail. Playing message details;
• Access category for the Dial block in IVR;
• V5.2-LE. hotline service.
Changed:
• Changed response from 502 to 486 busy here when using DVO
DND;
• Operation of OPTIONS messages with redundancy scheme
(switching precedence does not stop the workSIP
OPTIONS messages);
• Operation of transport mode on SIP interfaces (on one one
mode is allowed per port).
Version4.2 V.3.18.0 05/14/2020 Added:
• Registration of a SIP subscriber from an arbitrary network

interface;
• Routing by TO instead of RURI (optional);
• Option "Transit SIP-headers" for sip-profile;
• LDAP server (SMG-2016; SMG-3016);
• Voice mail.
Changed:
• Extending the life of the backup device up to 720 hours;
вЂў Added the internal number of the subscriber to the conversation

records when calling a call group viaIVR;
• Display of accidents, now all current accidents are
included in a separate list;
• Transport protocol setting now on each sipinterface;
• Fixed bugs in assembling a pair of master-slave with

usageLACP.
13
Version4.1 V.3.17.0 11/18/2019 Added:
• Support for working with a remote LDAP server;

• VAS "Call Parking";
• E1 flow reservation (SMG-2016);
• Advanced sip-profile settings;
• Ability to use "Login" as "User-Name" when authorizing/
accounting byRADIUS;
• The number of the call group in the call record if you have reached
subscriber through this group.
Changed:
• Switching settings in the web interface has been changed

from drop-down list on tabs, for convenience;
• Added a timeout between switching the master- slave";
• Removed broadcast address setting in network interfaces

(autocomplete);
• Playing time and position in the queue moved to two different
functions (call group);
• Renamed prefix type "Modifier" to "Subscriber capacity";
• Renamed Direct Prefix Availability Control to "Block when direct

prefix is not available."
Version4.0 V.3.16.0 08/07/2019 Added:
• Playback of audio files as CPV;

• NTP server on SMG-1016M;
• PRI profile for PRI subscribers;
• Support for multiple E1 streams for PRI subscribers;
• Restriction on the number of lines for PRI-subscribers;
• Use of different numbering plans for PRI-subscribers;
• Calls to PRI-subscribers;
• SNMP trap about changing E1 streams synchronization sources;
• SNMP OID with E1 stream name;
• Forwarding by days of the week and time of day;
• The names of external drives are tied to the interface ports;
• Video stream transmission in Video Offroad mode;

• Trunk blocking when direct prefix is not available;
Changed:
• The size of the interception group has been increased to 60 participants;

• The upper limit of the timeout in the call group has been increased to 3600
seconds;
• Web settings sorted - most used functions are moved up and
logically grouped.
Version3.8 V.3.14.1 04/16/2019 Added:
• Callback authorization upon receipt of a RADIUS CoA

request.
14
Version3.7 V.3.14.0 11/28/2018 Added:
• Sending the received X-UniqueTag SIP header or shaping

it from a valueRADIUS Acct-Session-Id;
• SNMP OID of SIP trunk availability;
• Ability to enable call traces on a trunk group or by phone
number;
• Transmission of Connected Name for SIP-subscribers;
• Switching to local call service when there is no transit registration
on the server;
• Device-side release mark in CDR.
Version3.6 V.3.12.0 22.10.2018 Added:
• Work in the mode of the facilitated reserve according to the scheme 1+1;
• Queues in call groups.
Version3.5 V.3.10.1 08/09/2018 Added:
• Edit link ID for V5.2;

• Own subscribers via PRI;
• Combining RADIUS servers into groups for use different servers
in profilesRADIUS;
• Ability to send unmodified CgPNs to RADIUS orCdPN in User-
Name regardless of assigned modifiersCgPN and CdPN;
• Option to ignore HOLD indication in linkset settings OKS-7;
• DVO "Black List" (for SMG-2016);

• DVO "Do Not Disturb" (for SMG-2016);
• NTP server;
• Announcement of NTP servers via DHCP.
15
Version3.4 V.3.10.0 06.12.2017 Added:
• Modification of numbers when changing the numbering plan;

• Deferred application of changes in dial plans;
• Mask "exception" when selecting a number;
• Ability to set a description for the trunk group;
• Automatic configuration upload via FTP and TFTP protocols;
• Sending queries to RADIUS based on table selection modifiers;
• Transfer to RADIUS of the subscriber's IP address in the Framed-IP-Address

attribute;
• Configuring sending SNMP notifications about requests to
RADIUS;
• Setting up BLF and intercom when configuring subscribers
throughSNMP;
• Access to call recordings based on recording categories
conversations;
• Automatic upload of recorded conversations to FTP;
• Recording conversations on a USB drive;
• The numbering plan has been added to the name of the recorded conversation;
• Setting hop counter in OKS-7 linksets;
• Modification of Location Number;
• Transit of SIP headers;
• Optional filling of display-name when receiving a call without
display-name;
• Automatic gain setting;
• Notification of subscribers by a pre-recorded message;
• Authorization of SIP-subscribers only by IP-address;
• Setting the caller's display name and priority using the
given name;
• Traceroute function.
Changed:
• Renamed "fail2ban" section to "dynamic firewall";
• The "firewall profiles" section has been renamed to "static

firewall";
• Separated blocking rules in dynamic firewall for various services.
Version3.3 V.3.9.0 07/31/2017 Added:
• New protocol V5.2 LE;

• New types of VAS: access to long-distance communication by password,
password activation, outgoing communication restriction (Appendix H.
Working with VAS services);
• Copying prefixes between dial plans (section
3.1.6 numbering plan);
• Selecting an outgoing RADIUS profile in the SIP interface settings
(Section 3.1.7.3.1.1. SIP Interface Settings tab);
• Ability to change the order of SIP-interfaces in the list;
• Dial plan selection in the Dial block of the IVR scenario;
• Ability to download the MIB-file from the device;
• Description of the work of the local gatekeeper.
16
Version3.2 V.3.8.0 01/09/2017 Added:
• Choice of time rounding and transmission of milliseconds in

RADIUS parameters;
• Transferring the name of the call recording file to RADIUS-
parameters;
• VAS Clear All service management for dynamic
subscribers throughRADIUS;
• Using # and * in select boxes in IVR;
• Increased the number of dial plans to 255 for
SMG-20161;
• Creating a common prefix in the numbering plan for all groups
interception;
• Testing the work of number modifiers;
• Selective assignment of E1 streams from groups of SS-7 lines to
various trunk groups;
• Launching the SS-7 channel integrity test from the web interface;
• Disabling the issuance of Redirecting and Original Called numbers in OKS-
7 if there are differences in the SIP RURI and To fields;
• Issuance of the Diversion field in SIP URI format;
• Disabling the transmission of the + symbol in numbers of the international type;
• Setting the address of the subnet from which calls will be received
in settingsSIP interfaces;
• DTMF transmission by SIP NOTIFY method (Cisco DTMF);
• Separate mode for limiting the number of available incoming and
outgoing linesSIP subscribers;
• Selection and memorization of the interface language based on
preferences in browser settings and user choice;
• Holding a call on an incoming trunk with automatic
establishing a connection on an alternative route when the
connection is broken;
• Duplication of incoming INVITEs to the SMS receiving server;
• Reception of SMS messages via SMPP and transmission via SIP to
serverSMS.
Changed:
• IVR-only settings have been removed from the system

parameters and moved to settingsIVR;
• In the IVR Caller Info block, the original name of the subscriber, if it does
not match the number mask (previously, the original name was
removed).
Version3.1 V.3.7.0 08/26/2016 Added:
• Configuring the use of SM-VP submodules;

• Customizable set of CDR fields;
• Expanded list of CDR fields;
• SORM settings over TCP;
• Restriction of duration of calls on a prefix;
• Optional issue of MOH in trunk group settings;
• Setting up BLF monitoring groups;
• New SIP header options for intercoms;
• English language of the web-interface.
17
Version3.0 V.3.6.0 06/14/2016 Added:
• Intercom and paging calls;

• Limiting the number of calls (CPS) on trunks;
• Indication of an accident exceeding the CPS limit on trunks;
• Management of the signaling link OKS-7 in the web-configurator;
• Channel management (CIC) OKS-7 in the web-configurator;
• Operator selection code analysis option and node type selection
links in the SORM settings;
• Selecting a RADIUS profile for outgoing communication in the
settings trunk group;
• Option "Local CPV instead of early-media";
• QSIG Tunneling Protocol in SIP (SIP-Q).
Version2.9 V.3.5.1 04/04/2016 Added:
• The new state of the SM-VP submodule is "SSW.Sorm";

• Support for P-Early-Media (RFC5009).
Version2.8 V.3.5.0 03/21/2016 Added:
вЂў Voice notification about the beginning of the recording of the conversation;
• Protection against hacking WEB, TELNET, SSH in Fail2ban;
• Configurable list of Q.850 release reasons to switch to backup
trunk group;
• Detection of digits "*" and "#" as flash signal;
• Collection of a conference with sequential collection using re-
INVITE with the sendonly flag;
• Optional sending of RADIUS-acct to both legs of the connection;
• Displaying the numbering plan name in the settings tree;
• Text description for each modification rule;
• Changing the order of masks inside the prefix and table
modifiers;
• Caller ID request in trunk group via incoming connection;
• Optional rounding of call duration in CDR records up or down;
• Uploading the configuration file in the cfg_${dev-name}

_YYYYMMDD.yaml format;
• Support for RFC6432 "Carrying Q.850 Codes in Reason Header
Fields in SIP (Session Initiation Protocol) Responses";
• Conference with consecutive gathering for SORM;
• Correct operation of SORM when dialing the operator selection code
when calling;
• VLAN configuration on the switch for SMG-2016.
Version2.7 V.3.4.2 06.11.2015 Added:
• Number modifiers for SORM;

• Option "Do not transmit VAS service prefix" for the protocol
SORM;
• Do not use extended error codes option for SORM protocol;
• Arming/disarming by pressing "*", "#";

• Optional use of AV-Pair Class for transmission categoriesSS7
subscriber;
• Increased timer Т303 for Q.931 protocol up to 40 sec;
• Reduced the lower limit of the timer T301 for the Q.931 protocol before30
s.
18
Version2.6 V.3.4.0 09/03/2015 Added:
• Setting the mode of creating CDR files;

• Setting directories for storing CDR data;
• Ability to add a disconnect initiator flag to recordsCDR;
• Type of prefix "IVR scenario";

• Type of prefix "interception group";
• Clear Channel setting;
• Clear Channel override setting;
• Setting Clear Channel-transit;
• Setting the local direction on the trunk;
• Setting the dial plan and caller mask for call groups.
Version2.5 V.3.3.0 05/21/2015 Added:
• Monitoring of each processor core;

• List of SIP responses to fail over to the backup trunk group;
• Using Redirecting number for routing calls;
• New modes of operation in call groups;

• REC and Caller Info blocks in IVR scenarios;
• Log of blocked addresses fail2ban;
• Setting the transmission of original or processed numbers
in messagesRADIUS;
• Sending RADIUS-Authorization for local forwarding;
• Transmission of time in UTC format in RADIUS-Accounting
messages;
• Issuance of standard phrases of voice messages when receiving
a rejection messageRADIUS servers with reason failure.
Version2.4 V.3.2.1 03/30/2015 Added:
• Setting up an IVR scenario;

• Path for storing scripts and sounds for IVR;
• Information about drives;
• Conference with sequential collection and according to the list;
• Prefix type "Conference";
• Prefix type "IVR scenario".
Version2.3 V.3.2.0 28.10.2014 Added:
• Type of prefix "call group" and "pickup group";

• Options "Send no more than 15 digits to IAM" and "Control
availabilityRedirecting/Original Called on incoming call
forwarding" in the settings of the group of lines SS-7;
• Option "Transit Registration" in the SIP interface;
• Setting call groups;
• Setting up pickup groups;
• Ability to set the gateway for network interfaces;
• Setting up groups of dynamic subscribers.
19
Version2.2 V.3.0.0 09/02/2014 Added:
• Reservation of ports global Dual Homing;

• Ability to select the operating mode of the Ethernet ports;
• Software update via FTP;
• "NAT keep-alive" option in SIP profile;
• Ability to connect via https;
• SORM setup procedure according to Order 268.
Version2.1 V.2.15.02 02.05.2014 Added:
• Emergency phasing with one signal link in linkset;
• Indication of an accident in case of unavailability of the

oncoming protocol devicesSIP;
• Sending caller category via SIP protocol in the fieldscpc and cpc-
rus;
• Restricting the transfer of optional (optional) fields in
messagesSIP;
• VDO timeouts;
• OKS-7 timers;
• Ability to record conversations.
Version2.0 V.2.15.01 07.02.2014 Added:
• Setting up VDO;
• Application for working with VDO;
• Setting up RADIUS call management.
Version1.12 V.2.14.02 12/12/2013 Added:
• LACP settings;
• Additions to Appendix D. Provision of SORM functions;
вЂў Setting the sending of dialing digits to IAM during overlap;
• Setting the minimum registration interval for subscribers;
• DTMF transmission RFC2833 PT.
Version1.11 V.2.14.01 10.10.2013 Added:
• Support for H.323 protocol;

• Setting up the correspondence table Q.850-cause and SIP-reply;
• Scheduled routing setup;
• Setting the range of RTP ports;
• Setting up an FTP server;
• Setting up Firewall profiles;
• Setting the use of voice messages;
• Choosing a device for emergency logging;
• View connection information by channel for
submodules;
• Activity control at L1 level for SORM;
• An example of the SMG connection diagram when working in quasi-
coupled mode OKS-7 via PBX with STP functions;
• Example of SMG connection scheme in combined mode;
• Appendix G. Voice messages and music on hold MOH.
Version1.10 V.2.12.01 05/20/2013 Added:
• Appendix “Recommendations for the work of SMG in the public

networks".
20
Version1.9 V.2.12.01 1.04.2013 Added:
• Section "Network services" - setting NTP, DHCP, SNMP

parameters, the list of allowed addresses in a separate
section;
• Setting system parameters;
• Monitoring of E1 channels;
• Monitoring of VoIP submodules;
• Setting up trunk directions;
• Modifiers Original CdPN and RedirPN;
• Setting Q.931 timers;
• Device access restriction settings;
• Setting limits on incoming and outgoing communication for
subscriber;
• Configuring the network interface for receiving and
transmitting signalSIP messages and voice traffic.
Version1.8 V.2.11.02 09.01.2013 Added:
• Expanded list of E1 flow monitoring parameters;

• Monitoring of SFP modules;
• Monitoring of an emergency condition;
• Log of emergency events;
• Support for MTP3 counter code function (DPC-MTP3);
• Support for ISUP counter code function (DPC-ISUP);
• Support for the Kazakh SORM specification;
• Search for numbering plan masks by template;
• NAT (comedia mode) for SIP through NAT;
• Configuring VPN/PPTP interfaces;
• Create a list of allowed addresses to connect to device
• Tracing filters;
• Limiting the number of simultaneous calls for subscriber.
Version1.7 V.2.10.04 20.09.2012 Added:
• Setting the modifier table in a separate menu;

• Choice of modifiers from the table when setting CDR-
records;
• Selection of modifiers from the table when setting up
pbx- profiles;
• Selecting modifiers from the table when configuring RADIUS-
profiles;
• Selection of modifiers from the table when configuring trunk groups.
Version1.6 V.2.10.02 20.08.2012 Added:
• Fail2ban settings;
• Monitor CPU load;
• Examples of how modifiers work;
• Configuring registration parameters for the SIP interface;
• Viewing the list of addresses issued via DHCP;
• STUN server settings;
• Digest authorization settings;
• Group editing of SIP-subscribers.
21
Version1.5 V.2.9.05 20.03.2012 Added:
• РBX profiles for SIP subscribers;

• Additional settings for CDR-records (labels redirection,
number of redirector);
• Separate interface for RADIUS messaging.
Version1.4 V.2.9.03 28.12.2011 Added:
• The maximum number of TG and SIP interfaces has been increased

before64;
• Setting up SNMP traps;
• DHCP server management;
• Binding of IP-MAC addresses;
• Apply/confirm switch settings without rebooting the
gateway;
• Apply/confirm VLAN settings without reboot gateway;
• Checking the availability of the subscriber's number in

the database configuredSIP subscribers;
• Checking the possibility of routing by number;
• Possibility of reading CDR from a local disk;
• Control of incoming media traffic from a specific IP addresses.
Version1.3 V.2.1.01 3.11.2011 Added:
• CDR settings.
Version1.2 V.2.1.01 21.10.2011 Added:
• SORM alarm settings;

• Appendix D. SORM function settings.
Version1.1 V.2.0.10 10/10/2011 Added:
• DHCP server settings;

• Volume settings for the received/transmitted signal;
Version1.0 V.2.0.10 09/12/2011 First publication
-1In the presence of a license DVO.
22
2 Conventions and target audience
2.1 Conventions
Designation Description
Calibri Notes and warnings, titles of chapters, headings, headings of tables are highlighted
in bold.
Calibri Italics indicate information requiring special attention.
Courier New FontCourier New recorded examples of entering commands, the result of them
execution, program output.
<KEY> Capital letters in angle brackets indicate the names of keyboard keys.
Analog phone icon.
digital gateway iconSMG.
Soft switch iconSoftswitch ECSS-10.
Digital subscriber telephone exchange icon.
Network connection icon.
Optical transmission medium.
23
2.2 Hints, notes and warnings
-Tips provide tips on how to use and set up your device.
-Notes contain important information or recommendations for use and setup devices.
-Warnings inform the user of situations that may cause harm device or person, cause the device
to malfunction or data to be lost.
2.3 Target audience

This user manual is intended for technical personnel who configure and monitor the Gateway throughweb
configurator, as well as procedures for installing and maintenance of the device. Qualification of technical
personnel assumes knowledge of the basics of the TCP/IP, UDP/IP and principles of building Ethernet
networks.
24
3 Description of products
3.1 Introduction
Communication facilities are intensively developing in the world, exploiting the most modern hardware and
software solutions. This raises the problem of introducing new communication devices using other principles of
information transfer into existing communication networks. The solution is in the use of special equipment that
connects heterogeneous sections of the communication network into a single whole. Such equipment is currently
digital gateways. The presence of a gateway allows a gradual transition from the existing communication network
to communication networks that have a more efficient implementation, but work according to other principles.
At the moment, the most efficient networks areIP networks that are weakly dependent on the environment
data transfer and on the type of data, however, are the most flexible and manageable. For interfacing
traditional communication networks, which are based on the principle of circuit switching, with
communication networks that use to transmit informationIP network, SMG digital gateway is designed,
designed and manufactured by the company "ELTEKS".
This manual contains information about the main featuresSMG-1016M, SMG-2016 and SMG-3016. IN This
document lists the technical characteristics of the gateway and its components. It also provides an
introduction to how to operate and maintain using the software.
3.2 Product description
3.2.1 Purpose
Digital GatewaysSMG-1016M, SMG-2016 and SMG-3016 are designed to interface alarms and PSTN media
streams (E1) and VoIP networks, as well as to work as a media gateway (converting codecs, conferencing,
receiving and generating tones, andDTMF, voice output messages).
Number of paths E1, supported by SMG, can reach 16, the number of spoken (media) channels from side
E1 - up to 495, from the VoIP side - 768 (when using the G.711 codec with bundling20ms or more).
The gateway's sub-modular design allows for flexible capacity changes, while the minimum number of module
types makes it easy to expand and upgrade the system.
SMG is the best reliable solution for upgrade, build and migration tasks telecommunications
infrastructure from PSTN toNGN.
The gateway allows you to organize one streamE1 to SORM console. E1 stream running on the protocol
SORM, contains28 conversational channels for listening to controlled subscribers. At combined control, audio
traffic from subscribers A and B is mixed into the conversational channel of the SORM stream. Audio streams
are mixed using a three-way conference atVoIP submodule. One VoIP submodule supports 27 three-way
conferences. Thus, to ensure the possibility of interception simultaneously on all channels of the stream E1 is
required to the gateway has at least2 VoIP submodules.
Main characteristicsSMGs:
• number of E1 interfaces from 4 to 16 in increments of 4;
• up to 768 VoIP channels (128 channels for connection to TDM per one submodule);
• number of Ethernet ports for SMG-1016M:
• 3 ports 10/100/1000BASE-T;
• 2 x 1000BASE-X (SFP) ports.
25
• number of Ethernet ports for SMG-2016 and SMG-3016:
• 4 ports 10/100/1000BASE-T;
• 2 combo 1000BASE-X (SFP) ports.
• support for static address and DHCP;
• DHCP server;
• IP telephony protocols SIP, SIP-T, SIP-I, SIP-Q, MGCP1, MEGACO1, SIGTRAN1; H.3232;
• TDM protocols: DSS1/EDSS1 (ISDN PRI Q.931), QSIG and CORNET for transferring the subscriber's
name, OKS-7 (coupled and quasi-coupled operation), V5.2;
• support for the Q.699 standard — interaction between EDSS1 and SS-7;
• support for registration of SIP-subscribers:
• up to 2000 for SMG-1016M;
• up to 3000 for SMG-2016 and SMG-3016.
• DTMF transmission (SIP INFO, RFC2833, in-band, SIP NOTIFY);
• echo cancellation (recommendation G.168);
• speech activity detector (VAD);
• comfort noise generator (CNG);
• adaptive and fixed jitter buffer;
• V.152 data transmission;
• fax transmission:
• G.711 pass through;
• T.38 UDP Real-Time Fax.
• NTP support;
• DNS support;
• SNMP support;
• bandwidth limitation and QoS for SMG-1016M;
• ToS and CoS for RTP and signaling;
• VLAN for RTP, signaling and management;
• software update: via web-configurator, CLI (Telnet, SSH, console (RS-232));
• configuration and setup (including remotely):
• web-configurator;
• CLI (Telnet, SSH, console (RS-232)).
• remote monitoring:
• web-configurator;
• SNMP.
- 1Not supported in this version.

2Optional.
FunctionalSIP/SIP-T/SIP-I:
• RFC 2976 SIP INFO (for DTMF transmission);
• RFC 3204 MIME Media Types for ISUP and QSIG (ISUP support);
• RFC 3261 SIP;
• RFC 3262 Reliability of Provisional Responses in SIP (PRACK);
• RFC 3263 Locating SIP servers for DNS;
• RFC 3264 SDP Offer/Answer Model;
• RFC 3265 SIP Notify;
• RFC 3311 SIP Update;
• RFC 3323 Privacy Header;
• RFC 3325 P-Asserted-Identity;
• RFC 3326 SIP Reason Header;
• RFC 3372 SIP for Telephones (SIP-T);
• RFC 3398 ISUP/SIP Mapping;
• RFC 3515 SIP REFER;
26
• RFC 3581 – An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing;
• RFC 3665 Basic Call Flow Examples;
• RFC 3666 SIP to PSTN Call Flows;
• RFC 3891 SIP Replaces Header;
• RFC 3892 SIP Referred-By Mechanism;
• RFC 4028 SIP Session Timer;
• RFC 4566 Session Description Protocol (SDP);
• RFC 5009 P-Header;
• RFC 5373 Requesting Answering Modes for the Session Initiation Protocol;
• RFC 5806 SIP Diversion Header;
• RFC 6432;
• Q1912.5 SIP-I;
• Interaction of SIP and SIP-T/SIP-I;
• SIP Enable/Disable 302 Responses;
• Delay offer;
• SIP OPTIONS Keep-Alive (SIP Busy Out);
• NAT support (comedia mode);
• SIP registrar (optional).
3.2.2 Typical applications

This manual offers several schemes for connecting the deviceSMG.
3.2.2.1 Conjugation of signaling and media streams of TDM and VoIP networks
In this configuration, the device provides the ability to connect up to16 threads E1 with various signaling
protocols (SSS-7, ISDN PRI/QSIG/CORNET, V5.2) and maintenance 768 uncompressed channels (codec
G.711), up to 432 compressed channels (G.729 A / 20-80) or 324 facsimile channelsT.38.
The device connects toIP networks via 10/100/1000BASE-T network interface over protocols
H.323/SIP/SIP-T/SIP-I.
* – not supported in the current version
Drawing1 – Conjugation of signaling and media streams of TDM and VoIP networks
27
On the image2 shows the scheme of interfacing TDM- and VoIP-networks on the example of the interaction of
DATS MS240 and ECSS-10 software switch.
* – not supported in the current version
Drawing2 – Conjugation of signaling and media streams of TDM and VoIP networks
3.2.2.2 Mini IP-PBX

In this configuration, the device provides the ability to register up to2000 for SMG-1016M and before3000
for SMG-2016 and SMG-3016 subscribers and interaction with the PSTN network through 16 E1 streams with
various signaling protocols (SSK-7, ISDN PRI/QSIG/CORNET, V5.2).
Drawing3 - Mini IP-PBX based on SMG-1016M
28
Drawing4 - Mini IP-PBX based on SMG-2016
Drawing5 - Mini IP-PBX based on SMG-3016
29
3.2.2.3 Subscriber remote according to protocol V5.2
Activation of additional options of the software moduleIP-PBX ECSS-10 allows you to organize
subscriber removal according to the protocolV5.2 and serve up to 2000 subscribers for SMG-1016M
and up to 3000 subscribers for SMG-2016 and SMG-3016 with support for the full set of VAS. IN
equipment of any manufacturer that supports the protocol can be used as a subscriber extension.V5.2
AN.
Drawing6 – V5.2 AN stem based on SMG-1016M
Drawing7 - V5.2 AN stem based on SMG-2016
thirty
Drawing8 – V5.2 AN stem based on SMG-3016
3.2.3 Structure and operation of the product
3.2.3.1 Structure of SMG-1016M

DeviceSMG-1016M has a sub-modular architecture and contains the following elements:
• controller, which includes:
• control processor;
• flash-memory - 64 MB;
• RAM - 512 MB.
• up to 4 E1 C4E1 stream submodules;
• up to 6 submodules IP SM-VP-M300;
• Ethernet switch (L2) for 3 10/100/1000BASE-T ports, 2 MiniGBIC (SFP) ports;
• switching matrix;
• PLL system.
31
Functional diagramSMG-1016M is shown in the figure below.
Drawing9 - Functional diagram SMG-1016M
3.2.3.2 Structure of the SMG-2016
DeviceSMG-2016 has a sub-modular architecture and contains the following elements:

• flash-memory - 1024 MB;
• RAM - 4096 MB.
• Ethernet switch (L2) for 4 ports 10/100/1000BASE-T, 2 combo ports MiniGBIC (SFP);
• PLL system.
32
Functional diagramSMG-2016 is shown in the figure below.
Drawing10 - Functional diagram of SMG-2016
3.2.3.3 Structure of SMG-3016

DeviceSMG-3016 has a sub-modular architecture and contains the following elements:
• RAM - 8192 MB.
• Ethernet switch (L2) for 4 ports 10/100/1000BASE-T, 2 combo ports MiniGBIC (SFP);
• Dedicated OOV port;
• PLL system.
33
Functional diagramSMG-3016 is shown in the figure below.
Drawing11 - Functional diagram of SMG-3016
3.2.3.4 How the SMG works

In the directionTDM-IP signal arriving at E1 streams is fed through the internal system trunk to audio codecs
of submodulesVoIP (6 lines x 128 TDM channels), encoded over one of the selected standards and in the
form of digital packages arrives inEthernet switch. Towards IP-TDM digital packages fromEthernet switch are
transmitted to the VoIP submodules, decoded and through the intrasystem highway are transferred to flows
E1.
External2-megabit E1 streams through matching transformers are fed to framers, with This separates the
synchronization signal from the stream and outputs it to the common synchronization line of the device.
Synchronization lines priority control occurs at the software level, according to a given algorithm.
The switching matrix is part of the intrasystem backbone and provides communication between
submodules E1 (C4E1) and VoIP submodules (SM-VP-M300).
-For workSMG requires at least one SM-VP submodule to be installed.
34
The structure of the device software is shown in the figure below.
Drawing12 - Structure of the SMG software
3.2.4 Main technical parameters

The main technical parameters of the terminal are given in the table below.
Table1 - Main technical parameters ProtocolsVoIP
Supported protocols SIP-T/SIP-I
SIP
SIP-Q
MGCP1
MEGACO1
SIGTRAN (M2UA, IUA)1
SIGTRAN (M3UA)1
H.323v2/v3/v42
T.38

2Optional.
35
Audio codecs
Codecs G.711 a-law (in text G.711A)
G.711 μ-law (in text G.711U)
G.729A/B
G.723.1 (6.3 Kbps; 5.3 Kbps)
G.726 (32 Kbps)
QuantityVoIP-channels supported by the submodule, depending on the type of codec
Codec/packetization time, ms Number of channels
G.711 (A/U) / 20-60 128
G.711 (A/U) / 10 112
G.729A/20-80 72
G.729A/10 62
G.723.1 (6.3 Kbps, 5.3 Kbps) 58
G.726/20 98
G.726/10 88
T.38 54
TDM channels per 1 submodule 128
Tripartite conferences on1 submodule 27
Electrical interface parametersethernet
Quantity SMG-1016M SMG-2016, SMG-3016

interfaces
3 4
Electric RJ-45
connector
Speed autodetect,10/100/1000 Mbps,

transmission
duplex
36
Support 10/100/1000BASE-T
standards
Optical interface parametersethernet
Quantity SMG-1016M SMG-2016, SMG-3016

interfaces
2 2 combo ports
Optic Mini Gbic (SFP):

connector
1) duplex, two-fiber with a wavelength of 1310 nm (Single-Mode), 1000BASE-LX
(connectorLC), range - up to 10 km, supply voltage - 3.3 V
2) duplex, single-fiber with wavelengths for receiving / transmitting 1310/1550 nm, 1000BASE-LX
(SC connector), range - up to 10 km, supply voltage - 3.3 V
Speed 1000 Mbps duplex

transmission
Support 1000BASE-X
standards
Console Options
Serial portRS-232
Transfer rate 115200 bps
Electrical parameters of signals As recommended by ITU-TV.28
Interface OptionsE1
Number of channels As recommendedITU-T G.703, G.704
Line data rate 2048 kbps
Line code HDB3, AMI
line output 3.0 V peak into 120 ohm load
2.37 V peak into 75 ohm load
(as recommended by CCITTG.703)
Line input From0 to -6 dB with respect to standard output pulse
37
Elastic buffer Capacity2 frames
Signaling protocols DSS1/EDSS1 (ISDN PRI Q.931), QSIG and CORNET for subscriber name transmission, OKS-
7, V5.2
Reservation
Reservationmaster-slave Only forSMG-2016 and SMG-3016
ReservationE1 Only forSMG-2016 and SMG-3016

Number of conference participants
Device Quantity
SMG-1016M Maximum number of participants for all conferences40. One conference can be no more40
participants.
Example:
1 conference for 40 participants;
10 conferences for 4 participants, etc.
SMG-2016 Maximum number of participants for all conferences160. In one conference maybe no
more40 participants.
Example:
4 conferences for 40 participants;
10 conferences with 16 participants, etc.
SMG-3016 Maximum number of participants for all conferences160. In one conference maybe no
more40 participants.
Example:
4 conferences for 40 participants;
10 conferences with 16 participants, etc.
Supported file systems for external media
Device Disk partitions File systems
SMG-1016M MBR USB flash - NTFS, FAT32, ext2, ext3, ext4
USB HDD - NTFS, ext2
GPT Not supported
38
Device Disk partitions File systems
SMG-2016 MBR HDD - NTFS, ext2
USB flash - NTFS, FAT32, ext2, ext3, ext4
GPT HDD - NTFS, ext2
SMG-3016 MBR HDD - NTFS, ext2
GPT HDD - NTFS, ext2
Supported interfaces
Device Interface
SMG-1016M/2016 SATA2
SMG-3016 SATA3
External Synchronization Signal Parameters
Number of sync inputs 2
cable type Balanced two-wire line (twisted pair)
Input impedance of synchronization receivers 120 ohm
Received signal parameters According to the recommendationITU-T G.703 Section 15: 2048
kHz syncronization interface (T12)
The shape and frequency of the received signal Meander2048 kHz
Common parameters
Working temperature range From0 to +40 °С
Relative Humidity Before80%
39
Noise level From44 to 60 dB
Meal Options – One DC or AC power supply;
– Two DC or AC power supplies.
Power supplies (PS) AC network DC network

current
Supply voltage 100-240V, 47-63Hz 36-72 V
IP designation RM160-220/12 RM100-48/12
IP power 160 W 100 W
Power consumption No more50 W
Dimensions (W× H × D) SMG-1016M SMG-2016, SMG-3016
430×45×260 mm 430×45×340 mm
Execution 19" constructive, standard size 1U
Weight device in full SMG-1016M SMG-2016, SMG-3016

configuration
3.2 kg 5.3 kg
BP 0.5 kg
Ventpanel 0.1 kg
SATA drive1 0.1 kg
Life time at least15 years
-1Only for SMG-2016 and SMG-3016.
40
3.2.5 Design
3.2.5.1 SMG-1016M
digital gatewaySMG-1016M is made in a metal case with the possibility of installation in 19″ frame size
1U.
The appearance of the front panel of the device is shown in the figure below.
Drawing13 - External view of the front panel SMG-1016M

The front panel of the device contains the following connectors, indicator lights, and controls, table2.
Table2 - Description of connectors, indicators and front panel controls
No. Element Description

front panel
1 USB USB port for connecting an external drive
2 F Function button
3 Console Console portRS-232 for local device control (wiring connectors are listed in
Annex A)
4 10/100/1000 0..2 3 RJ-45 10/100/1000BASE-T Ethernet interfaces
5 SFP0, SFP1 2 chassis for 1000BASE-X Gigabit uplink SFP optical modules for exit toIP network
6 E1 Line 0..7, E1 Line 2 CENC-36M connectors for connecting E1 streams (wiring of connectors is given in
8..15 Annex A)
7 SATA-0, SATA-1 Interface operation indicatorsSATA
8 Info1, Info2 Optical interface indicatorsSFP
9 Alarm Device failure indicator
10 Status Device operation indicator
41
The appearance of the rear panel of the device is shown in the figure below.
Drawing14 - External view of the rear panel of SMG-1016M
The table below lists the connectors located on the back of the Switch. Table3 - Description of the
rear panel connectors of the switch
No. Back panel element Description
1 Power connector Connector for connecting to a power

supply
2 Removable fans Removable hot-swappable ventilation modules
3 Device earth terminal

Ground terminal
3.2.5.2 SMG-2016
digital gatewaySMG-2016 is made in a metal case with the possibility of installation in a 19″ frame size1U.
Drawing15-Appearance of the front panel SMG-2016

No. Front panel element Description
1 ConnectorsSATA drives Connectors with sled for installationSATA drives
2 F Function button
42
3 Console Console port for local control of the device

(pinouts are given in Annex A)
5 0, 1 2 RJ-45 Ethernet 10/100/1000BASE-T Gigabit uplink

connectors for IP network access
6 2, 3 2 chassis for installing SFP modules 1000BASE-X

uplink interface for access to the IP network
2 x RJ-45 10/100/1000BASE-T Gigabit uplink interface

to accessIP network
7 E1 Line 0..15 16 RJ-48 connectors for connecting E1 streams

(connector pinouts are given inAnnex A)
8 Sync.0, Sync.1 2 RJ-45 connectors for connecting sources

external synchronization
Indicators
Status Device operation indicator
Sync.1 External synchronization interface

indicatorSync.2
Sync.0 External synchronization interface

indicatorSync.1
power Device power indicator
RPS Device auxiliary power indicator
FAN Fan indicator
USB Operation indicatorUSB
43
Drawing16-Rear view of the SMG-2016

1 Power modules Modules with a connector for connecting to a power

supply
2 Fan panels Removable hot-swappable ventilation modules

Ground terminal
3.2.5.3 SMG-3016
digital gatewaySMG-3016 is made in a metal case with the possibility of installation in a 19″ frame size1U.
Drawing17-Appearance of the front panel SMG-3016

No. Front panel element Description
1 ConnectorsSATA drives Connectors with sled for installationSATA drives
2 Console Console port for local control of the device (pinouts are given
inAnnex A)
44
3 OOB Dedicated portEthernet for configuration devices1. The

port is not capable of switching from other portsSMG
4 F Function button
6 12 2 x RJ-45 Ethernet 10/100/1000BASE-T Gigabit uplink to exit to

IP network
7 3, 4 2 chassis for installing 1000BASE-X uplink SFP modules

interface to accessIP network
2 x RJ-45 10/100/1000BASE-T Gigabit uplink interface

to accessIP network
8 E1 Line 0..15 16 RJ-48 connectors for connecting E1 streams (wiring

connectors are listed inAnnex A)
9 Sync.1, Sync.2 2 RJ-45 connectors for connecting external sources

synchronization
Indicators
Status Device operation indicator
Sync.1 External synchronization interface indicator Sync.2
Sync.0 External synchronization interface indicator Sync.1
power Device power indicator
RPS Device auxiliary power indicator
FAN Fan indicator
USB Operation indicatorUSB
45
Drawing18-Rear view of the SMG-3016

1 Power modules Modules with a connector for connecting to a power

supply
2 Fan panels Removable hot-swappable ventilation modules

Ground terminal
3.2.6 Light indication

The current status of the device is displayed using indicators located on the front panel.
3.2.6.1 Light indication of the device in operation
3.2.6.1.1 SMG-1016M
Light indication of the device in working condition is shown in the table below. Table8
- Light indication of the state of the device in working order
Indicator Indicator status Device Status
info1 Does not burn Missing linkSFP0
Lights up green LinkSFP0 in operation
info2 Does not burn Missing linkSFP1
Lights up green LinkSFP1 in action
Lights up red Device loading
46
Alarm Flashing red Critical device crash
Lights up red Non-critical device crash
Lights up yellow No accidents, there are non-critical remarks
Lights up green normal operation
Status Lights up green normal operation
Does not burn No power to device
3.2.6.1.2 SMG-2016
Light indication of the device in working condition is shown in the table below. Table9
- Light indication of the device in working order
Sync.0, Sync.1 Lit green External sync is active, source sync is being
captured
Lights up red Synchronization from an external source is active, an

external source is not connected (no frequency in
range)
Lights up in orange Synchronization from an external source is not

active, an external source is connected (there is a
frequency in the range)
Flashing orange Frequency output mode
47
Does not burn Synchronization from an external source is not

active, not configured for frequency output, external
source is not connected (no frequency in range)
power Lit green Powered by Power Supply #0
Lights up in orange Power unit #0 installed, no power to it served
RPS Lit green Power unit #1 is installed, it is served nutrition
Lights up red Power unit #1, power is not supplied to it
Does not burn Power unit #1 not installed
FAN Lit green All removable fan modules installed, all

fans running
Lights up in orange All removable fan modules installed,

non-working fans present
Lights up red One or both removable fan modules are not

installed
USB Lit green USB flash installed
Does not burn USB flash not installed
48
3.2.6.1.3 SMG-3016
Light indication of the device in working condition is shown in the table below. Table
10 - Light indication of the device in working order
Sync.1, Sync.2 Lit green External sync is active, source sync is being
captured
Lights up red Synchronization from an external source is active, an

external source is not connected (no frequency in
range)
Lights up in orange Synchronization from an external source is not

active, an external source is connected (there is a
frequency in the range)
Flashing orange Frequency output mode
Does not burn External clock source not connected
power Lit green Powered by Power Supply #1
Lights up in orange Power unit #1 installed, no power to it served
RPS Lit green Power unit #2 is installed, it is served nutrition
Lights up red Power unit #2, power is not supplied to it
Does not burn Power unit #2 not installed
49
FAN Lit green All removable fan modules installed, all

fans running
Lights up in orange All removable fan modules installed,

non-working fans present
Lights up red One or both removable fan modules are not

installed
USB Lit green USB flash installed
Does not burn USB flash not installed
3.2.6.2 Light indication of the state of flows E1
Light indication of the state of flows E11shown in the table below.
-1Only for SMG-2016 and SMG-3016.
Table11 - Indication of the state of flows E1
ConnectorsRJ-48 Indication (flickering period)
Status Red Yellow green
E1 disabled in gateway configuration Does not burn Does not burn Does not burn
Flow E emergency1 Flashing (200 Does not burn Does not burn
ms)
Signal Loss (LoS) Lit Does not burn Does not burn
AccidentAIS Lit Flashing (200ms) Does not burn
AccidentLOF Lit Lit Does not burn
AccidentLOMF Lit Lit Does not burn
Normal operation of thread E1 Does not burn Does not burn Lit
Trouble at the far end (RAI) Does not burn Flashing (200ms) Flashing (200ms)
50
ConnectorsRJ-48 Indication (flickering period)
Status Red Yellow green
Stream E1 in operation, there are slippages on flow ( Does not burn Flashing (300ms) Flashing (1500ms)
SLIP)
Stream E is being tested1 Flashing (200 Flashing (200ms) Flashing (200ms)

ms)
3.2.6.3 Light indication of Ethernet 1000/100 interfaces

Interface statusEthernet is indicated by the LED indicators built into the 1000/100 connector and is shown
in the table below.
Table12 - Light indication of Ethernet 1000/100 interfaces
Device Status Indicator/Status
Yellow indicator1000/100 Green indicator1000/100
The port is in operation.1000BASE-T Solid on Solid on
no data transfer
The port is in operation.1000BASE-T Solid on Flashing
there is a data transfer
The port is in operation.10/100BASE-TX Does not burn Solid on
no data transfer
The port is in operation.10/100BASE-TX Does not burn Flashing
there is a data transfer
51
3.2.6.4 Light indication during boot and reset to factory settings
3.2.6.4.1 SMG-1016M
Light indication during loading and resetting to factory settings is shown in the table below. Table
13 - Light indication when loading and resetting to factory settings
No. Indication How to reset to default settings
info1 info1 Alarm Status (device included)
1 Yellow Yellow Yellow Yellow Press and hold the "F" in flow1 second
before the appearance of this
combinations, then release the button.
Through3 seconds will restart devices.
2 Green Red Yellow Red Starting a factory reset. This combination

of LEDs will light up when the device
boots up.
3 Yellow Yellow Yellow Yellow At this stage, the operability of the LEDs is
checked, all LEDs should light up yellow,
includingSATA-0 and SATA-1.
4 Does not burn Does not burn Green Green At this stage, the gateway operating
system is loaded. To change the network
settings and return the device
configuration to the factory settings, after
the combination appears, press and hold
the button "F" for 40-45 seconds (during
holding the button, the combination will
briefly light up2 without paying attention
to her attention, continue to hold until the
combination appears4).
5 Yellow Yellow Yellow Yellow Release the button when the combination
appears.F".
After a while, the following message will be

displayed in the console:
<<<BOOTING IN SAFE-MODE.RESTORING
DEFAULT PARAMETERS>>>
Factory reset completed.
52
-It is not recommended to hold down the "F" while resetting the device - this will result in complete stop
of the device. Resuming work will be possible only after a power reset.
-It is possible to reset to factory settings on the device being turned on. In
this case, item1 must be skipped.
3.2.6.4.2 SMG-2016, SMG-3016

Light indication during loading and resetting to factory settings is shown in the table below. Table
14 - Light indication when loading and resetting to factory settings
No. Indication How to reset to default settings
Alarm Status Sync.0 Sync.1 (device included)
1 Yellow Yellow Yellow Yellow Press and hold the "F" in flow1 second
before the appearance of this
combinations. Through3 seconds will start
device reboot.
2 Yellow Red Yellow Yellow Starting a factory reset. This combination

of LEDs will light up when the device
boots up.
3 Green Green - - At this stage, the gateway operating

system is loaded. To change the network
settings and return the device
configuration to the factory settings, after
the combination appears, press and hold
the button "F" for 40-45 sec.
4 Yellow Yellow - - Release the button when the combination

appears.F".
After a while, the following message will be

displayed in the console:
<<<BOOTING IN SAFE-MODE.RESTORING
DEFAULT PARAMETERS>>>
Factory reset completed.
-The state of the diodesPOWER, RPS, FAN, USB can be neglected during reset. It is
possible to reset to factory settings on the device being turned on. In this
case, item1 must be skipped.
53
3.2.6.5 Light indication of alarms

The table below provides a detailed description of the alarms displayed in the status of the indicator.alarm.
- Save indicationCDR files.

IfFTP server is unavailable, CDR records are stored in RAM devices for storageCDR files allocated 30
MB. When the memory is full in certain borders, an alarm will be triggered.
Table15 - Alarm indication
Indicator statusAlarm Accident level Description of the accident
Flashing red Critical (critical) Configuration error
A losssip module
Accident of a group of lines OKS-7 (with set

flagAlarm indication on the menu
"Routing / SS Line Groups")
Thread crash (when the flag is set Indication

Alarmon the menu"Flows E1/ Physical
parameters»)
FTP server unavailable, operational

storage memoryCDR files filled from
above50%
Lights up red Non-critical (errors) OKS link failure7 (when installed flagAlarm
indicationon the menu "Routing / SS Line
Groups»)
A lossVoIP Submodule (MSP)
Synchronization failure (operating in free

run)

above15%
Lights up yellow Warnings (warning) Remote flow crash
Synchronization from a lower priority

source (higher priority
not available)
54
Indicator statusAlarm Accident level Description of the accident

above5%
Alarm threshold exceededCPS on one

of the trunk groups
duplication errorINVITE from

equipment UOVEOS
3.2.7 Using the function key "F"

Function button "F" is used to reboot the device, restore the factory configuration, as well as for
password recovery.
To reset to default settings with the device turned on, seeLight indication during boot and reset to factory
settings:tables13,14.
After restoring the factory configuration, the device can be accessed byIP address 192.168.1.2 (mask
255.255.255.0):
• via telnet or console: loginadmin, passwordrootpasswd;
• via the web configurator: loginadmin, passwordrootpasswd.
Then you can save the factory configuration, reset the password or reboot the device.
55
3.2.8 Saving the factory configuration To save

the factory configuration:
• reset the device to factory settings (sectionLight indication when loading and reset to factory settings);
• connect via Telnet or Сonsole using loginadmin, passwordrootpasswd;

• enter a commandsh(device will exit CLI mode to SHELL mode);
• enter a commandsave;
• reboot the device with the commandreboot.
The gateway will boot with the factory configuration.
*********************************************
* Welcome to SMG-1016M *
*********************************************
smg login: admin

Password: rootpasswd
********************************************
********************************************
Welcome! It is Wed Mar11 08:45:20NOVT2015 SMG>sh
/home/admin#save
tar: removing leading'/'from member names
**********
**********
* * * Saved successful
New image1
Restored successful
/home/admin #reboot
3.2.9 Password recovery
3.2.9.1 CLI password recovery To

recover your password:
• connect via Telnet, SSH or Console;

• enter a commandsh(device will exit cli mode to shell mode);
• enter a commandrestore(the current configuration will be restored);
• enter a commandpasswd(the device will require you to enter a new password and confirm it);
• enter a commandsave;
The gateway will boot up with the current configuration and the new password.
In the event of a reboot without performing any action, the device will restore the current configuration
without resetting the password. The gateway will boot up with the current configuration and the old
password.
56
*********************************************
*********************************************
smg login: admin

********************************************
********************************************
Welcome! It is Fri Jul2 12:57:56UTC2010 SMG>sh
/home/admin # restore
new image1
Restored successful
/home/admin # passwd admin Changing
passwordforadmin New password:
1q2w3e4r5t6y Retype password:
1q2w3e4r5t6y Passwordforadmin changed by
root /home/admin # save

**********
**********
New image0
Restored successful
# reboot
3.2.9.2 Web password recovery To

recover your password:
• connect via Telnet, SSH or Console;

• enter a commandsh(device will exit cli mode to shell mode);
• enter a commandrestore(the current configuration will be restored);
• connect to the device's web interface at 192.168.1.2;
• go to the "Users: Management" section;
• change the password for the admin user;
• in the console enter the commandsave;
-Save configuration fromweb when recovering a password is not recommended, because it may result
in the loss of the saved gateway configuration. Use commandsave from shell mode.
The gateway will boot up with the current configuration and the new password.
In the event of a reboot without performing any action, the device will restore the current configuration
without resetting the password. The gateway will boot up with the current configuration and the old
password.
57
*********************************************
*********************************************
smg login: admin

********************************************
********************************************
Welcome! It is Fri Jul2 12:57:56UTC2010 SMG>sh
/home/admin # restore
new image1
Restored successful
At this stage, the password is changed fromweb.
/home/admin#save
**********
**********
New image0
Restored successful
# reboot
3.2.10 Scope of delivery
3.2.10.1 SMG-1016M
In the basic delivery set of the deviceSMG-1016M includes:
• Digital gateway SMG-1016M;
• CENC-36M connector – 2 pcs. (if there is no UTP CAT5E cable 18 pairs in the order);
• Latches for CENC-36M connectors – 4 pcs. (if there is no UTP CAT5E cable 18 pairs in the order);
• Connecting cable RS-232 DB9(F) – DB9(F);
• Mounting kit in 19″ rack;
• Memo on documentation;
• Passport;
• Declaration of Conformity;
• Operation manual on CD (optional).
58
3.2.10.2 SMG-2016
In the basic delivery set of the deviceSMG-2016 includes:
• Digital Gateway SMG-2016;
• Passport;
3.2.10.3 SMG-3016
In the basic delivery set of the deviceSMG-3016 includes:
• Digital gateway SMG-3016;
• Passport;
3.2.11 Safety instructions
3.2.11.1 General information
When working with the equipment, it is necessary to comply with the requirements of the “Safety Rules for the
Operation of Consumer Electrical Installations”.
-It is forbidden to work with the equipment to persons who are not allowed to work in accordance
with safety requirements in the prescribed manner.
The operation of the device must be carried out by engineering and technical personnel who have
undergone special training.
Connect only suitable auxiliary equipment to the device. The Digital Gateway is designed for
24/7 operation under the following conditions:
• Ambient temperature from 0 to +40 С̊;
• Relative air humidity up to 80% at a temperature of 25 С̊;
• Atmospheric pressure from 6.0×10*4 to 10.7×10*4 Pa (from 450 to 800 mmHg).
Do not expose the device to mechanical shocks and vibrations, as well as smoke, dust, water, chemicals.
To prevent overheating of the device components and malfunction of the device, do not block the
ventilation holes with foreign objects and do not place objects on the surface of the equipment.
3.2.11.2 Electrical safety requirements

Before connecting the device to a power source, you must first ground the equipment case using the ground
terminal. The ground wire attachment must be securely fixed to the ground terminal. The resistance
between the protective earth terminal and the earth bus must not exceed0.1 ohm.
59
Before connecting measuring instruments and a computer to the device, they must first be grounded.
The potential difference between the cases of equipment and measuring instruments should not exceed1
V.
Before turning on the device, make sure that the cables are intact and securely fastened to the connectors.
When installing or removing the cover, make sure that the device is powered off.
Installation and removal of submodules should be carried out only with the power turned off, following the
instructions in the sectionInstalling Power Modules.
3.2.11.3 Precautions in the presence of static electricity

To avoid electrostatic damage, it is strongly recommended to wear a special belt, shoes or wrist strap to
prevent the accumulation of static electricity (in the case of a wrist strap, make sure that it fits snugly against
the skin) and to ground the cord before working on the equipment.
3.2.11.4 Power requirements
3.2.11.4.1 Requirements for the type of power supply

The power supply must be from a DC source with grounded positive potential with voltage48 V or AC remote
power supply voltage up to220 V.
3.2.11.4.2 Requirements for allowable changes in DC power supply voltage Power supply voltage changes
with voltage48 V is allowed within the range of 40.5 to 57 V.
In the event of a decrease in the voltage of the power supply below the permissible limits and with the
subsequent restoration of the voltage, the characteristics of the communication means are restored
automatically.
60
3.2.11.4.3 Permissible disturbance requirements for DC power supply

The equipment must operate normally with power supply disturbances not exceeding those given
in the table below.
Table16 - Permissible interference requirements for DC power supply
Type of interference Meaning
Permissible voltage deviation from the nominal value,%:
duration50ms - 20
duration5 ms 40
Voltage ripple of harmonic components, mVeff
up to300 Hz 50
in the range above300 Hz to 150 kHz 7
3.2.11.4.4 Requirements for interference from equipment in the power supply circuit
Interference voltages generated by equipment in the power supply circuit must not exceed the
values given in the table below.
Table17 - Requirements for interference caused by equipment in the power supply circuit
Type of interference Meaning
Total interference in the range from25 Hz to 150 Hz, mVeff 50
Selective interference in the range from300 Hz to 150 kHz 7
Weighted (psophometric) noise value, mVpsof 2
3.2.11.4.5 AC power supply requirements AC power supply

parameters:
• Maximum allowable voltage - no more than 220 V;
• The AC power supply is equipped with a residual current device (RCD);
• Insulation strength of AC power supply circuits against chassis withstands (under normal
conditions) at least1000 V peak.
61
3.2.12 Installing the SMG
Before installing and switching on the device, it is necessary to check it for visible mechanical damage. In
case of damage, stop the installation of the device, draw up an appropriate report and contact the supplier.
The product must be installed in rooms with limited access - only for service personnel.
If the device has been at a low temperature for a long time, it should be kept at room temperature
for two hours before starting work. After a long stay of the device in conditions of high humidity,
before turning it on, keep it under normal conditions for at least12 hours.
Mount device. The device can be attached to19" support racks with mounting kit, or installed on a
horizontal perforated shelf.
After installing the device, it is required to ground its case. This must be done before the power supply is
connected to the device. Grounding should be carried out with an insulated stranded wire. The rules for the
grounding device and the cross-section of the ground wire must comply with the requirements of the PUE.
The ground terminal is located in the lower right corner of the rear panel,drawing14, drawing16,figure 18.
3.2.12.1 Switching order

1. Connect digital streams, optical and electrical Ethernet cables to the appropriate gateway
connectors.
-To protect digital streams from extraneous voltages, the linear side of the cross should be
equipped with comprehensive protection devices. Firm protection plugs are recommended
KRONE “Com Protect 2/1 CP HGB 180 A1”.
2. Connect the power cable to the device. To connect to a DC network, use

wire with a cross section of at least1 mm2.
3. If you intend to connect a computer to the SMG console port, connect the console portSMG with PC
COM port, while the PC must be turned off and grounded at one point with digital gateway.
4. Make sure that the cables are intact and securely fastened to the connectors.
5. Turn on the power of the device and make sure that there are no accidents according to the status of the indicators
on front panel.
62
3.2.12.2 Fixing brackets

The device is supplied with brackets for rack mounting and screws for attaching the brackets to the
device body.
Drawing19-Mounting brackets for SMG-1016M (top left), SMG-2016 (top right) and
SMG-3016 (bottom)
To install brackets:
1. Align the four screw holes on the bracket with the same holes on the side device panel,drawing19.
2. Use a screwdriver to screw the bracket to the chassis.

Repeat steps1, 2 for the second bracket.
3.2.12.3 Installing the device in a rack To

install the device in a rack:
1. Place the device on the vertical rails of the rack.
2. Align the holes on the brackets with the holes on the rack rails. Use holes in the rails at the same
level on both sides of the rack, so that the device is placed horizontally.
3. Use a screwdriver to attach the device to the rack with screws.

4. To dismantle the device, disconnect the connected cables and screws securing the brackets to rack.
Remove the device from the rack.
63
Drawing20 - Installing the device in the SMG-1016M rack (left), SMG-2016 (right) and SMG-3016 (bottom)
3.2.12.4 Installing power modules

The device can operate with one or two power modules. Installing a second power module is necessary if
the device is used in environments that require increased reliability.
Places for installing power modules are equivalent from an electrical point of view. From the point of view of using
the device, the power module located closer to the edge is considered the main one, closer to the center - the
backup one. Power modules can be installed and removed without shutting down the device. When you install or
remove an optional power module, the device continues to operate without restarting.
The device has2 x 3.15A power supply fuses. replacement of fuses is not possible and is carried out only by
qualified specialists at the service center of the manufacturer.
Drawing21 - Installing Power Modules
64
3.2.12.5 Opening the case

Turn off the power firstSMG, disconnect all cables and, if required, remove the device from the rack
(see sectionInstalling the device in a rack).
Drawing22 – SMG-1016M Case Opening Procedure
Drawing23 – SMG-2016 Case Opening Procedure
65
Translated from Russian to English - www.onlinedoctranslator.com
Drawing24 – SMG-3016 Case Opening Procedure

1. Using a screwdriver, detach the brackets from the device body.
2.Only for SMG-1016Munscrew the fixing screws of the front panel, then pull it towards you until it
separates from the top and side panels (drawing22).
3. Unscrew the screws on the top panel of the device.
4. Remove the top panel (cover) of the device by pulling it up.
When assembling the device into a housing, perform the above steps in reverse order.
Drawing25 - Types of screws for assembling SMG
The figure above shows the types of screws used to assemble the device into the case:
• Mounting brackets for rack mounting.
• Fastening of body parts.
• Fastening boards, ventilation blocks, plugs, guides.
• Fan fastening screw.
• Ground screw.
66
-When assembling the device, do not use the wrong type of screws for the specified operations.
Changing the screw type may damage the device.
Drawing26 - Assembling the SMG into the body
-When assembling the deviceSMG in the place indicated in the figure above, you need to install a
screw, laid down during production. Changing the screw type may damage the device.
3.2.12.6 Installing submodules

The device has a modular design that can be installed up to6 IP submodules SM-VP-M300 (Submodule
MSP)and up to 4 E1 C4E1 stream submodules(Submodule C4E1)in the positions shown on drawings below.
The device requires at least one module to operate.SM-VP-M300. Required quantity submodules for the full
operation of the device is calculated based on the required number of threadsE1, active VoIP channels
(taking into account the codecs used) and the presence of SORM.
67
Drawing27 - Location of submodules in SMG-1016M
Drawing28 - Location of submodules in SMG-2016
68
Drawing29 - Location of submodules in SMG-3016

Order of installation of submodulesSMGs:
1. Check the presence of mains power on the device.

2. If voltage is present, turn off the power.
3. If necessary, remove the device from the rack (see sectionInstalling the device in a rack).
4. Open the case of the device (see sectionCase opening).
5. In some hardware revisions, submodules are covered with plates of a special shape, preventing
submodules from falling out during transportation (see sectionCase opening, drawings22,23,24). In
this case, the plate must be removed.
6. Install the module in a free position (see figures27,28,29).
6.1 Install washers on the board, install brass racks on them.
6.2 Install the submodule on the racks, making sure that the connectors are tightly connected to the submodule.
6.3 Fix the submodule with screws.
Drawing30 - Installing the submodule on the board
6.4 Install the submodule on the board, making sure that the connectors are tightly connected to the submodule.
69
6.5 Fix the submodule with a sealant to fix the submodule on the board.
Drawing31 - Installing the submodule on the board
7. For the positions of C4E1 submodules, the following correspondence is established with the numbers of E1 streams: For
SMG-1016M
• Submodule C4E10– Stream E10-3;

• Submodule C4E13– Stream E112-15.
ForSMG-2016
• Submodule C4E14– Stream E112-15.
ForSMG-3016
• Submodule C4E1 1 - Stream E11-4;
• Submodule C4E1 4 - Stream E113-16.
8. Replace the limit plates over the submodules (if any), assemble the housing, install the device in a rack
(if required).
70
3.2.12.7 Installation of ventilation units

The design of the device provides for the possibility of replacing ventilation units without turning off the
power.
Drawing32-SMG-1016M ventilation unit. Housing mount
Drawing33-SMG-2016 ventilation unit. Housing mount
Drawing34 - Ventilation unit SMG-2016 rev. B. Chassis mount
71
Drawing35 - SMG-3016 ventilation unit. Housing mount

To remove a block:
1. Using a screwdriver, remove the right screw securing the ventilation unit on the rear panel.
2. Gently pull the unit towards you until it is removed from the housing.
3. Disconnect the block contacts from the connector in the device,figure 36.
Drawing36-Fan connector
To install the block you need:
1. Connect the contacts of the block to the connector in the device.
2. Insert the block into the device case.
3. Screw the ventilation unit to the rear panel.
72
3.2.12.8 Installing SSDs for SMG-1016M
Drawing37 - Installing the SSD
Drawing38 - Mounting the SSD

3. If necessary, remove the device from the rack (see chapter
Installing the device in a rack).
5. If there is no mounting pin on the device board (see drawing37),
you must use a detachable stand:
a. attach the stand-fixer to the SSD drive;
b. remove the top protective layer from the adhesive
surface fixing racks.
6. Install the drive in a free position - total available2 positions (see
figure 37), and if on the board there is a mounting pin, secure
with a screw,drawing38.
When removedSSD drive, perform the above steps in reverse order.
73
3.2.12.9 Installing SATA drives for SMG-2016, SMG-3016

When ordering with devices can be additionally suppliedSATA drives. Connection slot drives are designed
for form factor drives2.5" thick up to 12.5mm".
During installationSATA drives are required:
1. Remove the guide slides from the device housing (drawing15,figure 17element 1), for to do this, press the
button on the right until the ejector handle moves away, then pull the handle towards you until the slide is
removed from the housing;
2. Remove the set of fasteners located under the ejector handle,figure 39;
3. Fix the disc in the guide rail tray,figure 40;
4. Insert the sled with the installed SATA drive back into the slot and press the handle
ejector to a characteristic click,drawing41.
When removedSATA disk, perform the above steps in reverse order. Installation and removalSATA
drives can be produced when the device is powered on.
Drawing39-Location of fastener kit when shipped
Drawing40-Attaching a SATA drive to the slide rail tray
74
Drawing41 - Mounting the SATA disk in the device case
3.2.12.10 Replacing the real time clock battery

INRTC (an electronic circuit designed for autonomous accounting of chronometric data (current time, date,
day of the week, etc.)) a power element (battery) is installed on the device board, which has the characteristics
shown in the table below.
Table18 - Characteristics of the battery for RTC
Battery Type Lithium
Size CR2032 (possible to install CR2024)
Voltage 3V
Capacity 225 mA
Diameter 20 mm
Thickness 3.2 mm
Life time 5 years
Storage conditions from -20 to +35 °С
75
Drawing42-RTC battery position for SMG-1016M
Drawing43 - RTC battery position for SMG-2016
Drawing44 - RTC battery position for SMG-3016
76
If the battery has expired, for the correct and uninterrupted operation of the equipment, it is necessary
to replace it with a new one by following these steps:
3. If necessary, remove the device from the rack (see sectionInstalling the device in a rack).
5. Remove the used battery (figures42,43,44) and install a new one in a similar position.
When assembling the device into a housing, perform the above steps in reverse order.
-With sync disabledNTP after battery replacement RTC needs to be reset the system date and
time on the device.
-Used batteries are subject to special disposal.
3.3 General recommendations when working with the gateway
The easiest way to configure and monitor a device isweb configurator, therefore, it is recommended to
use it for these purposes.
To avoid unauthorized access to the device, we recommend changing the password to access viaTelnet and
Console (default useradmin, passwordrootpasswd) and change the password for administrator to access
viaweb configurator. Setting a password for access via Telnet and Console is described in the section
Changing the password for accessing the device via CLI. Setting a password for access viaweb configurator
is described in the sectionControl Menu. It is recommended to write down and save the set passwords in a
safe place, inaccessible to intruders.
To avoid losing device configuration data, for example, after a factory reset, we recommend that you save
a backup copy of the configuration on your computer each time you make significant changes to it.
-To ensure the safety of the device, you must follow the recommendations described in Appendix M.
Safety Recommendations.
77
4 Device configuration
There are four ways to connect to the device:web configurator, using the Telnet protocol, SSH or by cable via
the RS-232 connector (when accessing via RS-232, SSH or Telnet, the CLI is used).
-All settings are applied without restarting the gateway. To save the changed configuration to
non-volatile memory, use the menu "Tools/Save configuration toFlash" in the web
configurator or the copy running to startup command in the CLI.
4.1 Configuring the SMG via the web configurator
-Interface appearance may vary.
In order to configure the device, you need to connect to it viaweb- browser (hypertext document viewer), for
example:Google, Firefox, Internet Explorer, etc. Enter the IP address of the device in the browser line.
-FactorySMG device IP address:192.168.1.2,netmask:255.255.255.0.
After enteringIP address, the device will ask for a username and password. Here you can also select the
language to be used in the interface.
-On first start, username:admin, password:rootpasswd.
78
After gaining access tothe web configurator will open the page "System Information".
The figure below shows the navigation elementsweb configurator.
79
Drawing45 - Web configurator navigation elements

The user interface window is divided into several areas:
Navigation tree serves to control the settings field. The navigation tree
hierarchically displays the control sections and the menus
contained in them.
Settings field based on the user's choice. It is intended for viewing device settings
and entering configuration data.
Control Panel panel for managing the settings field and the state of the device
software.
Control menu drop-down menus of the control panel of the settings field and the
state of the device software.
Alarm signaling serves to display the current priority alarm, is also a link for
working with the alarm log.
Authorization link to work with access passwords to the device viaweb-

configurator.
80
Interface language buttons to switch the interface language.
Control icons controls for working with objects of the settings field duplicate
the "Objects" menu on the control panel:
– Add object;
– Edit object;
– Delete object;
- View object.
Control buttons controls for working with the settings field.
In order to avoid unauthorized access during further work with the device, it is recommended to change
the password (sectionControl Menu).
-
Button ("Hint") next to the edit element allows you to get explanations on
this parameter.
81
4.1.1 System parameters

System Options → Basic Settings
• Device name -device name. This name is used in the web header. device configurator;
• Backup Unsaved Changes– if the option is enabled, the device every 60 seconds creates a backup copy
of unsaved configuration changes with the option to restore them later. For example, the device had
unsaved changes and a power restart occurred. If the option was enabled after the device was started,
a window with a suggestion to restore unsaved changes will appear in the web interface;
• Path to the disk for storing traces -device has the ability to save debug information (traces) in RAM (
RAM) or on the installed drive:
• default-debugging information is stored in RAM;

• /mnt/sdx-path to the local storage, the setting is displayed when installed drive. When you
select a drive, a directory will be created on it.logs, which will contain trace files are stored.
• Number of active dial plans –number of simultaneously active plans numbering, total can be
configured up to16 (up to 255 on SMG-2016 and SMG-3016 if available) VAS licenses) independent
numbering plans with the ability to add subscribers to each plan and build your own call routing table;
• Delayed dialing plan application −if flag is set, SMG will not apply changes to the numbering plan
until special confirmation. Setting this option helps when working with large dial plans, avoiding their
lengthy processing after each setting change;
82
• Emergency logging device– selection of a drive for recording critical emergency messages to non-
volatile memory. This option may be necessary when determining the reasons for a restart or
equipment failure;
• /mnt/sdx-select the path to the local drive.When this option is enabled on drive, a file is
createdalarm.txt, which contains information about accidents.
File examplealarm.txt
1. 24/09/13 20:03:22. software started.
2. 24/09/13 20:03:22. state ALARM. Sync from local source, but sync source table not empty
3. 24/09/13 20:03:22. state OK. PowerModule#1. Unit ok! or absent
4. 24/09/13 20:03:31. state OK. MSP-module lost: 1
File Format Description:
0, 1, 2… – sequence number of the event;
24/09/13 – date of occurrence of the event;
20:03:22 – time of occurrence of the event;
ALARM/OK – current state of the event (OK – alarm is normalized, ALARM – alarm is active). Table19 —
Examples of output messages about accidents
Emergency message Decryption
Configuration not read Configuration file error
No connection withSIP module Failure of the software module responsible for the operation
VoIP
Group of lines OKS-7 (linkset) not in operation Accident of a group of lines OKS-7
E flow failure1 E flow failure1
OKS link failure7 Alarm channel OKS-7
Synchronization from a lower priority source Loss of main clock source, current source has lower
priority
Remote E flow alarm1 Remote E flow alarm1
Failed to sendCDR files to remote storage File upload problemCDR to remote storage
Launching the device software Launching the device software
• Using SM-VP Submodules –selection of SM-VP submodules that will be in work.
83
Alarm indication
• Fan operation -when the flag is set in case of failure of the cooling fans, there will be an indication
of an accident (the indicator on the device will light upALARM, accident will be entered in the
accident log);
• Processor load -if the flag is set in case of high load of the manager processor, an alarm will be
indicated (the indicator on the device will light upALARM, the accident will entered in the accident log);
• RAM usage -if the flag is set in case of employment more than 75% of the total amount of RAM, there
will be an indication of an accident (the indicator on the device will light upALARM, the alarm will be
entered into the alarm log);
• Filling external drives -with the flag set, if one of the external drives are filled with more than80% if the
external storage does not exceed 5 GB (or left less1024 MB free space if external storage is more than 5
GB), there will be an indication of an accident (the indicator on the device will light upALARM, the
accident will entered in the accident log);
• Backup device failures– if the flag is set, the main device will receive transmitted accidents of the
backup device;
• Lack of communication with the slave– when the flag is set, in case of lack of communication with the slave on
the global or local link, there will be an indication of an accident (the indicator on the device will light upALARM,
the alarm will be entered into the alarm log.
Automatic configuration
System parameters → Automatic configuration
SMG can automatically receive configuration and files with software versions from the server
autoconfiguration (hereinafter referred to as the "server") with a specified period.
84
After downloading the configurationThe SMG will wait for all active calls to end and then apply the new
configuration. Or the configuration will be applied along with the new software before rebooting.
The file with the description of software versions contains information about the software available on the server -
versions and file names. You can also set the time allowed for the update. The file format should be the following:
<software version number>;<software file name>;<allowed update time, hour>

• Software version number-is set completely to the assembly version;
• The software file name must have the .bin extension;
• The allowed update time may not be available. In this case, the SMG will be updated in soon, when
there are no active calls. If a time interval is specified, thenSMG will be updated only at the specified
time interval.
An example of a software version description file:
3.7.0.1944;smg1016m_firmware_3.7.0.1944.bin
3.8.0.2050;smg1016m_firmware_3.8.0.2050.bin;9-13
• Enable auto-update -enable automatic configuration and software updates;
• Source -server information source selection:
• static-information about the server is entered and stored on the SMG in the appropriate field;
• DHCP(interface name)-server information will be retrieved on the selected protocol interface
DHCP option 66, version filename and filename information configuration will be obtained from
the option67.
• Protocol -choosing a protocol for connecting to the server;
• Authentication -use authentication to access the server (for FTP, HTTP, HTTPS protocols);
• Name -name (login) to access the server;

• Password -password to access the server;
• Server -The IP address or domain name of the server. Used when the source is Static;
• Update configuration -allows updating the configuration from the server;
• Configuration file name -configuration file name. The name must be with .cfg extension and be no
longer than64 characters;
• Configuration update period, m-frequency of checking the server for availability
configuration;
• Update software -allows software updates from the server;
• Software version file name -file name with software versions. The name must be with .manifest extension and be
no longer than64 characters;
• Software update period, m –the frequency of checking the server for new software.
85
Uploading configurations
System parameters → Upload configuration
SMG can automatically upload the configuration to an external FTP/TFTP/SCP server each time it is saving to
non-volatile memory.
• Enable autoload– enables configuration upload function;
• Protocol– select the protocol by which the upload will be performed. FTP, TFTP, SCP supported;
• Server– IP address of the server to which the upload will be performed;

• Port– port of the server to which the upload will be performed;
• The path to the file– directory on the server where the configuration will be saved;
• Name– name for authentication when using the FTP protocol;
• Password -password for authentication when using the FTP protocol.
86
PPV settings
System parameters → KPV settings
The ringtone settings allow you to replace the standard call ringing sound with any other, similar to the operation of the
"Change dial tone" service.
• Path to disk -specifies the path to the external drive where the audio files will be stored;
• Folder name— indicates the name of the folder on the external drive where the audio files are stored;
• File name— selection of the desired file to be played;
• Working mode:
• CPV- standard ringback control sound;
• Audio file— a special file selected as the audio for the CPV.
The "Browse" submenu allows you to load, select, delete the desired audio files as CPV:
System parameters → Payload settings → Overview
• Download- downloading an audio file of a certain format;
-Sound files must be in the formatWAV, G.711a codec, 8 bit, 8 kHz, mono.
• Apply- select the desired audio file;

• Cancel— exit from the "Overview" submenu.
When setting the callback from the "System parameters" item, the audio file is applied to all subscribers and
trunk groups of the system.
There are several levels of settings, each next "more detailed" level takes precedence over the
previous one:
87
1. KPV system settings
2. CPB settings for Trunk groups and PBX profiles
3. Callback settings for subscribers
4.1.2 Monitoring
Monitoring → Telemetry
4.1.2.1 Telemetry
The section displays information about the readings of telemetry system sensors installed on the device,
as well as information about installed power supplies and fans.
Temperature sensors
ForSMG-1016M:
• Sensor #0- readings of the temperature sensor located on the central processor;
• Sensor #1- readings of the temperature sensor located on the RAM module.
88
ForSMG-2016, SMG-3016:
• Sensor #0- readings of the temperature sensor located on the central processor.
Power supplies
• Power Supply #0 -the state of the power supply in the zero position;
• Power Supply #1 -state of the power supply in the first position.
Possible states of power supplies:
• Installed- the power supply is installed.
• Not installed– the power supply is not installed.
• Works- Supply voltage is supplied to the power supply.
• Does not work– The power supply is not supplied with power.
Fans1
• Fan #N –information about the state of the fan N and its rotation speed (for example, 9600 rpm);
-1In deviceSMG-1016M has 2 fans, SMG-2016, SMG-3016 have 4 fans.
Voltage1
• Internal voltage (+12V)– information about the state of the 12 V voltage sensor.
current voltage2
• + 12.0 V– information about the state of the voltage sensor 12 V;
• + 3.3 V– information about the state of the voltage sensor 3.3 V;
• + 1.8V– information about the state of the voltage sensor 1.8 V;
• CPU– information about the state of the CPU supply voltage;
• CPU Vcore– information about the state of the CPU core supply voltage;
• Battery RTC– information about the battery voltage status of the real time clock.
Current CPU load:
• USR-the percentage of CPU time used by user programs;
• sys-the percentage of CPU time used by kernel processes;
• NIC-the percentage of CPU time used by programs with a changed priority;
• IDLE-percentage of unused processor resources;
• IO-percentage of CPU time spent on I/O operations;
• IRQ-percentage of CPU time spent processing hardware interrupts;
• SIRQ-percentage of CPU time spent handling software interrupts.
- 1Only for SMG-1016M.

2Only for SMG-2016 and SMG-3016.
89
4.1.2.2 Monitoring E1 flows

The section displays information about installed chips on submodules C4E1, as well as monitoring and flow
statistics E1.
Monitoring → Flow monitoringE1
For E chips1 in the table indicates the number of the position in which it is installed (see section
Installation submodules), chip name and ID.
Stream options:
• State -stream status:
• WORK-flow at work;
• LOS-signal loss;
• OFF-the stream is disabled in the configuration;
• NONE-submodule not installed;
• AIS-alarm indication signal (signal containing all units);
• LOMF-signal indicating the emergency state of the multicycle;
• RAI-remote alarm indication;
• TEST-flow test indication (PRBS test, loopback local and remote).
• D channel state -status of D-channel, service control channel:
• up-D-channel in operation;
• down-D-the channel is not in operation;
• no-there is no control channel on the stream;
• off-the alarm is off on the stream;
• KPD1/KPD2 down– Efficiency 1/Efficiency 2 does not work.
• Statistics collection time (sec) –time period for collecting statistics, in seconds;
• Positive slips -the number of positive slips on the flow;
• Negative slips -the number of negative slips on the flow;
• Bytes received -the number of bytes received from the stream;
90
• Bytes sent -the number of bytes transferred by stream;
• Short packages -the number of received packets is less than the standard size;
• big packages -the number of received packets exceeding the standard size;
• Overflows -buffer overflow error counter;
• CRC errors -CRC error counter;
• Transmission failures -streaming failure counter;
• Code violation counter -counter of signal code sequence failures;
• CRC Error Counter / PRBS -number of CRC errors (in the "PRBS test" mode);
• bit error rate -the number of bit errors in the stream.
Below the table are the buttons:
• Reset counters -when setting the flag for the selected stream when the button is clicked
"Reset"accumulated statistics will be reset;
• Remote twist -test mode of the E1 path, in which the signal received by the set from connected
stream E1 will be directed directly to transmission to the same stream;
• PRBS-testincludes a pseudo-random sequence on the output port of the kit (transmits to the
connected stream E1), while at the input port of the kit (stream E1 reception) the error detection
mode of this sequence is turned on to assess the quality of signal transmission. The number of
errors and the analysis time counter can be viewed in the stream information window;
• PRBS test and local volvulus -E1 path test mode, in which the external line is turned off, and the
signal transmitted by the set will be directed directly to the reception of the same set. A pseudo-
random sequence will be enabled on the output port of the kit, the input port will work in error
detection mode;
• Disable test -disable test mode.
4.1.2.3 Monitoring of E1 channels

The section displays information about the status of stream channels E1. The top of the box is shown channel
matrix for streamsE1, where the line indicates the channel number, and the column indicates the stream
number (in the signaling protocol set for it is given in parentheses). At the bottom are information tables and
a control table.
Information tables
Connection information in stream # over channel #:
• Port/channel -section consists of two parts:
• signaling protocol (PRI/SS7);
• port coordinates:stream no.: channel no.
• Associated Port/Channel -section consists of two parts:
• associated port signaling protocol (PRI/SS7/VoIP);
• associated port coordinates:Stream No.: Channel No. forPRI/SS7orsubmodule numberVoIP:channel
number forVoIP.
• Related Callref– associated channel call identifier;
• State -channel state:
• Off– the channel is switched off;
• block– the channel is blocked;
• Init– channel initialization;
• Idle– channel in the initial state;
• In-Dial/Out-Dial– incoming/outgoing dialing;
• In-Call/Out-Call– incoming/outgoing session;
• In-Busy/Out-Busy– issuing a busy signal;
• Talk– the channel is in a conversational state;
• Release– channel release;
91
• Wait-Ack- Waiting for confirmation;
• Wait-CID– waiting for CgPN (AON);
• Wait-Num– waiting for dialing;
• hold– the subscriber has been put on hold.
• Status timer– duration of the channel being in the last state;
• Incoming category SS7– category SS7 of the incoming call before transformations;
• Incoming CdPN number– number of the called subscriber before transformations;
• Incoming CgPN number– caller's number before transformations;
• Outgoing category SS7– category SS7 of the incoming call after transformations;
• Outgoing CdPN number– number of the called subscriber after transformations;
• Outgoing CgPN number– caller's number after transformations.
The state of the streams is an information table for decoding graphic symbols in the matrix:
• State -stream status:

• NONE-submodule C4E1 is missing;
• OFF-the stream is disabled in the configuration;
• ALARM-C4E1 submodule initialization error;
• LOS-signal loss;
• AIS-alarm indication signal (signal containing all units);
• LOMF-signal indicating the emergency state of the multicycle;
• WORK/RAI-remote alarm indication;
• WORK/SLIP-slip indication (SLIP) on the stream;
• WORK-flow at work;
• TEST-flow test indication (PRBS test, loopback local and remote).
Channel status - information table for decoding graphic symbols in the matrix:
• State -channel status:

• off-the channel is disabled in the configuration;
• Idle-channel in its original state;
• block-the channel is blocked;
• incoming dialingincoming dialing;
• Outgoing dialing -outgoing dialing;
• Incoming alerting -incoming session, the called subscriber is free;
• Outgoing alert -outgoing session, the called subscriber is free;
• Busy, Releaserelease of the channel, the issuance of a signal "busy";
• Talk, holdthe channel is in a conversational state, on hold;
• Waiting-waiting for the response of the opposite side (waiting for confirmation classes,
waiting for caller ID, waiting for dialing);
• 3way, Conference -conference mode (three-party or sequential collection).
In the absence of one of the submodules C4E1 a message is issued"Submodule C4E1 is not installed, channel
monitoring is not available."
The channel status is updated once per5 second.
92
Link management
To be able to manage a stream, left-click on its name - the field will be highlighted in color, for example,
the screenshot below shows information for the stream2 (OKS-7). Next in the table"Management of
OKS-7 link"select the field with the required action and click on it with the left mouse button. A pop-up
informational message about the execution of the command will be displayed on the screen.
Monitoring → Channel MonitoringE1
93
Management of OKS-7 link - table of control of the signal link OKS-7:
• Send LUN– send a Link uninhibit signal;
• Submit LIN– send a Link inhibit signal;
• Submit LFU– send a Link forced uninhibit signal;
• Set state "Overload"– set signal link overload state;

• Cancel "Overload" state– cancel the signal link overload state;
• Set the state "Local processor failure";
• Cancel the "Local processor failure" state;
• Initiate the normal start of the signal link;
• Initiate an emergency launch of the signal link;
• Stop signal link.
OKS-channel management7
To be able to manage a channel in a stream, left-click on its icon - the field will be highlighted in color, for
example, the screenshot below shows information for the channel2 streams 1 (OKS-7). Next in the table
"Management of OKS-7 channel"select field with desired action and click on it with the left mouse button. A
pop-up informational message about the execution of the command will be displayed on the screen.
-It is possible to perform group operations for channels in a stream, for this it is necessary
select a range of channels with the < key pressedSHIFT>.
94
Monitoring → Channel MonitoringE1
OKS-channel management7 – channel control table (CIC) SS-7:

• Block channel (send BLO) –send BLO channel blocking message;
• Unblock channel (send UBL)– send UBL channel unblocking message;
• Reset to original (send GRS)– send an RSC message;
• Local blocking -block the channel locally without sending a BLO message;
• Local unlock– reset local blocking;
• Release (sending REL) – send REL message;
• Release confirmation (send RLC) –send an RLC message;
• Run integrity test (send CCR)–start a link integrity test by sending messagesCCR;
• Stop integrity test -forcibly terminate the link integrity test;

• Integrity test status -display the current status of the link integrity test.
95
4.1.2.4 Processor load graph

This section displays real-time CPU usage information (10 minute interval). Statistics graphs are built
on the basis of averaged data for each3 seconds device operation.
Monitoring → CPU Load Graph
Navigation between monitoring charts for individual parameters is carried out using
buttons and . To facilitate visual identification, all graphs have a different color
coloring.
• TOTAL-total percentage of CPU usage;

• IO-percentage of CPU time spent on I/O operations;
• IRQ-percentage of CPU time spent processing hardware interrupts;
• SIRQ-percentage of CPU time spent processing software interrupts;
• USR-the percentage of CPU time used by user programs;
• sys-the percentage of CPU time used by kernel processes;
• NIC-the percentage of CPU time used by programs with a changed priority.
4.1.2.5 Monitoring SFP modules

The section displays status indication and optical line parameters.
Monitoring → MonitoringSFP modules
96
• SFP port X status– state of the optical module:
• Availability of SFP module– indication of the module installation (the module is installed, the module is not
installed);
• Signal status– signal loss indication (signal lost, in operation);
• Temperature, °Cis the temperature of the optical module;
• Voltage, Vis the supply voltage of the optical module, V;
• Bias current Tx, mA– bias current during transmission, mA;
• Input power, mW– signal power at the reception, mW;
• Outgoing power, mW– signal power for transmission, mW.
4.1.2.6 Monitoring the front ports of the switch

The section displays information about the physical state of the switch ports - the presence of a link, the
agreed speed on the port and the transmission mode. If the port is dual (copper and optical connectors), then
next to the port number will be marked "SFP". It disappears if the dual port active and connected by copper
cable.
Monitoring → Monitoringswitch front ports
• Link state -state of the cable connection on the port (active/inactive);

• Speed -agreed speed on the port;
• Transfer mode -the mode used for data transmission (half-/full-duplex);
• LACP group -it displays the LACP channel, which includes the port and its status (UP/DOWN);
• LACP port status -the mode in which the port is located (active/backup);
• Bytes received -cumulative counter of received bytes, including various types of received
packages;
• Bytes sent -cumulative counter of transferred bytes, including various types of transferred packages.
97
4.1.2.7 Monitoring VoIP submodules

The section displays information about installed submodulesSM-VP, as well as information about the state of
the channels of these submodules.
Monitoring → MonitoringVoIP submodules
• No. -submodule serial numberSM-VP;

• Type -installed submodule type;
• State:
• Not present-not installed;
• no init-not initialized, no initialization attempts were made;
• off-disabled, submodule loading start;
• WaitAck-waiting for confirmation from the CPU after loading the submodule;
• Failed-the submodule is not responding;
• work-normal operation of the submodule;
• recovery-control packets are not received from the submodule;
• Reserved– the submodule is reserved for the SORM needed;
• SSW.Sorm– the submodule is used by the SORM intermediary.
• Active compounds -the number of active connections on the submodule at the current moment
time;
• Loading -the percentage of submodule resources used at the current time.
To monitor the status of channels, click on the line with the number of the required submodule with the left
mouse button. To hide the information, you must click on this line again.
98
Monitoring → MonitoringVoIP submodules→ Type (M82359)
Channel connection information:

• Port/channel -port/channel information:
• signaling protocol (VoIP);
• port coordinates:submodule numberVoIP:channel number.
• callref– internal call identifier;
• Associated Port/Channel -associated port/channel details:
• associated port signaling protocol (PRI/SS7/VoIP);
• associated port coordinates:Stream No.: Channel No. forPRI/SS7 orsubmodule numberVoIP:channel
number forVoIP.
• Related Callref– associated channel call identifier;
• State– channel state:
• Off– the channel is switched off;
• block– the channel is blocked;
• Init– channel initialization;
• Idle– channel in the initial state;
• In-Dial/Out-Dial– incoming/outgoing dialing;
99
• In-Call/Out-Call– incoming/outgoing session;
• In-Busy/Out-Busy– issuing a busy signal;
• Talk– the channel is in a conversational state;
• Release– channel release;
• Wait-Ack- Waiting for confirmation;
• Wait-CID– waiting for CgPN (AON);
• Wait-Num– waiting for dialing;
• hold– the subscriber has been put on hold.
• Status timer– duration of the channel being in the last state;
• Incoming category SS7– category SS7 of the incoming call before transformations;
• Incoming CdPN number– number of the called subscriber before transformations;
• Incoming CgPN number– caller's number before transformations;
• Outgoing category SS7– category SS7 of the incoming call after transformations;
• Outgoing CdPN number– number of the called subscriber after transformations;
• Outgoing CgPN number– caller's number after transformations.
Channel status:
• Idle (grey)– initial state, the channel is ready to serve the call;
• Active (green)– active state, the channel is busy with an active call;
• reserved (yellow)– the channel is reserved for service needs (issuance of tone signals "busy",
"ringback", "answer station") or a new call with his participation.
To view detailed information on a channel, select it in the table by pressing the left mouse button.
Information aboutIP connection per channel:

• State– channel state (description given above);
• codec– codec used (Payload Type is indicated in square brackets);
• Status– media information transfer status, options:
• good-channel in progress;
• Loss of RTP -loss of an oncoming RTP stream (when the “RTP Wait Timeout” expires)
packages");
• VBD-the channel is connected in data transfer mode;
• T38-facsimile communication has been established on the channel using the T.38 protocol;
• Mode-media channel mode:
• sendrecv-the channel works in two-way mode (reception and transmission);
• send-only-the channel works in one-way mode, only for transmission;
• recvonly-the channel works in one-way mode, only for reception;
• inactive-the channel is not active, the reception and transmission are inactive;
• SSRC-value of the SSRC (Synchronizatoin Source) field for the RTP stream outgoing from the device;
• IP:port remote -remote IP address and port of RTP stream source;
• IP:portlocal-local IP address and port of RTP stream source;
• MAC remote -remote source MAC address of the RTP stream;
• MAC-locallocal MAC address of RTP stream source.
Below the tables with the channel status there is a button"Disconnect", which allows forcibly
terminate the connection.
-In the case of using the SORM license, one of the submodules is completely reserved for ensuring joint control (see
sectionPurposeAndAppendix D. SORM function settings). In this case, the status of the submodule is displayed
as Reserved, channel monitoring this module is not produced, in accordance with the requirements of the order
of the Ministry of Communications of the Russian Federation dated
11/19/2012 No. 268.
100
4.1.2.8 Alarms. Alarm log

When an accident occurs, information about it is displayed in the headerweb configurator indicating
emergency flow numbers, OKS-line groups7, signal link or faulty module. If there are several active alarms,
in the headerweb configurator displays the most critical in the current moment of accident.
If there is no alarm, a message is displayed"There are no accidents."
Table20 - Examples of output messages about accidents
Configuration not read Configuration file error
No connection withSIP module Failure of the software module responsible for the operationSIP
Group of lines OKS-7 (linkset) not in operation Accident of a group of lines OKS-7
flow crashE1 E flow failure1
OKS link failure7 Alarm channel OKS-7
Synchronization from a lower priority Synchronization from a local source. All specified sources
source are not working
Remote flow crashE1 Remote E flow alarm1
Synchronization from a lower priority Loss of main clock source, current source has lower
source priority
Failed to sendCDR files to remote storage File upload problemCDR to remote storage
No connection withVoIP submodule No connection to submoduleSM-VP
RAM is running out High memory usage crash
No power supply One of the PSUs is not powered by the primary network
No connection withH323 module Failure of the software module responsible for the operationH.323
101
High CPU temperature Temperature:
70 °C - Warning
85 °C - accident
100 °C - critical failure
SIP interface not responding to OPTIONS requests One of theSIP interfaces
High CPU usage Loading:
higher90% warning
higher95% - accident
Problem with fans One or more fans not working
Running out of free disk space Running out of free space on one of your external drives
Trunk group'TrunkGroupName' CPS threshold exceeded One of the trunk groups receives more calls per second than
configured"Emergency value CPS"
SIP interface 'SIPInterfaceName' error Duplicate message errorINVITE received from UOVEEOS
duplicationINVITE equipment, usually associated with the unavailability of the
duplication server
Flow No. Efficiency1 and KPD2 not working Efficiency does not work1/efficiency2
On the menu"Journal of emergency events"a list of emergency events is displayed, ranked by date, time and
events. The "Only active" events show the actual accidents on the device at the moment. In the "all events"
events, all available information about accidents is displayed. There is also a button"Clear", which removes all
information from the current log messages and normalized crashes.
Monitoring → Alarm log → Active only
102
Monitoring → Alarm log → All events
Alarm table:
• Clear– delete the existing table of emergency events;
• No.– sequence number of the accident;
• Time– time of occurrence of the accident in the format HH:MM:SS;
• date– date of occurrence of the accident in the format DD/MM/YY;
• Type– type of accident:
• CONFIG– critical accident, configuration file failure;
• SIPT-MODULE– critical failure, failure of the software module responsible for the operation of VoIP;
• LINKSET– a critical accident, a group of lines OKS-7 is not in operation;

• STREAM– critical accident, flow E1 is not in operation;
• SM-VP DEVICE– accident, malfunction of the SM-VP module;
• SS7LINK– accident on the signal channel OKS-7;
• SYNC– synchronization failure, loss of synchronization source;
• STREAM REMOTE– warning, remote E1 flow alarm;
• CDR_UPSERVER– accident or warning, error sending the CDR file to a remote storage;
• TRUNK-CPS– exceeding the number of allowed calls per second on the trunk group;
• SORM-KPD – failure of KPD1/KPD2 not in operation;
• SIP DUPLICATE– errors when duplicating an INVITE message received from equipment
UOVEOS.
• State– emergency status:
• Critical alarm, flashing red light -an accident requiring immediate intervention of service
personnel, affecting the operation of the device and the provision of communication
services;
• Alarm, red indicator -non-critical accident, intervention also required personnel;
• Warning, yellow indicator -an accident that does not affect the provision of communication services;
103
• OK, green indicator -the accident has been cleared.
• Options– textual description of the details of the accident. Depending on the type of accident, the
following view:
• CONFIG;
• SIPT-MODULE– no connection with the SIP module;
• LINKSET– line group OKS-7 (linkset) XX not in operation, where XX – line group number
OKS-7;
• STREAM– flow accident E1 XX, where XX – flow number;
• SM-VP DEVICE– no connection with the VoIP submodule XX, where XX is the number of the SM-VP submodule;
• SS7LINK– OKS-7 link failure. Linkset XX, stream E1 YY, where XX is the number of the SS-7 group, YY is number
of the signaling channel in the SS-group7;
• TRUNK-CPS– trunk group 'XX' CPS threshold exceeded, where XX – trunk group name;
• SORM-KPD – stream XX KPD1/KPD2 not working, where XX – number of E1 stream;
• SIP DUPLICATE– SIP interface 'XX'. Error duplicating INVITE to server '<YY>', where XX is NameSIP
interface on which the error occurred; YY is the address of the duplication server, on which the
error occurred.
4.1.2.9 Monitor interfaces

This section is intended for monitoring the status of network interfaces (tagged/ untagged/VPN), as
well as viewing users connected to the VPN device.
Monitoring → Interface monitoring
• Ethernet -Ethernet interface name;

• Network name -the name with which the specified network settings are associated;
• VLAN ID -virtual network identifier (for a tagged interface);
• DHCP-Status using DHCP protocol to get network settings automatically (requiresDHCP server in
the operator's network);
• IP address,netmask,Broadcast-interface network settings (if DHCP is not used).
VPN/pptp interfaces
• PPP interface -interface name;
• Network name -the name with which the specified network settings are associated;
• PPTPDIP -IP address of the PPTP server to connect;
• Username -user ID;
• IP address,PtP, Netmask -interface network settings.
104
4.1.2.10 Drive information

This section displays information about external drives connected to the device.
• Extract– by clicking on the link, the drive will be safely removed.
Monitoring → Storage information
The names of external drives are tied to interface ports:
-Device naming follows the principle /dev/sdX.
SMG1016M
SSDNo.1 /dev/sda*
SSDNo.2 /dev/sdb*
USB /dev/sdc*
SMG2016
HDDNo.1 /dev/sda*
HDDNo.2 /dev/sdb*
USB /dev/sdc*
SMG3016
HDDNo.1 /dev/sda*
HDDNo.2 /dev/sdb*
USB /dev/sdc*
105
4.1.2.11 Interfaces V5.2
In this section1displays the status of V5.2 interfaces.

• Red— the interface is not in operation;
• Green— interface in operation.
-1Available with V5.2 license.
4.1.2.12 Queue statistics

This section displays the queue operation statistics.
• Queue ID— queue identifier;
• Total received calls- the total number of calls received in the queue;
• Answered- the number of successful calls ended with the operator's answer;
• Not answered- the number of calls in which the caller hung up without waiting operator response;
• Average queue length (hour/day/workday)— the maximum value of the queue length for last
hour/day/business day. The last hour/day is a periodic interval of time that repeats every hour/24
hours respectively, the beginning of the first interval is necessary count the moment of software
start. The time intervals of the working day are set in the call groups settings;
• Unsuccessful call attempts- the number of unsuccessful attempts to call back the subscriber, with
using the optioncallback1;
-1Not supported in current software version 3.20.5.
• Queue overflows- the number of calls that were rejected due to size overflow queues;
• Average waiting time- average waiting time for an operator response, based on this value a response
is formed;
To clear the statistics of queues, set the "Select" flag next to those queues whose statistics you
want to clear, and click the button that appears"Clear Selected".
106
4.1.2.13 Tasks of the SSS (the section is available with an SMG-VNS license)
Monitoring → Tasks of SSS
This section displays the status of running voice announcement systems.

• Task name– the name of the SSS task;
• State– displays the status of a running task on a notification:
• Waiting;
• Booked;
• Prepared;
• Launched;
• Error;
• Requires completion;
• Stopped;
• Completed.
• Start time– start time of the notification task in the format Hours:Minutes:Seconds Day month
Year;
• Percent Complete– percentage of task completion (the ratio of the number of processed calls to
all calls in this task);
• Inactive– number of inactive calls in the task. Example: 30(40) - 30 out of 40 (total numbers in
the task);
• Active– number of active calls in the task. Example: 15(40) - 15 out of 40 (total numbers in task);
• Unsuccessful– the number of unsuccessful calls in the task. Example: 5(40) - 5 out of 40 (total numbers in
the task);
• Completed– the number of completed calls in the task. Example: 35(40) - 35 out of 40 (total
numbers in the task);
• Complete– Forced termination of the calling task.
4.1.3 E1 streams
This section configures the signaling and parameters of each E stream.1.
4.1.3.1 Timing sources

To synchronize the device from multiple sources, a priority list algorithm is used. Its essence is as follows:
when the clock signal from the current source fails, the list is looked through for the presence of active
signals from sources with a lower priority. When a signal is restored from a source with a higher priority, it
switches to it. It is also possible to have multiple sources with the same priority, and no switching will occur
when the signal with the same priority is restored.
Can be set up to16 clock sources (from any of the 16 E1 streams and from two external sources).
107
Ports for receiving an external clock signal have an impedance120 ohm. The input signal must have the
parameters described in the recommendationITU-T G.703 clause 15: 2048 kHz syncronization interface (T12).
streamsE1→ Synchronization sources
The list is formed using the buttons:
- "Add source";
- "Delete".
Changing the source priority is done with the buttons "Up down» in front of each
source. The highest priority is the value0", the lowest priority is "15".
• Signal Loss Timeout- the time interval during which there is no switching to a lower priority
synchronization source in case of signal loss. If the signal recovers within this interval, no switching
will occur;
• return timeout– time interval during which it must be active again sync signal from a higher
priority source before it is switched to.
-If the stream from which the clock signal is received is configuredD-channel (for SS7 or PRI protocol),
you need to make sure that the D-channel is in operation, otherwise the clock from the stream will
not be captured, which will lead to slippage (slip).
108
4.1.3.2 Selecting the signaling protocol

The choice of the signaling protocol used on the stream is made in the drop-down list "Signal
Protocol".
streamsE1→ Flow0 (Q.931-U)→ Physical parameters/Q.931
The device supports the following signaling protocols:

• Q.931 (User);
• Q.931 (Network);
• SS7 (OKSNo.7);
• SORM;
• SORM-TRANSIT1;
• V5.2 (LE);
• M2UA2;
• IUA (User)1;
• IUA (Network)1.
InterfacesV5.2:
• Media Gateway1.
- 1This software version is not used on SMG-1016M, SMG-2016, SMG-3016.

2This version of the software is not used.
4.1.3.3 Setting the physical parameters

Physical parameters:
• Name– name of the flow E1;
• Included– physical inclusion of the flow;
• Framing:
• double frame– CRC4 disabled;
• CRC multiframe– formation of the CRC4 checksum on transmission and control on
reception.
• Equalizer– when the flag is set, the transmitted signal is amplified;
109
• Alarm indication– if the flag is set, in case of a local accident on the stream, indication of an accident
(the indicator on the device will light upALARM, the alarm will be logged accidents);
• Remote alarm indication– if the flag is set, in case of a remote accident on the stream, indication of an
accident (the indicator on the device will light upALARM, the alarm will be logged accidents);
• Line code type -type of information coding in the channel (HDB3, AMI);
• Slip indication -if the flag is set, in case of slip detection in the receiver path will be an indication of an
accident;
• Slip detection timeout– the frequency of polling the flow parameters from the board, if on this If a
slip has been detected in a stream, then during this timeout the gateway will signal an accident.
110
4.1.3.4 Configuring DSS1/EDSS1 (ISDN PRI Q.931) signaling protocol
4.1.3.4.1 Physical/Q.931 tab

111
Q.931 LAPD - Link layer parameters of the Q.931 LAPD protocol

• T200 -transmission timer. This timer determines the amount of time during which a response to the
frame must be received, after which further frames can be transmitted. This interval must be greater
than the time it takes to transmit a frame and receive its acknowledgment;
• T203 -the maximum time during which the equipment is allowed not to exchange frames with
an oncoming device;
• N200-number of attempts to retransmit frames.
OptionsQ.931
• Trunk group– name of the trunk group that includes the E1 stream;
• PRI profile– selection of a PRI profile for servicing PRI subscribers;
• Scheduled Routing Profile– selection of a scheduled routing profile from list of existing ones;
• Access category– choice of access category;

• Numbering plan– defines the numbering plan in which routing will be performed for a call received
from this port (this is necessary for the coordination of numbering plans);
• Numbering plan type -specifies the ISDN dial plan type. To use the common numbering planE.164
selectISDN/telephony;
• Caller ID category for incoming calls– ANI category assigned to those accepted from this call port;
• Caller ANI Category Transfer– allows the transmission of the caller's ANI category subscriber in the
information elementCgPN of the SETUP message as the first digit of the number.
-For proper operation, it is necessary to support this mode on the opposite side.
• "End of Dial" message– issuance of the information element "Sending Complete" when occurrence
of the "End of dialing" event (arrival of such an event from the side of the associated channel,
reaching the maximum number of digits according to the prefix, timeout waiting for dialing the
next digit);
• Do not issue interface RESTART -when the flag is set, the gateway does not output to the line
messageRESTART on stream recovery (raising the LAPD link layer);
• Do not issue channel RESTART -if the flag is set, the gateway does not issue a RESTART message to the
line after the T308 timer expires. This timer is enabled after transmission to the channel messages
RELEASE and is reset when a RELEASE COMPLETE message is received in response. If during the timer
T308 RELEASE COMPLETE message was not received, then for channel release message is sent
RESTART;
• Canal Occupation– determines the order in which the physical channel is allocated when performing
outgoing call. Four types can be selected: sequentially forward, sequentially backward, starting from
the first forward, starting from the last back. To reduce conflict situations when connecting to
adjacent exchanges, it is recommended to set inverse types of channel occupation;
• Issue DialTone on incoming overlap-session– if the flag is set, the gateway incomingoverlap-
occupation issues in a lineDial Tone(ready signal "Station answer"). IN this caseoverlap-
occupation - receiving a SETUP message without indicating sending complete;
• Handle PI In-Band in DISCONNECT– when the flag is set, the field is processedPI In-Bandin the
received DISCONNECT message to issue an autoinformer voice message when the call is released,
otherwise this field is ignored;
• Treat PROCEEDING as ALERTING– if the flag is set, upon receipt of the PROCEEDING message, we
process it as ALERTING and issue a CPV;
• Handle PI in SETUP– adds the ability to change the Progress Indicator in SETUP- message:
• Transit – transfer without change;
112
• 1 - Not end-to-end ISDN;
• 2 - Dest addr is non ISDN;
• 3 - Orig addr is non ISDN;
• 4 - Return to ISDN;
• 5 – Interworking occurred;
• 8 - In-band information.
• Replace characters '?' on 'D' in CgPN– if the flag is set, if the '?' character arrives in the CgPN in the
received SETUP message, it will be replaced by the 'D' character;
• Transit ISUP Location Number –if the flag is set, if the Location Number parameter is transmitted in the
incoming SS7/SIP-T message, then it will be passed to the Calling Party Number parameter in the
outgoing SETUP Q.931 message.
4.1.3.4.2 Naming Options tab

On this tab, you can configure the method of receiving/transmitting subscriber names and the encoding of the received/
transmitted name.
streamsE1→ Flow0 (Q.931-U)→ Name transfer options
• Name passing method:

• No– transfer of names is disabled;
• Q.931 DISPLAY– transmission in Q.931 Display element c Codeset 5;
• QSIG-NA– QSIG-NA (ECMA-164) protocol transmission;
• CORNET– transmission via Siemens CorNet protocol;
• CORNET HICOM-350– transmission via Siemens CorNet protocol with additional
information for ATSHicom;
• AVAYA DISPLAY– transmission in Q.931 Display element c Codeset 6;
• QSIG-NA (Ericsson)- transfer to the facility and user-user information.
• Name encoding method:
• Transit– recoding is not carried out (by default, it is assumed that the name VUTF-8);
• CP 1251– encoding Windows-1251;

• Siemens adaptation– ATS Siemens coding;
• AVAYA adaptation– AVAYA PBX coding;
• Latin transliteration– Russian names will be transliterated in Latin letters.
• Forward direction onlysending the name of the subscriber only in direct messages
directions.
The selected method of receiving/transmitting names and the encoding of the received/transmitted name
are valid only inside the configurable stream E1. It is possible to transfer from stream to stream with
different name transfer settings. In this caseSMG to harmonize the parties itself performs recoding.
113
4.1.3.4.3 Channel usage tab

streamsE1→ Flow0 (Q.931-U)→ Using channels
In this menu, you can enable the flow channel E1 or off. To do this, you need to install or uncheck the flag
opposite the corresponding channel. The "Trunk group" column displays the number of the group in which
these channels are configured (used when the trunk group is set not for the entire stream, but for the
channels of the stream).
114
4.1.3.5 SS7 signaling protocol setting
4.1.3.5.1 Physical parameters/SS7 tab

streamsE1→ Flow0 (OKSNo.7)→ Physical parameters/OKS7
Parameters OKS-7:
• OKS-7 line group –choice of linkset (group of SS-7 lines);
• Channel ID (SLC) –signaling channel identifier in the group of SS-7 lines;
• Counter code MTP3 (DPC-MTP3) –opposite signaling transit point (STP) code. Used at workSMG
in quasi-linked mode. If the quasi-coupled mode is not required, you must set the value0. In this
case, the opposite MTP3 code is meaningDPC-ISUP,configured in the configuration (section
Groups of lines OKS-7);
• CI for D-channel -timeslot number on which the signaling will be transmitted;
-After changing numberD-channel on a stream with OKS-7 signaling must be switched to the
"Channel Settings" tab and set the correctCIC for CT previously assigned to D- channel.
• Bit D in LSU -setting bit D to 1 in the status field (SF) of the LSSU (bitsDFs in the SF status field are
reserved).
115
4.1.3.5.2 Channel settings tab

streamsE1→ Flow0 (OKSNo.7)→ Channel tuning
• ISUP CIC - channel identifier code– setting the numbers of spoken channels (CIC).
116
For automatic numbering of spoken channels, press the button"Ask".
streamsE1→ Flow0 (OKSNo.7)→ Channel setup → Set
This will open the following menu:

• Start number -number of the first spoken channel;
• Numbering step -channel numbering step. Each subsequent channel will be assigned a number. one
"numbering step" more than the previous channel;
• Last number -displays the number that will be assigned to the last CIC channel in selected
range;
• CI range -selection of values in this block allows you to assign numbering to all channels stream or for
the specified range of channels.
4.1.3.6 V5.2 protocol setting

Assigning a thread to an interfaceV5.2 is produced in the parameters of the V5.2 interface.
This section displays the current interface for reference.V5.2 to which this thread and also the thread id
insideV5.2 interface.
streamsE1→ Flow0 (OKSNo.7)→ Physical parameters/V5.2
117
4.1.3.7 Configuring the SORM signaling protocol

streamsE1→ Flow0 (OKSNo.7)→ Physical parameters/COMP
• Enable command wait timer 10 min– enable/disable the receive waiting timeout commands from SORM PU (implemented
in accordance with paragraph1.5 OrdersNo.70 of the State Communications Committee of Russia dated 04/20/1999);
118
• Activity control -monitoring the activity of messaging at the L1 level, in case flow15 seconds no packets
were received on at least one of the channels, a reset will occur and re-initialization of thread E's framer
1;
• Do not send VAS service prefix– when ordering VAS services, the subscriber to the SORM console will not
the prefix of the VAS service is transmitted. For example, when ordering the "Unconditional Call
Forwarding" service and dialing a number *21*2728331# to the SORM console in message 44 will be
present only number2728331 to which the redirect is assigned;
• Do not use extended error codes– when the flag is set in response to a command with incorrect
parameters will send messages about the non-acceptance or non-execution of the command only
with the signs defined in order No.268. Otherwise there will be use the signs of non-execution of
the manufacturer's commands, allowing you to more accurately determine the reason for the
failure of the command. The list of standard codes and manufacturer's codes is given in Appendix E;
• Operator selection code analysis– when monitoring the subscriber, the number dialed by the subscriber is not taken
into account prefix for choosing a telecom operator for long-distance or international calls (for more details, see
Appendix D);
• Control by Redirecting number -use the number from the Redirecting number field (or diversion in the
SIP protocol) for transmission to the PU. When a call comes in with a Redirecting number (or a
diversion in the SIP protocol), the number is initially compared from the Calling Party Number field
with the numbers that are on the control, then, if a match is not found, with the number from the field
Redirecting number (or diversion in SIP). If the option is not available, comparisons WithRedirecting
number (or diversion in the SIP protocol) does not occur;
• Do not return 1.1 for incomplete dialing;
• Communication node type -the type of the host carried in the last byte of the messageNo.11 (Software version
stations);
• Protocol specification– selection of the SORM specification according to which the device will operate:
• RU Order 70- SORM specification for the order of the State Communications Committee of Russia dated 04/20/1999No.70;
• RU Order 268- SORM specification for the order of the Ministry of Telecom and Mass Communications of Russia dated 11/19/2012 No.
268;
• KZ– SORM specification for the Republic of Kazakhstan.
Connection mode
• X25– Efficiency signaling channels are organized through the X25 protocol, using channels 30-31
flow E1;
• TCP– signaling channels of the CPD are organized through the TCP protocol. Settings active
only when "Connection mode" is selectedTCP"):
• Port 1– virtual TCP-port for organizing signaling channel KPD-1;
• Port 2– virtual TCP-port for the organization of the KPD-2 signal channel;
• Interface– select the network interface of the device.
Channel operation mode
• Channel 1– block for setting the parameters of the channel for transmitting control information from the SORM PU;
• Channel 2– block for setting the parameters of the channel for transmitting information about controlled
connections fromSMG-1016M.
Channel settings
• Channel operation mode:
• DTE– if the flag is set, the device type is DTE (information transmitter);
• DCE– if the flag is set, the device type is DCE (receives data from DTE- devices).
• Send SABM– when the flag is set, a message about the beginning of connection initialization
procedures;
• Send RESTART (L3)– transmission of the message "restart level 3" when establishing
connections with PU SORM;
119
• Send INITIAL_RESET (L3)– transmission of a "level 3 reset" message when the connections with
PU SORM.
Frame addresses
• TxCmd Addr– command frame address;
• TxRespAddr– address of the response frame;
-It is not allowed to install the SORM protocol on several streams.

After selecting the SORM protocol on one of the streams, it is necessary to restart the software.
Factory password SORM "123456".
• DTE/DCE mode trim -DTE/DCE auto tuning option, default enabled. If the device and the remote side
are set to the same mode (DTE-DTE orDCE/DCE) and the tuning option is enabled, the SMG will
automatically change the mode to the correct one.
-It is not recommended to disable the option "Mode AdjustmentDTE/DCE",because this may lead to
malfunction of the device.
-Modification of numbers on the SORM stream serves only to fine-tune interaction with SORM
console in some exceptional configurations and should not be used in normal SORM setup. The
need for the use of modifiers is determined by a qualified specialist. The SORM configuration
procedure is described in the section Appendix D. SORM function settings.
Incoming number modifiers– selection of the modifier table intended for analysis and modification of the
subscriber's telephone number in the SORM messages received from the console.
Outgoing number modifiers– selection of a modifier table intended for analysis and modification of the
subscriber's telephone number in SORM messages sent to the console.
Always modifyB number– option required to modify all B numbers, previously for outgoing number
modifier was not applied to the number dialed by the local subscriber.
Controlled number modifiers– selection of the modifier table intended for analysis and modification of
the subscriber's telephone number before its selection for sending to the SORM console.
4.1.4 Numbering plan

This section configures the numbering plan of the device.
The device has implemented up to16 independent numbering plans (up to 255 for SMG-2016 and
SMG-3016 with a DVO license). Each numbering plan can have its own subscribers and prefixes. The
number of active plans is configured in the sectionSystem Settings.
Exists4 criteria by which calls are routed on the device:
• search by caller number – CgPN (Calling Party Number);
• search by called number – CdPN (Called Party Number);
• search by caller number – CgPN (Calling Party Number) and callee – CdPN(Called Party Number);
• search in the database of subscribers configured on the device.

When a call arrives in the numbering plan, its routing begins, initially it is searched for a match with number
masksCgPN. If there is a prefix with the logic "AND" (masks are set ByCgPN and CdPN, and a match was
found for both parameters) and a prefix with the same mask is found ByCgPN, then if the “Priority”
parameter is equal, the call will follow the prefix with the “AND” logic, because
120
its mask is considered to be more accurate. If the priority of the prefix with "AND" is less, then the call will follow
the prefix with "OR".
If, when searching forCgPN there are two prefixes with the logic "AND", and the CgPN mask is the
same, then comparedCdPN and the call is routed by the prefix with the more precise mask.
Next, the search takes place in the database of subscribers configured on the device. In case of finding a
match by prefix with a maskCgPN or the subscriber base, the call is routed and further search is
terminated.
Search and call routing based on the database of configured subscribers is carried out even if the call
parameters match the number masksCgPN.
If the call parameters do not match the masksCgPN and with the subscriber number, a search is performed
for all masksCdPN configured in the dial plan.
-If masks for numbers are simultaneously configured in the prefix parametersCgPN and CdPN and the
logical OR operator is set, then this rule works according to the OR logic, i.e. simultaneous analysis
by numberCgPN and CdPN does not occur.
If masks for numbers are simultaneously configured in the prefix parametersCgPN and CdPN
and the AND logical operator is set, then this rule works according to the AND logic, i.e. For
routing a call on this prefix requires a match with masksCgPN and CdPN.
Numbering plans → Plan #0 'NumberPlan#0'
Dial plan options:

• Name -numbering plan name;
Number check by number– checking the possibility of routing by the number entered in this field.
The check is carried out by the masks of the calling and called subscribers, as well as by the
database of configuredSIP subscribers.
• ST– when the flag is set, the end-of-set sign is taken into account during the search;
Mask search– search for a prefix by number pattern, name, direction, prefix type, trunk direction, trunk
group.
121
As a result of the check, data on the possibility of routing by this number is displayed:
• calling-table-routing by caller table;
• called-table-routing according to the table of called subscribers;
• NOT found inrouting by this table is not possible;
• found in-routing by this table is possible;
• Subscriber 'SIP' idx[4] –SIP subscriber [record number of this subscriber in the database];
• Prefix[6] -routing by prefix [prefix number in the list].
Copying prefixes to another dial plan
• Copy all prefixes to dial plan -option to copy all prefixes current numbering plan to another
numbering plan. Used similarly to copying selected prefixes, but does not require selection of
prefixes;
• Copy selected prefixes to dial plan –option appears when selected prefix in the table allow you to copy
marked prefixes to another dial plan. To use, select prefixes, target numbering plan and click the
button
"Copy".
4.1.4.1 Creating a dial plan prefix

To create a new prefix, select the menu"Objects" - "Add object"or click the button below the list and fill
in the prefix parameters in the opened form:
Numbering plans → Plan #0 'NumberPlan#0'→
Basic prefix parameters

• Name -numbering plan name;
• Numbering plan– choice of numbering plan;
• Access category -setting the access category;
• Check access category -if the flag is set, the possibility is checked routing by this prefix based on
the rights defined by the access categories;
• prefix type -prefix type setting:
122
• trunk group– access to the trunk group;
• trunk direction– access to the trunk direction;
• numbering plan change– allows you to switch to another plan when dialing this prefix
numbering. When choosing this type of prefix, the option “new numbering plan” will be
available, in which you need to choose which numbering plan to switch to;
• subscriber capacity– designed to set the subscriber capacity of the device. If If the number is present in the
subscriber capacity, but not assigned to the subscriber, then when calling to such a number, a release
message is displayed with the value of the release reason (cause code): 1 - Unallocated (unassigned)
number;
• DVO prefix– designed to manage VAS services from a telephone set;
• interception group– is intended for configuring the group exit prefix interception;
• IVR scenario– intended for configuring the exit prefix for the IVR scenario.
Parameters of the "Trunk group and trunk direction" prefix Basic
parameters of the prefix:
• Trunk group -trunk group to which the call will be routed on this prefix;
• Direction– type of access to the trunk group: local, special service call, zonal, departmental network,
long-distance communication, international communication. Used for SORM calls, as well as to restrict
communication in case of failure in data exchange withRADIUS server (see sectionSettingRADIUS);
• Caller ID Request– indicates the need for ANI information (number and category of the calling
subscriber) to access the trunk group specified in the "Trunk group.When a call is received from an
interacting node and there is no ANI information in this call, an ANI request will be sent to the node
(messageINR according to OKS-7 signaling);
• Caller ID is required– indicates that the ANI informationobligatorywhen exiting direction. If ANI
information cannot be obtained from the calling party, then the connection establishment
process is aborted;
• Dial Mode -number transfer method:
• enblock– after the accumulation of all address information,
• overlap– without waiting for the accumulation of all address information.
• Do not send end of set (ST)– if the flag is set, do not transmit the sign of the end of the set (ST - in the
SS or sending complete in the PRI);
• A priority -if there are overlapping masks in the dial plan, the call will promoted to the highest priority
prefix. Meaning0 is the highest priority, 100 is the lowest a priority;
• Call duration limit (sec) –call connection duration limit, passed through this prefix;
• Notify when a call ends in (sec)– activated when using the option "Call duration limit (sec)", an audible
signal is issued, warning about the end of the call for the specified number of seconds before the end
of the conversation. If the specified time is more60 seconds, then 5 seconds before the end of the call,
another additional warning sound. If the specified time is less60 seconds then no additional signal will
be given.
• Logical operator:
– or – if there are CgPN and CdPN masks on the prefix, simultaneous analysis by CgPN and CdPN
number does not occur;
– and – simultaneous analysis by CgPN and CdPN number takes place.
For correct operation of prefixes with the logical AND operator, it is necessary to configure a mask
forCgPN and CdPN. If one of the masks is missing, the prefix will not work.
123
OptionsCDPN:
• Type of number -callee number type:unknown, subscriber number, national number, international
number, network specific, do not change. The selected number type will be sent to alarm messages
OKS-7, ISDN PRI, SIP-I/T when making an outgoing call via prefix("Do not change"– do not convert
number type, i.e. transmit as it was received from the incoming channel);
• Numbering plan type– type of dial plan of the called subscriber, can take the following values:
unknown, isdn/telephony, national, privat, do not change. The selected numbering plan type will be
be sent in signaling messagesISDN PRI when making an outgoing call via prefix (Do not change - do
not convert the number type, i.e. transmit in the form in which it was received from the incoming
channel).
Timers for direct output(used when connecting trunk groups directly without analyzing prefix masks -
function"Direct Prefix"in trunk group settings).
These timers only work when dialing in mode.overlap:
• short timertime in seconds that the digital gateway will wait to continue dialing if part of the
address information has already been received. Default -5 s;
• Duration-dialing duration timer. The default is 30 s.
Parameters of the "Change numbering plan" prefix
• New numbering plan– numbering plan to which the call will be transferred;
• New access category -category assigned to the caller after going to different numbering plan;
• A priority– if there are overlapping masks in the dial plan, the call will promoted to the highest priority
prefix. Meaning0 is the highest priority, 100 is the lowest a priority;
• Call duration limit (sec)– limitation of call connection duration, passed through this prefix;
be given.
numbers does not occur;
Modifiers when changing the numbering plan:
• CdPN Modifiers– intended for modifications based on number analysis called subscriber;
• CgPN Modifiers– intended for modifications based on number analysis caller;
Parameters of the prefix "Prefix DVO"

Number masks forprefixDVO must always end with a # (pound sign).
• VET service type– selection of the VAS service type for its management from the subscriber's telephone set:
• CFU-unconditional forwarding;
• CFB-call forwarding on employment;
• CFNR-forwarding on non-response;
124
• CFOOS-forwarding on unavailability;
• call pickup– call pickup;
• Conference– conference call;
• Clear all– cancellation of all services;
• Intercom– intercom call (with automatic answer of party B);
• Paging– similar to Intercom, but with a call to conference numbers;
• Password– setting a password;
• Password once– password access;
• Password access– password activation;
• Restrict out– restriction of outgoing communication;
• DND- do not disturb;
• Blacklist- black list.
• Action– select an action for the service:
• Installation -installation of VVO service;
• Cancel -cancellation of the VVO service;
• Control -VAS service activity control;
• numberAdd -add number;
• numberDel -delete number.
Pickup Group Prefix Options
• Intercept group– pickup group in which the call will be picked up when dialing given prefix. If you
select the "Any" group, interception will be performed in all groups;
subscriber) to access the trunk group specified in the "Trunk group.When a call is received from an
interacting node and there is no ANI information in this call, an ANI request will be sent to the node
(messageINR according to OKS-7 signaling);
process is aborted;
• A priority– setting the prefix priority in the range from 0 to 100. The prefix with the lower the value of
this parameter has a higher priority (0 - highest priority, 100 - lowest priority)
be given.
Timers for direct output
• short timertime in seconds that the digital gateway will wait to continue dialing if the already dialed
number matches a pattern in the dialing plan, but there is a possibility of more digits resulting in a
match with another pattern. Default -5 s;
125
Prefix options "IVR scenario"

• IVR scenario– IVR scenario to which the call will be routed by this prefix;
subscriber).When a call is received from an interacting node and there is no ANI information, an ANI
request will be sent to the node (messageINR according to OKS-7 signaling);
process is aborted;
• A priority– setting the prefix priority in the range from 0 to 100. The prefix with the lower the value of
this parameter has a higher priority (0 - highest priority, 100 - lowest priority)
be given.
Timers for direct output

List of masks
For numbering plans created in the section"List of masks"number masks are configured for routing by
this prefix.
Numbering plans → Plan #0 'NumberPlan#0'→ Object
The list is formed using the buttons:
- "Add mask";
– “Edit mask”;
– “Remove mask”;
- "See the mask.
126
The green arrows to the left of the created mask allow you to move the entry in the table, adjusting their
order (priority).
Numbering plans → Plan #0 'NumberPlan#0'→ Object→
• Mask– template or set of templates with which the received from the incoming channel is compared
number of the calling or called subscriber intended for further call routing (the syntax of the mask is
described in sectionDescription of the number mask and its syntax);
• Type- mask type. Determines which number will be routed - by caller number (calling) or called
subscriber (called);
• Long time -time in seconds during which the digital gateway will wait for dialing the next digit until
it matches any pattern in the numbering plan. Default - 10s;

Forprefix editingit is necessary to double-click in the table of prefixes with the left button
mouse over the line with the prefix or select the prefix and press the button below the list.
Forremove prefixhighlight the prefix and press the menu button"Objects" - below the list, or select
"Delete object".
4.1.4.2 Number mask description and syntax

The number mask is a set of patternstemplate, separated by the special character '|'. The mask must be
enclosed in parentheses. (templ) is equivalent to (templ1|templ2|...|templN).
Syntax:
• XorX– any character from "0-9*#";
• * - symbol *;
• # - symbol #;
• 0-9- numbers from 0 to 9;
• D- number D;
• . - the special character "dot" means that the character in front of it can be repeated an
arbitrary number of times (but no more30 characters for the entire number), for example:
• (34x.)– all possible combinations of numbers starting with “34”;
• [ ]- an indication of the range (through dashes), or enumeration (without spaces, commas and
other characters between digits) prefixes, for example:
127
• range([1-5]XXX)– all 4-digit numbers starting with 1,2,3,4 or 5;
• enumeration([138]xx)– all 3-digit numbers starting with 1,3 or 8).
• {min, max}- specifying the number of repetitions of the character before the brackets, for example:
• (1x{3,5})– means that any digits (X) can be from 3 to 5 and is equivalent to a mask (1ххх|
1хххх|1ххххх);
• | -vertical bar. BooleanOR– used to separate patterns in the mask;
• !- Exclamation point. When used before a pattern, it means negation, i.e. sets mismatch of the
number with the template;
• (-)– mask used only in CgPN number modifier tables for calls without caller number. Allows you to
add the caller's number if it was not available, as well as set indicators for this number.
-If there are overlapping prefixes in the dial plan, then when processing the number in numbering
plan, the prefix with the most accurate mask for a particular number will be prioritized, for
example:
Prefix1:(2xxxx)
Prefix2: (23xxx)
On admission to the numbering plan23456 it will be processed by prefix 2.
Also masks containing an arbitrary number of repetitions (x.) or quantity range repetitions {min,
max}, less priority than masks with the exact number of characters, For example:
Prefix1: (2x{4,7})
Prefix2: (23xxx)
On admission to the numbering plan23456, it will be processed by prefix 2. Masks with specified
repetition range {min, max} take precedence over masks with any number of repetitionsx.), for
example:
Prefix1: (2x.)
Prefix2: (2x{4,7})
On admission to the numbering plan23456 it will be processed by prefix 2.
4.1.4.3 Mask operation examples

Example1.
(#XX#|*#XX#|*XX*X.#|112|011|0[1-4]|6[2-9]XXX|5[24]XXXXX|810X{11, 15})
The mask contains9 patterns:
1.#XX#– a 4-digit number is dialed, starting and ending with #, 2nd and 3rd digits numbers can take
any value from0 to 9, as well as * and #.
Such a template is usually used to disable the use of VAS from a telephone set;
2.*#XX#– Dial a 5-digit number starting with*#and ending with#, 3rd and 4th digits of the number
can take any value from0 to 9, as well as * and #.
Such a template is usually used to control the use of VDO from a telephone set;
3.*XX*X.#– an N-digit number is dialed, starting with *, then any two digits of the number (from 0 to 9,
as well as * and #), then *, then an indefinite number of any digits (from 0 to 9, *) up to those until it
meets in the set#.
Such a template is usually used to order VAS from a telephone set;
4. 112 - dialing a specific number from 3 digits - 112;
5. 011 - dialing a specific number from 3 digits - 011;
6. 0[1-4] – dial a 2-digit number starting with 0 and ending with 1, 2, 3 or 4, i.e. numbers 01, 02, 03 and
04;
7. 6[2-9]XXX – a 5-digit number is dialed, starting with the number 6, the second digit of the number is any
of the range from2 to 9, the last three digits are any from 0 to 9, as well as * and #;
128
8. 5[24]XXXXX – a 7-digit number is dialed, starting with the number 5, the second digit of the number
is or2 or 4; the last five digits are any from 0 to 9, as well as * and #;
9. 810X{11, 15} – Dial a number starting with 810, followed by allowed dial from11 to 15 any digits from 0
to 9, as well as * and #. Including the first 3 digits, the length of the number according to this rule,14
to 18 digits.
Example2.
You must configure the dial plan so that all numbers starting with1 and having length3 were routed to
Trunk0, and the number 117 separately from them to Trunk1.
To solve this problem, we configure the prefixes as follows:
1. first prefix with mask(117)to Trunk1;
2. second prefix with mask(11[0-689]|1[02-9]x)to Trunk0.
In the second prefix, patterns overlap all numbers of the form "1xx", except for number 117. Example
3.
You want to configure a dial plan by excluding some numbers from a group. Number group
2340000-2349999, excludes numbers 2341111, 2341112, 2341113, 2341114, 2341115, 2341234.
The mask in this case is set as follows:(234xxxx|!234111[1-5]|!2341234)
4.1.4.4 Timer example

Consider the operation of timers using the example of dialing with number overlap011 (example 1 from previous
section). Let the timer values:
L=10 sec
S=5 sec
Reception of the first digit0.The mask for such a set contains 2 rules: 011 and 0[1-4]. After reception of the
first digit of a complete match with no rule, it turns onL-timer (10 seconds) to wait for the next digit (if
within10 seconds the next digit will not be accepted, then a timeout will be triggered, and since no rule
matches, there will be a set error).
Reception of the second digit -1. Match with 6th rule 0[1-4] (prefix 01) since match with there is a rule, but it
is possible that there will be a match with5th rule - 011, then the S-timer is turned on (5 seconds) to wait for
the next digit (if within5 seconds the next digit will not be accepted, then a timeout will be triggered, and
since there is already a match with the rule, the call will be successfully routed to this mask).
Reception of the third digit -1, with the 6th rule, in this case, the match is lost and a match with the 5th rule
appears. This match is final, since there are no other rules that could match further dialing, no mask. The
call is immediately routed to5th rule.
4.1.4.5 An example of setting up a prefix with the “Subscriber capacity” type

Task
ForSMG is allocated a range of numbers: 26000 - 26199, but not all numbers can be immediately assigned
to subscribers. When a call comes in to a number from this range that is not assigned to the subscriber,
SMG will reject it with disconnect reason3 - No route to destination. But, since this numbering is local to
the gateway, it should have sent a reason in the disconnect message1 – Unallocated (unassigned)
number.
129
Solution
To be able to send the correct disconnect reason, you need to create a local numbering - configure a
prefix with the "Subscriber capacity".
For this, in the sectionNumbering planyou need to add a new prefix with the parameter value Prefix type
- "Subscriber capacity». In the settings of this prefix, add a list of masks prefix with type "Called". For the
range of numbers 26000-26199 specified in the task, the mask will be look like(26[0-1]xx).
130
4.1.5 Routing
4.1.5.1 Trunk groups

Routing → Trunk groups
A trunk group is a set of connecting lines (trunks), which can be: E flow channels1, the bandwidth of the data
transmission medium (IP channels). Through E1 flow channels alarms workQ.931, SS-7, via IP channels - SIP/
SIP-T/SIP-I/H.323 interface. For trunk group editingdouble-click with the left mouse button on
corresponding line in the group table or select a group and press the button below the list.
Fordeleting a trunk groupyou need to select a group and press the button select below the list or
menu"Objects" - "Delete object".
Maximum possible to create up to255 trunk groups.
4.1.5.1.1 Basic settings tab
To add a trunk group, click the button , then fill in the following fields:
Routing → Trunk groups →
131
-To access the trunk group, the device configuration must contain prefixes, accessing this group.
• Name -trunk group name;

• Description -description of the added trunk group;
• Composition of the group -trunk group composition:
• stream with Q.931 signaling, SS line group, SIP or H323 interfaces;
• E1 flow channels– E1 stream channels with signaling protocol Q.931, SS7;
• E1 flows from the group of SS-7 lines.
• Stream E1– selection of the E1 stream to assign a trunk group to the channels of the E1 stream, this menu active
only when selected in "The composition of the group "values"Channels of flow E1";
Routing → Trunk groups → → Basic settings
-One trunk group can only be assigned to channels within the same stream E1.
• OKS-7 line group– a group of SS-7 lines for selecting E1 streams from it. This menu is active only if you
select in the “Group composition” the value “Flows E1 from the group of OKS-7 lines;
• Channel selection order– order of channel selection during occupation in E1 streams. This menu only active
when selected"The composition of the group"values"Flows E1 from the group of lines OKS-7 ";
-You cannot simultaneously have a trunk group with a group of lines SS-7 and trunk group with
separate streams E1 from the same group of OKS-7 lines.
• local direction -if the flag is set, subscribers of this direction considered as local. Subscribers of this
direction are set to SORM control with the type and sign of the number "subscriber of this station";
• Play music on hold (MOH)– option to issue “music on hold” upon receipt a sign of putting the
subscriber on hold;
• Vocal path closing delay– artificially introduced turn-off delay voice path after the subscriber
answers.
132
4.1.5.1.2 Incoming communication tab
Routing → Trunk groups → → Incoming communication
• Incoming call barring– if the flag is set, receiving incoming calls is prohibited. Deny setting does
not terminate currently established connections;
• direct prefix– access to a prefix without parsing the number of the calling or called subscribers. It is
designed to switch all calls from one trunk group to another, regardless of the dialed number (without
creating masks in prefixes). When dialing in modeoverlap uses direct dial timers configured in the
direct prefix;
• Block when direct prefix is not available -option appears if trunk group includes flows E1 and a direct
prefix is selected. If the option is enabled, then failure of the remote (to which the direct prefix is
routed) side, stream E is turned off1 from which the initialization call came. Thus the initializing side
understands that the thread is no longer in operation and the reservation is triggered on the side of
the operator that initialized the call on the thread;
• Use voice messages -with the flag set at the time of occurrence certain event, the output of voice
messages recorded on the device is used, a detailed description is given inAppendix G: Voice
messages and music on hold MOH;
• Block transmission Connected number– prohibition of field transmissionconnected number;

• Copy CgPN to Redirection– when the flag is set, if the incoming call does not have Redirecting
number, then it will be formed from the CgPN number;
• Use Redirecting for routing– when the flag is set, the field is used Redirecting numberwhen using SS7
or Q.931 signaling protocols, or the fielddiversion protocolSIP for incoming call routing in the
numbering plan by CgPN number masks;
subscriber) to access the trunk group specified in the "Trunk group.At
133
When a call is received from an interacting node and there is no ANI information in this call, an ANI
request will be sent to the node (messageINR according to OKS-7 signaling);
• CPS alarm value– the number of calls per second, upon reaching which the the alarm is displayed in
the log. Meaning "0" - disabling the indication of an accident. Display time accidents -10 minutes after
the specified CPS threshold is exceeded;
• CPS Limitis the maximum number of calls per second that can be accepted on the trunk group.
Meaning "0" - disable call restriction. CPS value calculated as a moving average over the last3
seconds. For example, if during the first seconds will come3×CPS calls, they will be skipped, but if
there are calls in the next two seconds, they will be rejected;
• RADIUS profile -selection of the RADIUS profile to be used (profiles are configured in menu"Setting
RADIUS/ List of profiles",chapterProfile List);
• Restore calls after outgoing leg failure– if a call received via trunk group with the setting activated,
fought back not from the incoming side, thenSMG will without interrupting the conversation on
shoulder A, try to restore communication using a second call or alternative routes when the main
one is unavailable.
Inbound modifiers
• CdPN Modifiers– intended for modifications based on number analysis the called subscriber
received from the incoming channel;
• CgPN Modifiers– intended for modifications based on number analysis caller received from the
incoming channel.
4.1.5.1.3 Outgoing tab
Routing → Trunk groups → → Outgoing call
• Outgoing call barring– when the flag is set, transfer of outgoing calls prohibited. Deny
setting does not terminate currently established connections;
• Change CgPN to Redirecting– when the flag is set, the CgPN number is changed to Redirecting;
• Check access category– when the flag is set, the possibility is checked routing based on
rights defined by access categories;
• Redundant Trunk Group -specifies the trunk group to which the call routing when routing over the
current trunk group is impossible (all channels are busy or idle);
• List of Q.850 release reasons for failover– table selection"List of clearing reasons Q. 850"to configure
Q.850 release reasons for failover to a standby trunk group;
134
• RADIUS profile -selection of the RADIUS profile to be used (profiles are configured in menu"Setting
RADIUS/List of profiles",chapterProfile List).
Outgoing modifiers
transmitted to the outgoing channel;
• CgPN Modifiers– intended for modifications based on number analysis the caller transmitted to
the outgoing channel;
• Original CdPN Modifiers –intended for modifications based on analysis original called party
number (original Called party number) sent to outgoing channel;
• RedirPN Modifiers -intended for modifications based on analysis forwarding number (

redirecting number) sent to the outgoing channel;
• GenericPN Modifiers– intended for modifications based on analysis special number (generic
number) transmitted to the outgoing channel;
• LocationNumber modifiers -intended for modifications based on analysis location numbers (
location number) sent to the outgoing channel.
To create, edit and delete groups (as well as for other objects) use the menu "Objects" - "Add object",
"Objects" - "Edit object"And"Objects" - "Delete object", as well as buttons:
- "Add trunk group";
– “Edit trunk group parameters”;
– “Delete trunk group".

PPV settings
Working mode:
• Default– this setting refers to the settings in the system parameters;
• CPV– playing the standard sound of the KPV, ignoring the settings from the system parameters;
• Audio file– replacing the standard sound of the CPV with a randomly selected one that was loaded to
the step of adjusting the PPV in the menu item "System parameters" (individual sound for the
direction).
4.1.5.2 Groups of SS-7 lines

Routing → Groups of lines SS-7
-Setting up the SS-signaling protocol7 is produced in the "E1 threads" section (section Setting
up the SS-signaling protocol7 (SS7)).
135
"Group of lines OKS-7"is a set of signaling links of one direction. For creating, editing and deleting line
groups are used by the menu"Objects" - "Add object", "Objects" - "Edit object"And"Objects" - "Delete
object", as well as buttons:
- "Add line group OKS-7(LinkSet)";
– “Edit group of SS-7 lines (LinkSet)”;
– “Delete group of SS-7 lines (LinkSet)”.
136
Routing → Groups of lines SS-7→
137
Line group parameters OKS-7:
• Name– SS-7 line group name;
• Trunk group– name of the trunk group on which the group of SS-7 lines operates;
• Numbering plan– defines the numbering plan according to which the routing for this group
(this is necessary for the coordination of numbering plans);
• Scheduled Routing Profile– selection of the service profile “routing by schedule”, which is
configured in the section “Internal resources”;
• Intercity– indicates that this signaling link is associated with ATE. Installed for correct work with
the long-distance call type (used for transits toCAS alarms);
• Alarm indication– if the flag is set, in case of an accident in the signaling link OKS-7 there will be an
alarm indication (the ALARM indicator will light up on the device, the alarm will entered in the accident
log);
• Channel occupation order -the order in which the channels will be engaged when committing
outgoing calls. Possible options:
• sequentially forward;
• sequentially back;
• starting from the first forward;
• starting from last back;
• sequentially forward even;
• sequentially back even;
• sequentially forward odd;
• sequentially back odd.
-To reduce conflict situations when connecting to adjacent PBXs, it is recommended set inverse
channel occupation types.
• Reserve group of lines OKS-7– selection of a backup group of SS-7 lines. In case of unavailability the
main group of lines OKS-7 all signaling messages will be exchanged via reserve group of lines OKS-7;
• Combined mode– Combined Linkset mode, in which in this group of SS-7 lines only voice streams
are used, and the signaling is transmitted through the signaling channels of the primary and
secondary groups of the SS-7;
• Primary group of lines OKS-7 (primary)– selection of a group of SS-7 lines by signal D-channels, which
will exchange signaling messages related to this group of SS-7;
• Secondary line group OKS-7 (secondary)– selection of the second group of SS-7 lines by signal D-
channels, which will exchange signaling messages related to this group of SS-7;
-When operating in combined mode, the distribution of the signal load between the primary and
secondary group of lines OKS-7 will be even 50/50.
• OKS-7 timer profile– selection of the timer profile to be used for this groups of lines OKS-7;
• Order of streams by SLC – influences the operation of the “Channel Occupation Order” setting, when if the option
is enabled, the order of occupied threads E1 is determined by the SLC number (sorted from smallerSLC to
higher), when the option is disabled, it is determined by the E1 stream index.
138
LevelMTP2
• Emergency phasing with one signal link in a linkset –inclusion of the procedure emergency
phasing when a group of OKS-lines is put into operation7 if in this group lines OKS-7 one signal
link;
Service information (SIO)
• Network ID– indicates the type of network: international, federal, local network or reserve (usually on
RF networks, the value "Local network" is used);
Routing label
• Proprietary code (OPC)– own signaling point code;
• Counter ISUP code (DPC-ISUP)– code of the interacting signaling point of the ISUP subsystem.
SubsystemISUP
• Initialization– actions of the device when the flow is restored to work:
• Leave on block– channels remain blocked (BLO);
• Individual Unlock– a per-channel unlock command (UBL) is sent;
• Group unlock– a group channel unlock command (CGU) is sent;

• Group reset– a group channel reset (GRS) command is executed.
• REL in response to SUS– sending a Release message in response to a Suspend message;
• Send dial digit to IAM on overlap– sending one digit of the number in the fieldCalled party numberIAM
messages in the overlap dialing method;
• Send no more than 15 digits to IAM -when the flag is set in the IAM message is sent no more15 digits
of the CdPN number, the remaining digits are sent in the SAM message;
• Redirecting/Original Called Presence Control for Incoming Call Forwarding –control flag
presence of fieldsRedirecting/Original Calledin an incoming IAM message with information
about forwarding, if this flag is set, then in the absence of these fields the call will be rejected;
• Ignore HOLD Indications –if flag is set, SMG will ignore CPG messages with remote hold or remote
retrieval flags;
• Passing Global Callrefs −if there is no Global Call Reference (GCR) field in the incoming leg, SMG
will generate it independently;
• Hop counter-sets the rules for working with the hop counter field, the parameter works as outgoing, and
incoming communication:
• Transit -transfer with decreasing value;
• Do not change -transfer without change;
• Meaning -the transfer is always with the assigned value;
• Ban -disable issuing hop counter on outgoing communication or ignore received parameter for
incoming.
Message indicatorsIAM
• Transmission media requirements- specifies the type of information to be delivered transmission
medium, when choosing a type"transit"the field value is taken from the incoming connection leg. In
the absence of this field in the incoming shoulder, the default value is taken"3.1 kHz audio.
139
Forward call indicators
• ISUP Preference Indicator -preference indicator change rule subsystemsISUP (ISUP preference
indicator). In the standard situation, these bits do not require changes;
• Interaction indicator– determines whether or not to change the value of the indicator interactions
(determines whether the interaction was not withISDN network);
• Call type indicator– parameter changes"National/international call indicator»at FCI.
Connection nature indicators
Satellite channel indicator– determines the presence of a satellite channel:
• Change to “no satellite” –change the indicator value tono satelliteregardless the value
• Do not change -do not change the indicator value;
• Add one satellite -the setting is used if the signaling link operates via satellite channel. In this case,
the satellite channel parameter transmitted in the indicators nature of connection will be increased
by 1.
• Enable link integrity check support– includes validation support the integrity of the channel in the
group of lines SS-7. When making a call, the called party installs a remote twist on the stream,The SMG
sends a frequency to the channel, which after passing through the channel detects at the reception. If
the frequency is detected, then the call service continues on this channel, if not, then a similar attempt
is made on the next channel. In the case of three unsuccessful attempts (on three different channels),
the call is terminated;
• Frequency of Link Integrity Checks– sets the frequency of link integrity checks when outgoing calls via
SS-Line Group7. For example, a value of 3 means that every third the outgoing call will be made with a
link integrity check.
For the gateway, you can set the correspondence of the SS categories to the ANI categories. This setting is described in the
sectionCategories of OKS.
Examples
• An example of the SMG connection diagram when operating in the SS-7 quasi-coupled mode through
signal transit points (STP).
Drawing46 - Wiring diagram of the SMG when operating in quasi-coupled mode via STP
Task
Connection needs to be madeSMG to an oncoming signaling point (SP) using two signal links. The first
signaling link must pass through the signaling transit point STP 1, and the second signaling link through
STP 2.
140
Point code: SMG = 22, STP 1 = 155, STP 2 = 166, SP = 23.
Solution
In addition to the basic settings, set in the menu"Groups of lines OKS-7"parameter"Own Code (OPC)" =22,
counter ISUP code (DPC-ISUP) =23.
Let's assume that the flow0 is connected to STP1, and stream 1 is connected to STP 2. In the stream
settings, you must specify: "Signaling protocol"SS7 (SS7), configure CIC numbering correctly and select
required time slot of thread E1 for signal D-channel, in settings"Group of lines OKS7" select the previously
created group of lines SS-7 and specify the parameter"Counter Code MTP3 (DPC-MTP3)" for flow0 equal155,
for flow 1 –166.
• An example of the SMG connection scheme when operating in the SS-7 quasi-coupled mode through the PBX
with functionsSTP.
Drawing47 - SMG connection diagram when operating in quasi-linked mode via PBX with STP (LS -
group of lines OKS-7 (Link Set))
Task
Connection must be made betweenSMG and two PBXs with STP functions (PBX/STP), upon exit failure of the
main beam1LS signaling messages must be sent between SMG and PBX/STP 1 through2LS.
Solution
Let's assume that the flow0 SMG connected to PBX/STP 1, configured with first line group OKS-7; flow 1
SMG is connected to PBX/STP 2, the second group of SS-7 lines is configured on it. IN stream settings, you
must specify: "Signaling protocol" -SS7 (OKSNo.7), correct configure numberingCIC and select the required
time slot of the E1 stream for signaling D- channel, in the configuration of the first group of lines OKS-7
required in the "Reserve group of lines" setting OKS-7" indicate the second group of SS-7 lines.
141
• Example of SMG connection diagram in combined mode.
Drawing48 - Wiring diagram for SMG in combined mode

Task
BetweenSMG and PBX/SP only have voice channels, signaling traffic is needed send via PBX/STP 1
and PBX/STP 2.
Solution
Let's assume that the flow0 SMG connected to PBX/STP 1, configured with first line group OKS-7, SMG stream
1 is connected to PBX/STP 2, the second group of SS-7 lines is configured on it, SMG stream 2 is connected to
PBX/SP, the third group of SS-7 lines is configured on it. In settings streams must be specified:"Signaling
protocol"SS7 (OKSNo.7),configure correctly numberingCIC and for streams 0 and 1 select the required time
slot of the E1 stream for signaling D- channel, in the configuration of the third group of lines OKS-7 needed in
setting"Primary group of lines OKS-7 (primary)"specifyfirstgroup of lines OKS-7 and in setting"Secondary
group of lines OKS-7 (secondary)"specifysecondgroup of lines OKS-7.
4.1.5.3 SIP/SIP-T/SIP-I interfaces, SIP profiles
4.1.5.3.1 Configuration
This section configures general stack configuration parametersSIP, customized settings for each
direction working according to the protocolSIP/SIP-T/SIP-I, and SIP- subscribers.
ProtocolSIP (Session Initiation Protocol) is a signaling protocol used in IP telephony. Provides basic call
control tasks such as opening and ending a session.
Network addressingSIP is based on the SIP URI scheme: sip:

user@host :port;uri-parameters user– SIP subscriber number;
@– separator between the number and domain of the SIP subscriber;
host– domain or IP address of the SIP subscriber;
port– UDP port on which the SIP subscriber service is running;

uri-parameters- Extra options.
142
One of the additional optionsThe SIP URI is the user=phone parameter. If this setting is present, then the
subscriber number syntaxSIP (in the user part) must comply with the TEL URI syntax described in RFC 3966.
In this case, requests will be processed, in the SIP subscriber number which will contain the characters "+",
";", "=", "?", as well as when using the protocolSIP-T if a call will be made to an international number,SMG
will add a "+" symbol in front of the number called party automatically.
Routing → InterfacesSIP→ Configuration
General configurationSIP:
• Timer T1– time to wait for a response to a request, after which the request will be sent again.
Maximum relay interval for requestsINVITE is 64*T1;
• Timer T2– maximum relay interval for responses to INVITE requests and all requests except
INVITE;
• Timer T4– the maximum time allowed for all retransmissions of the final response;
• Ringing timeout (sec)– timeout of the call being in the pre-answer state after receiving messages
18X, during which the subscriber hears a callback signal or an autoinformer phrase;
• Use Q.850 cause header for all SIP response codes (RFC 6432) - when installed flag the device analyzes
the fieldQ.850 cause in all final SIP messages. When if the flag is not set, then the fieldQ.850 cause is
only parsed into BYE and CANCEL messages;
• Ignore address in R-URI– when the flag is set, address information is ignored after the "@"
delimiter inRequest-URI, otherwise a check is made for a match of the address information from
The IP address and hostname of the device, and if they don't match, the call rejected;
• Set the specification in accordance with the requirements of Kazakhstan;

• Maintain subscriber database– when the flag is set, save information about registered subscribers to
the non-volatile memory of the gateway. It is necessary to save the database of registered subscribers
in case the device is rebooted by power supply or due to a failure. In case of reboot fromweb or CLI
gateway regardless of this settings will save the current database to non-volatile memory;
• Database retention period– setting the period for updating data in the archive database (from one
to sixteen hours);
143
ProtocolSIP defines two types of responses to a request initiating a connection (INVITE) − preliminary and
final. Class Answers2xx, 3xx, 4xx, 5xx and 6xx are final and transmitted securely - with confirmation of their
ACK message. Class Answers1xx, except response100 Trying are tentative and transmitted unreliably -
without acknowledgment (RFC3261). These responses contain information about the current stage of
processing the INVITE request, and in protocolSIP-T/SIP-I class 1xx responses encapsulate SS-7 messages,
resulting in loss of these responses are undesirable. The use of reliable provisional responses is also
mandated by the protocol.SIP (RFC3262) and is determined by the presence of the 100rel tag in the initiating
request, in which case provisional responses are confirmed by a messagePRACK.
Maximum possible to create up to255 interfaces.To create, edit, delete and moving interfacesSIP/SIP-T
menu used"Objects" - "Add object", "Objects" - "Edit object"And"Objects" - "Delete object", as well as
buttons:
- "Add interface";
– “Edit interface parameters”;
– “Remove interface»;
– “Moving interfaces up or down".

The gateway's signal processor performs the functions of coding analog voice traffic, fax/modem data into
digital signals, as well as reverse decoding. The gateway supports the following codecs:G.711A, G.711U,
G.729, T.38 protocol and CLEARMODE.
G.711– is PCM coding without speech compression. This codec should must be supported by all
manufacturersVoIP equipment. G.711A and G.711U codecs differ from each other by the coding law (A-law -
linear coding andU-law - non-linear). Coding byU-law applies in North America, and A-law applies in Europe.
G.726– is an ITU-T standard for adaptive pulse code modulation - ADPCM and describes band-aid voice
transmission16, 24, 32, and 40 kbps.G.726-32replaces G.721, which describesADPCM voice transmission
with a bandwidth of 32 kbps.
G.723.1– codec with speech information compression, provides two modes of operation: 6.3 Kbps and 5.3
kbps. codecG.723.1 has a voice activity detector and provides comfort noise generation at the far end during
the silent period (Annex A).
G.729– is also a speech compression codec and provides a bit rate of 8 kbps. Similar to codecG.723.1, G.729
codec supports voice activity detector and provides comfortable noise generation (Appendix B).
T.38is a standard that describes the transmission of facsimile messages in real time over IP networks. The
signals and data transmitted by the fax machine are encoded in T.38. In generated packets can introduce
redundancy - data from previous packets, which allows reliable fax transmission over unstable channels.
CLEARMODE– a mode in which signal encoding/decoding is not used. used for transparent transmission
of digital information64 kbps (RFC4040).
144
4.1.5.3.1.1 SIP interface settings tab

To create interfacesSIP/SIP-T menu used"Objects" - "Add object" orbutton
, when pressed, the following menu appears:
Routing → InterfacesSIP→ Configuration → → Interface customizationSIP
• Name– interface name;

• Mode– select the protocol for the interface (SIP/SIP-T/SIP-I/SIP Profile);
• Inbound RADIUS profile -select RADIUS profile for SIP interface-profile for incoming communication
(for other interfaces, profileRADIUS is assigned in the trunk group);
• Outgoing RADIUS profile -select RADIUS profile for interface SIP profile by outgoing communication
(for other interfaces, the profileRADIUS is assigned in the trunk group);
• Trunk group1– name of the trunk group that the interface belongs to;
145
• Numbering plan– defines the numbering plan in which dialing will be performed from this port (this is
necessary for the harmonization of numbering plans);
• Hostname/IP address1– IP address or host name communicating via SIP/SIP-T protocol gateway;
• Subnet mask for incoming calls– when setting the mask, the SMG will receive calls from subnet that
owns the communicating host specified in the field"Hostname/IP address". Please note that when
setting masks0.0.0.0 (/0), 255.255.255.255 (/32) or 255.255.255.254 (/31), SMG will only accept calls
from the address in the field"Host name/IP address", not from the subnet;
• SIP Signaling Destination Port1– UDP/TCP port of the interacting gateway on which it receives alarm
SIP/SIP-T;
• Port for receiving SIP signaling1– local UDP/TCP port of the device on which it receives alarmSIP/SIP-T
from the device interacting through this interface;
• SIP domain- the domain that is substituted in the fieldfromwhen making an outgoing call through the
interface and used for registrationSIP interface;
• Ignore source port for incoming calls- if the flag is not set the signaling used for signaling is checked
UDP ports of the interoperable gateway specified in the "port for receivingSIP signaling", otherwise - is
made, and if the request is receivedINVITE from another port the call is rejected. If an INVITE request is
received over TCP, no port check is performed regardless of the value settings;
• trusted network– means that the interface is connected to a trusted network. This option determines
the formation of request fieldsINVITE when calling with a hidden number caller (presentation
restricted). When the flag is set, information about the number the caller is passed in the fieldsfrom
AndP-asserted-identitytogether with information about that the number is hidden, in the fieldPrivacy:
id, otherwise, information about the caller's number is not transmitted in no field;
• Alarm indication– when the flag is set, SMG will signal an accident in case of Loss of communication
with an oncoming device. For this option to work correctly, you must set the flag "Control of the
availability of the opposite side by messagesOPTIONS" in settings protocolSIP;
• Alarm network interface– selection of a network interface for receiving and transmitting signal
SIP messages;
• Network interface for RTP– selection of a network interface for receiving and transmitting voice
traffic
• Correspondence table Q.850-cause and SIP-reply -choice of correspondence table between causes lights
outQ.850-cause and SIP-reply response codes. The correspondence tables are configured in menu
"Internal resources";
• List of SIP responses for switching to a backup TG– selection of the 4XX - 6XX class SIP response list
table to switch to the backup trunk group. Customizing the Response List Table produced in section
Internal resources;
• Scheduled Routing Profile– selection of the service profile “routing by schedule", which is
configured in the sectionInternal resources;
• Line operation mode – selection of the line operation mode to limit simultaneous connections through
this interface:
- Combined– the total number of simultaneous calls (incoming and outgoing) is taken into account
through this interface;
- Separated– incoming and outgoing calls are counted separately.
• Active compounds– the maximum number of simultaneous (incoming and outgoing) connections
through this interface. The field is displayed if the line operation mode "Combined" is selected;
• Number of incoming lines— the number of simultaneous incoming calls passing through theSIP
interface. The field is displayed if the line operation mode "Separate" is selected;
146
• Number of outgoing lines– number of simultaneous outgoing calls passing through through this
SIP interface. The field is displayed if the operating mode "Separate" is selected;
• Transport– selection of the transport layer protocol used for receiving and transmitting
messagesSIP:
• TCP preference– receive over UDP and TCP. Sending over TCP. In case it was not possible to
install connection byTCP, sent via UDP;
• UDP preference– receive over UDP and TCP. Sending packets over 1300 bytes over TCP, less than 1300 bytes
- byUDP;
• UDP-only– use only UDP protocol;
• TCP-only– use only the TCP protocol.
• Global Callref Generation– if there is no GCR in the call, it will be generated locally. If there is a CGR,
then it will be transmitted further, a new one will not be generated.Option available for protocol
onlySIP-I;
• Node ID– identifier used to generate the global Callref. Range valid values [0; 255].The
option is available only for the SIP-I protocol;
-1The field is not active in the SIP profile mode.
OptionsSTUN servers and Public IP:

network protocolSTUN(RFC 5389) allows applications behind a translation server addressesNAT, determine
your external IP address and the port associated with the internal port. used ifSMG is behind NAT. Either
STUN or Public IP can be used to determine the external address, but not both.
• Use STUN- if the flag is set, use STUN, otherwise - the specified publicIP addresses;
• STUN server IP– STUN server IP address;

• STUN server port– server port for sending requests (default - 3478);
• Request period– interval between requests (10-1800 seconds);
• Public IP address– setting specifies the public (external) address of the NAT WAN interface for
substitutions in signaling protocol messagesSIP.
Before sending a signaling message, a request is sent from the interface (Binding Request) on STUN- server,
in the response message (Binding Response) STUN server reports external IP address and port (udp) devices
thatSMG uses when generating signal messages.
Requests forThe STUN server is generated before each SIP signaling message is sent, but not more
often than the configured request period time.
In interface modeSIP profile" settingPublic IPnot used.
147
4.1.5.3.1.2 "SIP protocol settings" tab
Routing → InterfacesSIP→ Configuration → → Protocol settingSIP
Setting Options for ProtocolsSIP/SIP-T/SIP-I:

• Counter party availability control by OPTIONS messages –control function availability of direction
through requestsOPTIONS, if call direction is not available will be done through the redundant trunk
group. The function also analyzes the received response to the requestOPTIONS, which allows you not
to use those configured in this direction possibilities100rel,replacesAndtimerif the opposite side does
not support them. Parameter determines the period for transmitting requests and accepts values
from the range30-3600s;
148
• Opposite party availability control mode:
• SIP OPTIONS– with a specified interval for monitoring the opposite side, the device will send
control messageOPTIONS. This message should be followed by response from the opposite
side, if there is no response, then the direction is considered unavailable, and an emergency
state is initiated on the device;
• SIP NOTIFY– with a specified interval for monitoring the opposite side, the device will send
control messageNOTIFY. This message should be followed by response from the opposite
• UDP-CRLF– with a specified interval for monitoring the opposite side, the device will
send an empty packetUDP, peer response to an empty UPD packet is not provided,
accordingly, the alarm condition on the device will not be initiated.
-These methods also perform the function of maintaining a connection onNAT.
• Always send SDP in provisional responses- enables early opening of the vocal tract. For example, if
the flag is cleared, thenThe SMG sends a 180 response without session descriptionsSDP, and
according to this response, the outgoing side loses the CPV, with set flagThe SMG sends a 180
response with the description of the SDP session and the CPB is played incoming party;
• 'In-band signal' with 183+SDP transmission– issue SIP response 183 with SDP session description for
switching off the vocal tract when receiving fromISDN PRI messages CALL PROCEEDING or PROGRESS
containing progress indicator=8 (In-band signal);
• Local CPV instead of early-media– upon receipt of the attribute on the outgoing link connection early
switching of the channel (Early media) instead of an intracavitary voice message the caller is given a
dial tone;
• Use P-Early-Media (RFC5009)– use the P-Early-Media header defined in RFC 5009. On an outgoing call,
the device will send the P-Early-Media: supported header to the INVITE. Upon receipt of an INVITE with
the P-Early-Media: supported flag in 18X response messages header will be sentP-Early-Media:
sendrecv;
• Fill in the empty Display-Name field– if the flag is set, then upon receiving a call from absentdisplay-
name SMG will automatically fill it with the name (number) of the user, taken fromURI;
• Send DisplayName in Remote-Party-ID header -option enables/disables DisplayName substitution in

Remote-Party-ID;
• Ignore the difference between RURI and To– disable the issuance of Redirecting and Original Called numbers when
calls to OKS-7 if there are differences in the SIP RURI and To fields;
• Do not use '+' in CdPN and Diversion– disable adding + in the number if the number type is
International;
• SIP URI in Diversion header– use the SIP URI in the Diversion header instead of the TEL URI;
• Allow integrity check– allow transmission in SIP-I/T IAM with value parameterContinuity check
indication to 2.The option is available only for SIP-T and SIP-I protocols;
• Allow redirect (302) -if the flag is set, the gateway is allowed to perform forwarding after receiving a
response from this interface302. When the flag is cleared when receiving response302, the gateway
will reject the call and not forward;
• Direction to redirect server– the option is available when processing the 302 response is enabled
(parameter"Allow forwarding (302)"). Allows you to redirect a call sent by public address to the
subscriber's private address received in the response302 not using numbering plan routing. Routing is
done directly to the address from the headercontact 302 response received from the redirect server;
• Allow processing of REFER messages −the REFER request is passed to the interacting gateway to
perform the "Call transfer" service. If the flag is set, the gateway is allowed to
149
handle requestsREFER received from this interface. If the flag is unchecked, upon receiving the REFER request,
the gateway will reject the call and will not perform the “Call transfer” service;
• Allow Re-INVITE processing with a=sendonly -flag allows the call to be put on hold when receiving a
messageRe-INVITE with a=sendonly flag in SDP;
• Send caller category– selection of the method for transferring the category of the caller protocol
subscriberSIP. The following methods have been implemented:
• off– sending and receiving of the Caller ID category is disabled;
• category– send and receive caller category in a separate fieldcategoryV messageINVITE, in this
case, the SS-7 category is transmitted with values 0 - 255;
• cpc– sending and receiving the category of the caller using the "cpc=" tag, transmitted in the field
from, in this case, the ANI category is transmitted with values 1-10;
• cpc-rus– sending and receiving the category of the caller using the “cpc-rus=” tag, transmitted in
the fieldfrom,in this case, the ANI category is transmitted with values 1-10;
• Reliable delivery of pre-responses (1xx)– if the flag is set, INVITE request and pre-class responses1xx
will contain the option require: 100rel requiring guaranteed confirmation of preliminary answers;
• off– the option of reliable delivery of provisional responses is disabled;

• support– INVITE request and 1xx class provisional responses will contain the support:
100rel option;
• support+– duplicate SDP in 200 OK message when using support: 100rel;
• require– INVITE request and provisional responses of class 1xx will contain the option
require: 100rel, requiring guaranteed confirmation of provisional responses;
• require+– duplicate SDP in 200 OK message when using require: 100rel.
• DSCP for Signaling– type of service (DSCP) for signaling traffic (SIP);
-SettingsDSCP for RTPAndDSCP for SIPwill be ignored when using VLAN for transmissionRTP
and signaling. To prioritize traffic in this case, there will be usedClass of Service VLAN.
• SIP header transit– allows transit of received SIP headers to outgoing shoulder.
TimersSIP sessions (RFC 4028):

• Enable support for timers −when this flag is set, SIP session timers (RFC 4028) are supported. Session
refresh is supported by sending re-INVITE requests for sessions;
• Requested session control period (Session Expires) -time period in seconds after which the
session will be forced to end if the session is not updated in time (from90 to 64800 s,
recommended value is 1800 s);
• Minimum Session Control Period (Min SE) –minimum check interval connection health (from90
to 32000 s). This value must not exceed forced session timeoutSession expires;
• Session update side −determines the party that will carry out the update session(client(uac) -
client side (caller), server (uas) - server side (called)).
150
Registration Options1:
• Registration on the upstream server -select the type of registration on the upstream server:
• No registration -do not register on the upstream server;
• Trunk registration -registration on the upstream server with the specified in this parameters
section;
• Subscriber registration -registration on the upstream server with the data specified bookmark
"registration".This type of registration allows you to define a list of subscribers who are allowed
access through this interface;
• Transit registration (Upper registration) –transit registration of subscribers devices on the
upstream server, when this option is selectedSMG sends messagesSIP from your subscribers
through this SIP interface. When choosing a transit registration in settingsSIP profile that
requires transit registration, you must specify thisSIP interface.
• Login -the name used for authentication;

• Password -the password used for authentication;
• Username/Number –user number used as caller number subscriber when making outgoing trunk
calls;
• Default cdpn -CdPN number, which will be substituted for all calls through this interfaceSIP;
• CgPN substitution on outgoing call –if the flag is set, the caller's number (CgPN) is taken from the
parameter"Username/Number",otherwise, the CgPN number is used, received in an incoming call;
• Registration period -time period for re-registration;

• Registration Request Interval (ms) –the minimum interval between sending Regicter messages
required to protect against heavy traffic caused by simultaneous registration of a large number of
subscribers.
-1The parameter block is only available for SIP mode.
Duplication settingsSIP INVITE

In this section, you can configure the acceptance of incoming requests.INVITE with SMS text from equipment
UOVEEOS and duplicating them on the receiving serversSMS. SMPP settings are also configured here. server for
receiving messages by protocolSMPP and forwarding them to the servers for receiving SMS via protocolSIP.
Duplication is carried out as follows: after activating the option, when receiving onSIP request interface
INVITE with SMS text (determined by the presence of a body in the message with Content-Type: text/plain
or Content-Type: multipart/mixed, where text/plain is among the content), SMG over TCP will redirect it to
the duplication server. To confirm delivery, the server must respond with a message403 Forbidden. Any
other release from the server will be treated as a duplication failure with the issuance of the corresponding
alarm. The call will then end with the message403 Forbidden.
If a request is received with duplication enabledINVITE without SMS text, then INVITE will be
duplicated, and the call will be processed as usual.
• Turn on– activate duplication of INVITE requests;
-Duplication works according to the protocolTCP, so when you enable the option, you need
configure in General configurationSIP (seeGeneral SIP Configuration) setting "Transport" in
such a way as to allow work onTCP (UDP-prefer, TCP-prefer or TCP-only).
• Primary Server IP– address of the main server;

• Primary server port– port of the main server;
• Backup Server IP– backup server address;
151
• Backup server port– backup server port;
• Port for receiving SMS– port for receiving SMS via SMPP protocol. When this option is specified, the SMG will
accept connections on the specified port using the protocolSMPP and forward received messagesSMS to
duplication servers via SIP protocol. The encoding of transmitted messages in text/plain will correspond to
the encoding of the incoming message, it will be additionally specified headingsContent-Type (charset
parameter) and Content-Transfer-Encoding in the INVITE message.
Setting Options for a ModeSIP profile:
Routing → InterfacesSIP→ Configuration → InterfaceSIPNo.-0→ Setting
protocolSIP
• Opposite side availability control –direction availability control function (NAT keep-alive) using the SIP-
OPTIONS, SIP-NOTIFY or empty UDP method. The parameter defines the period passing requests and
accepting values from the range30-3600s;
control messageOPTIONS. This message should be followed by
152
response from the opposite side, if there is no response, then the direction is
considered unavailable, and an emergency state is initiated on the device;
• Register expires, min -minimum value of registration time expires;

• Register expires, maxmaximum registration time expires;
• Always send SDP in provisional responses- enables early opening of the vocal tract. For example, if
the flag is cleared, thenThe SMG sends a 180 response without session descriptionsSDP, and
according to this response, the outgoing party loses the CPV; at set flagThe SMG sends a 180
response with the description of the SDP session and the CPB is played incoming party;
• 'In-band signal' with 183+SDP transmission– issue SIP response 183 with SDP session description for
switching off the vocal tract when receiving fromISDN PRI messages CALL PROCEEDING or PROGRESS
containing progress indicator=8 (In-band signal);
• Local CPV instead of early-media– upon receipt of the attribute on the outgoing link connection early
switching of the channel (Early media) instead of an intracavitary voice message the caller is given a
dial tone;
• Use P-Early-Media (RFC5009)– use the P-Early-Media header defined in RFC 5009. On an outgoing call,
the device will send the P-Early-Media: supported header to the INVITE. Upon receipt of an INVITE with
the P-Early-Media: supported flag in 18X response messages header will be sentP-Early-Media:
sendrecv;
• Fill in the empty Display-Name field- if the flag is set, then when receiving a call from absentdisplay-
name SMG will automatically fill it with the name (number) of the user, taken fromURI;
• Ignore the difference between RURI and To– disable the issuance of Redirecting and Original Called numbers when
calls to OKS-7 if there are differences in the SIP RURI and To fields;
• Do not use '+' in CdPN and Diversion– disable adding + in the number if the number type is
International;
• SIP URI in Diversion header– use the SIP URI in the Diversion header instead of the TEL URI;
• Allow redirect (302) -if the flag is set, the gateway is allowed to perform forwarding after receiving a
response from this interface302. When the flag is cleared when receiving response302, the gateway
will reject the call and not forward;
• Allow processing of REFER messages −the REFER request is passed to the interacting gateway to perform
the "Call transfer" service. When the flag is set, the gateway is allowed to process requestsREFER received
from this interface. If the flag is unchecked, upon receiving the REFER request, the gateway will reject the
call and will not perform the service"Call transfer";
• Allow Re-INVITE processing with a=sendonly– the flag allows the call to be put on hold when receiving a
messageRe-INVITE with a=sendonly flag in SDP;
• Reliable delivery of pre-responses (1xx)– if the flag is set, INVITE request and pre-class responses1xx
will contain the option require: 100rel requiring guaranteed confirmation of preliminary answers:
• off– the option of reliable delivery of provisional responses is disabled;

• support– INVITE request and 1xx class provisional responses will contain the support:
100rel option;
153
• require– INVITE request and class 1xx provisional responses will contain the option require:
100rel requiring guaranteed confirmation of provisional responses.
• DSCP for Signaling– type of service (DSCP) for signaling traffic (SIP).
-SettingsDSCP for RTPAndDSCP for SIPwill be ignored when using VLAN for transmissionRTP and
signaling. To prioritize traffic in this case, there will be usedClass of Service VLAN.
• The maximum number of redirects between subscribers - the maximum possible number of
consecutive redirects between subscribers, default value5.
OptionsNAT
• NAT (comedia mode) - option, which is necessary for the correct operation of SIP through NAT (Network
Address Translation) when using SMG in a public network. Allows you to check data source in incomingRTP
stream and broadcast the outgoing stream to the IP address and UDP port, with which the media stream is
received;
• NAT: send SDP in 18x messages– broadcast in provisional 18x SDP replies nesting when option is
enabledNAT (comedy mode). Allows early switching of the conversational path (before the subscriber
answers) and early verification of the source data in the incomingRTP stream;
• Checking if VIA and IP address match– NAT traversal support option. When this option is enabled the
address is parsedVIA and the IP address where the request came from. If they match, the SMG will be
assume that the device is notNAT.
client side (caller), server (uas) - server side (callable));
Transit Registration Options1: (Parameter block is only available for SIP mode) profile):
• Transit registration interface– selection of SIP interface for transit registration.
-1The parameter block is available only for the SIP profile mode.
Setting Options for a ModeSIP-Q:

• Opposite side availability control –direction availability control function (NAT keep-alive) using the SIP-
OPTIONS, SIP-NOTIFY or empty UDP method. The parameter defines the period passing requests and
accepting values from the range30-3600s;
control messageOPTIONS. This message should be followed by response from the opposite
154
• DSCP for Signaling– type of service (DSCP) for signaling traffic (SIP);
• SIP header transit– allows transit of received SIP headers to outgoing shoulder.

client side (caller), server (uas) - server side (called)).
OptionsSTUN servers:
network protocolSTUN (RFC 5389) allows applications behind a translation server to addressesNAT,
determine your external IP address and the port associated with the internal port. used ifSMG is behind
NAT.
• Use STUN– when the flag is set, use STUN;
• STUN server IP– STUN server IP address;
• STUN server port– server port for sending requests (default - 3478);
• Request period– interval between requests (10-1800 seconds).
Before sending a signaling message, a request is sent from the interface (Binding Request) on STUN- server,
in the response message (Binding Response) STUN server reports external IP address and port (udp) devices
thatSMG uses when generating signal messages.
Requests forThe STUN server is generated before each SIP signaling message is sent, but not more
often than the configured request period time.
Duplication settingsSIP INVITE
In this section, you can configure the acceptance of incoming requests.INVITE with SMS text from equipment
UOVEEOS and their duplication to the receiving serversSMS. SMPP settings are also configured here. server for
receiving messages by protocolSMPP and forwarding them to the servers for receiving SMS via protocolSIP.
155
Duplication is carried out as follows: after activating the option, when receiving onSIP- request interface
INVITE with SMS text (determined by the presence of a body in the message with Content-Type: text/plain
or Content-Type: multipart/mixed, where text/plain is among the content), SMG over TCP will redirect it to
the duplication server. To confirm delivery, the server must respond with a message403 Forbidden. Any
other release from the server will be treated as a duplication failure with the issuance of the corresponding
alarm. The call will then end with the message403 Forbidden.
If a request is received with duplication enabledINVITE without SMS text, then INVITE will be
duplicated, and the call will be processed as usual.
• Turn on– activate duplication of INVITE requests;
-Duplication works according to the protocolTCP, so when you enable the option, you need
configure in General configurationSIP (seeGeneral SIP Configuration) setting "Transport" in
such a way as to allow work onTCP (UDP-prefer, TCP-prefer or TCP-only).
• Primary Server IP– address of the main server;

• Primary server port– port of the main server;
• Backup Server IP– backup server address;
• Backup server port– backup server port;
• Port for receiving SMS– port for receiving SMS via SMPP protocol. When this option is specified, the SMG will
accept connections on the specified port using the protocolSMPP and forward received messagesSMS to
duplication servers via SIP protocol. The encoding of transmitted messages in text/plain will correspond to
the encoding of the incoming message, it will be additionally specified headingsContent-Type (charset
parameter) and Content-Transfer-Encoding in the INVITE message.
156
4.1.5.3.1.3 RTP codec settings tab
Routing → InterfacesSIP→ Configuration → → Codec settings/RTP
157
Options
• Voice Activity Detector / Comfort Noise Generator (VAD/CNG)- when installed the silence detector
and the comfort noise generator are enabled. Speech activity detector allows you to disable the
transmission of conversational packetsRTP in moments of silence, thereby reducing the load in the
data network;
• RTP Source IP:Port Control –at the set setting, the flow is controlled media traffic fromIP address
and UDP port specified in the SDP session description, otherwise receive traffic from anyIP
address and UDP port;
• echo cancellation– echo cancellation mode:
• voice(default)echo cancellers are enabled in the voice information transmission mode;
• voice nlp-off– echo cancellers enabled in voice mode, non-linear NLP processor switched off. In
the case when the levels of signals at transmission and reception are very different, a weak
signal can be suppressed by a nonlinear processorNLP. To prevent suppression, this mode of
operation of echo cancellers is used;
• modem– echo cancellers are enabled in the modem mode (filtering constant signal
component is off, processor controlNLP off, generator comfort noise off);
• voice nlp-option 1– echo cancellers are enabled in the voice mode, NLP is enabled in the mode of
less intense influence on the signal than in the default mode;
more intensive influence on the signal than in the default mode;
• off-do not use echo cancellation (this mode is set by default);
• DSCP for RTP– type of service (DSCP) for RTP and UDPTL (T.38) packets;
• Timeout waiting for RTP packets -the function of monitoring the state of the speech path by the
presence of RTP traffic from the interacting device. Valid value range from 10 to 300 seconds. When
the flag is cleared, controlRTP is disabled, when set it is enabled. Control is carried out as follows: if
during the given timeout no one arrives from the oncoming deviceRTP packet and the last packet was
not a silence suppression packet, then the call rejected;
• Timeout waiting for RTP packets after receiving Silence-Suppression (multiplier) –time-out
expectationsRTP packets when using the silence suppression option. Acceptable range values from1
to 30. The coefficient is a multiplier and determines how many times the value this timeout is greater
than "Wait timeoutRTP packages". Control is exercised as follows: if during the given time from the
oncoming device noRTP packet and the last packet was a silence suppression packet, then the call is
rejected;
• RTCP packet transmission period (s) –period of time in seconds (5-65535 s.), after which the device
sends control packets using the protocolRTCP. In the absence of an established flag protocolRTCP is
not used;
• Session activity control via RTCP protocol– the function of monitoring the state of the conversational
path, takes values from the range2-255. Number of time intervals (RTCP timer), V during which
protocol packets are expectedRTCP from the opposite side. With absence packets in a given period of
time, the established connection is destroyed. At the same time, to the sideTDM and IP protocols set
the disconnect reason"cause 3 no route to destination". The value of the control period is determined
by the formula:RTCP timer * RTCP control periodseconds. If the flag is not set, the function is
disabled.
158
clear channel- a channel organized for the transparent transmission of digital data, when organizing the
device does not try to recode such a channel, but transmits it transparently. To organize such a
connection, it is necessary to obtain the field"Transmission Medium Requirement» with values:
• restricted digital info (protocolQ.931);
• unrestricted dig.info (protocolQ.931);
• video (Q.931 protocol);
• 64 kbit/s unrestricted (OKS-7 protocol).
– Clear Channel override– if the flag is set, when organizing a clear channel in SDP, the only one codec
CLEARMODE if Clear Channel operation was requested on the first leg of the call. If the flag is not set, then
SDP will always transmit the entire list of selected codecs in order of priority;
– Clear Channel transit- this is a mode that allows you to directly transfer RTP from the incoming shoulder
connection to outgoing in case of connectionSIP - SIP bypassing internal switching buses devices, thereby
completely preserving the originalRTP traffic, including packetization time;
– Video off road— this mode allows transparent transmission of video traffic between clients.
digital amplification
• Receive Gain (0.1 dB)–received signal volume, amplification/attenuation the level of the signal
received from the interacting gateway;
• Transmit Gain (0.1 dB) –transmitted signal volume, amplification/attenuation signal level transmitted
towards the interacting gateway.
AGC (Auto Gain Control)
• Compliance with ITU-T G.169 –when the option is activated, automatic amplification starts working as
requiredITU-T G.169. The default mode of operation uses several non-recommendation algorithms
that provide better suppression of background noise in the absence of speech.
Receive Gain Options

• Enable Gain -activate automatic signal amplification in the receiving path;
• Restrict during simultaneous conversation –limit the gain level if subscribers speak at the same time;
• Nominal signal level, dBm0 –the signal level to which the amplification will strive;
• Maximum gain value, dB -the maximum allowable value of the gain of the original signal;
• Minimum gain value, dB -the minimum allowable gain value of the original signal.
Transmit Gain Options

• Enable Gain -activate automatic signal amplification in the transmission path;
• Restrict during a simultaneous call– limit the gain level if subscribers speak at the same time;
• Nominal signal level, dBm0– signal level to which the amplification will tend;
• Maximum gain value, dB- the maximum allowable value of the gain of the original signal;
• Minimum gain value, dB -the minimum allowable gain value of the original signal.
159
Reception / transmissionDTMF:
• DTMF transmission method– method of DTMF transmission over IP network;
• inband-in RTP protocol packets, in-band;
• RFC2833-in RTP protocol packets, as recommended by RFC2833;
• SIP INFO -out of band, according to the SIP protocol, INFO messages are used, while the
form transmitted signalsDTMF will depend on the MIME extension type;
• SIP-NOTIFY-out-of-band, over the SIP protocol, NOTIFY messages are used. Such broadcast
DTMF is an implementation of a method that is used on Cisco equipment.
-To be able to use extension dialing during a call, make sure that similar signaling
methodDTMF is configured on the opposite gateway.
• Allow inband DTMF -the option appears for all DTMF transmission methods except inband. At disabled
option ifSMG comes in dtmf in two formats, for example in RFC2833 and inband, Thatinband will be
ignored and only the RFC2833 format will be processed
• Flash Signal Processing (RFC2833)– flag for activating FLASH signal processing by INFO, RFC2833 and
re-invite methods for VAS service operation"Call transfer";
• RFC2833PT– type of dynamic payload used for packet transmissionDTMFaccording to RFC2833.
Allowed values for use - from96 to 127. RFC2833 defines signalingDTMF via RTP protocol. This setting
must match with the same interoperable gateway setting (most commonly used values:96, 101);
• Same RFC2833 PT -if the flag is set in the case when the SMG is a party, who sentoffer SDP, waiting for
RFC2833 packets with PT value sent to us Vanswer SDP, otherwise, RFC2833 packets are expected to be
received with the PT value that SMG sent tooffer SDP;
• DTMF MIME Type– payload type used for DTMF transmission in SIP INFO packets:
• application/dtmf relay– in INFO application/dtmf-relay packets of the SIP protocol (* and # are transmitted like
symbols * and #);
• application/dtmf– in SIP INFO application/dtmf packets (* and # are transmitted as numbers 10 and
11).
Optionsjitter buffer:
• Mode– jitter buffer operation mode: fixed or adaptive;
• Minimum size, ms– fixed jitter buffer size or lower bound (minimum size) of the adaptive jitter buffer.
The range of valid values from0 to 200 ms;
• Initial size, ms– initial value of the adaptive jitter buffer. Acceptable range values from0 to 200 ms;
• Maximum size, ms– upper limit (maximum size) of adaptive jitter buffer in milliseconds. The range of
valid values is from "minimum size" to200ms;
• Adaptation period, msis the buffer adaptation time to the lower boundary in the absence of violations in
the order of the packets;
• Delete mode– buffer adaptation mode. Specifies how packages will be removed when adapting the
buffer to the lower bound:
• Soft– an intelligent scheme is used to select packages for removal that exceed threshold;
• Hard– Packets whose delay exceeds the threshold are dropped immediately.
• Removal threshold, ms –threshold for immediate removal of packages in milliseconds. With the
growth of the buffer and the packet delay exceeds this limit, the packets are immediately dropped.
The range of valid values is from the maximum size to500ms;
• Tuning mode– selection of the adjustment mode of the adaptive jitter buffer when it is increased
(smooth / instant);
160
• Size for VBD, ms -the size of the fixed jitter buffer used in transmission data in modeVBD
(modem connection). The range of valid values is from 0 to 200 ms.
Codecs:
In this section, you can select codecs for the interface and the order in which they will be used
when establishing a connection. The codec with the highest priority must be set to the top
position.
When you press the left mouse button, the line with the selected codec is highlighted. Arrows are
used to change codec priority (down up).
• Turn on– if the flag is set, use the codec specified in the opposite field;
• codec– codec used to transmit voice data. Supported codecs G.711A,
G.711U, G.729A, G.729B, G.723.1, G.726-32;
-When enabledVAD/CNG codec G.729 works like G.729B, otherwise like G729A, and codec G.
723.1 works with annex A support, otherwise - without annex A support.
• pType– load type for the codec. The field is available for editing only if G.726 codec is selected (values
allowed for use are from 96 to 127, or 2 to match with devices that do not support dynamic load type
for this codec). For other codecs it is assigned automatically;
• PTE– Packetization time is the number of milliseconds (ms) of speech transmitted in one packet.
4.1.5.3.1.4 Fax Setup and Data Transfer Tab
Routing → InterfacesSIP→ Configuration → → Fax and data setup
Data transfer:
• Use VBD-if the flag is set, create a VBD channel according to the V.152 recommendation for modem
transmission. When a signal is detectedCED is in transitionVoice band data.Clearing the flag disables
modem tone detection, but does not disable transmission. modem (the transition to the modem
codec will not be initiated, but this transition can be made by the opposite gateway);
• VBD codec -codec used for data transmission in VBD mode;
161
• Load type VBD– payload type used for data transmission in VBD mode:
• Static– use the standard value of the payload type for the codec (for the G.711A codec – load
type8, for G.711U codec – load type 0);
• 96-127– load types from the dynamic range.
Fax transmission:
• Detection mode– determines the transmission direction in which the tones are detected fax, after
which the transition to the fax codec is carried out:
• no detect fax– disables fax tone detection, but does not disable fax transmission (the transition
to the fax codec will not be initiated, but this transition can be made by the opposite gateway);
• Caller and Callee– tones are detected both during fax transmission and reception. At Fax
transmission signal detectedCNG FAX from subscriber line. When receiving a fax signal is
detectedV.21 from subscriber line;
• caller– tones are detected only during fax transmission. When transmitting a fax, it detects signal
CNG FAX from subscriber line;
• callee– tones are detected only when a fax is received. When receiving a fax, it is detected signal
V.21 from the subscriber line.
-SignalV.21 can also be detected from a transmitting fax.
• Transfer mode– selection of the protocol for fax transmission;

• Maximum fax speed transmitted over T.38 protocol- maximum speed fax transmitted using the T.38.
This setting affects the capabilities of the gateway work with high-speed fax machines. If your fax
machines support transmission at14400, and the gateway is configured to limit 9600, then the
maximum connection speed between fax machines cannot exceed 9600 baud On the contrary, fax
machines support transmission at 9600 speed, and the gateway is set to restrict14400, this setting
will not affect interaction, the maximum speed will be determined by the capabilities of the fax
machines;
• TCF Training Sequence Processing Method– set control method baud rate:
• local TCF– the method requires that the trimmer signal TCF be generated by the
receiving gateway locally. Usually used when transmitting T.38 for TCP;
• transferred TCF– the method requires that the subscript TCF signal be transmitted from the
transmitting receiving devices. Usually used when transmitting T.38 over UDP;
• Removal and insertion of padding bits for T.38 data– deletion and insertion of padding bits for non-
ECM (error correction mode) data;
• The amount of redundancy in T.38 data packets– amount of redundancy in T.38 data packets (the
number of previous packages in the subsequent package T.38). The introduction of redundancy allows
restore the transmitted data sequence at the reception if there were losses among the transmitted
packets;
• Packetization time for T.38 protocol -determines the frequency of T.38 packet formation in
milliseconds (ms). This setting allows you to adjust the size of the transmitted packet. If the
communicating gateway can receive datagrams with a maximum size of72 bytes (
maxdatagrammSize: 72), then the packetization time must be set on the SMG minimal;
• T.38 packet transit– in the case when the call is made through two SIP interfaces and Protocol T.38
for fax transmission is used in both interfaces, this setting allows transit of T packets.38 from one
interface to another with minimal delays.
162
The values of the "type of service" field (IP DSCP) for RTP, T.38 and SIP/SIP-T/SIP-I:
0 (DSCP 0x00, Diffserv 0x00) – standard send (Best Effort) – default value;
8 (DSCP 0x08, Diffserv 0x20) – class 1;
10 (DSCP 0x0A, Diffserv 0x28) - guaranteed departure, low probability of reset (Class1, AF11);
12 (DSCP 0x0C, Diffserv 0x30) – guaranteed departure, average reset probability (Class1, AF12);
14 (DSCP 0x0E, Diffserv 0x38) – guaranteed departure, high probability of reset (Class1, AF13);
16 (DSCP 0x10, Diffserv 0x40) - class 2;

18 (DSCP 0x12, Diffserv 0x48) – guaranteed departure, low probability of reset (Class2, AF21);
20 (DSCP 0x14, Diffserv 0x50) – guaranteed departure, medium reset probability (Class2, AF22);
22 (DSCP 0x16, Diffserv 0x58) – guaranteed departure, high probability of reset (Class2, AF23);

26 (DSCP 0x1A, Diffserv 0x68) - guaranteed departure, low probability of reset (Class3, AF31);
28 (DSCP 0x1C, Diffserv 0x70) – guaranteed departure, medium reset probability (Class3, AF32);
30 (DSCP 0x1E, Diffserv 0x78) - guaranteed departure, high probability of reset (Class3, AF33);

34 (DSCP 0x22, Diffserv 0x88) - guaranteed departure, low probability of reset (Class4, AF41);
36 (DSCP 0x24, Diffserv 0x90) - Guaranteed Departure, Medium Drop Probability (Class4, AF42)
38 (DSCP 0x26, Diffserv 0x98) – guaranteed departure, high probability of reset (Class4, AF43);
40 (DSCP 0x28, Diffserv 0xA0) - class 5;

46 (DSCP 0x2E, Diffserv 0xB8) - Expedited Forwarding (Class5, Expedited Forwarding). IP
precedence:
0 - IPP0 (Routine); 8 -
IPP1 (Priority); 16 -
IPP2 (Immediate); 24 -
IPP3 (Flash);
32 - IPP4 (Flash Override);
40 - IPP5 (Critical);
48 - IPP6 (Internetwork Control);
56 - IPP7 (Network Control).
163
4.1.5.3.1.5 Advanced settings tab

This section contains advanced protocol settings.SIP. With these settings, you can edit message fields
SIP according to the given rules.
Routing → InterfacesSIP→ Configuration → → Advanced settings
Field filling format

[sipheader:HEADER_NAME=operation],[sipheader:...],...
Where:
• Operations -disable, insert, or modification rule;

• HEADER_NAMEis a case-insensitive parameter, for example Accept = accept = ACCEPT. In others
parameters are case sensitive.
Modification Rules
Modification rules are described by symbols:
• $ – leave the following text;
• ! - delete the remaining text;
• + (ABV) – add the specified text;
• - (ABV) – delete the specified text.
Examples of implementation of operation rules are given in the table below.
-To implement the transferSIP headers, you must set the option "TransitSIP- headings"at that
SIP interface from which the headers will be selected.
164
Table21 — Examples of implementation of operation rules
Operation original title rule Result
Do not send Accept: application/SDP [sipheader:accept=disable]

header
Submit without change Additional headings on the [sipheader: The given heading will appear on
title from the first first shoulder: [ the second shoulder:
shoulder LIST OF MESSAGES]:
[
MASK
P-Asserted-Identity: _TITLE]=transit] Subject: test call
username@domain
[sipheader:
Subject: test call [
MASK
_TITLE]=transit]
In messagesINVITE and
200:
[sipheader:INVITE,
200:Subject=transit]
For any message:
[sipheader:Subject=transit]
Submit without change Additional headings [sipheader:P-*=transit] on the The given headings will appear
heading group from first shoulder: on the second shoulder:
first shoulder
note that
P-Asserted-Identity: sip: this rule: P-Asserted-Identity: sip:userna
username@domain me@domain
[sipheader:*=transit]
won't work
P-Called-Party-ID: sip: since the symbol * P-Called-Party-ID: sip:username
username@domain can only replace e@domain
part of the name.
Privacy: id
Subject: test call
165
Insert blanks [sipheader:insert[ RemoteIp:example.SMG

LIST
_
HEADINGS
]:RemoteIp=+(TEXT)]
In all requests:
[sipheader:insert:RemoteIp
=+(example.SMG)]
Only in requestINVITE:
[sipheader:insert,INVITE:RemoteIp=+
( example.SMG)]
Only in specified
requests (eg.
INVITE and ACK):
[sipheader:insert,INVITE,A
CK:RemoteIp=+
(example.SMG)]
Add text to the beginningAccept: application/SDP [sipheader:accept=+ Accept: application/

(application/ISUP,)$] ISUP,application/SDP
Add text to the end Accept: application/SDP [sipheader:accept=$+ Accept: application/

(,application/ISUP)] SDP,application/ISUP
Delete text Accept: application/ [sipheader:accept=- Accept: application/ISUP

SDP,application/ISUP (application/SDP,)$]
Delete from Accept: application/ [sipheader:accept=-(text)] Accept: application/SDP

specified text SDP,text/plain
Replace text Accept: application/SDP [sipheader:accept=+ Accept: application/ISUP

fully (application/ISUP)!]
Replace text Accept: application/ [sipheader:accept=-(SDP)+ Accept: application/ISUP,text/

SDP,text/plain (ISUP)$] plain
Replace text Accept: application/ [sipheader:accept=-(SDP)+ Accept: application/ISUP

discarding the data in SDP,text/plain (ISUP)!]
end
Add text To: "Ivanov AA" <sip: [sipheader:to=-(eltex)+ To: "Ivanov AA" <sip:
123@eltex > (eltexdomain.loc)$] 123@eltexdomain.loc >
166
An example of an integrated From: [sipheader:from=+ From: DISPLAY<sip:

modifications <sip: who@host >;tag=aBc (DISPLAY )-(who)+(12345)- (>) 12345@host ;user=phone>;tag
+(;user=phone>)$+ =aBc;line=abc
(;line=abc)]
Do not transferX- X-UniqueTag: 12345678 [unique-tag=disable] headerX-UniqueTag not is

UniqueTag 90abcdef 12345678 transmitted.
90abcdef
Transfer content X-UniqueTag: 12345678 [unique-tag=NewHeader- NewHeader-Name: 12345678

X-UniqueTag in another 90abcdef 12345678 Name] 90abcdef 12345678 90abcdef
header 90abcdef
The option allows We get: [siprequest:cdpn=to] Sending:

use for
routingto,
Instead ofRURI Request Line: INVITE Request Line: INVITE
sip:558018@10.22. sip:73852245673@10. 22.
128.36:5060SIP/2.0 120.40:5060SIP/
... 2.0
To: <sip:73852245673@ 10 ...
.22.1.50 To: <sip:73852245673@ 10
;user=phone> .22.120.40
;user=phone>
Activate sendingh history- [siprequest:history=true]

info in
forwarded
call
Example
[sipheader:Accept=disable],[sipheader:user-agent=disable]
In this example, all messagesSIP sent by the device through this SIP interface will be follow borderless
AcceptAnduser-agent.
-List of required message headersSIP prohibited for ignoring and transit: via, from, to, call-id, cseq,
contact, content-type, content-length.
4.1.5.3.1.6 Obtaining a Display Name from a 3rd party server via LDAP
To set up receivingDisplay Name from a third-party server, you need to add a setting in the form line in the
menu item "Advanced protocol settingsSIP".
The SMG polls the server(s) at the specified interval and keeps the current name. When called names are
requested for the initiator and destination. If there are no actual ones in the database, then the default
configured subscriber names are used (from the settingssip subscribers).
Configuration string format:

STRING::
ldap:ID:display:INTERVAL:DIRECTION:IP:PORT:LOGIN:PASSWORD:BASE[:ATTRPHONE:ATTRDISPLAY]
167
• ID– record identifier, for several interfaces there may be the same description, in in this case, the
identifier must also be the same; in particular, it solves the issue of duplicating entries for sip
profiles (when all users of one profile will have the same entry);
• INTERVAL– database update interval (minutes);

• DIRECTION- for which subscriber to apply:
• sip– value for From when calling from the SIP side and To when calling to the SIP side;
• exchange– value for To when calling from the SIP side and From when calling to the SIP side;
• * – both names are requested in one item.
• IP-LDAP server address;
• PORT– LDAP server port:
• * - for brevity, you can specify instead of the usual LDAP port 389.
• LOGIN– database user name;
• PASSWORD– database user password;
• base– path to the server subscriber base;
• ATTRPHONE– an attribute describing in the base the Number by which the name will be
searched. The parameter is optional, you can not specify: default value:telephoneNumber;
• ATTRDISPLAY– an attribute describing the DisplayName in the base. The parameter is optional, you
can not specify: default value -displayName.
Configuration line example:
Full entry: [ldap:L1:display:thirty:sip:192.168.23.187:389:cn=user,dc=smg,dc=com:userpassword:dc

=smg,dc=com:telephoneNumber:displayName]
Short entry: [ldap:L1:display:thirty:*:192.168.23.187:*:cn=user,dc=smg,dc=com:userpassword:dc=s mg,dc=com]
4.1.5.3.1.7 Using user=phone in RURI

Customization:
[siprequest:user=phone]
[siprequest:user=ip] (instead of "ip" can be anything other than "phone").
interface type Setting INRURI set ;user=phone
trunk No Yes
trunk siprequest:user=phone Yes
trunk siprequest:user=ip No
user No No
user siprequest:user=phone Yes
user siprequest:user=ip No
168
4.1.5.4 H323 interfaces
This section configures general stack configuration parametersH.3231, individual settings for each
direction working according to the protocolH.323.
ProtocolH.323– signaling protocol used in IP telephony for multimedia transmission data onpacket
networks. Provides basic management tasks call, such as opening and ending a session.
SignalingH.323is a protocol stack based on the recommendationQ.931used in ISDN. The gateway uses the
following guidelines:H.225.0AndH.245.
SMG can be used in a circuit with bothgatekeeper(Gatekeeper), and without it. Separate the license
allows you to use the gatewaySMG as a gatekeeper, and interact with the Directory gatekeeper to locate
the subscriber.
Routing → InterfacesH.323
-1The menu is available only in the software version with an H.323 license, for more information about licenses, see
Licenses.
General configurationH.323
• Device ID (Alias)– gateway name when registering with Gatekeeper;
• Network interface for signaling– selection of network interface for H.323 signaling;
• Alarm receiving port– local TCP port for receiving H.323 signaling messages.
OptionsGateKeeper
• GateKeeper– Specifies the Gatekeeper usage mode. In "remote" mode, the SMG will interact with an
external gatekeeper, in "local" mode it will act as a gatekeeper;
169
Settings for remote mode:
Routing → InterfacesH.323→ Remote mode
• Search GateKeeper– when the flag is set, automatic gatekeeper discovery method is used in multicast
mode using IP address 224.0.1.41 and UDP port 1718, otherwise this method is not used andThe
gatekeeper has a specific IP address;
• GateKeeper IP– Gatekeeper discovery on a specific IP;
• GateKeeper Port– Gatekeeper UDP port (port 1719 is used by most gatekeepers default);
• Registration time– time period in seconds for which the device registers with the Gatekeeper;
• Registration update time– period of time in seconds after which the device re-registered for
gatekeeper.
-To securely re-register the device toGatekeeper period value re-registration "Keep Alive Time»must
be set to 2/3 of the period registration "Time To Live». In this case, the parameterTime To Live»
it is recommended to set the same as onGatekeeper to re-register period value "Keep Alive
Time» gateway was not greater than or equal to "Time To Live», sent in Gatekeeper responses.
Otherwise, an incorrect setting may cause the Gatekeeper to remove registration from the
gateway before the gateway re-registers, which in turn will lead to the destruction of all active
connections established throughgatekeeper.
-When applying the settings in this section, the module is restartedH323 and all established
protocol conversationsH.323 will be terminated, also possible short-term occurrence of an
accident "H323-MODULE LOST".
170
Settings for local mode1:
Routing → InterfacesH.323→ "Local" mode
• GateKeeper H.323 ID– identifier of the local gatekeeper running on the SMG platform;
• Technology prefix– defines the default direction to which the local gatekeeper will route calls
returned from the Directory Gatekeeper that are not intended for SMG SIP subscribers. This referral
must be registered with the local Gatekeeper SMG;
• DSCP for RAS– type of service (DSCP) for signaling traffic (H.323 RAS);
• Primary Directory GatekeeperAndSecondary Directory Gatekeeper– settings for interacting with
main and backupdirectory gatekeeper;
• H.323 ID– directory gatekeeper identifier;
• IP address– IP address of the Directory Gatekeeper.
Local interactionGatekeeper with Directory Gatekeeper is performed as follows: outgoing callSMG sends
location request (RAS LRQ) to Directory Gatekeeper, Directory Gatekeeper determines the location of the
subscriber and transmits his signaling address in the messagelocation confirm (RAS LCF), if the Directory
Gatekeeper cannot determine the subscriber's location, it messagelocation reject (RAS LRJ). On an incoming
call to the SMG: The Directory Gatekeeper sends a location request (RAS LRQ) to the SMG, if the called party is
its subscriber, then the SMG sends your signaling address in the messagelocation confirm (RAS LCF). If the
called party is not subscriberSMG, then if there is a registered technology prefix, the SMG in the location
confirm message (RAS LCF) sends the signaling address of the device that registered this prefix onSMG, in the
absence of a registered technology prefix, the SMG hangs up the call messagelocation reject (RAS LRJ).
- 1The menu is available only in the software version with the H.323-GK license, more about licenses in the section
Licenses.
171
4.1.5.4.1 H.323 interface settings tab
Routing → InterfacesH.323→ → Setting up interfacesH323
• Name– interface name;

• Trunk group– selection of the trunk group to which the interface belongs;
• Numbering plan– defines the numbering plan in which dialing will be performed from this interface
(this is necessary for the coordination of numbering plans);
• Use GateKeeper– if the flag is set, this interface interacts via Gatekeeper, the settings of which are
specified in the “H323 General configuration” section;
• Hostname / IP address– IP address or hostname of the gateway interacting via the H.323 protocol;
• H323 alarm destination port– signaling TCP port of the interacting gateway, on which he receives
the signalH323;
• Network interface for RTP -selection of a network interface for receiving and transmitting voice
traffic
• Scheduled Routing Profile −selection of the service profile “Routing by schedule”, which is
configured in the section “Internal resources”;
• Active compounds– the maximum number of simultaneous (incoming and outgoing) connections
through this interface.
172
4.1.5.4.2 H.323 protocol settings tab
Routing → InterfacesH.323→ → Protocol settingH323
• Device ID (Alias)– gateway name when registering with Gatekeeper;

• fast start– if the flag is set, the “quick start” function is enabled, otherwise it is disabled. When using the
option, the description of the session for establishing a media channel is carried out according to the H.225,
otherwise according to the H.245 protocol;
• H.245 tunnel– when the flag is set, H.245 signaling tunneling through signaling channelsQ.931 enabled,
otherwise disabled;
• Name encoding method:
• Transit– recoding is not carried out (by default, it is assumed that the name VUTF-8);
• CP 1251– encoding Windows-1251;

• Siemens adaptation– ATS Siemens coding;
• AVAYA adaptation– AVAYA PBX coding;
• Latin transliteration– Russian names will be transliterated in Latin letters.
• Name passing method:

– Q931 DISPLAY –transmission in Q.931 Display element c Codeset 5;
– AVAYA DISPLAY-transmission in Q.931 Display element with Codeset 6;
– QSIG-NA –QSIG-NA (ECMA-164) protocol transfer.
• CISCO 1700 adaptation -when using the option works like this:
• Bandwidth for Adminssion Request is set to 64000
• When making an outgoing call, the following are added:
• remote alias with CgPN value
• local alias with value H.323 ID Primary Directory Gatekeeper
• Also added to the above is a local alias with the value "Device ID (Alias)"
from the general configuration H323
• An incoming call does not search for an alternative H323 interface.
173
• DSCP for signaling– type of service (DSCP) for signaling traffic (H.323);
• Number prefixes (Prefix 1, Prefix 2, Prefix 3)– numbers that SMG registers on the Gatekeeper,
depending on the settings – local or external. This table contains numbers or initial digits of numbers
SIP subscribers registered on SMG in order to toThe gatekeeper could route calls addressed to SIP
subscribers towards the SMG (for example, for subscribers100101 and 100102, it is enough to write
one common prefix 10010).
174
4.1.5.4.3 Codec/RTP settings tab
Routing → InterfacesH.323→ → Codec settings/RTP
Options:
• Voice Activity Detector / Comfort Noise Generator (VAD/CNG)- when installed the silence detector
and the comfort noise generator are enabled. Speech activity detector allows you to disable the
transmission of conversational packetsRTP in moments of silence, thereby reducing the load in the
data network;
• RTP Source IP:Port Control –at the set setting, the flow is controlled media traffic fromIP address
and UDP port specified in the SDP session description, otherwise receive traffic from anyIP
address and UDP port;
175
• echo cancellation– echo cancellation mode:
• voice (default)echo cancellers are enabled in the voice information transmission mode;
• voice nlp-off– echo cancellers enabled in voice mode, non-linear NLP processor switched off. In
the case when the levels of signals at transmission and reception are very different, a weak
signal can be suppressed by a nonlinear processorNLP. To prevent suppression, this mode of
operation of echo cancellers is used;
• modem– echo cancellers are enabled in the modem mode (filtering constant signal
component is off, processor controlNLP off, generator comfort noise off);
less intense influence on the signal than in the default mode;
more intensive influence on the signal than in the default mode;
• off-do not use echo cancellation (this mode is set by default);
• Receive Gain (0.1 dB)–received signal volume, amplification/attenuation the level of the signal
received from the interacting gateway;
• Transmit Gain (0.1 dB) –transmitted signal volume, amplification/attenuation signal level transmitted
towards the interacting gateway;
• DSCP for RTP– type of service (DSCP) for RTP and UDPTL (T.38) packets;
• Timeout waiting for RTP packets– the function of monitoring the state of the speech path by the
presence of RTP traffic from the interacting device. Valid value range from 10 to 300 seconds. When
the flag is cleared, controlRTP is disabled, when set it is enabled. Control is carried out as follows: if
during the given timeout no one arrives from the oncoming deviceRTP packet and the last packet was
not a silence suppression packet, then the call fights back;
• Timeout waiting for RTP packets after receiving Silence-Suppression (multiplier)- timeout
expectationsRTP packets when using the silence suppression option. Acceptable range values from1
to 30. The coefficient is a multiplier and determines how many times the value this timeout is greater
than "Waiting TimeoutRTP packages. Control is exercised as follows: if during the given time from the
oncoming device noRTP packet and the last packet was a silence suppression packet, then the call is
dropped;
• RTCP Packet Transmission Period(s) –period of time in seconds (5-65535 s.), after which the device
sends control packets using the protocolRTCP. In the absence of an established flag protocolRTCP is
not used;
• Session activity control via RTCP protocol– the function of monitoring the state of the conversational
path, takes values from the range2-255. Number of time intervals (RTCP timer), V during which
protocol packets are expectedRTCP from the opposite side. With absence packets in a given period of
time, the established connection is destroyed. At the same time, to the sideTDM and IP protocols, the
disconnect reason is set -"cause 3 no route to destination". The value of the control period is
determined by the formula:RTCP timer* RTCP control periodseconds. If the flag is not set, the
function is disabled;
176
BroadcastDTMF:
• DTMF transmission method– method of DTMF transmission over IP network;
• inband-in-band, in RTP voice packets;
• RFC2833– as recommended by RFC2833 as a dedicated payload in voice packagesRTP
• H.245 Alphanumeric– out of band, in H.245 protocol userInput messages, basicstring

compatibility is used for DTMF transmission;
• H.245 signal– out of band, in H.245 userInput messages, for DTMF transmission used
compatibilitydtmf;
• Q.931 Keypad IE– out-of-band, information is used for transmission and DTMF element
Keypad in the Q.931 INFORMATION message;
-To be able to use extension dialing during a call, make sure that similar signaling
methodDTMF is configured on the opposite gateway.
• RFC2833PT– type of dynamic payload used for packet transmissionDTMFaccording to RFC2833.

Allowed values for use - from96 to 127. RFC2833 defines signalingDTMF via RTP protocol. This setting
must match with the same interoperable gateway setting (most commonly used values:96, 101);
• Same RFC2833 PT– with the flag set in the case when the SMG is a party, initiating connection, packets
are expected to receiveRFC2833 with PT value sent us inOpenLogicalChannelAck, otherwise, RFC2833
packets are expected to be received with the PT value whichThe SMG sent in the
OpenLogicalChannelAck request.
Optionsjitter buffer:
• Mode– jitter buffer operation mode: fixed or adaptive;
• Minimum size, ms– fixed jitter buffer size or lower bound (minimum size) of the adaptive jitter buffer.
The range of valid values from0 to 200 ms;
• Initial size, ms– initial value of the adaptive jitter buffer. Acceptable range values from0 to 200 ms;
• Maximum size, ms– upper limit (maximum size) of adaptive jitter buffer in milliseconds. The range of
valid values is from "minimum size" to200ms;
• Adaptation period, msis the buffer adaptation time to the lower boundary in the absence of violations in
the order of the packets;
• Delete mode– buffer adaptation mode. Specifies how packages will be removed when adapting the
buffer to the lower bound:
• Soft– an intelligent scheme is used to select packages for removal that exceed threshold;
• Hard– packets whose delay has exceeded the threshold are immediately dropped;
• Removal threshold, ms –threshold for immediate removal of packages in milliseconds. With the
growth of the buffer and the packet delay exceeds this limit, the packets are immediately dropped.
The range of valid values is from "maximum size" to500ms;
• Tuning mode– selection of the adjustment mode of the adaptive jitter buffer when it is increased
(smooth / instant);
• Size for VBD, ms -the size of the fixed jitter buffer used in transmission data in modeVBD
(modem connection). The range of valid values is from 0 to 200 ms.
Codecs:
In this section, you can select codecs for the interface and the order in which they will be used
when establishing a connection. The codec with the highest priority must be set to the top
position.
177
When you press the left mouse button, the line with the selected codec is highlighted. Arrows are
used to change codec priority (down up).
• Turn on– if the flag is set, use the codec specified in the opposite field;
• codec– codec used to transmit voice data. Supported codecs G.711A,
G.711U, G.729A, G.729B, G.723.1.
-When enabledVAD/CNG codec G.729 works like G.729B, otherwise like G729A, and codec G.
723.1 works with annex A support, otherwise - without annex A support.
• pType– load type for the codec. The field is available for editing only if G.726 codec is selected (values
allowed for use are from 96 to 127, or 2 to match with devices that do not support dynamic load type
for this codec). For other codecs it is assigned automatically;
• PTE– Packetization time is the number of milliseconds (ms) of speech transmitted in one packet.
4.1.5.4.4 Fax and data settings tab
Routing → InterfacesH.323→ → Fax and data setup
Data transfer:
• Use VBD-if the flag is set, create a VBD channel according to the V.152 recommendation for modem
transmission. When a signal is detectedCED is in transitionVoice band data.Clearing the flag disables
modem tone detection, but does not disable transmission. modem (the transition to the modem
codec will not be initiated, but this transition can be made by the opposite gateway);
• VBD codec -codec used for data transmission in VBD mode;

• Load type VBD– payload type used for data transmission in VBD mode:
• Static– use the standard value of the payload type for the codec (for the G.711A codec – load
type8, for G.711U codec – load type 0);
• 96-127– load types from the dynamic range.
178
Fax transmission:
• Detection mode– determines the transmission direction in which the tones are detected fax, after
which the transition to the fax codec is carried out:
• no detect fax– disables fax tone detection, but does not prohibit fax transmission (not the
transition to the fax codec will be initiated, but this transition can be made by the opposite
gateway);
• Caller and Callee– tones are detected both during fax transmission and reception. At Fax
transmission signal detectedCNG FAX from subscriber line. When receiving a fax signal is
detectedV.21 from subscriber line;
• caller– tones are detected only during fax transmission. When transmitting a fax, it detects signal
CNG FAX from subscriber line;
• callee– tones are detected only when a fax is received. When receiving a fax, it is detected
signalV.21 from subscriber line;
-SignalV.21 can also be detected from a transmitting fax.
• Transfer mode– selection of the protocol for fax transmission;

• Maximum fax speed transmitted over T.38 protocol- maximum speed fax transmitted using the T.38.
This setting affects the capabilities of the gateway work with high-speed fax machines. If your fax
machines support transmission at14400, and the gateway is configured to limit 9600, then the
maximum connection speed between fax machines cannot exceed 9600 baud On the contrary, fax
machines support transmission at 9600 speed, and the gateway is set to restrict14400, this setting
will not affect interaction, the maximum speed will be determined by the capabilities of the fax
machines;
• T.38 data rate control method- set method baud rate control:
• local TCF– the method requires that the trimmer signal TCF be generated by the
receiving gateway locally. Usually used when transmitting T.38 for TCP;
• transferred TCF– the method requires that the trimmer signal TCF be transmitted with
transmitter to receiver. Usually used when transmitting T.38 over UDP;
• Removal and insertion of padding bits for T.38 data– deletion and insertion of padding bits for non-
ECM (error correction mode) data;
• The amount of redundancy in T.38 data packets– amount of redundancy in T.38 data packets (the
number of previous packages in the subsequent package T.38). The introduction of redundancy allows
restore the transmitted data sequence at the reception if there were losses among the transmitted
packets;
• Packetization time for T.38 protocol -determines the frequency of T.38 packet formation in
milliseconds (ms). This setting allows you to adjust the size of the transmitted packet. If the
communicating gateway can receive datagrams with a maximum size of72 bytes (
maxdatagrammSize: 72), then the packetization time must be set on the SMG minimal;
• T.38 packet transit– in the case when the call is made via two VoIP interfaces and Protocol T.38 for
fax transmission is used in both interfaces, this setting allows transit of T packets.38 from one
interface to another with minimal delays.
179
4.1.5.5 Trunk directions

A trunk direction is a set of trunk groups. When making a call to a trunk direction, you can specify
the order in which trunk groups included in the direction are selected.
Routing → Trunk directions
The menu is used to create, edit and delete trunk directions."Objects" - "Add object", "Objects" - "Edit
object"And"Objects" - "Delete object", A also buttons:
- "Add Direction";
– “Edit direction parameters”;
- "Remove Direction"".
-To access the trunk direction, the device configuration must contain prefixes providing access to
this direction.
Routing → Trunk directions→
• Name– name of the trunk direction;

• Trunk group selection mode in the list– order of trunk group selection in the direction:
180
• Consistently forward– all trunk groups included in the composition of the direction, starting
from the first in the list; those. the first call is sent to the first trunk group in the list, the next
to the second, and so on, then the cycle repeats;
• Sequential back– all trunk groups included in the composition of the direction, starting
with the last one in the list; those. the first call is sent to the last trunk group in the list, the
next to the penultimate one, and so on, then the cycle repeats;
• Starting from the first forward– the first free trunk group included in the the composition of the
direction, the search starts from the beginning of the list;
• Starting from the last back– the first free trunk group included in the composition of the
direction, the search starts from the end of the list.
• local direction -if the flag is set, subscribers of this direction considered as local. Subscribers of this
direction are set to SORM control with the type and sign of the number "subscriber of this station".
List of trunk groups in the direction:
Routing → Trunk directions → → List of trunk groups in direction →
The following buttons are used to add and remove trunk groups:
- "Add";
- "Delete".
Arrows are used to change the order of trunk groups in the list. (down up).
181
4.1.5.6 Interfaces V5.2
The menu is intended for setting interface parametersV5.2. In order to add to configuration of a new
interface, follows with the highlighted item "InterfacesV5.2" on the left side
windows press the button on the panel. The number of created interfaces must correspond to the
number of station offsets.
4.1.5.6.1 Interface Options tab

Routing → InterfacesV5.2→ Interface selection → Interface options
• Name– interface display name;

• Primary stream E1– Primary stream for V5.2 interface;
• Secondary flow E1– secondary stream for V5.2 interface;
• Interface ID– interface identifier;
• Variant ID– provisioning option in the initial configuration;
• C-chan ID– logical C-channel identifier;
• PSTN link– number of the stream to which the PSTN protocol will be assigned;
• PSTN ts– CI number to which the PSTN protocol will be assigned;
• Path identification– matching of E1 path IDs on the LE and AN sides during interface launch;
182
• Faster Unblocking Ports– use of the Accelerated Port Alignment mechanism during interface startup.
Possible options for accelerated unblocking ports:
• PSTN&ISTN– unblocking of PSTN and ISDN ports;

• PSTN– Unblock only PSTN ports.
• Alarm indication– when the flag is set, output a message about the emergency state;
• RADIUS profile– select a RADIUS profile for the interface.
- "Add stream E1".

When adding a new threadE1, you should specify its LInkID in the field opposite the drop-down list
streams.
To change the order of streams E1 list uses arrows (down up).
4.1.5.6.2 Subscriber list tab

This section is intended for binding created subscribersV5.2 to this V5.2 interface. Each cell for the
subscriber contains the "Address of the level3" (Layer 3 address), which is unique within the same
interface.
Routing → InterfacesV5.2→ Object → Interface List
• No.– serial number of the subscriber;

• Layer 3 address– Layer 3 subscriber address required for subscriber identification within V5.2
interface;
• Subscriber ID– unique subscriber ID;
• Subscriber name– name of the subscriber;
• Subscriber number– subscriber's telephone number.
The following buttons are used to edit the list:
• Add– add a V5.2 subscriber;
• Swap selected– swaps two selected subscribers;
• Clear selected– deletes the contents of the subscriber cell;
• Delete selected– deletes the contents of the subscriber cell.
183
4.1.5.7 Registration
4.1.5.7.1 Configuration
Registration → Registrations → Configurations
Configuring subscriber registration and authentication parameters for interfaces with a subscriber
registration type.
Registration options:
• Password -the password used for authentication;
• Username/Number –user number registered in the SIP domain;
• SIP domain– domain in which the subscriber is registered on the upstream server.
ListedSIP interfaces are assigned / removed registration binding to a specific SIP interface. This allows you to
define a list of subscribers who are allowed to make calls through this interface.
4.1.5.7.2 Monitoring
When you select an item from the dropdown list"Monitoring"a table is displayed for monitoring
subscriber registration on the upstream server.
Registration → Registrations → Monitoring

• User Number/Number –user number registered on the upstream server;
• List of SIP interfaces -list of interfaces through which access is allowed to this subscriber;
• Status -subscriber registration status (registered, not registered, registration expired);
• Reason -possible reason for not registering;

• Registration expires -the time remaining until the expiration of the registration.
184
4.1.6 Subscribers
The menu is for setting parametersSIP subscribers1.
-1The menu is available only in the software version with a SIP registrar license, more about licenses in
sectionLicenses.
4.1.6.1 SIP subscribers
4.1.6.1.1 Subscriber configuration

Subscribers →SIP subscribers→ Configuration
• Subscriber search– checking the presence of a subscriber in the database of configured SIP
subscribers, it is possible to check by name, number, AON number,IP address: Port, SIP domain, SIP
profile, PBX profile and numbering plans;
• Edit selected -by pressing the button, the transition to the group menu is carried out editing the
parameters of selected subscribers (opposite which the flag is set "Highlight"). To be able to edit, you
need to set the flag"Change" opposite the required parameter. Description of parameters for
configuration is given below;
• Delete selected– by clicking on the button, group deletion of the selected subscribers.
To create, edit and delete an entry for an individual subscriber, use the menu"Objects"
– “Add object”, “Objects” – “Edit object”And"Objects" - "Delete object", A also buttons:
- "Add subscriber";
– “Edit subscriber parameters”;
– “Delete subscriber".
185
4.1.6.1.1.1 Subscriber settings tab
Subscribers →SIP subscribers→ Configuration →
186
• Number of subscribers -number of subscribers;

• Initial title -arbitrary text description of subscribers;
• Start number -subscriber number, for a group of subscribers, each subsequent one will
assigned a number increased by one;
• Initial AON number -ANI number of the subscriber, for a group of subscribers to each subsequent
a number increased by one will be assigned;
• Use ANI number when forwarding -when using redirection, the Diversion or Redirecting
number fields will be filled with the ANI number instead of the subscriber's number;
• Caller ID number type -subscriber number type;
• Caller ID category -subscriber's ANI category;
• Line operation mode -operation mode limiting the number of simultaneous calls. Maybe take two
values: "Combined" and "Separate". In the first mode, the total number of simultaneous calls
involving the subscriber is taken into account, in the second mode, incoming and outgoing calls are
counted separately;
• Number of lines– number of simultaneous calls involving the subscriber. Field is displayed if
the mode of operation of the lines "Combined" is selected. Valid range [1;255] or 0 – no
restrictions;
• Number of incoming lines1-number of concurrent incoming calls per side subscriber. The field
is displayed if the line operation mode "Separate" is selected. Valid range [1;255] or 0 – no
restrictions;
• Number of outgoing lines1-the number of simultaneous outgoing calls from the subscriber. The
field is displayed if the line operation mode "Separate" is selected. Valid range [1;255] or 0 – no
restrictions;
• IP address: Port -IP address and port of the subscriber. If the value is set to 0.0.0.0, the subscriber
is allowed to register from anyIP addresses. Setting port to zero ignores the port which
registration comes;
• Allow calls without registration -the option becomes active only if in the option "IP Address:Port» both
address and port of the subscriber are set. If the flag is set, the subscriber will be able to do
187
calls without prior registration from the specifiedIP and port. This option does not work if selectedsip
profile "Any";
• SIP domain -determines whether the subscriber belongs to a particular domain. Transmitted by the gateway
subscriber in the parameter "host" scheme SIP URI fieldsfromAndto;
• SIP profile -select a SIP profile. The SIP profile defines most of the subscriber's settings. If you select
the "Any" profile, this will make it possible to registersip subscriber to any availablesip profiles in the
system (see sectionSIP/SIP-T/SIP-I interfaces, SIP profiles);
• PBX profile -selection of the PBX profile (see sectionPBX profiles);
• Access category -access category selection;
• Numbering plan -defines the numbering plan in which the subscriber will be located;
• Authorization -sets the authentication mode for the device:
• No– authentication is disabled;
• With REGISTER– Authentication is carried out only during registration – at the request of
REGISTER;
• With REGISTER and INVITE- Authentication is carried out both during registration and during
making outgoing calls - on requestREGISTER and INVITE;
• Login -username for authentication;
• Password -password for authentication;
• Ignore source port after registration −after registering a message from subscribers can come from any
port of the registered address;
• Subscriber service mode -sets the restriction on incoming and outgoing communication to the subscriber:
• switched off:out of service. The subscriber number will be present in the plan numbering, but
the subscriber terminal will not be able to register. Accordingly, incoming calls will be rejected
with the reasonout of order, outgoing calls cannot be initiated;
• included:switched on, all types of communication are available;

• off 1:there is incoming communication, outgoing only to special services;
• off 2:there is no incoming communication, outgoing only to special services;
• prohibition 1:complete ban on incoming and outgoing calls. Calls will be routed to
numbering plan, but will be rejected;
• prohibition 2:a complete ban on incoming and outgoing except for special services;
• prohibition 3:prohibition of incoming, outgoing are allowed;
• prohibition 4:prohibition of incoming, outgoing are allowed only within the local and
departmental communications;
• prohibition 5:incoming allowed, complete ban on outgoing;
• prohibition 6:incoming is allowed, outgoing is allowed only for special services;
• prohibition 7:incoming allowed, outgoing allowed only within the local and departmental
communications;
• prohibition 8:incoming allowed, outgoing allowed only within the local, departmental
and zonal communications;
• excluded:excluded from numbering. The number is completely excluded from subscriber
numbers numbering plan. When calling to this number, the call will be dropped due tono route
to destination or go to the appropriate prefix in the dial plan.
• Display name -the name that will be passed to display-name. The parameter also affects usagedisplay-
name as Connected Name in responses when calling to the subscriber;
• Display name usage −display name usage mode (SIP displayname). Can take values:
• Never -setting "Display name"will not be useddisplay-name is always will take the value that
was in the initiatingINVITE;
• If not accepted -if a call initiation request without display-name is received from the subscriber, then
Vdisplay-name will be substituted with whatever is configured on the SMG. Otherwise it will used
camedisplay-name;
• Always -whatever comes in the caller's request, the display-name set to SMG will be used.
188
Multiple Registration (SIP-forking)
Multiple registration of up to five clients on one account is allowed. Registration is possible both on one and
on different network interfaces. The call goes to all registered contacts at the same time. Work with priorities
(q-parameter) will be implemented in future versions.
• SIP-forkingenabling multiple registration on the subscriber;
• Number of registered contacts -allowed valid logging range on one subscriber (The range of valid
values [2; 5]).
Busy indication settings (BLF)
-ForSMG-1016M up to 500 subscriptions possible.
• Allow subscription to events −allows the subscriber to subscribe to BLF events of others subscribers;
• Number of subscribers– number of monitored numbers when the BLF service is activated;
• Monitoring group– BLF monitoring group, BLF monitoring among themselves can be carried out
subscribers included in the same monitoring group.
-1The settings appear when you select the separate mode of operation of the lines.
-Directions (local network, special service, zonal network, private network, long-distance
communication, international communication) are set when configuring the prefix in the dial plan in
fieldDirection.
Intercom call settings

• Intercom call type– type of incoming intercom call (call with automatic answer subscriber B):
• Unilateral– with an incoming intercom call, subscriber B will hear subscriber A, but subscriber A
will not hear subscriber B (one-way notification);
• Bilateral– during an incoming intercom call, both subscribers will hear each other;
• Normal call– an incoming intercom call will be made as a normal call without auto answer side
B;
• Reject– the incoming intercom call will be rejected.
• Intercom call priority– priority of an incoming intercom call over others calls;
• a regular call has priority 1;

• the intercom can be configured 1-5, the default is 3;
• notification - 7.
Examples:
• If subscriber A with priority 1 calls an already busy subscriber B (with one line
and any priority), then subscriber A will fight off;
• If subscriber A with priority 2 calls an already busy subscriber B (with one line and
any priority), then subscriber A will interrupt an already busy regular call;
any priority), but subscriber B is already busy with subscriber C with priority3, then
subscriber A will fight off;
• Notification of subscriber A must go through in any case, because. has more
high priority7.
189
• SIP header for intercom – select the SIP header that will be sent to the subscriber in message
INVITE on intercom/paging call:
• Answer-Mode: Auto;
• Alert-Info: Auto Answer;
• Alert-Info: info=alert-autoanswer;
• Alert-Info: Ring Answer;
• Alert-Info: info=RingAnswer;
• Alert-Info: Intercom;
• Alert-Info: info=intercom;
• Call-Info: =\;answer-after=0;
• Call-Info: \\;answer-after=0;
• Call-Info: ;answer-after=0;
• Pause before answer (sec)– transmission of pause time before answering intercom/paging call in
parameter "answer-after".
DVO settings
• CLIRO-service for overcoming the prohibition of issuing the number of the calling subscriber;
• Use VDO1– connection of VAS services for the subscriber. Selecting this item will table available
"Activation of VVO services":
- 1The menu is available only in the software version with an SMG-VAS license, more about licenses in the section
Licenses.
190
Activation of VET services
Subscribers →SIP subscribers→ Configuration → → Use VDO
• Forwarding unconditional– activation of unconditional forwarding service (CF Unconditional);

• Forwarding on busy– activation of call forwarding on busy service (CF Busy);
• Forward on no answer– Activation of call forwarding on non-response service (CF No Reply);
• Redirect on unavailability– activation of call forwarding on unavailability (CF Out Of Service);
• Forwarding by time– activation of the forwarding service by time;

• Call Hold– activation of the call hold service (Call Hold);
• Call Transfer– activation of the Call Transfer service;
• Trilateral Conference– activation of the three-way conference service (3WAY);
• Call pickup -activation of the Call Pickup service;
• Sequential Gathering Conferencing– activation of the conference call service with
sequential collection;
• Disconnecting a conference when the initiator disconnects– when this flag is set, the conference will be
disabled when the initiator leaves the conference. Otherwise, the conference will be saved after the
initiator hangs up and will be disconnected only when the last participant leaves it;
191
• Intercom call– activation of access to the outgoing intercom or paging call service (call with an
automatic response from party B);
• Password change– changing the password to restrict outgoing communications;
• Outbound Restriction– use the service "restriction of outgoing communications by password";
• Outgoing password communication– allows the subscriber to make a call once without restrictions communication by
entering the VVO password;
• Password activation– allows the subscriber to enter the password once to remove the restriction
outgoing connection. Re-entering the password again sets the restrictions;
• Do not disturb– allows the subscriber to set the Do Not Disturb mode and set several
whitelisted numbers that can still call him1;
• Black list– allows the subscriber to blacklist numbers so that they cannot
call him1;
• Call Park -allows the subscriber to use the call parking service;
• Putting in a slot -allows a subscriber with enabled "Call Park" service install subscribers
in the slot;
• Extraction from the slot -allows a subscriber with enabled "Call Park" service to pick up subscribers
from slots;
• Voice mail -activation of the voice mail service;
• Call Recording on Demand –activation of the call recording service on demand;
• Cancellation of all services– function required to cancel all configured numbers for redirects by
pressing the service prefix configured in the dial plan.
-1The service is available on SMG-2016 and SMG-3016.
-For the service to work"Conference on the List"you need to create a call group (sectionGroups call) and
specify in itConference number.To include all members of a call group in conference, you must dial a
service prefix with the type"conference"and number conference set in the call group.
For example, conference number "12345", service prefix DVO Conference "*71*x{1,20}#", for to
gather group members into a conference, dial "*71*12345#".
PPV settings
Allows you to customize the playback of an audio file for the subscriber individually.
Working mode:

• Audio file– replacing the standard sound of the CPV with a randomly selected one that was loaded to the
stage of setting the callback in the menu item "System parameters" (individual sound for the subscriber).
192
4.1.6.1.1.2 Additional numbers tab

The subscriber can have different numbers in different numbering plans, and when the call passes through the
numbering plan change prefix, the number is automatically changed to the subscriberCgPN on it number in the
corresponding numbering plan, for example:
The subscriber has an internal short numbering, respectively, he is registered at the gateway under a short
number, when accessing the external network, each such subscriber must be substituted asCgPN your
number in international format. Access to the external network is carried out through prefix9.
To solve this problem, you need to activate in the section"System Settings"2 plans numbering, create a list of
subscribers with short numbering on the gateway, in the settings"Additional numbers"in field"Numbering
plan #1"for each subscriber, specify its external number. In respect of numbering1 must be created to access
the external network prefix, in the dial plan 0 must be prefix created"(9x.)"with the "change numbering plan"
type, which will switch to numbering plan 1. When the subscriber dials the full number, at the beginning of
which there will be 9, the call will go through the prefix "Change of the numbering plan",when entering the
numbering plan1 he will automatically be made number changeCgPN to his external number.
Subscribers →SIP subscribers→ Configuration → Configuration selection → Additional numbers
Numbering plan #0-16 – additional number of the subscriber in the corresponding numbering plan.
4.1.6.1.2 VAE management

In this section, VAS settings for subscribers are configured.
Each subscriber is provided with VAS services, but in order to use a specific service, it must be connected to
the operator. The operator can create a maintenance plan from several VVO functions, for this, in the section
Subscriber configurationflag is set"Use DVO» and flags opposite the necessary functions of the VDO.
The subscriber can manage the status of services from his telephone set. The following features are
available:
• service activation – activation and introduction of additional data;
• service check;
• service cancellation – service deactivation.
After entering the activation code or canceling the service, the subscriber can hear either a signal
"Confirmation"(3 short beeps), or beep"Busy"(periodic signal with duration signal/pause -0.35/0.35s). Signal
"Confirmation"indicates that the service has been successfully activated or canceled, signal"Busy"– that the
subscriber is not connected to this service.
-Calling a service through VDO prefixes always ends with a pound sign "#".
193
After entering the service verification code, the subscriber can hear either a signal"Station Answer"
(continuous signal) or signal"Busy". Signal"Station Answer"indicates that the service turned on and
activated at the subscriber, signal"Busy"– that either the service is switched off or the subscriber is not
connected to this service.
The menu displays only those numbers for which the flag is set"Use DVO"in the configuration menu
(sectionSubscriber configuration).
Subscribers →SIP subscribers→ Far Eastern Department Management
194
Subscribers →SIP subscribers→ Far East Department → Object
• Forward unconditional number– phone number for unconditional service forwarding;
• Forward Busy Number– phone number for call forwarding service employment;
• Forward number on no answer– phone number for call forwarding service non-response;
• Number for forwarding on unavailability– phone number for call forwarding service inaccessibility;
• Password– a password of 4 to 8 digits for access to the communication restriction service by password;
• Password activation– when the flag is set, the password is enabled and restrictions on outgoing communications
are removed;
• Outbound Restriction– sets a ban on outgoing communications for certain types directions
with an inactive password:
• everyone is allowed– outgoing communication restriction is not active, restriction code – 0;
195
• only for special services– outgoing communication is limited to calls to special services, code
restrictions -1;
• only within local and departmental communications– outgoing communication is limited local
and departmental communications, restriction code -2;
• only within local, departmental and zonal communications- outgoing communication
limited to local, departmental and zonal communications, restriction code -3.
White List Tab- on this tab, you can activate the Do Not Disturb service and set a white list of numbers that
can make calls to the subscriber, despite the ban.
Black List Tab– on this tab, you can activate the Black List service and set a black list of numbers that
cannot make calls to the subscriber.
A detailed description of the operation and configuration of VAS services is given inAppendix H. Working with VVO
services.
4.1.6.1.3 Subscriber monitoring

When you select an item from the dropdown list"Monitoring"the subscriber state table is displayed.
Subscribers →SIP subscribers→ Monitoring
• Subscriber search -checking the presence of a subscriber in the database of configured SIP
subscribers, it is possible to check by name, number, status,SIP domain, IP address:Port;
• State -subscriber registration status (registered, not registered, registration expired);
• Name -arbitrary text description of the subscriber;

• Number -subscriber number;
• SIP domain -the domain to which the subscriber belongs;
• IP/Port-address and port of the subscriber;
• Last registration -time of last registration;
• Registration expires -the time remaining until the expiration of the registration.
At the push of a button"Reset Registration"a forced reset of the registration of selected subscribers is
carried out.
196
4.1.6.1.4 BLF monitoring

Subscribers →SIP subscribers→ MonitoringBLF
At the push of a button"Find"among the records, a search will be made for a subscriber with the specified number.
• Group name– arbitrary text description of the group;

• Subscriber number;
• BLF state– current state of the Line Seized Indication service. BLF states can take the following
values:
• idle– subscription is inactive (expired);
• early– channel occupation;
• alert– making a call;
• confirmed- the conversation is established;
• terminated– Conversation ended/absent.
• Number of observers- the current number of subscribers who are watching the state subscriber
lines.
4.1.6.2 PRI profiles

Subscribers →PRI profiles→ Object
PRI profiles are used to configure PRI subscribers:

• Profile name– PRI profile menu;
• Working mode– determines the order in which the channels are occupied:
• From the first forward;
• From last back.
• Outgoing modifiers:
197
• CgPN Modifiers– intended for modifications based on number analysis the caller transmitted to
the outgoing channel;
• Original CDPN modifiers– intended for modifications based on analysis original called party
number (original Called party number) sent to outgoing channel;
• RedirPN modifiers– intended for modifications based on analysis forwarding number (

redirecting number) sent to the outgoing channel;
• Q.931 streams– flows are selected that will be associated with PRI-subscribers.
Incoming/outgoing communication modifiers forPRI subscribers work as follows. For example, on the trunk
group of stream E1, to which PRI subscribers are attached, for incoming communication modifiers are set
CgPN (Table1) and CdPN (Table0), on the PBX profile to which PRIs are bound subscribers, modifiers are also
set for incoming communicationCgPN (Table3) and CdPN (Table2). In all tables, the selection mask is set as (
x.)
A call comes from thread E1:
1. The rule for CgPN from the table of modifiers Table1 is applied.
2. Checking the CgPN number on the PRI subscriber.
3a. If the call is not from a PRI subscriber, the call is processed as from a normal trunk, the the
remaining modifiers associated with the trunk group on the incoming link.
3b. If the call is from a PRI subscriber, the remaining modifiers associated with the trunk will be applied.
group andPBX profile, the order of applying modifiers is as follows:
– Apply CgPN rule from Table3
– Apply CdPN rule from Table1
Outgoing modifiers toPRI profiles are triggered if the call is routed onPRI subscriber associated with this
profile.
198
4.1.6.3 Dynamic caller groups
4.1.6.3.1 Configuring dynamic caller groups

This section is intended for configuring groups of dynamic subscribers.
With dynamicregistration andDigest authentication is usedRADIUS server (RFC 5090, RFC-no-challenge, draft-
sterman) for subscribers.
Subscribers → Dynamic subscriber groups → Configuration
The menu is used to create, edit and delete an entry."Objects" - "Add object", "Objects" - "Edit object"And
"Objects" - "Delete object", as well as buttons:
- "Add subscriber";
199
Subscribers → Dynamic subscriber groups → Configuration → Object
200

Dynamic subscriber group
• Number of subscribers -number of subscribers in the group;
• Name -name of the group of dynamic subscribers;
• Line operation mode -operation mode limiting the number of simultaneous calls. Maybe take two
values: "Combined" and "Separate". In the first mode, the total number of simultaneous calls
involving the subscriber is taken into account, in the second mode, incoming and outgoing calls are
counted separately;
• Number of lines– number of simultaneous calls involving the subscriber. Field is displayed if
restrictions;
• Number of incoming lines1– number of simultaneous incoming calls to the side subscriber.
The field is displayed if the line operation mode "Separate" is selected. Valid range [1;255] or 0
– no restrictions;
• Number of outgoing lines1– number of simultaneous outgoing calls from the subscriber. The field
restrictions;
• SIP domain -determines whether the subscriber belongs to a particular domain. Transmitted by the gateway
subscriber in the parameter "host" scheme SIP URI fieldsfromAndto(see sectionExample of how timers work);
• SIP profile -select a SIP profile. The SIP profile determines most of the settings subscriber. If you select
the "Any" profile, this will make it possible to registersip subscriber on any of the availablesip profiles
in the system (see sectionInterfaces SIP/SIP-T/SIP-I, SIP- profiles);

• Ignore source port after registration −after registering a message from subscribers can come from any
port;
• switched off -out of service. The subscriber number will be present in the plan numbering, but
• included -switched on, all types of communication are available;

• off 1 –there is incoming communication, outgoing only to special services;
• off 2 -there is no incoming communication, outgoing only to special services;
• prohibition 1 -complete ban on incoming and outgoing calls. Calls will be routed to
• prohibition 2 -a complete ban on incoming and outgoing except for special services;
• prohibition 3 -prohibition of incoming, outgoing are allowed;
• prohibition 4 -prohibition of incoming, outgoing are allowed only within the local and departmental
communications;
• prohibition 5 -incoming allowed, complete ban on outgoing;
• prohibition 6 -incoming is allowed, outgoing is allowed only for special services;
• prohibition 7 -incoming allowed, outgoing allowed only within the local and departmental
communications;
• prohibition 8 -incoming allowed, outgoing allowed only within the local, departmental
• excluded -excluded from numbering. The number is completely excluded from subscriber
to destination, or go to the appropriate prefix in the dial plan.
201
-1The settings appear when you select the separate mode of operation of the lines.
-Directions (local network, special service, zonal network, private network, long-distance
communication, international communication) are set when configuring the prefix in the dial plan in
fieldDirection.
Multiple Registration (SIP-forking)

Multiple registration of up to five clients on one account is allowed. Registration is possible both on one and
on different network interfaces. The call goes to all registered contacts at the same time. Work with priorities
(q-parameter) will be implemented in future versions.
• SIP-forkingenabling multiple registration on the subscriber;
• Number of registered contacts -allowed valid logging range on one subscriber (The range of valid
values [2; 5]).
Busy indication settings (BLF)
• Allow subscription to events– BLF function (Busy Lamp Field) allows you to track current state
of lines of other subscribers in real time;
• Number of subscribers– the number of subscribers who can monitor the state of the line subscriber;
• Monitoring group– BLF monitoring group, BLF monitoring among themselves can be carried out
subscribers included in the same monitoring group.
Setting up an intercom call
• Intercom call type– type of incoming intercom call (call with automatic answer subscriber B):
• Unilateral– with an incoming intercom call, subscriber B will hear subscriber A, but subscriber A
will not hear subscriber B (one-way notification);
• Bilateral– during an incoming intercom call, both subscribers will hear each other;
• Normal call– an incoming intercom call will be made as a normal call without auto answer side
B;
• Reject– the incoming intercom call will be rejected;
• Intercom call priority– priority of an incoming intercom call over others calls:
• a regular call has priority 1;

• the intercom can be configured 1-5, the default is 3;
• notification - 7.
Examples:
• If subscriber A with priority 1 calls an already busy subscriber B (with one line
and any priority), then subscriber A will fight off;
any priority), then subscriber A will interrupt an already busy regular call;
any priority), but subscriber B is already busy with subscriber C with priority3, then
subscriber A will fight off;
• Notification of subscriber A must go through in any case, because. has more
high priority7.
• SIP header for intercom– selection of the SIP header to be sent to the called party to the subscriber
in the messageINVITE on intercom/paging call:
• Answer-Mode: Auto;
202
• Alert-Info: Auto Answer;
• Alert-Info: info=alert-autoanswer;
• Alert-Info: Ring Answer;
• Alert-Info: info=RingAnswer;
• Alert-Info: Intercom;
• Alert-Info: info=intercom;
• Call-Info: =\;answer-after=0;
• Call-Info: \\;answer-after=0;
• Call-Info: ;answer-after=0.
• Pause before answer (sec)– transmission of pause time before answering intercom/paging call in
the headers"answer-after".
DVO settings:
• DVO connection -selection of the method of enabling VAS services for dynamic subscribers:
• Do not connect -do not include VAS services for dynamic subscribers;
• Individual choice -the ability to configure VAS services through the gateway configurator for each
subscriber individually. When this item is selected, a table will become available. "Activation of
VVO services" (more details in the sectionSubscriber Settings Tab);
• Via RADIUS -for dynamic subscribers, it is possible to transfer VAS settings via responses from
RADIUS servers, more details inAppendix D. Transferring VAS settings from RADIUS- servers for
dynamic subscribers.
4.1.6.3.2 Monitoring a group of dynamic subscribers

Subscribers → Groups of dynamic subscribers → Monitoring
• State -subscriber registration status (registered, not registered, registration expired);
• Group name -arbitrary text description of the group;

• SIP domain -the domain to which the subscriber belongs;
• IP/Port-address and port of the subscriber;
• Last registration -time of last registration;
• Registration expires -the time remaining until the expiration of the registration;
• Highlight -if the flag is set, this record in the table will be processed when pressing the button
"Reset registration";
• Reset Registration– forcibly reset the registration of the selected subscriber.
At the push of a button"Reset"the registration of all subscribers in the specified group will be reset. The
group is selected from the drop-down list.
203
4.1.6.3.3 VAS control of a group of dynamic subscribers

Subscribers → Groups of dynamic subscribers → VAS management

• Options -subscriber VAS parameters;
• Highlight -if the flag is set, this record in the table will be processed when pressing the button
"Reset DVO".
At the push of a button"Reset DVO"VAS settings for selected subscribers will be forcibly reset.
4.1.6.3.4 Dynamic subscriber group BLF monitoring

Subscribers → Groups of dynamic subscribers → MonitoringBFL

• Subscriber number;
• BLF state– current state of the serviceLine Seized Indication". BLF states can take the following
values:
• idle– subscription is inactive (expired);
• early– channel occupation;
• alert– making a call;
• confirmed- the conversation is established;
• terminated– Conversation ended/absent.
• Number of observers -the current number of subscribers who are watching the status subscriber
lines.
204
4.1.6.4 V5.2 subscribers

Subscribers →V5.2 subscribers→ Configuration
• Subscriber search– checking the presence of a subscriber in the database of configured V5.2
subscribers, it is possible to check by name, number, AON number,PBX Profile, Dial Plans, V52
interface;
• Edit selected -by pressing the button, the transition to the group menu is carried out editing the
parameters of selected subscribers (opposite which the flag is set "Highlight"). To be able to edit, you
need to set the flag"Change" opposite the required parameter. Description of parameters for
configuration is given below;
• Delete selected– by clicking on the button, group deletion of the selected subscribers.
To create, edit and delete an entry for an individual subscriber, use the menu"Objects"
– “Add object”, “Objects” – “Edit object”And"Objects" - "Delete object", A also buttons:
- "Add subscriber";
Link selected subscribers -add selected subscribers to the interfaceV5.2.
205
Subscribers →V5.2 subscribers→ Configuration → Object
Subscriber parameters
• Subscriber ID -unique subscriber identifier;
• Name -arbitrary text description of subscribers;
• Number -subscriber number, for a group of subscribers, each subsequent one will be assigned
number increased by one;
• Hotline (incoming communication)- set the hotline number. If the number is given, then the service
activated automatically;
• Hotline delay (incoming communication), sec- allows you to set a delay hotline
activation. Valid range [0;10];
• AON number -ANI number of the subscriber, for a group of subscribers, each subsequent one
will assigned a number increased by one;
• Use ANI number when forwarding -use the number specified in the "Number Caller ID" when
performing the call forwarding service.
• Issuance of AON -choice of format for issuing AON;
206

• off 1:there is incoming communication, outgoing only to special services;
• off 2:there is no incoming communication, outgoing only to special services;
• prohibition 1:complete ban on incoming and outgoing calls. Calls will be routed to
• prohibition 2:a complete ban on incoming and outgoing except for special services;
• prohibition 3:prohibition of incoming, outgoing are allowed;
• prohibition 4:prohibition of incoming, outgoing are allowed only within the local and
departmental communications;
• prohibition 5:incoming allowed, complete ban on outgoing;
• prohibition 6:incoming is allowed, outgoing is allowed only for special services;
• prohibition 7:incoming allowed, outgoing allowed only within the local and departmental
communications;
• prohibition 8:incoming allowed, outgoing allowed only within the local, departmental
DVO settings
• Use VDO1– connection of VAS services for the subscriber. Selecting this item will table available
"Activation of VVO services":
-1The menu is available only in the software version with an SMG-VAS license, more about licenses in the section
Licenses.
207
Subscribers →V5.2 subscribers→ Configuration → Object → Use VDO

• Call Hold– activation of the call hold service (Call Hold);

• Call Transfer– activation of the Call Transfer service;
• Trilateral Conference– activation of the three-way conference service (3WAY);
• Call pickup -activation of the call pickup service (Call Pickup);
• Sequential Gathering Conferencing– activation of the conference call service with
sequential collection;
disabled when the initiator leaves the conference. Otherwise, the conference will
208
saved after the initiator hangs up and will be disabled only when the last participant leaves it;
• Password change– changing the password to restrict outgoing communications;

• Outbound Restriction– use the service "restriction of outgoing communications by password";
• Outgoing password communication– allows the subscriber to make a call once without restrictions communication by
entering the VVO password;
• Password activation– allows the subscriber to enter the password once to remove the restriction
outgoing connection. Re-entering the password again sets the restrictions;
• Do not disturb– allows the subscriber to set the Do Not Disturb mode and set several
whitelisted numbers that can still call him1;
• Black list– allows the subscriber to blacklist numbers so that they cannot
call him1;
• Cancellation of all services– function required to cancel all configured numbers for redirects by
pressing the service prefix configured in the dial plan.
-1The service is available on SMG-2016 and SMG-3016.
Far Eastern Department
Subscribers →V5.2 subscribers→ Far Eastern Department Management
In this section, VAS settings for subscribers are configured.

Each subscriber is provided with VAS services, but in order to use a specific service, it must be connected to
the operator. The operator can create a maintenance plan from several VVO functions, for this, in the section
ConfigurationSIP subscribersflag is set"Use DVO» and flags opposite the necessary functions of the VDO.
The subscriber can manage the status of services from his telephone set. The following features are
available:
• service activation– activation and introduction of additional data;
• service check;
• service cancellation– service deactivation.
After entering the activation code or canceling the service, the subscriber can hear either a signal
"Confirmation"(3 short beeps), or beep"Busy"(periodic signal with duration signal/pause -0.35/0.35s). Signal
"Confirmation"indicates that the service has been successfully activated or canceled, signal"Busy"– that the
subscriber is not connected to this service.
After entering the service verification code, the subscriber can hear either a signal"Station Answer"
(continuous signal) or signal"Busy."Signal"Station Answer"indicates that the service is enabled and
activated for the subscriber, the signal"Busy"– that either the service is switched off or the subscriber is
not connected to this service.
The menu displays only those numbers for which the flag is set"Use DVO"in the configuration menu
(sectionConfigurationSIP subscribers).
209
Subscribers →V5.2 subscribers→ Far East Department →
• Forward unconditional number– phone number for unconditional service forwarding;
• Forward Busy Number– phone number for call forwarding service employment;
• Forward number on no answer– phone number for call forwarding service non-response;
• Number for forwarding on unavailability– phone number for call forwarding service inaccessibility;
• Password– a password of 4 to 8 digits for access to the communication restriction service by password;
• Password activation– when the flag is set, the password is enabled and restrictions on outgoing communications
are removed;
• Outbound Restriction– sets a ban on outgoing communications for certain types directions
with an inactive password:
• everyone is allowed– outgoing communication restriction is not active, restriction code – 0;
• only for special services– outgoing communication is limited to calls to special services, code
restrictions -1;
• only within local and departmental communications– outgoing communication is limited local
and departmental communications, restriction code -2;
• only within local, departmental and zonal communications- outgoing communication
limited to local, departmental and zonal communications, restriction code -3.
White List Tab- on this tab, you can activate the Do Not Disturb service and set a white list of numbers that
can make calls to the subscriber, despite the ban.
Black List Tab– on this tab, you can activate the Black List service and set a black list of numbers that
cannot make calls to the subscriber. A detailed description of the operation and configuration of VAS
services is given inAppendix H. Working with VVO services.
210
4.1.6.5 PRI subscribers

PRI subscribersare the numbers that are behind the PRI trunk (E1 flows with Q.931 signaling) and
perceivedSMG as local subscribers with the provision of some subscriber services. Routing to such
subscribers is performed without creating additional rules in the numbering plan.
Checking if the caller isPRI-subscriber, is carried out by the coincidence of the E1 Q.931 stream from which
the call came and the A-number.
Subscriber search -checking the presence of a subscriber in the database of configuredPRI subscribers,
possible check by name, number,PRI profile, PBX profile, numbering plans;
Subscribers →PRI subscribers→ Configuration
Subscriber parameters
Subscribers →PRI subscribers→ Configuration → Object
• Number of subscribers– number of subscribers;

• Initial title– arbitrary text description of subscribers;
• Start number– subscriber number, for a group of subscribers, each subsequent one will
assigned a number increased by one;
• PRI profile– selection of the PRI profile;
• RVX profile– selection of the PBX profile (see sectionPBX profiles);
• Caller ID category– subscriber's ANI category;
211
• Number of lines -the number of simultaneous calls involving the subscriber. Field is displayed if
restrictions. If the operating mode of the line "Separate" is selected, then the number of lines for
incoming / outgoing communication is selected;
• Number of incoming lines– number of simultaneous incoming calls to the side subscriber. The
field is displayed if the line operation mode "Separate" is selected. Valid range [1;255] or 0 – no
restrictions;
• Number of outgoing lines– number of simultaneous outgoing calls from the subscriber. The field
restrictions;
• Numbering plan– defines the numbering plan in which the subscriber will be located;
• Subscriber service mode– sets the restriction on incoming and outgoing communication to the subscriber:

• off 1: there is incoming communication, outgoing only to special services;
• off 2: no incoming communication, outgoing only to special services;
• ban 1: Complete ban on incoming and outgoing calls. Calls will be routed to numbering
plan, but will be rejected;
• ban 2: a complete ban on incoming and outgoing except for special services;
• ban 3: barring incoming, outgoing allowed;
• ban 4: Deny incoming calls, outgoing calls are allowed only within the local and departmental
communications;
• ban 5: incoming allowed, complete ban outgoing;
• ban 6: incoming is allowed, outgoing is allowed only for special services;
• ban 7: incoming allowed, outgoing allowed only within local and departmental
communications;
• ban 8: incoming allowed, outgoing allowed only within the local, departmental and
zonal communications;
DVO settings
• Use VDO1– connection of VAS services for the subscriber. Selecting this item will the table "Activation
of VET services" is available:
-1The menu is available only in the software version with an SMG-VAS license, more about licenses in the section
Licenses.
212
Subscribers →PRI subscribers→ Configuration → Object → Use VDO

• Forwarding by time– activation of the forwarding service by time.

A detailed description of the operation and configuration of VAS services is given inAppendix H. Working with VVO
services.
PPV settings
Allows you to customize the playback of an audio file for the subscriber individually.
Working mode:

• Audio file– replacing the standard sound of the CPV with a randomly selected one that was loaded to the
stage of setting the callback in the menu item "System parameters" (individual sound for the subscriber).
4.1.7 Internal resources
4.1.7.1 CDRs
This section configures the settings for storing detailed call records.
CDR - detailed call records, allow you to save a history of calls made through the SMG gateway. If the main
server is unavailable, CDR records are sent to the backup server (if the backup server is configured
accordingly) until communication with the main server is restored. After the connection is restored,CDR
records sent to the reserve, to the main server will not be loaded. Go to the "Internal Resources" section in
the "CDR records.
213
214
Save OptionsCDR records
• Enable saving CDRs– if the flag is set, the gateway will generate CDR- records.
Creation settingsCDR files

• Creation mode– selection of the CDR file creation mode:
• with a given periodThe CDR file is created after the specified period has elapsed since device
boot;
• once a day -CDR file is created once a day at the specified time;
• once an hour -The CDR file is generated once per hour at the specified minute.
• Saving period: Days, Hours, Minutes– the period of formation of CDR records and their storage in
device RAM;
• Add title– when the flag is set, the header is written to the beginning of the CDR file type:SMG1016.
CDR. File started at 'YYYYMMDDhhmmss', where 'YYYYMMDDhhmmss' is the start time saving records
to a file;
• hallmark- sets a distinctive feature by which it is possible to identify the device that created the entry;
• File name format– change the format of the CDR file name. The option is active only when selected.
file creation mode "once a day". It can take the following values:
• date and time -converts the file name to the form "YYYYMMDDhhmmss.cdr";
• once a day -converts the file name to "YYYYMMDD.cdr".
Local storage settings
• Save to local drive– when the flag is set, save CDR records on the local drive;
• Path to local drive– path to the local drive. When specifying a path to a local drive the menu will display
a list of folders and files on that drive. To download data to a computer, you must set the flag opposite
the required records and click"Download".In this case, the folder with the recordings will be placed in
an archive, which, in order to avoid disk overflow, is recommended to be deleted after loading. To
delete irrelevant data, you must set the flag opposite the required records and click"Delete";
Internal resources →CDR records
215
Internal resources →CDR records→ Save to local drive
• Using directories– selection of directories for storing CDR data:

• directories by dates– CDR records are stored in separate directories, directory name corresponds
to the file creation dateCDR, name format "cdrYYYYMMDD", e.g. cdr20150818;
• single directory -all CDR records are stored in a single directory cdr_all on the selected drive.
• Data retention time:Days, Hours, Minutes -the period of storage of CDR records on the local
drive.
-If the remote server for storageCDR is not available, CDR records are stored in device RAM. When
the memory is full, a warning will be triggered and then an alarm. Save indicationCDR files are
listed in the section Light indication of accidents. The limits for issuing warnings and alarms are
described in the table memory limits for savingCDR.
-When an alarm is activated, the correspondingSNMP trap.
Table of memory limits for savingCDR

For temporary storageCDR on the device is allocated a certain amount of RAM for if for some reason it is
impossible to save data on a remote server. When it is filled, the appropriate warning or alarm will be
displayed.
SMG-1016M SMG-2016 SMG-3016
Total allocated memory: 30 MB 512 MB 512 MB
Limits for issuing accidents:
- warning 512 KB 20 MB 20 MB
- accident 5 MB 85 MB 85 MB
- critical accident 15 MB 255 MB 255 MB
One entryCDR takes from 200 to 400 bytes, so 1 MB of memory holds from 2600 to 5200 records. Remote
storage settings
• Protocol -the protocol by which CDR records will be transmitted to the remote server.
Protocols supportedFTP and SCP.
216
Remote storage settings
• Save to server -if the flag is set, CDR records will be transferred to the server;
• Server -server IP address;
• Port -TCP port of the server;
• The path to the file -specifies the path to the folder on the server where the CDR records will be saved;
• Login -username to access the server;
• Password -user password to access the server.
Backup remote storage settings
CDR records will be sent to the backup server (when the backup server is configured accordingly). server)
if the main server is unavailable until communication with the main server is restored.
• Save to server -if the flag is set, CDR records will be transferred to the backup server;
• Only in case of failure on the main server– if the option is set, then saving the CDR to the standby
server will be made only if the recording on the main server fails. OtherwiseCDRs will be recorded
simultaneously on the primary and backup servers.
• Server -standby server IP address;
• Port -TCP port of the backup server;
• The path to the file -specifies the path to the folder on the standby server where the CDR- records;
• Login -username for accessing the backup server;

• Password -user password to access the backup server.
Other settings
• Save unsuccessful calls -when the flag is set, write to CDR files unsuccessful calls (not
ending with a conversation);
• Keep empty files– when the flag is set, save CDR- files;
• Transferred call duration– when the flag is set in the CDR record for forwarded call with "discinfo:
redirected call;" will set the actual duration call, when the flag is cleared, the duration will be reset to
zero;
• Change Redirection number and CgPN– the option is applicable for forwarded calls to case of
simultaneous use of fieldsCgPN and Redirecting number in the CDR record. At no fieldRedirecting
number in CDR record, CgPN is automatically replaced by Redirecting number for redirected calls;
• Duration Rounding– this option sets rounding mode for call duration in CDR records:
• To the big side– ring duration rounding mode, in which the value call duration is rounded up
when exceeding330ms;
• Downward– ring duration rounding mode, in which the value call duration is rounded down
when exceeding850ms;
• No rounding (ms included)– in this mode, call duration is not rounded and recorded
with millisecond precision.
217
Incoming number modifiers
Incoming number modifiers - modifiers that allow you to convert any fields containing subscriber
numbers in recordsCDRs that are applied to these fields before passing call through the numbering
plan.
• CDPN– intended for modifications based on the analysis of the number of the called subscriber, received
from the incoming channel;
• CgPN– intended for modifications based on the analysis of the calling number the subscriber
• RedirPN– intended for modifications based on the analysis of the subscriber number
forwarded call received from the incoming channel.
Outgoing number modifiers
Outgoing number modifiers - modifiers that allow you to convert any fields containing subscriber numbers
in recordsCDRs that are applied to these fields after passing call through the numbering plan.
• CDPN– intended for modifications based on the analysis of the number of the called subscriber,
• CgPN– intended for modifications based on the analysis of the calling number the subscriber
• RedirPN– intended for modifications based on the analysis of the subscriber number,
forwarded call, transferred to the outgoing channel.
218
4.1.7.1.1 List of used CDR fields

Internal resources →CDR records
You can select the fields that will be written to the filesCDR and adjust their order. In a collumn
“Available” displays all fields available for adding, the “Added” column displays the fields and their order
in which they will be written to filesCDR.
Below the list of fields there are buttons:
• Add all– transfers all available fields to the added column;
• Remove everything– removes all fields from the added ones;
• Default– the base set of fields remains in the added fields (see the list of fields in the section Format
Default CDRs).
Adding or removing fields is done by dragging the required fields with the left mouse button to the
corresponding column. The column "Added" has a numbering that reflects the ordinal number of the field
inCDR.
219
4.1.7.1.2 Default CDR Format

• First line– header common to the entire CDR file (the parameter is present if appropriate
setting is set);
• Subsequent lines– CDR records in the form of fields separated by a semicolon ";". Base the set of
fields is as follows:
• distinguishing feature;
• connection establishment time in YYYY-MM-DD hh:mm:ss format (in case of unsuccessful call this
parameter is equal to the disconnection time);
• call duration, sec;
• disconnect reason according to ITU-T Q.850;
• call status on disconnection;
Caller information:
• IP address;
• source type;
• description – subscriber/trunk name (TG);
• number of the caller at the entrance;
• caller's number at the exit;
Called party information:
• IP address;
• assignment type;
• description – subscriber/trunk name (TG);
• number of the called subscriber at the entrance;
• number of the called subscriber at the output;
• call arrival time in the format: YYYY-MM-DD hh:mm:ss;
• connection disconnection time in the format: YYYY-MM-DD hh:mm:ss.
4.1.7.1.3 Description of CDR fields

hallmark– user-configurable string identifying the device;
Call arrival time, call answer time, disconnect time– time of the corresponding event in the
format “YYYY-MM-DD HH:MM:SS.MSEC”;
Call duration– taken into account in seconds “SS”, when choosing the rounding method “without
rounding”, milliseconds are transmitted with a dot as a separator “SS.MSEK”;
Reason for disconnectionQ.850– numerical release code, as recommended by ITU-T Q.850;
220
Call statuses on disconnect:
• user answer– successful call;
• user called, but unanswer– unsuccessful call, the subscriber did not answer;
• unassigned number– unsuccessful call, unassigned number;
• user busy– unsuccessful call, the subscriber is busy;
• incomplete number– unsuccessful call, incomplete number;
• out of order– unsuccessful call, terminal equipment unavailable;
• unavailable trunk line– unsuccessful call, trunk unavailable;
• unavailable voice-chan– unsuccessful call, no free voice channels;
• access denied– unsuccessful call, access denied;
• RADIUS-response not received– unsuccessful call, no response was received from the RADIUS server;
• unspecified– unsuccessful call, another reason.
Caller/Called IP address– IP address if the call is made via SIP/H.323 protocols. If the call is not made
throughIP network, the field will contain the value 0.0.0.0;
Types of sources and destinations:
• SIP userSIP subscriber;

• v52-user-subscriber v5.2;
• user-service-VDO call, only for source type;
• trunk-SIP-SIP trunk;
• trunk-SS7– trunk OKS-7;
• trunk-Q.931– ISDN PRI trunk;
• trunk-H.323– H.323 trunk.
Caller Description– contains the textual name of the trunk through which the call passed or the name of
the subscriber. If the call is initiated by a VDO, then the description can take on the following meaning:
• redirection– forwarding;
• call transfer– call transfer;
• CallPickup– call pickup;
• Service Management– management of the Far East;
• Conference– conference with consecutive gathering;
• IVR– call from IVR;
• 3 way– tripartite conference;
Incoming/outgoing caller number– number of the caller at the input (before modification on the
incoming TG) or at the output (after all modifications in the incoming and outgoing TG);
Incoming/outgoing call number– callee number at the input (before modification on the incoming TG)
or at the output (after all modifications in the incoming and outgoing TG);
Redirect label:
• normal-call without forwarding;
• redirecting– the calling subscriber forwarded the call to the called subscriber;
• redirected– the caller's call was redirected to another party.
Intercept label:
• normal– the call passed without interception;
• pickup– the call was intercepted.
Disconnect Initiator Label:
• originate– the call was terminated by the caller;
• answer– the call was terminated by the called;
• internal– the call is terminated by the equipment (by the SMG itself).
221
Incoming/outgoingSS7 CIC– CIC number for the incoming/outgoing call. If the call was not
made through the jointSS7, the field will be empty;
Incoming/outgoingSIP Call ID– Call-ID for incoming/outgoing call. If the call not made
throughSIP, the field will be empty;
Incoming/outgoingSS7 category– caller category SS-7 at the entrance (up to modifications on the
Incoming/Outgoing Caller ID Category– ANI category at the input (before modification on the incoming TG) or
at the output (after all modifications in the incoming and outgoing TG);
Incoming/outgoing flow E1– number of incoming/outgoing E1 flow. If the call was made not through
stream E1, then the field will be empty;
Incoming/outgoing channel E1– number of incoming/outgoing E1 channel. If the call was made not
through E1, the field will be empty;
Entry sequence numberare two numbers separated by a hyphen. The first is the timestamp generated
when the device starts, the second is the serial number of the recordCDR;
Incoming/outgoing forwarding number– forwarder number at the input (before modification on the
RADIUS Accounting-Session-Id– the value of the Acct-Session-Id attribute sent to RADIUS;
Globalcallref– the Global Call Reference field, which is formed according to the rule: "|XX.XX.XX|
YY.YY.YY.YY.YY", where:
XX.XX.XX– OPC in the form of little-endian HEX;
YY.YY.YY.YY.YY– call sequence number in the form of little-endian HEX;

Incoming/Outgoing Dial Plan– number of the numbering plan through which the call came and went;
IdentifierUniqueTag– individual identifier of the call that is received on the way entire call progress;
Caller/Called/Incoming NAI forwarding/outgoing redirecting– indicators, indicating the belonging of

the number:
• 0 - Spare;
• 1 – Subscriber number;
• 2 - unknown;
• 3 – National (significant) number;
• 4 – International number, where:
• Local - Subscriber;
• International communication - INTERNATIONAL;
• Intercity communication - NATIONAL;
• Special services, zonal and departmental - unknown.
Call transfer label– shows call transfer label:
• <empty>;
• transferred (initial call that was subsequently transferred);
• transferring (the second call that accepted the transfer).
Blocker addressserver RADIUS– information about the call-blocking RADIUS server in following
formatIP,PORT,REPLYCODE, where
• IP– IP address of the RADIUS server barring the call;
• PORT– RADIUS server port;
• REPLYCODE– RADIUS server response code.
222
4.1.7.1.4 Sample CDR file

ExampleCDR file containing four entries. Enabled adding a header to the file and selected the following
fields:
1. Sequential number of the entry;
2. Distinguishing feature;
3. Call arrival time;
4. Call response time;
5. Call disconnection time;
6. Call duration;
7. Cause of release Q.850;
8. Call status when disconnected;
9. Disconnect initiator label;
10. Forwarding label;
11. Interception mark;
12. Caller type;
13. Description of the caller;
14. Incoming stream E1;
15. IP address of the caller;
16. Incoming caller number;
17. Outgoing number of the caller;
18. Type of callee;
19. Description of the callee;
20. Outgoing stream E1;
21. IP address of the callee;
22. Incoming call number;
23. Outgoing call number.
RADIUS Accounting-Session-Id
SMG2016. CDR. File started at '20161213115258'
20161210124301-00000;SMG 2016 ELTZ;2016-12-13 11:52:58.126;2016-12-13 11:52:58.465;2016-12-13
11:52:58.479;0.014;16;user answer;originate; normal;normal;trunk-SIP;sipp_in;;
192.168.0.123;20001;20001;trunk-SS7;TrunkSS7_00;0;0.0.0.0;10001;10001;11000321 584f7eaa 65a813f9
53681e51;
20161210124301-00001;SMG 2016 ELTZ;2016-12-13 11:52:58.134;2016-12-13 11:52:58.462;2016-12-13
11:52:58.483;0.021;16;user answer;originate; normal;normal;trunk-
SS7;TrunkSS7_01;1;0.0.0.0;20001;20001;trunk-SIP;sipp_out;;192.168.1.123;10001;10001;06000106 584f7eaa
59a880c4 5b369253;
20161210124301-00002;SMG 2016 ELTZ;2016-12-13 11:52:58.026;2016-12-13 11:53:00.049;2016-12-13
11:53:00.062;0.013;16;user answer;originate; normal;normal;trunk-SIP;sipp_in;;
192.168.0.123;20000;20000;trunk-SS7;TrunkSS7_00;0;0.0.0.0;10000;10000;11000043 584f7ea9 5068f1a1
418fbc82;
20161210124301-00003;SMG 2016 ELTZ;2016-12-13 11:52:58.034;2016-12-13 11:53:00.046;2016-12-13
11:53:00.066;0.020;16;user answer;originate; normal;normal;trunk-
SS7;TrunkSS7_01;1;0.0.0.0;20000;20000;trunk-SIP;TrunkAsterisk;;192.168.69.123;10000;10000;06000105
584f7eaa 7f14fecf 2a88c6d7.
223
4.1.7.1.5 Maximum size of CDR fields
Parameter English name Maximum field size
hallmark Device sign 63
Call arrival time setup time 63
Call Answer Time connect time 63
Call release time Disconnect time 63
Call duration duration 15
Reason for disconnectionQ.850 Release cause 4
Call status on disconnect call release info 63
Caller's IP address incoming IP address 31
Caller Type incoming type 63
Caller Description incoming description 63
Callee's IP address Outgoing IP address 31
Callable type outgoing type 63
Description of the callee outgoing description 63
Incoming caller number Incoming CgPN 41
Outgoing caller number Outgoing CgPN 41
Incoming call number Incoming CDPN 41
Outgoing call number Outgoing CDPN 41
Incoming forwarding number Incoming redirect number 41
Outgoing forwarding number Outgoing redirecting number 41
224
Redirect Label Redirecting mark 31
Intercept label pickup mark 31
Disconnect Initiator Label Release side mark 31
Incoming OKS-7 CIC Incoming SS7 CIC 15
IncomingSIP Call ID Incoming SIP Call ID 255
Outgoing SS-7 CIC Outgoing SS7 CIC 15
OutgoingSIP Call ID Outgoing SIP Call ID 255
Incoming OKS-7 category Incoming SS7 category 3
Incoming ANI category Incoming Calling party category (RUS) 3
Outgoing SS-7 category Outgoing SS7 category 3
Outgoing ANI category Outgoing Calling party category (RUS) 3
Incoming flow E1 Incoming E1 stream 3
Incoming channel E1 Incoming E1 channel 3
Outgoing stream E1 Outgoing E1 stream 3
Outgoing channel E1 Outgoing E1 channel 3
Entry sequence number sequence number 15
RADIUS Accounting-Session-Id RADIUS Accounting-Session-Id 63
Globalcallref Global callref 63
Incoming dial plan Incoming numplan 3
Outgoing dial plan Outgoing numplan 3
225
UniqueTag UniqueTag 63
NAI NAI 4
Call transfer label call transfer mark 16
226
4.1.7.2 CCS categories

Internal resources → Categories OKS-7
This section indicates the correspondence between the categories of AON and the categories of the OKS- protocol7. The
generally accepted correspondence of the categories of OKS-7 categories of caller ID of the subscriber are given below:
category OKS-7 10 - AON category1
227
4.1.7.3 Access categories

Internal resources → Access categories
Access categories are used to define the access rights of subscribers, trunk groups and other objects to each
other. Categories determine whether a call can be made from an incoming channel to an outgoing channel.
If you want to restrict access to any object, you should assign it the appropriate category; for other
categories – define in this menu the accessibility to the category assigned to the object (remove access –
uncheck the flag opposite the corresponding category, add access – set the flag opposite the corresponding
category).
Total available for customization128 access categories. Each of them is written by default permission
to access the first16 categories. Go to setting and editing the selected
categories is carried out by the button .
228
Access restriction example
To restrict access to long-distance communications, you must:
1. Select an access category for long distance communication. For convenience, you can set the name"Intercity".
InsideEarly Resources → Access Categories → About object
2. For subscribers, select 2 categories:"Subscriber with MG"And"Subscriber without MG",in which,

respectively allow/deny access to a category"Intercity"(set/uncheck the flag opposite the category "Intercity").
Internal resources → Access categories → Object
Internal resources → Access categories → Object
229
3. On the prefix of the exit to 8-ku, select a category"Intercity"and set the flag"Check access
category.
Internal resources
4. For subscribers with access to long-distance communications, assign a category"Subscriber with MG"
5. For subscribers who do not have access to long-distance communications, assign a category"Subscriber without MG".
Internal resources
230
Internal resources
-Items4 and 5 can be done through group editing of subscribers:

• set flags"Highlight"opposite the required subscribers;
• press the button"Edit selected".
Select the required parameter for editing by setting the flag opposite.
4.1.7.4 Routing by access category

When searching for a route by number masks, the numbering plan checks the availability of the prefix/
call group by access category. If the check access category flag is not set on the prefix/group, then this
route is considered unconditionally available.
Now you can create several completely identical masks leading to different prefixes with different
access categories.
In this regard, the order of mask analysis now looks like this:
1. There is a search for masks corresponding to the current number.
2. Masks are checked for availability by prefix/call group access category (new mode).
• All masks that do not match the access category are denied service.
• With the only match found, available by access category, we use this mask (new mode).
• If more than one match is found for accessibility by access category, then the query processed
according to the old existing algorithm.
3. Prefix priorities are checked (call group has unconditional priority over prefixes).
• If there is only one match found, use this mask (new mode).
• If more than one match is found, then the request is processed according to the old
the existing algorithm.
4. Accuracy is checked.
• A single mask is selected that best matches the routing rules.
231
4.1.7.5 PBX profiles

PBX profiles are used to assign additional parametersSIP subscribers.
Subscribers →PBX profiles
To create, edit and deletePBX profile used menu"Objects" - "Add object", "Objects" - "Edit object"And
– “Add profile”;
- "Edit profile";
- "Delete profile".
232
PBX profile:
Subscribers →PBX profiles→ Object
• Profile name– profile name;

• Station prefix– prefix added to the beginning of the subscriber number (CgPN) of a SIP subscriber;
• direct prefix– access to a prefix without parsing the number of the calling or called subscribers.
Designed to switch all calls fromSIP subscriber to a trunk group, configured in a direct prefix,
regardless of the dialed number (without creating masks in prefixes);
• Scheduled Routing Profile– selection of the service profile “routing by Schedule" that is
configured in the "Internal Resources" section.
Incoming connection:
• Use voice messages– when the flag is set, when certain event, the output of voice messages
recorded on the device is used, for more details, seeAppendix G: Voice messages and music on hold
MOH;
• Block the transmission of Connected number -field transfer prohibitionconnected number;
• Copy CgPN to Redlirecting -if the flag is set, if there is no Redirecting number in the incoming
call, then it will be formed from the CgPN number;
233
• Use Redirecting for routing −when the flag is set, the field is used Redirecting numberwhen using SS7
or Q.931 signaling protocols, or the fielddiversion protocolSIP for incoming call routing in the
numbering plan by CgPN number masks;
received from the subscriber equipment;
• CgPN Modifiers– intended for modifications based on number analysis caller received from the
user equipment.
Outgoing connection:
• CdPN Modifiers– intended for modifications based on number analysis the called subscriber,
before sending the call to the subscriber equipment;
• CgPN Modifiers– intended for modifications based on number analysis caller before sending
the call to the subscriber equipment.
KPV settings:
Allows you to configure the playback of an audio file for a group of subscribers who belong to a
certainPBX profile.
Working mode:
• Audio file– replacing the standard sound of the CPV with a randomly selected one that was loaded to the stage of
setting up the call center in the menu item "System parameters" (individual sound for a group of subscribers).
Timers:
• Timeout for dialing the first digit, sec– timeout waiting for the first digit, after pressing caller key
FLASH when using the "call transfer" service. After this timeout, the subscriber will receive a signal
"busy", range 5-20 seconds;
• Timeout for dialing the next digit, sec– timeout for waiting for the next digit after the first one
dialing, when using the "call transfer" service. After this timeout, the end of dialing will be
determined and the call will be routed, the range5-20 seconds;
• Timeout for issuing a "busy" signal, sec– timeout for issuing a “busy” signal in case of an unsuccessful
dialing the subscriber's number when using the "call transfer" service. After this timeout, the call will
be switched to the subscriber who is on hold;
• Call answer timeout, sec (for V5.2 subscribers)– subscriber response timeout for incoming call, after
its expiration, the caller will be disconnected;
• Hold timeout, sec (for V5.2 subscribers)– subscriber's state timeout retention.
Timers DVO:
• Forwarding timeout on no response (CFNR), sec– timeout after which the subscriber after receiving a
call to it, the VAS service "forwarding on no answer" will work, the range 5 - 60 seconds;
• Timeout of keeping the participant in the parking lot, sec –timeout after which the subscriber after
installing it in the parking slot, a callback will be triggered on the initiator of installing it in the slot.
Signal parametersflash:
• Accept as on-hook– the flash signal will be perceived as disconnection;
• flash1,2,3– selection of the block of parameters of the flash signal. The parameter block itself is set to AN.
234
4.1.7.6 Modifier tables

Internal resources → Modifier tables
This table displays all the created modifiers and shows which objects they are assigned to.
The menu is used to create, edit and delete a modifier."Objects" - "Add object", "Objects" - "Edit object"And
- "Add modifier";
– “Edit modifier parameters”;
- Remove modifier»;
- "Add modifier by copying".

General modifier table settings:
Internal Resources → Modifier Tables → Object
• Name– display name of the table;

• long timer– dialing timeout in overlap mode;
• short timer– timeout for dialing a digit in the overlap mode;
• Modifiers– list of modifiers used in the table.
235
To assign/edit the parameters of the created modifier, select
corresponding line and click .
In order to confirm the change of the modifier parameters, it is necessary to press the button
"Apply", to exit without saving changes, press the button"Cancel".
To test the modifier, you can click on the link "Check number» under the table modifiers. The verification
procedure is described in the sectionChecking the work of modifiers.
4.1.7.6.1 Number selection tab
Internal Resources → Modifier Tables → Object →
• Modifier for SORM– hides the display of modifications that are not used when working with SORM;
• Description– description of the modifier;

• Number mask– template or set of templates against which the subscriber number is compared (syntax masks are
described in the sectionDescription of the number mask and its syntax);
• Type of number -subscriber number type:
• subscriber– subscriber number (SN) in E.164 format;
• national-national number. Number format: NDC + SN, where NDC is the geographical area code zones;
• International-international number. Number format: CC + NDC + SN, where CC is the country code;
• Network specific -special network number;
• Unknown-indefinite number type;
• Any -modification will be made on a number with any type;
• Unsupported-number type not supported on SMG.
• Caller ID category– subscriber's ANI category.
236
4.1.7.6.2 General modification tab
Internal Resources → Modifier Tables → Object → → General modification
• Modification example- at the push of a button viewing the final

modification results after applying the specified modification rules;
• Access category– allows to modify the access category;
• Numbering plan– allows you to change the numbering plan in which the call will be made
further routing (this is necessary for the coordination of numbering plans).
4.1.7.6.3 CdPN/Original CdPN Modification tab
Internal Resources → Modifier Tables → Object → → ModificationCDN/Original

CDPN
• Modification Rule for CdPN/Original CdPN– callee number translation rule subscriber. The syntax used
is described in the sectionModification Rule Syntax, examples use in Appendix B. This rule also applies
to modifying the original called party number (original Called party number), if this table modifiers
selected in the "trunk group" section for modificationOriginal CDPN;

modification results after applying the specified modification rules. Instead of a number
123456789, entered in the example to check the rules, it is recommended to set the number above
which is planned to be modified;
237
• type of number– callee number type conversion rule:
• Unknown-indefinite number type;
• subscriber– subscriber number (SN) in E.164 format;
• International-international number. Number format: CC + NDC + SN, where CC is the country code;
• Network specific -special network number;
• Do not change -leave the number type unchanged.
• Numbering plan type– numbering plan type conversion rule:
• Do not change -leave the number type unchanged;
• Unknown-undefined dial plan type;
• Isdn/telephony– numbering plan according to ITU-T E.164 recommendation;
• Private-private numbering plan.
238
4.1.7.6.4 CgPN/RedirPN/Generic/Location Modification tab
Internal Resources → Modifier Tables → Object → → ModificationCDN/RedirPN/

Generic/Location
• Modification rule for CgPN/RedirPN/Generic/Location– number conversion rule called subscriber. The
syntax used is described in the sectionModification Rule Syntax, examples of use in Appendix B. This
rule also applies to forwarding number modifications (redirecting number), if this table modifiers
selected in the "trunk group" section for modificationRedirPN; to modify the Generic Number, if
selected in the GenericPN modifications section; to modify the Location Number, if selected in the
modification section of the LocationNumber;

modification results after applying the specified modification rules. Instead of a number
123456789, entered in the example to check the rules, it is recommended to set the number above
which is planned to be modified;
• type of number– caller number type conversion rule;
• presentation– caller representation transformation rule;
• Screen– caller shield indicator conversion rule;
• Caller ID category– caller category conversion rule;
• Numbering plan type– numbering plan type conversion rule:
• Do not change -leave the number type unchanged;
• Unknown-undefined dial plan type;
• Isdn/telephony– numbering plan according to ITU-T E.164 recommendation;
• Private-private numbering plan.
239
4.1.7.6.4.1 Modification rule syntax

The modification rule is a set of special characters that define number changes:
• '.'And'-': special characters that indicate that the digit at this position of the number is deleted, and on
it place shifted numbers following next;
• 'X','x': special characters indicating that the digit at the given position remains unchanged
(mandatory presence of a number in this position);
• '?': a special character indicating that the digit at the current position remains unchanged
(optional presence of a number in this position);
• '+': special character meaning that all characters between this position and the next special
character (or the end of the sequence) are inserted into the number at the specified place;
• '!': special character indicating the end of parsing, all further digits of the number are cut off;
• '$': special character indicating the end of parsing, all further digits of the number are used
unchanged;
• 0-9, D, # and *(not having a special character in front of them'+'): information characters that
replace the digit in the number at this position.
Modification examples:
Adding an area code383 to number 2220123
Modifier:+383
Result:38322201234
Replacing the country code with7 in room

83832220123 Modifier:7
Result:738322201234
Replacing the third digit of the number

2220123 for 6 Modifier:xx6$ or XX6$ Result:
22601234
Removing a prefix99# at number 99#2220123

Modifier:---$
Result:2220123
Delete the last four digits of a number22201239876

Modifier:$----
Result:2220123
Selecting the first seven digits of a number

222012349876 Modifier:xxxxxxx!
Result:2220123
240
Delete the last two digits, replace the third digit with6 and adding area code 383 to 222012398
Modifier:+383xx6$-- Result:
3832260123
4.1.7.6.4.2 Testing modifiers

By clicking on the link"Check number"under the table of modifiers, you can check the operation of
modifiers on the room with the given parameters.
Internal resources → Modifier tables → Check number
To check, you need to enter numbersCdPN and CgPN, fill in the fields"room type", "plan type numbering", "
Presentation", "Screeen", "AON Category". Then select tables of interest modificationsCdPN and CgPN, then
click on the button"Check". About completed fields after blue arrows will show the values that will be
assigned to the number as a result of the modification. Below will be displayed masks of numbers, which
included the studied numbers and descriptions of modifiers that were entered into the table of modifications.
If the modification table contains only SORM modifiers, then the service"Check number» this table will not be
displayed, because check does not work for tables with SORM modifiers.
241
4.1.7.7 Q.931 timers

InsideEarly resources → Timers Q.931
This section configures the third level timers required for the signaling protocol to work.Q.931.
The name of the timers and the default values are described in the recommendationITU-T Q.931 §9 List of
system parameters.
Name Default value, sec Range, sec
T301 180 30 - 360
T302 15 10 – 25
T303 4 4 - 10
T304 20 20 -30
T305 thirty 30 - 40
242
T306 thirty 30 -40
T307 180 180 - 240
T308 4 4 - 10
T309 90 6-90
T310 10 10 – 20
T312 6 6-12
T313 4 4 - 10
T314 4 4 - 10
T316 120 120 - 240
T317 120 120 - 240
Not lessT316
T320 thirty 30 - 60
T321 thirty 30 - 60
T322 4 4 - 10
4.1.7.8 OKS-7 timers

In this section, level timers are configured.MTP2, MTP3 and ISUP of the SS-7 protocol.
Internal resources → Timers OKS-7
243
The following buttons are used to create, edit and delete a profile:
- "Add profile";
– “Edit profile parameters”;
- "Delete profile".
• No.– sequence number of the OKS-timer profile7;
• Profile– profile name;
• OKS-7 line group– list of SS-7 line groups for which this profile is selected.
Profile settings:
Internal resources → Timers OKS-7→ Object
244
Table21 – Name of MTP2 layer timers and default values are described in ITU-T Q.703 §12.3 Timers
T1 50 40 - 50
T2 50 5 - 150
T3 2 12
T4n 8.2 7.5 – 9.5
T4e 0.5 0.4 - 0.6
T6 6 3-6
T7n 2 0.5 - 2
Table22 – Name of MTP3 layer timers and default values are described in ITU-T Q.704 §16.8 Timers and
timer values
T2 2 0.7 - 2
T4 1.2 0.5 - 1.2
T12 1.5 0.8 - 1.5
T13 1.5 0.8 - 1.5
T14 3 2-3
T17 1.5 0.8 - 1.5
T22 180 180 - 360
T23 180 180 - 360
245
Table23 – ISUP layer timer names and default values are described in ITU-T Q.764 Annex A, Table A.1/Q.764
– Timers in the ISDN user part
T1 60 15 - 60
T5 900 150 - 900
T6 thirty 10 - 60
T7 thirty 20 - 30
T8 15 10 – 15
T9 180 30 - 240
T12 60 15 - 60
T13 900 150 - 900
T14 60 15 - 60
T15 900 150 - 900
T16 60 15 - 60
T17 900 150 - 900
T18 60 15 - 60
T19 900 150 - 900
T20 60 15 - 60
T21 900 150 - 900
T22 60 15 - 60
T23 900 150 - 900
T24 2 0-2
T25 10 1 - 10
246
T26 180 60 - 180
T33 15 12 – 15
T34 4 2-4
T35 20 15 – 20
The timer values can be reset with the "Default"to the values recommended in ITU-T Q.703, Q.704 and
Q.764.
4.1.7.9 Mapping of Q.850-cause clear-cause and SIP-reply response code

This section establishes the correspondence between the clearback reasons described in the
recommendationQ.850 signaling protocols OKS-7, PRI and 4xx, 5xx, 6xx SIP responses.
By default, the correspondence given in Order No. is used.10 MINISTRIES OF COMMUNICATION AND OF
MASS COMMUNICATIONS OF THE RUSSIAN FEDERATION fromJanuary 27, 2009, for reasons not
described in this order, the correspondence specified in the recommendation is usedQ.1912.5 for
protocolsSIP-I and RFC3398 for SIP/SIP-T.
Internal resources → Table of correspondencesQ.850-cause and SIP-reply
Internal resources → Table of correspondencesQ.850-cause and SIP-reply→ Object
247
The following buttons are used to create, edit and delete rules in the correspondence tables:
- "Add rule";
– “Edit rule parameters”;
– “Delete rule".
• Name– name of the Q.850-cause and SIP-reply mapping table;
Profile settings:
Internal resources → Table of correspondencesQ.850-cause and SIP-reply→ Object →
• Direction:
• SIP-reply->Q.850-cause-direction from SIP side to Q.850 side;
• Q.850-cause-> SIP-reply -direction from the Q.850 side to the SIP side.
• Q.850 cause– Q.850 cause value;
• SIP-reply– 4xx, 5xx, 6xx class response value of the SIP protocol.
4.1.7.10 Scheduled Routing

This section configures the "scheduled routing" feature, which allows you to use different dial plans
depending on the time and day of the week.
Internal Resources → Scheduled Routing
248
The following buttons are used to create, edit and delete rules:
- "Add rule";
– “Edit rule parameters”;
– “Delete rule".
Routing rule:
Internal resources → Scheduled routing →
• Work period start date– selection of the start date for the operation of the routing rule by
schedule
• Duration of work (days)– the duration of the operation of the routing rule by schedule
• Repeat every monthoption allows you to specify the repetition of the use of the rule routing
every month;
• Days of the week– selection of days of the week for the operation of the scheduled routing rule;
• Opening hours– selection of hours of operation of the scheduled routing rule;
• Numbering plan– selection of the numbering plan to which the transition will be made during
operation scheduled routing rules.
249
4.1.7.11 Time routing

Time routing allows you to set call forwarding schedules for subscribers.
To configure call forwarding time intervals, you need to create a schedule:

Internal Resources → Time Routing
Further, in the schedules, you can select the desired time intervals for forwarding.
Internal Resources → Time Routing → Object
-After creating and configuring the schedule, it must be linked to the subscriber through VVO services (see
paragraphFar Eastern Department).
4.1.7.12 Call groups
call group1– a group of numbers to which the device can initiate calls, with different the type of ringing
of these numbers when a call arrives at the call group prefix.
Call group is for organizationCall-center or to connect offices for simultaneous or sequential
calling of employees included in the same call group.
In total, it is possible to create up to1000 call groups.
- 1The option is available only if you have an SMG-VAS license, more about licenses in the section
Licenses.
250
Internal Resources → Call Group
Search for a group by name— checking the presence of a call group by its name; Group
search by mask- check for the presence of a call group by mask forCDPN. Buttons are
used to create, edit and delete records in the table:
- "Add a note";
– “Edit recording parameters”;
– “Delete entry".
Internal Resources → Call Group → Object
A call group can include both device subscriber numbers and external numbers.
• Name -call group name;
• Numbering plan– selection of the numbering plan in which the call group will be located;
• Masks for CDPN– mask of the number of the called subscriber for calling the group from the assigned to
numbering plan group (the mask syntax is described in sectionDescription of the mask and its syntax);
• Recording and notification (option available only with SMG-REC license)- in this mode group members
will play a notification dictated by the initiator of the group call. Notification recordings are managed in
the Call Recording section
→ Group notification records.
251
Work algorithm:
• The notification initiator makes a call to the group number;
• After 10 seconds, the SMG answers the call and emits a 1400Hz tone for one second, the recording
is turned on;
• The initiator dictates a message and hangs up;
• After three seconds, the SMG starts calling the group member, when answering the member, a
recorded message;
• If the paging participant listened to less than 1/3 of the recording, the paging is considered unsuccessful and
five seconds later, another notification attempt will be made. If the second time the participant again
listened to less than1/3 of the record, the notification is still considered successful;
• With sequential notification, the call will be retried after three seconds;
• If the participant does not answer within the specified participant call timeout, a pause is made 60
seconds and another notification attempt is made. A total of five attempts are made;
• In consecutive announcements, participants who were not announced are placed at the end.
paging queue and the call goes to the next participant.
• Working mode– method of calling members of the call group:
• simultaneous call -simultaneous call of all members of the call group;
• starting from the first, one by one -a method in which, when a new call arrives at a given group,
the number that is first in the list of numbers of this call group is always called first, afterTimer
call on group member is canceled and starts calling a subsequent member of this group;
• one by one in successiona method in which calling within a group is carried out with the number
on which the conversation ended during the previous call to this call group. This method is
needed to balance the load between members, afterTimer a call to a group member is canceled,
and a call to the next member of this group begins;
• starting from the first one with the addition of the following −a method in which, upon receipt of
a new call to this call group, the number that is first in the list of numbers of this call group is
always called first, afterTimer call on group member not is canceled and the next member of this
group is called;
• sequentially with the addition of the following -a method in which calling within a group is
carried out from the number on which the conversation ended during the previous call to this
call group, this method is necessary to balance the load between members, afterTimer call to a
group member is not canceled and the call starts subsequent member of this group;
• serial search (starting from the first)- a method in which the search for the first available from the
beginning of the subscriber list, the call to the first available one occurs until the subscriber
answers or until the timeout hangs up, only the subscriber of this gateway can be members of
this group;
• serial search (sequentially) –method that searches for the first available subscriber, starting from
the number on which the conversation ended during the previous call, the first available call
occurs until the subscriber answers or before the timeout hangs up, only subscribers of this
gateway can be members of this group.
• End mode -call group members hangup method:
• default- after the answer of one of the members of the call group, everyone else a message is
sent to participantsCANCEL, as a result, on the phones of these subscribers a missed call
notification appears;
• quiet -after the answer of one of the members of the call group, all other members a
message is sentCANCEL with header Reason: SIP;cause=200, resulting in the phones of
these subscribers will not receive a missed call notification.
• Conference number -number, when dialed after the service prefix DVO Conference all members of
this call group will join the conference;
252
• Call back a rejected call– when using the option, repeated attempts to dial the group members who
rejected the call without lifting the handset. If the called subscriber rejected the call three times,
attempts to reach him will stop;
• call back busy– when using the option, retries will occur dialing the group members who were
busy at the time of the group call (before the group call was answered or the group call timeout
expired).
When choosing an option"Record and notice»
• Working modetakes the following values:
• recording and simultaneous notification– after recording the message, the group members will be
notified at the same time;
• recording and sequential notification– after recording the message, the group members
will be notified in turn, starting from the first;
• Participant call timeout, sec –call timeout of one call group member;
• Group call timeout, sec –total call timeout of the entire call group;
• Maximum notification recording time, sec –the setting is available when the option is activated
"Record and notice". Specifies the maximum message length that can be write down for the
group when arranging the alert.
• Composition of the group -call group composition, up to 40 participants on SMG-1016M, up to 160
participants on SMG-2016 and SMG-3016. If the call group is used for organizing conferences, then the
maximum group size is reduced to40 participants on SMG-1016M, SMG-2016 and SMG-3016. The
maximum number of such conferences for 40 participants (including the initiator) can be 1 for SMG-1016m
and 4 for SMG-2016/3016.
When choosing operating modes"simultaneous call", "starting from the first one by one", "consecutively one
by one", "starting from the first with the addition of the next"And"successively with the addition of the
following"queue functionality will be available.
The queue functionality is necessary for the organizationcall center.
253
Internal Resources → Call Group → Object
• Queue size -the maximum number of participants who are in the queue and waiting operator
response, if the specified number is exceeded, new calls will be rejected;
• Path to disk -at the selected valueoffsystem sound files will be used for queues that are in the device's
file system. If necessary, you can record your sound files to an external drive and select the path to
the drive with sound files. The files must have specific names as shown in the table below;
• Directory for sound files -the name of the directory on the external drive where the sound files are
stored queue files.
254
Table24 - Names of sound files
File name Meaning Default
queue_position.wav "Your position in the queue" There is
answer_tone.wav The sound\melody that will be played is not present when

the operator answers
callback.wav Phrase played to the operator before calling No

back to the subscriber
advertise Advertising files directory No
not_more_2m.wav "Waiting time no more2 minutes" There is
more_than_5m.wav "Waiting time over5 minutes" There is
1-20.wav, 30.wav Number in line There is
callback_operator.wav Phrase played to the operator before calling No

back to the subscriber
callback_subscriber.wav Phrase played to the subscriber when No

the option is enabledcallback
• Advertising -if the flag is set, while waiting for the operator's response to the caller the subscriber
will play sound files from the directoryadvertise with specified timeout playing ads;
-Will only be usedThe first 5 files from the advertise directory. This option available only when
using an external storage device to store queue audio files.
• Advertising playback timeout, sec- the period of time after which the subscriber will play
ads;
• Lose position in queue– when using the option, the caller will be his position in the queue is
reported;
• Position playback timeout, sec- the period of time after which the subscriber will its position
in the queue is played, the beginning of the period is the end time of the last playback of the
position;
• First playback timeout, sec- the time after which the first time will be played position in the
subscriber's queue;
255
• Persian numerals– SMG-1016M, SMG-2016 and SMG-3016 support playback compound Persian
numerals. To play numbers more20 used three parts of the numeral, including the linking word;
• Reply notification– with the option selected, after the operator answers the caller a sound file
will be played to the subscriber and operatoranswer_tone.wav;
• Call caching– option needed to remember with which operator the last time the caller was talking. So
that when you call back, the caller immediately gets to the operator with whom he spoke the last time:
• Not used– caching is disabled;

• Strict– if the operator is busy, the call will not go to other operators, but will wait for the
release of the desired operator;
• Not strict– in case the required operator is busy, the call will be distributed between other
operators in accordance with the specified mode of operation.
• Working hours- set the time interval of the working day, for calculating statistics call group
operation;
• PPV settings:
• MoH instead of CPV– use music on hold instead of callback tone when waiting for a response
operator;
• Pause before music– the time during which the standard payback will be played, before
inclusionMoH;
• Type– MoH type selection:
• Music on hold– when this type is selected, the subscriber will play
standardMoH SMG;
• Audio file– when this type is selected, it becomes possible to assign playing a
sound file previously loaded on the drive. The choice of a drive for loading sound
files is carried out in the System parameters → KPV settings section:
• File name– select an audio file to be played as a CPB.

• Reserve member setup:
• Reserve number– number to which the call will be made after activation "group call
timeout";
• Reserve call timeout- timeout, responsible for the duration making a call to a reserve
number.
• Composition of the group– list of operators that are part of the call group.
256
4.1.7.13 Pickup groups
Intercept group1– a group of subscribers of the device, when a call is received by one of the subscribers of
this pickup group, another member of the group can pickup the call by dialing the exit prefix to this call
group.
- 1The option is available only if you have an SMG-VAS license, more about licenses in the section
Licenses.
Internal resources → Pickup group
Buttons are used to create, edit and delete records in the table:
- "Add a note";
– “Delete entry".
The call group can only include subscribers of the device.
Internal resources → Pickup group → Object
• Name -name of the interception group;

• List of numbers -the composition of the interception group.
257
Pickup group member type:
• Limited -cannot intercept, but a call to him can be intercepted other members of the group;
• Ordinary -can intercept a call to a regular and restricted group member, but cannot intercept a call to
a privileged member of the group;
• Privileged -can pickup a call to any members of the pickup group.
4.1.7.14 Voice messages

The device has15 standard voice message phrases that are issued for informing subscribers. The
section is intended for loading voice messages other than standard files.
The file must be in the formatWAV using G.711a codec, 8 bit, 8 kHz, mono. Size no more than 2 MB.
Internal resources → Voice messages
• No. -sequence number of the voice message file;

• Name– voice message file name;
• Description– description of the voice message file.
You can add your own file to the list of user voice messages and select an event description for it, at which
this file will be played, using the buttons «Review"And "Add".
• Use– enable playback of the voice message file.
258
4.1.7.15 List of SIP responses for failover trunk group

This section is for configuring the response listSIP class 4XX - 6XX, for which either failover to the standby
trunk group or failover to the next trunk in the trunk direction will be performed.
Internal Resources → Answer ListSIP
The menu is used to create, edit and delete a list."Objects" - "Add object", "Objects" - "Edit object"And
- "Add a list of answers";
- "Edit the list of answers";
- "Delete answer list".

Internal Resources → Answer ListSIP→ Object
It is necessary to set the name of the list and form it using the buttons"Add"And ("Delete").
259
4.1.7.16 Q.850 release reason list

This section is for configuring clearback reasons.Q.850 protocols SS-7 and Q.931, according to which will
either failover to the standby trunk group or failover to the next trunk in the trunk direction.
Internal resources → List of hangup reasonsQ.850

Internal resources → List of hangup reasonsQ.850→ Object
It is necessary to set the name of the list and form it using the buttons"Add"And ("Delete").
260
4.1.7.17 Q.850 restore reason list

This section is for configuring clearback reasons.Q.850 protocols SS-7 and Q.931, according to which an
attempt will be made to restore communication if the call is not rejected from the incoming side.
Internal resources → List of recovery reasonsQ.850→ Object
4.1.8 Public address system
-Functionality is activated with licensesSMG-VNS and SMG-VAS.
The Voice Announcement System (hereinafter referred to as SPS) is intended for simultaneous or
sequential calling and notification of several subscribers according to a pre-created notification task
and a prepared list of subscribers' numbers.
-For the work of the SGO, toSMG needs to connect the drive, and select it in the "Write conversations” –
“Recording options”. The drive stores voice message files for alerts, alert recording files, and CSO
reports.
Possibilities:
1. Ability to create 40 lists of numbers, each of which can contain up to 200 numbers subscribers.
2. Possibility to use one phone number simultaneously in several lists.

3. Ability to create 200 notification tasks.
4. Ensuring the simultaneous execution of up to 20 tasks for notifying groups of subscribers, with a
common total number of notified subscribers up to500. Example1: 20 groups of 25 subscribers, 500
subscribers in total.
Example2: 10 groups of 30 subscribers, 10 groups of 20 subscribers, 500 subscribers in total.
Example3: 10 groups of 40 subscribers, 10 groups of 10 subscribers, total 500 subscribers.
261
Algorithm for working with SGO:
1. Preparing a task for voice notification.

2. Performing the task of voice notification.
3. Formation of a report on the completed task of voice notification.
Description of each of the stages of the algorithm for working with SSS:
1. Algorithm for preparing a task for voice notification.

1.1. Drawing up a list of numbers of notified subscribers.
1.2. Recording a voice message.
1.3. Creating a notification task, indicating a list of numbers and a recorded voice messages.
2.Algorithm for the actual execution of the voice notification task.

2.1. The operator gives a command to start a pre-prepared task.
2.2. The CPS accepts the command and starts the notification task.
2.3. In case of unsuccessful launch of the notification task, the CPS generates a short report with
indicating the error.
2.4. If the notification task is successfully launched, the CSO will call and notify numbers on
the list.
2.5. When the subscriber is busy or unavailable, there is no answer to the call or there is no
eavesdropping confirmation SSS makes several attempts to notify the given subscriber.
2.6. The same task can be restarted only after the completion of the existing one. call
process.
3.Formation of a report on the result of the completed task.
3.1. Upon completion of the notification, the CSO generates a report available through the web interface,
in which states:
– date and time of the task start;

– date and time of completion of the task;
– conditional number of the voice message;

– list of notified numbers marked “notified”/”not notified”.
Detailed description of the actual launch and execution of the voice announcement task
1. Starting the execution of the notification task.
1.1. The operator from his telephone dials a special number of the form *XX# to access SGO.
1.2. CPS receives the call and gives an acoustic signal "Station response" (continuous
acoustic signal440 Hz), waiting for the additional dialing of the conditional task number NN
via DTMF signals.
1.3. Possible alternative: the operator dials from his telephone special type number *XX*NN#
indicating the conditional number of the task NN.
1.4. CPS, having received a call and a conditional number of the task for notification, submits:
– acoustic signal "confirmation" in case of successful launch of the task on notification

(two-frequency signal with frequencies330 and 440 Hz for 100 ms, repeated three times
at intervals100 ms), then ends the call;
262
– acoustic signal "error" in case of an error or impossibility to start the task (three-tone signal
with frequencies950/1400/1800 Hz per burst 330 ms at intervals330 ms) and then ends the call.
1.5. SSS generates a preliminary report on the attempt to launch the task, indicating the date, attempt
time and task status: running/startup error. In the event of a startup error, the CGS indicates the
reason in the report.
2.Handling the successful launch of the notification task.
2.1. If the notification task is successfully launched, the CPS starts calling by telephone
numbers specified in the list of notified subscribers.
2.2. After the called subscriber picks up the handset, the CPS plays back to him the specified in
task voice message.
2.3. After playing back at least 1/3 of the length of the recorded message, the CPS is waiting from
the subscriberDTMF confirmation codethe fact of listening (for example, pressing button 1 on
phone).
2.4. After receiving the confirmation code, the CPS notes in its database the fact of a successful
notification of this employee when the task is completed.
2.5. In the absence of a DTMF confirmation code and listening to less than 1/3 of
duration of the message The CPS considers that the employee did not receive the
message and will make further attempts.
2.6. If after 5 attempts to notify the CPS does not receive a DTMF code from the
subscriber confirmation, it notes in the database the fact of failure to notify this
employee and stops notifying him until the end of this task.
2.7. In case of no answer to the call / unavailability of the subscriber, the CPS repeats attempts
call in accordance with the ringing cycle settings, the following algorithm works:
2.7.1. N dialing attempts are made with a "Timeout" interval between them sec.
2.7.2. In the case of N failed dialing attempts in a row, the pause timer "Between repeats" sec.
2.7.3. Items 2.7.1-2.7.2 are repeated a given number of times.

3.Restarting the notification task.
3.1. Restart is possible only after the completion of the previous run of this task.
3.2. When you try to restart an unfinished task of calling the SGO, it will give an error launch with the
corresponding entry in the database.
3.3. Successful restart of the notification task does not take into account the previous result task
completion and all subscribers from the list will be notified.
SHO allows you to simultaneously perform up to20 tasks for notifying groups of subscribers with a
common total number of notified subscribers up to500.
Description of the completed notification report:
Upon completion of the notification task, the CSO generates a report that is available throughweb
interface, which states:
– date and time of the task start;
– the success of the task launch;
– date and time of completion of the task;
– conditional task number;
263
– task name;
– name of the voice message;
– voice message file name;
– the number (and percentage of the total number) of notified participants;
– list of notified numbers marked “notified”/”not notified”.

Voice announcement system → Voice messages
Voice announcement system → Voice messages → Object
Voice announcement system → Voice messages → Object → Overview
In this section of the menu, you create (bind) a voice message for further use. Where:
• Path to disk- specify the location of the audio files (the disk is selected in the section
"Recording conversations" - "Recording options");
• Description– description of the voice message;
• File name– the name of the selected audio file.
264
In the "Download" section, it is possible to upload your own audio file of a certain format (file format "
Windows-WAV", audio encoding: PCMA, 64 kbps, 8 kHz, mono).
You can record a voice message from a telephone, for this you need to dial the code
* # 82 #, dictate a message and hang up. After that, a Voicemail will be automatically created. message with
this entry. You can also immediately add a voice message to an already created task when recording, for this
you need to dial the code *#82*TASK_NUMBER#, dictate a message and hang up, after that the newly
recorded message will be attached to the selected task, the next time the task is started, it will be played to
subscribers from the list of numbers.
If the task with the specified number does not exist, the message will be added to the general list of
voice messages and will not be linked to any task.
Downloaded audio files and recorded voice messages are stored on the drive in the directory vns_files/
audio.
4.1.8.2 Alert tasks

Voice notification system → Notification tasks
Voice notification system → Notification tasks → Object
In this section of the menu, notification tasks are created, where various parameters are specified, such as:
• Name– task name;

• Number– number from which notification will occur;
265
• Display name– display name when calling subscribers through the public address system (Display
name);
• Create alert entries1-when this option is activated, records of all notified subscribers. Recordings
are managed in the Voice Announcement System → Announcement Recordings section.
• Call recording category (the option is available when the "Create recordings" checkbox is
activated alerts")the category to be assigned to the alert entries. This option is used to define
user access rights to recorded alerts. For a detailed description, see sectionCategories of
conversation recordings;
• Number of notified participants– number of simultaneously notified participants. Acceptable range:
forSMG1016M - [4;8], for SMG2016/3016 - [4;40];
• Numbering plan– selection of the numbering plan in which the search for participants will be carried out
public address systems indicated in the list of numbers;
• Access category– access category of the warning system (taken into account in delimiting calls by
category);
• Don't wait for DTMF confirmation– if this option is activated, the notification system will not will await
confirmationDTMF from the subscriber (it will be enough to listen more3 seconds);
• A voice message– select a voice message;

• Participant response time– waiting time for the notification subscriber's response. Range allowable
values, sec [5; 120]; If the notified participant does not answer the call within the specified time, then
the call is considered unanswered, and then the CSO performs attempts to dial this participant in
accordance with the settings of the ringing cycle;
• Report language– selection of the language that will be used when creating the CGS report;
• Report Format– setting the report type:
• Default -subscribers in the report will be located in the same way as in the lists of
numbers, that are added to the notification task;
• Unannounced callers at the beginning -unannounced subscribers in the report will be
located at the beginning of the list, and notified at the end;
• Unannounced callers at the end -unannounced subscribers in the report will be located
at the end of the list, and notified at the beginning;
• Only unannounced subscribers -the report will include only unannounced subscribers;
• Number list– adding lists of numbers to call.
-In case onSMG, in addition to the SMG-VNS license, the SMG-REC license is installed, and in the section
"Record Options" uses recording masks (for exampleX.), then when alerting numbers participants
matching this mask, a notification record will be created even if this option is not active in the task.
Call loop settings

In case of an unsuccessful call to the number, the CSO repeats attempts to get through according to the following algorithm:
1. N dialing attempts are made (configured in the "Attempts" column) with a "Timeout" interval between
them sec.
2. In the case of N failed dialing attempts in a row, the pause timer “Between retries” starts sec.
3. Steps 1-2 are repeated for a specified number of repetitions.

Example "Unavailable":
Timeout (s) -10
Attempts -3
266
Between repetitions (s) -180
Replays -5
1. 3 dialing attempts are made with an interval of 10 seconds.
2. In case of 3 failed dialing attempts in a row - a pause of 180 seconds.
3. Steps 1-2 are repeated up to 5 times.
4.1.8.3 List of numbers

Voice announcement system → List of numbers
In this section of the menu, lists are created and loaded, which include numbers for calling through the
voice announcement system. The maximum number of number lists is40. In each the list can be up to200
call numbers.
-Duplication of a number in one list of numbers is prohibited. In different lists use identical numbers
are allowed.
• Name– name of the list of numbers;

• Active– when this option is activated, the CSO will make a call to the specified number. This option
allows you to temporarily turn off the notification of some participants, without deleting the
numbers from the list. For example, if the subscriber is on vacation, business trip, etc.;
• Name– name of the subscriber that will be used when generating the report;
• Number– telephone number of the caller;
• A priority -the procedure for notifying the participant when performing the task of the CGS. This
parameter allows you to set notification participants a priority when forming the notification queue.
Values: from1 to 5, where 1 is the highest (alert participants with this priority will be notified first)5 -
the smallest (alert participants with this priority will be notified last).
-If the participant, with priority1 is not notified on the first attempt, then it is carried to the end
notification queue.
Download room lists- this option allows you to downloadSMG lists numbers from beforehand prepared
file.csv
The file name is the name (description) of the list of numbers;
File format:
<NAME>;<NUMBER>;<Priority>
<NAME> is the name of the participant. This option may be missing.
<NUMBER> – participant number.
267
<Priority> – priority. This parameter may be absent, in which case the participant will be set priority
5.
Example:
Uploading a filenumber_list1.csv filled with the following data:
Name1;500;1
Name2;501;2
Name3;502;3
;503;4
;504
as a result, a list of numbers will be creatednumber_list1 of the form:
Voice announcement system → Number list → Facility
Multiple files can be uploaded at the same time. The number of simultaneously downloaded files cannot
exceed40, however, if prior to uploading files, lists of numbers have already been created (or downloaded
earlier), then the number of simultaneously downloaded files is reduced by the number of lists already
created. When loading a file with content other than the format described above, a warning will be shown -
"Something went wrong while performing the last operation." When uploading a file containing the same
numbers, a warning will be shown - "Some files could not be loaded: duplicate numbers."
If the name of the uploaded file matches the name of an already existing list, the following options will be
offered:
• supplement– the list will be supplemented with new numbers, numbers that are already present
in list, remain;
• overwrite– the list will be replaced with a new one;
• cancel– the file will not be loaded, the existing list will remain unchanged.
Search by number –searches for a number in all existing lists of numbers.
268
Voice announcement system → List of numbers
Search by number also allows you to edit and delete the found number in any of the lists of numbers. To
do this, enter the number in the "Search by number" field and click the "Find" button. Then, in the search
results, select an entry from those lists of numbers in which you need to change any parameters of this
number and click the "Edit selected" button. In the table that appears, select the fields you need to change,
edit them and click the "Apply" button.
To remove a number from the list, press the "Delete selected" button. After that, the number will be
removed from the selected number lists.
4.1.8.4 Reports
Public address system → Reports
This section of the menu stores all reports created during the operation of the voice announcement system.
Reports are generated in .csv file with the ability to download to a local car. Before downloading, you can
choose the encoding of the generated report:UTF-8 or WINDOWS-1251. Reports are saved to the drive in
the vns_files/reports directory.
-Only available forSMG-2016 and SMG-3016, encoding selection is not available for SMG-1016M.
• Task name– name of the notification task;

• Task number– task number for notification;
• File name– name of the report file;
• Start execution– start time of the call task;
• Completion of execution– completion time of the call task;
• Size– report size in kB.
The report file contains information about the result of the notification task execution.
269
Report file example:
task 0 Notification task number Notification task name Voice

name Task#000 message name Voice message file name Notification task
message VNS-VoiceMessage#01 start time Notification task end time Notification task
progress status Number (and percentage of total)
file priv.wav participants notified
started 2022.09.30 14:38:22
finished 2022.09.30 14:38:47
status Finished
total notified 1 (50.00%) List of participants (number, name, last attempt, notification
status)
number name last try status
701 1 14:38:26 Not notified.
User not answered
555 2 14:38:26 OK
The order in which participants are displayed in the report is configured in the notification task (field - Report
Format).
4.1.8.5 Alert records

File management section for recorded notifications. Recorded alerts are saved to the drive in the
directoryvns_files/notify_records.
Voice Announcement System → Alert Recordings
• Total number of entries -total number of notification record files;

• Disk Usage- Displays the used space of the drive selected for notification records;
• Select a date– select a date for displaying files with notification records;
• Time interval– selection of a time interval for displaying files with records alerts;
• Refine your request– search for files with notification records. The search is made on any match
of the entered value with the name of the notification record file.
A detailed description of the controls is given in the sectionCall Recordings.
270
4.1.9 Local LDAP server
4.1.9.1 List of LDAP Stores

This menu item configures the operation of the localLDAP servers.
LDAP→ ListLDAP storages
LDAP→ ListLDAP storages→ Edit
FormationLDAP storage occurs based on the subscriber capacity of the station (FXS, SIP- station
subscribers).
• Displayname = display name. If this field is empty in the settings, then it is substituted meaning "
no_name";
• Uid = title;
• Cn = subscriber ID;
• Sn = display name;
• telephoneNumber = subscriber's telephone number.
To connect to a local serverLDAP uses the following options:
• Protocol Version = 3;
• Port: 389;
• LDAP protocol: ldap;
• Base: ou=phonebook,dc=smg,dc=com;
271
• Username: cn=user,dc=smg,dc=com;
• Password: userpassword.
4.1.10 Voicemail
4.1.10.1 Voice mail options
• Path to the mail storage drive– sets an external storage medium for storing voice messages;
• Mail folder name– set the name of the folder where voice messages will be stored;
• Maximum number of messages– the maximum number of messages per subscriber (range of valid
values [0; 200] 0 - No restrictions);
• Storage time for unheard messages, days– storage time of unheard messages, through
which the message will be deleted from the voice box;
• Time spent listening to messages, days– storage time of listened messages, through which the
message will be deleted from the voice box;
• Minimum message duration, sec– minimum message duration from the subscriber, which can get into
voice mail (if the entry is smaller, the message will not be saved);
• Maximum message duration, sec– maximum message duration from subscriber, which can get
into voice mail (if the recording is longer, the connection will be disconnected and only the
recorded part will be saved).
272

In this section, you can listen, download, delete, change the status of voice messages. Messages are
grouped by the number on which the Voice Mail service is activated.
Voice mail → Voice messages
• Status– indicates the status of the message:

• – message not heard;
• – the message has been listened to.
• date– date of receipt of the voice message;

• Time– time of receipt of the voice message;
• Caller number– number of the subscriber who made the call to Voice mail;
• Called party number– number of the subscriber who has activated the service "Voice mail";
• Duration– duration of the voice message;

• Size, kB– size of the voice message recording file.
"Change message status"– changes the status from “Listen” to “Unheard” and vice versa;
"Update Table"– updates the table with voice messages;
"Load Selection"– downloads selected voice messages;
"Delete Selected"– deletes the selected voice messages.
- Only forSMG-2016.
4.1.11 IVR
IVR (Interactive Voice Response)– intelligent call routing system based on information entered by the
client from the telephone keypad using tone dialing, current time and day of the week, calling and called
subscriber numbers, with the ability to notify subscribers using sound files downloaded to the device. This
feature is required for the organizationcall centers, taxi services, technical support, etc.
In this section, lists of scripts and sounds are configured.IVR, as well as control recorded conversation
files.
273
4.1.11.1 Scenario list

In this section, scenarios for the operation of the service are created.IVR1.
Buttons are used to create, edit and delete records in tables:
- "Add a note";
– “Delete entry»;
- Download script» – download the scripts highlighted in the table to the user's PC.
TableList of scenarios– this table displays all created scenariosIVR.
IVR→ Scenario list
• Name– name of the IVR scenario;

• File name– select an IVR script file from the list of files created on the device.
TableSystem Settings- contains the setting "Path to the disk for storingIVR scenarios", which specifies the
drive for storing script files.
Tablelist of files– this table displays the generated script filesIVR.

To add a previously saved fileIVR should press the button "Review", in the dialog box select a file and
click the buttonDownload".
274
- 1The option is available only if you have an SMG-IVR license, for more information about licenses, see
Licenses.
TableList of typical scenarios– table contains files of common scriptsIVR, available for editing.
The menu for creating and editing scenarios is a constructor, in the center of the field a flowchart of the
scenario is formedIVR, on the left side there are typical blocks, on the right side - list of configurable
parameters for the current block.
275
IVR→ List of scenarios → List of typical scenarios → Object
To select a block on the diagram, click on it with the left mouse button. The selected block has orange
borders.
To add a block, select an empty block"Add"and select the required action from the set of typical blocks by
clicking on it with the left mouse button. In the field on the right, you need to configure the parameters for
the created block. Logical links for the newly created element will be added automatically. Logical link for
the block"goto» is set manually; for this, in the block parameters button must be pressed"Select a block on
the diagram",then select the desired block. Logical connection"goto"shown as a dotted line.
After setting up the selected block, you must save the changes in this unit by clicking the button "Save",to
undo changes -"Cancel".
To remove the selected block from the diagram, click the button"Delete block".If this block has
subordinate logical links, it will be deleted.whole branchobjects for which this block is the root block.
Blocks can be moved around the field, to do this, select the required block and, holding down the left
mouse button, move it to the selected location. At the same time, all existing logical connections are
preserved.
276
IVR→ List of scenarios → List of typical scenarios → Object
The form of the logical connection between the blocks can also be changed by clicking on it with the left mouse
button. The selected line has an orange color and three editing points: for setting the exit point from the block, the
entry point into the block, and the curvature of the line.
Description of blocksIVR is shown in the table below.

Table25 - Description of IVR blocks
Designation Name Description
Add An empty unit intended for adding a block.
277
ring The block required for issuing a callback signal to the subscriber, this
block is always the first in the list of scenarios. When a call arrives at the
blockRING The call state does not change.
Options
The duration of playing the CPV,c- choice of duration playback

of the callback signal, or disabled.
Connections
Entrance– start a call toIVR.
Exit– one output, at the output of the block information about the parameters
of the incoming call is available (number A, number B).
Peculiarities
The block does not change the state of the call.
info The block is required to play one or more voice messages to the calling
subscriber in the pre-answer state (without lifting the handset by the
subscriberB). That is, when playing this block there is no connection fee.
This block can be in the script after blocks that do not change the state of
the call, and if there was no transition to the response state before. The
block is useful for informing the called subscriber of standby information
until a resource is free that can handle the call.
Options
Messages to play until the caller answers– select one or more voice
messages to be played to the caller. Managing voice messages is
described in the sectionVoice messages. storage drive files is set in the
sectionSystem Settings.
Loop playback– selection of the number of message playback cycles,

messages are played in turn, starting from the first one.
Connections
Entrance– incoming call in pre-answered state.
Exit– end playback of the selected files.
Peculiarities
Before the blockInfo can only stand blocks that do not affect call state (
Ring, Info, Digitmap, Time, Goto).
278
play The block is required to play one or more voice messages to the caller in
a conversational state (after the caller answersB). The block is used to
inform subscriber A.
Options
Messages to play after the caller answers– select one or more voice
messages to be played to the caller. Managing voice messages is
described in the sectionVoice messages. storage drive files is set in the
sectionSystem Settings.
Loop playback– selection of the number of playback cycles.

Messages are played in turn, starting with the first one.
Connections
Entrance– an incoming call in pre-answered or conversational

state.
Exit– end playback of the selected files.
279
IVR The block required to implement the interactive voice menu function. In
this block, it is possible to logically select the path of the call by pressing
certain combinations of numbers, dialing the subscriber's number
according to the internal numbering plan and playing sound files,
system sounds (ringback, ringing, busy signal) and numbersDTMF for
notification subscriber.
Options
Type– type of sound file being played.
File– a sound file downloaded to the device. List of soundsIVR formed in

the sectionList of soundsIVR).
Tone– selection of the system sound to be played (numberDTMF, dialtone,

busy, ringback).
Subscriber selection– configuring the logic of further call passing. When

a configured combination of numbers is pressed, the device determines
the outgoing branch of the blockIVR. When if the subscriber has not
pressed anything, the branch "No match".
Subscriber selection waiting time, s– additional number dialing timer,

after this timer expires, the outgoing branch is selectedIVR.
Allow extension dialing– if the flag is set, additional dialing is allowed,

after dialing which routing will be performed according to the
numbering plan of the device, for example, you can dial an internal
subscriber.
Access category– select access category. Using the access category,

you can restrict the call to the number that was dialed by the
subscriber in the blockIVR.
Number of digits for extension dialing– the maximum number of

digits that can be dialed using extension dialing.
Interdigit interval, s– value of the interdigit interval of the dialed

number.
Connections
Entrance– an incoming call in the pre-answer state or in the active

call phase.
Exit– the number of outputs is configurable, and the output can also be an additional
dialing of the subscriber's number.
280
Peculiarities
If at the entrance to the block the call is in the pre-response state, then
the block automatically switches it to the active state (sends a response
to the caller), after which the further execution of the block logic is
carried out.
Dial The block required to dial the specified number, the routing of this
number occurs according to the numbering plan of the device.
Options
Number- given number.
Numbering plan:
Transit– the numbering plan is not changed.
Access category - sets the access category that will be used after
passing the blockDial:
Transit– access category does not change.
Connections
Entrance– an incoming call in the pre-answered state or in the

active call phase.
Exit– exit from the block is provided in case of unsuccessful dialing.
Peculiarities
Ends a script branch.
Time The block required to select the call flow logic according to the
current time and day of the week.
Options
Time– selection of time pattern and day of the week. The time is set in24-
hourly format.
Connections

call phase.
Exit- the block has2 exits, the first - when the time coincides with given
pattern (output "yes"), the second - in case of mismatch ("no" output).
Peculiarities
281
numbers The block required to select the logic for call progress according to
the caller's number.
Options
Number– caller number template.
Connections
Entrance– an incoming call in the pre-answered state or in the

active call phase.
Exit- the block has2 exits, the first - when the number matches caller
with the given pattern (exit "yes"), the second
– in case of mismatch (output “no”).
Peculiarities
Digitmap The block required to select the logic when passing a call in accordance with
the number of the called subscriber. The number of the called subscriber is
checked at the stage of entering the blockdigitmap.
Options
Mask– callee number template.
Connections

call phase.
Exit- the block has2 exits, the first - when the number matches called
subscriber with a given template (output "yes"), the second - in case of
mismatch (output "no").
Peculiarities
282
goto The block required to transfer the call to another arbitrary script
block.
Options
Select a block on the diagram- after pressing this button, you can
select the block on the diagram to which the transfer will be made.
Maximum number of operations– selection of the number of

cycles of the call passing through this block to protect against call
looping.
Connections

call phase.
Exit– one exit to the block to which the transfer is being made.
Peculiarities
REC The block is necessary to start recording a conversation; from the moment
the call logic passes through the block, the conversation of subscribers is
recorded to a file.
Connections
Entrance– an incoming call in the active call phase.
Exit- the block has one output.
Peculiarities
The block does not change the state of the call. The recording of the
conversation stops only after disconnection. Directory for saving
conversation recording filesIVR is configured in sectionRecording
options parameter "Folder name for recording conversationsIVR".
Control records are made in the sectionCall Recordings.
283
caller info The block allows you to change the name of the caller that will be
displayed on the called party's phone. The block allows you to display
the caller's name, company name and other data on the called party's
phone.
Options:
Number mask -caller number pattern.
Subscriber name -new subscriber name.
Connections

call phase.
Exit -block has one output.
Peculiarities
set A block that allows you to define a variable forIVR script.
Options:
Key- the name of the variable by which you can refer to it in other blocks.
Meaning- the value of the variable.
284
Condition The condition block is designed to test Boolean conditions composed of

variables and strings. All operations are performed on strings. In the
block, you can specify up to10 conditions. Every condition the
corresponding exit branch is set (from0 to 9) from block to another block.
In the blockCondition transition is carried out along the branch of the first
true condition (if there are multiple true conditions, the first one is
chosen). If the blockCondition none of the conditions turned out to be
true, then the transition along the branch will be performedFalse. The
following operators exist to form conditions. Logical operators:
!, not - logical NOT; &&,

and - logical AND; ||, or
- logical OR.
Comparison operators:
< - less;
<= - less than or equal to; =
- equal;
> - more;
> = - greater than or equal;
<> is not equal.
Since the comparison is performed on strings, the comparison is
performed character by character.
Examples of comparing strings of digits of equal length:
"101" < "102" = true "101" =< "102" = true "101" > "102" =
false "101" >= "102" = false
Examples of comparing strings of digits of unequal length:

"101" < "1102" = true "101" =< "1102" = true "101" > "1102" =
false "101" >= "1102" = false
Examples of comparing strings of numbers and letters of equal length:

"A01" < "102" = false "A01" =< "102" = false "A01" > "102" = true "A01"
>= "102" = true
"A01" < "102" = false, since strings are compared character by character, and
exactly the character code A in the tableASCI greater than character code 1.
Entry operator:
in is an operator for entering a variable into a list (for example, %%CGPN%% in
(710, 711, 712)).
Variables:
A string enclosed in percent (%) characters. The variable name can
contain characters: [A-Za-zA-Za-z_0-9].
Constants:
Any character enclosed in single (') or double (") quotes. A slash (/)
character is used for escaping. Or any sequence of non-blank
characters that do not start with a percent character does not
contain single, double quote characters.
285
Predefined variables: CGPN – caller's

number; CDPN – called subscriber
number;
YEAR, MONTH, DAY, HOUR, MINUTE, SECOND - date and time script
execution (time is usedUTC+0); YEAR_LOCAL, MONTH_LOCAL,
DAY_LOCAL, HOUR_LOCAL, MINUTE_LOCAL, SECOND_LOCAL – date and
time of script execution (using the local time from the device).
286
RPC Block for interaction with externalHTTP server:
SettingsHTTP request:
-url-the full URL of the request to the http server. If necessary, you
can use the variables of the current IVR script in the URL;
Example:http://infoUserServer.co/shirts?style=%CDPN%
- Method -HTTP request method (GET, POST, PUT, TRACE, OPTIONS,

DELETE, HEAD);
– Request timeout —HTTP request attempt time server in milliseconds;
– Request data type (Content type) —the type of data in request

body;
– Request body (Body content) –request body (string with optional the
presence of macro variables);
- Headers -HTTP request header.
• Key (Key) - toluchhttp header;

• Value (Value) - witha string with a possible value of
macro variables;
– Type in response body (Response type) —the type of data in

response body;
json-when choosing this type, if in the body of the response you

receive data of the form key:value, thenThe SMG records this data
as variables that can be used later.
- If in the body of the response the key is written in small letters,

for examplevar, then to then refer to this variable must be
written in capital lettersVAR%;
-regexp-When this type is selected, the Regular expression" in which

you can writeregexp expression for parsing the response fromHTTP
servers with the ability to write parsed data into variablesIVR and use
them in further.
Example:
Reply in the body of the message:hello world

String in a field"Regular expression":hello(?<var1>.*) As a result,
withinIVR script variable will be created VAR1=world
– Maximum response size (Max bytes) — mmaximum response size;
287
– Encoding in the response (Expected encoding) — toencodings

supported in the response;
– Codes –expected HTTP server response codes.
After creating a scenario flowchart, you must specify its name and save it by clicking the button
"Save Script"By button"Back to the list"the constructor exits without saving the changes.
4.1.11.2 List of IVR sounds

This section is intended for working with sound files necessary for workingIVR.
TableSystem Settings- contains setting"Disk path to store soundsIVR", which sets the drive for storing
conversation records fromIVR.
List of sounds
• IVR Sounds -list of downloaded files;

• Duration -duration of the uploaded file;
• Review -selecting an audio file to download to the device;
• Download -command to load the selected file.
-It is possible to upload an archive with several sound files of the formattar or zip sound
files must be located in the root directory of the archive.
• Listen -listen to the selected file;

• Stop -stop listening to the file;
• Delete -delete the selected file;
• Download -download the selected file from the device.
288
4.1.11.3 Call Recordings (IVR)

Recorded Conversation File Management SectionIVR. If there is a block in the IVR scriptREC, all recorded
conversations will be displayed in the table.
IVR→ Call recordings
• Total number of records– total number of call recording files in the selected directory for conversation
records;
• Disk Usage- Displays the used space of the drive selected for conversation records;
• Select a date– select date for displaying files with conversation records;
• Time interval– selection of a time interval for displaying files with records conversations;
• Refine your request– search for files with conversation records, the search is performed by any the
match of the entered value with the name of the conversation recording file.
The description of the record control buttons is given in the table

below. Table26 - Recording control buttons
Button Function
previous post
start playback
stop playback
next post
289
Button Function
repeat playback of a recording
save the record
delete entry
Description of the columns of the records table
• Date Time– date and time of recording start;

• Caller/Called Number– numbers of subscribers participating in the conversation;
• Called party number from call group– number of the subscriber who answered after call group
passing;
• Numbering plan– numbering plan in which the entry was made;
• Category– conversation recording category;
• FTP– whether uploading to FTP was performed;
• Duration- call duration;
• Size, kB – record size in kilobytes.
Conversation Recording File Format
1. Simple call without using call forwarding or call transfer YYYY-MM-DD_hh-
mm_ss-CgPN-CdPN.wav Where:
YYYY-MM-DD– file creation date, YYYY – year, MM – month, DD – day; hh-

mm_ss– file creation time, hh – hours, mm – minutes, ss – seconds;
CgPN– caller's number, in case of its absence, the value none is set; CDPN– number of the
called subscriber. Example:
Subscriber7111 calls subscriber 7222, the file will look like this:
2014-05-20_12-05-35_7111_7222.wav
2. Call when using call forwarding service YYYY-MM-DD_hh-
mm_ss-CgPN- RdNum cf CdPN.wav
Where:

CgPN– caller's number, in case of its absence, the value none is set; RdNum– forwarding number—
number on which the call forwarding service is configured; cf– a label indicating that there was a call
forwarding service;
CDPN– number of the called subscriber—the number to which the call actually arrives.
Example:
Subscriber7111 calls subscriber 7222, which is set to call forward to 7333.
2014-05-20_12-05-35_7111_7222cf7333.wav
290
3. Call when using call transfer service
The use of the call transfer service involves3 subscribers - call initiating subscriber (subscriber A), the
subscriber who transfers the call (subscriberB), and the subscriber to whom call is transferred
(subscriberC).
When transferring a call, it will create3 conversation recording files:
• conversation of subscribers A - B;
• conversation of subscribers B - C;
• conversation of subscribers A - C after the transfer of the call.
Example:
Subscriber7111 calls subscriber 7333, who transfers the call to subscriber 7333. The following files will
be generated: 2014-05-20_12-05-35_7111_7222.wav - conversation between subscribers A and B.
2014-05-20_12-06-36_7222_7333.wav - conversation between subscribers B and C, after subscriber B
put on hold the subscriberA.
2014-05-20_12-05-35_7111_7222ct7333.wav - conversation between subscribers A and C after the

implementation call transfer by the subscriberB, ct in the file name is the label that the translation was made
call.
4. Call from "Call Group"
If the call to the subscriber comes after the call group, then an additional field is added to the
record file with information through which call group the call was made to a member of this
group.
YYYY-MM-DD_HH-MM-SS_ CgPN - CdPN -CALLEDHG_nPLAN_cCATEGORY.wav
YYYY-MM-DD– file creation date, YYYY – year, MM – month, DD – day; hh-mm_ss
– file creation time, hh – hours, mm – minutes, ss – seconds;
called subscriber—the number to which the call is actually received; CALLEDHG– call group
number; nPLAN– numbering plan; cCATEGORY– call recording category.
5. Calling a subscriber through a “call group” YYYY-MM-DD_hh-mm_ss-CgPN-

CdPN-hgPN_numplan_category.wav Where:

CgPN– caller's number, in case of its absence, the value none is set; CDPN– number of the called
subscriber – number to which the call actually arrives (number call groups);
hgPN– number of the subscriber who answered after passing through the call
group; numplan– numbering plan; category– call recording category.
291
4.1.12 Call recording

Call recording settings menu1.
Digital GatewaysSMG-1016M, SMG-2016, SMG-3016 does not apply to special technical means intended for
secretly obtaining information (based on the notes to Art.
138.1 of the Criminal Code of the Russian Federation).
- 1The menu is only available in the software version with SMG-REC and/or SMG-VNS licenses, learn more about
licenses in the sectionLicenses.
The SMG can maintain a different number of concurrent entries depending on the connection type. Before
setting, please refer to the table below:
Connection type One submodule Six submodules

SM-VP-M300 SM-VP-M300
E1-E1 27 162
E1-SIP 22 132
SIP - SIP 20 120
-Please note that the call recording feature is designed to record business telephone
conversations and is not intended to comply with the provisions of Article13 federal law of
the Russian Federation No.374-FZ of 07/06/2016
Recorded conversations can be uploaded toFTP server. In this case, the records are first stored on local
media and then, according to the schedule, they are sent toFTP server.
-It is not recommended to recordUSB-drive with a large number of recorded conversations. The interface
bandwidth is insufficient to simultaneously write the proper number of files, which leads to an
increase in I / O buffers in RAM and can disrupt the gateway.
292
4.1.12.1 Recording options

Call recording → Recording options
General Recording Options:

• Path to the disk for recording conversations– select the storage device available in the device to
which conversations will be recorded;
• Folder name for recording conversations (option is not available when using only the SMG-VNS
license)– the name of the directory on the device storage to which the recording will be made
conversations; if the folder name is not specified, conversations will be recorded in the root directory
of the drive;
• Folder name for recording IVR conversations (option not available when using only SMG-VNS license)
– the name of the directory on the drive of the device to which the recording will be made
conversation when a call hits the blockREC in IVR scenario;
• Number of files in one directory– maximum number of files with records conversations in one
directory, if the maximum number of files is reached, a new directory will be created.
293
In the directory for recording conversations, a new directory is created for each recording day with the name:
YYYY-MM-DD-NNNN,
Where:
YYYY– 4 characters – current year;

MM– 2 characters – current month;
DD– 2 characters – current number;
NNNN– 4 characters – directory number with conversation records for the current date.
If the value "Number of files in one directory» the device will create a new directory with incremented
value№№№№.
Exampledirectories created for2014-02-27:
2014-02-27-0000
2014-02-27-0001
2014-02-27-0002
2014-02-27-0003
• Data retention time(Days/Hours) - the time during which files are stored on the drive with recorded
conversations, after this time the old files will be deleted;
• Action on disk full– selection of the action to be applied to the recording files conversations in case
of disk full:
• Stop Recording– stop recording new conversations if the disk is full;
• Delete old entries– delete old conversation records if the disk is full.
SettingsFTP servers:
• Save to FTP– if the flag is active, the recorded conversations will be automatically unload
onFTP server according to the selected download mode;
• Download mode– defines the frequency with which records should be uploaded to FTP:
• once a day– unloading once a day at a specified time;
• once an hour– unloading every hour;
• once a minute- Upload every minute.
• Watch- Available in "once a day" download mode. Allows you to specify the hour at which to produce
unloading;
• minutes- available in download modes "once a day" and "once an hour". Allows you to specify the
minutes in which to unload;
• FTP server– IP address or domain name of the FTP server to which the recorded files will be uploaded.
conversations;
• FTP port– FTP server port;
• The path to the file– path to saved files on the FTP server;
• Login for FTP– login for authorization;
• Password for FTP– password for authorization;
• Delete files after upload– if the flag is set, then after sending the recording files will be removed from
local storageSMG.
-When used onSMG only SMG-VNS licenses, these settings will apply to SGO records. CGS records are
saved to disk in the directoryvns_files/notify_records.
When used onSMG licenses SMG-REC and SMG-VNS, settings apply to recordings conversations, and
to records of alerts of the CPS.
294
Filtering masks for conversation recordings (option available only if you have a licenseSMG-REC):
Call recording → Recording options → Object
The device determines the need to record a conversation by numbersCgPN and CdPN.
• Mask– number selection mask, selection mask syntax is described in sectionNumber mask description and
its syntax;
• Type– search for a mask match by CdPN or CgPN numbers:
-Please note that the setting uses "or" logic, i.e. for determining record is enough to match or
CgPN or by CdPN.
• All– search by CgPN and CdPN numbers;

• Calling– search for a match only by CgPN number;
• Called– search for a match only by CdPN number.
• Numbering plan– sets the numbering plan in which the write mask will work. When choosing
conditions "Ignore dial plan" search will be performed in all active numbering plans;
• Recording start notification -notification of the called party that the conversation will be recorded
by:
• Do not notify– turn off the notification about the beginning of the recording of the conversation;
• A voice message– issuing a notification about the start of recording by a voice message.
• Call recording category- the category that will be assigned to the entry that falls under given
mask.
295
4.1.12.2 Call recordings(section not available when using SMG-VNS license only) File management
section for recorded conversations.
Call recording → Call recordings
• Total number of records– total number of call recording files in the selected directory for conversation
records;
• Disk Usage- Displays the used space of the drive selected for conversation records;
• User category– displays the category of call recordings that the current userweb interface;
• Select a date– select date for displaying files with conversation records;
• Time interval– selection of a time interval for displaying files with records conversations;
• Refine your request– search for files with conversation records, the search is performed by any the
The description of the record control buttons is given in the table

below. Table27 - Recording control buttons
Button Function
previous post
start playback
stop playback
next post
296
Button Function
repeat playback of a recording
save the record
delete entry
Description of the columns of the records table
• Date Time– date and time of recording start;

• Caller/Called Number– numbers of subscribers participating in the conversation;
• Numbering plan– numbering plan in which the entry was made;
• Category– conversation recording category;
• FTP– whether uploading to FTP was performed;
• Duration- call duration;
• Size, kB– record size in kilobytes.
Conversation Recording File Format
1. Simple call without using call forwarding or call transfer YYYY-MM-DD_hh-
mm-ss_CgPN-CdPN_nX_cY.wav Where:
YYYY-MM-DD– file creation date, YYYY – year, MM – month, DD – day; hh-mm-

ss– file creation time, hh – hours, mm – minutes, ss – seconds;
called subscriber;
nX– number of the numbering plan in which the recording was made;
cX– entry category. Example:
Subscriber40010 calls subscriber 40012, the file will look like this:
2017-10-23_09-27-26_40010-40012_n0_c0.wav
2. Calling when using the call forwarding service YYYY-MM-DD_hh-
mm-ss_CgPN-CdPN_Srv_SrvNum_nX_cY.wav Where:
YYYY-MM-DD– file creation date, YYYY – year, MM – month, DD – day; hh-mm-

ss– file creation time, hh – hours, mm – minutes, ss – seconds;
called subscriber—the number to which the call is actually received; srv- a label indicating that
the supplementary service has been used. Label values: cf– the call has been diverted; ct– the
call has been transferred; cp– the call was intercepted;
SrvNum- the number that was used in the work of the VDO. Depending on the label valuesrv
indicates the number to which the call was forwarded, transferred or from which the call was
intercepted;
nX– number of the numbering plan in which the recording was made;
cX– entry category.
297
Example:
Subscriber40010 is calling subscriber 40011, which is set to call forward to 40012.
2017-10-23_09-28-04_40010-40011_cf_40012_n0_c0.wav
3. Call when using call transfer service
The use of the call transfer service involves3 subscribers - call initiating subscriber (subscriber A), the
subscriber who transfers the call (subscriberB), and the subscriber to whom call is transferred
(subscriberC).
When transferring a call, it will create3 conversation recording files:
• conversation of subscribers A - B;
• conversation of subscribers B - C;
• conversation of subscribers A - C after the transfer of the call.
Example:
Subscriber40012 calls subscriber 40010, who transfers the call to subscriber 40000. The following files will
be generated: 2017-10-23_10-15-19_40012-40010_n0_c0.wav – conversation between subscribers A and B;
2017-10-23_10-15-31_40010-40000_n0_c0.wav - conversation between subscribers B and C, after subscriber
B put on hold the subscriberA; 2017-10-23_10-15-19_40012-40010_ct_40000_n0_c0.wav - conversation
between subscribers A and C after call transfer by the subscriberB, ct in the file name is the label that was
call transferred.
4.1.12.3 Group notification entries(section not available when using SMG-VNS license only)
File management section for recorded call group notifications.

Call Recording → Group Notification Recordings
• Total number of entries -total number of alert record files in the selected directory to record
conversations;
• Disk Usage- Displays the used space of the drive selected for notification records;
• Select a date– select a date for displaying files with notification records;
• Time interval– selection of a time interval for displaying files with records alerts;
• Refine your request– search for files with notification records, the search is performed by any the
298
In the "Date" column, each entry is a link to the alert log. The log shows the progress of the notification and its result.
You can listen to the notification text by clicking on the link in the "Record" column, in the same column you can
download the record by clicking on the icon next to the record.
4.1.12.4 Categories of call recordings

Call recording → Call recording categories
The call recording categories are used to define user access rights to recorded conversations.
If you want to restrict access to any records, you should assign them the appropriate category; for other
categories – define in this menu the accessibility to the category assigned to the object (remove access –
uncheck the flag opposite the corresponding category, add access – set the flag opposite the corresponding
category).
Total available for customization32 recording categories. By default, "Category 0" has an unchangeable
access to all other categories and is used to work with an administrator account that has access to all
conversations. The rest of the categories have configurable access. Default first15 of them have access to
the first 16 categories.
The transition to setting and editing the selected category is carried out by the button.
299
An example of setting up restriction of access to recording conversations
Let's consider an example when it is necessary to delimit access to records of negotiations for production
(user "production") and the sales department ("sales" user). Each user must have the ability to listen only to
the conversations of the corresponding department. To restrict access, you must:
1. Select an access category for writing. For convenience, you can specify a name, for example,"Production"
And"Sales".Set categories to access only themselves:
300

2. Go to the user account management (see subsection "Web Interface Users"). In the rights of the user
"production" select the rights "Listening to recorded conversations »and set available category category
"Production". User "sales" choose rightsListening to recorded conversations »and set the category "
Sales":
Control → Object
Control → Object
301
3. In the section "Recording Options»add record masks for production and sales department numbers and assign
them the corresponding record categories.
Call recording → Recording options
4. Now, if the user enters the section "Recordings of conversations», then he will see in the selection only
records of those categories to which he has access.
5. If in the considered example it is necessary to add the user "management" with the rights
listening to all departments, then as in p.1 you will need to add a new category, for example,
"Management"and set permissions to categories there"Production" And "Sales". Then in user management
assign user "management" access to the "Management" category.
Control → Object
302
As a result of the settings made, the table for restricting access to conversation records will look like this:
4.1.13 TCP/IP settings

This section sets the network settings of the device, routing rulesIP packages.
DHCP– a protocol designed to automatically obtain an IP address and other parameters, required for
networkingTCP/IP. Allows the gateway to automatically obtain all necessary network settings fromDHCP
server.
SNMP– simple network control protocol. Allows the gateway to transmit in real time reports of accidents
to the superintendentSNMP manager. Also SNMP Gateway Agent supports monitoring of the status of the
gateway sensors upon request fromSNMP manager.
DNS– a protocol designed to obtain information about domains. Allows the gateway to obtain the IP
address of a communicating device from its network name (host). It may be necessary
303
for example, when specifying hosts in the routing plan, or using as an addressSIP- its network name
server.
TELNET– a protocol designed to organize control over a network. Allows you to remotely connect to
the gateway from a computer for configuration and management. When using the protocol TELNET
data is transmitted over the network unencrypted.
SSH– a protocol designed to organize control over a network. When using this protocol, as opposed to
TELNET, all information, including passwords, is transmitted over the network to encrypted.
4.1.13.1 Routing table

In this submenu, the user can configure static routes.
Static Routingallows you to route packets to the specifiedIP networks or IP addresses through the
specified gateways. Packets sent toIP addresses not belonging to an IP network gateway and do not fall
under the static routing rules will be sent to the default gateway.
The routing table is divided into2 parts, these are the configured routes that displayed at the
top of the table, and routes created automatically.
Routes created automatically cannot be changed, they are created automatically when raising network and
VPN/PPTP interfaces, and are necessary for the normal operation of these interfaces.
SettingsTCP/IP→ Routing table
The menu is used to create, edit and delete a route."Objects" - "Add object", "Objects" - "Edit object"And
– “Add route”;
– “Edit route parameters”;
– “Delete route”.
304
Route options:
SettingsTCP/IP→ Routing table →
• Turn on -if the flag is set, the route is enabled;

• Direction– IP network;
• Mask– sets the netmask for the given IP network (for the IP address, use the netmask
255.255.255.255);
• Interface– selection of the transmission network interface;
• Gateway– sets the gateway IP address for the route;
• Metrics– route metric.
4.1.13.2 Network parameters

SettingsTCP/IP→ Network settings
In this submenu, the user can specify the device name, change the network gateway address, address DNS
servers and access ports via SSH and Telnet.
• host name -network name of the device;
• Use Interface Gateway– selection of the network interface whose gateway will be considered main on
the device;
305
• DNS Primary– main DNS server;
• DNS standby -backup DNS server;
• ssh access port– TCP port for accessing the device via SSH protocol, 22 by default;
• Telnet access port– TCP port for accessing the device via Telnet protocol, by default
23.
4.1.13.3 Network interfaces

The device has the ability to configure1 main network interface eth0 and up to 9 additional interfaces,
these interfaces can be interfacesVLAN and Alias of the main interfaceeth0 or VLAN interface Alias.
Aliasis an additional network interface that is created on the basis of the existing main interfaceeth0, or
based on an existing VLAN interface.
OnSMG-3016 has the ability to configure 2 main network interfaces eth0 and eth2. Interfaceeth2 is of type
Management and is only used to manage the device through the port OOV. The interface supports working
with a static address, with an address received viaDHCP, VLAN. There can be only one interface on a device
with the typemanagement.
SettingsTCP/IP→ Network interfaces
The buttons are used to create, edit, and delete network interface rules. "Add", "Edit"And"Delete".
306
Network interface settings Basic
settings:
SettingsTCP/IP→ Network interfaces
• Network name– network name;

• firewall profile– displaying the selected firewall profile for the given interface;
• Type– interface type (always untagged for eth0 interface):
• untagged– untagged interface (without VLAN);
• tagged– tagged interface (with VLAN);
• VPN/pptp client– client interface for VPN connection to a remote server via protocolPPTP
• VLAN ID– VLAN ID (1-4095) (only for tagged interfaces);

• Use DHCP– obtain an IP address dynamically from a DHCP server (for Alias not
supported);
• IP address– network address of the device;
• netmask– network mask for the device;
• Gateway– network gateway for this interface (not supported for Alias);
• Get DNS automatically– get DNS server IP address dynamically from DHCP server (ForAlias is not
supported);
• Obtain NTP automatically– NTP server IP address dynamically from DHCP server (for Alias not
supported).
Services– menu for managing allowed services for this interface:
• Web Control– allows access to the configurator through the interface;
• Telnet control– allows access via Telnet protocol through the interface;
• SSH management– allows access via SSH protocol through the interface;
• Use SNMP– allows the use of the SNMP protocol through the interface;
307
• Send RTP– allows receiving and transmitting voice traffic through the network interface, configured
in this section;
• SIP signaling– Allows the reception and transmission of SIP signaling information over the
network interface configured in this section;
• RTP signaling– Allows the reception and transmission of RTP signaling information over the
• H.323 signaling– Allows the reception and transmission of H.323 signaling information over the
• Use RADIUS– Enables the use of the RADIUS protocol over the interface.
-After the changeIP addresses or netmasks, or when Web Based Management is disabled configurator
on the network interface, in order to avoid losing access to the device, you must confirm these
settings by connecting toweb configurator, otherwise after the two-minute timer will roll back to
the previous configuration.
Front-ports - setting up external front-ports
-Only forSMG-2016.
This setting is only available for tagged interfaces.VLAN (in the "Type" parameter set to "Tagged").
SettingsTCP/IP→ Network interfaces →Tagged
• Default VLAN ID– when a packet arrives at the port without a VLAN ID tag, this packet is tagged with the VLAN ID tag
of the selected network interface; if the packet is received with the VLAN ID tag, then the received tag is not changes;
• Egress mode-rules for working with a VLAN tag when sending a packet from a port:
• tagget– send a packet with the VLAN ID of the selected network interface;
• untagget– send a packet without VLAN ID.
308
SettingsVPN/PPP interface:
SettingsTCP/IP→ Network interfaces →VPN/pptp client
Basic settings:
• Network name– network name;
• firewall profile– displaying the selected firewall profile for the given interface;
• Type– VPN/pptp client;
• Turn on -enable VPN/PPP interface;
• PPTPDIP -IP address of the PPTP server;
• Username -username (login) under which the device joins the network;
• Password -password for the VPN connection.
Options:
• Ignore default gateway -ignore gateway setting in section"Network options";
• Enable Encryption - inEnables encryption.

Services– menu for managing allowed services for this interface:
• Web Control– allows access to the configurator through the interface;
• Telnet control– allows access via Telnet protocol through the interface;
• SSH management– allows access via SSH protocol through the interface;
• Use SNMP– allows the use of the SNMP protocol through the interface.
309
4.1.13.4 RTP port range

This section configures the range of portsUDP for transmitting RTP voice packets. OptionsUDP
ports:
SettingsTCP/IP→ RangePort RTP
• Start port– number of the initial UDP port used to transmit the conversational traffic (RTP) and
T.38 protocol data;
• Number of ports– number of UDP ports (starting from the start port) used for transmission of voice
traffic (RTP) and T.38 protocol data.
-To avoid conflicts, the ports used for transmissionRTP and T.38 should not intersect with ports
used for signalingSIP (default port 5060).
4.1.14 Network services
4.1.14.1 NTP
NTP– a protocol designed to synchronize the internal clock of the device. Allows synchronize the
time and date used by the gateway with their reference values.
Network Services →NTP
310
• Use NTP -enable time synchronization via NTP protocol;
• Time server (NTP) -IP address or hostname of the NTP server;
• Timezone -setting the time zone and the deviation of the current time relative to GMT (Greenwich
Mean Time):
• Manual mode– selection of time deviation relative to GMT;
• Auto mode– in this mode it is possible to choose device location, deviation fromGMT will be set
automatically, also in In this mode, automatic changeover to summer and winter time works.
• NTP synchronization period, min –the period for sending requests for time synchronization;
• Start local NTP server -enable local NTP server for time synchronization by third-party devices
fromSMG. The option is available when enabled "UseNTP";
• Network interface -selection of the network interface on which the local NTP server will be
respond to inquiries.
Use the buttons to save and cancel changes.Save" And "Cancel».For forced time synchronization from the
server, you must click the "RestartNTP- client» (the NTP client restarts).
4.1.14.2 SNMP settings

SoftwareSMG allows you to monitor the device using the SNMP protocol. In the submenu"SNMP"
configuring the SNMP agent settings. The SNMP monitoring functions allow you to query the gateway for
the following parameters:
• gateway name;
• device type;
• software version;
• IP address;
• E1 flow statistics;
• statistics of IP submodules;
• state of linksets;
• state of E1 stream channels;
• status of IP channels (statistics on current calls via IP).
In the statistics of current calls byThe following data is transmitted to IP channels:
• channel number;
• channel status;
• call identifier;
• MAC address of the caller;
• IP address of the caller;
• caller's number;
• MAC address of the called subscriber;
• IP address of the called subscriber;
• number of the called subscriber;
• channel occupation duration.
311
OptionsSNMP:
Network Services →SNMP
• Sys Name– device name;

• Sys Contact- Contact Information;
• Sys Location– location of the device;
• ro Community– password/community for reading parameters;
• rw Community– password/community to write parameters.
Buttons are used to apply and cancel settings."Apply"And"Reset".
4.1.14.3 SNMPv3
ConfigurationSNMPv3:
There is only one user in the systemSNMPv3. The SNMPv3 user is used for sending SORM commands to
the gatewaySMG.
• RW user name- Username;
• RW user password– password (password must contain at least 8 characters).
To apply user configurationSNMPv3 button is used"Add"(settings are applied immediately after
clicking). To delete an entry, click the button."Delete".
4.1.14.4 Configuring traps (SNMP trap)
-Detailed description of monitoring parameters and messagesTrap is provided in MIB files,

supplied on disk with the gateway.
The SNMP agent sends an SNMPv2-trap message when the following events occur:
• configuration error;
• SIP-module failure;
• failure of the IP submodule;
• linkset failure;
312
• failure of the signal channel OKS-7;
• loss of synchronization, or synchronization from a lower priority source;
• E1 flow failure;
• remote flow alarm;
• configuration error fixed;
• SIP-T module operability restored after an accident;
• the operability of the IP submodule was restored after the accident;
• restored linkset functionality after a crash;
• the operability of the OKS-7 signal channel was restored after the accident;
• restored synchronization from the priority source;
• no flow alarm (after the presence of an alarm or a remote flow alarm);
• the server is unavailable, the RAM for storing CDR files is over 50% full (15 – 30 MB);
• the server is unavailable, the RAM for storing CDR files is less than 50% full (5 – 15 MB);
• the server is unavailable, the RAM for storing CDR files is full up to 5 MB;
• external storage is full, less than 5 MB of free space left;
• status of software update and configuration file upload/download.
• Restart SNMPd– pressing the button restarts the SNMP client;

• Download MIB file– download the current MIB file.
Buttons are used to create, edit and delete trap parameters:
- Add;
– Edit;
- Delete.
Network Services →SNMP→ Parameter settingSNMP traps→
• Type– SNMP message type (TRAPv1, TRAPv2, INFORM);

• Community– password contained in traps;
• IP address -trap receiver IP address;
• Port– Trap receiver UDP port (standard port is 162).
313
4.1.14.5 DHCP server settings

Host Configuration ProtocolDynamic Host Configuration Protocol (DHCP)automatically assigns an IP
addresses to network devices.
Upon receiving a request,The DHCP server selects an IP address from a pool of addresses in its database and
offers it to the DHCP client. If he accepts the offer, then the network settings, i.e. IP address, mask and others
parameters are leased to the client for a certain period.
Network Services →DHCP server
314
OptionsDHCP Servers:
• Enable DHCP Server– if the flag is set, the DHCP server is started at the gateway startup;
• network interface– selection of a network interface for a DHCP server;
• Starting IP address– starting address of the range of assigned IP addresses;
• Destination IP address– end address of the range of assigned IP addresses;
• Subnet mask– network mask;
• DNS server address 0/1/2/3– addresses of DNS servers from the operator's network;
• Gateway/router address– the address of the router or default gateway assigned by clients
DHCP server
• wins address– IP address of the WINS server in the operator's network;
• domain name– network domain name;
• Number of leased addresses– setting the quantity limit at the same time leased
addresses;
• Minimum address lease time, sec– setting the minimum usage time clientDHCP-assigned IP
address for at least 10 seconds;
• Maximum address lease time, sec– setting the maximum usage time clientDHCP-assigned IP
address, from 10 to 10,000,000 seconds;
• Database saving period, sec- the period of time after which the device will save information about
leased addresses to a filedhcpd.leases. Use "off" to do not save information about leased addresses;
• Address reserve time upon receipt of a failure, sec– period of time for which the IP address will be
reserved for the client in case of receiving a rejection message (DHCP decline), at least 10 seconds;
• Address reserve time in case of ARP conflict, sec– period of time for which the IP address will be
reserved for the client in case of detection of a MAC address conflict, at least10 Seconds;
• Suggested address reserve time, sec– the period of time for which the IP address requested by the
client will be reserved, at least 10 seconds;
• Advertise local NTP server– the option will be available only if the local NTP server is activated in the
“NTP” section and the interface for it is specified. When this option is enabled, the DHCP server will
advertise in option 42 the configured address of the local NTP server;
• Advertise an arbitrary NTP server– when this option is enabled, the DHCP server will
announce in option42 server addresses specified in the "NTP Server Address" option;
• NTP server address– address of the NTP server that the SMG will advertise in option 42 if the
option "Announce randomNTP server.
ControlDHCP server
• Server start– start the DHCP server;
• Server stop– stop the DHCP server;
• Erase records -delete established IP-MAC mappings in the memory of the DHCP server.
BindingIP-MAC addresses -assignment of static correspondences of IP and MAC addresses.
315
To assign a new correspondence to editing and deleting parameters, use the buttons:
- Add;
– Edit;
- Delete.
Network Services →DHCP server→ BindingIP-MAC addresses→
• Name– match name;

• IP address– client IP address;
• MAC address– MAC address of the client.
IssuedIP addresses:
• MAC address– MAC address of the client;

• IP address– address issued from the pool of IP addresses;
• Lease expires– the time after which the lease of the given address expires:
• Expired– address lease has expired.
316
4.1.14.6 FTP server

This section configures the built-inFTP server for providing access by protocolFTP to directories:
• cdr – directory with CDR record files;

• log – directory with trace files and other debugging information;
• mnt – directory with files from external drives (SSD drives, SATA drives, USB flash drives).
OptionsFTP servers:
Network Services →FTP server
• Use -option to enable/disable the use of a local FTP server;

• network interface– select the network interface on which the FTP server will be launched;
• Port -selection of the TCP port on which the FTP server will be launched;
• Authorization timeout, sec– time of entering data for subscriber authorization on the FTP server, according to
when it expires, the server will forcibly disconnect the connection;
• Idle timeout, sec– user idle time on the FTP server, after its expiration the server will forcibly close the
connection;
• Session timeout, sec– session duration time.
317
User setup:
By default, a subscriber is created on the device with the rights to read all directories with the loginftpuserAnd
passwordftppasswd.
Network Services →FTP server
• Name -Username;
• Password– user password;
• log access– configuration of access to the log directory, read/write;
• Access to mnt– configuration of access to the mnt directory, read/write;
• Access to CDR– configuring access to the CDR directory, reading/writing;
• Access to configuration -setting access to the /etc/config directory, read/write.
4.1.15 Network Utilities
4.1.15.1 PING
The utility is used to check the connection (the presence of a route) to a device on the network.
Network Utilities →PING
IP Probing– used for one-time control of the connection to the device in the network.
For transmissionPing request (using ICMP protocol)you must enter an IP address or network host name in
field"IP probing"and press the buttonPing.The result of the command will be displayed in bottom of the
page. The result indicates the number of transmitted packets, the number
318
the responses received, the percentage of losses, as well as the time of reception and transmission (minimum /
average / maximum) in milliseconds.
Network Utilities →PING
Periodicping– used to periodically monitor connections to devices on the network.

• Run at device startup– when the flag is set, send ping requests to the addresses specified in the
list of hosts will be activated immediately after the device is started;
• Period, min– interval between requests in minutes;
• Number of attempts– number of attempts to send a request to the address.
State
• Restart– start/restart periodic ping;
• Stop– forced stop of periodic ping;
• Information– by pressing this button, the log file '/tmp/log/ hosttest.log' with data on the last
attempt of a periodic ping request will be available for viewing.
ListIP addresses-a list of IP addresses to which periodic ping requests will be sent.
To add a new address to the list, you must specify it in the input field and click the button "Add". To
delete, click the button"Delete"opposite the desired address.
319
4.1.15.2 TRACEROUTE
UtilityTRACEROUTEperforms the functions of route tracing and echo tests (transmitting ping requests) for
network diagnostics. This function allows you to evaluate the quality of the connection to the tested node.
Network Utilities →TRACEROUTE
In the "Host name orIP address to check the quality of the connection” enter the IP address of the
network device to which the connection quality is evaluated. To use options, you must set a flag in the
corresponding line.
Options:
• Number of transmitted packets– number of ICMP request transmission cycles;

• Packet size to send– ICMP packet size in bytes;
• Display IP addresses instead of hostnames- do not use DNS. Display IP addresses without attempts
to obtain their network names;
• Delay between ICMP requests (default 1 sec)– polling interval;
• Use only IPv4– use only IPv4 protocol;
• Use only IPv6– use only IPv6 protocol;
• Network interface address for sending ICMP requests– IP address of the network interface, s
which will be sentICMP requests.
After enteringIP addresses of the network device to which the quality of the connection and installation is
evaluated options, press the button"Check".
As a result of the utility, a table is displayed containing:
• node number and its IP address (or network name);
• percentage of lost packets (Loss%);
• number of packets sent (Snt);
• round trip time of the last packet (Last);
• average packet round trip time (Avg);
• the best round trip time of the package (Best);
• worst packet round trip time (Wrst);
• the standard deviation of delays for each node (StDev).
Network Utilities →TRACEROUTE→ EnterNetwork Device IP Addresses
320
4.1.16 Security
4.1.16.1 Configuring SSL/TLS

Security → SettingsSSL/TLS
This section is designed to obtain a self-signed certificate that allows you to use an encrypted
connection to the gateway using the protocolHTTP and file upload/download protocol configurations
FTPS.
• Protocol for interaction with the web configurator– mode of connection to the web-configurator:
• HTTP or HTTPS– both unencrypted connections are allowed – via HTTP, and encrypted - by
HTTPS. At the same time, connection via HTTPS is possible only if there is generated certificate;
• HTTPS only– only encrypted connection via HTTPS is allowed. Connecting via HTTPS is only
possible with a generated certificate.
Generate new certificates
-These parameters must be entered in Latin letters.
• Two-digit country code– country code (for Russia – RU);

• Region- the name of the region, region, territory, republic, etc.;
• City- city name;
• Organization- Name of the organization;
• Subdivision- the name of the division or department;
• Contact e-mail- E-mail address;
• Device name (or IP address)– Gateway IP address.
DownloadPEM certificate and key
The section allows you to download a pre-generated and signedPEM certificate and key. For download,
select the type of downloaded file from the drop-down menu. Push button"Review"and select the
desired file. Then press the button"Download".
-After downloading the certificate and key, you will need to restart the web server with the button
"Restart web server".
321
4.1.16.2 Dynamic firewall

Dynamic firewallis a utility that monitors attempts to access various services. Upon detection of constantly
repeated unsuccessful attempts to access from the sameIP address or host fail2ban blocks further
attempts from this IP address/host.
Failed attempts can be identified as:
• selection of authentication data for the web-configurator or via the SSH protocol, i.е. attempts enter the
management interface with an incorrect username or password;
• authentication data guessing - accepting REGISTER requests from a known IP address, but with
incorrect authentication data;
• receiving requests (REGISTER, INIVITE, SUBSCRIBE, and others) from an unknown IP address;
• receiving unknown requests on the SIP port.
Security → Dynamic Firewall
Options:
• Turn on– run the dynamic firewall utility;
• Blocking time, s– time in seconds during which access from a suspicious addresses will be
blocked;
• Forgiveness time, s– the time after which the address from which the problem request came will be
forgotten if it has never been blocked;
• Number of access attempts– the maximum number of unsuccessful attempts to access the
service, before the host is blocked by a dynamic firewall;
• Number of temporary locks– the number of locks, after which the problematic address will be
forcibly blacklisted;
• progressive blockage– when the flag is set, each successive blocking of the address will be twice the
previous one, and half as many access attempts will be used to block the address. For example, the first
time the address was blocked on30 seconds after 16 attempts,
322
for the second time -60 seconds after 8 attempts, the third time - 120 seconds after 4 attempts, and so on
Further.
Whitelist (latest30 records)– a list of IP addresses or subnets that cannot be blocked by a dynamic
firewall.
-Whitelisting does not mean that access will be allowed. For whitelisted addresses no permission rules
are created. The presence of an address in the whitelist only means that this address will not be
automatically blocked.
Blacklist (latest30 records)– list of banned addresses or subnets, access from which will always be blocked.
Total can be created up to8192 entries on SMG-1016M and 16384 entries onSMG-2016 and SMG-3016. To
add/search/delete an address in the list, you need to enter it in the input field and click the buttonAdd/Find/
Remove.
It is possible to enter asIP address and subnet.
To enter a subnet, you must enter data in the following format:
AAA.BBB.CCC.DDD/mask
Example:
192.168.0.0/24 – the entry corresponds to the network address 192.168.0.0 with the mask 255.255.255.0
• Download full white/black list of IP addresses– the web configurator displays only the last 30 records
in the file, clicking on this button allows you to download the entire white or blacklist on the
computer.
List of blocked addresses– list of addresses blocked during dynamic firewall operation. There can be
up to8192 entries on SMG-1016M and 16384 entries on SMG-2016 and SMG-3016.
• Download full list of blocked IP addresses- allows you to download the entire list blocked
addresses on the computer.
Lists are updated at the click of a button."Update"opposite the title. The log file of the
dynamic firewall is located in the filepbx_sip_bun.log.
4.1.16.3 Blocked addresses log

This section displays a log of addresses blocked by the dynamic firewall, which allows you to analyze
when and which addresses have been blocked since the gateway was turned on.
Security → Blocked addresses log
• Search -address entry, to search in the table of blocked addresses;

• IP address -The IP address that was blocked;
323
• Lock date -date and time when the IP address was blocked;
• Reason for blocking- an explanation of which service and for what the blocking was made;
• Update -update the log of blocked addresses;
• Clear log -delete all entries from the blocked addresses log.
The table below lists the blocking messages and their causes. Table28 - Lock messages
Message in file Cause MessageSIP

pbx_sip_bun.log
Request error: REGISTER failed : Dynamic user registration limit Answer403

Resource limit overflow reached
Request error: REGISTER failed : Unknown user registration request Answer403

Unknown user or registration domain
Request error: REGISTER failed : A registration request in which the Answer403

Server doesn't allow a third party headersTo and From are different
registration
Request error: REGISTER failed : Invalid username/password Answer403

Authentication is wrong
Request error: REGISTER failed : Deregistration attempt Answer200

Wrong de-registration user
unregistered contact
Request error: REGISTER failed : Attempt to register from an address Answer403

Request from disallowed IP different from the allowed one
Request error: INVITE failed : No A call was attempted from a user who Answer403
registration before is known, but his contact was not
registered
Request error: INVITE failed : A call was attempted from a user Answer403
Registration is expired who is known, but his contact
registration has expired
Request error: INVITE failed : Incoming call or registration was Answer403

Authentication is wrong not authenticated
Request error: INVITE failed : Call from unknown destination The call is routed tomgapp, where a
Unknown original address decision is made to pass or reject it
Request error: INVITE failed : RURI not Unknown hostname or address in response404
for me ruri
324
Message in file Cause MessageSIP

pbx_sip_bun.log
Request error: BYE failed : Call/ No dialog found to accept Answer481

Transaction Does Not Exist request
4.1.16.4 Static firewall

firewallorfirewall— a set of software tools that control and filter network packets transmitted through it in
accordance with the specified rules, which is necessary to protect the device from unauthorized access.
-Firewall rules won't work to restrict access by protocolHTTP/HTTPS, SSH, Telnet, SNMP, FTP. To restrict
access via these protocols, use the list permittedIP addresses (sectionList of allowed IP addresses)
and activation settings services on network interfaces (sectionNetwork interfaces).
Profilesfirewall
To create, edit and delete profilesfirewall buttons are used:
Security → Static firewall
• «Add";
• "Edit";
• "Delete".
The software allows you to set up rulesfirewall for incoming, outgoing and transit traffic, as well as
for certain network interfaces.
325
Security → Static Firewall → Object
When creating a rule, the following parameters are configured:

• Name– rule name;
• Use– determines whether the rule will be used. If the flag is not set, then the rule will be inactive;
• Traffic type– type of traffic for which the rule is created:

• incoming– designed for SMG;
• outgoing- sent SMG.
• Rule Type -can take values:
• Normal -rule with checking IP addresses and ports;
• GeoIP -rule with address verification based on GeoIP;
• String-a rule that checks if a string is in the packet.
Security → Static Firewall → Object → Rule Type (Normal)
326
Security → Static Firewall → Object → Rule Type (string)
Security → Static Firewall → Object → Rule Type (GeoIP)
• Package Source– specifies the network address of the packet source either for all addresses, or for a
specificIP addresses or networks:
• any– for all addresses (checked);
• IP address/mask– for a specific IP address or network. The field is active when the flag is unchecked
"any".A network mask must be specified for the network.IP addresses specifying a mask is not
Necessarily;
• Source Ports −TCP/UDP port or range of ports (specified with a dash "-") package source. This
parameter is used only for protocolsTCP and UDP therefore, in order for this field to become
active, you must select the protocol in the fieldUDP, TCP orTCP/UDP.
327
• Destination address– defines the network address of the packet receiver either for all addresses, or for a
specificIP addresses or networks:
• any– for all addresses (checked);
• IP address/mask– for a specific IP address or network. The field is active when the flag is unchecked
"any". A network mask must be specified for the network.IP addresses specifying a mask is not
Necessarily;
• Destination ports -TCP/UDP port or range of ports (specified with a dash "-") packet receiver.
This parameter is used only for protocolsTCP and UDP therefore, in order for this field to
become active, you must select the protocol in the fieldUDP, TCP, or TCP/UDP.
• Protocol– protocol for which the rule will be used: any, UDP, TCP, ICMP or TCP/UDP;
• Message type (ICMP)– ICMP message type for which the rule is used. This field is active if the field
"Protocol"selectedICMP;
• Action– action performed by this rule:
• ACCEPT– packets matching this rule will be passed by the firewall;
• DROP– packets that fall under this rule will be dropped by the firewall without any
information to the party that transmitted the packet;
• REJECT– packets matching this rule will be dropped by the firewall. Either a TCP RST packet
or an ICMP destination unreachable will be sent to the sender of the packet.
• A country -select the country to which the address belongs. The field is displayed only for the rule
type"GeoIP";
• Content -string to be contained in the package. The string will be searched for the contents of the
package are case-sensitive. The field is displayed only for the type rule"String".
The created rule will fall into the appropriate section:"Rules for incoming traffic","Rules for outgoing traffic"
or"Rules for transit traffic".
also inprofilefirewallit is possible to specify the network interfaces for which will be used profile rules.
-Each network interface can only be used in one profile at a time firewall. When you try to assign a
network interface to a new profile from an old one, it will removed.
To apply the rules, click on the button"Apply”, which will appear if settingsfirewall changes have
been made.
328
4.1.16.5 List of allowed IP addresses

This section configures the list of allowedIP addresses from which the administrator can connect to the
device viaweb configurator, as well as Telnet and SSH protocols. Default all addresses are allowed.
Security → Allowed listIP addresses
• Access only for authorized IP addresses- when the flag is set, the list is applied permittedIP
addresses, otherwise access is allowed from any address.
It is possible to allow access for subnets, for this you need to specify the address in the formatIP/
mask, for example: 192.168.0.0/24.
• Apply -apply changes;
• Confirm -confirm changes.
To create, edit and delete the list of allowed addresses, use the buttons:
Security → Allowed listIP addresses→ Add
- Add;
– Edit;
- Delete.
-After generating the list of addresses, you must click the button"Apply"And "Confirm",if within60
seconds do not confirm changes, settings are returned to preset values - this allows you to protect
the user from losing access to the device.
329
4.1.16.6 SMG network protection scheme

OnSMG works in the following order of working out the rules of dynamic and static firewall, list of banned
addresses and access restrictions from network interfaces:
1. Dynamic firewall rules are processed (sectionDynamic firewall). At this stage, requests from addresses
that are in the black list and the list of temporary blocks are reset.
2. Access restrictions are being worked out, configured in sectionsNetwork interfaces-> Services and
Allowed ListIP addresses. For each management service (WEB, Telnet, SSH, SNMP) allowed to work on
the network interface, rules are created that allow access with any ofIP addresses. Access to other
management services is blocked. When the list is activated permittedIP addresses access rules are
supplemented by source IP address control - connections are allowed only from the addresses
specified in the list.
3. Other access is allowed to network interfaces to which there are no rule bindings static
firewall.
4. Static firewall rules are being worked out (sectionStatic firewall) on those network interfaces to
which the rules are bound.
-If one of the rules from the list has worked, then the remaining rules will not be applied to the request.
will.
4.1.16.7 Ensuring typical SMG firewall tasks

Restricting access to management by protocolsWEB/Telnet/SSH/SNMP.
To restrict access to management, useNetwork interfaces-> Services and Allowed ListIP addresses. First, on
the network interfaces where you need to allow access, the flags of the protocols for which access must be
allowed are set. Thus, a restriction on the destination address will be set. After that, the list of allowed IP
addresses, which will additionally set a restriction on the source address for addresses from the list.
Restricting access to interfacesSIP/H.323 specific addresses and/or geographic

locations.
To do this, you need to configure a static firewall (sectionStatic firewall). Using the example of setting up
access with the following restrictions:
• Allow access from Russia;
• Allow access from subnet 34.192.128.128/28;
• Restrict access from other addresses.
To do this, create three static firewall rules in the following order:
1. Rule for incoming traffic with type "GeoIP" and country "Russian Federation (RU)". Action - Accept;
2. Rule for incoming traffic with type "Normal" and IP address and source mask
"34.92.128.128/255.255.255.240". Action - Accept;
3. Rule for incoming traffic with type "Normal", packet source "Any". Action - Drop.
After that, select the required network interfaces in the list of interfaces and save the settings.
Complete restriction of access toSMG from a specific address or subnet
This restriction can be implemented by activating the dynamic firewall (sectionDynamic firewall), and blacklist
the address or subnet. Please note - if the addresses are too a lot, it is better to go from the opposite and
create static firewall rules (sectionStatic firewall) according to the principle "first allow connection to trusted
nodes, then discard everything" and
330
settings for restricting access through the list of allowedIP addresses (sectionList of allowed IP addresses);
Automatic blocking of failed requests/authorizations

Performed by a dynamic firewall (sectionDynamic firewall). You must activate the dynamic firewall and
configure the trigger conditions. It is also recommended that you whitelist those addresses and subnets that
should not be subject to auto-block rules.
4.1.17 RADIUS setting
4.1.17.1 RADIUS servers

RADIUS→ Servers
The device supports up to8 authorization servers (Authorization) and up to 8 billing servers (Accounting).
Servers can be combined into groups and then, when configuring RADIUS profiles, choose which group of
servers will be used to send requests. Four groups are available.
• Server response timeout– time during which the server response is expected;
• Number of attempts to send a request– the number of retries of the request to the server. With unsuccessful
when all attempts are used, the server is considered inactive, and the request is redirected to another server, if it
is specified, otherwise an error is detected;
• Server downtime on failure- the time during which the server is considered inactive (no
requests are sent to it);
• Network interface for group <N>– selection for the corresponding network interface group, through
which requests will be sentRADIUS;
• WEB/telnet/ssh user authorization via RADIUS-authorization servers- upon attempt user login by
WEB/telnet/ssh authorization will take place on the RADIUS server.
331
You must first create a local user with the necessary names and configure their access rights (see.
Control Menu) Setting a password for access through the web-configurator);
• Allow access if RADIUS server fails– if authorization is enabled users onRADIUS and no response was
received from the RADIUS server, you can log in use the locally configured administrator account (
admin).
4.1.17.2 Profile list

RADIUS→ Profile list
The following buttons are used to create, edit and delete the list of profiles:
- Add;
– Edit;
- Delete.
332
RADIUS→ Profile list → Object
333
Profile settingsRADIUS
• Name– profile name;
• Use RADIUS-Authorization– enables/disables sending authentication messages/ authorization (Access
Request) to a RADIUS server;
• Use RADIUS Accounting– enables/disables sending billing messages (Accounting Request) to the
RADIUS server;
• Send reports via SNMP– Enables sending SNPM traps each time a RADIUS request is sent.
• Group– a group of RADIUS servers used to send requests.

Modification options:
• InCdPN modifiers– selection of the called subscriber number modifier (CdPN) for incoming
connection, as applied to fieldsCalled-Station-Id, xpgk-dst-number-in in messagesRADIUS-
Authorization and RADIUS-Accounting;
• InCdPN number– selection of the number sent in the xpgk-dst-number-in field in the RADIUS-Authorization
and RADIUS-Accounting messages:
• original– the original number that was received in the CdPN field of the incoming call before it
modifications;
• processed– CdPN number after its modification.
• Modifiers InCgPN– selection of the calling party number modifier (CgPN) for incoming
connection, as applied to fieldsCalling-Station-Id, xpgk-src-number-in messagesRADIUS-
Authorization and RADIUS-Accounting;
• Number InCgPN– selection of the number sent in the xpgk-dst-number-in field in the RADIUS-Authorization
and RADIUS-Accounting messages:
• original– the original number that was received in the CgPN field of the incoming call before it
modifications;
• processed– CgPN number after its modification.
• Redirecting Modifiers– selection of a redirect number modifier (RedirPN) in the h323-redirect-
number field in the RADIUS-Authorization and RADIUS-Accounting messages;
• OutCdPN modifiers– selection of the called subscriber number modifier (CdPN) for outgoing
connection, as applied to the fieldxpgk-src-number-out in RADIUS-Authorization and RADIUS-
Accounting messages;
• OutCgPN Modifiers– selection of the calling party number modifier (CgPN) for outgoing
connection, as applied to the fieldxpgk-dst-number-out in RADIUS-Authorization and RADIUS-
Accounting messages.
OptionsRADIUS Authorization:
Send requests via incoming communication. Authentication/Authorization requests can be sent at
different moments of the call:
• during an incoming session (only CgPN);
• at end of dialing (CgPN and CdPN) – upon receipt of the full dialing number;
• for local forwarding.
Send outbound requests.An authentication/authorization request can be sent:
• during an outgoing session.
Checking calls toRADIUS can be limited based on the modifier mask. For this it is necessary select one or
more modifiers in the "Modification Options»and set the option "Send requests based on modifiers"into
the meaning of "Limited". In this case authorization request will go toRADIUS only if the number matches
one of the masks in modifier tables. Modification will then be carried out as usual, according to the rules in
the modification table.
334
-When request restriction based on modifiers is enabled, those calls whose numbers are not hit the
modifier mask will be considered automatically authorized.
Restrict outgoing communication when the server fails.If the server fails (no response is received from the server), it
is possible to set restrictions on outgoing communication:
• no restrictions– allow all calls;

• only local and area networks- allow calls to special services, departmental, local and zonal
network;
• local network only– allow calls to special services, departmental and local networks;
• only special services- allow calls only to special services;
• everything is forbidden– bar all calls.
This restriction determines whether a call can be routed by the prefix on which the corresponding
type is set (local, long distance, etc.).
• USER-NAME field– selection of the User-Name attribute value in the corresponding Access Request
authorization packet (RADIUS-Authorization):
• CgPN– use the telephone number of the calling party as the value;
• CDPN– use the telephone number of the called party as the value;
• IP or E1 stream– use the IP address of the calling party as the value, or the number of the
stream on which the incoming connection is made;
• Trunk name– as a value, use the name of the trunk through which incoming connection;
• Original CgPN– use unmodified phone number as value the calling party;
• Original CDPN– use unmodified phone number as value called party;
• Login– use the login from the authorization of the sip subscriber as the value.
• Redirect Number– RedirPN transfer mode to RADIUS:
• replace Calling-Station-Id– RedirPN will be passed in the Calling-Station-Id field, overwriting
existing value;
• pass in h323-redirect-number– RedirPN will be passed separately in the h323-redirectnumber
field.
• USER-PASSWORD field- setting the value of the User-Password attribute in the corresponding package
authorizationRADIUS Authorization;
• Individual passwords for SIP subscribers– when the flag is set, use individual passwordsSIP
subscribers during authentication/authorization instead of a password, configured in the field
USER-PASSWORD;
• DIGEST authorization– selection of the authorization algorithm for subscribers with dynamic registration
throughRADIUS server. With digest authentication, the password is not transmitted in clear text, as with
using basic authentication, but in the form of a hash code and cannot be intercepted when scanning
traffic:
• RFC5090 (full implementation of RFC5090 recommendation);
• RFC5090-no-challenge (working with a server not transmitting an Access Challenge);
• Draft-sterman (NetUp) (draft work on the basis of which recommendationRFC5090).
• Session time– setting the maximum call duration limit:

• Ignore– do not use the possibility of limiting the maximum call duration;
• Consider Session-Time– use to limit the maximum call duration attribute

valuesession-timeout(27);
• Consider Cisco h323-credit-time– use to limit the maximum call duration valueCisco
VSA(9) h323-credit-time(102);
335
• Session-Time Priority– if both parameters (sessiontime and Cisco h323-credit-time) are present
in the response from the server, then session-time is used, and Cisco h323-credit-time ignored;
• Cisco h323-credit-time priority– if both parameters (session-time and Cisco h323-credit-time) are
present in the response from the server, then Cisco h323-credit-time is used, and session-time
ignored.
-GatewaySMG can use attribute valueSession-Timeoutor attribute Cisco VSA h323-credit-

timefrom the Access-Accept package to limit the maximum duration of the authorized
call.
• Allow access to special services when receiving a connection refusal from the server- at receiving
Access-Reject from the server to allow a call to the special services host.
Setting optional package attributesAuthentication Request:
• NAS Port Type -type of physical port of the NAS (server where the user is authenticated), according
to defaultasync;
• Service Type-service type, not used by default (Not Used);
• framed-protocol-protocol, specified when using packet access, default is not used (not used);
• class– processing the AV-Pair Class field to change the category:

• not used– do not process the AV-Pair Class field;
• SS7 category– use the value of the received AV-Pair Class field as the SS-7 category caller.
OptionsRADIUS Accounting:
Send requests:
• accounting start– send an accounting start packet notifying the RADIUS server about the start of
conversation;
• accounting-stop– send an accounting stop packet notifying the RADIUS server about end of
the conversation;
• accounting-stopfor unsuccessful calls, send information about the call to the RADIUS server
unsuccessful calls;
• accounting-update with a period– transmit during a conversation to a RADIUS server with a specified
period packageupdate, indicating the activity of the current conversation;
• accounting for call-origin=originate– sending RADIUS-Accounting messages for the incoming leg
connections;
• accounting for call-origin=answer– sending RADIUS-Accounting messages for the outgoing leg
connections.
Sending billing information toRADIUS can be limited based on the modifier mask. For To do this, you must
select one or more modifiers in the "Modification Options»and set the option"Send requests based on
modifiers"into meaning"Limited". In that billing information will go toRADIUS only if the number matches
under one of the masks in the modifier tables. Modification will then be carried out as usual, according to the
rules in the modification table.
-When you enable request restriction based on modifiers for calls whose numbers did not fall into the
modifier mask, billing information will not be sent.
• Cisco Customization– swaps originate and answer sides in accounting messages;

• Send time in UTC format– transmission of time in RADIUS-Accounting messages in formatUTC;
336
• Duration Rounding– selection of time rounding in RADIUS-Accounting messages. Three options
are available - round up, round down, and don't round (transmit milliseconds).
Restrict outgoing communication when the server fails.If the server fails (no response is received from the server), it
is possible to set restrictions on outgoing communication:
• no restrictions– allow all calls;

• only local and area networks- allow calls to special services, departmental, local and zonal
network;
• local network only- allow calls only to special services;
• everything is forbidden– bar all calls.
This restriction determines whether a call can be routed by the prefix on which the corresponding
type is set (local, long distance, etc.).
• USER-NAME field– selection of the User-Name attribute value in the Accounting Request (RADIUS-
Accounting) packet:
• CgPN– use the telephone number of the calling party as the value;
• CDPN– use the telephone number of the called party as the value;
• IP or E1 stream– use the IP address of the calling party as the value, or the number of the
stream on which the incoming connection is made;
• Trunk name– as a value, use the name of the trunk through which incoming connection;
• Original CgPN– use unmodified phone number as value the calling party;
• Original CDPN– use unmodified phone number as value called party.
• Redirect Number– RedirPN transfer mode to RADIUS:

• replace Calling-Station-Id– RedirPN will be passed in the Calling-Station-Id field, overwriting
existing value;
• pass in h323-redirect-number– RedirPN will be passed separately in the h323-redirectnumber
field.
• CDPN field– selection of the value of the called subscriber number, which is used when
package formationRADIUS for some Attribute-Value pairs (sectionDescription variables):
• CDPN-in– use the called party number before modification (number received in requestSETUP/
INVITE);
• CDPN-out– use the called party number after modification.
• CgPN field– select the value of the caller's number, which is used when package formation
RADIUS for some Attribute-Value pairs (sectionDescription variables):
• CgPN-in– use the caller's number before the modification (number received in requestSETUP/
INVITE);
• CgPN-out– use the caller's number after modification.
Answer matchesRADIUS and voice messages
When receiving a messageReject from the RADIUS server, it is possible to issue a standard gateway voice
message to inform the subscriber about the reason for connection failure. The issuance of a voice message
is based on the analysis of the fieldreplay-Message or h-323-return-code messagesreject.
• Correspondence table of RADIUS responses and voice messages– selection of a lookup table response
RADIUS-reject and voice message;
• RADIUS response attribute– selection of the attribute by which the analysis of the RADIUS-reject message will be
performed.
337
OptionsEltex-VSA
• Use Eltex-VSA for call control– activation of the Radius call management service (when having a license
RCM), a description of the Radius call management service is given inAppendix I. ServiceRADIUS CALL
MANAGEMENT;
• Use full CISCO-VSA value– transfer of the full name of the attributes in the CISCO-VSA fields.
Transfer"real ip" in RADIUS-Accounting

Upon receipt inINVITE message in the From field of the real ip parameter, this field is transmitted V
Framed-Ip-Address (8) RADIUS-Accounting.
4.1.17.3 Correspondence tables of RADIUS responses and voice messages.

This section configures response matchingRADIUS-reject and voice messages, issued to subscribers.
RADIUS→ Correspondence tables of answersRADIUS and voice messages
The menu is used to create, edit and delete tables."Objects" - "Add object", "Objects" - "Edit object"And
– “Add table”;
– “Edit table”;
- Delete table.
RADIUS→ Correspondence tables of answersRADIUS and voice messages
338
RADIUS→ Correspondence tables of answersRADIUS and voice messages→
• RADIUS response– value of the replay-Message field or h-323-return-code of the Reject message from the
RADIUS server;
• A voice message– selection of a voice message to be delivered to the subscriber.
4.1.17.4 RADIUS packet format

The description of each package consists of a description of all Attribute-Value pairs (Attribute-Value Pair) for
this package type. Attributes can be either standard or vendor-specific attributes (Vendor-Specific Attribute).
If for some reason the value of an attribute is unknown (for example, when in the absence of an outgoing
trunk, it is impossible to determine the value of the variablecdPN_OUT, which is used as the value of some
attributes), then that attribute is not added to the message.
For standard attributes, the description looks like:
Attribute name (Attribute number): Attribute value
For vendor attributes view:
Attribute Name (Attribute Number): Vendor Name (Vendor Number): NameVSA (VSA Number): VSA value
Where:
Attribute name- AlwaysVendor specific;

Attribute number- Always26; Vendor
name– vendor name;
Vendor number– vendor number assigned to it by the organizationIANA document “PRIVATE
ENTERPRISE NUMBERS” (http://www.iana.org/assignments/enterprise-numbers);
"NameVSA”– vendor attribute name; "Number
VSA”– vendor attribute number; "MeaningVSA”–
vendor attribute value.
-The attribute value can be a construction of the form<$NAME>,WhereNAME- This variable name. The
meaning of the variables is described in the sectionDescription of variables.
339
Package Access-Request
User-Name(1): <$USER_NAME>
User-Password(2): based on password "eltex" (without quotes) NAS-
IP-Address(4): <$SMG_IP>
Called-Station-Id(30): <$CdPN_IN>
Calling-Station-Id(31): <$CgPN_IN>
Acct-Session-Id(44): <$SESSION_ID>
NAS-Port(5): <$NAS_PORT>
NAS-Port-Type(61): Virtual(5) Service-
Type(6): Call-Check(10) Framed-IP-Address:
<$USER_IP> Starter packAccounting
Request Acct-Status-Type(40) – Start(1)
User-Name(1): <$USER_NAME> Called-
Station-Id(30): <$CdPN> Calling-Station-
Id(31): <$CgPN_IN> Acct-Delay-Time(41):
RFC2866 Event-Timestamp(55): RFC2869
NAS-IP-Address(4): <$SMG_IP>
Acct-Session-Id(44): <$SESSION_ID>
Framed-IP-Address: <$USER_IP>
Vendor-Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-src-number-in=<$CgPN_IN> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-src-number-out=<$CgPN_OUT> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-dst-number-in=<$CdPN_IN> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-dst-number-out=<$CdPN_OUT> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-route-retries=< $ROUTE_RETRIES>
Vendor-Specific(26): Cisco(9): Cisco-AVPair(1): h323-remote-id=<$DST_ID>Vendor-Specific(26): Cisco(9): Cisco-
AVPair(1): h323- call-id=<$CALL_ID>
Vendor-Specific(26): Cisco(9): h323-remote-address(23): h323-remote-address=<$DST_IP> Vendor-
Specific(26): Cisco(9): h323-conf-id(24 ): h323-conf-id=<$CALL_ID> Vendor-Specific(26): Cisco(9):
h323-setup-time(25): h323-setup-time=<$TIME_SETUP> Vendor-Specific(26): Cisco(9): h323-call-
origin(26): h323-call-origin=originate Vendor-Specific(26): Cisco(9): h323-call-type(27): h323-call-
type=<$ CALL_TYPE> Vendor-Specific(26): Cisco(9): h323-connect-time(28): h323-connect-
time=<$TIME_CONNECT> Vendor-Specific(26): Cisco(9): h323-gw-id (33): h323-gw-id=<$SMG_IP>
Vendor-Specific(26): Eltex Enterprise, Ltd.(35265): Incoming-SIP-call-id(2): <$inc_SIP_call_ID> Vendor-

Specific(26): Eltex Enterprise, Ltd.(35265): Outgoing-SIP -call-id(3): <$out_SIP_call_ID> Vendor-Specific(26):
Eltex Enterprise, Ltd.(35265): Incoming-RTP-local-address(4): <$inc_RTP_loc_IP>
340
Vendor-Specific(26): Eltex Enterprise, Ltd.(35265): Incoming-RTP-remote-address(5): <$inc_RTP_rem_IP>
Vendor-Specific(26): Eltex Enterprise, Ltd.(35265): Outgoing-RTP -local-address(6): <$out_RTP_loc_IP>
Vendor-Specific(26): Eltex Enterprise, Ltd.(35265): Outgoing-RTP-remote-address(7): <$out_RTP_rem_IP>
Vendor-Specific(26): Eltex Enterprise, Ltd.(35265): call-record-file=<$call_record_file_name> Stop
packageAccounting Request Acct-Status-Type(40) – Stop(2) User-Name(1): <$USER_NAME> Called-
Station-Id(30): <$CdPN> Calling-Station-Id(31): <$CgPN_IN> Acct-Delay-Time(41): RFC2866 Event-
Timestamp(55): RFC2869 NAS-IP-Address(4): <$SMG_IP>
Acct-Session-Id(44): <$SESSION_ID> Acct-

Session-Time(46): <$SESSION_TIME>
Framed-IP-Address: <$USER_IP>
Vendor-Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-src-number-in=<$CgPN_IN> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-src-number-out=<$CgPN_OUT> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-dst-number-in=<$CdPN_IN> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-dst-number-out=<$CdPN_OUT> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-route-retries=< $ROUTE_RETRIES> Vendor-
Specific(26): Cisco(9): Cisco-AVPair(1): h323-remote-id=<$DST_ID Vendor-Specific(26):
Cisco(9): Cisco-AVPair(1): h323-call-id=<$CALL_ID>
Vendor-Specific(26): Cisco(9): Cisco-AVPair(30): h323-disconnect-cause=<$DISCONNECT_CAUSE>
Vendor-Specific(26): Cisco(9): Cisco-AVPair(1): xpgk-local-
disconnectcause=<$LOCAL_DISCONNECT_CAUSE>
Vendor-Specific(26): Cisco(9): h323-remote-address(23): h323-remote-address=<$DST_IP Vendor-Specific(26):
Cisco(9): h323-conf-id(24) : h323-conf-id=<$CALL_ID> Vendor-Specific(26): Cisco(9): h323-setup-time(25):
h323-setup-time=<$TIME_SETUP> Vendor-Specific(26): Cisco (9): h323-call-origin(26): h323-call-
origin=originate Vendor-Specific(26): Cisco(9): h323-call-type(27): h323-call-type=<$CALL_TYPE > Vendor-
Specific(26): Cisco(9): h323-connect-time(28): h323-connect-time=<$TIME_CONNECT Vendor-Specific(26):
Cisco(9): h323-disconnect-time(29 ): h323-disconnect-time=<$TIME_DISCONNECT> Vendor-Specific(26):
Cisco(9): h323-gw-id(33): h323-gw-id=<$SMG_IP>
Vendor-Specific(26): Eltex Enterprise, Ltd.(35265): Incoming-SIP-call-id(2): <$inc_SIP_call_ID> Vendor-

Specific(26): Eltex Enterprise, Ltd.(35265): Outgoing-SIP -call-id(3): <$out_SIP_call_ID> Vendor-Specific(26):
Eltex Enterprise, Ltd.(35265): Incoming-RTP-local-address(4): <$inc_RTP_loc_IP> Vendor-Specific(26): Eltex
Enterprise, Ltd.(35265): Incoming-RTP-remote-address(5): <$inc_RTP_rem_IP>
341
Vendor-Specific(26): Eltex Enterprise, Ltd.(35265): Outgoing-RTP-local-address(6): <$out_RTP_loc_IP> Vendor-
Specific(26): Eltex Enterprise, Ltd.(35265): Outgoing-RTP -remote-address(7): <$out_RTP_rem_IP> Vendor-
Specific(26): Eltex Enterprise, Ltd.(35265): call-record-file=<$call_record_file_name>
Plastic bagAccess-Accept
AtByreceiving the packageAccess-Accept from the RADIUS server, the call is considered authorized. Then
an outgoing trunk is searched, and if successful, an attempt is made to establish a connection.
If the attribute was passed in the packageSession Time(27)or attributeCisco VSA(9) h323-credit-time(102), A
the corresponding setting was also set in the profileRADIUS, then the attribute value will be used to limit the
maximum call duration. After this time, the connection will be disconnected from the sideSMG.
4.1.17.5 Description of variables Table

29 - Description of variables
Variable Description and possible values
$CALL_TYPE determined based on which transmission medium the

outgoing trunk belongs to:
• "Telephony", if the outgoing trunk is PSTN (TDM);

• "VoIP" if the outgoing trunk is VoIP
$CdPN determined based on settingsSMGs:
• $CdPN = $CdPN_IN [default];

• $CdPN = $CdPN_OUT
$CdPN_IN called party number before conversion (obtained in SETUP/INVITE)
$CdPN_OUT called party number after translation (sent to the called party inSETUP/
INVITE)
$CgPN_IN caller number before conversion (obtained in SETUP/INVITE)
$CgPN_OUT caller number after conversion (sent to the called party inSETUP/INVITE)
$DISCONNECT_CAUSE Q.850 call termination reason
$DST_ID outgoing trunk name for this call
$DST_IP (string) IP address of the terminating device if the outgoing trunk is VoIP;
example: 192.168.0.1
342
$USER_IP The IP address of the device that initiated the call, if the incoming VoIP
trunk or SIP subscriber
$LOCAL_DISCONNECT_CAUSE the local reason for terminating the call; values:
• 1 – connection with the called subscriber was established (User-

Answer);
• 2 – incorrect or incomplete number format (Incomplete-
Number);
• 3 – number does not exist (Unassigned-Number);
• 4 - unsuccessful attempt to establish a connection, the reason is
not defined (Unsuccesfull-Other-Cause);
• 5 – called subscriber is busy (User-Busy);
• 6 – equipment malfunction (Out-of-Order);
• 7 – no answer from the called subscriber (No-Answer);
• 8 – outgoing trunk is unavailable (Unavailable-Trunk);
• 9 – authorization denied from RADIUS server (Access-Denied);
• 10 – no free channel for connection establishment

(Unavailable-Voice-Channel);
• 11 – RADIUS server is unavailable (RADIUS-Server-Unavailable).
$NAS_PORT (xport.type<<24) + (xport.slot<<16) + (xport.stream<<8) + (xport.cell)
$ROUTE_RETRIES current attempt number; report starts with1 (for the first try,
respectively)
$SESSION_ID session ID
$SESSION_TIME call duration time
$SMG_IP SMG IP address
$SRC_ID incoming trunk name for this call
$TIME_SETUP message arrival timeSETUP/INVITE format hh:mm:ss.uuu t www MMM

dd yyyy
$TIME_CONNECT receiving timeCONNECT/200 OK from called party to format

hh:mm:ss.uuu t www MMM dd yyyy
$TIME_DISCONNECT receiving timeDISCONNECT/BYE from one of the parties in the format

hh:mm:ss.uuu t www MMM dd yyyy; if the call is unsuccessful, then
indicates the time of the message, upon receipt of whichSMG starts call
destruction procedure (CANCEL, others)
343
$USER_NAME determined based on the settings of the incoming trunk:
• <$CgPN_IN>;
• source IP address or E1 flow number [default];
• incoming trunk name
<$inc_SIP_call_ID> field valueCall-ID of SIP messages of the incoming connection leg
<$out_SIP_call_ID> field valueCall-ID of SIP messages of the outgoing connection leg
<$inc_RTP_loc_IP> localIP address of the device to establish an RTP session

incoming connection leg
<$inc_RTP_rem_IP> remoteThe IP address of the communicating device for

establishingRTP sessions of the incoming connection leg
<$out_RTP_loc_IP> localIP address of the device to establish an RTP session

outgoing connection leg
<$out_RTP_rem_IP> remoteThe IP address of the communicating device for

establishingRTP sessions of the outgoing connection leg
<$call_record_file_name> name of the conversation recording file. Example:
call_records/2016-12-13-0000/2016-12-13_12-41-45_20000-10000.wav
4.1.17.6 Callback authorization
-The functionality is only available with a license.
The function is used to initiate a call through a requestRADIUS Change-of-Authorization (CoA) (described in
standardRFC 5176). It is used for the service of authorization of connection to public networks. callback
access. The user connects to the network and gets toweb portal where an access password is requested
and you are prompted to enter a password for authorization. After entering the number, the user receives
a call on their phone. The caller number displayed to the user, or part of it, serves as a password for
accessing the public access network, which must be entered onweb- portal.
To initiate a callthe web portal must send a CoA-Request packet to the SMG via the RADIUS protocol,
containing attributeCalled-Station-Id with the user's phone number. Example of a CoA-Request:
344
RADIUS Protocol
Code: CoA Request (43) Packet
identifier:0xa0(160) Length:33
Authenticator: ac02dd52e3435a2fa46ed7cd2f7f177d Attribute

Value Pairs
AVP:l=13t=Called-Station-Id(thirty):70123456789
type:thirty
Length:13
Called-Station-Id:70123456789
In case the number can be called,SMG selects a caller number from a given pool numbers and sends it in the
responseCoA-ACK in the Calling-Station-Id attribute. The SMG will then initiate call from the selected number
to the user's number. Regardless of the results of the call (call drop, user answer, or end of call due to no
answer timeout),SMG sends information about the call made in requestsRADIUS Accounting. When the user
answers, the call will dropped immediately. Response ExampleCoA-ACK:
RADIUS Protocol
Code: CoA-ACK (44) Packet identifier:
0xa0(160) Length:33
Authenticator: 60363e5d4f742df10316cc05b81a42f6 Attribute

Value Pairs
AVP:l=13t=Calling-Station-Id(31):73830019698
type:31
Length:13
Calling-Station-Id:73830019698
If the number specified by the user cannot be called,The SMG will respond with a CoA-NAK without any
attributes and will not initiate the call.
In case the requestCoA-Request came from a RADIUS server that is not bound to the selected profile
RADIUS or to a network interface that does not match the selected server, SMG will ignore such a
request.
345
The call is made from a virtual number. Call routing is performed on a common basis through the numbering
plan associated with the virtual number.
Callback Authorization
Virtual number parameters:

• PBX profile– PBX profile binding;
• RADIUS profile– the RADIUS profile that will be used to send Accounting requests. RADIUS CoA
requests can be received from servers associated with this profile;
• Numbering plan– binding of a numbering plan for call routing;
• Caller ID category– selection of the ANI category;
• Selection method– method for selecting numbers from those specified in the number pool:
• random- the numbers will be randomly selected;
• consistent– Numbers will be selected in order.
• Number pools– pools of numbers from which calls will be made. To organize a pool you must
specify the starting number and range of numbers in the pool. Total can be set64 pool.
346
4.1.18 Traces
4.1.18.1 PCAP traces

The menu configures parameters for analyzing network traffic and protocolsTDM networks.
Traces →PCAP traces
347
TCPdump - settings for the TCP-dump utility:
TCPdump- a utility that allows you to intercept and analyze network traffic.
• Interface– interface for capturing network traffic;

• Packet length limit (0 - no limit) –capturing size limit packets, in bytes;
• Add filter -packet filter for tcpdump utility.

Structure of filter expressions
Each filter expression includes one or more primitives consisting of one or more object identifiers and
classifiers that precede it. An object identifier can be its name or number.
Object classifiers:
1.type– indicates the type of the object specified by the identifier. As an object type values are
indicated:
host(host);
net(net);
port(port).
If the object type is not specified, the value is assumedhost.
2.dir- sets the direction in relation to the object. This classifier supports values:
src(the object is the sender); dst(the

object is the recipient); src or dst(sender
or recipient); src and dst(sender and
recipient).
If the classifierdir not set, value assumedsrc or dst.
For dummy interface capture modeany classifiers can be usedinbound Andoutbound.
3.proto– specifies the protocol to which the packets should belong. This classifier can take values:
ether,fddi1,tr2,wlan3,ip,ip6,arp,rarp,decnet,tcpAndudp.
If the primitive does not contain a protocol qualifier, the filter is assumed to satisfy all protocols
that are compatible with the object type.
In addition to objects and classifiers, primitives can contain arithmetic expressions and keywords:
• gateway(Gateway);
• broadcast(broadcast);
• less(less);
• greater(more).
348
Complex filters can contain many primitives linked together using logical operators.and,orAndnot. To
shorten the expressions that define filters, you can omit identical lists of classifiers.
Filter examples:
dst foo– selects packets in which the IPv4/v6 destination address field contains the host address foo;
src net 128.3.0.0/16– selects all Ipv4/v6 packets sent from the specified network;
ether broadcast– Ensures that all Ethernet broadcast frames are selected. ether keyword may be omitted;
ip6 multicast– selects packets with IPv6 multicast addresses.

For more detailed information about packet filtering, refer to specialized resources.
• Run -start collecting data;

• Complete -complete data collection;
• Restart -restarting the utility, start collecting data again.
In equipmentSMG-1016M has a PCAP trace removal feature (TCP-dump). If you shoot traffic from a
specific interface (for example,eth0.129), then the resulting dump will not contain outgoing flowRTP. To
capture both streams (incoming and outgoing), the withdrawal must be performed on interfaceANY for
SMG1016m and on bond1 interface for SMG2016/3016.
PCM-dump - settings for the PCM-dump utility
PCM-dump– a utility that allows you to intercept and analyze signal traffic along E1 streams. The device has
the ability to removePCM-dump both from one stream and from several, with withdrawalPCM-dump from
multiple threads at the same time trace is written to one file, in which is entered signaling messages from
several threads, while the simultaneous removalPCMdump from streams with different signaling protocols is
not possible.
• Choose– selection of E1 streams;

• Signaling– signaling protocol selected on the stream:
• OKS-7;
• Q.931-N;
• Q.931-U;
• v5.2;
• Restart -restart the utility and start collecting data again.
349
Port mirroring - traffic mirroring settings:
-Only forSMG-1016M.
Port mirroring allows you to copy the received and transmitted frames from the ports of the gateway
switch and forward them to another port.
For device ports, the following actions are possible:

• Incoming packet source ports −copy frames received from the given port (port- source);
• Outgoing packet source ports −copy frames transmitted by the given port (port- source);
• Destination port for incoming packets −destination port for copied frames received selected source
ports;
• Destination port for outgoing packets– destination port for copied frames, transmitted by
selected source ports;
Buttons:
• Apply -apply mirroring settings;

• Confirm -confirm applied mirroring settings;
• Clear -reset mirroring settings;
• Save -save mirroring settings.
-If the settings are not confirmed within one minute by pressing the button"Confirm", then they return
to their previous values.
In the blockFiles and folders in the trace directorylist of trace files available.
To download files to a local PC, you need to set the flags opposite the required file names and click the
button"Download".To remove the specified files from the directory, click the button "Delete".
350
4.1.18.2 PBX traces Basic traces tab
-Using traceIP PBX causes delays in device operation. This type debugging is recommended to be used
only in case of problems in the operation of the gateway to identify their causes.
Traces →PBX tracing
351
The following options allow you to quickly identify the causes of incorrect operation of the gateway. Turn
onPBX-PSTN– allows you to run a log of the operation and interaction of the device nodes, as well as
messaging over various protocols. Automatically starts the following level of traces:
accidents 1
challenges 99
SIP 99
SS7-ISUP 99
Q.931 99
RTP connections 99
SM-VP teams 99
RADIUS 1
IVR 1
Turn onPBX-SIP– allows you to start tracing messages and errors of the SIP protocol; Turn on
PCAP– allows you to run TCP-dump for the main network interface.
To start data collection, enable the necessary options and click the button"Run". Stopping data collection
is done with the button"Complete".After stopping data collection, an archive with all traces taken will be
automatically generated and downloaded. If all three types of logs were launched, then the following files
will be in the archive after the tracing is completed:
messages
app_log_*
gzcore_*
pbx_sip*
pbx_pstn*
*. pcap*
/etc/config/cfg*
/tmp/disk/service.yaml
/var/run/service.yaml
Advanced Traces Tab

Here you can run logs on specific protocols and device subsystems.
Run at startup– allows you to start taking traces immediately after restarting the gateway
(Automatically enabling logging after restarting the gateway).
In the blockPBX PSTNthe log of the operation and interaction of the device nodes is taken, as well as the exchange
messages over various protocols. In parametersPBX PSTN can select events and protocols, for which you need to
remove the log.
To start data collection, select the necessary protocols and subsystems in the list and click the button
"Run". The enabled option corresponds to the log level 99.
Stopping data collection is done with the button"Complete".
Also, during the data collection, you can change the parameters and restart the data collection with the
button "Restart".
In the blockPBX SIPtracing of messages and errors of the SIP protocol is removed:

• Restart -restart tracing, start collecting data again.
352
In the blockPBX-H323H.323 protocol messages and errors are traced:

• Restart -restart tracing, start collecting data again.
-After stopping data collection, buttons will appear that allow you to download trace files to local
computer.
In the blockFiles and folders in the trace directorya list of trace files is available.
To download files to a local PC, you need to set the flags opposite the required file names and click the
button"Download". To remove the specified files from the directory, click the button "Delete".
Tab "By TrunkGroup"

Traces →PBX tracing→ By TrunkGroup
This section starts the removal of logsPBX_PSTN on the selected trunk group. Levels traces work
similarly to the trace levels settingsPBX_PSTN from the General tab settings", with the exception that a
single logging level will be set for all protocols.
To start data collection, set the tracing level on the required trunk groups to a non-zero level and
press the button"Run".
Also, during tracing, you can change the parameters and restart data collection with the button "Restart".
353
Tab "By phone number"
Traces →PBX tracing→ By phone number
This section starts the removal of logsPBX_PSTN on the selected phone number. The selection is underway at
the same time as by numbersCdPN and CgPN. Trace levels work similarly to settings trace levelsPBX_PSTN
from the General Settings tab, except that for all protocols will be set to a single logging level.
To start data collection, numbers must be added to the list of numbers. Then set the trace level and
click the button"Run".
Also, during the data collection, you can change the parameters and restart the data collection with the
button "Restart".
4.1.18.3 SYSLOG settings

On the menu"SYSLOG"configuring system log settings.
SYSLOG– a protocol designed to transmit messages about events occurring in the system. The gateway
software allows you to generate data logs on the operation of system applications, the operation of
signaling protocols, accidents and transfer them toSYSLOG server.
-High debugging levels can cause device lags. It is not recommended to use
syslog unnecessarily.
-The system log should be used only in case of problems in operation. gateway to identify their causes.
In order to determine the required levels of debugging, we recommend that you contact the service
center of ELTEX Enterprise LLC.
Traces– used to save the log of the operation and interaction of the device nodes, as well as the exchange of
messages using various protocols.
In the tracing parameters, the level of tracing by events and protocols is configured. Possible levels:0 -
disabled, 1-99 - enabled. 1 is the minimum, 99 is the maximum debugging level.
354
Traces →SYSLOG
• Server IP address -address of the server to which the trace will be sent;
• Server port -port of the server to which the trace will be sent.
Displaying the history of entered commands– used to save the history of changes in the gateway settings.
• Server IP address -address of the server to which the log of entered commands will be sent;
• Server port -server port to which the log of entered commands will be sent;
• Level of detail -log verbosity level of entered commands:
• Disable logs– do not generate a log of entered commands;
• Standard– the name of the changed parameter is transmitted in messages;
• Full– the name of the changed parameter and value is transmitted in messages parameter
before and after the change.
355
Syslog Configuration– syslog configuration settings for reporting events related to access to the device.
• Enable logging -if the flag is set, the history of events related to access to the device will be saved,
if the flag is not present, logging is stopped;
• Send to server -if the flag is set, the system log will be stored on server at the specified address;
• Server IP address -address of the server for storing the system log;
• Server port -port of the server to which the system log will be sent.
4.1.19 Switch
-Only forSMG-1016M.
Menu"Switch"is for configuring switch ports.
4.1.19.1 LACP Settings

In this section, you can configure groupsLACP.
Link Aggregation Control Protocol (LACP)- a protocol for combining several physical channels into one
logical.
Switch → SetupLACP
To create, edit, delete, apply group changesLACP buttons are used: "Add", "Edit", "Remove"And"Apply".
356
Switch → SetupLACP→ Object
• Group name– LACP group name;

• enable-when the flag is set, it is allowed to use the LACP protocol;
• mode– LACP protocol operation mode:
• active-backup– one interface is in active mode, the others are in standby mode. If the active
interface goes out of service, control is transferred to one of the waiting ones. Does not
require support for this functionality from the switch;
• balance-xor– packet transmission is distributed between aggregated interfaces over formula: ((
Source MAC address) XOR (Destination MAC address)) % number of interfaces. The same
interface works with a specific recipient. This mode allows you to balance the load and increase
fault tolerance;
• 802.3ad– dynamic port aggregation. In this mode, you can get a significant increase in
throughput for both incoming and outgoing traffic, using all aggregated interfaces. Requires
support for this functionality from the switch, and in some cases, additional configuration of
the switch.
• Primary– setting up the host interface;
• update– interface change period when the leading interface is unavailable;
• Miimon– MII check period, frequency in milliseconds;
• LACP rate– transmission interval of control packets of the LACPDU protocol:
• fast– transmission interval 1 second;
• slow– transmission interval 30 seconds.
• Combine interfaces in PortChannel– list of ports added to the LACP group.
357
4.1.19.2 Configuring Switch Ports The switch can

operate in four modes:
1.Without using VLAN settings– to use the mode on all ports flags"Enable VLAN"should not be set,
value"IEEE Mode"All ports must have set to "Fallback", the interoperability of ports for data
transmission is necessary define flags "output". Routing table"802.1q"in the bookmark "802.1q"
should not contain records.
2.Port based VLAN– to use the value mode"IEEE Mode"All ports must have set to "Fallback", the
interoperability of ports for data transmission is necessary define flags "output". To work with VLAN,
you must use the settings"Enable VLAN","Default VLAN ID", "Egress" and "Override".Routing table
"802.1q"in the bookmark "802. 1q"should not contain entries.
3.802.1q– to use the value mode"IEEE Mode"All ports must have installed in"Check»orSecure.To work
with VLAN settings are used -"Enable VLAN", "Default VLAN ID", "Override".It also uses the routing
rules described in routing table"802.1q"bookmarks «802.1q.
4.802.1q + Port based VLAN.802.1q mode can be used in conjunction with Port based VLAN. IN in this
case the value"IEEE Modeon all ports must be set to "Fallback", the mutual availability of ports for
data transfer must be determined by the flags "output". For work withVLAN settings must be used
"Enable VLAN", "Default VLAN ID", "Egress and Override".It also uses the routing rules described in
the routing table "802.1q"bookmarks «802.1q.
Switch → Configuring Switch Ports
358
-In the factory configuration, the switch ports are inaccessible to each other.
The device switch has3 (for SMG-1016M) or 4 (for SMG-2016 and SMG-3016) electric portEthernet, 2
optical ports and one port for communication with the processor:
• GE port -electrical Ethernet ports of the device;
• SFP port -optical Ethernet ports of the device;
• CPU-an internal port connected to the device's CPU.
Switch settings
• Use VLAN– when the flag is set, use the Default VLAN ID, Override settings AndEgress on the given
port;
• Default VLAN ID– when an untagged packet arrives at the port, it is considered that it has this VID;
when a tagged packet arrives, it is considered that the packet has the VID specified in its tagVLANs
• vid override– when the flag is set, it is considered that any incoming packet has a VID, specified in line
defaultVLANID.Valid for both untagged and tagged packages;
• Egress:
• unmodified– packets are transmitted by this port without changes (i.e. in the same form in which
received on another port of the switch);
• untagged– packets are always transmitted by this port without a VLAN tag;
• tagged-packets are always transmitted by this port with a VLAN tag;
• double tag -packets are transmitted on this port with two VLAN tags - if the received packet was
tagged and with one tagVLAN - if the received packet was untagged.
• IEEE mode– sets the security modes for processing received tagged frames:
• fallback-the frame is received on the incoming port, regardless of whether its 802.1q tag is present
on the routing table "802.1q":
• If the 802.1q tag is not contained in the "802.1q" routing table, then the frame
transmitted to the outgoing port, provided that it is allowed in the "output" in
incoming port settings;
• If the 802.1q tag is in the "802.1q" routing table, then the frame sent to the
outgoing port, provided that the outgoing port is a memberVLAN in the
"802.1q" table and allowed in the "output" section in the settings incoming port.
• check– a frame is received on an incoming port if its 802.1q tag is contained in the table routing "
802.1q" (the incoming port does not have to be a member of the VLAN in the "802.1q" table):
• The frame is transmitted to the outgoing port if the outgoing port is a member of the VLAN
in the "802.1q" table and is allowed in the "output" section of the incoming settings. port.
• secure– a frame is received on an incoming port if its 802.1q tag is contained in the table
routing "802.1q" and the incoming port is a member of the VLAN in the "802.1q" table:
• The frame is transmitted to the outgoing port if the outgoing port is a member of the VLAN
in the "802.1q" table and is allowed in the "output" section of the incoming settings. port.
• Output– mutual availability of ports for data transfer. Sending permissions are set packets received by
this port to ports marked with a flag;
• LACP trunk– selection of the LACP group to which the port will belong;
• Port MAC– change the MAC address of the port. The option is available for editing when selecting the
LACP group on the port. Ports in the same LACP group must have different MAC addresses;
• Backup port– selection of the port to which the traffic will be switched in case of emergency situation
(for example, a line break). This setting is required to ensure redundancydual homing;
359
-The current version of the software only supportsglobal dual homing.
• Return to master port– when the flag is set, the transition to the main port after its restoration;
• Port operation mode– selection of the port operation mode (auto, 10/100 Mbps Half, 10/100 Mbps
Full, 1 Gbps). Mode setting is only possible for electrical Ethernet ports(GE port 0, GE port1, GE port 2).
-If the settings are not confirmed within one minute by pressing the button "Confirm",
then they return to their previous values.
To apply the settings, click the button."Apply", to confirm the applied settings - button"Confirm".
With the button "Default» you can set default parameters (values, default settings are shown in
the figure).
To save the settings to a configuration file without applying, click the button "Save".
4.1.19.3 802.1q
In the submenu"802.1q"packet routing rules are set when the switch operates in mode802.1q.
The gateway switch has3 electrical Ethernet ports, two optical and one port for interaction
with the processor (only forSMG-1016M):
• GE port 0, port 1, port 2– electrical Ethernet ports of the device;
• SFP port 0, SFP port 1 -optical Ethernet ports of the device;
• CPU– an internal port connected to the central processing unit of the device.
Switch →802.1q
360
Adding an Entry to the Packet Routing Table
• VID– in the field, enter the identifier of the VLAN group for which the rule is being created routing,
and for each port, assign the actions to be performed by it when transmitting a packet that has the
specifiedVID:
• unmodified– packets are transmitted by this port without changes (i.e. in the same form in which
were accepted);
• untagged– packets are always transmitted by this port without a VLAN tag;
• tagged– packets are always transmitted by this port with a VLAN tag;
• not member– packets with the specified VID are not transmitted on this port, i.e. port is not
member of this groupVLAN.
• override– if the flag is set, rewrite the 802.1р priority for the given VLAN, otherwise – leave the
priority unchanged;
• priority– 802.1p priority assigned to packets in this VLAN if the flag is setoverride.
Then you need to press the button"Add".To apply the settings, you must click the button."Apply"then
confirm the settings with the button"Confirm".
-If the settings are not confirmed within one minute by pressing the button"Confirm", then they return
to their previous values.
Save settings toFlash memory device without application is possible with a button "Save".
Removing an Entry from the Packet Routing Table

To delete records, set the flags opposite the rows to be deleted and click the button "Delete selected".
361
4.1.19.4 QoS and bandwidth control

In chapter"QoS and bandwidth control"quality assurance functions are configured service (quality of
service).
Switch →QoS and bandwidth control
• VLAN priority (default)– 802.1p priority assigned to untagged packets received given port. If the
package already has priority802.1rorIP diffserv, then this parameter is not used (default vlan priority
will not apply to packets containing an IP header, in when using one of the modesQOS:DSCP only,
DSCP preferred, 802.1p preferred);
• QoS Mode -QoS usage mode:
• DSCP only– queuing packets based on IP diffserv priority only;
• 802.1p only– queuing packets based on 802.1p priority only;
362
• DSCP, 802.1p– distribute packets into queues based on IP diffserv priorities and
802.1p, while in the presence of both priorities in the packet, queuing carried out on the
basisIP diffserv;
• 802.1p, DSCP– distribute packets into queues based on IP diffserv priorities and
802.1p, while in the presence of both priorities in the packet, queuing carried out on the
basis802.1r.
• Reprioritize 802.1p– 802.1p priority reassignment for tagged packages. Each priority accepted in the
packetVLAN, you can thus assign a new meaning;
• Incoming Packet Restriction Mode– mode of restricting traffic arriving at the port:
• Switched off- no restriction;
• All packages– all traffic is limited;
• BroadMultFlood– limited multicast (multicast), broadcast (broadcast) and avalanche
unicast (flooded unicast) traffic;
• BroadMult– limited to multicast and broadcast (broadcast) traffic;
• Broad-only broadcast traffic is limited.

• Rate limit for incoming packets in queue 0– bandwidth limitation traffic arriving on the port for queue
zero. Valid values range from70 to 250,000 kilobits per second;
• Rate limit for incoming packets in queue 1 -bandwidth limitation traffic arriving on the port for the first
queue. The bandwidth can either be doubled (prev prio *2) relative to the zero queue, or leave the
same (same as prev prio);
• Rate limit for incoming packets in queue 2– bandwidth limitation traffic arriving on the port for the
second queue. The bandwidth can either be doubled (prev prio *2) relative to the first queue, or leave
the same (same as prev prio);
• Rate limit for incoming packets in queue 3– bandwidth limitation traffic entering the port for the third
queue. The bandwidth can either be doubled (prev prio *2) relative to the second queue, or leave the
same (same as prev prio);
• Enable outgoing packet restriction −if the flag is set, restriction is allowed bandwidth for traffic
outgoing from the port;
• Rate limit for outgoing packets– bandwidth limitation for outgoing traffic from the port. Valid values
range from70 to 250,000 kbps.
• Apply -apply the settings;
• Confirm -confirm the changed settings;
then they return to their previous values.
• Default -set default settings;

• Save -save the settings to the device's Flash memory without using it.
363
4.1.19.5 Prioritization
Switch → Queuing Priority
• 802.1p prioritization by queue- allows you to distribute packets into queues depending on priority
802.1r.
• 802.1r– 802.1р priority value;
• Queue– outgoing queue number.
• Prioritization of IPdiffserv queues- allows you to distribute packages by queues based on
priorityIP diffserv:
• diffserv– IP diffserv priority value;
• Queue– outgoing queue number.
• Apply -apply the settings;
• Confirm -confirm the changed settings;
then they return to the previous values.
• Default -set default settings;

• Save -save the settings to the device's Flash memory without using it.
-Queue3 is the highest priority, queue 0 is the least priority. Weighted distribution of packets
across outgoing queues3/2/1/0 is the following: 8/4/2/1.
364
4.1.20 Working with objects and the "Objects" menu
In addition to using the icons for creating, editing and deleting objects in the corresponding tabs, it
is possible to perform actions on the specified object using the corresponding items in the "Objects"
menu.
Objects
4.1.21 Saving the configuration and the "Service" menu

Service
To cancel all changes, select the menu"Service" - "Revert all changes".

When making changes to the configuration without savingFLASH followed by "cancel all changes" -
registrationSIP subscribers flies.
To save the database of registeredSIP subscribers need to select the menu"Service" - "Save
subscriber base".
To write the configuration to the non-volatile memory of the device, select the menu"Service"
– "Save configuration in FLASH".
To restart the device software, select the menu"Service" - "Restart software".
To completely restart the device, select the menu"Service" - "Restart device".
To force resynchronization of time fromNTP server must be selected from the menu"Service"
– "Restart NTP client".
To read/write the main configuration file of the device, select the menu "Service" - "Manage
Configuration Files".
To manually set the local date and time on the device, select the menu"Service" - "Set date and time", see
sectionSetting the date and time.
To update the software viaweb configurator, you must select the menu "Service” – “Software update”, see
sectionSoftware update viaweb configurator.
To update the addition of licenses, select the menu "Service” – “License Upgrade”, see sectionLicenses.
365
4.1.22 Setting the date and time

Tools → Set date and time
In the corresponding fields it is possible to set the system time in the HH:MM format and the date in the
DD.month.YYYY format.
To save the settings, use the "Apply".

At the push of a button"Synchronize"the system time of the device is synchronized with the current time on
the local computer.
4.1.23 Software update via web configurator

To update the device software, use the menu"Service" - "Software update". A form for uploading
software files to the device will open:
Service → Software update
• Firmware update– updates the software of the control program and/or the Linux kernel.
To update the software, in the field "Firmware file» using the button «Review» name file to update and click
the "Download". After the operation is completed, restart device via menu"Service" - "Restart device".
366
4.1.24 Licenses
LicensesSMG-1016M:
• SMG1-PBX-2000– registration of up to 2000 SIP subscribers;
• SMG1 SORM– activation of the SORM functionality;
• SMG1-VAS-500+IVR– activation of VAS functionality for 500 subscribers and IVR;
• SMG1-CORP-500+IVR– activation of the registration functionality for up to 500 SIP subscribers, 500 VAS for SIP
subscribers and IVR;
• SMG1-H323– activation of the H.323 protocol functionality;
• SMG1-RCM– activation of the Radius Call Management functionality;
• SMG1-REC– activation of the call recording functionality;
• SMG1-SRM-1– activation of the functionality of the SORM intermediary to provide the functions of the SORM
ECSS-10 Softswich;
• SMG1-V5.2-LE– activation of the V5.2 LE protocol functionality for connecting subscriber extensions
protocolV5.2AN;
• SMG1-VNI-40– expansion of the number of network interfaces up to 40;
• SMG1-VNS-activation of the functionality of the voice notification system;
• SMG1-AUTH-CALL – activation of the "Authorization by callback" functionality;
• SMG1-SORM-374N1– activation of the functionality of the telemetry channel on the agro-industrial complex manufactured by CJSC
"Norsi-Trans" to implement the requirement of Federal Law No.374 ("Yarovaya Package");
• SMG1-SORM-374P1– activation of the telemetry channel functionality on the RTK-NT storage system;
• SMG1-SORM-374T1– activation of the telemetry channel functionality on the TechArgos HSC for conducting an operational-
search activity on the collection and storage of votes;
• SMG1-SORM-374V1– activation of the telemetry channel functionality on the HSC of VAS Experts to conduct an operational-
• SMG1-SORM-374M1– activation of the functionality of the telemetry channel on the APK of MFI Soft to conduct an
operational-search activity on the collection and storage of votes.
LicensesSMG-2016
• SMG2-PBX-3000– registration of up to 3000 SIP subscribers;
• SMG2 SORM– activation of the SORM functionality;
• SMG2-VAS-1000+IVR– activation of VAS functionality for 1000 subscribers and IVR;
• SMG2-CORP-1000+IVR– activation of the registration functionality for up to 1000 SIP subscribers, 1000 VAS
ForSIP subscribers andIVR.SMG2-H323– activation of the H.323 protocol functionality;
• SMG2-RCM– activation of the Radius Call Management functionality;
• SMG2-REC– activation of the call recording functionality;
• SMG2-SRM-2– activation of the functionality of the SORM intermediary to provide the functions of the SORM
ECSS-10 Softswich;
• SMG2-V5.2-LE– activation of the V5.2 LE protocol functionality for connecting subscriber extensions
protocolV5.2AN;
• SMG2-VNI-40– expansion of the number of network interfaces up to 40;
• SMG2 RESERVE– activation of redundancy over IP in master-slave mode;
• SMG2-RESERVE-SLAVE-activation of redundancy over IP in master-slave mode (Total time operation
of the device without a gateway with a licenseSMG2-RESERVE is 200 hours);
• SMG2-RESERVE-E1-E1 redundancy activation in master-slave mode (requires availability of a
licenseSMG2-RESERVE (SMG2-RESERVE-SLAVE));
367
LicensesSMG-3016
• SMG3-PBX-3000 – registration of up to 3000 SIP subscribers;
• SMG3-SORM – activation of the SORM functionality;
• SMG3-VAS-1000+IVR – activation of VAS functionality for 1000 subscribers and IVR;
• SMG3-CORP-1000+IVR – activation of the registration functionality for up to 500 SIP subscribers, 500 VAS for SIP
subscribers and IVR.SMG2-H323 – activation of the H.323 protocol functionality;
• SMG3-RCM – activation of Radius Call Management functionality;
• SMG3-REC – activation of call recording functionality;
• SMG3-SRM-2 -activation of the functionality of the SORM intermediary to provide the functions of the SORM
ECSS-10 Softswich;
• SMG3-V5.2-LE -activation of the V5.2 LE protocol functionality for connecting subscriber extensions
protocolV5.2AN;
• SMG3-VNI-40 –expansion of the number of network interfaces up to 40;
• SMG3 RESERVE-activation of redundancy over IP in master-slave mode;
• SMG3-RESERVE-SLAVE-activation of redundancy over IP in master-slave mode (Total time operation
of the device without a gateway with a licenseSMG2-RESERVE is 200 hours);
• SMG3-RESERVE-E1-E1 redundancy activation in master-slave mode (requires availability of a
licenseSMG2-RESERVE (SMG2-RESERVE-SLAVE));
To update / add licenses, you need to obtain a license file by contacting the commercial department of ELTEX
Enterprise LLC ateltex@eltex-co.ru or call +7(383) 274-48-48, indicating the serial number and MAC address of
the device (see sectionView factory settings and system information).
- 1Not supported in the current software version. Software version required for integration with SORM
FZ No.374 of your vendor, check with the service center of ELTEX Enterprise LLC.
368
Next on the menu"Service"select option"License Upgrade".
Service
With button"Choose File"specify the path to the license file received from the manufacturer and update by
clicking"Update".
Confirmation is required to update the license file.
Service → License update
After the operation is completed, you will be prompted to restart the device, or this must be done through
the menu"Service" - "Restart device".
4.1.25 Help menu

Help
The menu provides information about the current software version, factory settings, and other system
information.
369
4.1.26 Control menu

Control
The "Management" section is intended for working with access passwords to the device viaweb-
configurator,telnet, ssh and setting the rights of users who have access to the device.
Set administrator passwordweb interface:
Management → Set password
To change the administrator password, you must enter a new password in the field"Enter password", in field
"Confirm new password"repeat the new password. Push button"Ask"to apply a password.
To save the configuration, use the menu"Service" - "Save configuration toFlash.
Web interface users:

Management → Web Interface Users
This block is intended for setting access restriction toweb configurator at the level users. There is
always an administrator in the system who can add and remove users, as well as assign access
levels.
Buttons are used to create, edit and delete a user:
– “Add user”;
– “Edit user parameters”;
– “Delete user”.
The program does not allow changing the administrator's access rights and removing him from the
list of users, which ensures guaranteed entry into the system administrator program.
370
User creation:
Management → Web Interface Users → Object
To create a user, fill in the following fields:

• Username– username for entering the web configurator;
• enter password– password for access to the web-configurator;
• Confirm the password– confirm the password for accessing the web configurator.
User rights:
• Device/software restart– it is possible to restart the device and software;
• TDM management (E1 streams)– it is possible to configure E1 streams;
• VoIP management (SIP interfaces, H323 interfaces)- given the opportunity interface settings
SIP and H323;
• Subscriber management– it is possible to configure SMG subscribers;
• Manage IP Settings, Switch RADIUS- Possibility of customization switch parameters,TCP/IP,
network services and security;
• Configuration management- Possibility to upload/download files configuration;
• Software management– it is possible to update the software and license of the device;
• Listening to recorded conversations- Possibility of listening recorded conversations of a
certain category without the possibility of downloading;
• Export recorded conversations -provides the ability to download recorded conversations (listening to
conversation recordings without the possibility of downloading);
• Call recording management- provides access to setting up call recording and access to them;
• Monitoring– access to monitoring sections is provided;

• SGO operator- access to sections to sections of the CGO "List of numbers" and "Reports", as well as
to the Monitoring section "Problems of the SSS".
• CSO Administrator– access to the sections of the CGS "Voice messages", "Tasks alerts", "Notification
records", as well as to the Monitoring section "CSS Tasks".
371
To grant full access to the SGS section, you must use the rights of SGS Operator and SGS Administrator
jointly.
To save the configuration, press the button"Apply"and then use the menu "Service" - "Save configuration
toFlash.
Set an administrator password forTelnet and SSH:
Management → Set administrator password fortelnet and ssh
This block is designed to change the access password throughTelnet, SSH and console.
To change the password, you must enter a new password in the field"Enter password", in field"Confirm
password"repeat the new password. Push button"Ask"to apply a password.
List of active sessions
This block displays a list of users who are currently connected to the web interfaceSMG. It is possible for
the administrator to forcibly end the session of others users, to do this, click the button"Forced Exit"in
the line with the user whose session you want to end.
4.1.27 View factory settings and system information

Help
Use the menu to view"Help" - "System Information". Factory parameters are also indicated in the
nameplate (sticker) on the bottom of the product case.
Detailed information about the system (factory settings, versionSIP adapter, current date and time, time in
operation, network settings, temperature inside the case) is available by clicking on the link "Home"on the
control panel.
4.1.28 Exiting the configurator

By clicking on the link"Exit» exits the configurator.
372
4.2 CLI Command Reference (SMG)
4.2.1 Command line in debug mode, list of supported commands and switches INSMG
provides several ways to connect to the command line interface:
• Terminal (com port)– designed to configure the device through command line interfaceCLI
and software change;
• Telnet port 23– terminal duplicate (com-port);
• ssh port 22– duplicate terminal (com-port).
Command system for working with the gatewaySMG in debug mode
To switch to debug mode, you need to connect to the command line interfaceCLI and enter command
tracemode.
Table30 - Debug mode commands
Team Description
help Viewing the list of available commands
quit Exit debug mode
logout Exit debug mode
exit Exit debug mode
history Displaying a list of previously entered commands
redact [on/off] Turn on/offRADIUS
radshow Viewing a list of requests forRADIUS server
resolve Checking domain name resolution.
Parameter: domain name
rstat Viewing statistics of work by protocolRADIUS
q931timers Viewing Timer ValuesQ.931
mspping [on/off] Enable/disable polling of the signal processor,idx – signal processor number
<idx> – 0..5
stream [stream] Viewing the Status of E Threads1, or state of a particular stream, stream – stream number 0..15)
373
Team Description
e1stat <stream> View flow counters E1
alarm View information about the alarm log
sync Viewing information about synchronization sources
syncfreq Viewing information about clock frequencies
setsync Forced change of synchronization source.
Parameter – <stream number>
checkmod Checking the operation of the number modifier for a specific number.
Parameters: <modifier table> <verified telephone number>
frmtrace Enabling low-level tracing on E signal streams1.
Parameters: <level> <stream number> <use>
• level: l1, l2, l3

• use: 1 - on, 0 - off
cic <linkset> View the status of channels in a line group, <linkset> – SS-7 line group number
checknum Checking the number according to the numbering plan
cfg read Applying the current configuration, this command resets and reinitializes E threads1
callref Displaying information about activeSIP calls
rtpdebug <level> Enable debuggingSwitch RTP, <level> – debug level
- Using this command may cause the gateway to freeze when running under load.
mspcports Status ViewRTP ports
mspcshow Viewing connection statistics on signal processors

<device>
sipstat View statisticsSIP calls
374
Team Description
sipclrstat Reset countersSIP statistics
sipreg View information about registration of subscribers or trunks.
Parameters: <user>, <trunk<self|user>>
sipreg user Viewing the list of registered subscribers (similar to the commandreginfo)
sipreg trunk self Viewing Trunk Registration InformationSIP interfaces on the upstream server
sipreg trunk user Viewing Subscriber Registration InformationSIP interfaces on the upstream server
route Viewing information about network routes handled by telephony
showcall View information about currently active calls
license Viewing information about current active licenses
mspreglog Enabling Signal Processor Command Tracing
mspunreglog Turn off signal processor instruction tracing
talk View call statistics
trunk cps Information on the current number of calls per second through the trunk group. Options: <idx> –
trunk group number
trunk stat Information on current calls through the trunk group.
Parameters: <idx> – trunk group number
sys View system information, software version
hwreboot Device reboot
trace Tracing functions
reginfo Entering information about registered subscribers
regcon The command is required to return to normal mode after using the command unregcon
(unless the application crashed)
375
Team Description
unregcon The command is used in extreme cases to determine the exact location of an application
crash.
stop Software restart
4.2.1.1 Trace commands available through the debug port
4.2.1.1.1 Global enable debugging

Command syntax:
trace start
4.2.1.1.2 Turn off debugging globally

Command syntax:
trace stop
4.2.1.1.3 Enable/disable debugging for specific arguments Command syntax:
trace<POINT>on/off<IDX> <LEVEL>
Options:
<POINT> argument
<IDX> numeric parameter
<LEVEL> debug level

Table31 - Valid arguments (<POINT>)
Meaning Command decoding Meaning

<POINT> <IDX>
hwpkt Tracing the contents of the packets of the first level of the exchange of the main 0..15
application with the E stream driver1
stream Flow trace E1 0..15
port Application tracing Not

used
isup Subsystem TracingISUP protocol OKS-7 Not

used
mtp3 Level operation traceMTP3 of the SS-7 protocol over the E1 stream 0..15
376
sip Protocol TracingSIP/-T/-I Not

used
pril3 Tracing the work of the third level of the protocolDSS1 on E1 stream 0..15
sw Work traceTDM switch Not

used
mspc tracingIP connections Not

used
mspd Signal Processor Tracing 0..7
net Data network tracing2nd level Not

used
sync Tracing the operation of synchronization sources Not

used
erl1 Low-level tracing of the message passing system between the Not
application andSIP module used
erl3 High-level tracing of the message passing system between the Not
application andSIP module used
snmp Work traceSNMP protocol Not

used
np Tracing the work of the numbering plan (routing) Not

used
mod Tracing the work of modifiers Not

used
alarm Gateway Crash Tracing Not

used
radius Work traceRADIUS protocol Not

used
4.2.2 Configuring the SMG via Telnet, SSH or RS-232

In order to configure the device, you need to connect to it using the protocolTelnet, SSH or cable via RS-232
connector (using CLI for access). With factory installations address:192.168.1.2, mask255.255.255.0.
Configuration changes made viaCLI (Command Line Interface) or web configurator, are applied
immediately after the commission.
377
To save the configuration to the non-volatile memory of the device, execute the commandcopy
running_to_startup.
On first start, username:admin, password:rootpasswd. Below is a
complete list of commands in alphabetical order.
4.2.2.1 List of CLI commands

Table32 - CLI Commands
Team Parameter Meaning Action
? Show list of available commands
alarm Show information about current alarms

global
alarm list Clear alarm log

clear
alarm list Show a log of emergency events indicating the type and status
show of the accident, the time of occurrence and localization
parameters.
config Switching to the device parameter configuration

mode
CPU load Show download statisticsCPU last minute

statistical
date Set the local date and time on the device.
<DAY> 1-31
<MONTH> 1-12
<YEAR> 2011-2037
<HOURS> 00-23
<MINS> 00-59
dhcp start RunDHCP server
dhcp stop StopDHCP server
exit End this sessionCLI
firmware Software update without automatic reboot of

update the gateway
tftp
378
<FILE> software file name FILE - file name with software
<SERVERIP> IP address in SERVERIP format – TFTP server IP address

AAA.BBB.CCC.DDD
firmware Software update without automatic reboot of

update ftp the gateway
<SERVERIP> IP address in SERVERIP format – FTP server IP address

AAA.BBB.CCC.DDD
firmware <FILE> software file name Software update without automatic reboot of
update the gateway
usb
FILE - file name with software
firmware Software update with automatic gateway reboot

update_an
d_reboot
tftp
<SERVERIP> IP address in SERVERIP format – TFTP server IP address

AAA.BBB.CCC.DDD

update_an
d_reboot
ftp
<SERVERIP> IP address in SERVERIP format – FTP server IP address

AAA.BBB.CCC.DDD

update_an
d_reboot
usb
history Viewing history of entered commands
license Check for licenses on the device

check
(License installed - the license is installed;
<LICENSE> SMG-PBX-2000
License NOT installed- license not installed)
SMG SORM/
SIP-PBX-Demo/
SMG-PBX-3000/
379
SMG-H323/
SMG-RCM/
SMG-VAS-500/
SMG-DEMO
license Download the license file from the specified address

download
<FILE> file name

licenses
<SERVERIP> Server IP address in

format
AAA.BBB.CCC.DDD
license Upgrade license

update
license no/yes Remove all installed licenses

reset
managem Switching to flow control mode OKS-7

ent
mirroring Switching to mirror control mode
number Checking the possibility of routing by this number. The

check check is carried out by the masks of the calling and called
subscribers, as well as by the database of configuredSIP,
PRI and V5.2 subscribers. IN As a result of the check, data
on the possibility of routing by this number in the given
numbering plan is displayed:
• calling-table– table routing callers;
• called-table– table routing called

subscribers;
• NOT found in– routing by this table impossible;
• found in– routing by this table possible;
SIP/PRI/V5.2 subscriber ID[11] index [0] — SIP/PRI/V5.2 subscriber

[subscriber ID] [record number of this subscriber in the database]
prefix index [6]– Routing by prefix [number prefix in

list]
<NUMPLAN> 0-15/0-255
380
<NUMBER> string not long

more31 characters
<COMPLETE> yes/no
mirroring Configuring Port Mirroringethernet
password Change password for access viaCLI
pcmdump Collect packets from the specified stream E1
<STREAM> 0-15 STREAM - stream number to capture;
<FILE> line FILE - file to write
quit End this sessionCLI
reboot <YES_NO> yes/no Reboot device
sh Jump fromCLI in Linux Shell
sntp retry SendingSNTP request to the server for synchronization

time
statistical Switching to statistics view mode
tcpdump Capture packages fromEthernet devices
<DEVICE> eth0/eth1/local DEVICE - monitoring interface
<FILE> line FILE - file for writing packages
<SNAPLEN> 0-65535 SNAPLEN - the number of bytes captured from each packet (0 -
the packet is captured completely)
tftp put Get file byTFTP. The team is for downloading traces
captured by commandstcpdump and pcmdump
<LOCAL_FILE> line
<REMOTE_FILE> line
<SERVERIP> IP address in the format

AAA.BBB.CCC.DDD
tracemode Switching to trace removal mode
381
4.2.2.2 Changing the password for accessing the device via CLI
Since you can connect to the gateway remotely viaTelnet, then in order to avoid unauthorized access it is
recommended to change the password for the useradmin.
For this you need:
1. Connect to the gateway via CLI, log in using login/password, enter the commandpasswordAnd press
a key<Enter>.
2. Enter a new password:
New password:
3. Repeat the entered password:
Change password:
Password changed (Passwordforadmin changed by root)
4. Save configuration to Flash: switch to configuration mode by entering the commandconfig, enter
commandcopy running_to_startupand press the key<Enter>.
4.2.2.3 "Statistics" mode

In this mode, you can view statistical data in accordance with the recommendation tables
Q.752 ITU-T.
4.2.2.3.1 Entering statistics view mode

Command syntax:
statistical
4.2.2.3.2 Switching to the MTP signal traffic volume view mode (SS-7) Command
syntax:
mtp
Execution result:
Change to MTP statistic mode SMG-[STAT]-[MTP]>
Parameters used in commands for viewing traffic statisticsMTP
<LINK> flow number E1
<LINKSET> line group number OKS-7
<TIME1> period of time for which statistics are displayed (hours)
<TIME2> time period for which statistics are displayed (minutes)
4.2.2.3.2.1 Viewing the overall status of MTP traffic

Command syntax:
signaling link allstat<LINK> <TIME1> <TIME2>
382
Example:
SMG-[STAT]-[MTP]> signaling link allstat 8 12 0

Decryption:
Displays statistics for all tables for8th stream E1 for 12 hours 00 minutes.
4.2.2.3.2.2 View signaling traffic (MTP message accounting)

RecommendationQ.752 ITU-T Table 15 Command syntax:
message accounting<LINK> <TIME1> <TIME2>
Example:
SMG-[STAT]-[MTP]> message accounting 8 12 0

Execution result:
+---------------------------------------------------+|
SS7 MTP message accounting. Link 08 |
+---------------+-----------------+------------------+|
Period:00:00:00-00:00:00( 0sec) |
+--------------------------------+------------------+|
| messages | Octets |
+---------------+-----------------+------------------+|
Received | 0 | 0 |
+---------------+-----------------+------------------+|
Transmitted | 0 | 0 |
+---------------+-----------------+------------------+
Decryption:
The amount of signal traffic is displayedMTP for the 8th E1 stream for 12 hours 00 minutes.
4.2.2.3.2.3 Viewing fault and signaling link performance (MTP) counters

signaling link faults and performance)
RecommendationQ.752 ITU-T Table 1
Command syntax:
signaling link faults_and_performance<LINK> <TIME1> <TIME2>
Example:
SMG-[STAT]-[MTP]> signaling link faults_and_performance 8 12 0
383
Execution result:
+---------------------------------------------------+|
MTP SL faults and performance. Link08 |
+---------------------------------------------------+|
Period:00:00:00-00:00:00( 0sec) |
+--------------------------------+------------------+|
Duration the in-service state | 0sec |
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - + | SL
failure events all reasons | 0 |
+--------------------------------+------------------+|
Number of SU received in error | 0 |
+--------------------------------+------------------+
Decryption:
Fault and performance counters for the signaling link are displayed for8th stream E1 for 12 hours00
minutes.
4.2.2.3.2.4 View MTP signaling link availability time RecommendationQ.752 ITU-T Table 2 Command
syntax:
signaling link availability<LINK> <TIME1> <TIME2>
Example:
SMG-[STAT]-[MTP]> signaling link availability 8 12 0

Execution result:
+---------------------------------------------------+|
MTP SL availability. Link08 |
+---------------------------------------------------+|
Period:00:00:00-00:00:00( 0sec) |
+--------------------------------+------------------+|
Duration of SL unavailability | 0sec |
+--------------------------------+------------------+
Decryption:
The duration of the signaling link unavailability for any reason is displayed for8th stream E1 for 12 hours00
minutes
4.2.2.3.2.5 Viewing MTP signaling link utilization metrics RecommendationQ.752 ITU-T Table 3
Command syntax:
signaling link utilization<LINK> <TIME1> <TIME2>
Example:
SMG-[STAT]-[MTP]> signaling link utilization 8 12 0
384
Execution result:
+---------------------------------------------------+|
MTPSL utilization. Link08 |
+---------------------------------------------------+|
Period:00:00:00-00:00:00( 0sec) |
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - + | SIF
and SIO octets transmitted | 0 |
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - + | SIF
and SIO octets received | 0 |
+--------------------------------+------------------+|
MSUs discarded due congestion | 0 |
+--------------------------------+------------------+
Decryption:
Indicators of signaling link usage are displayed for8th stream E1 for 12 hours 00 minutes
4.2.2.3.2.6 Viewing Link Group Availability Metrics (MTP signaling link set and route set
availability)
RecommendationQ.752 ITU-T Table 4
Command syntax:
signaling link availability<LINKSET> <TIME1> <TIME2>
Example:
SMG-[STAT]-[MTP]> signaling link availability 8 12 0

Execution result:
+---------------------------------------------------+|
MTPSL utilization. Link08 |
+---------------------------------------------------+|
Period:00:00:00-00:00:00( 0sec) |
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - + | SIF
and SIO octets transmitted | 0 |
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - + | SIF
and SIO octets received | 0 |
+--------------------------------+------------------+|
MSUs discarded due congestion | 0 |
+--------------------------------+------------------+
Decryption:
Displays indicators of the availability of a group of lines (linkset) and signaling routes for8th linkset
for12 hours 00 minutes
4.2.2.3.2.7 View MTP signaling point status RecommendationQ.752 ITU-T Table 5

Command syntax:
signaling point status<LINK> <TIME1> <TIME2>
385
Example:
SMG-[STAT]-[MTP]> signaling point status 8 12 0

Execution result:
+---------------------------------------------------+|
MTP signaling point status. Link08 |
+---------------------------------------------------+|
Period:00:00:00-00:00:00( 0sec) |
+--------------------------------+------------------+|
Adjacent SP inaccessible | 0 |
+--------------------------------+------------------+|
Duration of SP inaccessible | 0sec |
+--------------------------------+------------------+|
MSUs discarded due error | 0 |
+--------------------------------+------------------+
Decryption:
Displays the status indicators of the signaling point for8th stream E1 for 12 hours 00 minutes
4.2.2.3.3 Switching to the packet traffic viewing mode

Command syntax:
packets
Execution result:
SMG-[STAT]-[PACKETS]>
4.2.2.3.3.1 Viewing Packet Quality of Service statistics Command syntax:
show<TIME1> <TIME2>
Options:
<TIME1> the period of time for which statistics are displayed (hours);
<TIME2> the period of time for which statistics are displayed (minutes);
Example:
SMG-[STAT]-[PACKETS]> show 12 0
386
Execution result:
+---------------------------------------------------+|
Packet statistics |
+---------------------------------------------------+|
Period:12:00:17-13:22:32(4935sec) |
+------------------------------+---------------------+|
Packets received | 0 |
+------------------------------+---------------------+|
packets transmitted | 0 |
+------------------------------+---------------------+|
Packets lost | 0 |
+------------------------------+---------------------+|
Packets lost (percentage) | 0.000000 |
+------------------------------+---------------------+|
Packets bad | 0 |
+------------------------------+---------------------+|
Packets bad (percentage) | 0.000000 |
+------------------------------+---------------------+|
Packets trip-time average | 0ms |
+------------------------------+---------------------+|
Packets trip-time min | 0ms |
+------------------------------+---------------------+|
Packets trip-time max | 0ms |
+------------------------------+---------------------+
Decryption:
Displays statistical data on the quality of serviced packet traffic for12 hours 00 minutes
387
4.2.2.4 Control mode

To switch to flow control mode SS-7 you need to execute the commandmanagement.
SMG>management
Entering management mode.
SMG-[MGMT]>
? Show list of available

commands
exit Move up one menu level
history Viewing the history of entered

commands
nslookup <HOST> line RequestIP address for host with

given name
HOST– request address
ping host <HOST> SendPING request to

specified host
ping ip <IP> IP address in the format SendPING request to

AAA.BBB.CCC.DDD specifiedIP address
e1 stat clear <STREAM> 0-15 Reset statistics on the specified

thread E1
e1 stat show <STREAM> 0-15 View statistics on

specified flow E1
ss7link <SS7_LINK> 0-15 Transition to management

parameters of the specified stream
OKS-7
388
4.2.2.4.1 SS7 flow control mode

To switch to this mode, it is necessary to7 execute commandss7link<Link>, where <Link> is the number of
the SS-7 stream, takes values from 0 to 15.
SMG-[MGMT]>ss7link0
E1[0]. Signaling is SS7 SMG-
[MGMT]-[SS7LINK][0]>
chan block <CHAN_INDEX> 1-31 Block the specified channel (blo)
chan ccr Sending a messageCCR and verification

channel integrity by this message.
<CHAN_INDEX> 1-31
start
state
stop
chan group block Block channel group
<CHAN_INDEX_START> 1-31 CHAN_INDEX_START– initial

channel numberE1 in the group;
<CHAN_COUNT> 2-31 CHAN_COUNT- the number of channels in

group
chan group reset Reset channel group


group
chan group unblock Unlock channel group


group
chan rel <CHAN_INDEX> 1-31 Disconnect the connection on the specified

channel
chan reset <CHAN_INDEX> 1-31 Reset the specified channel
389
chan rlc <CHAN_INDEX> 1-31 Confirm disconnect on the

specified channel
chan unblock <CHAN_INDEX> 1-31 Unblock the specified channel
exit Moving from this configuration

submenu to a higher level
link clr outage Remove the "Local processor failure"

state on a thread
link send LFU Send a "forced link resolution"

message to the stream
link send LIN Send a "link denied" message

to the stream
link send LUN Send a "link resolve"

message to the stream
link set congestion Set the state of the stream to

"Overload"
link set outage Set the state of the thread to

"Local processor failure"
link start emergency Trigger an emergency thread start
link start normal Initiate a normal thread start
link stop Disable flow
show info chan Show information about the status of

channels in a stream
show info link Show thread status information
390
4.2.2.5 Port mirroring parameter configuration mode

In the port mirroring parameter configuration mode (Only forSMG-1016M) for to switch to this
mode, you must execute the commandmirroring.
SMG> mirroring
Change to the mirroring mode SMG-
[MIRRORING]>
apply yes/no Apply settings
exit Moving from this configuration submenu to a higher level
set Set up port mirroring:
<PORT> CPU/ PORT– port type;
GE_PORT0/
GE_PORT1/
GE_PORT2/
SFP0/
SFP1
<name> NAME– port assignment:
src_in/ src_in-source port of incoming packets -copy frames received from the
given port (source port);
src_out/ src_out-source ports of outgoing packets -copy frames

transmitted by this port (source port);
dst_in/ dst_in-destination port for incoming packets -destination port for

copied frames received by selected source ports;
dst_out dst_out-destination port for outgoing packets– receiver port for copied
frames transmitted by selected source ports
<ACT> on/off
391
show Show port mirroring settings
4.2.2.6 Configuration mode of general device parameters

To proceed to configuring/monitoring device parameters, execute the commandconfig.
The command available in each configuration menu isdo, which allows you to execute a command from
root menuCLI when in any configuration submenu and commandtopto go to root menuCLI.
SMG>config
Entering configuration mode. SMG-
[CONFIG]>
alarm path <set> off or /mnt/sd[abc][1-7]* Selecting an external storage device for saving
alarm messages:
Off– disabled;
/mnt/sd[abc][1-7]*- the path to the drive for

trace storage
access category Switching to the access category

configuration mode
cdr Entering Recording Parameters

Configuration ModeCDR
copy Write the current configuration to the non-

running_to_start volatile memory of the device (to the start
up configuration)
copy Restore current configuration from start

startup_to_runni
ng
count linkset Show number of SS-line groups7
count trunk Show number of trunk groups
392
count Show number of trunk directions

trunk_direction
count sip- Show number of interfacesSIP

interface
count radius- Show number of profilesRADIUS

profile
delete Show number of modifier table profiles

modifiers-table
count sipcause- Show number of match profiles

profile Q.850 and sip-reply
count routing- Show number of scheduled

profile routing profiles
count h323- Show Quantityh.323 profiles

interface
count ss7timers Show number of timer profiles OKS-7
delete link set <OBJECT_INDEX> existing number Delete line group SS-7
line groups
delete trunk <OBJECT_INDEX> existing number Delete trunk group

trunk group
delete <OBJECT_INDEX> existing number Delete trunk direction

trunk_direction trunk
directions
delete sip- <OBJECT_INDEX> existing number Delete InterfaceSIP

interface interfaceSIP
delete radius- <OBJECT_INDEX> existing number Delete profileRADIUS

profile profileRADIUS
delete <OBJECT_INDEX> existing number Delete modifier table

modifiers-table tables
modifiers
393
delete sipcause- <OBJECT_INDEX> existing number Delete lookup tableq.850 and sipreply
profile lookup tables
q.850 and sip-reply
delete routing- <OBJECT_INDEX> existing number Delete routing table on schedule

profile tables
routing by
schedule
delete h323- <OBJECT_INDEX> existing number Delete InterfaceH.323

interface interfaceH.323
delete <OBJECT_INDEX> existing number Delete SS-timer profile7

ss7timers timer profile
OKS-7
delete hunt- <OBJECT_INDEX> Existing group Delete call group

group call
delete pickup- <OBJECT_INDEX> Existing group Delete pickup group

group interception
e1 <E1_INDEX> 0-15 Switching to the configuration mode of

the selected streamE1
exit Move up one menu level
firewall dynamic Entering Dynamic Firewall

Configuration Mode
firewall static Switching to static firewall

configuration mode
ftpd Switching to configuration modeftp-

servers
h323 Switching to the H.323

configuration
h323 interface <H323_INDEX> 0-63 Switching to the mode of setting the operation of
the specified interface using the H.323
history Viewing the history of entered commands
394
hunt group <hunt-group_INDEX> 0-31 Switching to the operation setting mode

of the specified call group
logpath Apply path settings to trace storage.
Setting the trace storage path:
<apply>
<set> local local– local storage in operational memory;
/mnt/sd[abc][1-7]* /mnt/sd[abc][1-7]*- the path to the drive for

trace storage
<show> View trace storage path settings
link set <LINKSET_INDEX> 0-15 Switching to the configuration mode of groups

of lines SS-7
modifier table <MODTBL_INDEX> 0-255 Switching to modifier table configuration mode
network Switching to the network parameter

configuration mode
new link set Create a new line group SS-7
new trunk Create a new trunk group
new Create a new trunk direction

trunk_direction
new sip- Create a new interfaceSIP-T

interface
new radius- Create a new profileRADIUS

profile
new modifiers- Create a new modifier table

table
new sipcause- Create lookup tableq.850 and sipreply

profile
395
new routing- Create Scheduled Routing Table

profile
new h323- Create InterfaceH.323

interface
new ss7timers Create a profile of timers OKS-7
new hunt group Create call group
new pickup- Create pickup group

group
numplan Switching to dial plan configuration mode
pbx_profiles Switching to profile configuration

modePBX
ports range <RANGE_PORT> 1-65535 Set RangeUDP ports, used to transmit voice
traffic (RTP) and T.38 data
ports show Show configurationUDP ports
ports start <START_PORT> 1024-65535 Set initialUDP port used for the transmission
of voice traffic (RTP) and protocol T.38
q931-timers Switching to the timer configuration

modeQ.931
radius Switching to configuration modeRADIUS
record Switching to the call recording configuration

mode
reset_config Reset configuration
route Switching to static route configuration

mode
396
routing Entering Scheduled Routing Profile

Configuration Mode
show running Show current master configuration step by

main by_step step
show running Show the current master configuration in full

main wholesale
show running Show current network configuration

network
show running Show current configurationRADIUS- servers

radius_servers
show running Show current configurationSNMP

snmp
show startup Show initial basic configuration step by step

main by_step
show startup Show initial main configuration in full

main wholesale
show startup Show initial network configuration

network
show startup Show initial configurationRADIUS- servers

radius_servers
show startup Show initial configurationSNMP

snmp
sip Entering parameter configuration

configuration modeSIP/SIP-T
sip interface <SIPT_INDEX> 0-63 Switching to the interface parameter

sip users Switching to the subscriber parameters

ss7cat Switching to the configuration mode of

categories OKS-7
397
ss7timers <SS7_TIMERS_INDEX> 0-15 Switching to the configuration mode

of timers OKS-7
submodule- Switching to the configuration mode

usage for using submodulesSM-VP
switch_port Entering the internal switch

configuration mode
sync Switching to configuration mode
synchronization settings
syslog Entering the syslog parameter

configuration mode
trunk <TRUNK_INDEX> 0-63 Switching to trunk group

configuration mode
trunk_direction <DIRECTION_INDEX> 0-31 Entering Trunk Direction

Configuration Mode
v5.2 Entering parameter configuration mode

V5.2 for current E1 stream
4.2.2.7 CDR parameter configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modecdr.
SMG-[CONFIG]> cdr
Entering CDR info mode. SMG-
[CONFIG]-[CDR]>
archive Data archivingCDR
<all> String not long

more31 characters
<directory>
category save yes/no Save/do not save subscriber category

in filesCDR
398
config Return to menuConfiguration
duration count mode <CDR_COUNT_MODE> round-up/round-down/ Rounding duration up, down, or do not
not round round (write in milliseconds)
empty save <CDR_EMPTY> yes/no Save/don't saveCDR files, not containing

records
enabled <CDR> yes/no form/not formCDR- records

fields add <field> Adds the specified field to the end of the
list of fields (see sectionField ListCDR)
fields default Sets the base set of fields
fields flush Clears the list of used fields
fields set <field> <FIELD_INDEX> 0-39 Replaces the field at the corresponding
position with the specified field (see
section Field ListCDR)
file create mode <CDR_FILE> File Creation ModeCDR:
periodically/ periodically– with a given period;
once-a-day/ once-a-day- once a day;
once-an-hour once-an-hour- once an hour
header <CDR_HEADER> yes/no Record / do not record at the beginning

CDR file header of the form: SMG. CDR. File
started at 'YYYYMMDDhhmmss', where
'YYYYMMDDhhmmss' is the start time
saving records to a file
399
localdisk Data storage pathCDR on local

drives;
<set> /mnt/sd[abc][1-7]* View storage path settingCDR

<show>
localkeep period Data retention timeCDR on local

storage
<day> 0-30
<hour> 0-23
<min> 0-59
localsave Save dataCDR on local disk
<no>
<yes>
period day <CDR_DAY> 0-30 Set formation periodCDR- records and

their saving in the RAM of the device, days
period hour <CDR_HOUR> 0-23 Set formation periodCDR- records and

save them in the device's RAM, watch
period min <CDR_MIN> 0-59 Set formation periodCDR- records and

their saving in the RAM of the device,
minutes
pickup mark <CDR_pickup_MARK> yes/no Add/not add to entryCDR additional field

"intercept label"
redirectmark <CDR_REDIRECT_MARK yes/no Add/not add to entryCDR additional

> field "forward label"
redirect save <CDR_REDIRECT> yes/no Add to entriesCDR optional field

Redirecting number, otherwise for
forwarded callRedirecting number will
replace Calling party number
400
redirected duration <CDR_REDIR_DURATIO yes/no Specify duration

N> forwarded call
release initiator mark <CDR_RELEASE> yes/no Preserve disconnect initiator

label
show Show settingsCDR records
show_dirs Show folder path to accessFTP server
signature <CDR_SIGNATURE> string not long Specify a distinguishing feature by

more63 characters which you can identify the device that
created the record
unsuccess <CDR_UNSUCC> yes/no Write / do not write toCDR files

unsuccessful calls (did not end with a
conversation)
upload archive ftp/ Send archive toFTP/TFTP Server

tftp
<ARCHIVE_NAME> string not long

more63 characters
<FTP/TFTP_server> IP address
upserver enabled <CDR_UPLOAD> yes/no Transfer/not transferCDR records to the

server
upserver ipaddr <CDR_SERVER_IPADDR string not long AskServer IP

> more63 characters
upserver login <CDR_SERVER_LOGIN> string not long Set a username to access the server
more63 characters
upserver passwd <CDR_SERVER_PASSW string not long Set a user password to access the server
D> more63 characters
upserver path <CDR_SERVER_PATH> string not long Set the path to the folder on the server
more63 characters where the files will be savedCDR records
upserver port <CDR_SERVER_PORT> 1-65535 AskServer TCP Port
upserver protocol <CDR_VIA_PROTO> FTP/SCP Set the protocol forCDRs will go to the
server
401
upserver_reserve <CDR_RESERV_ENA> yes/no Transfer/not transferCDR records to the

enabled backup server
upserver_reserve <CDR_RESERV_IPADDR string not long AskBackup Server IP

ipaddr > more63 characters
upserver_reserve <CDR_RESERV_LOGIN> string not long Set a username to access the standby
login more63 characters server
upserver_reserve <CDR_RESERV_ONLY_F yes/no Enable/disable savingCDR- files to the

only_fail AIL> backup server only if an error occurs
while writing to the main
upserver_reserve <CDR_RESERV_PASSW string not long Set a user password to access the backup
passwd D> more63 characters server
upserver_reserve <CDR_RESERV_PATH> string not long Set the path to the folder on the backup
path more63 characters server where the files will be saved CDR
records
upserver_reserve port <CDR_RESERV_PORT> 1-65535 AskBackup server TCP port
4.2.2.8 List of CDR fields

Field ListCDR used in commandsfields add<field> andfields set<field> <n>.
<field> Meaning
acct-session-id RADIUS Account-Session-Id, Acct-Session-Id field value, sent

in an accounting package toRADIUS
called in Called number at the input (before modifications)
called out Called number on exit (after modifications)
calling in Caller number at the entrance (before modifications)
calling out Caller number at the exit (after all modifications)
device sign hallmark
disc code Disconnect code byQ.850
402
disc info Call status on disconnect
duration Call duration
global-callref FieldGlobal Call Reference (GCR)
incoming CID category Caller ID category at the entrance (before modifications)
incoming description Caller Description - Subscriber/Trunk Name (TG)
incoming E1 chan Incoming channel number E1
incoming E1 stream Incoming flow number E1
incoming ipaddr Caller's IP address
incoming SIP call id SIP Call-ID of incoming call
incoming SS7 category Category OKS-7 at the entrance (before modifications)
incoming SS7 CIC NumberCIC incoming call
incoming type Caller Type
mark pickup Call pickup label
mark redir Call forwarding label
mark release side Disconnect Initiator Label
numplan in Dial plan through which the call came
numplan out Dial plan through which the call left
outgoing CID category Category of caller ID at the exit (after modifications)
outgoing description Called Party Description - Subscriber/Trunk Name (TG)
outgoing E1 chan Outgoing channel number E1
outgoing E1 stream Outgoing stream number E1
outgoing ipaddr Called IP address
403
outgoing SIP call id SIP Call-ID of an outgoing call
outgoing SS7 category Category OKS-7 output (after modifications)
outgoing SS7 CIC NumberOutgoing CIC
outgoing type Called party type
radius-rejected Blocker addressRADIUS servers
redirecting in Forwarding number at the input (before modifications)
redirecting out Exit Forwarding Number (after modifications)
sequential number Entry sequence number
time connect Call Answer Time
time disconnect Call release time
time setup Call arrival time
404
4.2.2.9 Access category configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modeaccess
category.
SMG-[CONFIG]> access category

Entering Access-Category mode. SMG-
[CONFIG]-[ACCESS-CAT]>

set access Define access rights of categories in

relation to each other:
<CAT_IDX> 0-63 CAT_IDX - custom category index access;
<ACCESS_IDX> 0-63 ACCESS_IDX – category to which

access is configured;
<ACCESSIBLE> enable/disable ACCESSIBLE – category access status

(available, not available)
set name Change the name of the access category
<CAT_IDX> 0-63 CAT_IDX - custom category index access;
<name> category name NAME - name of the access category

access, no more31
characters (numbers,
letters, sign "_")
show <CAT_IDX> 0-63 Show configuration for this access category
showall Show configuration of all access

categories
405
4.2.2.10 E1 stream configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modee1
<E1_INDEX>, where <E1_INDEX> is the E1 stream number.
SMG-[CONFIG]>e10
Entering E1-stream mode. SMG-
[CONFIG]-E1[0]>
alarm <ON_OFF> on/off Enable/disable indication of

alarms for this streamE1
crc4 <ON_OFF> on/off Enable/disable controlCRC4 given

streamE1
disabled Disable a thread
enabled Enable the flow
equalizer <ON_OFF> on/off Enable/disable flow signal amplification E

1

lapd Entering parameter configuration mode

LAPD for current E1 stream
linecode AMI Set the type of linear coding on the

given streamAMI
linecode HDB3 Set the type of linear coding on the

given streamHDB3
name letter or number or '_', '.', '-'. Max Flow name Е1 63 symbols
406
q931 Switching to alarm configuration

modeQ931 for current flowE1
remalarm <ON_OFF> on/off Enable/disable indication in case of a

remote accident on a given stream
show Show the configuration of a given

stream
signaling <Signaling type> Q931_USR Set alarm type for flow
Q931_NET Possible alarm types: Q931_USR,

Q931_NET, SS7, SORM, V5.2LE,
SS7 SORM-TRANSIT
SORM
V5.2LE
SORM-TRANSIT
slipIND <ON_OFF> on/off Display an alarm if an error occurs
slip in the receiving path
407
slipTO <TIMEOUT> 5sec/ Set the frequency of polling the flow

parameters from the board, if slippage is
10sec/ detected on this flow, then during this
timeout the station will
20sec/
signal an accident
30sec/
45sec/
1min/
2min/
3min/
5min/
10min/
15min/
30min/
1hour/
2hour/
6 hours
sort Switching to configuration mode
SORM for current thread E1
ss7 Switching to configuration mode
alarm parameters OKS-7 for current

threadE1
408
4.2.2.10.1 LAPD parameter configuration mode for the current E1 stream

The mode is only available for signalingQ.931 (set by commandsignaling). To go to this mode is required in
flow configuration mode E1 execute commandlapd.
SMG-[CONFIG]-E1[0]> lapd E1[0].

Signaling is Q931 SMG-[CONFIG]-
E1[0]-[LAPD]>
N200 <N200> 0-255 Set number of connection attempts
show Show configurationLAPD
t200 <T200> 0-255 Set timer valueT200, x100 ms
t203 <T203> 0-255 Set timer valueT203, x100ms
409
4.2.2.10.2 Q.931 signaling configuration mode for the current E1 stream

The mode is only available for signalingQ.931 (set by commandsignaling). To go to this mode is required in
flow configuration mode E1 execute commandq931.
SMG-[CONFIG]-E1[0]> q931 E1[0].

Signaling is Q931 SMG-[CONFIG]-
E1[0]-[Q931]>
access category <CAT_IDX> 0-31 Set access category for stream
categoryAON <CAT_AON> 0-15 Set categoryCaller ID for incoming call
channel Enable/disable the specified channel
<CHAN_NUM> [0-31] or 'all'
<on_off> on/off
chanorder <CHAN_ORDER> Set the channel occupation order:
up_ring/ up_ring- consecutively forward
down_ring/ down_ring- sequentially back
up_start/ up_start- starting from the first forward
down_start down_start– starting from last back
exit Return from this configuration submenu to a higher level
InBand in <on_off> on/off Enabling the option "ProcessPI In-Band in

Disconnect DISCONNECT"
invokeID <INVOKE_ID> 1024-65535 Set the initial operation call ID (used as a reference number
to uniquely identify the operation call)
410
numplan <CLD_PLAN_ID> unknown/ Set the dial plan type.
ISDN/
-To use the common plan numberingE.164 select -
telephony/ ISDN/telephony.
national/
Privat
qsig <ON_OFF> on/off Enable/disable alarmQSIG
RestartChannel <SEND> send/ Give out / don't give outRESTART channel

don't_send
RestartInterface <SEND> send/ Give out / don't give outRESTART interface

don't_send
RoutingProfile <PROF Number> [0-127] or none Select scheduled routing profile
SendCatAON <ON_OFF> on/off Allow/prohibit the transmission of the caller's ANI category in
the messageSETUP as first number digits.
- For proper operation, it is necessary to support

this mode on the opposite side.
SendDialTone <ON_OFF> on/off Issue / do not issue a ready signal to the lineDial Tone with
incomingoverlap-occupation
SendEndOfDial <ON_OFF> on/off Enable/disable the transmission of the message "End of

dialing"
show Show alarm parameter configurationQ931
transit location <ON_OFF> on/off Enable/disable parameter redirectionLocation Number from

number the incoming SS7/SIP-T message to the Calling Party Number
parameter of the outgoing SETUP message Q931
trunk <trunk_index> 0-31 Set trunk group number for this stream
411
4.2.2.10.3 SORM configuration mode for the current E1 stream

The mode is only available for signalingSORM (installed with the commandsignaling). To go to this mode is
required in flow configuration mode E1 execute commandsort.
SMG-[CONFIG]-E1[0]> sorm E1[0].

Signaling is SORM SMG-[CONFIG]-
E1[0]-[SORM]>

commands
activity <ON_OFF> on/off Enable/disable level messaging

activity controlL1
chan1(2) mode <SORM_MODE> DCE/DTE Set mode forchan1(2).
Allowed modes:DCE, DTE
chan1(2) send L3 Reset <ON_OFF> on/off Allow/Deny to send to the channel

1(2) L3 restart command
chan1(2) send L3 Restart <ON_OFF> on/off Allow/Deny to send to the channel1

reset command L3
chan1(2) send SABME <ON_OFF> on/off Install/Disable

balanced asynchronous extended
mode(SABME) to channel1(2)
cmd <CMD_ADDR> 1/3 Set command frame address


commands
mode tcp/x25 Selecting the operating mode of signal

channels KSL
412
protocol specification <SPECIFICATION> order_70/ Choice of SORM specification
KZ_specification/
order_268
resp <RESP_ADDR> 13 Set reply frame address
show Show configurationSORM
tcp interface <IFACE_NAME> Choosing a network interface for an

organizationTCP connections
tcp port1 10000-65535 Choosing a virtualtcp port for

organization KPD-1
tcp port2 10000-65535 Choosing a virtualtcp port for

organization KPD-2
timer 10 minutes <ON_OFF> on/off Enable/disable timeout for waiting

for receiving commands from SORM
PU
413
4.2.2.10.4 Configuration mode of SS-7 signaling parameters for the current E1 stream
The mode is available only for signaling OKS-7 (set by commandsignaling). To go to this mode is required in
flow configuration modeE1 execute commandss7.
SMG-[CONFIG]-E1[0]> ss7 E1[0].

Signaling is SS7 SMG-[CONFIG]-
E1[0]-[SS7]>
CIC fill Set valueCIC for everyone time slots,

starting from zero:
<CIC> 0-65535 CIC - CIC start number
<step> 0-255 step - numbering step
CIC set Set valueCIC for single timeslot:
<TIMESLOT> 0-31 TIMESLOT - timeslot number
<CIC> 0-65535 CIC - CIC value
Dchan <D_CHAN> 0-31 Set numberD-channel for line:
0 - do not use D-channel

(conversational flow)
DPC-MTP3 0-16383 Assign valueDPC MTP3 for given

stream

link set <linkset_index> 0-15 Assign a line group OKS-7 for given
stream
414
show Show configuration of SS-alarm

parameters7
SLC <slc> 0-15 Set the identifier of the signaling channel

in the group of lines SS-7
4.2.2.11 Dynamic firewall parameter configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modefirewall
dynamic.
SMG-[CONFIG]> firewall dynamic

Entering dynamic firewallmode. SMG-
[CONFIG]-[DYN-FIREWALL ]>
blacklist add <BLACKIP> IP address in the format Add an address to the list of blocked
AAA.BBB.CCC.DDD or subnet in addresses
notationsCIDR AAA.BBB.CCC.DDD/FF
blacklist <BLACKIP> IP address in the format Remove an address from the list of blocked
remove by AAA.BBB.CCC.DDD or subnet in addresses
addr notationsCIDR AAA.BBB.CCC.DDD/FF
blacklist <POSITION> 0-65635 Remove an address from the list of blocked

remove by addresses by its position in the list
pos
blacklist Show list of blocked addresses

show all
blacklist Show the number of entries in the list

show count of addresses blocked by the dynamic
firewall
blacklist <BLACKIP> IP address in the format Find the specified address in the list
show AAA.BBB.CCC.DDD or subnet in of blocked addresses
address notationsCIDR AAA.BBB.CCC.DDD/FF
blacklist <COUNT> 0-4095 Show the specified number from the

show first beginning of the list of blocked addresses
415
blacklist <COUNT> 0-4095 Show the specified number from the end of
show last the list of blocked addresses
blacklist <POSITION> 0-65635 Show the entry at the specified position in

show the list of blocked addresses
position
block history Viewing the history of blocked

show all addresses
block show Show the number of entries in the

count log of blocked addresses
block show <BLACKIP> IP address in the format Find the specified address in the log
address AAA.BBB.CCC.DDD or subnet in of blocked addresses
block show <COUNT> 0-4095 Show the specified number from

first the beginning of the blocked
addresses log
block show <COUNT> 0-4095 Show the specified number from the end
last of the log of blocked addresses
block show <POSITION> 0-65635 Show an entry at the specified block

position address log position
blocklist <BLACKIP> IP address in the format Remove an address from the list of
remove by AAA.BBB.CCC.DDD or subnet in automatically blocked addresses
addr notationsCIDR AAA.BBB.CCC.DDD/FF
blocklist <POSITION> 0-65635 Remove an address from the list of

remove by automatically blocked addresses by its
pos position in the list
blocklist Show list of automatically

show all blocked addresses
blocklist Show the number of entries in the list of

show count automatically blocked addresses
blocklist <BLACKIP> IP address in the format Find the specified address in the list of
show AAA.BBB.CCC.DDD or subnet in automatically blocked addresses
address notationsCIDR AAA.BBB.CCC.DDD/FF
416
blocklist <COUNT> 0-4095 Show the specified number from

show first the top of the list of automatically
blocked addresses
blocklist <COUNT> 0-4095 Show the specified number from the end of
show last the list of automatically blocked addresses
blocklist <POSITION> 0-65635 Show the entry at the specified position in

show the list of automatically blocked
position addresses

set Set the time in seconds for the service

block_time during which access from a suspicious
address will be blocked
<SERVICE> SIP/WEB/TELNET/SSH/OTHER
<BLCKTIME> 60-352800
set enable <ENA> on/off Enable/Disable Dynamic Firewall
set tries Set the maximum number of failed

attempts to access a service before a
host is blocked
<TRIES> 1-10
set Set the forgiveness time for the service

forgive_time
<FORGIVETIME> 60-352800
set Enable progressive blocking

increment for a service
417
<INCREMENT_FLG no/yes
>
show Show dynamic firewall settings
whitelist add <WHITEIP> IP address in the format AddIP address to address list,
AAA.BBB.CCC.DDD or subnet in prohibited for automatic blocking
whitelist <WHITEIP> IP address in the format DeleteIP address from the list of
remove by AAA.BBB.CCC.DDD or subnet in addresses, prohibited for automatic
addr notationsCIDR AAA.BBB.CCC.DDD/FF blocking
whitelist <POSITION> 0-65635 DeleteIP address from the list of

remove by addresses, forbidden for automatic
pos blocking by its position in the list
whitelist Show a list of addresses blocked from

show all automatic blocking
whitelist Show the number of entries in the

show count list of addresses blocked from
automatic blocking
whitelist <WHITEIP> IP address in the format Find the specified address in the
show AAA.BBB.CCC.DDD or subnet in list of addresses blocked from
address notationsCIDR AAA.BBB.CCC.DDD/FF automatic blocking
whitelist <COUNT> 0-4095 Show the specified number from the

show first beginning of the list of addresses
banned from automatic blocking
whitelist <COUNT> 0-4095 Show the specified number from the end
show last of the list of addresses banned from
automatic blocking
whitelist <POSITION> 0-65635 Show the entry at the specified position

show in the list of addresses not allowed for
position automatic blocking
418
4.2.2.12 Static firewall parameter configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modefirewall static.
SMG-[CONFIG]> firewallstatic Entering

staticfirewall mode SMG-[CONFIG]-
[FIREWALL]>

commands
add profile <PROF_NAME> allowed to use letters, numbers, Add profilefirewall

symbol '_', maximum63 symbol
add rule <direction> Add rulefirewall
forward The direction of the rule
input
output
<ENABLE> enable/disable Enable/disable

rules
<RULE_NAME> Text, max.63 characters Rule name
<S_IP> AAA.BBB.CCC.DDD Source IP address
<S_MASK> AAA.BBB.CCC.DDD Source subnet mask
<R_IP> AAA.BBB.CCC.DDD Destination IP address
<R_MASK> AAA.BBB.CCC.DDD Destination subnet mask
<PROTO> protocol type
any
tcp
udp
icmp
tcp+udp
<S_PORT_START> 1-65535 Source start port
<S_PORT_END> 1-65535 Source end port
<D_PORT_START> 1-65535 Destination start port
419
<D_PORT_END> 1-65535 Destination destination port
<ICMP_TYPE> Package typeICMP
420
none
any
echo-reply
destination unreachable
network unreachable
host unreachable
protocol unreachable
port-unreachable
fragmentation-needed
source-route-failed
network unknown
host unknown
network-prohibited
host-prohibited
TOS-network-unreachable
TOS-host-unreachable
communication inhibited
host-precedence-violation
precedence-cutoff
source-quench
redirect
network redirect
host redirect
TOS-network-redirect
TOS-host-redirect
echo request
router-advertisement
router-solicitation
421
time-exceeded
ttl-zero-during-transit
ttl-zero-during-reassembly-
parameter-problem
ip-header-bad
required-option-missing
timestamp request
timestamp-reply
address-mask-request
address-mask-reply
<ACTION> Action - action

performed by data
rule:
accept ACCEPT- packets falling under

this rule will be skipped by the
firewall firewall
drop DROP- packets falling under

this rule will be rejected by the
firewall firewall without any
informing the party that
transferred the package
reject REJECT- packets falling under

firewall firewall, the party that
transmitted package, either
package will be sentTCP RST or
ICMP destination unreachable
<P_IDX> 1-65535 Profile numberfirewall
add rule geoip <direction> AddGeoIP rule

firewall
input The direction of the rule:
output
422

rules
<COUNTRY> The name of the country Country to which the address

belongs
any
tcp
udp
icmp
tcp+udp
423
none
any
echo-reply
network unreachable
host unreachable
port-unreachable
source-route-failed
network unknown
host unknown
network-prohibited
host-prohibited
precedence-cutoff
source-quench
redirect
network redirect
host redirect
TOS-host-redirect
echo request
router-solicitation
424
time-exceeded
parameter-problem
ip-header-bad
timestamp request
timestamp-reply
address-mask-reply

performed by data
rule:
accept ACCEPT- packets falling under

firewall firewall
drop DROP- packets falling under

reject REJECT- packets falling under

add rule string <direction> Add rulefirewall- string

checking
input The direction of the rule
output
425

rules
<CONTENT> Text, max.127 characters The text string that should

be in the package
<S_IP> AAA.BBB.CCC.DDD Source IP address
<S_MASK> AAA.BBB.CCC.DDD Source subnet mask
<R_IP> AAA.BBB.CCC.DDD Destination IP address
<R_MASK> AAA.BBB.CCC.DDD Destination subnet mask
any
tcp
udp
icmp
tcp+udp
426
none
any
echo-reply
network unreachable
host unreachable
port-unreachable
source-route-failed
network unknown
host unknown
network-prohibited
host-prohibited
precedence-cutoff
source-quench
redirect
network redirect
host redirect
TOS-host-redirect
echo request
router-solicitation
427
time-exceeded
parameter-problem
ip-header-bad
timestamp request
timestamp-reply
address-mask-reply

performed by data
rule:
accept ACCEPT - packets that hit under

firewall firewall
drop DROP - packets falling under

reject REJECT - packets hit under this

rule will be rejected by the
apply Apply settingsfirewall
del profile <ID> 1-65535 Delete profilefirewall
428
del rule <ID> 1-65535 Delete rulefirewall
exit Exit from this configuration

modify profile <ID> 1-65535 Profile Indexfirewall
<name> allowed to use letters, numbers, Entering a new device name

symbol '_'. Maximum63 symbol
modify rule <Type> action Edit the specified rule firewall

(one of the options)
dport_end
dport_start enable
icmp-type
name
prof_id
proto
r_ip
r_mask
s_ip
s_mask
sport_end
sport_start
traffic type
<ID> 1-65535
<param> New value according to the given

parameter type
move down <ID> 1-65535 Move rule down one position
move up <ID> 1-65535 Move rule up one position
429
set eth <PROFILE ID> 0-65535 Assign a rule to a network

interface
PROFILE ID = 0 means that

profile is not used
set pptp <PPP_IDX> 0-5 Assign a rule to

interface
<PROFILE ID> 0-65535 PROFILE ID = 0 means that

profile is not used
set vlan <VLAN_IDX> VLAN1…VLAN8 Assign a rule toVLAN
<PROFILE ID> 0-65535 PROFILE ID = 0 means that

profile is not used
show config Show configuration
show interfaces Show Options

interfaces
show system Show system

options
4.2.2.13 FTP parameter configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modeftpd.
SMG-[CONFIG]>ftpd
Entering ftpd mode.
SMG-[CONFIG]-[FTPd]>

commands
exit Exit from this configuration submenu

to a higher level
430
set enable <EN> on/off Enable/DisableFTP server
set port <PORT> 1-65535 Set port forFTP servers
set interface <IFACE_NAME> line before255 Set network interface forFTP servers
characters
set timeout idle <TIME> 0-600 Set inactivity timer, in seconds
set timeout login <TIME> 0-600 Set authorization timer, in

seconds
set timeout session <TIME> 0-600 Set session timer, in seconds
show config Show configurationFTP servers
show user Show configuration

users
user add <USER_NAME> Add user
Set new username
<PASSWD> Set a password for a new user
<CDR_ACCESS> Set directory permissions CDR
<LOG_ACCESS> Set directory permissions LOG
<MNT_ACCESS> Set directory permissions MNT

(external drives)
<CFG_ACCESS> no_access/r/w/r Set directory permissions cfg

(config files)
no_access/r/w/r
no_access/r/w/r
no_access/r/w/r
user del <IDX> 1-4 Delete user
431
user modify access <IDX> 0-4 Modify access rights for the
specified user:
<CDR_ACCESS> no_access/r/w/r • Configuring access to the CDR

directory, read / write
<LOG_ACCESS> no_access/r/w/r • Configuring access to the log

directory, read / write
<MNT_ACCESS> no_access/r/w/r • Configuring access to the mnt

directory, read/write
<CFG_ACCESS> no_access/r/w/r • Configuring access to the cfg

directory, read/write
user modify password <IDX> 0-4 Modify the password for the
specified user.
<PASSWD>
4.2.2.14 H.323 protocol parameter configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modeh323
configuration.
SMG-[CONFIG]> h323 configuration

Entering H323Config-mode.
SMG-[CONFIG]-H323(config)>
alias H323ID <IDX> String no more63 Set the gateway name when registering forGatekeeper ´e
characters
cisco1700_adaptati <ON_OFF> on/off Enable / disable adaptationcisco1700

on
exit Exit from this configuration submenu to a higher

level
gatekeeper discover <ON_OFF> on/off Enable/disable search modeGK
gatekeeper DSCP <GK_DSCP_RA 0-63 Assign priorityIP diffserv for messages protocol
S> RAS
432
gatekeeper H323ID <GK_H323ID> line before63 characters Set GateKeeper ID. The value "none" removes the ID or
none
local gatekeeper <ON_OFF> on/off Allows registration of local users on

subscribers the localGK
gatekeeper mode <GK_MODE> Working modeGK:
none/ none- do not use
local/ locallocal
remote remote– remote
gatekeeper ipaddr <IPADDR> AAA.BBB.CCC.DDD AskGK's IP address
gatekeeper <KEEPAL> 10-86400 Set registration time toGK

keepalive
gatekeeper port <PORT> 1-65535 Set port forGK
gatekeeper tech <GK_TECH_PR line before255 Set technology prefix forG.K. Meaning "
prefix EFIX> characters ornone none" removes the prefix
ttl gatekeeper <TTL> 90-86400 Set re-registration time forGK
gatekeeper use <ON_OFF> on/off Enable/disable usageGK
iface <IFACE_NAME line before255 Set network interface forH.323

> characters
port <PORT> 1-65535 Set local numberTCP port to receive signal

messagesH.323
primary DGK <DGK_H323ID> line before63 characters Set PrimaryID for Directory GateKeeper.
H323ID ornone Meaning "none" removes the ID
primary DGK ipaddr <DGK_IPADDR AAA.BBB.CCC.DDD Set PrimaryIP address for Directory
> GateKeeper
433
secondary DGK <DGK_H323ID> line before63 characters Set additionalID for Directory GateKeeper.
H323ID ornone The value "none" removes the ID
secondary DGK <DGK_IPADDR AAA.BBB.CCC.DDD Set additionalIP address for Directory

ipaddr > GateKeeper
show Show settings
4.2.2.15 H.323 interface parameters configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modeh323
interface<H323_INDEX>, where <H323_INDEX> is the number of the H.323 direction.
SMG-[CONFIG]>h323interface0 Entering
H323-mode.
SMG-[CONFIG]-H323-INTERFACE[0]>
access category <CAT_IDX> 0-31 Assign an access category
alias H323ID <H323ID> String no more63 Remove gateway name when registering to
clear characters Gatekeeper
alias H323ID set <H323ID> String no more63 Add gateway name when registering for
characters Gatekeeper
codec disable <CODEC_IDX> 0-3 Disable the selected codec. Codecs are
numbered by priority - from0 (highest) to 3
(lowest)
codec pte <CODEC_IDX> 0-3 Askpayload time
<PTE> 10/20/30/40/50/
60/70/80/90
434
codec ptype <CODEC_IDX> 0-3 Askpayload type. static value sets the
default value depending on the selected
codec
<PTYPE> 0-127 or static
codec set <CODEC_IDX> 0-3 Set codec to use
<CODEC> G.711-U/
G.711-A/
G.729/
G.723.1_5.3/
G.723.1_6.3
destination clear Delete destination for an interface
destination set <HOSTNAME> String no more63 Set interface destination

characters
DSCP RTP <DSCP_RTP> 0-255 Set IDDSCP for RTP traffic
DSCP-SIG <DSCP_SIG> 0-255 Set IDDSCP for SIG traffic
DTMF mime <DTMF_c> 0-255 Set levelSIP INFO
DTMF mode <DTMF_m> inband/ ModeDTMF for this interface
RFC2833/
SIP INFO
DTMF payload <DTMF_p> 96-127 Set payload type for RFC2833
econ <CANCELATION> Set echo cancellation mode:
voice/ Voice– echo cancellers included
435
nlp-off-voice/ nlp-off-voice– echo cancellers included voice

mode, non-linear processor NLP is off. When the
levels transmitting and receiving signals are
very different, a weak signal can be suppressed
by a non-linear processorNLP. For To prevent
this from happening, use this mode of
operation of echo cancellers
modem/ modem– echo cancellers included modem

operation mode (filtering of the constant
component of the signal is turned off,
control by the processorNLP off, comfort
noise generator off)
off Off- do not use echo cancellation (this mode

is set by default)

to a higher level
fast start <ON_OFF> on/off Enable/Disablefast start
fax detection Set fax detection mode:
<DETECTION> no/ no– do not detect faxes
callee/ callee- only on the receiving side
caller/ caller– only on the transmitting side
callee_and_caller callee_and_caller - on the receiving and

transmitting party
gain rx <GAIN> Set the volume for voice reception,

amplification / attenuation of the level of the
signal received from the interacting gateway and
output to the speaker of the telephone set
connected to the gatewaySMG
gain tx <GAIN> Volume for voice transmission, amplification /

attenuation of the signal level received from the
microphone of the telephone set connected to the
gatewaySMG and transmitted to the cooperating
gateway
gatekeeper <ON_OFF> on/off Enable/Disable UsageGK (gatekeeper)
436
h245tunneling <ON_OFF> on/off Enabling/disabling the use of tunneling
interface rtp <IFACE_NAME> line before255 Selecting a network interface for transmission RTP
characters
jitter adaptation <JT_AP> 1000-65535 Set the period of adaptation of the jitter
period buffer to the lower limit, in milliseconds
jitter adjust mode <JT_AM> Set jitter buffer tuning mode:
non-immediate/ non-immediate- smooth
immediately immediately– instant
jitter deletion <JT_DM> soft/hard Set buffer adaptation mode. Determines how
mode packets will be removed when the buffer
adapts to the lower bound:
• soft- using intelligent a scheme for

selecting packets for removal that have
exceeded the threshold;
• hard– packets whose delay
exceeded the threshold are
immediately deleted.
jitter deletion <JT_DT> 0-500 Set the threshold for immediately removing
threshold packages in milliseconds. If the buffer grows
and the packet delay exceeds this limit, the
packets are immediately deleted
jitter init <JT_INIT> 0-200 Set the initial value of the adaptive jitter buffer
in milliseconds
jittermax <JT_MAX> 0-200 Set the upper bound (maximum size) of the
adaptive jitter buffer in milliseconds
jitter min <JT_MIN> 0-200 Set the size of a fixed or lower bound
(minimum size) of the adaptive jitter buffer
jitter mode <JT_MODE> Jitter buffer mode:
437
adaptive/ adaptive– adaptive
non adaptive non adaptive- fixed
jitter vbd <JT_VBD> 0-200 Set a fixed buffer size for data transfer in
modeVBD
max_active <MAX_ACTIVE> 0-65535 Set the maximum number of active

connections for an interface
name <s_name> allowed Set a name forH.323 interface

use letters,
digits, character '_'.
Maximum31 characters
nat <NAT> enable/disable Switch on switch offNAT
numbering plan <NUMPLAN> 0-15/0-255 Select numbering plan
port <PORT> 1-65535 AskThe TCP port of the communicating

gateway on which it receives signaling
SIP
routing_profile <prof> 0-127 Scheduled Routing Profile Selection
RTCP control <RTCP_c> 2-255 Set the number of time intervals (RTCP period),
during which protocol packagesRTCP from
opposite side
RTCP period <RTCP_p> 5-255 Set the time period in seconds after which the
device sends control packets via the protocol
RTCP
show config Show interface informationH.323
src verify <ON_OFF> on/off Enable/disable control of incoming media

traffic fromIP address and UDP port, specified
in the session descriptionsdp, otherwise,
traffic is received from anyIP addresses and
UDP ports
438
t38 bitrate <BITRATE> nolimit/2400/4800/ Set the maximum fax transmission speed for T.
38
7200/9600/12000/
14400
t38 disable Disable fax reception by protocolT.38
t38 enable Enable fax reception by protocolT.38
t38 fillbitremoval <ON_OFF> on/off Enable/disable padding bit removals and

insertions for non-ECM mode data
t38 pte <T38_PTE> 10/20/30/40 Set the packet formation frequency T. 38 in

milliseconds
t38 ratemgmt Set baud rate control method:
<T38_RATE_MGMT> localTCF/ local TCF- the method requires tuning

signalTCF generated receiving gateway
locally
transferredTCF transferred TCF- the method requires

tuning signalTCF was transmitted from
transmitter to receiver
t38 redundancy <T38_REDUNDANCY> off/1/2/3 Use redundant frames for error

protection
• off- do not use
trunk <TRUNK> 0-31 Set trunk group number for interface
VAD_CNG <ON_OFF> on/off Enable/disable speech activity detector/

comfort noise generator for interface
vbd codec <CODEC> G.711-U, G.711-A Codec used for data transmission VBD
vbd enable Enable useV.152
vbd disable Turn off useV.152
vbd payload type <VBD_p> Static,96-127 Type of load used forVBD codec
439
4.2.2.16 Call group configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modehunt group <hunt-
group_INDEX>, where <hunt-group _INDEX> is the hunt group number.
SMG-[CONFIG]> hunt-group 0
Entering HuntGroup-mode. SMG-
[CONFIG]-HUNT-GROUP[0]>

commands


commands
move number to start Move number to top of list
End Move number to end of list
position Move number to

a certain position
set conference number * , # , D,0-9. Or 'none' for Set conference number

blank(delete) number
set ltimer Number in the range 5-255 AskL-group call timer
set mode (all/seqFisrt/ Set group operation mode
seqNext/seqAllFirst/
seqAllNextr)
set name letter or number or '_', '.', '-'. Max Set call group name
63 symbols
440
set number Set call group member

number
set record-and-notify <MODE> simultaneous-notification/ Set the operation mode "recording

mode and notification" - simultaneous /
sequential-notification separate
set record-and-notify <DURATION> 15-120 Set maximum notification

duration recording time
set stimulator Number in the range 5-255 AskS-timer call one group
member
set number-mask Max 255 symbols Set mask for call group
set recall-busy yes/no Enable/disable the "Call back

busy" option
set recall-declined yes/no Enable / disable the option "Call

back the rejected call"
set release mode <MODE> default/silent Set Call Group Clear Mode -
Default/Quiet
4.2.2.17 SS-7 line group configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modelink set
<LINKSET_INDEX>, where <LINKSET_INDEX> is the line group number.
SMG-[CONFIG]>linkset0
Entering Linkset-mode.
SMG-[CONFIG]-LINKSET[0]>
access <CAT_IDX> 0-31 Assign an access category for a line group

category
441
alarm_ind <ON_OFF> on/off Enable/disable alarm indication for this group

of SS-7
CCI <ON_OFF> on/off Enable link integrity check support in SS-link

group7
CCI frequency <FREQ> 0-127 Set the frequency of link integrity checks for
outgoing calls via SS-Line Group.7
cdpn digit in <ON_OFF> on/off Sending the first digit of a numbercdpn in message
IAM IAM when typing with the overlap method
chan order Set the channel occupation order for a given group
of SS-7
<CHAN_SELECT> up_ring/ up_ring- consecutively forward
down_ring/ down_ring- sequentially back
up_start/ up_start- starting from the first forward
down_start/ down_start– starting from last back
odd_up_ring/ odd_up_ring- sequentially forward odd
odd_down_ring/ odd_down_ring- sequentially back odd
even_up_ring/ even_up_ring- sequentially forward even
even_down_ring even_down_ring- sequentially back even
China <ON_OFF> on/off Enable/disable support mode for Chinese

specification of the OKS-protocol7
combined <ON_OFF> on/off Enable/disable the use of combined

mode
DPC <DPC_ID> 0-16383 Set the code of the oncoming signaling point
– DPC
emergency <ON_OFF> on/off Emergency phasing with one signal link in a linkset
alignment

442
ignore hold <ON_OFF> off/on Ignore receivedCPG with remote hold or

remote retrieval features
init <INIT_MODE> blocked/ Set the type of initialization for the given
group of lines
individual-ublock/
group-unblock/
group reset
interworking <INTERWORK> Set up an indicator of the presence of interaction

with other alarm systems:
no_change/ no_change– broadcast the value without

changes from incoming call
no_encountered/ no_encountered- do not report interaction with a

network that does not support most of the services
provided by the networkISDN
encountered encountered- report interactions some areas

(networkISDN communicates with a network that
does not support most of the services provided by
the networkISDN and not can use functions that
are commonly used)
name <s_name> allowed Set a name for this line group

use letters,
digits, symbol '_',
maximum31 characters
net_ind Set Network ID:
<NET_IND> international/ international– international network
reserved/ reserved- reserve
federal/ federal– federal network
national national– local network
numbering plan 0-15 Selecting a dial plan forLink Set
OPC <OPC_ID> 0-16383 Set the code of your own signaling point for this
group of SS-7
443
primary link set <PRI_LINKSET> 0-15 Selection of the primary group of lines SS-7,
at work in combined mode
release on <ON_OFF> on/off Issue / do not issue disconnect messages

suspend when a message is received suspend
reserve link set <RES_LINKSET> 0-15 Selection of a backup group of lines SS-7
satellite <SATELLITE> override_no_satellite/ Determines the presence of a satellite channel

when working through this group of lines SS-7
transit/
add_one
secondary <SEC_LINKSET> 0-15 Selection of the secondary group of lines

link set OKS-7, at work in combined mode
show Show the configuration of this group of lines SS-

7
ss7timers <index> 0-15 Selecting the profile of OKS-timers7
stream SLC <ON_OFF> off/on Enable/disable the option "Order of streams by

SLC"
TMR <TMR> speech/ Set media requirements (Transmission Medium

Requirement) for this groups of lines OKS-7
64kb_unrestricted/
3.1KHz_audio/
transit
trunk <trunk_index> 0-31 Set the trunk group number for this group of SS-7
444
4.2.2.18 SS-7 timer configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modess7timers
<SS7_TIMERS_INDEX>, where <SS7_TIMERS_INDEX> is the profile number.
SMG-[CONFIG]>ss7timers0 Entering
SS7Timers-mode. SMG-[CONFIG]-
SS7-TIMERS[0]>

set mtp2 T1 <TIMER> 400-500 Set level timer valueMTP2 T1 (x100ms)
set mtp2 T4 normal <TIMER> 75-95 Set level timer valueMTP2 T4 normal
(x100ms)
set mtp2 T4 emergency <TIMER> 4-6 Set level timer valueMTP2 T4 emergency
(х100ms)
set mtp2 T7 normal <TIMER> 5-20 Set level timer valueMTP2 T7 normal
(x100ms)
set mtp3 t2 <TIMER> 7-20 Set level timer valueMTP3 T2 (x100ms)
445
set mtp3-t4 <TIMER> 5-12 Set level timer valueMTP3 T4 (x100ms)
set isup T1 <TIMER> 150-600 Set level timer valueISUP T1 (x100ms)
446
show Show configuration
447
4.2.2.19 Submodule usage configuration mode

To switch to this mode, it is necessary to execute the command in the configuration mode
submodule-usage.
SMG-[CONFIG]> submodule-usage SMG-

[CONFIG]-[SUBMODULE-USAGE]>
set msp <INDEX> 0-5 on/off Enabling/disabling a submoduleSM-VP with

selected index
show Show submodule usage table
4.2.2.20 Modifier table configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modemodifier table
<MODTBL_INDEX>, where <MODTBL_INDEX> is the table number.
SMG-[CONFIG]-TRUNK[0]> modifiers table Entring

TRUNK-Modifiers mode.
SMG-[CONFIG]-TRUNK[0]-MODIFIER>

commands
add Add modifier:
448
<MODIFIER_MASK> mask- MODIFIER_MASK- mask

modifier, modifier
maximum255
symbols,
necessary
enter into
round brackets
"(" And ")"
[CLD_RULE] rule- CLD_RULE- rule

modifier, number conversion
[CLG_RULE] maximumthirty called
symbols,
necessary
enter into
quotes
caller ID request <YES_NO> no/yes Caller ID Request
change aoncat Edit ANI category number for

modifier:
<MODIFIER_INDEX> 0-512 MODIFIER_INDEX -number

modifier
<AONCAT> 0-9/any AONCAT-AON category
change called numbering plan Edit dial plan type modifier for
type called party number:
<MODIFIER_INDEX> 0-8191 MODIFIER_INDEX- number

modifier
<CALLED_NP_TYPE> change; CALLED_NP_TYPE- plan type

numbering
unknown;
isdn/telephony;
national;
private
change called rule Edit Rule

number conversion
callable for modifier
<MODIFIER_INDEX> 0-8191 MODIFIER_INDEX -number

modifier
449
<CALLED_RULE> rule- CALLED_RULE-rule

maximumthirty called subscriber
symbols,
necessary
enter into
quotes
change called type Edit callee number type for

modifier:

modifier
<CALLED_TYPE> NUM_TYPE– subscriber number type:
unknown/ unknown- undefined type

numbers
subscriber/ subscriber- applied when servicing

local calls and incoming long
distance calls
national/ National- used for service of

outgoing
long distance calls, or local
and incoming
long distance calls instead of
subscriber
international/ International- used on MG- lines and

ZSL lines when servicing outgoing
international calls
network_specific network_specific- special network

number
nochange nochange– do not change the number type
change calling category Edit Caller ID category number for

modifier
<MODIFIER_INDEX> 0-8191
<CALLING_CAT_AON> 0-9/nochange
450
change calling numbering Edit dial plan type modifier for

plan type caller number:

modifier
<CALLING_NP_TYPE> nochange/ CALLING_NP_TYPE- plan type

numbering
unknown/
isdn/
telephony/
national/
private
change calling presentation Edit Rule

caller view transformations
<CALLING_PRESENT> allowed/
restricted/
not_available/
spare/
nochange
change calling rule Edit Rule

number conversion
caller for modifier

modifier
<CALLING_RULE> rule- CALLING_RULE- rule

maximumthirty called
symbols,
necessary
enter into
quotes.
451
change calling screen Edit Rule

caller escape indicator
conversions
<CALLING_SCREEN> not_screened/
user_passed/
user_failed/
network/nochange
change calling type Edit caller number type for

modifier:

modifier
<CALLING_TYPE> NUM_TYPE– subscriber number type

numbers

distance calls

outgoing
long distance calls or local
and incoming
subscriber

international calls
network_specific/ network_specific- special network

number
nochange nochange– do not change the number type
change general access-cat Edit general modifier access

category
<ACCESS 0-31/nochange
452
change general numplan Edit general modifier

numbering plan
<NUMPLAN> 0-15/nochange
change mask Edit modifier mask

modifier
<MODIFIER_MASK> mask- MODIFIER_MASK- mask

modifier,
maximum255
symbols,
necessary
enter into
round brackets
"(" And ")".
change mod table Move the modifier to the table with

the specified number
<NEW_MODTBL_INDEX> 0-255
change numtype Edit modifier number type

modifier
<NUM_TYPE> NUM_TYPE– subscriber number type:

numbers

distance calls

outgoing
long distance calls or local
and incoming
subscriber

international calls
453
network_specific/ network_specific- special network

number
any any– any type of room
change type Change subscriber type for

modifier (caller/callied)
<MODIFIER_TYPE> calling/called

to a higher level

commands
remove <MODIFIER_INDEX> 0-8191 Remove the specified modifier
show <MODIFIER_INDEX> 0-8191 Show configuration

modifier
voice channel setup delay <DELAY> 0-7 Vocal path closing delay
4.2.2.21 Network parameter configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modenetwork.
SMG-[CONFIG]> network
Entering network mode.
SMG-[CONFIG]-NETWORK>

commands
add interface Add newVPN/PPTP Client

pptpVPNclient
<LABEL> allowed to use letters, numbers, LABEL- interface name

characters '_', '.', '-', ':', maximum 255
characters
454
<IPADDR> IP address in the format IPADDR– IP address of the PPTP server

AAA.BBB.CCC.DDD
allowed to use letters, numbers,

characters '_', '.', '-', maximum 63
characters
<USER> allowed to use letters, numbers, USER- Username

characters
<PASS> PASS- password
add interface Add a new network interface

tagged
dynamic/static

characters
<VID> 1-4095 VID– VLAN ID

AAA.BBB.CCC.DDD
<NETMASK> netmask in the format NETMASK- network mask

AAA.BBB.CCC.DDD
add interface Add a new network interface

untagged
dynamic/static

characters

AAA.BBB.CCC.DDD
<NETMASK> netmask in the format NETMASK- network mask

AAA.BBB.CCC.DDD
confirm Confirm changed network settings

and settingsVLAN without gateway
reboot. If within a minute the
applied network settings are not
confirmed, their values will

return to their original
455
dhcp server Change to mode

parameter configuration DHCP
servers

to a higher level

commands
ntp Change to mode

configurationNTP
remove <NET_IFACE_IDX> 0-39 Delete the specified interface

interface
rollback cancel changes
set interface Set address for

broadcast broadcast packets for the specified
interface
<NET_IFACE_IDX> 0-39
<BROADCAST> IP address in the format

AAA.BBB.CCC.DDD
set interface Assign priority802.1p for specified

COS interface
<COS> 0-7
set interface Get network settings dynamically

dhcp fromDHCP server for specified
interface
<ON_OFF> on/off
set interface ReceiveDNS server IP address

dhcp_dns dynamically fromDHCP server for
specified interface
456
<ON_OFF> on/off
set interface Don't get gateway settings

dhcp_no_gw dynamically fromDHCP server for
specified interface
<ON_OFF> on/off
set interface Set the default gateway for an

gateway interface
<IPADDR> IP address in the format

AAA.BBB.CCC.DDD
set interface Get settingsNTP

dhcp_ntp dynamically fromDHCP server for
specified interface
<ON_OFF> on/off
set interface Ignore the gateway setting for the

gw_ignore specified interface
<ON_OFF> on/off
set interface Allow signaling exchangeH.323 for

h323 specified interface
<ON_OFF> on/off
set interface AskIP address and netmask for

ipaddr the specified interface

AAA.BBB.CCC.DDD
<NETMASK> netmask in the format

AAA.BBB.CCC.DDD
set interface Set a name for this

network label interface
457
<LABEL> digits, characters '_', '.', '-', ':', maximum 255

characters
set interface Allow messaging RADIUS via

radius interface
<ON_OFF> on/off
set interface Allow TransferRTP packages via

rtp interface
<ON_OFF> on/off
set interface Automatically start the interface at

run_at_startup startup (only for VPN interface)
<STARTUP> on/off
set interface AskPPTP server IP address

serverip

AAA.BBB.CCC.DDD
set interface Allow messagingSIP via interface

signaling
<ON_OFF> on/off
set interface <NET_IFACE_IDX> 0-39 Allow packet transmissionSNMP via

snmp interface
<ON_OFF> on/off
set interface allowssh session via interface

ssh
<ON_OFF> on/off
set interface allowtelnet session via interface

telnet
458
<ON_OFF> on/off
set interface Enable/disable encryption (only for

use_mppe VPN interface)
<ON_OFF> on/off
set interface Set username (only forVPN

username interface)
<USER> allowed to use letters, numbers,

characters
set interface Set a password (only forVPN

user_pass interface)
<PASS> allowed to use letters, numbers,

characters
set interface AppointVID for the interface

VID
<VID> 1-4095
set interface Allow access byweb via interface

web
<ON_OFF> on/off
set settings <IPADDR> IP address in the format AskPrimary DNS IP address

dns primary AAA.BBB.CCC.DDD servers
set settings <IPADDR> IP address in the format AskBackup DNS IP address servers
dns secondary AAA.BBB.CCC.DDD
set settings <NET_IFACE_NAME> The name of the interface whose

gateway_iface gateway will be the primary default
gateway
459
set settings <HOSTNAME> allowed to use letters, numbers, Set hostname

hostname characters '_', '.', '-', maximum 63
characters
set settings <PORT> 1-65535 AskTCP port to access protocol

ssh deviceSSH, by default22
set settings <PORT> 1-65535 AskTCP port to access protocol

telnet devicetelnet, by default23
set settings <ON_OFF> on/off Switch on switch off

use_ip_list use of the whitelistIP addresses
set settings <PORT> 1-65535 AskTCP port for web configurator,

web default80
show interface Show the settings of the

by_index specified network interface
show interface Show list of available network

list interfaces
show settings Show network options
snmp Change to mode

configurationSNMP
ssh restart Process restartSSH
-After the changeIP addresses, netmasks, or when Web Based Management is disabled configurator on
the network interface, you must confirm these settings with the command confirm, otherwise, after
the two-minute timer expires, the configuration will be rolled back to the previous one.
4.2.2.21.1 DHCP server parameter configuration mode

To switch to this mode, it is necessary to execute the command in the network parameters
configuration modedhcp server.
SMG-[CONFIG]-NETWORK> dhcp server

Entering Network mode.
SMG-[CONFIG]-[NETWORK]-[DHCPD]>
460
conflict time <CONFLICT> 10-10000000 Set the time period for whichThe IP address will reserved
in case of detection of a MAC address conflict, not less than
10 Seconds
decline time <DECLINE> 10-10000000 The period of time for whichIP address will be reserved in case
of receiving a rejection message (DHCP decline), not less10
Seconds
dhcpd start RunDHCP server
dhcpd stop StopDHCP server
dns 0/1/2/3 <DNS> IP address in Set addressesDNS servers from the operator's network
format
AAA.BBB.CCC.
DDD
domain <DOMAIN> string length Set the default domain name for DHCP clients
no more31
symbol
enabled <ENABLE> no/yes Run / do not runDHCP server at gateway startup
exit Exit from this configuration submenu to a higher level
gateway <GW> IP address in Set the default router or gateway address assigned
format to clientsDHCP servers
AAA.BBB.CCC.
DDD
interface <IFACE_NAME> line before255 Selecting a network interface forDHCP servers

characters
ipaddr end <IPADDR> IP address in Set the end address of a range of assignableIP addresses
format
AAA.BBB.CCC.
DDD
ipaddr start <IPADDR> IP address in Set the start address of a range of assignableIP addresses
format
AAA.BBB.CCC.
DDD
461
max_lease <MAX_LEASE> 10-10000000 Set maximum device usage timeThe IP address assigned by
sec the DHCP server is not less10 Seconds
maxleases <MAXLEASES> 1-65535 Set limits on the number of leased addresses
min_lease <MIN_LEASE> 10-10000000 Set the minimum device usage time DHCP-assigned IP address
sec for at least 10 seconds
netmask <NETMASK> IP address in Set netmask

format
AAA.BBB.CCC.
DDD
ntp <NTP_SERVER> IP address in Set external server addressNTP to advertise in options42

announce format
external AAA.BBB.CCC.
server DDD
address
ntp <ANNOUNCE_EXT> no/yes Allow external server announcementNTP in option 42

announce
external
server enable
ntp <ANNOUNCE_LOC no/yes Allow local server announcementNTP in option 42

announce AL>
local
offer time <OFFER> 10-10000000 Set the time period for which the requestedIP address will
be reserved, at least10 Seconds
save time <SAVE> 7200-1000000 Set the period of time after which the device will save
0/off information about leased addresses to a file dhcpd.leases
off- do not save the database
show config Show configurationDHCP: usage status, address range,

netmask, default gateway, domain addresses,Wins servers,
the number of leased addresses, request timeouts
462
static_lease Assign static matchesIP and MAC addresses:

add
<name> string lengthNAME- match name no more63
characters
<IPADDR> IP address in IPADDR– IP address

format
AAA.BBB.CCC.
DDD
<MAC> MAC address in MAC– MAC address

format
XX:XX:XX:XX:X
X:XX
static_lease <INDEX> 0-4095 Delete the specified rule in the static match tableIP
remove and MAC addresses
static_lease Show static mapping tableIP and MAC addresses

show
wins <WINS> IP address in InstallIP address of the primary WINS server for use
format DHCP client
AAA.BBB.CCC.
DDD
4.2.2.21.2 PPTP client configuration mode
SMG-[CONFIG]-NETWORK> pptp
Entering PPTP mode.
SMG-[CONFIG]-[NETWORK]-PPTP>
add <USER> line before31 characters Set username

interface
<PASS> line before31 characters Set password
<IP_SRV> IP address in the format AskPPTP server IP address

AAA.BBB.CCC.DDD
<LABEL> line before31 characters Set Label
<MPPE> on/off Enable/Disable Encryption
463
<STARTUP> on/off Run at startup

level
modify Change settingsPPTP

interface
label line before31 characters Change Label
mppe psword on/off Change enable encryption
line before31 characters Change password
server_ip IP address in the format ChangePPTP server IP address

AAA.BBB.CCC.DDD
Change auto startPPTP
on/off
startup username line before31 characters Change username
show Show settingsPPTP
start <IDX_INERFACE> 0-16 RunPPTP interface at the moment time

interface
status <IDX_INERFACE> 0-16 View the status of a given interface

interface
stop <IDX_INERFACE> 0-16 StopPPTP interface to current moment of

interface time
464
4.2.2.21.3 NTP protocol configuration mode

To switch to this mode, it is necessary to execute the command in the network parameters
configuration modentp.
SMG-[CONFIG]-NETWORK> ntp
Entering NTP mode.
SMG-[CONFIG]-[NETWORK]-NTP>

commands
apply no/yes Apply/reject settings NTP

restart ntp no/yes Restart processNTP
set ntp Get SettingsNTP over DHCP from a

dhcp given interface
NET_IFACE_IDX Network index

interface
ON_OFF off/on
set ntp ON_OFF off/on Activate localNTP- server to get time

local from SMG
server
enable
set ntp NET_IFACE_IDX Network index Set the network interface on

local interface which the local server will run
server NTP
interface
set ntp NTP_PERIOD 10-1440 Set time synchronization period

period
465
set ntp NTP line63 characters Set addressNTP server, with

server which will
synchronizeSMG
set ntp ON_OFF off/on ActivationNTP client

usage

config
time zone GMT/GMT+1/GMT-1/ Set timezone

set GMT+2/GMT-2/GMT+3/ relative to UTC
GMT-3/GMT+4/GMT-4/
GMT+5/GMT-5/GMT+6/
GMT-6/GMT+7/GMT-7/
GMT+8/GMT-8/GMT+9/
GMT-9/GMT+10/GMT-10/
GMT+11/GMT-11/GMT+12
Asia Choice of city location in Asia
Europe Choosing a city location in Europe
4.2.2.21.4 SNMP protocol configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modesnmp.
SMG-[CONFIG]-NETWORK> snmp
Entering SNMP mode.
SMG-[CONFIG]-SNMP>
add Add transfer ruleSNMP traps:
<TYPE> trapsink/ TYPE– SNMP message type
trap2sink/
informsink
<IP> IP address in the format IP– IP address of the trap receiver

AAA.BBB.CCC.DDD
466
<COMM> line before31 characters COMM– password contained in traps
<PORT> 1-65535 PORT– Trap receiver UDP port
create user Create a user (assign a login and password for

access)
<LOGIN> line before31 characters
<PASSWD> password from8 to 31

symbol

level
modify Edit transfer ruleSNMP traps (password

community contained in traps)
<IDX> 0-15
<COMM> line before31 characters
modify ip Edit transfer ruleSNMP traps (address ladder

receiver)
<IDX> 0-15
<IP> IP address in the format

AAA.BBB.CCC.DD
modify port Edit transfer ruleSNMP traps (port ladder receiver)
<IDX> 0-15
<PORT> 1-65535
modify type Edit transfer ruleSNMP traps (SNMP message

type)
<IDX> 0-15
467
<TYPE> trapsink/
trap2sink/
informsink
remove <IDX> 0-15 Delete transfer ruleSNMP traps
restart yes/no RestartSNMP client

snmpd
ro <RO> string up to63 Set password for reading parameters

characters
rw <R.W.> string up to63 Set a password for reading and writing

characters parameters
show Show configurationSNMP
syscontact <SYSCONTACT> string up to63 Specify contact information

characters
syslocation <SYSLOC> string up to63 Specify the location of the device

characters
sysname <SYSNAME> string up to63 Specify device name

characters
4.2.2.22 Dial plan configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modenumplan.
SMG-[CONFIG]> numplan
Entering Numbering-plan mode. SMG-
[CONFIG]-[NUMPLAN]>
468
create prefix <IDX_Numplan> 0-15/0-255 Create a prefix in a given dial plan
delete prefix <IDX Prefix> Delete given prefix

to a higher level
prefix Switching to prefix configuration

mode
set active 0-15/0-255 Set number of active dial plans
set domain <IDX> 0-15/0-255 Assign a domain for registration
<DOMAIN> string up to15

characters
set name <IDX> 0-15/0-255 Set name for numbering plan
<name> string up to15

characters
show active count Show number of active dial

plans
show active list Show list of active dial plans
show list Show numbering plan list
show prefixes <IDX> 0-15/0-255 Show numbering plan prefixes with the
specified number
no/yes
469
4.2.2.22.1 Prefix configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modeprefix
<PREFIX_INDEX>,Where<PREFIX_INDEX>– prefix number.
SMG-[CONFIG]-[NUMPLAN]> prefix0
Entering prefix-mode.
SMG-[CONFIG]-[NUMPLAN]-PREFIX[0]>
access <CAT_IDX> 0-31 Assign an access category for a line group

category
access check <ON_OFF> on/off Check/do not check access category
called npi <PFX_CLD_NPI> transit/ Change caller number type (transit - do not
convert)
unknown/
isdn/
telephony/
national/
private
called type Called Party Number Type Conversion (transit

- do not convert)
<PFX_CLD_TYPE> unknown/
subscriber/ subscriber number- applied when servicing

local calls and incoming long distance calls.
Wherein
The transmitted number should look like:
abxxxxx or bxxxxx or xxxxx
national/ national number- used for service of outgoing

long distance calls, or local and incoming long
distance calls instead ofsubscriber. In this case,
the transferred number should look like:
ABCabxxxxx or 2abxxxxx or 10 <international
number>
470
international/ international number- used on MG- lines and

ZSL lines when servicing outgoing international
calls. In this case, the transferred number
should look like: <international number>
(without the prefix "10" access to the
international network)
specific_net/
transit transit- do not convert
command Selecting an action for a service:
<PFX_COMMAND> set/ set– installation of VAS service
clear/ clear– cancellation of VVO service
control control– monitoring the activity of the VAS service
dial mode Set dialing mode by prefix:
<MODE> nochange/ nochange– number of the called subscriber

transmitted in the form in which it was received
from the incoming channel
enblock/ enblock– number of the called subscriber

transmitted in a block
overlap overlap– number of the called subscriber

transmitted with overlap (one digit at a time)
direction Set access type to trunk group or direction:
<PFX_DIRECTION> local/ local– local
emergency/ emergency- call for special services
zone/ zone– zone
vedomst/ vedomst- to a departmental network
toll/ toll– long distance communication
international international– international communication
duration <PFX_DURATION> 0-255 Set dialing duration timer, in seconds

to a higher level
471
getCID <ON_OFF> on/off Enable/Disable RequestCallerID at prefix

routing
ivr <IVR_INDEX> 0-255 Scenario selectionIVR for prefix with type ivr
mask edit Switch to prefix mask editing mode
mask show Show prefix masks
modifiers <MODTBL_INDEX> 0-255 or none Called number modification table applied when
table called changing the numbering plan
modifiers <MODTBL_INDEX> 0-255 or none Calling number modification table applied when
table calling changing the numbering plan
name <s_name> line no more31 Set name/designation for prefix symbol
(allowed
use
letters, numbers and '_')
needCID <ON_OFF> on/off Enable/disable mandatory request for

informationCallerID
new access <CAT_IDX> 0-127 Selecting a new access category for a

category prefix with a typechange-numplan
new numplan <PLAN_IDX> 0-15/0-255 Selecting a new dial plan for a prefix
with typechange-numplan
numplan <PLAN_IDX> 0-15/0-255 Specify which numbering plan the prefix

belongs to
notdial ST <USE_ST> yes/no Don't send/transmit end-of-set character (ST

- in OKS or sending complete in PRI)
operator <OPERATOR> or/and Selecting the logical operator "or / and"
472
pickup group <PICKUP_GROUP_INDEX> 0-254/any Group selection for prefix with typepickupgroup.
Either a specific group is specified, or mode of
selecting any group, which includes the
subscriber's number
service VET service type
<PFX_USER_SERVICE> cf-unconditional/ cf-unconditional– unconditional forwarding
cf-busy/ cf-busy– call forwarding on busy
cf-no-reply/ cf-no-reply- forwarding on no answer
cf-out-of-order/ cf-out-of-order- forwarding to

inaccessibility
call-pickup/ call-pickup– call pickup
conference/ conference- conference with

consecutive collection
clear-all/ clear-all– cancellation of all services
intercom/ intercom– intercom
paging paging– paging
show Show prefix configuration
session time <PFX_SESSION_TIME> 5-64800 Set the time in seconds that limits the
duration of a call that has passed
off - without through the prefix
restrictions
session <PFX_SESSION_TIME_WARN 1-300 An option that includes the issuance of a

warning time > sound signal that warns of the end of a call a
off - no warn specified number of seconds before the end
of the call
trunk <TRUNK> 0-31 Set trunk group or direction number
type Set prefix type:
<PFX_TYPE> trunk/ trunk– access to the trunk group
trunk-direction/ trunk direction– access to trunk

direction
473
change-numplan/ change-numplan - change the numbering plan
modifier/ modifier– prefix type modifier
user_service user_service– DVO service prefix
pickup group/ pickup group- pickup group
ivr ivr– IVR scenario selection
4.2.2.22.2 Prefix mask configuration mode

To switch to this mode, it is necessary to execute the command in the prefix configuration mode mask edit.
SMG-[CONFIG]-PREFIX[0]> mask edit

Entering Prefix-Mask mode.
SMG-[CONFIG]-PREFIX[0]-MASK>
add Add a new mask to the prefix. It is possible to

set the type of mask - for the caller (calling) or
for the called (called), by default the mask type
<PREFIX_MASK> mask-prefix. is always called
maximum255
symbols,
necessary
enter into
round brackets
"(" And ")"
[PFX_MASK_TYPE] calling/called
[called]

level
modify duration Set dialing duration timer
<PREFIX_MASK_INDEX> 0-1024 PREFIX_MASK_INDEX– mask number
<DURATION> 0-255 DURATION- timer
474
modify Ltimer Set "Long Timer"long timer
<LONG_TIMER> 0-255 LONG_TIMER- timer
modify mask Adjust mask
<PREFIX_MASK> mask-prefix. PREFIX_MASK- mask

maximum255
symbols,
necessary
enter into
round brackets
"(" And ")".
modify prefix Move mask to another prefix
<PREFIX_MASK_INDEX> 0-1024 PREFIX_MASK_INDEX– number of the mask, which

needs to be rescheduled
<PFX_INDEX> 0-255 PFX_INDEX- the prefix to which it is transferred

mask
modify stimulator Set "Short Timer"short timer
<SHORT_TIMER> [0-255] DURATION- timer
modify type Set mask type - called or calling number

analysis:
<PREFIX_MASK_INDEX> 0-1024 PREFIX_MASK_INDEX– number of the mask, which

needs to be rescheduled
<PFX_MASK_TYPE> PFX_MASK_TYPE– mask type:
calling/ calling– calling number analysis
called called– called number analysis
remove <PREFIX_MASK_INDEX> 0-1024 Remove mask
show Show mask information
475
4.2.2.23 Pickup group configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modepickupgroup
<pickup-group_INDEX>, Where<pickup-group_INDEX>– interception group number.
SMG-[CONFIG]> pickup-group0
Entering pickup-group-mode. SMG-
[CONFIG]-PICKUP-GROUP[0]>

commands

member add <CALL_NUMBER> symbols(not more then 30): *,#,D,0-9. Or Add a member of the capture group
'none' for blank(delete) number.
member <GROUP_MEMBER [0-19] Remove a member of a pickup group

remove _INDEX>
member set <GROUP_MEMBER [0-19] Set pickup group member

number _INDEX> number
member set Set call group member type

user-type
<GROUP_MEMBER [0-19]
_INDEX>
<USER_TYPE> 0 - 'restricted', 0 - limited
1 – 'ordinary', 1 - normal
2 – 'privileged' 2 - privileged
show Show pickup group settings
476
4.2.2.24 PBX profile configuration mode

To switch to this mode, it is necessary to execute the command in the configuration mode
pbx_profiles.
SMG-[CONFIG]> pbx_profiles
Entering PBX profiles mode. SMG-
[CONFIG]-PBX_PROFILES>
add pbx AddPBX profile with name, number prefix and direct
prefix
<name> line
up to
63
characters
<PREFIX> 1-15
<PFX> 0-255/none

level
flash mode Signal transmission modeflash
<PROFILE_INDEX> 0-31
<FLASH> none/
flash1/
flash2/
flash3
modifier table Set modifier forPBX profile based on analysis of the called
coming subscriber number received from the incoming channel.
called
<MODTBL_INDEX> 0-255/none
477
modifier table Set modifier forPBX profile based on parsing the caller's
coming number received from the incoming channel.
calling
modify pbx <CONNNUM> normal/ Forbid passing a fieldconnected number

connected block
transit number
modify pbx Access to a prefix without analyzing the number of the

direct_pfx calling or called subscriber. Designed to switch all calls
fromSIP subscriber to trunk group regardless of the dialed
<PROFILE_INDEX> 0-31 number (without creating masks in prefixes)
<PFX> 0-255/none
modify pbx Issuing voice message phrases

band
messages
<YES/no>
modify pbx Rename the specified profile

name
<IDX> 0-31
<name> line
up to
63
characters
modify pbx Reassign the station prefix for the specified profile
prefix
<IDX> 0-31
<PREFIX> no more15
numbers or
none
modify pbx <IDX> 0-127 Scheduled Routing Profile Selection

routing_profile
timeout busy <TIMER> 0-31 Timeout for issuing a "busy" signal when using the "call
signal transfer" service
478
timeout cfnr <TIMER> 0-31 Redirect timeout on no response (CFNR)
timeout cfoos <TIMER> 0-31 Forward unreachable timeout (CFOOS)
timeout first- <TIMER> 0-31 Timeout for dialing the first digit when using the "call
digital transfer" service
timeout next- <TIMER> 0-31 Timeout for dialing the next digit when using the "call
digital transfer" service
remove pbx <IDX> 0-31 Delete profilePBX with specified number
show pbx Show list of profilesPBX
479
4.2.2.25 Q.931 timer configuration mode

To switch to this mode, it is necessary to execute the command in the configuration mode q931-
timers.
SMG-[CONFIG]> q931-timers
Entering q931-timers mode. SMG-
[CONFIG]-[q931-T]>

to a higher level
set t301 30-360 Set timer valuet301
t302 10-25 Set timer valuet302
show Show timers configurationQ.931
480
4.2.2.26 RADIUS configuration mode

To switch to this mode, it is necessary to execute the command in the configuration moderadius.
SMG-[CONFIG]> radius
Entering RADIUS mode.
SMG-[CONFIG]-RADIUS>
acct ipaddr InstallAccounting server IP address
<IP_ADDR> IP address in the format IP_ADDR - IP address

AAA.BBB.CCC.DDD
<SRV_IDX> 0-8 SRV_IDX - server number
acct port Set account server port (Accounting)
<PORT> 0-65535 PORT- port number
<SRV_IDX> 0-8 SRV_IDX- server number
acct secret Set a password for the account server (Accounting)
<SECRET> string maximum31 SECRET- password

symbol
acct Set a group for the accounting server

server_gro (Accounting)
up
<SRV_GROUP_ID> 0-3 SRV_GROUP_ID- group number
auth ipaddr InstallAuthorization server IP address
<IP_ADDR> IP address in the format IP_ADDR– IP address

AAA.BBB.CCC.DDD
auth local <AUTH_LOCAL> no/yes Allow local administrator access in case of denial
RADIUS servers
481
auth port Set authorization server port (authorization)
<PORT> 0-65535 PORT- port number
auth secret Set a password for the authorization server

(Authorization)
<SECRET> string maximum31 SECRET - password

symbol
<SRV_IDX> 0-8 SRV_IDX - server number
auth Set group for authorization server

server_gro (Authorization)
up
<SRV_GROUP_ID> 0-3 SRV_GROUP_ID- group number
auth user <AUTH_USER> no/yes User authorizationweb/telnet/ssh over RADIUS
deadtime <DEADTIME> 5-60 Server idle time on failure - the time during which the
server is considered inactive

level
iface <IFACE_NAME> line before255 Set network interface forRADIUS

characters
profile <PROFILE_INDEX> 0-31 Go to configuring profile parameters RADIUS
retries <RETRIES> 2-5 Set the number of attempts to send a request
show Show configuration informationRADIUS- servers

config
482
timeout <TIMEOUT> 3-10 Set the time during which the server response is
expected (x100ms)
voice-msg- <TABLE_INDEX> 0-31 Choice of the answer correspondence tableRADIUS

table and voice messages
4.2.2.26.1 RADIUS profile parameter configuration mode

To switch to this mode, you must in the configuration modeRADIUS execute command
profile<PROFILE_INDEX>,Where<PROFILE_INDEX>– RADIUS profile number.
SMG-[CONFIG]-RADIUS> profile0 Entering

RADIUS-Profile-mode. SMG-[CONFIG]-
RADIUS-PROFILE[0]>
acct answer <ON/OFF> off/on Enable/disable messagingacct Forcall-orig=answer
acct CDPN Set callee number for packagesAccounting

Request:
<CDPN_MODE> CDPN-IN/ CDPN-IN- use caller number subscriber before

modification (received in the package SETUP/
INVITE)
CDPN-OUT CDPN-OUT- use caller number subscriber after

modification
acct CgPN Set caller number for packagesAccounting

Request:
<CGPN_MODE> CgPN-IN/ CdPN-IN -use caller number subscriber before

modification (received in the package SETUP/
INVITE)
CgPN-OUT CDPN-OUT- use caller number subscriber after

modification
acct duration <RADIUS_COUNT_MODE> round-up/ Time rounding options. Round up, down, don't
count mode round-down/ round (pass milliseconds)
not round
acct originate <ON/OFF> off/on Enable/disable messagingacct Forcall-

origin=originate
483
acct restrict Set a limit on outgoing communication when the

server fails (no response from the server):
<RESTRICT> none/ none- allow all calls
zone/ zone- allow calls to special services, to local and

area network
local/ local– allow calls to special services and local net
emergency/ emergency– allow calls only to special

services
restrict-all restrict- bar all calls
acct start <ON_OFF> on/off Enable/Disable Messagingacct. start
acct stop <ON_OFF> on/off Enable/Disable Messagingacct. stop
acct update <ON_OFF> on/off Enable/Disable Messagingacct. update
acct <PERIOD> 10sec/ Message transmission periodacct. update

update_period
20sec/
30sec/
45sec/
1min/
2min/
3min/
5min/
10min/
15min/
30min/
1 hour
acct <ON_OFF> on/off Transfer/not transfer toRADIUS server

unsuccessfull information about unsuccessful calls
acct username Set attributeUser-Name in Accounting-Request packets

answer for the answer side:
484
<USERNAME_MODE> cgpn/ cgpn- use as a value calling party phone

number
ip_or_stream/ ip_or_stream– use IP as the value the address of the

calling party or the number of the stream on which
the incoming connection is made
trunk/ trunk- use name as value trunk on which the

incoming connection is made
cdpn/ cdpn- use phone number called party
initial_cgpn/ initial_cgpn- use unmodified calling party phone

number
initial_cdpn initial_cdpn- use unmodified called party telephone

number
acct username Set attributeUser-Name in Accounting-Request packets

originate for the originate side:

number

trunk/ trunk- use name as value trunk on which the


number

number
auth check on <ON_OFF> on/off Send/not send an authorization request

seize (Authorization) on incoming session

stop dial (Authorization) at the end of dialing

local redir (Authorization) for local forwarding
485
auth digestauth <DIGESTAUTH> rfc5090/ Choice of authorization algorithm for subscribers with
dynamic registration throughRADIUS server. With
rfc5090-no- digest authentication, the password is transmitted as a
challenge/ hash code and cannot be intercepted when traffic is
scanned
draft-sterman
auth <PERMIT> not-allow/ Allow/deny access to special services when a

emergency-on- allow connection is refused from the server
REJ
auth <FRAMED_PROTOCOL> none/ Assign protocol when using packet access for
framed protocol authentication requestsRADIUS
PPP/
none- packet access is not used
SLIP/
ARAP/
Gandalf/
Xylogics/
X75_Sync
486
auth nas port <PORT_TYPE> async/ Assign physical port typeNAS (servers where user is
type authenticated), by default async
sync/
ISDN_Sync/
ISDN_Async_v
120/
ISDN_Async_v
110/
virtual/
PIAFS/
HDLC_Channel
/
x25/
X75/
G3_Fax/
SDSL/
ADSL_CAP/
ADSL_DMT/
IDSL/
Ethernet/
xDSL/
cable/
Wireless/
Wireless_IEEE_
802.1
auth pass <PASSWD> Password not Set attribute valuesUser-Password in

more15 corresponding packageRADIUS Authorization
characters
auth restrict Set a limit on outgoing communication when the

server fails (no response from the server):
<RESTRICT> none/ none- allow all calls
487
zone/ zone- allow calls to special services, to local and

area network
local/ local– allow calls to special services and local net
emergency/ emergency - allow calls only on special

services
restrict-all restrict-all- bar all calls
auth service <SERVICE_TYPE> none/ Set service type, default is not used (none)
type
login/
Framed/
Callback_Login
/
callback_frame
ed/
Outbound/
administrative
/
NAS_Promt/
Authenticate_
Only/
Callback_NAS_
Prompt/
Call_Check/
Callback_Admi
nistrative
auth session Set a maximum call duration limit based on the value
time of one of the attributes passed inAccess-Accept from
serversRADIO:
<SESSION_TIME_MODE> ignore/ ignore- ignore the possibility of restriction

maximum call duration
use_RFC_Sessi use_rfc_session_timeout- as a value timer limits the

on_timeout/ maximum duration of the call to use the attribute
valueSession-Timeout
488
use_CISCO_h3 use_cicso_h323_credit_time- as a value timer limits

23_credit_time the maximum duration of the call to use the attribute
valueSession-Timeout or Cisco VSA attribute h323-
credit-time
auth username Set attribute valueUser-Name in Access –Request

answer packets for the answer side:

number

trunk/ trunk– use the trunk name on which an


number

number
auth username Set attribute valueUser-Name in Access –Request

originate packets for the originate side:
<USERNAME_MODE> cgpn cgpn- use as a value calling party phone

number

trunk/ trunk– use the trunk name on which an


number

number
auth <ON_OFF> on/off Use / do not use individual passwords forSIP

userpasswd subscribers during authorization
modifiers table MODTABLE_MODE default/ Number authorization mode inRADIUS

auth mode
489
restricted restricted– only numbers that fall into modifier table

mask
modifiers table MODTABLE_MODE default/ Number accounting mode inRADIUS

acct mode
restricted restricted– accounting only for numbers that fall into

modifier table mask
modifiers table <MODTBL_INDEX> 0-255/none Set caller number modifier (CdPN) for incoming
incoming connection, as applicable for fieldsCalled-Station-Id,
called xpgk-dst-number-in in messagesRADIUS-Authorization
and RADIUS-Accounting
modifiers table <MODTBL_INDEX> 0-255/none Set caller number modifier (CgPN) for an incoming
incoming connection, applied to fieldsCalling-Station-Id, xpgk-
calling srcnumber-in in RADIUS-Authorization and RADIUS-
Accounting messages
modifiers table <MODTBL_INDEX> 0-255/none Set forwarding number modifier (RedirPN) in the
incoming h323-redirect-number field in the RADIUS-
redirecting Authorization and RADIUS-Accounting messages
modifiers table <MODTBL_INDEX> 0-255/none Set caller number modifier (CdPN) for outgoing
outgoing called connection, as applicable for the fieldxpgk-src-number-
out in RADIUS-Authorization and RADIUS-Accounting
messages
modifiers table <MODTBL_INDEX> 0-255/none Set caller number modifier (CgPN) for outgoing
outgoing connection, applied to the fieldxpgk-dst-number-
calling out to messagesRADIUS-Authorization and
RADIUS-Accounting

level
reset voice- Don't use a match table RADIUS and voice

msg-table messages
490
server_group <SRV_GROUP> 0-3 Server group numberRADIUS, which will used by

profile
set vmt-reply- h323-return- Selecting the attribute by which the message will
attributes code/Reply- be analyzedRADIUS-reject
message
set voice-msg- <TABLE_IDX> [0-31] Choice of the answer correspondence tableRADIUS

table and voice messages
show Show profile configurationRADIUS
use acct <ON_OFF> on/off Allow/deny sendingAccounting queries onRADIUS

server
use auth <ON_OFF> on/off Allow/deny sendingAuthorization- requests for

RADIUS server
use class as <ON_OFF> on/off UseAV-pair Class to transfer category OKS-7

ss7cat subscribers
use eltex-vsa <ON_OFF> on/off Service activationRCM
use full cisco <ON_OFF> on/off Use full valueCisco-VSA for RCM Service
vsa
use porta <ON_OFF> on/off Enable/disable usagePortaBilling

billing
use porta <ON_OFF> on/off Enable/disable usagePortaRouting

routing
use incoming original/ Number selectionCdPN transmitted in the field

called processed xpgk-dst-number-inin RADIUS-Authorization and
RADIUS-Accounting messages
use incoming original/ Number selectionCgPN sent in the xpgk-dstnumber-in field

calling processed in the RADIUS-Authorization and RADIUS-Accounting
messages
use snmp <ON_OFF> on/off SendSNMP trap on every RADIUS hit
use utc time <ON_OFF> on/off Use the time inUTC
491
4.2.2.27 Callback authorization configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modeauth_calls:
SMG1016M-[CONFIG]> auth_calls
Entering Auth Calls mode. SMG1016M-
[CONFIG]-AUTH_CALLS>

commands
add number_pool FIRST_NUMBER phone number Add number pool - starting number
and range
RANGE 1-65535

remove number_pool INDEX 0-63 Delete a number pool by its

index
remove by id number_pool POOL_ID 1-65535 Delete a number pool by its

id
set access category CAT_IDX 0-127 Set access category
set category CATEGORY 0-9 Set AON category
set number_pool INDEX 0-63 Change starting phone

first_number number in number pool
NUMBER phone number
set number_pool range INDEX 0-63 Change range in number pool by its
index
RANGE 1-65535
set by id * POOL_ID 1-65535 Commands work similarly to

commandsset number_pool *, but
identifier
492
set numplan PLAN_IDX 0-15 or none Set numbering plan
Meaningnone - remove plan

numbering
set pbx_profile PROFILE 0-15 or none InstallPBX Profile
Meaningnone- remove PBX

profile
set radius_profile RADIUS_PROFILE 0-31 or no InstallRADIUS profile
Meaningno- remove RADIUS

profile
set select_mode Set the mode for selecting numbers from

the pool
SELECT_MODE sequential/ sequential- sequential
random random– random
show number_pool all Show all configured number pools
show number_pool by_id POOL_ID 1-65534 Show number pool by its id
show number_pool by_index INDEX 0-63 Show number pool by its

index
show user Show virtual subscriber settings
493
4.2.2.28 Configuration mode for call recording settings
-The menu is only available in the software version with a licenseCall-record, more about licenses in the section
Licenses.
To switch to this mode, it is necessary to execute the command in the configuration moderecord.
SMG-[CONFIG]>record
Entering Record-setup mode. SMG-
[CONFIG]-[RECORD]>

to a higher level
ftp enabled REC_FTP no/yes Keep a record of conversations onFTP server
ftp login REC_FTPLOGIN line before63 characters Login access toFTP
ftp mode Upload mode toFTP server

recording
REC_MODE once-a-day/ once a day
once-an-hour/ once an hour
once-an-minute once a minute
ftp passwd REC_PASSWD line before63 characters Access password forFTP
ftp path REC_FTPPATH line before63 characters Path to files onFTP
ftp period day REC_HOUR 0-23 Set the hours and minutes of uploading for the mode
once-a-day
REC_MINUTE 0-59
ftp period hour REC_MINUTE 0-59 Set upload minutes for modeonce-ahour
ftp port REC_FTPPORT 1-65535 PortFTP servers
ftp remove- REC_FTP_REMOVE no/yes Delete records from local storage after
after-upload uploading toFTP
494
ftp server REC_FTPSERVER line before63 characters Address or domain nameFTP servers
set action on stop-recording/remove- Choice of action when the disk is full: stop
full disk oldfiles recording/delete old
set dirname none or text string, Set the name of the directory for recording
maximum63 characters conversation files
set none or text string, Set the name of the directory for recording conversations
dirname_IVR maximum63 characters IVR
set files count FILECOUNT 100-65535 or unlimited Number of record files in one directory
per dir
set files keep KEEP_DAY 0-90 The number of days during which
period day records are stored on local storage
set files keep KEEP_HOUR 0-23 The number of hours during which
period hour records are stored on local storage
set notification <NOTIFY_TYPE> None Notification about the start of recording conversations
voice_message
set path off/mnt/sd[abc][1-7]* Set the path for storing conversation

recording files
495
4.2.2.29 Chat recording mask configuration mode
To enter this mode1required in the mode of configuring call recording settings run commandmask.
SMG-[CONFIG]-[RECORD]> mask
Entering Record-Mask mode. SMG-
[CONFIG]-[RECORD]-MASK>

level
add Add a new entry mask. Options:
REC_MASK_NUMPLAN 0-255 or all numbering plan (all - any PN)
RECORD_MASK String maximum write mask, which must be included in

255 characters parentheses "(" and ")"
REC_MASK_TYPE type of number
all/ any
calling/ defiant
called called
modify RECORD_MASK_INDEX 0-4095 Change the call recording category for the mask
category
CAT_IDX 0-31
modify Change mask number type to specified

direction
RECORD_MASK_INDEX 0-4095
REC_MASK_TYPE all/
calling/
called
modify Change the value of the mask. The mask must be

mask enclosed in parentheses "(" and ")"
RECORD_MASK_INDEX 0-4095
PREFIX_MASK String maximum

255 characters
496
modify Recording start notification

notification
RECORD_MASK_INDEX 0-4095 none- do not notify
NOTIFY_TYPE voice_message- notify; voice message
modify Change numbering plan

numplan
RECORD_MASK_INDEX 0-4095 or none/

voice_message
REC_MASK_NUMPLAN 0-255 or all
remove RECORD_MASK_INDEX 0-4095 Remove mask
show Show all masks
4.2.2.30 Static route configuration mode

To switch to this mode, it is necessary to execute the command in the configuration moderoute.
SMG-[CONFIG]> route
Entering route mode.
SMG-[CONFIG]-ROUTE>

level
route add Add route:
<DESTINATION> IP address in the format DESTINATION– Destination IP address

AAA.BBB.CCC.DDD
<MASK> format mask MASK– netmask for the given IP address

AAA.BBB.CCC.DDD
497
<GATEWAY> gateway in the format GATEWAY– Gateway IP address

AAA.BBB.CCC.DDD
<METRIC> unsigned integer METRIC- metric
<IFACE_NAME> line before255 characters IFACE_NAME– network interface
<ENABLE> disable/enable ENABLE– enable/disable network route
route del Delete route:
<IDX> 0-4095 IDX– network route index
show Show route configuration information
4.2.2.31 Q.850 release reason list configuration

To switch to this mode, it is necessary to execute the command in the configuration moderecord.
SMG1016M-[CONFIG]> release cause list0 Entering

RelCauseList-mode. SMG1016M-[CONFIG]-REL-
CAUSE-LIST[0]>
add cause <CAUSE> 1-127 Add reasonq.850 to table

level
remove <CAUSE> 1-127 Remove reasonq.850 to table

cause
set name <LIST_NAME> letter or number or '_', '.', '-'. Max 63 Set table name
symbols
show Show table configuration
498
4.2.2.32 SIP/SIP-T general settings editing mode

To switch to this mode, it is necessary to execute the command in the configuration modesip
configuration.
SMG-[CONFIG]> sip configuration

Entering SIP/SIP-T/SIP-I/SIP-profile config mode. SMG-[CONFIG]-
SIP(general)>
cause codes <ON_OFF> on/off Set/cancel the specification in accordance with the
KZ requirements of Kazakhstan
dynamic route <PROFILE> 0-63 SIP profile for dynamic routing

profile

level
ignore_RURI no/yes Ignore/don't ignore address inR-URI. Ignore address

information after the "@" delimiter inRequest-URI,
otherwise checking for matching address information
withIP address and hostname of the device, and if they
don't match, the call is rejected
port <PORT> 1-65535 Set the port of the interacting server to which
destination messages will be transmitted and from which
messages will be received
port source <PORT> 1-65535 Set portSMG from which will be transmitted and to which
messages will be received
ringing timeout <RING_TIMER> 10-255 Call answer timeout
499
save_database on/off Save/do not save information about registered

subscribers to the non-volatile memory of the gateway.
Necessary to save the database of registered subscribers
in case the device is rebooted by power or due to a
failure. In case of reboot fromweb or CLI gateway
regardless of this setting will save the current database
to non-volatile memory
show Show general configurationSIP-T
T1 <T1_TIMER> 0-255 InstallSIP timer T1
transportation Set the transport layer protocol used to receive and

transmit messagesSIP:
<TRANSPORT> UDP-only/ UDP-only– use only UDP protocol
UDP-prefer/ UDP preference -receive over UDP and TCP. Sending packages
more1300 bytes over TCP, less than 1300 bytes over UDP
TCP preference/ TCP preference– receive over UDP and TCP. Sending
over TCP. IN if the connection could not be established
TCP, sent via UDP
TCP-only TCP-only– use only TCP protocol
write_timeout <TIMEOUT> 1hour/ Set the period for updating data in the archive
database (from one to sixteen hours)
2hours/
4hours/
6hours/
8hours/
12hours/
16hours
500
4.2.2.33 SIP/SIP-T interface parameter configuration mode

interface <SIPT_INDEX>,Where<SIPT_INDEX>– SIP/SIP-T interface number.
SMG-[CONFIG]> sipinterface0 Entering

SIPT mode.
SMG-[CONFIG]-SIP/SIPT/SIPI-INTERFACE[0]>
access category <CAT_IDX> 0-31 Assign an access category for a line group
alarm indication <on/off> Enabling the indication of an accident about

the unavailability of the interface
category mode <MODE> none Do not transfer the AON category toSIP
category Pass the AON category in the specified field,

none– do not send the ANI category to SIP
cpc
cpc-rus
CCI <on/off> on/off Enable link integrity check support
cdpn default <CDPN> Before30 digits or Default CDPN when calling via trunk
'none' registration interface
cdpn plus sign <YES/NO> no/yes Transfer sign + in type numbers

international. Enabled by default
cgpn replace <YES_NO> no/yes TakeCgPN from parameter "Name User/

Number", when the function is disabled -
the number is usedcgpn, received in an
incoming call
clearchan override <on/off> <on/off> Set optionclear channel override- announce

only the codec on the second arm CLEARMODE
when operating the first arm inclear channel
501
clearchan transit <on/off> <on/off> Set optionclear channel transit- transmitRTP

exactly the same as he came to the first
shoulder (including the time of packaging)
codec disable <CODEC_IDX> 0-5 Disable the selected codec. Codecs are
numbered by priority - from0 (highest) to 5
(lowest)
codec pte Askpayload time
<CODEC_IDX> 0-5
<PTE> 10/20/30/40/50
/60/70/80/90
codec ptype Askpayload type. static value sets the

default value depending on the selected
codec
<CODEC_IDX> 0-5
<PTYPE> 0-127 or static
codec set Set codec to use
<CODEC_IDX> 0-5
<CODEC> G.711-U/
G.711-A/
G.729/
G.723.1_5.3/
G.723.1_6.3
command line <command> Allowed Advanced protocol settingsSIP

symbols: [0-9a-
zA-Z-_.!~*'();:=+
$,%#] always
inside[]. For
clearing use
'none'
diversion use sip-uri <YES_NO> no/yes When the option is enabled, the number in the
header Diversion will always be passed as SIP-URI
502
dname_rpid <YES_NO> no/yes Enable/disable the "Send DisplayName in

Remote-Party-ID Header"
DSCP RTP <DSCP_RTP> 0-255 Set IDDSCP for RTP traffic
DSCP-SIG <DSCP_SIG> 0-255 Set IDDSCP for SIG- traffic
DTMF <DTMF_ALLOW_INBAND> no/yes allowinband DTMF

allow_inband_DTMF
DTMF mime type Set the type of load used for transmissionDTMF
in SIP INFO packets
<MIME_TYPE> application/ application/dtmf – in SIP INFO application/

dtmf dtmf packets (* and # are sent as numbers10
and 11)
application/ application/dtmf-relay – in SIP INFO

dtmf relay application/dtmf-relay packets (* and # are
passed as * and # characters);
DTMF mode <DTMF_m> inband/ ModeDTMF for this interface
RFC2833/
SIP INFO/
SIP NOTIFY
DTMF payload <DTMF_p> 96-127 Set payload type for RFC2833
DTMF payload-equal <DTMF_PT_EQ> (off/on) Enable/disable options "Same RFC2833PT"
duplicate enable <YES_NO> no/yes Enabling duplicate inbox mode INVITE
duplicate primary Specify the address and port of the main

host duplication server
<REM_IPADDR> IP address in
format
AAA.BBB.CCC.D
DD
503
<REM_PORT> 0-65535
duplicate secondary Specify the address and port of the backup server
host of duplication
<REM_IPADDR> IP address in
format
AAA.BBB.CCC.D
DD
<REM_PORT> 0-65535
early media header <early media header> (off/on) Enable SupportP-Early-Media (RFC5009)
econ Set echo cancellation mode:
<CANCELATION> voice/ Voice– echo cancellers enabled (this mode is

set by default)
nlp-off-voice/ nlp-off-voice– echo cancellers included voice

mode, non-linear processor NLP is off. When the
levels transmitting and receiving signals are
very different, a weak signal can be suppressed
by a non-linear processorNLP. For to prevent
this from happening, use this mode of
operation of echo cancellers
modem/ modem– echo cancellers included modem

operation mode (filtering of the constant
component of the signal is turned off,
control by the processorNLP off, comfort
noise generator off)
off Off- do not use echo cancellation

to a higher level
egress_lines <COUNT> 0-65535 Set the number of outgoing lines on the

interfaceSIP
0 - no restrictions
fax detection Set fax detection mode:
<DETECTION> no/ no– do not detect faxes
callee/ callee- only on the receiving side
504
caller/ caller– only on the transmitting side
callee_and_calle callee_and_caller- at the host and

r transmitting party
fax mode <MODE> T38_only/G. Selecting a fax transmission mode

711_only/
T38_and_G.711
fill empty display- FILL_DNAME on/off Filldisplay-name when receiving a call without
name display-name
gain rx <GAIN> - 140 - 60 Set the volume for voice reception,

amplification / attenuation of the level of the
signal received from the interacting gateway and
output to the speaker of the telephone set
connected to the gatewaySMG
gain tx <GAIN> - 140 - 60 Volume for voice transmission, amplification /

attenuation of the level of the signal received from
the microphone of the telephone set connected to
the gatewaySMG and transmitted to the cooperating
gateway
hold mode Call Hold on Press:
flash/ flush
flash/star flush or asterisks
flash/hash flush or "lattices"
flash/star/hash flush, stars or bars
hostname clear Delete the hostname of the communicating

gateway
hostname set <HOSTNAME> line before63 Set the hostname of the communicating
characters gateway
ignore RURI/To diff <IGNORE_RURI_TO_DIFF> off/on When enabled, options will not be transmitted
Redirecting and Original Called numbers in OKS-7 if
there are differences in the fieldsSIP RURI and To
505
inband_signal_ on/off Issue inSIP response 183/SDP for switching

off the vocal tract when receiving fromPRI
with_183_and_sdp messages CALL PROCEEDING or PROGRESS
containing progress indicator=8 (In-band
signal)
ingress_lines <COUNT> 0-65535 Set the number of incoming lines on the

interfaceSIP
0 - no restrictions
jitter adaptation <JT_AP> 1000-65535 Set the period of adaptation of the jitter
period buffer to the lower limit, in milliseconds
jitter adjust mode Set jitter buffer tuning mode:
<JT_AM> non-immediate/ non-immediate- smooth
immediately immediately– instant
jitter deletion mode Set buffer adaptation mode. Determines how

packets will be removed when the buffer
adapts to the lower bound:
<JT_DM> soft/ soft– uses an intelligent circuit selecting

packages to remove that exceed the threshold
hard hard– packets whose delay exceeded

threshold are removed immediately
jitter deletion <JT_DT> 0-500 Set the threshold for immediately removing
threshold packages in milliseconds. If the buffer grows
and the packet delay exceeds this limit, the
packets are immediately deleted
jitter init <JT_INIT> 0-200 Set the initial value of the adaptive jitter buffer
in milliseconds
jittermax <JT_MAX> 0-200 Set the upper bound (maximum size) of the
adaptive jitter buffer in milliseconds
jitter min <JT_MIN> 0-200 Set the size of a fixed or lower bound
(minimum size) of the adaptive jitter buffer
506
jitter mode Jitter buffer mode:
<JT_MODE> adaptive/ adaptive– adaptive
non adaptive non adaptive- fixed
jitter vbd <JT_VBD> 0-200 Set a fixed buffer size for data transfer in
modeVBD
keep-alive enable Enable Direction Availability Control (NAT keep-

alive) (SIP profile only)
keep alive disable Disable Direction Availability ControlNAT keep-

alive (only for SIP- profile)
keep-alive mode Opposite party availability control mode:
<KEEP_ALIVE_MODE> SIP-OPTIONS/ SIP-OPTIONS - availability control directions

through requestsOPTIONS
SIP-NOTIFY/ SIP-NOTIFY - availability control directions

through requestsNOTIFY
UDP-CRLF UDP-CRLF - availability control directions by

sending an empty UDP
keep-alive period <KEEP_ALIVE_PERIOD> 30-3600 Request submission period
lines_mode <LINES_MODE> common/ Line operation mode: combined /

separate separate
local ring back <on/off> on/off Enabling the local CPV option instead early
media
login <LOGIN> line before15 Set name used for authentication

characters
max_active <MAX_ACTIVE> 0-65535 Set the maximum number of active

connections for an interface
507
mode <mode> profile/ Set interface operation mode (SIP- profile

assigned to subscribersSIP)
SIP/
SIP-T/
SIP-I/
SIP-Q
name <s_name> allowed Set a name for the interface

use
letters, numbers,
symbol '_'.
Maximum31
symbol
nat <NAT> enable/disable Switch on switch offNAT
net-interface rtp <IFACE_NAME> line before255 Set network interface forRTP

characters
net interface sig <IFACE_NAME> line before255 Set network interface forSIP
characters
numbering plan <NUMPLAN> 0-15/0-255 Select numbering plan
options <OPTIONS> enable/disable Enable direction availability control via

messages OPTIONS. When directions are not
available the call will be made through the
standby trunk group. Function also
parses the received response to the message

OPTIONS, which allows you not to use
opportunities set in this direction100rel,
replaces and timer if the opposite side does not
support them
options period <OPTIONS_PERIOD> 30-3600 Set the time in seconds after which, if the
direction is unavailable, the call will be made
through the backup trunk group
password <PASSWD> line before15 Set password used for authentication

characters
508
port <PORT> 1-65535 AskUDP port of the communicating

gateway on which it receives signaling
SIP
radius profile <RADIUS_PROFILE> number [0-31] or Assign profileRADIUS for SIP interface profile
'no'
no- do not use the profile for

interface
Re-INVITE on/off Allow processingRe-INVITE with a=sendonly

a=sendonly
redirect 302 <REDIRECTION> on/off Set/cancel the use of call forwarding (

302)
redirect server <REDIRECT_SERV> on/off Redirect/not redirect a call sent to a public

address to a subscriber's private address
without using dial plan routing. Routing is
done
directly to the address from the header contact

302 response received from the server
redirects. You must first set up a redirect.302
(redirection 302 command)
refer <REFER> enable/disable Set/cancel the ability to transfer a call using

REFER
register delay <REGEXP> 500-5000 Minimum interval between sending messages

Register required for protection against heavy
traffic caused by the simultaneous registration
of a large number of subscribers
register expires <REGEXP> 90-64800 Set a time period for re-

registration
regmode <REGMODE> none/ Set registration type on

upstream server
trunk-mode/
user mode
509
reliable_1xx_ <ON_OFF> off/ off-100rel tag passing disabled

response
Support/ When the option is enabledsupportINVITE

request and preliminary class responses1xx will
support plus/ contain tagsupport: 100rel requiring
guaranteed confirmation of preliminary
answers
require/ When the option is enabledrequireINVITE

request and preliminary class responses1xx will
require plus contain tagrequire: 100rel, requiring
guaranteed confirmation of preliminary
answers
RTCP control <RTCP_c> 2-255 Set the number of time intervals (RTCP period),
during which protocol packagesRTCP with
counter sides
RTCP period <RTCP_p> 5-255 Set the time period in seconds after which
the device sends control packets via the
protocolRTCP
RTP loss silence <RTP_TIMEOUT_SILENCE 1-30 Set wait timeoutRTP packages when using the
> silence suppression option. The coefficient
determines how many times the value is
greater thanRTP-loss timeout
RTP loss timeout <RTP_TIMEOUT> 10-300/ Set wait timeoutRTP packages
off
sdp_in_18x <ON_OFF> on/off Always transmitSDP in preliminary answers
sipdomain <SIPDOMAIN> IP address in Set registration domain address

format
AAA.BBB.CCC.D
DD
show config Show interface information
cause profile <SIPCAUSE> [0-63]/ Selecting a Cause Match ProfileQ.850 and sip-
reply
none
510
sms port <PORT> 0-65535 Receive PortSMS over SMPP protocol for
forwarding to the duplication server
src verify <ON_OFF> on/off Control the flow of media traffic fromIP
address and UDP port specified in session
descriptionSDP(on)/ receive traffic from anyIP
address and UDP port (off)
STUN ip <IPADDR> IP address in InstallSTUN server IP address

format
AAA.BBB.CCC.D
DD
STUN period <PERIOD> 10-1800/0 Set interval between requests
STUN port <PORT> 1-65535 Assign portSTUN server to send requests

(default -3478)
STUN use <YES_NO> yes/no Use / do not useSTUN
subnet mask clear Remove subnet mask for incoming calls
subnet mask set <SUBNET> String to63 Set subnet mask for incoming calls
characters in
mask
subnets:
AAA.BBB.CCC.D
DD
subscribers <MAX_FORWARDINGS> 5/10 Maximum number of redirects between

max_forwardings subscribers
t38 bitrate <BITRATE> no limit/ Set the maximum fax transmission

2400/4800/ speed for T.38
7200/9600/120
00/
14400
t38 disable Disable fax reception by protocolT.38
t38 enable Enable fax reception by protocolT.38
511
t38 fillbitremoval <T38_FBR> on/off Enable/disable padding bit removals and

insertions for non-ECM mode data
t38 pte <T38_PTE> 10/20/30/40 Set the packet formation frequency T. 38 in

milliseconds
t38 ratemgmt Set baud rate control method
<T38_RATE_MGMT> localTCF/ local TCF- the method requires tuning

signalTCF generated receiving gateway
locally
transferredTCF transferred TCF- the method requires

tuning signalTCF was transmitted from
transmitter to receiver
t38 redundancy <T38_REDUNDANCY> off/1/2/3 Use redundant frames for error

protection
off- do not use
timer enable <YES_NO> no/yes Use / do not use timersSIP- sessionsRFC4028
timer refresher <refresher> uac/uas Determine the party performing the

session update
timer session Min-SE <MIN_SE> 90-32000 Set the minimum session state monitoring
interval, in seconds. This interval must not
exceed the forced session termination timeout.
timer session expires
timer session expires <EXPIRES> 90-64800 Set a timeout in seconds, after which the
session will be forced to end if the session is not
updated in time
transit sip header YES_NO no/yes Allow transit of headersSIP from this
shoulder to other
trunk <TRUNK> 0-31 Set trunk group number for interface
trusted network <YES_NO> yes/no Selecting the "trusted network" option
512
username <USERNAME> string is not Set User ID

more15
characters
VAD_CNG <ON_OFF> on/off Enable/disable speech activity detector/

comfort noise generator for interface
vbd codec <CODEC> G.711-U, G.711- Codec used for data transmission VBD
A
vbd enable Enable useV.152
vbd disable Turn off useV.152
vbd payload type <VBD_p> Static,96-127 Type of load used forVBD codec
flash processing on/off Process signalflash
4.2.2.34 Configuration mode of parameters of subscriber registration of interfaces

registration.
SMG-[CONFIG]> sip registration Entering

sip-registration mode. SMG-[CONFIG]-SIP-
REGISTRATION>
add one Add a new account
count Show number of created accounts

level
513
remove <INDEX> 0-3000 Delete the specified account
set Set name used for authentication

authname
<INDEX> 0-3000
<name> line no more63

characters
set Set password used for authentication

authpass
<INDEX> 0-3000

characters
set Set registration domain

sipdomain
<INDEX> 0-3000

characters
set Set username for registration

username
<INDEX> 0-3000

characters
show all Display information about all created accounts
show one <ONE_INDEX> 0-3000 Display information about the account with the specified
number
4.2.2.35 SIP subscriber parameters configuration mode

To enter this mode1it is necessary to execute the command in the configuration modesip users.
-1The menu is only available in the software version that supports the SIP registrar.
514
SMG-[CONFIG]> sip users

Entering SIP-Users mode. SMG-
[CONFIG]-SIP-USERS>
add group/user Add new user/group of dynamic

subscribers

level
remove <INDEX> 0-1999/0-2999 Delete this user
savedb Save information about registered subscribers to the

non-volatile memory of the gateway. Necessary to
save the database of registered subscribers in case
the device is rebooted by power or due to a failure. In
case of reboot fromweb or CLI the gateway,
regardless of this setting, will save the current
database to non-volatile memory
service user <INDEX> 0-1999/0-2999 Switch to VAS configuration mode for a given
subscriber
service group <INDEX> 0-63 Switch to VAS configuration mode for a given
group
set Set user authorization mode

authorization
<INDEX> 0-1999/0-2999 INDEX– SIP subscriber index
<AUTHMODE> AUTHMODE– authorization mode:
none/ None- do not ask for authorization
register/ register- ask at registration
515
register_and_invi register_and_invite– ask at registration and outgoing

te calls
set user allow Allow calls without registration

unregistered
<INDEX> 0-1999/0-2999
<ON_OFF> off/on
set user Assign an access category for a given

access subscriber
category
<INDEX> 0-1999/0-2999
<CAT_IDX> 0-31
set user Assign a service mode to a given subscriber

access mode
<INDEX> 0-1999/0-2999
<ACCESS> Off/On/Off_1/
Off_2/Denied_1/
Denied_2/
Denied_3/
Denied_4/
Denied_5/
Denied_6/
Denied_7/
Denied_8/
exclude
set user blf Set monitoring group (subscription groupBLF)

groupID
<INDEX> 0-1999/0-2999
<GROUP_ID> 0-15
set user blf Set the maximum number of subscribers per

subscribers subscriber
<INDEX> 0-1999/0-2999
<BLF_SUBS> 0-200
set user blf Enable serviceblf (busy indication)

usage
516
<INDEX> 0-1999/0-2999
<ON_OFF> off/on
set user Set the ANI category for the specified subscriber
category
<CATEGORY> 0-9 CATEGORY– subscriber's ANI category
set usercliro Enable serviceCLIRO (definition of hidden

numbers)
<INDEX> 0-1999/0-2999
<ON_OFF> off/on
set user Display name usage mode:

display name
rules
<INDEX> 0-1999/0-2999
<USE_DISPLAY_NAME> received_only/ received_only- always use only adopted

name
received_prefer/ received_prefer- if the name is not accepted,

then use customized display name
configured_only configured_only– always use the configured display

name
set user Caller Display Name

display name
value none- clears the display name
<INDEX> 0-1999/0-2999
<DISPLAY_NAME> line40
characters or
none
set user InstallSIP domain for the subscriber

domain
<DOMAIN> line before15 DOMAIN- domain name

characters
517
set user egress Set the number of simultaneous outgoing calls

lines involving the subscriber for the line modeseparate.
Range of allowable values [1;255] or 0 – unlimited
<INDEX> 0-1999/0-2999
<COUNT> 1-255 or 0
set user Set the number of simultaneous incoming calls

ingress lines involving the subscriber for the line modeseparate.
<INDEX> 0-1999/0-2999
<COUNT> 1-255 or 0
set user AskSIP header for intercom

intercom
header
<HEADER> AIAA/ AIAA - Alert-Info: Auto Answer
AI/ AII - Alert-Info: Intercom' for user
AIIAA/ AIIAA - Alert-Info: info=alert-autoanswer
III/ AIII - Alert-Info: info=intercom
AIIRA/ AIIRA - Alert-Info: info=RingAnswer
AIRA/ AIRA - Alert-Info: Ring Answer
AMO/ AMO - Answer-Mode: Auto
CIAA/ CIAA - Call-Info: ;answer-after=0
CIESAA/ CIESAA - Call-Info: =\;answer-after=0
CISSAA CISSAA - Call-Info: \\;answer-after=0
<INDEX> 0-1999/0-2999
set user Intercom mode:

intercom mode
<INDEX> 0-1999/0-2999
<MODE> sendonly/ sendonly– one-sided
sendrecv/ sendrecv– bilateral
ordinary/ ordinary– normal call (without sending headers from

intercom header)
reject reject- do not use intercom
518
set user Set intercom priority

intercom
priority
<INDEX> 0-1999/0-2999
<PRIORITY> 1-5
set user Pause before answering. Used when sending SIP

intercom timer headers with the answer-auto parameter
<INDEX> 0-1999/0-2999
<TIMER> 0-255
set user ipaddr InstallIP address for the specified subscriber
<INDEX> 0-1999/0-2999
<IPADDR> IP address in
format
AAA.BBB.CCC.D
DD
set user lines Set the number of simultaneous calls involving the
subscriber for the line mode common. Range of
allowable values [1;255] or0 - no restrictions
<INDEX> 0-1999/0-2999
<COUNT> 1-255 or 0
set user lines Operation of concurrent call limits

mode
<INDEX> 0-1999/0-2999
<LINES_MODE> common common– general restriction of incoming

and outgoing calls
separate separate– separate restrictions for incoming and

outgoing outgoing calls
set login Set a username and password for this subscriber for
authentication
<INDEX> 0-1999/0-2999
<LOGIN> line before63

characters
<PASSWORD> line before63

characters
set user name Set nameSIP subscriber
519
<INDEX> 0-1999/0-2999
<name> line,
maximum31
symbol
set user no Ignore source port after registration

source-port-
control
<INDEX> 0-1999/0-2999
<ON_OFF> off/on
set user Set number forSIP subscriber

number
<INDEX> 0-1999/0-2999
<NUMBER> number
subscriber
set user Set ANI number for this subscriber

numberAON
<INDEX> 0-1999/0-2999
<NUMBER> number
subscriber
set user Use ANI number when forwarding

numberAON-
for-redirection
<INDEX> 0-1999/0-2999
<NUMBER> number
subscriber
set user Specify an additional subscriber number in a

numberList specific numbering plan.
<INDEX> 0-1999/0-2999
<NUM_IDX> 0-15/0-255
<NUMBER> [number]/none none- clean the room
set user Set numbering plan for subscriber

numplan
<INDEX> 0-1999/0-2999
<PLAN_IDX> 0-15/0-255
set user AskPBX profile for SIP subscriber

pbx_profile
<INDEX> 0-1999/0-2999
<PROFILE> 0-31
520
set user Re- Service activationhold when receiving a re-invite

INVITE with signa=sendonly
a=sendonly
<INDEX> 0-63
<HOLD> off/on
set user Enable/disable redirect processing (message302)

redirection from subscriber
<INDEX> 0-63
<REDIRECTION> off/on
set group Assign an access category for a group of

access subscribers
category
<INDEX> 0-63
<CAT_IDX> 0-31
set group blf Set monitoring group (subscription groupBLF)

groupID
<INDEX> 0-63
<GROUP_ID> 0-15
set group blf Set the maximum number of subscribers per

subscribers subscriber
<INDEX> 0-63
<BLF_SUBS> 0-200
set group blf Allow subscription to events

usage
<INDEX> 0-6
<ON_OFF> off/on
set group Set ANI category for the specified group

category
<INDEX> 0-63 INDEX– SIP subscriber index
<CATEGORY> 0-9 CATEGORY– subscriber's ANI category
set group cliro Enable serviceCLIRO (definition of hidden

numbers)
<INDEX> 0-63
<ON_OFF> off/on
521
set group InstallSIP domain for a group

domain
<INDEX> 0-63 INDEX– SIP subscriber index
<DOMAIN> line before15 DOMAIN- domain name

characters
set group Set the number of simultaneous outgoing calls

egress lines involving a group subscriber for the line mode
separate. Acceptable range values [1;255] or 0 –
unlimited
<INDEX> 0-63
<COUNT> 1-255 or 0
set group Set the number of simultaneous incoming calls

ingress lines involving a group subscriber for the line mode
separate. Acceptable range values [1;255] or 0 –
unlimited
<INDEX> 0-63
<COUNT> 1-255 or 0
set group AskSIP header for intercom:

intercom
header
<HEADER> AIAA/ AIAA - Alert-Info: Auto Answer
AI/ AII - Alert-Info: Intercom' for user
AIIAA/ AIIAA - Alert-Info: info=alert-autoanswer
III/ AIII - Alert-Info: info=intercom
AIIRA/ AIIRA - Alert-Info: info=RingAnswer
AIRA/ AIRA - Alert-Info: Ring Answer
AMO/ AMO - Answer-Mode: Auto
CIAA/ CIAA - Call-Info: ;answer-after=0
CIESAA/ CIESAA - Call-Info: =\;answer-after=0
CISSAA CISSAA - Call-Info: \\;answer-after=0
<INDEX> 0-63
set group Intercom mode:

intercom mode
<INDEX> 0-63
<MODE> sendonly/ sendonly– one-sided
522
sendrecv/ sendrecv– bilateral
ordinary/ ordinary– normal call (without sending headers from

intercom header)
reject reject- do not use intercom
set group Set intercom priority

intercom
priority
<INDEX> 0-63
<PRIORITY> 1-5
set group Pause before answering. Used when sending SIP

intercom timer headers with the answer-auto parameter
<INDEX> 0-63
<TIMER> 0-255
set group lines Set the number of simultaneous calls involving a

group subscriber for the line modecommon.
<INDEX> 0-63
<COUNT> 1-255 or 0
set group lines Concurrent call limit operation mode:

mode
<INDEX> 0-63
<LINES_MODE> common/ common– general restriction of incoming

and outgoing calls
separate separate– separate restrictions for incoming and

outgoing outgoing calls
set group max Set the number of group subscribers
<INDEX> 0-63
<MAX_REG> 0-1999/0-2999
set group Set group name

name
<INDEX> 0-63
<name> line,
maximum31
symbol
523
set group Set group numbering plan

numplan
<INDEX> 0-63
<PLAN_IDX> 0-15/0-255
set group no- Ignore source port after registration

source-port-
control
<INDEX> 0-63
<ON_OFF> off/on
set group AskPBX profile for a group

pbx_profile
<INDEX> 0-63
<PROFILE> 0-31
set group AskGroup SIP Profile

profile
<INDEX> 0-63
<PROFILE> 0-31
set group Re- Service activationhold when receiving a re-invite

INVITE with signa=sendonly
a=sendonly
<INDEX> 0-63
<HOLD> off/on
set group Enable/disable redirect processing (message302)

redirection from subscriber
<INDEX> 0-63
<REDIRECTION> off/on
set group refer Enabling call transfer with a messageREFER
<INDEX> 0-63
<REFER> off/on
show count Show QuantitySIP subscribers
show list Show listSIP subscribers
show user <INDEX> 0-1999/0-2999 Display information aboutSIP subscriber
524
show group <INDEX> 0-63 Display information about the group
4.2.2.35.1 VAS configuration mode of a subscriber

To switch to this mode, you must in the configuration modeSIP subscribers perform commandservice
<USER_INDEX>, WhereUSER_INDEX– SIP subscriber index.
SMG-[CONFIG]-SIP-USERS> service user0 Entering

User-Service modeforuser0 SMG-[CONFIG]-[SIP-
USERS][0]-SERVICE>
attach service Connect VAS for a subscriber

block
detach service Disable VAS for a subscriber

block
set call-pickup <ON_OFF> off/on Activate the "Call Pickup" service

enable
set cfb enable <ON_OFF> off/on Activate the "forwarding on busy" service
set cfb number <ON_OFF> number tothirty Set forward busy number
characters or
none none- disable call forwarding
set sfnr enable <ON_OFF> off/on Activate the "forward on no answer" service
set sfnr number <ON_OFF> number tothirty Set number for forwarding on no answer
characters or
set cfos enable <ON_OFF> off/on Activate the "forwarding on unavailability" service
525
set cfos number <ON_OFF> number tothirty Set number for forwarding on unavailability
characters or
set cfu enable <ON_OFF> off/on Activate the "unconditional forwarding" service
set cfu number <ON_OFF> number tothirty Set number for unconditional forwarding
characters or
set clear-all enable <ON_OFF> off/on Activate the "cancel all services" service
set conf-3way <ON_OFF> off/on Activate the "three-party conference" service. You must first
enable activate the "call hold" service
set conference <ON_OFF> off/on Activate the "conference with sequential collection"
enable service
set ct enable <ON_OFF> off/on Activate the "call transfer" service. You must first activate
the "call hold" service
set hold enable <ON_OFF> off/on Activate the "call hold" service
set intercom <ON_OFF> off/on Subscribe to the intercom service

enable
set <ON_OFF> off/on Connect the service "recording a conversation on demand"

one_touch_record
enable
set password <ON_OFF> off/on Activate the "password change" service

change enable
set password <ON_OFF> off/on Password activation for the "password activation" service. Meaning
restrict access onmakes the password active and restrict communication removed.
active
set password <ON_OFF> off/on Connect the "password activation" service.

restrict access
enable You must first activate the service "restriction of outgoing
communication"
526
set password <ON_OFF> off/on Connect the service "outgoing communication by password".
restrict once
communication"
set password <VALUE> string from4 Set a password for the "restriction of outgoing communication"
value numbers service
set restrict out <ON_OFF> off/on Activate the service "restriction of outgoing communication"
enable
set restrict out Outgoing restriction mode:

value
<ACCESS_M On/ On- everything is allowed

ODE>
Denied_6/ Denied_6- access only to special services
Denied_7/ Denied_7– access only to special services, local and

departmental communications
Denied_8 Denied_8- access only to special services, local,

departmental and zonal communication
show Show current DVO settings
show count Show the number of free DVO blocks
4.2.2.36 VAS configuration mode for a group of subscribers

To switch to this mode, you must in the configuration modeSIP subscribers perform commandservice
group <USER_INDEX>, WhereUSER_INDEX– SIP subscriber index.
SMG-[CONFIG]-SIP-USERS> service group0 Entering UserGroup-

Service modeforuser group0 SMG-[CONFIG]-[SIP-USERS][0]-
GROUP-SERVICE>
Team Parameter Value Action
attach service VAS connection mode for group subscribers - manual

block manual
attach service VAS connection mode for group subscribers - via RADIUS
block radius
527
detach service Disable VDO for a group

block
set call-pickup <ON_OFF> off/on Activate the "Call Pickup" service

enable
set cfb number <ON_OFF> number tothirty Set a call forward on busy number.
characters or
set sfnr enable <ON_OFF> off/on Activate the "forward on no answer" service
set sfnr number <ON_OFF> number tothirty Set number for forwarding on no answer.
characters or
set cfos enable <ON_OFF> off/on Activate the "forwarding on unavailability" service
set cfos number <ON_OFF> number tothirty Set the number for forwarding on unavailability.
characters or
set cfu enable <ON_OFF> off/on Activate the "unconditional forwarding" service
set cfu number <ON_OFF> number tothirty Set the number for unconditional forwarding.
characters or
set clear-all enable <ON_OFF> off/on Activate the "cancel all services" service
set conf-3way <ON_OFF> off/on Activate the "three-party conference" service. You must first
enable activate the "call hold" service
set conference <ON_OFF> off/on Activate the "conference with sequential collection"
enable service
set ct enable <ON_OFF> off/on Activate the "call transfer" service. You must first activate
the "call hold" service
528
set hold enable <ON_OFF> off/on Activate the "call hold" service
set intercom <ON_OFF> off/on Subscribe to the intercom service

enable
set password <ON_OFF> off/on Activate the "password change" service

change enable
set password <ON_OFF> off/on Password activation for the "password activation" service. Meaning on
restrict access makes the password active and the communication restriction is removed.
active
set password <ON_OFF> off/on Connect the "password activation" service.

restrict access
communication"
set password <ON_OFF> off/on Connect the service "outgoing communication by password".
restrict once
communication"
set password value<VALUE> string from4 Set a password for the "restriction of outgoing communication"
numbers service
set restrict out <ON_OFF> off/on Activate the service "restriction of outgoing communication"
enable
set restrict out Outgoing restriction mode:

value
<ACCESS_ On/ On- everything is allowed

MODE>
Denied_6/ Denied_6- access only to special services
Denied_7/ Denied_7– access only to special services, local and

departmental communications
Denied_8 Denied_8- access only to special services, local,

departmental and zonal communication
4.2.2.37 PRI subscriber parameters configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modepri-users.
529
SMG-[CONFIG]> pri-users
Entering SIP-Users mode. SMG-
[CONFIG]-[PRI-USERS]>
? Show list
available commands
add user Create a new subscriber
<NUMBER> subscriber number
<STREAM> flow number E1 0-15
remove by id <USER_ID> Subscriber ID to be deleted Delete subscriber byID
remove by index <INDEX> Subscriber index to be deleted Delete subscriber by

index
service <USER_INDEX> Subscriber index Change to mode

management of the Far East
subscriber
set by id access Assign category

category access bySubscriber ID
<USER_ID> Subscriber ID
<CAT_IDX> 0-127
set by id Assign mode

access_mode services forID
subscriber
<ACCESS> Off/On/Off_1/Off_2/Denied_1/Denied_2/
Denied_3/Denied_4/Denied_5/Denied_6/
Denied_7/Denied_8/Exclude
set by id name Set the name of the subscriber by

hisID
<USER_NAME> string from63 characters
set by id number Set number byID

subscriber
530
<NUMBER> subscriber's telephone number
set by id AskPBX profile by

pbx_profile Subscriber ID
<PROFILE> 0-15
set by id stream Set the flow followed by the

subscriber according to his ID
<STREAM> 0-15
set by index Assign category

access category access by index
subscriber
<INDEX> Subscriber index
<CAT_IDX> 0-127
set by index Assign mode

access_mode services by subscriber
index
<ACCESS> Off/On/Off_1/Off_2/Denied_1/Denied_2/
Denied_3/Denied_4/Denied_5/Denied_6/
Denied_7/Denied_8/Exclude
set by index Set the subscriber's name

name by its index
<USER_NAME> string from63 characters
set by index Set number by subscriber

number index
<NUMBER> subscriber's telephone number
set by index AskPBX profile by

pbx_profile subscriber index
<PROFILE> 0-15
531
set by index Set the stream followed by

stream the subscriber by its index
<STREAM> 0-15
show all Show settings for all PRI

subscribers
show by id <USER_ID> Subscriber ID Show settings

subscriber by hisID
show by index <INDEX> Subscriber index Show settings

subscriber by his index
show count Show general

quantityPRI subscribers
show list users Show a list of allPRI-

subscribers
4.2.2.38 VAS PRI configuration mode

To switch to this mode, you must in the configuration modePRI subscribers fulfill commandservice
<USER_INDEX>, WhereUSER_INDEX– PRI-subscriber index.
SMG-[CONFIG]-[PRI-USERS]> service0 Entering

User-Service modeforuser0 SMG-[CONFIG]-[PRI-
USERS][0]-SERVICE>
attach service Connect VAS for a subscriber

block
detach service Disable VAS for a subscriber

block
532
set cfb number <ON_OFF> number to30 characters or Set a call forward on busy number.
none
none- disable call forwarding
set sfnr enable <ON_OFF> off/on Activate the "forward on no answer"

service
set sfnr number <ON_OFF> number to30 characters or Set number for forwarding on no
none answer.
set cfos enable <ON_OFF> off/on Activate the "forwarding on

unavailability" service
set cfos number <ON_OFF> number to30 characters or Set the number for forwarding on
none unavailability.
set cfu enable <ON_OFF> off/on Activate the "unconditional

forwarding" service
set cfu number <ON_OFF> number to30 characters or Set the number for
none unconditional forwarding.
4.2.2.39 PRI profile configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modepri_profiles SMG-
[CONFIG]> pri_profiles Entering PRI profiles mode. SMG-[CONFIG]-PRI_PROFILES>
add pri_profile <name> Line, maximum63 characters Createpri-profile
533

to a higher level
remove <PROFILE_INDEX> 0-31 Deletepri-profile

pri_profile
set mode <PROFILE_INDEX> 0-31 Set operating modepri- profile

(From first forward/From last
back)
<PROFILE_MODE> start_first_forward/
start_last_backward
set <PROFILE_INDEX> 0-31 Set modifier forPRI- profile, based on

modifiers_table the analysis of the number of the
outgoing called called subscriber transmitted to the
outgoing channel
set <PROFILE_INDEX> 0-31 Set modifier forPRI- profile based on

modifiers_table the analysis of the caller's number
outgoing calling transmitted to the outgoing channel
set <PROFILE_INDEX> 0-31 Set modifier forPRI- profile, based on

modifiers_table the analysis of the original number of
outgoing the called subscriber (original Called
original_called party number), transmitted to the
<MODTBL_INDEX> 0-255/none outgoing channel
set <PROFILE_INDEX> 0-31 Set modifier forPRI- profile based on

modifiers_table the analysis of the forwarding number (
outgoing redirecting number) sent to the
redirecting outgoing channel
set name <PROFILE_INDEX> 0-31 Set namepri-profile
<name> Line, maximum63 characters
show Show settingspri-profiles
534
stream_list add <PROFILE_INDEX> 0-31 Add stream E1(Q.931) in pri-

profile
<STREAM> 1-16
stream_list <PROFILE_INDEX> 0-31 Delete thread E1(Q.931) of pri-

remove profile
<STREAM> 1-4
535
4.2.2.40 SS-7 category conversion configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modess7cat.
SMG-[CONFIG]>ss7cat
Entering SS7-categories mode. SMG-
[CONFIG]-SS7-CAT>
set Set data category:
<CAT_IDX> 0-15 CAT_IDX - category index
<PBX_CAT> 0-255 PBX_CAT - category of caller ID
<SS7_CAT> 0-255 SS7_CAT - category OKS-7
show Show information about the data category OKS-7
536
4.2.2.41 Switch parameter configuration mode

To enter this mode1it is necessary to execute the command in the configuration modeswitch.
-1Only for SMG-1016M. This version of the software is not supported.
SMG-[CONFIG]>switch
Enteringswitchcontrol mode. SMG-
[CONFIG]-[SWITCH]>
802.1q Switching to configuration mode802.1q
apply no/yes Apply mirroring settings

mirroring
settings
apply port no/yes Apply Port Settings

settings
confirm Confirm mirroring settings. If the settings are not confirmed

mirroring within one minute, they will return to the previous values.
settings
confirm port Confirm port settings. If the settings are not confirmed within
settings one minute, they will return to the previous values.
LACP2 Entering parameter configuration modeLACP
QoS_control Entering parameter configuration modeQoS
save mirroring Save mirroring settings without applying
537
save vlan Save settingsVLAN without application
set mirroring Set up port mirroring:
<PORT> GE_PORT0(0)/ PORT– port type
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<name> NAME– port assignment:
src_in/ src_in– source port of incoming packets – copy frames

received from this port (source port)
src_out/ src_out– source ports of outgoing packets – copy frames

transmitted by this port (source port)
dst_in/ dst_in– destination port for incoming packets – port-

destination for copied frames received by selected source
ports
dst_out dst_out– destination port for outgoing packets – port-

destination for copied frames transmitted by selected
source ports
<ACT> on/off
set port <ON_OFF> on/off Enable redundancydual homing

backup
<B_MASTER> GE_PORT0/ B_MASTER - main port

GE_PORT1/
GE_PORT2/
SFP0/SFP1
B_SLAVE GE_PORT0/ B_SLAVE - backup port

GE_PORT1/
GE_PORT2/
SFP0/SFP1
PREMPTION PREEMPTION - enable / disable return to the main port when

it is restored
538
set port AppointVLAN ID for this port

default vlan id
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<VLANID> 0-4095
set port Set the mode for sending packets on this port
egress
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<EGRESS> EGRESS - packet sending mode:
unmodified/ unmodified– packets are transmitted by this port without

changes (i.e. in the same form as received on another port of
the switch)
untagged/ untagged– packets are always transmitted by this port without VLAN
tag
tagged/ tagged– packets are transmitted by this port always with a VLAN
tag
double tag double tag– packets are transmitted on this port with two
tagsVLAN - if the received packet was tagged and with one
tagVLAN - if the received packet was not tagged
set port ieee Set the control mode of received tagged packets for the
mode given port
539
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<IEEE> IEEE - packet control mode:
fallback/ fallback– if a packet with a VLAN tag is received through the

port, for which has entries in the routing table specified in the
entry of this table, otherwise the routing rules specified in "
egress" and "output"
check/ Check– if a packet is received through the port with a VID for
which there is routing table entry802.1q", then it hits under the
routing rules specified in this table entry, even if this port is not a
group member for thisVID. Routing rules specified in "egress"
and "output" for this port are not applied
secure secure– if a packet is received through the port with a VID for
which there is routing table entry802.1q", then it hits under the
routing rules specified in this entry in this table, otherwise it is
discarded. The routing rules specified in "egress" and "output",
for this port is not apply
set port Assign trunkLACP for the specified port

LACP_trunk2
<PORT> CPU/
GE_PORT0/
GE_PORT1/
GE_PORT2/
SFP0/
SFP1
<LACP> 0-4
set port MAC <MACADDR> MAC address in AskMAC address for port
GE_PORT0 format
XX:XX:XX:XX:X
X:XX
540
set port Setting allowed ports for sending packets:

output
<PORT> GE_PORT0/ PORT- configurable port
GE_PORT1/
GE_PORT2/
CPU/
SFP0/
SFP1
<P_DEST> GE_PORT0/ P_DEST– valid shipping ports
GE_PORT1/
GE_PORT2/
CPU/
SFP0/
SFP1
<ENABLE> on/off
set port speed Set port operation mode
<SPEED> 1000M
100M (full-
duplex/
half duplex)
10M(full-
duplex/
half duplex)
auto
<PORT> GE_PORT0/
GE_PORT1/
GE_PORT2
set port vlan Enable/DisableVLAN on this port

enabling
541
<PORT> CPU/
GE_PORT0/
GE_PORT1/
GE_PORT2/
SFP0/
SFP1
<ENABLE> on/off
set port vlan Set override modeVLAN ID for this port to standard
override
<PORT> CPU/
GE_PORT0/
GE_PORT1/
GE_PORT2/
SFP0/
SFP1
<OVER> on/off
show mirror Show port mirroring options

settings
show port Show port settings

settings
542
4.2.2.41.1 802.1q parameter configuration mode

To switch to this mode, you must in the configuration modeswitchrun command
802.1q.
SMG-[CONFIG]-[SWITCH]>802.1q Entering
802.1q_control mode. SMG-[CONFIG]-
[SWITCH]-[802.1q]>
add VTU element Add a new element toVTU table:
<VID> 0-4095 VID - VLAN ID
<PRIO> 0-7 PRIO - 802.1p priority assigned to packets in this VLAN if the
parameterOVERactive (on)
<OVER> on/off OVER – rewrite 802.1p priority for this VLAN (yes/ No)
<GE_PORT0> PORT - actions performed by this port during transmission

package that has the specifiedVID:
<GE_PORT1> unmodified/
- Unmodified– packets are transmitted by this port without
<GE_PORT2>
untagged/ changes
<CPU>
tagged/ - Untagged– packets are always transmitted by this port without
tagVLAN
<SFP0> not_member
- Tagged– packets are always transmitted by this port with VLAN
<SFP1> tag
- Not_member– packets with the specified VID are not

transmitted given port, i.e. port is not a member of this group
VLAN
apply <YES_NO> yes/no Apply settingsVTU
confirm Confirm SettingsVTU. If within one minute settings are not

confirmed, they will revert to the previous values
543
QoS_control Switching to configuration modeQoS
remove VTU <NUMBER> 0-4095 Delete this itemVTU tables

element
save Save settingsVTU without application
set VTU override Overwrite/don't overwrite priority802.1p for this VLAN (yes/no)
<NUMBER> 0-4095
<OVER> on/off
set VTU priority Set Priority802.1p assigned to packets in this VLAN if "set VTU
override" is enabled
<NUMBER> 0-4095
<PRIO> 0-7
set VTU Assign actions to be taken by this port when transmitting

settings_CPU a packet that has the specifiedVID
<NUMBER> 0-4095
<CPU> unmodified/ Unmodified– packets are transmitted by this port without

changes
untagged/ Untagged– packets are always transmitted by this port without VLAN
tag
tagged/ Tagged– packets are always transmitted by this port with VLAN
tag
not_member Not_member– packets with the specified VID are not transmitted to
data port, i.e. port is not a member of this groupVLAN
settings_GE_POR Assign actions to be taken by this port when transmitting

T0 a packet that has the specifiedVID
<NUMBER> 0-4095

changes
tag
544
tag

T1 a packet that has the specifiedVID:
<NUMBER> 0-4095

changes
tag
tag

T2 a packet that has the specifiedVID:
<NUMBER> 0-4095

changes
tag
tag
settings_SFP0 Assign actions to be taken by this port when transmitting

a packet that has the specifiedVID:
<NUMBER> 0-4095

changes
tag
tag
545
settings_SFP1 Assign actions to be taken by this port when transmitting

a packet that has the specifiedVID:
<NUMBER> 0-4095

changes
tag
tag
show list Show list of items inVTU-table
show one <NUMBER> 0-4095 Show information about a given itemVTU tables
show table ShowVTU table
4.2.2.41.2 QoS parameter configuration mode

To switch to this mode, you must in the configuration modeswitchor802.1qexecute commandQoS_control
.
SMG-[CONFIG]-[SWITCH]> QoS_control
Entering QoS_control mode.
SMG-[CONFIG]-[SWITCH]-[QoS]>
802.1q Return to parameter configuration

mode802.1q
apply <YES_NO> yes/no Apply settingsQoS
confirm Confirm SettingsQoS. If within one minute the

settings are not confirmed, they will return to
the previous values
546

save Save settingsQoS without application
set 802.1p_prio_mapping Distribute packets into queues based

on priority802.1p:
<PRIO> 0-7 PRIO - 802.1p priority number
<queue> 0-3 QUEUE - queue number
set default_VLAN_priority Assign priority802.1p untagged packets received

on this port. If the package already has priority
802.1p or IP diffserv priority, this parameter is
not used (default vlan priority will not be apply to
packets containing headerIP, if using one from
modesQoS: DSCP only, DSCP preferred, 802.1p
preferred, and already tagged packages)
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<DEFPRIO> 0-7
set Distribute packets into queues based on

diffserv_prio_mapping priorityIP diffserv:
<NUMBER> *1 NUMBER - IP diffserv priority number
<queue> 0-3 QUEUE - queue number
set egress_limit Enable/disable bandwidth limits for outgoing

traffic from this port
547
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<EGRLIM> on/off
set egress_rate_limit <PORT> GE_PORT0(0)/ Set the bandwidth limit (kbps) for outgoing
traffic from this port
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<EGRRATE> 0-250000
set ingress_limit_mode Set the traffic restriction mode for this port
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<INGRMODE> INGRMODE - restriction mode:
off/ off- no limit
all/ all- all traffic is limited
multi_flood_broad/ multi_flood_broad- limited multicast (multicast)

broadcast (broadcast) and avalanche unicast (
flooded unicast) traffic
548
multi_broad/ multi_broad– limited to multicast and broadcast

traffic
broad broad- only limited broadcast

traffic
set ingress_rate_ Set the bandwidth limit (kbps) of traffic arriving

on this port for zero/first/second/third queue
prio_0/1/2/3
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<INGPRIO> 0-250000
set QoS_mode Set usage modeQoS
<PORT> GE_PORT0(0)/
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<QOSMODE> QOSMODE - usage mode:
DSCP_only/ DSCP only- distribute packets in queues only

based on priorityIP diffserv
802.1p_only/ 802.1p only- distribute packages queues

based on priority only
802.1r
DSCP_preferred/ DSCP preferred- distribute packages queues

based on priorityIP diffserv And802.1p, while in
the case of both priorities in the packet, queuing
is carried out based onIP diffserv
549
802.1p_preferred 802.1p preferred- distribute packages queues

based on priorityIP diffserv And802.1p, while in
the presence of both priorities in the packet,
queuing is carried out based on
802.1r
set remapping_priority Reassign priorities802.1p for tagged

packages
<PORT> GE_PORT0(0)/ PORT - custom port
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/
SFP0(6)/
SFP1(7)
<NUM> 0-7 NUM - current priority value
<REMAP> 0-7 REMAP - new value
show QOS <PORT> GE_PORT0(0)/ Show configuration optionsQoS for this port
GE_PORT1(1)/
GE_PORT2(2)/
CPU(4)/SFP0(6)/
SFP1(7)
show QOS_diffserv Show options for queuing packets based on

priorityIP diffserv
show QOS_priomap Show options for queuing packets based on

priority
802.1p
550
4.2.2.42 syslog parameter configuration mode

To switch to this mode, it is necessary to execute the command in the configuration modesyslog.
SMG-[CONFIG]> syslog
Entering syslog mode.
SMG-[CONFIG]-SYSLOG>
alarm <ALARM> 0-99 Transmit data about accidents with a

given priority level,0- data will not be
transferred
apply yes/no Apply syslog settings
authlog set Set server address for sending messages

syslog as well as mode work
IP IP address in the format

AAA.BBB.CCC.DDD
PORT 1-65535
ONOFF off/on on/off– enable/disable tracking logs
LOCREM local/remote local/remote– if set to remote, then

send logs to the syslog server
authlog show Show current logging settings
calls <CALLS> 0-99 Enable call tracing with the specified

debug level,0 - data will not be
transmitted

h323 <H323> 0-99 Enable alarm tracing

H.323 with debug level set, 0 - data will
not be transferred
551
hw Pass hardware stream data E1 with

debug level set, 0 - data will not be
transferred
<E1> 0-15 E1 – E1 flow number
<HW> 0-99 HW - priority level
ipaddr <IPADDR> IP address in the format Installsyslog server IP address

AAA.BBB.CCC.DDD
isup <ISUP> 0-99 Enable subsystem tracing ISUP with

debug level set, 0 - data will not be
transferred
msp <MSP> 0-99 Enable signal processor resource tracing

MSP with set level of debugging,0 - data
will not be transmitted
port <PORT> 1-65535 Set local port number
Q931 <Q931> 0-99 Enable alarm tracing

Q.931 with debug level set, 0 - data will
not be transferred
radius <RADIUS> 0-99 Enable protocol tracing RADIUS with

debug level set to 0
- data will not be transferred
rtp-create <RTP> 0-99 Enable tracing the creation of bridging

RTP with a given level debugging,0 - data
is not transmitted will
show Show configuration information syslog
sip <SIPT> 0-99 Enable alarm tracing SIP-T with debug

level set, 0 - data will not be transferred
start Enable sending data tosyslog- server
stop Disable sending data tosyslog- server
552
userlog Enable displaying the history of entered

commands
<IPADDR> IP address in the format IPADDR - IP address of the syslog server

AAA.BBB.CCC.DDD
<PORT> 1-65535 PORT - Syslog server port
<MODE> MODE - log verbosity level entered

commands:
off/ off- do not generate log

entered commands
standard/ standard- transmitted in messages

name of the changed parameter
full full- transmitted in messages the name of

the changed parameter and the
parameter value before and after the
change
4.2.2.43 Voice message file management configuration mode

To switch to this configuration mode, it is necessary to execute the command in the configuration mode
user-voice-files.
SMG-[CONFIG]> user-voice-files Entering User

voice-files setup mode. SMG-[CONFIG]-
USER_VOICE_FILES>

553
remove <FILE_TYPE> trunk_busy/ Delete user file with given type
trunk_error/
number_fail/
access_denied_temp/
service_restricted/
access_restricted/
access_unpaid
/user_unallocated
/user_changing/
music_on_hold/
number_changed/
conf_greeting
set <FILE_TYPE> trunk_busy/ Enable use

custom file with a given type
trunk_error/
number_fail/
access_denied_temp/
service_restricted/
access_restricted/
access_unpaid
/user_unallocated
/user_changing/
music_on_hold/
number_changed/
conf_greeting
show files Show downloaded

user files
show usage Show Usage

custom files
554
4.2.2.44 IVR function configuration mode

To switch to this trunk group configuration mode, execute the command in the configuration
modeivr.
SMG-[CONFIG]> ivr
Entering IVR-setup mode SMG-
[CONFIG]-IVR>

commands
add scenario Add a new script file IVR
delete scenario Delete script fileIVR
download scenario <SRC_PATH_AND_FILE_NAME> Download script from devicetftp

<DST_FILE_NAME> <SERVER_IP>

remove scenario Index [0-255] Delete scriptIVR
set scenario filename Index [0-255] Set script file nameIVR
set scenario name Index [0-255] Set script nameIVR
set scenario path default or /mnt/sd[abc][1-7] Set path to store scriptsIVR
show list scenarios Show all script files IVR
show path scenario Show path to store script files

IVR
555
show scenario Index [0-255] Show scriptIVR
4.2.2.45 Trunk group configuration mode

To switch to the trunk group configuration mode, execute the command in the configuration modetrunk
group <TRUNK_INDEX>,Where<TRUNK_INDEX>– trunk group number.
SMG-[CONFIG]> trunk group0

Entering trunk-mode.
SMG-[CONFIG]-TRUNK[0]>

commands
channel add CHAN_INDEX 0-31 Add to trunk groupE1- channels the

channel of the selected E1 stream
channel order CHAN_ORDER successive_forward/ Select the order of occupation of

channels on trunk groupsE1
successive_backward/ channels orLinkset line
start_first_forward/
start_last_backward
channel remove CHAN_INDEX 0-31 Remove from trunk groupE1-

channels E1 flow channel
cps max <CPS_MAX> 0-255 limit valueCPS, which can be

passed through the trunk group
cps warn <CPS_WARN> 0-255 Emergency valueCPS, at exceeding

which a warning will be issued in the
accident log
destination Assign a trunk group to an interface

Q931, OKS-7, SIP-T, individual flow
channelsE1 or to separate streams
of the OKS-linkset7
556
<TG_ENTRY> Q.931/ TG_ENTRY - interface type
SS7/
SIPT/
E1-channels/
Linkset line
<ENTRY_INDEX> unsigned integer ENTRY_INDEX - object index (flow

number with signaling Q931/
OKS-7, line groups, interfaceSIP-
T, linkset OKS-7)
direct prefix <IDX> 0-255/none Set direct routing of calls from the
given trunk group to the specified
prefix, without parsing the calling
and called subscriber numbers
disable all <YES_NO> yes/no Deny/allow outgoing and incoming

calls for this trunk group
disable in Deny incoming calls for this trunk

group
disable out Deny outgoing calls for this trunk

group


commands
linkset line add <LINE_INDEX> 0-15 Adding to a trunk group Linkset-

Line flow from E1 selected linkset
OKS-7
linkset-line remove <LINE_INDEX> 0-15 Removing from a trunk group

Linkset-Line flow E1
557
local <YES_NO> yes/no Set / do not set subscribers of this

direction for SORM control with
the type and sign of the number
"subscriber of this station"
modifiers table incoming <MODTBL_INDEX> 0-255/none Set trunk group modifier for
called modifications based on analysis of
the called party number received
from the incoming channel
modifiers table incoming <MODTBL_INDEX> 0-255/none Set trunk group modifier for
calling modifications based on parsing
the caller's number,
transmitted to the outgoing channel
modifiers table outgoing <MODTBL_INDEX> 0-255/none Set trunk group modifier for
called modifications based on called
party number parsing,
transmitted to the outgoing channel
original modifications based on parsing the
original called party number sent to
the outgoing channel
modifiers table incoming <MODTBL_INDEX> 0-255/none Set the trunk group modifier for
redirecting modifications based on the analysis
of the number of the forwarding
subscriber transmitted to the
outgoing channel
calling modifications based on parsing the
caller's number received from the
incoming channel
name <s_name> allowed to use Set trunk group name

letters, numbers, symbol '_'.
Maximum31 characters
558
radius profile incoming <IDX> 0-31/no Set profileRADIUS by incoming

communication
radius profile outgoing <IDX> 0-31/no Set profileRADIUS by outgoing

communication
recover on egress failure <RECOVER> no/yes Restore calls after outgoing leg
failure
reserve <TG_RSV_IDX> 0-31 Set standby trunk group

number

trunk group
4.2.2.46 Trunk directions configuration mode

To switch to the mode of configuring trunk directions, it is necessary to execute the command in the
configuration modetrunk direction <DIRECTION_INDEX>, Where<DIRECTION_INDEX>- trunk group
number.
SMG-[CONFIG]> trunk direction0 Entering

trunk-mode.
SMG-[CONFIG]-TRUNK_DIRECTION[0]>

commands


commands
list add <TD_TRUNK> 0-63 Add a trunk group with the given
index to the direction
list remove <TD_TRUNK> 0-63 Remove trunk group with given index
from direction
559
mode Set the method for selecting trunk

groups in the direction:
successive_forward/ Consistently forward
successive_backward/ Sequential back
first_forward/ Starting from the first forward
last_backward Starting from the last back
name <s_name> String, max.63 Set trunk direction name

symbol
show Show Trunk Direction Settings
4.2.3 Configuring the SMG-2016/3016 switch
4.2.3.1 Switch structure
560
Drawing49 - Switch Structure

SwitchSMG-2016 has interfaces:
• front port– external ethernet ports of the switch, which are displayed on the front panel.
Accepted values:0 - 3.
• ports 0 .. 1 – copper ports;
• ports 2 .. 3 – optical and copper combo ports.
• port channel– aggregation groups LAG front-port interfaces of the switch, are used in case of
association of severalfront-port to LACP group. Accepted values:14.
• cpu port– internal switch port for SMG-2016 management. Accepted

values:0.
• host port– internal ports of the SMG-2016 switch, designed for communication with the processor (CPU) of
the SMG-2016.
• host channel– LAG host-channel aggregation group of switch interfaces, this group is always active.
Accepted value:1.
• sm port– internal ports of the SMG-2016 switch intended for communication with SM-VP
submodules.
SwitchSMG-3016 has interfaces:
• front port– external ethernet ports of the switch, which are displayed on the front panel.
Accepted values:14.
• ports 1 .. 2 – copper ports;
• ports 3 .. 4 – optical and copper combo ports.
• port channel– aggregation groups LAG front-port interfaces of the switch, are used in case of
association of severalfront-port to LACP group. Accepted values:14.
• cpu port– internal switch port for SMG-3016 management. Accepted

values:1.
561
• host port– internal ports of the SMG-3016 switch, designed for communication with the processor
(CPU) SMG-3016.
Accepted values:12.
• host channel– LAG host-channel aggregation group of switch interfaces, this group is always active.
Accepted value:1.
• sm port– internal ports of the SMG-3016 switch intended for communication with SM-VP
submodules.
Accepted values:16.
When working with a switch, the value is usedunit number, equal to 1.
4.2.3.2 SMG-2016/3016 Switch Interface Control Commands
-ForSMG-3016 must take into account that the port numbering has been changed, initial frontport = 1.
4.2.3.2.1 interface
This command allows you to switch to the switch interface configuration mode
SMG-2016/3016.
Syntax:
interface <interface>
<number> Options:
<interface> – interface type:
• front-port – external interfaces of the switch;
• host-channel – LAG host-channel aggregation groups of switch interfaces;
• port-channel – LAG aggregation groups of external interfaces of the switch.
<number> – port number:
• for front-port: <unit/port>, where:
• unit – SMG-2016/3016 module number, always takes the value 1;
• port – port number takes the values [0 .. 3] (or 1 .. 3 for SMG-3016);
• for host-channel: 1;
• for port-channel: [1 .. 4].
Parameter <number> can be set to all to configure all ports of the same type at once interfaces.
4.2.3.2.2 shutdown
This command disables the configurable interface.
The use of a negative form of the command enables the configurable interface. Syntax:
[no] shutdown
Options:
The command does not contain any arguments.
562
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> shutdown
The configurable interface is disabled.
4.2.3.2.3 bridging to
This command sets the permission to transfer traffic between interfaces.
The use of a negative form of the command disables the transfer of traffic between interfaces.
Syntax:
[no] bridging to <interface>
<range> Options:
• cpu-port;
• front-port – external uplink interfaces;
• host-channel;
• host-port;
• port-channel—aggregation groups of LAG uplink interfaces;
• sm port.
<range> – number of port(s) with which traffic exchange is allowed:
• for cpu-port: <1/0>;
• unit – module number, takes the value [1],
• port – port number, takes the values [0 .. 3];
• for host-channel: [1];
• for host-port: <unit/port>, where:
• for port-channel: [0 .. 4];
• for sm-port: [0 .. 15]: <unit/port>, where:
• port – port number, takes values [0 .. 5].
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> bridging to front-port all
4.2.3.2.4 flow control

This command enables/disables the data flow control mechanism (flow control) on the configured interface.
Mechanismflow controlto compensate for differences in transmitter and receiver speeds. If the amount of
traffic exceeds a certain level, the receiver will send frames informing the transmitter to reduce the amount
of traffic in order to reduce the number of lost packets. To implement this mechanism, it is necessary that
the remote device also supports this function.
563
Syntax:
flow control <act>
Options:
<act> is the action to be assigned:
• on – enable;
• off – disable.
Default value:
off
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> flow control on
4.2.3.2.5 frame-types
The command allows you to assign certain rules for receiving packets for an interface:
• accept tagged and untagged packets;
• only accept packets with a VLAN tag.
Syntax:
frame-types <act>
Options:
<act> is the action to be assigned:
• all – accept tagged and untagged packets;

• tagged—only accept packets with a VLAN tag.
Default value:
All packages (tagged and untagged) are accepted Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> frame-types all
The configurable ports are allowed to receive untagged traffic.
4.2.3.2.6 speed
This command sets the speed value for the configured interface.
The command sets the following modes:10 Mbps, 100 Mbps, 1000 Mbps. When setting 10 Mbps,100 Mbps,
you must specify the transceiver operation mode: duplex, half duplex.
Syntax:
speed <rate> [<mode>]
Options:
<rate> – rate value: 10 M; 100M; 1000 Mbps; 10 Gbps; <mode> –
transceiver operation mode:
• full-duplex – duplex;
564
• half-duplex—half duplex.
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> speed 10M full duplex
Interface speed set10 Mbps duplex.
4.2.3.2.7 speed auto

This command sets the speed value for the configured interface automatically.
Syntax:
speed auto
Options:
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> speed auto
The speed for the port will be set automatically.
4.2.3.2.8 show interface configuration

This command is used to view the configuration of the switch interfacesSMG-2016. Syntax:
show interfaces configuration <interface>

<number> Options:
• host-channel;
• host-port;
• port-channel – LAG aggregation groups of external uplink interfaces;
• sm port.
• all – all ports of the selected interface;
• for front port: <unit/port>, where:
• unit – module number, takes the values [1],
• port – port number, takes the values [0 .. 3].
• for host port:
• for sm-port: [0 .. 15]:
565
Example:
SMG2016-[CONFIG]-[SWITCH]> show interfaces configuration front-port all Port

Duplex Speed Neg flow Admin
control State
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - front port
1/0 Full 10Mbps Enabled Off Up
front port 1/1 Full 10Mbps Disabled Off Up
front port 1/2 Full 10Mbps Enabled Off Up
front port 1/3 Full 10Mbps Enabled Off Up
SMG2016-[CONFIG]-[SWITCH]>
4.2.3.2.9 show interface status

This command allows you to view information about the state of an interface, a group of interfaces.
Syntax
show interfaces status <interface>
<number> Options:
• host-channel;
• host-port;
• sm port.
• unit – module number, takes the values [1];
• for host port:
• unit – module number, takes the value [1];
• for sm-port:
Example:
SMG2016-[CONFIG]-[SWITCH]> show interfaces status front-port all Port

media Duplex Speed Neg flow Link Back
control State Pressure
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - front-port
1/0 N/A N/A N/A N/A N/A Down N/A
front port 1/1 copper Full 10Mbps Disabled Off Up Disabled
front port 1/2 copper Full 100Mbps Enabled Off Up Disabled
front port 1/3 N/A N/A N/A N/A N/A Down N/A
SMG2016-[CONFIG]-[SWITCH]>
566
4.2.3.2.10 show interface counters

This command allows you to view the counters of an interface or a group of interfaces.
Syntax:
show interfaces counters <interface>
<number> Options:
• cpu-port;
• host-channel;
• host-port;
• port-channel—aggregation groups of LAG uplink interfaces;
• sm port.
<range> – number of port(s) with which traffic exchange is allowed:
• for cpu-port: <1/0>, where:
• port – number, the port takes the values [0 .. 3].
• for host port:
• for sm-port:
Example:
SMG2016-[CONFIG]-[SWITCH]> show interfaces counters front-port all
MAC MIB counters receive

~~~~~~~~~~~~~~~~~~~~~~~ Port
UC recv MC recv BC recv Octetsrecv
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - front-port
1/0 front port1/1 front port1/2 front 0 port1/3 0 0 0
436940 6297 9289 65685375
1422764 6077 41999 210652881
0 0 0 0
MAC MIB counters sent

~~~~~~~~~~~~~~~~~~~~~
port UC sent MC sent BC sent Octets sent
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - front-port
1/0 front port1/1 front port1/20front port1/3 0 0 0
455819 6087 42006 96955149
148842 6280 9296 17450454
0 0 0 0
567
4.2.3.3 Commands for configuring aggregation groups
4.2.3.3.1 channel-group
This command adds interfacesFRONT-PORT to the aggregation group.
Using a negative form of the command (no) removes FRONT-PORT interfaces from the group
aggregation.
Syntax:
channel-group <id> [force]
no channel-group
Options:
<id> – sequence number of the aggregation group to which the port will be added, takes the values [1 .. 4];
• [force] – optional parameter, takes the value:
• force - means to be compatible with the rest of the group.
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> channel-group1
All portsuplink are grouped 1.
4.2.3.3.2 lacp mode

This command allows you to select the link aggregation mode:
Passive - in this mode, the switch does not initiate the creation of a logical link, but considers incoming
packetsLACP;
Active - in this mode, it is necessary to form an aggregated communication line and initiate
agreement.
An association of communication lines is formed if the other side operates in the modesLACP active or
passive.
Using a negative form of the command (no) sets the link aggregation mode by by default.
Syntax:
lacp mode <name>
no lacp mode
Options:
<name> - mode:
• active;
• passive.
Default value:
active
568
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> lacp mode active
Link aggregation mode is enabled on configurable portsactive".
4.2.3.3.3 mode
This command sets the link aggregation mode:
• use the LACP link aggregation protocol;
• do not use link aggregation.
Syntax:
mode<act>
Options:
<act> - mode:
• lacp – use LACP;
• static - do not use the link aggregation protocol.
Example:
SMG2016-[CONFIG]-[SWITCH]>interfaceport channel1 SMG2016-

[CONFIG]-[SWITCH]-[if]> mode lacp
Link aggregation mode is enabled on the configured interface.
4.2.3.3.4 lacp port-priority

This command sets the priority for the configured port. The priority is set in the range [1..65535]. A priority
with a value of 1 is considered the highest. Use of negative command forms (no) sets the default priority
value.
Syntax:
lacp port-priority <priority>
no lacp port-priority
Options:
<priority> – priority for this port takes the values [0 .. 65535]. Default value:
all ports are set to priority32768 Command

mode:
INTERFACE FRONT-PORT
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> lacp port-priority256
Configurable ports are set to port priority256.
569
4.2.3.3.5 lacp rate

This command sets the interval for transmitting protocol control packets.LACPDU. Using a negative form
of the command (no) sets the control transmission interval protocol packagesLACPDU by default.
Syntax:
lacp rate <rate>
no lacp rate
Options:
<rate> – transmission interval:
• fast – transmission interval 1 second;

• slow – transmission interval is 30 seconds.
Default value:
1 second (fast)
Command mode:
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> lacp rate slow
Control packet transmission interval setLACPDU in 30 seconds.
4.2.3.4 Commands for managing the VLAN interfaces of the SMG-2016 board
4.2.3.4.1 pvid
This command sets the valueThe default VID for packets received on the port.
When an untagged package or a package with the valueVID in VLAN tag equal to 0 for a packet value is
assignedVID equal to PVID.
Syntax:
pvid <num>
Options:
<num> – VLAN identification number of the port is set in the range [1 .. 4094]. Default value:
PVID = 1
Command mode:
INTERFACE PORT-CHANNEL
570
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> pvid5
Configurable port assignedPVID 5.
4.2.3.5 STP/RSTP Configuration Commands
4.2.3.5.1 spanning-tree enable

With this command, the functionSTP is allowed on the configured interface. Using a
negative form of the command (no) disables STP on the interface. Syntax:
[no] spanning-tree
enable Options:
The command does not contain any
arguments. Command mode:
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> spanning-tree enable
FunctionSTP is enabled for all front-ports.
4.2.3.5.2 spanning-tree pathcost

This command sets the value of the path for the configurable interface for the protocol to work.STP.
Using a negative form of the command (no) sets the value of the path value by by default.
The default is set to0. Syntax:
spanning-tree pathcost <pathcost> no
spanning-tree pathcost
Options:
<pathcost> – path value, takes values [0..200000000]. Default
value:
path value value =0
Command mode:
571
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> spanning-tree pathcost1
Path value set1.
4.2.3.5.3 spanning tree priority

This command sets the priority for the configurable port for the protocol to work.STP.
Using a negative form of the command (no) sets the default priority for STP protocol operation. The
default value is 128.
Syntax:
spanning-tree priority <priority>
no spanning-tree priority
Options:
<priority> – priority, takes values multiple of 16 [0, 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208,
224, 240].
Default value:
128
Command mode:
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> spanning-tree priority144
Priority set144.
4.2.3.5.4 spanning-tree admin-edge

This command sets the connection type asedge link towards the host. In this case, when raising the link
on the interface automatically allows data transfer.
Using a negative form of the command (no) restores the default values. Syntax:
[no] spanning-tree admin-

edge Options:
arguments. Default value:
off
Command mode:
572
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> spanning-tree admin-edge
Connection type enabled for configurable portedge link.
4.2.3.5.5 spanning-tree admin-p2p

This command sets the connection definition typep2p.
Using a negative form of the command (no) sets the p2p connection definition type to by default.
Syntax:
spanning-tree admin-p2p <type>
no spanning-tree admin-p2p
Options:
<type> – connection definition type:
• auto – determination is based on BPDU;
• force-false – force the link to be established as non-p2p;
• force-true - force the link to be set as p2p.
Default value:
connection type definitionp2p happens based on BPDU Command
mode:
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> spanning-tree admin-p2p auto
For a configurable port, specifying the connection typep2p happens based on BPDU.
4.2.3.5.6 spanning-tree auto-edge

This command sets the automatic detection of the bridge on the configured interface.
Using a negative form of the command (no) disables automatic bridge detection on configurable interface.
By default, the automatic bridge detection feature is enabled. Syntax:
[no] spanning-tree auto-

edge Options:
573
Example:
SMG2016-[CONFIG]-[SWITCH]-[if]> spanning-tree auto-edge
The "automatic bridge detection" function is enabled.
4.2.3.6 MAC table setting commands
4.2.3.6.1 mac-address-table aging-time

This command sets the lifetimeThe MAC addresses in the table are global.
Using a negative form of the command (no) sets the MAC address lifetime by by default.
Syntax:
[no] mac-address-table aging time <aging time> no
mac-address-table aging time
Options:
<aging time> – MAC address lifetime, takes values of [10 .. 630] seconds. Default
value:
300 seconds
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> mac-address-table aging-time100
4.2.3.6.2 show mac address-table count

This command allows you to view the number of MAC address entries on allfront port interfaces
port-channel interfaces, slot-channel interfaces.
Syntax:
show mac address-table count
Options:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> show mac address-table count 17valid mac

entries
574
4.2.3.6.3 show mac address-table include/exclude interface

This command allows you to view the MAC address table according to the specified interface.
Syntax:
show mac address-table include/exclude interface <interface>
<number> Options:
• host-channel;
Command mode:
CONFIG SWITCH
4.2.3.7 Commands for configuring port mirroring
4.2.3.7.1 mirror <rx|tx> interface

This command enables the mirroring operation on the switch ports for incoming/outgoing traffic.
Port mirroring allows you to copy traffic from one port to another for external analysis.
Using a negative form of the command (no) disables the mirroring operation. Syntax:
[no] mirror <rx|tx> interface <port> <num>

Options:
<rx|tx> – traffic type:
• rx – incoming;
• tx – outgoing.
<port> – interface type:
• host-channel – interfaces for connecting interface modules;
• host-port;
• port-channel – logical combination of external uplink interfaces;
• sm port.
<num> – ordinal number of the port of the specified group (you can specify several ports by enumerating
through "," or a range of ports through "-"):
575
• "all" – all ports of this group;
• host-channel;
• host-port;
• sm port.
• for host port:
• for sm-port:
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> mirror rxinterfacefront port1/3
For incoming traffic arriving on interfacesfront-port 1/3, operation enabled port mirroring. Traffic is
copied from portsslot-port to the sniffer port set command "mirror rx analyzer.
4.2.3.7.2 mirror <rx|tx> analyzer

This command allows you to set the port on which packets will be duplicated to analyze incoming /
outgoing traffic from the ports set by the commandmirror rx port/ mirror tx port.
Using a negative form of the command (no) disables parsing of transmitted incoming/ outgoing traffic.
Syntax:
[no] mirror <rx|tx> analyzer <interface> <port>
Options:
<interface> – interface type. Only front-port, port-channel interfaces can be used as an analyzer port;
<port> – ordinal number of the port of the front-port group in the <unit/port> format, where:
576
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> mirror rx analyzer front-port1/2
Data for external analysis will be duplicated onfront-port 1/2 from the port(s) on which/ which the
"mirroring incoming traffic" option is set.
4.2.3.7.3 mirror add-tag

This command adds a label802.1q to the analyzed traffic. Label (tag) value setting executed by command
mirror <rx/tx> added-tag-config.
Using a negative form of the command (no) removes the tag.
Syntax:
[no] mirror add-tag
Options:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> mirror add-tag
4.2.3.7.4 mirror <rx|tx> added-tag-config

This command allows you to set a label value that can be added to the analyzed incoming/outgoing
traffic.
Syntax:
mirror <rx|tx> added-tag-config vlan <vid> [user-prio <user-prio>]
Options:
<vid> – VLAN identification number, takes values from [1 .. 4094]; <user-prio>
– COS priority, takes values from [0 .. 7].
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> mirror rx added-tag-config vlan77userprio5
577
4.2.3.7.5 mirror <rx|tx> vlan

The team setsVLAN ID to be used in the mirroring operation in transit incoming/outgoing traffic.
Syntax:
[no] mirror <rx|tx> vlan
<vid> Options:
<vid> – VLAN identification number, takes the values [1..4094]. Command
mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> mirror rx vlan56
4.2.3.8 Commands for setting the SELECTIVE Q-IN-Q function

To make general function settingsSelective Q-in-Q designed command modeSELECTIVE Q-IN-Q COMMON.
Command mode is used to set the list of Selective Q-in-Q rules SELECTIVE Q-IN-Q LIST.
FunctionSELECTIVE Q-IN-Q allows, based on configured rules, filtering by numbers internalVLAN (Customer
VLAN) add an external SPVLAN (Service Provider's VLAN), replaceCustomer VLAN, as well as deny traffic.
4.2.3.8.1 add-tag
This command adds an external label based on the internal one. Using a negative form of
the command (no) deletes the set rule. Syntax:
[no] add-tag svlan <s-vlan> cvlan <c-

vlan> Options:
<s-vlan> – external label number, takes the values [1..4095];
<c-vlan> – internal label number/numbers, takes values 1-4094. The C-VLAN list is specified through ",".
Command mode:
SELECTIVE Q-IN-Q
4.2.3.8.2 overwrite-tag
This command replaces CVLAN in the desired direction. Using a negative form of the
command (no) deletes the set rule.
578
Syntax:
[no] overwrite-tag new-vlan <new-vlan> old-vlan <old-vlan> <rule_direction>
Options:
<new-vlan> – new VLAN number, takes the values [1 ..4095];
<old-vlan> – VLAN number to be changed, takes the values [1 .. 4094];
<rule_direction> – traffic direction:
• Ingress – incoming;
• Egress - outgoing.
Command mode:
SELECTIVE Q-IN-Q
4.2.3.8.3 remove
This command deletes the ruleSelective Q-in-Q by given number. Syntax:
remove <rule_index>
Options:
<rule_index> – rule number, takes values [0 .. 511]. Command
mode:
SELECTIVE Q-IN-Q
4.2.3.8.4 clear
This command removes all rulesSelective Q-in-Q. Syntax:
clear
Options:
SELECTIVE Q-IN-Q
4.2.3.8.5 selective-qinq enable

With this command on the configurable switch interfaceSMG-2016 the “Selective Q-in-Q” function is
enabled. Using a negative form of the command (no) disables the “Selective Qin-Q” function on the
interface.
Syntax:
[no] selective-qinq
enable Options:
579
Command mode:
4.2.3.8.6 selective-qinq list

With this command, the configurable switch interfaceSMG-2016 is assigned a list of Selective Q-in-Q rules.
Using a negative form of the command (no) removes the binding. Syntax:
selective-qinq list <name>

no selective-qinq list
Options:
<name> is the name of the list of Selective Q-in-Q
rules Command mode:
4.2.3.8.7 show interfaces selective-qinq lists

This command is used to view information about the state of the function “Selective Q-in-Q” on switch
interfaces.
Syntax:
show interfaces selective-qinq lists
4.2.3.9 DUAL HOMING protocol setup
4.2.3.9.1 backup interface

This command specifies the backup interface to which the switch will occur in case of loss of communication
on the main one. Enabling redundancy is possible only on those interfaces on which the protocol is disabled
SPANNING TREE.
Using a negative form of the command (no) removes the setting from the interface.
Syntax:
[no] backup interface <INTERFACE> <INDEX> vlan <VLAN_ID_RANGE>
Options:
<INTERFACE> – interface type:
• front-port – external interfaces;
• port-channel – LAG aggregation groups of external uplink interfaces.
<INDEX> – port number:
• unit – SMG-2016 board number, takes the value [1];
580
<VLAN_ID_RANGE> – can take the following values:
• [1..4094] – specific identifier of the VLAN (VLAN range) for which enable redundancy;
• ignore – enable reservation regardless of existing VLANs on the port.
Command mode:
Example:
Global reservation
SMG2016-[CONFIG]-[SWITCH]-[if]> no backupinterfacevlan ignore SMG2016-[CONFIG]-[SWITCH]-[if]>

backupinterfacefront port1/1vlan ignore
Reservation in a certainVLAN
SMG2016-[CONFIG]-[SWITCH]-[if]> no backupinterfacevlan10 SMG2016-[CONFIG]-[SWITCH]-[if

]> backupinterfaceport channel1vlan10
4.2.3.9.2 backup-interface mac-per-second

This command specifies the number of packets per second that will be sent to the active interface during
a switchover.
Using a negative form of the command (no) restores the default value (400 packages).
Syntax:
[no] backup-interface mac-per-second
<COUNT> Options:
<COUNT> – number of MAC addresses per second, takes the value of [50..400].
Default value:
400 bags
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> backup-interfacemac-per-second200
581
4.2.3.9.3 backup-interface mac-duplicate

This command specifies the number of copies of packages with the sameMAC address to be sent to the
active interface on switchover.
Using a negative form of the command (no) restores the default value (1 package). Syntax:
[no] backup-interface mac-duplicate

<COUNT> Options:
<COUNT> – number of package copies, takes the value [1..4].
Default value:
1 package
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> backup-interfacemac-duplicate4
4.2.3.9.4 backup interface preemption

This command specifies that it is necessary to switch traffic to the main interface when the connection is
restored. If the restoration of the main interface is configured when the backup is active, then when the link
is raised on the main interface, the traffic will be switched to it. Using a negative form of the command (no)
restores the default setting.
Syntax:
[no] backup-interface
preemption Options:
arguments. Default value:
Switching is disabled.
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> backup-interfacepreemption
4.2.3.9.5 show interfaces backup

This command allows you to view interface redundancy settings. Syntax:
show interface backup
582
Options:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> show interfaces backup

Backup Interface Options:
Preemption is disabled.
MAC recovery packets rate400pps Recovery
packets repeats count1.
Backup Interface Pairs

~~~~~~~~~~~~~~~~~~~~~
VID Master Interface Backup Interface State
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - thirty
front port1/0 front port2/0 Master Up/Backup Standby
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 150
front port1/0 front port2/0 Master Up/Backup Standby
4.2.3.10 Configuring the LLDP protocol
4.2.3.10.1 lldp enable

This command allows the switch to work according to the protocolLLDP.
Using a negative form of the command (no) prevents the switch from using the LLDP protocol.
Syntax:
[no] lldp enable
Options:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> lldp enable
583
4.2.3.10.2 lldp hold-multiplier

This command sets the amount of time for the receiving device during which it is necessary to hold received
packets.LLDP before resetting them.
This value is transmitted to the receiving side inLLDP update packages (service packs), is the multiplicity
for the timerLLDP (lldp timer). Thus, the lifetime of LLDP packets calculated by the formulaTTL =
min(65535, LLDP-Timer * LLDP-HoldMultiplier).
Using a negative form of the command (no) sets the default value. Syntax:
lldp hold-multiplier <hold>

no lldp hold-multiplier
Options:
<hold> – time, takes the value of [2 .. 10] seconds.
Default value:
The default value is4 seconds.
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]>lldp hold-multiplier5
4.2.3.10.3 lldp reinit

This command sets the minimum time thatLLDP port will wait before reinitializationLLDP.
Using a negative form of the command (no) sets the default value. Syntax:
lldp reinit <reinit>
no lldp reinit
Options:
<reinit> – time, takes the value [1 .. 10] seconds.
Default value:
584
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> lldp reinit3
4.2.3.10.4 lldp timer

This command determines how often the device will send information updates.LLDP. Using a negative form
of the command (no) sets the default value. Syntax:
lldp timer <timer>
no lldp timer
Options:
<timer> – time, takes the value of [5..32768] seconds.
Default value:
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> lldp timer60
4.2.3.10.5 lldp tx-delay

This command sets the delay between subsequent packet transmissions.lldp, triggered value or
status changes in local databasesMIB LLDP.
It is recommended that this delay be less than the value0.25* LLDP Timer. Using a negative form
of the command (no) sets the default value. Syntax:
lldp tx-delay <txdelay>
no lldp tx-delay
Options:
<txdelay> – time, takes the value of [1..8192] seconds.
Default value:
Command mode:
CONFIG SWITCH
585
Example:
SMG2016-[CONFIG]-[SWITCH]> lldp tx-delay3
4.2.3.10.6 lldp lldpdu

This command sets the packet processing modeLLDP when LLDP is disabled. Using a negative form of the
command (no) sets the default value (filtering). Syntax:
lldp lldpdu [mode]
no lldp lldpdu
Options:
[mode] – LLDP packet processing mode:
• filtering - indicates that LLDP packets are filtered if LLDP is disabled on the switch;
• flooding—Indicates that LLDP packets are forwarded if LLDP is disabled on the switch.
Command mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> lldp lldpdu flooding
4.2.3.10.7 show lldp configuration

This command allows you to viewLLDP configuration of all physical interfaces of the device or specified
interfaces.
Syntax:
show lldp configuration [<interface><
number>] Options:
Optional parameters, if you omit them, then the display will show information on all ports.
[interface] – interface type:

[number] – port number (you can specify several ports by enumeration separated by "," or specify port
range separated by "-"):

• port – port number takes the values [0 .. 3].
586
Default value:
The display will show information for all ports. Command
mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> show lldp configuration
LLDP configuration
~~~~~~~~~~~~~~~~~~
Interface Status Timer (sec) Hold multiplier Reinit delay (sec) Tx delay
(sec)
------------- --------------------------- ------------- -----------------
------------
front-port1/0 front transmit-receive thirty 4 2 2
port1/1 front port1 transmit-receive thirty 4 2 2
/2 front port1/3 transmit-receive thirty 4 2 2
transmit-receive thirty 4 2 2
4.2.3.10.8 show lldp neighbor

This command allows you to view information about neighboring devices on which the protocol is
running.LLDP.
Syntax:
show lldp neighbor [<interface>< number>]
Options:

Default value:
mode:
CONFIG SWITCH
587
Example:
SMG2016-[CONFIG]-[SWITCH]> show lldp neighbor
LLDP neighbors
~~~~~~~~~~~~~~
Interface device ID Port ID TTL
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - front-port1/1 front
port1/2 SMG2016-[CONFIG]-[SWITCH]> 02:00:2a:00:07:15 02:00 g15 115/120
:04:88:7e: front port 1/3 105/120
4.2.3.10.9 show lldp local

This command allows you to viewLLDP information advertised by this port. Syntax:
show lldp local [<interface>< number>]

Options:

• port – port number takes the values [0 .. 3].
Default value:
mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> show lldp local
LLDP local TLVs

~~~~~~~~~~~~~~~
Interface device ID Port ID TTL
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - front-port1/1 front
port1/2 02:00:04:88:7c:0a 02:00 front port 1/1 120
:04:88:7c:0a front port 1/2 120
588
4.2.3.10.10 show lldp statistics
This command allows you to view statisticsLLDP for front-port, port-channel interfaces. Syntax:
show lldp statistics [<interface><number>]

Options:

• port – port number takes the values [0 .. 3];
• for slot-channel: [0 .. 15].
Default value:
mode:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> show lldp statistics
Tables Last Change Time:0:0:4:28 Table

Inserts:3
Table Deletes:1
Tables Dropped:0
Table Ageouts:0
LLDP statistics
~~~~~~~~~~~~~~~
Interface Tx total Rx total Rx errors Rx discarded TLVs discarded TLVs unrecognized
Agouts total
front port1/0 0 0 0 0 0 0 0
front port1/10 6134 6159 0 0 0 0
front port1/20 6141 6136 0 0 0 0
front port1/thirty 0 0 0 0 0 0
589
4.2.3.10.11 show lldp lldpdu

The command is used to view the processing methodLLDPDUs for interfaces where LLDP is disabled.
Syntax:
show lldp lldpdu
Options:
CONFIG SWITCH
Example:
SMG2016-[CONFIG]-[SWITCH]> show lldp lldpdu Global:

flooding
4.2.3.11 QOS setting
4.2.3.11.1 qos default

This command specifies the priority queue that will receive packets without predefined rules.
Queue with value7 is considered the highest priority.
Syntax:
qos default <queue>
Options:
<queue> – priority queue number, takes values [0 .. 7]. Default value:
Queue is the default0. Command mode:
CONFIG SWITCH
Example:
qosdefault6
Packets for which no other rules are set enter the priority queue6.
4.2.3.11.2 qos type

This command allows you to set a rule that will select the priority field for a packet.
Based on the established rules, the system will decide which method will be used to prioritize traffic (
IEEE 802.1p/DSCP).
The following traffic prioritization methods are distinguished in the system:
• All priorities are equal;
590
• Packet selection according to the IEEE 802.1p standard;
• Packet selection by IP ToS only (type of service) at layer 3 – Differentiated Services Codepoint
(DSCP) support;
• Interaction either over 802.1p or DSCP/TOS;
Syntax:
qos type <type>
Options:
<type> – traffic prioritization method:
• 0 – all priorities are equal;
• 1 – selection of packages for 802.1p only (Priority field in 802.1Q Tag);
• 2 – selection of packets by DSCP/TOS only (Differentiated Services field of the IP packet header, upper 6 bit);
• 3 - either 802.1p or DSCP/TOS communication.

Default value:
By default, all priorities are equal. Command
mode:
CONFIG SWITCH
Example:
qos type2
Traffic will be prioritized only onDSCP/TOS.
4.2.3.11.3 qos map

This command sets the parameters for the priority queue:
• the value of the Differentiated Services field of the IP packet header is indicated, the upper 6 bits,
• the value of the Priority field in the 802.1Q Tag.
Based on the rules set by the teamqos type, and the given priority values are carried out selection of
packets in this priority queue.
Using a negative form of the command (no) allows you to delete an entry from the settings table
queues.
Syntax:
[no] qos map <type> <field values> to
<queue> Options:
<type> – traffic prioritization method:
• 0 – according to the 802.1p standard (used at layer 2);
• 1 - according to the DSCP / TOS standard (used at level 3).
<field values> – the value of the field by which packets are selected is set to depending on <parameter1>
(field values are entered separated by commas, or as a range separated by "-"):
• if <type> = 0, then the value of the Priority field in the 802.1Q Tag is set: [0 .. 7];
• if <type> = 1, then field values are setDifferentiated ServicesIP packet header elder6 bits The value
is entered in decimal format: [0 .. 63].
<queue > – priority queue number, takes values [0 .. 7].
591
Command mode:
CONFIG SWITCH
Example:
qos-map0 7 7
ForThe 7th priority queue has the value of the field priority = 7 in the 802.1Q Tag.
4.2.3.11.4 cntrset
This command binds the queue statistics collector to queues with specified criteria.
Syntax:
cntrset <PORT> <UNIT> <SET> <VLAN> <QUEUE> <DROP PRECEDENCE>
Options:
<PORT> – port type for counting takes the following values:
• all – all ports;
• cpu – CPU port;
• front-port – counting front-port;
• host-port;
• sm port.
<UNIT> – serial number of the port:
• for cpu: takes values [1];
• for host-port: <unit/port>, where:
• for sm-port: <unit/port>, where:
• <SET> – statistics collector number, takes the values [0 .. 1];
• <VLAN> – VLAN identification number, takes the values [1 .. 4094] or all;
• <QUEUE> – queue number, takes the values [0 .. 7] or all;
• <DROP PRECEDENCE> – drop precedence value [0 .. 1] or all.
Command mode:
CONFIG-SWITCH
Example:
cntrset sm port1/2 1 22 2 1
592
4.2.3.11.5 show cntrset

A command to view information about the queue collector.
Syntax:
show cntrset <SET>
Options:
<SET> – counter number [0 .. 1].
Command mode:
CONFIG-SWITCH
4.2.3.11.6 show qos

This command is used to view the priorities assigned to queues. The default queue priority is0. The
priority value for the queue is set in the range [0 .. 7], queue with priority value7 is considered the
highest priority.
Syntax:
show qos
Options:
CONFIG-SWITCH
4.2.3.12 Configuration commands

At the switchSMG-2016 have 2 types of configuration:
• running-config – configuration that is currently active on the device;
• candidate-config – configuration that has been modified, running-config is will become after its
application a teamapply.
4.2.3.12.1 View configuration
4.2.3.12.1.1 View commandrunning-config

Syntax:
show running-config
Options:
CONFIG-SWITCH
4.2.3.12.1.2 View commandcandidate-config

Syntax:
show candidate-config
593
Options:
CONFIG-SWITCH
4.2.3.12.2 Apply and validate configuration commands

After completing the switch configuration stepsSMG-2016 must be applied configuration (apply) to make it
active on the device, and confirm the application (confirm) for protection from the fact that the changes made
caused the loss of access to the device. If within60 sec. confirmation was not performed, the configuration is
rolled back to the previous running-config.
4.2.3.12.2.1 Apply configuration command Syntax:
apply
Options:
CONFIG-SWITCH
4.2.3.12.2.2 Acknowledge command

Syntax:
confirm
Options:
CONFIG-SWITCH
4.2.3.13 Other commands
4.2.3.13.1config
Command to return to the menu
configuration. Syntax:
config
Options:
CONFIG-SWITCH
594
4.2.3.13.2 exit
The command to exit this configuration submenu to a higher level. Syntax:
exit
Options:
CONFIG-SWITCH
4.2.3.13.3 history
The command to view the history of entered
commands. Syntax:
history
Options:
CONFIG-SWITCH
595
5 Applications (SMG)
5.1 Appendix A. Assignment of cable connector pins
5.1.1 For SMG-2016, SMG-3016

Connector pin assignmentRJ-48to connect E1 streamsE1 Line 0..15corresponds specificationsISO/
IEC 10173 and shown in the table below.
Table A1 - Assignment of connector pinsRJ-48to connect E1 streams
contact number (pin) Purpose Contact numbering
1 RCV tip (receive data)
2 RCV ring (receive data)
3 RCV shield (receiver shield)
4 HMTtip (data transfer)
5 XMT ring (data transfer)
6 HMTshield (transmitter shield)
7 Not in use
8 Not in use
Connector pin assignmentRJ-45console portConsoleshown in the table below. Table A2 -

Assignment of connector pinsRJ-45console port
1 Not in use
2 Not in use
3 TX
4 Not in use
5 GND
6 RX
596
7 Not in use
8 Not in use
Connector pin assignmentRJ-45to connect an external clock sourceSync.0/ Sync.1shown in the table
below.
Table A3 - Assignment of connector pinsRJ-45to connect an external source synchronization
1 Sync A1
2 Sync B2
3 Not in use
4 Sync A
5 Sync B
6 Not in use
7 Not in use
8 Not in use
- 1Pins 1 and 4 are electrically interconnected inside the device.

2Pins 2 and 5 are electrically interconnected inside the device.
597
5.1.2 For SMG-1016M

E1 Line 0..7
E1 Line 8..15
Drawing50 - Assignment of connector pinsE1 line

ContactsPfPdesigned to receive a signal from the channel to the device.
598
ContactsDRPdesigned to transmit a signal from a device to a channel.
ContactsSyncdesigned to synchronize the device from external sources (input impedance120 ohm).
Drawing51 - Assignment of connector pinsConsole
Drawing52 - Cable diagram for connection to PORT1, PORT2
5.1.3 Correspondence tables for wire color and contact of the E1 Line connector
Table A4 - Correspondence of the color of the wire and the contact of the E1 Line connector (NENSHI NSPC-7019-18 cable)
Wire color connector pin Wire color connector pin
white-blue 1 black and blue 10
Blue 19 Blue 28
white-orange 2 black-orange eleven
Orange 20 Orange 29
white-green 3 black green 12
Green 21 Green thirty
white-brown 4 black brown 13
Brown 22 Brown 31
599
Violet 5 Yellow-blue 14
Grey 23 Blue 32
Red-blue 6 yellow-orange 15
Blue 24 Orange 33
red-orange 7 yellow green 16
Orange 25 Green 34
red-green 8 tan 17
Green 26 Brown 35
Red-brown 9 yellow gray 18
Brown 27 Grey 36
600

Table A5 - Correspondence of the color of the wire and the contact of the E1 Line connector (HANDIAN UTP 18PR cable)
white-blue 1 Red-grey 10
Blue 19 Grey 28
white-orange 2 black and blue eleven
Orange 20 Blue 29
white-green 3 black-orange 12
Green 21 Orange thirty
white-brown 4 black green 13
Brown 22 Green 31
Violet gray 5 black brown 14
Grey 23 Brown 32
Red-blue 6 Black gray 15
Blue 24 Grey 33
red-orange 7 Yellow-blue 16
Orange 25 Blue 34
red-green 8 yellow-orange 17
Green 26 Orange 35
Red-brown 9 yellow green 18
Brown 27 Green 36
601
5.2 Appendix B. Backup Firmware Update
5.2.1 Backup device firmware update via RS-232

If the software update fails viaweb configurator or console (Telnet, SSH), exists the possibility of backup
software updates throughRS-232.
In order to update the firmware of the device, the following programs are required:
• Terminal program (eg TERATERM);
• TFTP server program.
The sequence of actions when updating the device:
1. Connect to the Ethernet port of the device;
2. Connect the COM port of the computer to the Console port of the device with a crossed cable;
3. Run a terminal program;
4. Set the baud rate to 115200, data format 8 bits, no parity, 1 bit stop, no flow control;
5. Run the program on the computertftpserver and specify the path to the foldersmg_files, in it create
foldersmgwhere to put the filesSMG_kernel, SMG_initrd(the computer running the TFTP server and
the device must be on the same network);
6. Turn on the device and in the terminal program window stop the download by entering
commands“stop":
U Boot2009.06(Feb09 2010-20:57:21)
CPU: AMCC PowerPC 460GT Rev. At800MHz (PLB=200,OPB=100, EBC=100MHz) Security/Kasumi

support
Bootstrap Option B - Boot ROM Location EBC (16bits) 32kB I-Cache32
kB D-Cache
Board: SMG-1016Mv2 board, AMCC PPC460GT Glacier based,2*PCIe Rev. FF I2C:
ready
DRAM: 512MB
SDRAM test phase1: SDRAM
test phase2: SDRAM test
passed. OK! FLASH:64MB
NAND: 128MiB
DTT: 1FAILED INIT
net: ppc_4xx_eth0, ppc_4xx_eth1
Type run flash_nfs to mount root filesystem over NFS
Autobooting in3seconds, press'stop'forstop =>
7. Enterset ipaddr<Device IP address> <ENTER>;

Example:set ipaddr 192.168.2.2
8. Enterset netmask<device netmask> <ENTER>; Example:set
netmask 255.255.255.0
9. Enterset serverip<IP address of the computer running tftp server> <ENTER>; Example:
set serverip 192.168.2.5
602
10. Entermii si<ENTER> to activate the network interface:
=> mii si
Initswitch0: ..Ok! Init
switch1: ..Ok! Init phy1
: ..Ok! Init phy2: ..Ok! =>
11. Update the Linux kernel with the commandrun flash_kern:
=> run flash_kern

About preceeding transfer (eth0):
- sent packet number0
- received packet number0
- handled packet number0
ENET Speed is1000Mbps – FULL duplex connection (EMAC0) Using
ppc_4xx_eth0 device
TFTP from server192.168.2.5; our IP address is192.168.2.2 filename'smg/
SMG_kernel'. load address:0x400000
Loading: ################################################ ##################

##################################
done
Bytes transferred =1455525(1635a5 hex) Un-Protected
15sectors
. . . . . . . . . . . . . . . done
Erased15sectors
Copy to Flash...9....8....7....6....5....4....3....2....1....done =>
603
12. Update the file system with the commandrun flash_initrd:
=> run flash_initrd

Using ppc_4xx_eth0 device
TFTP from server192.168.2.5; our IP address is192.168.2.2 filename'smg/
SMG_initrd'. load address:0x400000
Loading: ################################################ ##################

###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
####################
done
Bytes transferred =25430113(1840861hex) Erase Flash
Sectors56-183in bank#2 unprotected256sectors
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . done Erased256
sectors
Copy to Flash...9....8....7....6....5....4....3....2....1....done =>
13. Start the device with the commandrun boot cmd.
5.2.2 Backing up device firmware from a USB flash drive

In the case when other methods of updating the software are not available, it is possible to update the
software usingUSB flash drive.
To update the device firmware usingUSB flash drive, you need the following:
• USB flash drive;
• Terminal program (eg TERATERM).
The sequence of actions when updating the device:
1. Copy the software file to the root directory of the USB flash drive;
2. Connect the COM port of the computer to the Console port of the device with a crossed cable, or
establish a connection with the device using the protocolTelnet/SSH
3. Run a terminal program;
4. Set the baud rate to 115200, data format 8 bits, no parity, 1 bit stop, no flow control (in case of
connection viaRS-232);
5. Turn on the device and wait for it to boot;
6. After downloading, connect in terminal mode via Telnet/SSH protocol or via RS-232;
604
7. In CLI mode, enter the command:
firmware update <file-name> usb
If the modeCLI is not available, update is possible in modeshell, for this you need enter in mode
shell:
/usr/local/scripts/get_firmware <file-name> usb
where <file-name> – software file name.

8. Wait for the software update to complete and restart the device.
5.3 Appendix B. Examples of modifiers and device settings via CLI
5.3.1 Examples of how modifiers work
5.3.1.1 How to apply modifiers on an incoming connection

• from trunk group or PBX profile by CgPN number – you can change CgPN and CdPN;
• from a trunk group or PBX profile by CdPN number – you can change CgPN and CdPN (CdPN
number is used as modified in step 1);
• from RADIUS via CgPNin – only CgPN can be changed (the CgPN number is used as modified in cl.
1.2);
• from RADIUS via CdPNin – only CdPN can be changed (the CdPN number used is the one changed in par.
1,2).
5.3.1.2 Order of application of modifiers on outgoing communication

• from trunk group or PBX profile by CgPN number – you can change CgPN and CdPN (CgPN number
is used after all higher items);
• from trunk group or PBX profile by CdPN number – you can change CgPN and CdPN (CdPN number
is used after all higher items);
• from RADIUS via CgPNout – only CgPN can be changed (CgPN number is used after all higher
points)
• from RADIUS via CdPNout – only CdPN can be changed (the CdPN number is used after all above
paragraphs).
5.3.1.3 Task 1
INtrunk group0for outgoing dialing corresponding to the mask (1x{4,6}) you need to do transformation -
remove the first digit, add numbers in its place34, other digits are not change.
Compiling a Modification Rule

Everyone falls under this mask.5, 6 and 7 digit numbers starting with 1. According to the syntax of the
modification rule would be:“.+34xxxx??(symbol "." in the first position - deleting the first digit, "+34" - adding
the numbers 34 after it, "xxxx" - the next 4 digits will be always present and not modified, "??" – latest2 digits
may be missing in case of 5- digit number, but if the number6 or 7-digit, then there are one or two digits in
these positions, and they are not modified).
Commands used:
SMG>config// enter configuration mode
605
Entering configuration mode
SMG-[CONFIG]>new modifiers-table// create a new modifier table NEW 'MOD-

TABLE' [07]: successfully created// created table number 7 SMG-[CONFIG]>modifier
table7// Enter table configuration modeNo.7 Entering modifiers-table mode.
SMG-[CONFIG]-MODTABLE[7]>add(1x{4,6}) ".+34xxxx??"// Add number mask and rule

transformations
Mdifier. add
modifier. Create: mask <(1x{4,6})>, cld-rule <.+34xxxx\?\?>, clg-rule <$> NEW'MODIFIER'[07]:
successfully created Modifier. Created with index[7]. 'MODIFIER'
[07]:
table: 7
mask: (1x{4,6})
numtype: any
AONcat: any
general-access: no change
general-numplan: no change
called-rule: . +34xxxx??
called-type: no change
called-numplan: no change
calling-rule: $
calling-type: no change
calling-numplan: no change
calling-present: no change
calling-screen: no change
calling-catAON: no change
SMG-[CONFIG]-MODTABLE[7]>exit// exit modifier table configuration mode Back to configuration mode.
SMG-[CONFIG]>trunk 0// enter trunk group configuration mode Entering trunk-

mode
SMG-[CONFIG]-TRUNK[0]>modifiers table outgoing called7// add the created table number
conversion modificationsCdPN for outgoing calls.
606
Trunk[0]. Set oModCld'7' 'TRUNK

GROUP'[00]:
name: TrunkGroup00
disable out: no
disable in: no
reserve trunk: none
direct_pfx: none
RADIUS-profile: none
destination: SIPT Interface [3]no
local:
Modifiers:
incoming calling: none
incoming called: none
outgoing calling: none
outgoing called: 7
5.3.1.4 Task 2
INtrunk group0from the caller's number received in the national code format zones383, you need to delete
the area code and change the type of number to a subscriber -subscriber.
Compiling a Modification Rule
Number in national format -10 digits and starts with 383 because the rest seven digits can be any, then
“xxxxxxx” is written in their place. The resulting mask (383ххххххх).It is necessary to delete the area code -
that is, the first 3 digits, the remaining digits remain without changes, resulting modification rule:"
...xxxxxxx". Category modification in progress teamchange(in the example commands below, the command
addincoming has been added modifier with number2, so in the category modification commandchangeneed
to use modifier2).
Commands used:
SMG>config// enter configuration mode
SMG-[CONFIG]>trunk 0// enter trunk group configuration mode SMG-[CONFIG]-TRUNK[0]>
modifiers//enter modifier configuration mode
SMG-[CONFIG]-TRUNK[0]-MODIFIER>add incoming calling (383xxxxxxx) "...xxxxxxx"// add rule caller
number modification on incoming calls
inmodifier. Create: mask <(383xxxxxxx)>, rule <...xxxxxxx> NEW'TRUNK: IN-

MODIFIER'[02]: successfully created InModifier. Created with index[2]. 'TRUNK:
IN-MODIFIER'[02]:
trunk: 0
type: calling
mask: (383xxxxxxx)
rules: . . . xxxxxxx
calling-type: no change
calling pres: no change
calling-scrn: no change
SMG-[CONFIG]-TRUNK[0]-MODIFIER>change incoming clg_type 2 subscriber// change number type

caller in the modifier created by the previous command
607
'TRUNK: IN-MODIFIER'[02]:
trunk: 0
type: calling
mask: (383xxxxxxx)
rules: . . . xxxxxxx
calling-type: subscriber
calling pres: no change
calling-scrn: no change
5.3.2 Example of device configuration via CLI
5.3.2.1 Task
Set up transit OKS-7-SIPT.
5.3.2.2 Initial data

Physically, the flow from the oncoming PBX is connected to the zero flow E1 on the SMG
connector. OKS-signaling parameters7:
• OPC=67;
• DPC=32;
• signaling channel SLC=1 in timeslot 1;
• CIC numbering from 2 to 31, respectively for channels 2 to 31;
• the order of channel occupation is “sequentially forward, even” (respectively, to exclude mutual
occupation of channels on the opposite side, the order of occupation of channels should be assigned,
for example, “successively back, odd”).
Alarm parametersSIP-T:
• IP address of the interacting gateway – 192.168.16.7;
• UDP port for receiving SIP-T signaling of the interacting gateway – 5060;
• number of allowed simultaneous sessions – 25;
• packetization time for G.711 codec – 30 ms;
• transmission of DTMF signals during an established session according to RFC2833, load type for
packagesRFC2833-101.
Routing:
• route to SS-7 via trunk group 0;
• route to SIP-T over trunk group 1;
• access to OKS-7 is carried out by 7-digit numbers starting with the numbers 6, 7, 91, 92, 93;
• access to SIP-T is carried out by 7-digit numbers starting with numbers 1, 2, 3;
• all SS-7 signaling messages are transmitted in transit.
5.3.2.3 Configuration via CLI
5.3.2.3.1 Configuring SS-7 SMG> signaling parametersconfig// enter

configuration mode SMG-[CONFIG]>new link set// create a new group
of lines (linkset) NEW 'LINKSET' [00]: successfully created
608
SMG-[CONFIG]>linkset 0// enter linkset configuration mode Entering
Linkset-mode.
SMG-[CONFIG]-LINKSET[0]>chan_order even_successive_forward// select the order in which the channels are occupied –
even, in a circle forward
Linkset[0]. Set chan_order '6'

SMG-[CONFIG]-LINKSET[0]>DPC 32// set the code of the opposite signaling point
Linkset[0]. Set DPC '32'
SMG-[CONFIG]-LINKSET[0]>OPC67// set the code of our own signaling point Linkset[0].
Set OPC '67'
SMG-[CONFIG]-LINKSET[0]>init group-reset// select the channel initialization mode when lifting signal
channel
Linkset[0]. Set init '7'
SMG-[CONFIG]-LINKSET[0]>net_ind national// set network indicator - local network
Linkset[0]. Set net_ind'3' 'LINKSET'[

00]:
Name: Linkset00
trunk: 1
Access cat: 0
OPC: 67
DPC: 32
init: 'group reset'
China: n
chan order: 'even_successive_forward'
netw_ind: national
satellite: override_no_satellite
interface: no change
TMR: speech
alarm ind: no
CCI: off
CCI_freq: 3
SMG-[CONFIG]-LINKSET[0]>exit// exit linkset configuration mode Leaving link set

mode
SMG-[CONFIG]>e1 0// enter the E1 zero flow configuration mode Entering E1-
stream mode
SMG-[CONFIG]-E1[0]>enabled// put the E1 thread into operation
E1[0]. Set line 'on'
SMG-[CONFIG]-E1[0]>signaling SS7// select the OKS-7 signaling protocol on the stream
609
E1[0]. Set signaling3 'E1:

PHYS'[00]:
line 'on'
code 'hdb3'
eq 'off'
crc 'off'
sig 'SIG_SS7' (3)
alarm_ind 'off'
rem_alarm_ind 'off'
SMG-[CONFIG]-E1[0]>ss7//enter the SS-7 protocol configuration mode E1[0].

Signaling is SS7
SMG-[CONFIG]-E1[0]-[SS7]>CIC fill 0 1// set the numbering of channels starting from 0 with a step of 1
E1-SS7[0]. Fill CIC: start[0], step[1]
SMG-[CONFIG]-E1[0]-[SS7]>Dchan 1// select channel 1 as signal E1-SS7[0]. Set

Dchan 1
SMG-[CONFIG]-E1[0]-[SS7]>SLC 1// assign code 1 to the created signal channel E1-SS7[0].
Set SLC 1
SMG-[CONFIG]-E1[0]-[SS7]>linkset 0// assign a null linkset to the thread
E1-SS7[0]. Set Link Set0 'E1:SS7'[

00]:
stream: 0
linkset: 0
SLC: 1
CICs:
00: --- |01:-D- |02:002|03:003| 04:004|05:005|06:
006|07:007| 08:008|09:009|10:010|eleven:011| 12:
012|13:013|14:014|15:015| 16:016|17:017|18:018|
19:019| 20:020|21:021|22:022|23:023| 24:024|25:
025|26:026|27:027| 28:028|29:029|thirty:030|31:
031|
SMG-[CONFIG]-E1[0]-[SS7]>exit// exit the SS7 protocol configuration mode Leaving SS7

signaling mode
SMG-[CONFIG]-E1[0]>exit// exit the E1 zero flow configuration mode Leaving E1-stream
mode
5.3.2.3.2 Configuring SIP-T signaling parameters
-Continuation of the session described above.
SMG-[CONFIG]>new sip-interface// create a new SIP-T interface NEW

'SIPT INTERFACE' [00]: successfully created
SMG-[CONFIG]> sip interface 0// enter the configuration mode of the created SIP-T interface
610
Entering SIPT mode.
SMG-[CONFIG]-SIP/SIPT/SIPI-INTERFACE[0]>ipaddr 192.168.16.7// set the IP address of the interacting
gateway
SIPT-Interface[0]. Set ipaddr '192.168.16.7'
SMG-[CONFIG]-SIPT-INTERFACE[0]>port 5060// set the UDP port of the communicating gateway for
signaling workSIP-T
SIPT-Interface[0]. Set port '5060' SMG-[CONFIG]-SIP/SIPT/SIPI-INTERFACE[0]>
codec set0 G.711-a// set codec SIPT-Interface[0]. Set codec '0'
SMG-[CONFIG]-SIP/SIPT/SIPI-INTERFACE[0]>codec pte0 30// set packetization time to 30ms for codec

G.711
SIPT-Interface[0]. Set pte '30'
SMG-[CONFIG]-SIPT-INTERFACE[0]>max_active 25// set the number of simultaneous sessions SIPT-
Interface[0]. Set max_active '25'
SMG-[CONFIG]-SIPT-INTERFACE[0]>DTMF mode RFC2833// select DTMF transmission method - RFC2833 SIPT-
Interface[0]. Set DTMF_type '1'
SMG-[CONFIG]-SIPT-INTERFACE[0]>DTMF payload 101// select load type 101 for RFC2833
611
SIPT-Interface[0]. Set DTMF_PT'101' 'SIP/SIPT

INTERFACE'[00]: id[00]
name: SIP-interface00
mode: SIP-T
trunk: 0
access category: 0
ip:port: 192.168.16.7:5060 <not set> /
login/password: <not set>
codecs:
0:
codec: G.711-A
ptype: 8
pte: thirty
max active: 25
VAD/CNG: no
echo cancel: voice(default)
DSCPRTP: 0
DSCP SIG: 0
RTCP period: 0
RTCP control: 0
RTP loss timeout: off
DTMF MODE: RFC2833

DTMF PType: 101
DTMFMIMETYPE: application/dtmf
CCI: off
redirect(302): REFER: disabled
disabled
Session Expires: 1800
Min SE: 90
Refresher: uac
Report: disabled
options: disabled:0
FAX detect: no detecting

FAX mode: none
VBD: disabled
jitter buffer adaptive mode

minimum size: 0ms
initial size: 0ms
maximum size: 200 ms
deletion mode: soft
deletion threshold: 500 ms
adaptation period: 10000 ms
adjustment mode: non-immediate
sizeforVBD: 0
SMG-[CONFIG]-SIPT-INTERFACE[0]>exit// exit the SIP-T interface configuration mode Leaving SIPT

mode
612
5.3.2.3.3 Routing setup:
SMG-[CONFIG]>new trunk// create a trunk group for a group of SS-7 lines NEW
'TRUNK GROUP' [00]: successfully created
SMG-[CONFIG]>new trunk// create a trunk group to work through the SIP-T interface NEW
'TRUNK GROUP' [01]: successfully created
SMG-[CONFIG]>new prefix// create a prefix for the exit in the direction of OKS-7 NEW
'PREFIX' [00]: successfully created
SMG-[CONFIG]>new prefix// create a prefix to exit in the direction of SIP-T NEW
'PREFIX' [01]: successfully created
SMG-[CONFIG]>trunk 0// enter trunk group configuration mode for line group OKS-7
Entering trunk-mode
SMG-[CONFIG]-TRUNK[0]>destination SS7 0// associate trunk group 0 with SS line group 0
Trunk[0]. Set destination'2' Trunk[0].

Same destination 'TRUNK GROUP'[00]:
name: TrunkGroup00
disable out: no
disable in: no
reserve trunk: none
direct_pfx: none
destination: Linkset[0]
SMG-[CONFIG]-TRUNK[0]>exit// exit the trunk group configuration mode for the group lines OKS-7
Leaving TRUNK mode

SMG-[CONFIG]>trunk 1// enter the trunk group configuration mode for the SIP-T interface Entering trunk-
mode
SMG-[CONFIG]-TRUNK[1]>destination SIPT 0// bind trunk group 1 to SIP-T interface 0
Trunk[1]. Set destination'3' Trunk[1].

Same destination 'TRUNK GROUP'[01
]:name:
TrunkGroup01
disable out: no
disable in: no
reserve trunk: none
direct_pfx: none
destination: SIPT-Interface [0]
613
SMG-[CONFIG]-TRUNK[1]>exit// exit trunk group configuration mode for SIP-T interface
Leaving TRUNK mode

SMG-[CONFIG]>prefix 0// enter the prefix configuration mode for accessing the trunk group0
Entering Prefix-mode
SMG-[CONFIG]-PREFIX[0]>type trunk// set the type of prefix - "exit to the trunk group" prefix[0]. Set
type '1'
SMG-[CONFIG]-PREFIX[0]>trunk 0// assign output by prefix to trunk group 0 prefix[0]. Set idx
'0'
SMG-[CONFIG]-PREFIX[0]>mask edit// enter the editing mode of the set and analysis masks caller
numbers
Entering Prefix-Mask mode
SMG-[CONFIG]-PREFIX[0]-MASK>add([67]xxxxxx|9[1-3]xxxxx)// add the set mask to
assignment
123
PrefixMask. add
NEW'PREFIX-MASK'[00]: successfully created PrefixMask.
Created with index[00]. 'PREFIX-MASK'[00]:
mask: ([67]xxxxxx|9[1-3]xxxxx) 0
prefix:
type: called
Ltimer: 10
Timer: 5
Duration: thirty
SMG-[CONFIG]-PREFIX[0]-MASK>exit// exit the editing mode of the set and analysis masks caller
numbers
Leaving Prefix-Mask mode
SMG-[CONFIG]-PREFIX[0]>called transit// set transit for callee number type subscriber
614
prefix[0]. Set called'5' 'PREFIX'[00]:
type: 'to trunk'

idx: 1
access cat: 0[no check]
direction: 'local'
called type: 'transit'
getCID: n
needCID: n
dial_mode: enblock
priority: 100
Timer: 5
duration: thirty
Maskforprefix [00]:
[000] - ([67]xxxxxx|9[1-3]xxxxx) [called]
Ltimer: 10
Timer: 5
Duration: thirty
SMG-[CONFIG]-PREFIX[0]>exit// exit prefix configuration mode Leaving prefix mode
SMG-[CONFIG]>prefix 1// enter the prefix configuration mode for accessing the trunk group1
Entering Prefix-mode
SMG-[CONFIG]-PREFIX[1]>type trunk// set the type of prefix - "exit to the trunk group" prefix[1]. Set
type '1'
SMG-[CONFIG]-PREFIX[1]>trunk 1// assign output by prefix to trunk group 1 prefix[1]. Set idx
'1'
SMG-[CONFIG]-PREFIX[1]>mask edit// enter the editing mode of the set and analysis masks caller
numbers
Entering Prefix-Mask mode
SMG-[CONFIG]-PREFIX[1]-MASK>add([1-3]xxxxxx)// add a set mask according to task
PrefixMask. add
NEW'PREFIX-MASK'[01]: successfully created PrefixMask.
Created with index[01]. 'PREFIX-MASK'[01]:
mask: ([1-3]xxxxxx) 1
prefix:
type: called
Ltimer: 10
Timer: 5
Duration: thirty
SMG-[CONFIG]-PREFIX[1]-MASK>exit// exit the editing mode of the set and analysis masks caller
numbers
Leaving Prefix-Mask mode
615
SMG-[CONFIG]-PREFIX[1]>called transit// set transit for callee number type subscriber
prefix[1]. Set called'5' 'PREFIX'[01]:
type: 'to trunk'

idx: 1
access cat: 0[no check]
direction: 'local'
called type: 'transit'
getCID: n
needCID: n
dial_mode: enblock
priority: 100
Timer: 5
duration: thirty
Maskforprefix [01]:
[001] - ([1-3]xxxxxx) [called]
Ltimer: 10
Timer: 5
Duration: thirty
SMG-[CONFIG]-PREFIX[1]>exit// exit prefix configuration mode Leaving prefix mode
5.3.2.3.4 Saving the configuration and restarting the device
SMG-[CONFIG]>copy running_to_startup// save the configuration tar:

removing leading '/' from member names
**********
* * * * * Saved successful
SMG-[CONFIG]> exit
Leaving configuration mode.

SMG>reboot yes// reboot the device
5.4 Appendix D. Transferring VAS settings from a RADIUS server for dynamic
subscribers
-Available with licenseSMG-PBX and SMG-VAS.
On the gateway, it is possible to transfer VAS service settings for dynamic subscribers using commands
fromRADIUS servers sent in response to RADIUS-Authorization requests when registration. Commands are
transmitted in text form usingVendor-Specific attribute (see chapterAnswer Correspondence TablesRADIUS
and voice messages) with vendor number, assigned to LLC “Enterprise “ELTEKS” and equal35265, and
attribute name "Eltex-AVPair", having a number1.
The general format of an attributeEltex-AVPair looks like this:
616
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1):<$COMMAND-STRING>
By passing various commands in the $ lineCOMMAND-STRING, it is possible to pass the following

options:
• enabling/disabling VAS services for dynamic subscribers;
• settings for connected services (numbers for forwarding, number of BLF subscribers);
• deactivation of all VAS services for the subscriber.
5.4.1 Query syntax

The command consists of the initial text identifier of the command, the identifier of the connection/disconnection of the
VAS service for which the configuration is being performed, and the VAS configuration command.
• "UserService:" is a text identifier indicating that this attribute contains a command for the management
of DVO.
• "CFU=", "CFB=", "CFNR=", "CFOS=", "CT=", "CallPickup=", "Hold=", "BLF=", "Intercom=", "Conf=" ,
"3PTY=", "ClearAll=" – identifier for connecting/disconnecting VAS services, can receive valuesyes
or no, to enable or disable the VAS service, respectively.
• CFU – call forwarding unconditional;
• CFB – call forwarding on busy;
• CFNR – forwarding on no response;
• CFOS – forwarding on unavailability;
• CT – call transfer;
• CallPickup – call pickup;
• Hold – hold a call;
• BLF – busy line indication (BLF);
• Intercom – access to intercom and paging calls;
• Conf – conference with sequential gathering;
• 3PTY - tripartite conference;
• ClearAll – access to the "Cancel all services" service.
• "numCFU=", "numCFB=", "numCFNR=", "numCFOS=" – configuration commands call", as a value, the
list telephone number of the subscriber to which
call forwarding is configured.

• “limitBLF=” – VAS configuration command “Busy Line Indication (BLF)”, as a parameter Maybe
transmitted the number of subscribers.

• 'CT=', 'CallPickup=', 'Intercom=', 'Conf=', '3PTY=', 'ClearAll=' have no additional settings.
• "UserService:none" – a command to disable VAS for a subscriber.
-If the subscriber has been connected to VAS services, i.e. ID has been passed connection/
deactivation of VAS services, equal to the value "yes", then disable this service You can only
pass the value "no" for this subscriber. If after connecting VAS services in subsequent
messages fromRADIUS server was not transmitting information about the connected VAS, then
the service is considered active until the parameter is transmitted "no".
If the subscriber was connected to any VAS and after some time he became inactive (the
registration time on the device expired), then his VAS are considered active until the
parameter "UserService:none" for this subscriber.
After rebooting the device, VAS connected to the subscriber remain active.
617
5.4.2 Service connection examples

Task1
Service subscriber connection"Unconditional call forwarding"to number12345, "Redirects on no response »
to number56789 and services"Call pickup".
Actions
You need to send a request with the following content:
UserService:CFU=yes;numCFU=12345;CFNR=yes;numCFNF=56789;CallPickup=yes"
Task2
Disabling services for a subscriber"Unconditional Call Forwarding", "Call Pickup"and service connection"BLF
for 10 subscribers»And"Call transfer".
Actions
You need to send a request with the following content:
UserService:CFU=no;CallPickup=no;CT=yes;BLF=yes;limitBLF=10;
5.5 Appendix E. SORM function settings

Related materials:
Hardware and software of devicesSMG-1016M, SMG-2016 and SMG-3016 allow you to perform technical
requirements for the system of technical means to ensure the functions of operational-search activities on
electronic exchanges, approved by order of the State Communications Committee of Russia dated
04/20/1999No.70 and the order of the Ministry of Telecom and Mass Communications of RussiaNo.268 dated 11/19/2012.
Organization of data transmission channels (CPD) betweenSMG and PU SORM for the transfer of control
information and information on controlled compounds provides for the option shown in the figure below.
Drawing53 - Diagram of connecting SMG to PU SORM

media gatewaySMG allows you to organize one E1 stream to the SORM console of special services.
-INSMG implemented the main option for connecting to the SORM PU (on the E1 stream), additional
connection option (according toTCP/IP) is supported from software version 3.7.0.
618
One Stream E1 SORM contains 28 voice channels (CSL - control trunks) for listening to controlled subscribers.
-With combined control, audio traffic is mixed into the conversational channel of the SORM stream from
subscribers A and B. Mixing of sound streams occurs using a three-party conference onVoIP
submodule. One VoIP submodule supports 27 triangular conferences. Thus, to ensure the possibility
of interception simultaneously on all channels of the stream E1 requires that at least 2 VoIP sub-
modules (SM-VP-M300) be installed on the gateway.
-To ensure the operation of SORM, one submodule is fully reservedSM-VP-M300. Other calls through it
will not go.
619
5.5.1 Calculation of the required number of submodules when using SORM

When Using a Network Switching GatewayTDM and VoIP number of submodules is determined the
required number of channels for servicing calls. A call between twoVoIP interfaces orSIP subscribers use
two channels of the VoIP submodule.
Quantity dataVoIP channels supported by the submodule, depending on the codec type, are given in
the sectionMain technical parameters.
-When calculating, it must be taken into account that the number of free channels at28 simultaneous
interceptions will be limited, this limit is shown in the table below. For example, when using the
codecG.711 for voice transmission to three VoIP submodules will remain free Total108 channels.
Table D1 - Number of free channels when using SORM for various codecs
Codec / packetization time Number of free channels when using3x submodulesVoIP

and occupying all 28 channels in the stream SORM
G.711 (A/U) / 20-60 108
G.711 (A/U) / 10 76
G.729A/20-80 48
G.729A/10 42
G.723.1 (6.3 Kbps, 5.3 Kbps) 42
G.726/20 66
G.726/10 60
T.38 38
620
5.5.2 The logic of the operation of setting up for control and interception of calls
SORM PU SORM is connected via flow E1 and, if necessary, over TCP/IP.
-Connection viaTCP/IP is only available from version 3.7.0.
Initially, a command to start the technical means of SORM is given from the SORM launcher. Then there is a
fixation of the CSL groups (channel intervals of the flow E1 for listening to calls) for co-located (in both
subscribers are heard in one CI) or separate (one subscriber in one CI, the second in another) control. One
group of KSL is used either only for combined or only for separate control.
Next comes "placing a subscriber under control" (teamNo.5). Pinning on control goes to format E.164:
• Russian numbers <7>+<city code>+<phone number>;

• international numbers <country code>+<city code>+<telephone number>;
• special service - 2-3 digits.
The operator selection code (the subscriber selects through which operator to make a call with
each mg/mn call by dialing a special code) is never included in the command.
The number received in the command is converted according to the modifiers of the incoming numbers on the SORM stream. Next
comes the analysis of the correctness of the parameters received in the command: the correspondence of the object type (a subscriber
of a given station, a network subscriber by a complete/incomplete number or a bundle of channels) and a sign of a number (a
subscriber of a given station, a subscriber of Russia, a subscriber of another country or a special service), the number of the KSL group
with type of control (combined/separate), the specified length of the number with the number of digits in the number.
The correspondence between the type of control and the sign of the number is as follows:
• the object type "subscriber of this station" can only have the sign of the number "subscriber of this
stations";
• object type "network subscriber by full/incomplete number" can have the attribute "subscriber Russia”,
“subscriber of another country”, “special service”. It is not allowed to put on control by an incomplete
number with the sign "subscriber of this station";
• the object type "bundle of channels" is put under control without a sign of a telephone number.
After that, the received number, type and attribute are compared with prefixesZero Plan CdPN numbering.
The sign of the prefix is determined by the parameter "direction":
• local, zonal and long-distance – Russian subscriber;
• international – subscriber of another country;
• special service - special service;
• SIP-subscriber or prefix indicates TG with set flag "local direction” (the direction
parameter is ignored) – subscriber of this station.
If a suitable subscriber/prefix is found, then we confirm the command and enter the number and its
parameters in the SORM database. Otherwise, we reject the execution of the command with an indication of
the error code, due to which the control did not occur.
This completes the control. Starting from the next call will be carried out "call pickup» controlled
subscriber.
Regardless of which numbering plan the call is in, numbers are checkedCgPN and CdPN with the SORM
database, before checking the numbers with the SORM database, you can make a modification using
modifiers"Modifiers of controlled numbers". Rooms are checked after modifiers for incoming
communication to the TG orPBX profile. If the number is on control, select
621
for it CSL in accordance with the type of control and issue to the PU information about the stages of establishing a
connection (41-44).
When monitoring network subscribers and channel bundles, numbers in messages41-44 will be broadcast after
modifiers for incoming communication to the TG orPBX profile and after modifier for outgoing numbers on the
SORM stream.
When monitoring local subscribers, the caller's number (CgPN) will also be issued after modifiers for
incoming communication on the TG and inPBX profile, and after the modifier for outgoing numbers on
the SORM stream. Called party number (CdPN) will be issued:
• before transformations on the incoming connection on the trunk or in the PBX profile and before the modifier
outgoing numbers on the SORM stream if the number is controlledCgPN;
• after the incoming link modifier on the trunk or in the PBX profile and after the modifier outgoing
numbers on the SORM stream if the number is controlledCdPN, as well as under control numbers
CgPN with the "Modify to number always" flag set on the SORM stream.
Number signCgPN for external subscribers will be set in accordance with the parameter "Direction"
prefixesCdPN of the zero numbering plan.
Number signCdPN in messages will be set in accordance with the "Direction" parameter prefixesThe CdPN
of the numbering plan in which the call was handled.
5.5.3 Methodology for configuring SMG for passing the SORM protocol in accordance with the OrderMinistry of Communications of the Russian
Federation from11/19/2012 N 268
Putting on control- receiving from PU SORM command No.5 with the number of the subscriber who needs
to be controlled as well as its control parameters. If there is a subscriber in the configuration, his number
and control parameters are entered into the internal database of the device, and a confirmation of the
successful execution of the command will be sent to the SORM CP. If the subscriber number is missing in
the configuration or any parameters in command No.5 were set incorrectly, on the PU SORM will send a
message about the failure of this command.
Call Pickup- transmission of messages to the SORM PU about all stages of establishing a connection
of a subscriber put under control (listed in the internal database of the device).
To successfully pass the function of operational-search activities, you must make the following settings:
• Make sure the gateway is set toat least twosubmodules SM-VP-M300. Quantity installed submodules
can be viewed inWeb configurator in the section"VoIP monitoring submodules"(chapterMonitoring
switch front ports);
• Update the software to a version of at least V.3.0.0.960, and when using the connection to the SORM PU,
protocolTCP/IP - for version not less than V.3.7.0.1944;
• Install SORM license and registration of SIP subscribers;
• Organize the E1 flow between the SMG media gateway and SORM PU of special services:
• expand flow E1;
• enable the flow in the gateway configuration;
• select the SORM protocol in the gateway configuration on the stream;
• select specification RUS Order 268 in the gateway configuration on the SORM stream;
• make sure that channels 1 and 2 are set to channel modeDTE(section Setting signaling protocol
SORM), inform the intelligence officers that they must set the mode on their equipment"DCE";
• make sure that there is no increase in the counters of positive and negative slips on the thread
(chapterFlow MonitoringE1).
-After selecting the SORM protocol on one of the streams, it is necessary to restart the software.
622
• Set up call routing in accordance with the requirements of the Order of the Ministry of Communications of the Russian Federation dated
11/19/2012No.268, or set up SORM number modifiers for sending and receiving from remote control SORM phone numbers in a
format that meets the requirements of the Order of the Ministry of Telecom and Mass Communications of the Russian
Federation dated11/19/2012No.268.
In the Order of the Ministry of Telecom and Mass Communications of the Russian Federation dated11/19/2012No.268 describes the number format in
which subscribers must be assigned for control, and requirements for issuing A and B numbers in messages about intercepting subscribers' calls.
Station subscribers, local and long-distance subscribers are assigned for control and are transmitted in
interception messages in the format11 digits with a 7 prefix at the beginning of the number.
International subscribers are assigned for control and transmitted in interception messages without
an international network access prefix (without a prefix810).
Call routing must be configured in accordance with the requirements described above, all calls, except for
calls to international destinations and special services, must be made usingeleven- ty digits with prefix7. For
the convenience of subscribers registered on SMG, it is necessary use functionalityPBX profiles and incoming
modifiers so that subscribers can still dial short5-7-digit numbers within the city and make calls to cellular
operators and long-distance directions with a prefix8. The same needs to be configured for transit calls using
incoming link modifiers on trunk groups.
-When intercepting a call from a monitored local subscriber A to the SORM console, subscriber
B's number is given in the form in which it was received from subscriber A (before all
transformations).
5.5.4 An example of setting up SMG for delivery under the SORM protocol Order of the Ministry of Communications of the Russian
Federation dated 11/19/2012No. 268 without using modifiers on the SORM stream
Consider settingSMG on the example of the following task:

Initial data:
• The operator is located in Novosibirsk, area code383.
• The number capacity is assigned to the operator2724000-2724999.
• The operator istransit terminal.
• Subscribers 2724000-2724199are SIP subscribers registered on SMG.
• Subscribers 2724200-2724399are the operator's subscribers located on the SMG-connected along
the E stream1 station (Avaya).
• Subscribers 2725000-2725999- these are transit subscribers of another operator connected to the GTS
through our operator.
• To access intercity and international destinations, some subscribers use channels of the
operator Rostelecom, and part of the channels of the operator TTK.
The example will consider the option of setting up routing to the format of assigning numbers to control, described in the Order
of the Ministry of Communications of the Russian Federation dated11/19/2012No.268.
-In the Order of the Ministry of Telecom and Mass Communications of the Russian Federation dated11/19/2012 N 268 signs local,
zonal, intercity combined into one feature TfSSOP of Russia =04H.
623
The format for assigning numbers for control in accordance with the Order of the Ministry of Communications of the Russian Federation dated11/19/2012No. 268:
• numbers of station subscribers (operator subscribers) are assigned for control by 11 digits with
prefix7, sign -"Station Subscriber"Object type -station subscriber.
• local, long-distance, zone numbers are assigned for control by 11 digits with a prefix
7, sign -"TfSSOP of Russia",Object type -"network subscriber is full".
• international numbers are assigned for control without 810, sign -"TfSSOP of another country", Object
type -"network subscriber is full".
• numbers of special services are assigned for control by 2-3 digits, sign"special services", Object type
"network subscriber full".
-Local, long-distance, international, zonal and special services subscribers can be assigned for control
with the type of object “network not full number”, while a part of the number is put on control.
Solution:
5.5.4.1 Setting up the numbering plan in accordance with the requirements of the Order of the Ministry of Communications of the Russian Federation dated
11/19/2012 N 268:
INSMG created 2 dial plans to separate dialing into long distance and international directions to different
operators, for calls between subscribers of different numbering plans, prefixes for changing the numbering
plan have been created.
Numbering plan #0 is used by SMG SIP-subscribers who, for access to long-distance and international
destinations use the channels of the operator Rostelecom, numbering plan #1 is used by subscribers
who use the channels of the TTK operator to access long-distance and international directions.
Consider the Numbering Plan00.

Suppose we have a numbering plan of the following form:
Necessary:
• Prefix#00 – in accordance with the format described above, numbers should be put under control By
11 digits, so you need to replace the number 8 with 7 in the mask, the type of direction is necessary
set "intercity";
• Prefix#01 - local prefixes are not used, you must add the number 7 to the mask and the code cities
383 to get the required 11 digits prefixed with 7, set priority to 95 and type directions "local";
-After changes Prefix #00 and #01 will overlap if prefixes are set to different trunk groups, calls can
go in the wrong direction, so on Prefix#01 must be set to a lower priority than was set on
Prefix #00.
624
• Prefix#02 – international numbers are put under control without "810", must be removed from the
mask numbers810, direction type "international";
• Prefix#03 – describes sets for special services, this prefix fully complies with the Order Ministry of Communications of the
Russian Federation from11/19/2012 N 268 and remains unchanged, the type of referral is "special service";
• Prefix#04, Prefix#05 and Prefix#13 - you need to add the number 7 and the area code 7383 to the mask in
order to get the required11 digits with prefix 7, direction type "local".
After all the transformations, the numbering plan should look like this:
Numbering plan #1 corresponds to dial plan 00, except that exit prefixes on long-distance and international
directions lead to the trunks of the TTK operator. You need to make similar changes to the numbering plan #
1.
Was:
It became:
-Subscribers are placed under control only according to the zero numbering plan and only by numbers
CdPN (prefix type trunk group or trunk direction) or by additional number in the zero numbering
plan. In other words, the search for the number received from the PU SORM in command No.5
(“Putting the object under control”) will be carried out amongSIP subscribers and CdPN prefixes of
the zero numbering plan.
If the setting for control was successful, then the interception of calls will be carried out from all
numbering plans.
5.5.4.2 Setting up SIP subscribers
-To be able to control allSIP subscribers must be migrated to plan 0 numbering. The implementation of
outgoing calls from subscribers through other numbering plans is organized using modifier tables
(in the "Modification general" section, the desired numbering plan is indicated). A modifier table with
rules for transferring a call to another numbering plan is assigned inPBX profile.
When assigned to control subscribers with the attribute and object type"subscriber of this station" checks if
the station existsSIP subscriber with this number or prefix, within the range which the fixed number will fall;
a trunk with the "Local direction" flag must be assigned on the prefix.
625
After the changes in the previous section, the dial plan is designed to be routed by11 digits so you need to
change the numbers toSIP subscribers from 7 digits to 11 digits with prefix 7.
RoomsSIP subscribers are configured in the section"Subscribers/SIP-subscribers":
Next, you need to configure modifiers for converting numbers for incoming and outgoing calls and assign
them to trunk groups (modifiers for incoming calls are needed to bring dials and caller IDs to the numbering
format configured on the station, and for outgoing calls
– to return dialing and caller IDs to the format used on the network).
626
5.5.4.3 Configuring incoming and outgoing number A and B number modifiers
To configure incoming and outgoing converters, you must remove call traces in all directions. Traces can
be captured inSMG web configurator, section "traces/PBX- tracing".
Set log levels: calls =99, SS7 = 1, SIP = 1, Q.931 = 1, press the start button, perform sets to all directions and
back, then stop logging (press the button "Complete")and analyze the information received.
Consider the option of setting up modifiers for transit calls. Interaction with
Rostelecom
Rostelecom sends A number via incoming connection10 digits, you need to add the number 7 to it, To obtain
11-digit number with 7, as a rule, caller IDs from international destinations are sent no numbers"810", so
they do not need to be converted.
627
Rostelecom sends B number via incoming connection7 digits. You must add the area code 7383 to it.
Let's create two modifiers, the table is below.

Table D2 - Rostelecom modifiers, incoming communication
Name Mask modifCDPN (Number modifCgPN (Number

B) A)
In_a_operator (xxxxxxxxxx) +7
In_b_operator (xxxxxxx) + 7383
(xxxxxxxxxx) +7
Modifiers are created in the "Internal Resources/Modifier Tables» (chapterModifier tables):
628
Modifiers are assigned to trunks in the sectionRouting/Trunk Groups(chapter Trunk groups):
The screenshot shows a Rostelecom trunk as an example, the corresponding procedure must be
repeated for each trunk (assign a modifier corresponding to the trunk).
-The new dial plan, after the changes in the previous section, is configured to be routed by 11 digits. To
interact with oncoming stations, you need to return the numbers to the former look.
On outgoing calls to Rostelecom, the opposite station is waiting for A number10 digits. Therefore, it is necessary
from11-digit number cut off the first digit.
629
On outgoing calls to Rostelecom, the opposite station expects:
• 7 digits when dialing to a local number. Therefore, in order to compensate for the changes made to incoming
connection must be deleted4 digits from the beginning of the number;
• 11 digits with exit prefix 8 for long distance dialing. In this case you need to replace the first
digit7 by 8.
• international dialing with exit prefix "810" (length varies according to depending on the
country). In this case, add "810" to international numbers.
Let's create two modifiers, the table is below.

Table D3 - Rostelecom modifiers, outgoing communication
Name Mask modifCDPN( modifCgPN (Number

Number B) A)
out_a_operator (7383xxxxxxx) -
out_b_operator (7383xxxxxxx) ----
(7xxxxxxxxxx) -+8
(x{10,22}) + 810
Interaction with TTK

TTK sends A number on incoming communication10 digits. You need to add the number 7 to it for
local and long distance calls and leave it unchanged for international calls.
TTC sends B number on incoming connection7 digits. You need to add the area code 7383 to it, To
obtain11 digit number.
On outgoing communication to the TTK, the oncoming station is waiting for A number10 digits. Therefore, it is necessary
from 11- digit number cut off the first digit.
On outgoing communication on the TTK, the opposite station expects:
• 7 digits when dialing to a local number. Therefore, it is necessary to remove 4 digits from the beginning of the number;
digit7 to 8;
• international dialing with exit prefix "810" (length varies according to depending on the
country). In this case, add "810" to international numbers.
-Since the number format on the trunks of Rostelecom and TTK is the same, you can use it for TTK
trunk the same modifiers that were created for Rostelecom trunks.
630
Interaction with the Client1
Incoming connection Client1 sends A a number of 10 digits. You need to add the number 7 to it for local
and long distance calls and leave it unchanged for international calls.
Incoming connection Client1 sends number B:
• 7 digits when dialing to a local number. You must add the number 7 and the area code 383;
digit8 to 7;
• international numbers with exit prefix "810". In this case, you need to delete "810" from an
international number.
Let's create two modifiers:
Table D4 - Client modifiers 1, incoming connection
Name Mask modifCDPN (Number modifCgPN (Number A)

B)
In_a_type_2 (xxxxxxxxxx) +7
In_b_type_2 (xxxxxxx) + 7383
(8xxxxxxxxxx) -+7
(810x{10,22}) ---
-In this example, sets from clients are considered, so the options for incoming communication several:
local, intercity and international. Sets for special services are not considered, as sets from special
services are processed without changes.
Outgoing communication to the Client1 oncoming station expects number A 10 digits. Therefore, it is necessary to cut
off the first digit from the 11-digit number.
Outgoing communication to the Client1 oncoming station expects number B 7 digits. Therefore, it is necessary delete4
digits from the beginning of the number.
Let's create two modifiers, the table is below. Table D5 -

Client modifiers 1, outgoing communication
Name Mask modifCDPN modifCgPN

(Number B) (Number A)
out_a_type_2 (7xxxxxxxxxx) -
(x{10,22}) + 810
out_b_type_2 (7383xxxxxxx) ----
631
InteractionAvaya
According to the conditions of the task, subscribers located at the stationAvaya, are our subscribers,
therefore, they must be assigned to the SORM control with the type of object and the sign of the number
“station subscriber”, therefore, on the trunkAvaya needs to flag"Local direction".
-The "Local direction" flag on the trunk allows you to assign and generate external numbers with the type of object
and the sign of the number "Subscriber of the station".
Incoming callAvaya sends number A 7 digits. You need to add the area code 7383 to it. Incoming callAvaya
sends number B:
• 7 digits when dialing to a local number. You must add the area code 7383 to it;
digit8 to 7;
• international numbers with exit prefix "810". In this case, you need to delete "810" from an
Outgoing call toAvaya opposite station expects A number 10 digits. Therefore, it is necessary from 11- digit
number cut off the first digit.
Outgoing call toAvaya opposite station expects B number 7 digits. Therefore, it is necessary delete4 digits
from the beginning of the number.
-Since the format of numbers on the Client's trunks1 and Avaya match, can be used for trunkAvaya
same modifiers as created for Client 1 trunks.
The exception is the format of the number A fromAvaya on inbound, need to modifier In_a_type_2add
mask (xxxxxxx) and modification rule CgPN +7383.
SIP subscribers SMG
On incoming communication to the stationSIP subscribers send A number 11 digits (we changed SIP
subscriber numbers in the SIP Subscriber Settings section), so there is no need to convert it.
Incoming callSIP subscribers dial Number B:
• 7 digits when dialing to a local number, you must add the area code 7383;
• 11 digits with exit prefix 8 when dialing to long distance, need to be replaced first digit8 to 7;
• international numbers with exit prefix "810", you need to remove "810" from
-All number conversions for outgoing calls toSIP subscribers were previously configured in trunk groups.
No additional transformations need to be configured.
-Since the format of the setsSIP subscribers matches the number format from the Avaya trunk, you
can use the modifier to modify number Bin_b_type_2.
632
ForSIP subscribers number modifiers for incoming calls are assigned in the sectionSubscribers/PBX profiles"
(chapterInterfacesSIP/SIP-T/SIP-I, SIP profiles).
-The modifier must be assigned to allPBX profiles.
The example was given for a special case of the Novosibirsk network, in each specific city the situation will
differ in the city prefix, the number of digits in the local number, etc.
5.5.4.4 Assigning numbers for control

When assigned to control the number, the FSB officer indicates the sign of the number and the type of object.
Object types:
• station subscriber (SIP subscribers and external subscribers behind a trunk with a flag
"Local direction");
• network full number (external subscribers, the trunk should not have a flag"Local
direction");
• the network is not a complete number (external subscribers, the flag should not be on the trunk"Local
direction");
• bundle (the entire trunk is put under control).
633
Number features:
• station subscriber;
• TfSSOP of Russia;
• PSTN of another country;
• special services.
Options for assigning numbers to control: Assignment

to the control of the subscriber of this station
The station compares the number received in the arming command with the numbersSIP subscribers or
prefixes, within the range of which the assigned number falls. If the subscriber is external (connected via
flow E1 or SIP trunk), on the prefix that the assigned number,mustbe assigned to a trunk with a flag"local
direction"otherwise, the number will not be fixed.
-The "Local direction" flag must be set only on those trunk groups, through which the operator's
numbering capacity is connected. Setting this flag on trunk groups from which local, long-distance
and international calls come from will result in setting incorrect object types and number signs in
intercepts.
Assigning a network subscriber with a full number to control

The station compares the number received in the arming command with the prefixes within the range of
which the assigned number falls. The sign with which the number is assigned to the control must
correspond to the parameter"Direction"on the prefix. Also on the prefixshould notbe assigned to a trunk
with a flag"Local direction".Otherwise, the number will not be fixed.
Assigning to control a network subscriber with an incomplete number
Assigning a network subscriber with an incomplete number to control complies with the rules for assigning a
full number.
Attachment to control beam channels
The station checks if a trunk group exists with a matching bundle ID. Before putting a bundle of channels
under control, FSB officers usually first request a list of all bundles using command No.16.
-INThe web configurator displays only serial numbers of trunks, which may not be match real IDs.
-The numbers in the call are checked against the numbers assigned for control after transformations by incoming
communication and before transformations on outgoing communication.
- • The factory password for connecting to the SORM interface of the SMG media gateway is
123456, this password can be changed by FSB officers using command no.3. In if the
SORM interface is stopped (receiving command No.2) or software restart media gateway,
the password will be reset to factory default.
• On the SMG, it is possible to use only one E1 stream to connect to the SORM PU.
634
-PU SORM takes synchronization from the threadE1 operator equipment. In case of use modems for
organizing the flowE1 to PU SORM, it is necessary to correctly position the Master/Slave modems.
The Master modem must be located on the SMG side, the Slave modem on the sides of PU SORM.
- • In version 3.2.0 and later, when passing the SORM, it is necessary to implement the VDO only
by means of subscriber gateways.
• Setting of subscribers for control is carried out only according to the zero numbering plan and
only by numbersCdPN (prefix type trunk group or trunk direction). In other words, the search
for the number received from the PU SORM in command No.5 ("Staging object for control")
will be carried out amongSIP subscribers and CdPN prefixes zero numbering plan.
If the setting for control was successful, then the interception of calls will be carried out from
all numbering plans.
• The feature of the phone number in messages 41-44, 51, 52 is given based on the analysis
parameter"Direction",configured in the appropriate prefixZero Plan CdPN numbering.
• local network, zonal network, long-distance communication correspond to the sign of the number
04H (subscriber of PSTN of Russia);
• international communication - 05H (PSTN subscriber of another country)
• special service - 06H (emergency and reference services) /
5.5.5 Symbols and codes of fields in SORM messages
5.5.5.1 Symbols and codes of alarms

When flow accidents occur E1 (loss of signal (LOS), remote alarm (RAI) and alarms "RelaunchSIP-adapter”) a
message will be sent to the SORM consoleNo.1 with corresponding code accidents.
Table D6 - Designations and codes of accidents
Code (Dec) Code (hex) Description
01 01H E flow failure1 loss of signal (LOS);
02 02H remote E flow alarm1 (RAI)
03 03H restartSIP adapter
635
5.5.5.2 Supplementary service service designators and codes Table D7 —

Designations and codes of VET services
Code (Dec) Code (hex) Name of VVO service Description
32 20H Any call forwarding Issued when the flag "Allow forwarding (302)"
in the SIP setting interface and the absence of
All CF VAS settings in the subscriber's parameters
33 21H Call Forward Unconditional It is issued when setting up the VAS "Forwarding
unconditional" in the parameters of the subscriber's VAS
CFU
40 28H Any conditional call forwarding Issued when setting up the VAS "Forwarding on
unavailability", "Forwarding on schedule", "Follow
me", "Follow me (on no answer)" in the VAS
All ConfCF parameters of the subscriber
41 29H Call forwarding on busy Issued when setting up the VAS "Forwarding on
Busy" in the subscriber's parameters
CFB
42 2AH Call Forward on No Answer It is issued when setting up the VAS "Forwarding on no
answer" in the VAS parameters of the subscriber
CFNRY
49 31H Call Transfer It is issued when setting up the VAS "Call transfer"
in the parameters of the VAS of the subscriber or
CT when setting the flag"Allow message processing
REFER"in the SIP setup interface in the absence of
VAS settings in the subscriber's parameters
50 32H Call Pickup It is issued when setting up the VAS "Call Interception" in
the parameters of the VAS of the subscriber
CP
51 33H Getting help during a call It is issued when setting the VAS "Call Hold" in the
parameters of the VAS of the subscriber, or when
setting the flag "Allow processing Re-INVITE
SS ca=sendonly» in the SIP setup interface in the
absence of VAS settings in the subscriber's
parameters
636
Code (Dec) Code (hex) Name of VVO service Description
66 42H Call Hold It is issued when setting the VAS "Call Hold" in
the VAS parameters of the subscriber or when
HOLD setting the flag"Allow processingRe-INVITE with
a=sendonly"in the SIP setup interface in the
absence of VAS settings in the subscriber's
parameters
80 50H All multilateral Issued when setting up the VAS

conferences "Conference with sequential collection" in
the parameters of the subscriber's VAS
CONF
82 52H Three way communication Issued when setting up the VAS "Three-party
conference" in the VAS parameters of the subscriber
3PTY
5.5.5.3 Reasons for non-acceptance and non-execution of commands
Table D8 - Reasons for not accepting commands sent in message 7, defined in the Order Ministry of Communications of the
Russian Federation from11/19/2012 N 268
Code Code Description

(Dec) (Hex)
0 00N Command accepted for execution
1 01H The command was rejected due to an incorrectly specified command format or incorrectly
specified command parameters from the ORM control point
2 02N The command was rejected due to the task of the command before the launch of the ORM technical means
Table D9 - Reasons for not executing commands sent in message 8, defined in the Order Ministry of Communications of the
Russian Federation from11/19/2012 N 268
0 00N Command completed successfully
1 01N Command failed
3 03N Command failed due to incorrect password
5 05N The command was not executed due to the wrong "number
of ORM technical means"
637
7 07N Command failed because ORM technical means launched
Table D10 - Reasons for non-acceptance and non-execution of commands sent in messages 7 and
8, defined inSMG
16 10N Command not accepted: wrong length (or wrong number

of characters in the number)
17 11H Parameter(s) Error
18 12N Invalid object type
19 13H Invalid number type
20 14N Wrong category
21 15N Priority error
22 16N Command not accepted: SORM has already started
23 17N Command not accepted: SORM is not running
24 18N Command not accepted: invalid SORM number
25 19N Invalid number length
32 20N Neither the number nor the trunk was specified when setting up for control
33 21H Aborted by PU command
37 25H Trunk group not set
45 2DH Command not accepted: executing a previously issued

command
48 30H The group is defined by a different type
49 31H Objects table is full, monitoring has not started
638
50 32H There is no such CSL in the specified group
51 33H Object already set
52 34H Invalid item number
53 35N Call number not found
54 36H Number already set
55 37H Object number is not suitable for the command
56 38H Wrong object type or wrong number type
57 39H Output already completed (response to command to stop output)
58 3AH KSL-A is already fixed
59 3BH Matches number
61 3DH Invalid object number (when connecting to a connection,

when disconnecting)
62 3EH Invalid KSL group number (no such group, group is busy)
63 3FH Invalid KSL-A number
64 40H KSL does not match (invalid KSL) incorrect number KSL-B
65 41H Invalid number of KSL-A and KSL-B Command error
68 44H The number of digits does not match
71 47H The trunk number is not set for the object of type "trunk"
72 48H Both object number and trunk number are set
73 49H Trunk with this number not found
74 4AH Such a trunk is already controlled
639
75 4BH The total number of monitored trunks has reached10
76 4CH Trunk number does not match the previously specified
78 4EH Trunk number specified for the wrong object type
83 53H No number or direction found
84 54H Port is not local
85 55H The sign of the number is incorrect
86 56H Wrong object type for local port
87 57H An invalid license plate attribute was sent for the given number
95 5FH No KSLs were selected (no KSLs matching your query)
97 61H DVO not set
115 73H CSL allocation error
5.5.5.4 Subscriber set status information in the messageNo.3

In case of receiving a request from the SORM CP to transfer data on control objects (command No.10) in
answer fromSMG will send a messageNo.3(23H). In the last, twentieth byte of this message information
about the state of the subscriber set will be transmitted. This parameter can take the values shown in the
table below.
Table D11 — Subscriber set states in the messageNo.3
Code (Dec) Code (hex) Decryption Description
0 00H The subscriber set is in good This status is issued if the subscriber is
condition and the control object has registered on the device. The service mode
no restrictions on the use of in the subscriber's parameters is set to
outgoing / incoming communications "enabled"
7 07H The control object has This status is issued if the subscriber is
limited opportunities when using registered on the device. The service mode
outgoing / in the subscriber's parameters is set to a
incoming communication value other than "enabled"
640
Code (Dec) Code (hex) Decryption Description
255 FFH Status Information This state is displayed for objects with control
kit not available type02H (full control number),12H (control by
incomplete number) and03H (channel bundle
control), then available for non-local
subscribers
5.5.6 Description of the operation of the option “Analysis of the operator selection code”
In accordance with the orders of the Ministry of Telecom and Mass Communications, the subscriber can
choose the operator through which he will make a long-distance or international call. To do this, the
subscriber is assigned a category of caller ID0, he dials in the form 8 <operator code> <phone number>, but
pinning to number B is controlled in format E.164: Russian numbers <7>+<city code>+<number phone
number>, international numbers <country code>+<city code>+<phone number>, that is, the operator
selection code is never included in the command. Exists13 Operators Set to Set codes.
Table D12 - Codes of various telecom operators
Operator Intercity International Universal code CategoryCPC

code code 8-15-XX
Rostelecom" 55 10 55 1
JSC "Mobile 23 28 23 2
TeleSystems»
OJSC Vimpelcom 51 56 51 3
OOO "Orange Business 54 59 59 4

Services»
ZAO TransTeleCom 52 57 57 6
ZAO Synterra 22 27 22 7
JSC "ARKTEL" 21 26 21 8
JSC Interregional 53 58 19 9
TransitTelecom»
O.S.S.-Telecom LLC - - 14 -
JSC "MegaFon" - - 15 -
ZAO OptiTelecom - - 16 -
641
Operator Intercity International Universal code CategoryCPC

code code 8-15-XX
OOO MOTIV (cellular - - 17 -

connection)"
OOO "CONNECT" 24 29 20 -
At the same time, the subscriber, depending on where (mg or mn) and through which operator he calls, has the right to dial
the number in different ways.
In modepre-select,when the subscriber makes a choice in favor of one operator and uses only it services,
the dialing order is preserved:
• 8-[beep]-АВС-ххх — for a long-distance call, (where: АВС — area code, ххх — subscriber's number);
• 8-[beep]-10-country code-xxx — for an international call (where: xxx — area code and subscriber's number).
In modeHot Choicethe subscriber chooses an operator for each call:

• 8-[beep]-[intercity code of the operator]-ABS-xxx - for a long-distance call (where: ABC - code city,
xxx — subscriber number);
• 8-[beep]-[international operator code]-country code-xxx - for an international call (where: xxx - area
code and phone number).
or
• 8-[beep]-15-[universal operator code]-8-ABC-xxx - when making a long distance call (where: ABC - area
code, xxx — subscriber number);
• 8-[beep]-15-[universal operator code]-810-country code-xxx — for an international call (where: xxx -
area code and subscriber number).
When calling mobile phones from landlines with federal numbers, the same rules apply:
• 8-[beep]-[intercity operator code]-xxx-xxxxxxx (xxx-xxxxxxx – mobile phone);

or
• 8-[beep]-15-[Universal Operator Code]-xxx-xxxxxxx (xxx-xxxxxxx is a mobile phone).
The principle of operation of the option is that the device analyzes the dialing of numbers by the subscriber in the
format:
• [7|8]-[operator's area code]-xxx...

• [7|8]-[international operator code]-xxx...
• [7|8]-15-[Universal Operator Code]-xxx...
and when transmitted to the SORM console, the operator selection code is deleted.
642
5.6 Appendix E. Interaction of the device with monitoring systems
To be able to track in real time emergency situations that occur on the device, you need to configure the
work with the monitoring system.
The absence of any alarms is considered normal operation, when an alarm event occurs, the state of the
device changes to emergency, when all current alarms are normalized, the normal operating state is
restored.
Possible device status indications:
• light indication on the front panel - LEDAlarm(LED indicationAlarmdescribed in sectionLight indication),
• indication of the most critical failure in the header of the web configurator (more detailed
information listed in the work log)
• transmission of events about accidents to the monitoring system via the SNMP protocol (trap, inform).
The events by which alarm conditions are generated are divided into unconditional and optional:
• Unconditional– accidents, the indication of which is not configurable, these include:
• CONFIG– critical accident, configuration file failure;
• SIPT-MODULE– critical failure, failure of the software module responsible for the operation of IP-
telephony;
• SM-VP DEVICE– accident, failure of the SM-VP IP submodule;
• SYNC– an accident when the synchronization source is lost, or a warning during operation from a
low priority clock source;
• CDR-FTP– critical accident, accident or warning, occurs when an error occurs data
transmissionCDR to FTP server, the crash level is determined by the amount of CDR data
awaiting transmission to the server;
• PM-POWER-STATE- a warning about the absence of voltage at the output of one of the
installed power supplies.
• Optional– alarms, the indication of which is configured by the corresponding settings, these
include:
• STREAM– critical accident, flow E1 is not in operation;
• STREAM REMOTE– warning, remote E1 flow alarm;
• STREAM-SLIP-warning, on slippage thread;
These alarms are configured in the settings for the physical parameters of flows E1 (
chapterSetting physical parameters).
• LINKSET– a critical accident, a group of lines OKS-7 is not in operation;
• SS7LINK– accident, problems on the OKS-7 signal channel;
• TRUNK-CPS– exceeding the specified number of calls per second on the trunk group.
These alarms are configured in the SS-line group settings.7 (sectionGroups of lines OKS-7).
By default, indication of optional alarms is disabled, i.e. when interacting with monitoring systems, it is
necessary to configure the indication of alarms for all flows included in the work E1 and groups of lines
OKS-7 (Linkset).
To interact with the monitoring system using the protocolSNMP must be enabled on the device protocolSNMP
and configure the issuance of SNMP TRAP or INFORM messages to the IP address of the server monitoring.
643
Parameter setting viaweb configurator
1. Setting the indication of optional alarms when configuring the E1 stream (menu"Flows E1/ Physical
parameters», see sectionSetting physical parameters).
For alarm indicationLOS, AIS on the E1 stream, you need to set the flag"Alarm indication". For
alarm indicationRAI need to set the flag"Remote Alarm Indication".
For slip indication (SLIP) on the stream, you must set the flag"SLIP indication"and set the SLIP
discovery timer.
2. Setting the indication of optional alarms when configuring a group of SS-7 lines (Streams menuE1/
Group of lines OKS7", chapterGroups of lines OKS-7).
To indicate an accident about the inoperability of the OKS-signal link7 need to install flag"Indication
of an accident".
644
3. SNMP protocol is enabled in the menu"TCP/IP Settings/Network Settings" (chapterNetwork settings
).
To configure, set the flag"UseSNMP.

4. Setting up the issuance of SNMP traps is done in the menu"Network Services/SNMP"(chapter
SettingsSNMP).
To configure, you must specify the typeSNMP messages (TRAPv1, TRAPv2, INFORM), password
(Community), IP address and port of the SNMP trap receiver.
After setting up and applying the configuration, you must restartSNMP agent by clicking on button
"RestartSNMPd".
645
5.7 Appendix G. Voice messages and music on hold MOH
By default, the device has phrases for issuing voice messages and for issuing a melody on hold (Music on
Hold). Issuing a message occurs on a specific event, the list messages and their correspondence to a
particular event are presented in the table below.
Table G1 - MOH messages and events
Name Decryption Event
TRUNK_BUSY "Congestion in this direction" There are no free channels on the

outgoing direction.
Outgoing channels are blocked or down.
Upon receiptQ.850 cause = 34
NUMBER_FAIL "Wrong number dialed" When calling a non-existent prefix
Upon receiptQ.850 cause = 3, 28
ACCS_DENIED_TEMP "The number is temporarily unavailable" When calling an unregistered

subscriber
ACCESS_RESTRICT “This type of communication is not included in the list Restriction of incoming communication at
of services from your device” the subscriber
Call restriction by access category
USER_UNALLOCATED "The subscriber's device is not connected to When calling a prefix with the
the station" "modifier" type
USER_CHANGE "Subscriber changed number" Upon receiptQ.850 cause = 22
MOH Music on hold When placing a subscriber on hold
The management of the issuance of voice messages is located in the trunk group settings and in the settingsPBX-
profiles for subscribers.
MessageMOH is issued unconditionally, regardless of the settings.
646
5.8 Appendix H. Working with VAS services

configurability
On the device, starting from the software versionOn 2.15.01, the following services were implemented:
• Forwarding unconditional– activation of unconditional forwarding service(CF Unconditional);

• Forwarding on busy– activation of call forwarding on busy service(CF Busy);
• Forward on no answer– activation of call forwarding service on no answer(CF No reply);
• Redirect on unavailability– activation of call forwarding on unavailability service(CF Out Of Service);
• Call hold (Call hold);

• Call Transfer– activation of the call transfer service(Call Transfer);
• Trilateral Conference (3Way). Call pickup;
• Collection Conferencing (CONF);
disabled when the initiator leaves the conference. Otherwise, the conference will be saved after the
initiator hangs up and will be disconnected only when the last participant leaves it;
• Intercom call– call service with automatic answer of party B;

• Paging callOV– the service is similar to an intercom call, but the call is made to the conference
number;
• Change password (PWD);
• Restriction of outgoing communication (Out calls restrict);
• Outgoing communication by password (PWD ACT);
• Password activation (RBP);
• Do Not Disturb (DND) –only for SMG-2016;
• Blacklist– only for SMG-2016;
• Follow me;
• Follow me (on no answer);
• Call Park;
• Setting in the slot;
• Extraction from the slot;
• Voice mail;
• Cancellation of all services.
647
The functionality of VVO services becomes available only after installing an additional license SMG-VAS.
To use VAS services, the subscriber needs to set the flag in the subscriber's settings "Use DVO".
To activate a certain VAS service, you need to set a flag in the subscriber's settings opposite the required
service in the menu"Activation of VET services".
648
5.8.1 Working with "Call Hold", "Call Transfer" and "Three-party Conference" services
To work with the service"Call Transfer"it is necessary that the subscriber terminal side support the
transmissionFLASH over SIP using SIP-INFO, RFC2833 methods. On the side of the subscriber terminal
signaling setup is also requiredDTMF methods inband, SIP-INFO or RFC2833, make sure that the same
method is selected in the subscriber setupSIP profile.
Example of setting up the "Call transfer" service
SubscriberA calls subscriber B, during the conversation subscriber B can press FLASH and put subscriber A
on hold, at this time subscriber A will receive a signal"Music on Hold"and subscriber B will hear the signal
"Station Answer"at this time, subscriber dialing timeouts start workingC, their meanings are given below.
After dialing and answering subscriber C, the following options are possible:
Being in a conversation with a subscriberA, set it to hold with a short lights outFLASH (R), wait for the
“answer station” signal and dial subscriber C. After answering Subscriber C can perform the following
operations:
• R 0 – disconnection of the subscriber on hold, connection with the subscriber who was in touch;
• R 1 – disconnection of the subscriber who is connected, connection with the subscriber who was on
retention;
• R 2 – switching to another subscriber (subscriber change);
• R 3 – tripartite conference;
• R 4 – call transfer, conversational connection is established between subscribers A and C;
• hang-up – call transfer, conversational connection is established between subscribers A and C.
Service timeouts"Call Transfer"– at the moment only default values are set, the configuration of these
timeouts will be implemented in the following software versions:
• timeout for dialing the first digit: 15 sec.
• timeout for dialing the next digit: 5 sec.
• timeout for issuing a busy signal: 60 sec.
5.8.2 Working with the Call Forwarding service

Service configuration"Call Forward"can be done with the appropriate setting inweb configurator in the
menu"SIP-subscribers" / "VAS management" / "Selecting the required subscriber"(chapterFar Eastern
Department) or by using the management of VAS services from a telephone device (according to RD-45),
this method will be described below.
Setting up VAS from a telephone set (according to GOST45.49-96)
The subscriber can install and remove the service by himself using a set of certain prefixes on his telephone
set. Service prefixes"Redirect"are configured in the dial plan (sectionNumbering plan), for this you need to
add a new prefix with the value"Type prefix"/"DVO prefix".
649
For VDO it is recommended to use the following prefix values:
5.8.2.1 Forward unconditional (CF Unconditional):

• installation (*21*|*21*x.#);
• withdrawal (#21#);
• control (*#21*|*#21*x.#).
5.8.2.2 Forwarding on Busy (CF Busy):

• control (*#22*|*#22*x.#).
5.8.2.3 Forwarding on no reply - (CF No reply).

• control (*#61*|*#61*x.#).
5.8.2.4 CF Out Of Service

• control (*#62*|*#62*x.#).
5.8.2.5 Forwarding by Time (CF Time)

• installation (*28*x.#);
650
• control (*#28#|*#28*x.#).
The meaning of the numbers21, 22, 61, 62, 28 can be any, in these examples are recommended values.
-In the numbering plan of the subscriber terminal, prefixes for VET service management. Work
with VAS services on the gateway is carried out after receiving the messageINVITE with the
required combination of numbers from the subscriber terminal.
Service timeouts"Call Forward", at the moment only the values according to By default, the ability to
configure these timeouts will be implemented in the following software versions:
• redirect timeout on no reply – (CF No reply): 10sec;

• CF Out Of Service timeout: 10 sec.
An example of setting up VAS services from a telephone set
Task
The subscriber needs to assign unconditional call forwarding to the number222333444.
Actions
1. The subscriber activates the service by dialing *21*, in response he hears a signalstation answer.
2. You can control the connection of the service by dialing *#21*. When the service is connected, the subscriber will
hear the signalstation answer.When the service is disabled, the subscriber will hear a signal"busy".
3. The subscriber sets the number for forwarding by dialing *21*222333444#, in response he hears a signal
station answer.
4. You can check that the service is connected to a specific number by dialing
*#21*222333444#. If the service is activated and the dialed number matches the one previously set, then the
subscriber will hear a signalstation answer.If the service is not connected or the dialed number does not match
the previously set one, the subscriber will hear a signal"busy".
To deactivate the service, the subscriber needs to dial #21#.

Example of setting up the service "Forwarding by time" Task
The subscriber needs to assign time forwarding within the period from12 to 14 from Mon to Fri to the number
222333444.
Actions
1. In the section Internal resources→ Forwarding by time, you need to create and / or edit the schedule
by checking the boxes on the hours and days of the week on which you want the forwarding to work,
for this example, these are columns12, 13, 14 for lines Mon, Tue, Wed, Thu, Fri
2. In the settings of the sip subscriber on which you want to set up call forwarding, enable VAS
forwarding by time
3. The subscriber sets the call forwarding number and the schedule configured in clause 1 by dialing * 28 *
<number> * <schedule_idx> #, where:
<number> - number to which the call will be forwarded
<schedule_idx> - index of the schedule by which the redirect will be performed for this
example, the set will look like this: *28*222333444*0#
4. You can check that the service is connected by dialing *#28# or *#28*222333444*0#. If the service is
activated, the dialed number and the schedule coincide with the previously set one, the subscriber will
hear a signalstation answer.If the service is not activated or the dialed number and
651
the schedule does not match the previously set one, the subscriber will hear a signal"busy".
To deactivate the service, the subscriber needs to dial #28#.
5.8.3 Sequential conferencing

The service allows the initiating subscriber to create a conference call by sequentially adding participant
subscribers and using subscriber hold for this.
When the initiating subscriber hangs up, the rest of the participants receive a signal"Busy"if the subscriber-initiator
has enabled ADD "Disconnection of the conference when the initiator breaks". If VDO is disabled, then when the
initiating subscriber hangs up, the conference will continue to work. The maximum number of participants for all
assembled conferences forSMG-1016M - 40, for SMG-2016 - 160. B there can be no more than one conference40
participants. For example: on the SMG-1016M you can assemble one conference on40 participants, 10 conferences
for 4 participants, etc. SMG-2016/3016 can host 4 conferences with 40 participants, 10 conferences with 16
participants, etc.
Access to the service is controlled by the flag of the VBO category "Conference with sequential collection".
Usage * 71# <NUMBER 1><FSC> R<NUMBER 2><FSC> ...
Where:
<NUMBERN> – number of the subscriber – conference call

participant; <FSC> – state of the conference; R - short release
(FLASH);
652
5.8.4 Call pickup

The service allows you to answer the call of another subscriber.
Access to the service is controlled by the flag of the VAS category "Call pickup".
Usage * 66 *<NUMBER>#
Where:
<NUMBER> – number of the subscriber whose call is intercepted.
5.8.5 Intercom and page calls

The service allows the subscriber to make a call with the automatic answer of the telephone set on side B.
Please note that the telephone sets used must support the answer modeAnswer-Mode: Auto according to
RFC 5373.
Access to the service is controlled by the flag of the VBO category "Intercom call".
Usage * 80*<NUMBER>#
Where:
<NUMBER> – number of the subscriber to whom the intercom call is being made.
The paging service works similarly to an intercom call, but allows you to make calls to a group of sites using a
conference number. To do this, in the call group settings (sectionCall groups) set a call group with the
conference number and add all subscribers to it, to be called by the service.
Usage * 81*<NUMBER>#
Where:
<NUMBER> is the number of the conference to which the paging call is being made.
5.8.6 Password activation/deactivation, outgoing communication by password
These services give the subscriber the opportunity to circumvent the established restrictions on access to communication services,
those. restrictions set by the VAS service"Restriction of outgoing communication".
For example, if a restriction on outgoing communication is set, then the service"Outgoing communication by
password" makes it possible to cancel the access restriction only for the next attempt to establish an
outgoing connection. Service"Password activation/deactivation"cancels/sets a limit on outgoing
communication for all subsequent outgoing attempts.
Access to the service is controlled by the VAS category flag"Password activation/deactivation". Access to the serviceOutgoing
communication with a passwordis controlled by the flag of the same name of the DVO category.
Passcode - activation * 29 * <PASSWORD> #
Passcode - deactivation #29#
653
Outgoing password communication * 32 * <PASSWORD> #
Where:
<PASSWORD> – subscriber's personal password.
5.8.7 Changing the passcode
This service allows the subscriber to change the passcode assigned by the PBX attendants. Access to the
service is controlled by the VAS category flag"Password change".
Replacement * 30 * <PASSWORD1> * <PASSWORD2> * <PASSWORD2> #
Where:
<PASSWORD1> – valid passcode;

<PASSWORD2> is the new passcode, you need to type it twice. The passcode must be four digits.
5.8.8 Restriction of outgoing communication
The service allows you to set a restriction on access from the subscriber's telephone set to certain types of
outgoing communications. The following groups of communication types are defined for using this service:
Group1 - only communication with special services;
Group2 - only communication with special services and local communications; Group3 -
types of communication assigned to groups 1 and 2 and zonal communication. The type of
connection is set in the prefixes parameters.
To bypass the restriction set with this service, you can use the services "Outgoing communication by
password"And"Passcode - activation". To restore the restriction removed service"Passcode - activation",
use the service"Passcode - deactivation".
Access to the service is controlled by the flag of the VVO category "Restriction of outgoing communication".
Service order * 34 * <PASSWORD> * N #
Service Cancellation # 34 * <PASSWORD> #
Control * # 34 * <PASSWORD> #
<N> – group number of allowed communication types.
654
5.8.9 Do Not Disturb

The service allows you to bar calls to a subscriber and assign a white list of addresses that can make
calls despite the barring.
Access to the service is controlled by the VDO category flag"Do not disturb".
Service order *26#
Service Cancellation #26#
Control *#26#
Add number to white list * 26 * <NUMBER>
Remove number from white list # 26 * <NUMBER>
Remove all numbers from the whitelist #26*0#
#26*00#
Black list
The service allows you to bar calls to a subscriber for certain numbers. Access to
the service is controlled by the VDO category flag"Black list".
Service order * 61 * <PASSWORD> #
Service Cancellation # 61 * <PASSWORD> #
Control * # 61 * <PASSWORD> #
Add a number to the black list * 61 * <PASSWORD> * <NUMBER>
Remove a number from the blacklist # 61 * <PASSWORD> * <NUMBER>
Remove all numbers from the blacklist # 61 * <PASSWORD> * 0 #
# 61 * <PASSWORD> * 00 #
655
5.8.10 Cancellation of all services
The service allows the subscriber to cancel all services ordered from his telephone using a single cancellation
procedure. The cancellation procedure consists of a service code and a password code.
Access to the service is controlled by the VDO category flag"Cancellation of all services".
Usage * 50#
5.8.11 Follow me
The Follow Me service allows you to enable forwarding of all calls from your phone to a remote phone using
the remote phone. An example of using this service: a subscriber, being away from his workplace, wants to
turn on the forwarding of all calls from his phone to the phone that is now "at hand".
Usage
Service activation:
Two SLTs participate in the service: local and remote telephone. The subscriber wants all calls that
come to the local phone to be forwarded to the remote phone.
To do this, first of all, on the local SLT, the service is activated withPIN or no PIN code (i.e., being at the
workplace, enable the possibility of using this service). After that, the subscriber from the remote phone
can turn on forwarding from the local SLT to the remote one (if the service was activated withPIN-code -
when you turn on call forwarding, you must specify a PIN-code; if without a PIN code, then you do not need
to specify a PIN code).
Service deactivation:
Remote call forwarding can be disabled from both the remote TA and from your local TA. The
service can only be deactivated from the local SLT,PIN code or not.
Service management from a telephone set
Activation of the service with a temporary PIN code is performed *23*PIN#

on a local number
Activation of the service without a PIN code is performed on a local *23#

number
Call forwarding from local to remote phone with temporary PIN, * 23 * PIN * LOCAL_PHONE #
performed on the remote number
Call forwarding from local to remote phone without PIN, * 23 ** LOCAL_PHONE#

Cancellation of call forwarding from local to remote phone # 23**LOCAL_PHONE#

without PIN code, performed on the remote number
656
Cancellation of call forwarding from local to a remote phone with # 23*PIN*LOCAL_PHONE#

a temporary PIN code is performed on a remote number
Deactivation, performed on a local number #23#
View status, performed on local number *#23#
Where
• PIN – digital secret code from 4 to 12 characters long;

• LOCAL_PHONE – phone number from which calls will be forwarded.
5.8.12 Follow me no response Description
The service "Follow me (on no answer)" allows you to forward all calls coming to the "local" number to
the "remote" number in case the call was not received on the local number within the specified time
interval.
Usage
Two SLTs participate in the service: local and remote telephone. The subscriber wants all calls that come to
the local phone and are not answered within the specified time interval to be forwarded to the remote
phone.
Activation/deactivation of the service is performed only on the local phone number. The call
forwarding request is made on the remote number.
Service management from a telephone set:
Activation of the service with a temporary PIN code is performed *25*PIN#

on a local number
Activation of the service without a PIN code is performed on a local *25#

number
Call forwarding from local to remote phone with temporary PIN, * 25 * PIN * LOCAL_PHONE #
Call forwarding from local to remote phone without PIN, performed * 25 ** LOCAL_PHONE#
on the remote number
Cancel call forwarding from local to remote phone #25**LOCAL_PHONE# without a PIN code, performed on
a remote number
Cancel call forwarding from local to remote phone #25*PIN*LOCAL_PHONE# with a temporary PIN, performed
on a remote number
657
Deactivation, performed on a local number #25#
View status, performed on local number *#25#
Where
• PIN – digital secret code from 4 to 12 characters long;

• LOCAL_PHONE – phone number from which calls will be forwarded.
5.8.13 Call Park

Description
The "Call Parking" service is designed to place a call on hold by one subscriber and release it from hold
by another subscriber.
Placement of a call to a parking slot is carried out by performing an unattended transfer during a
conversation session to the number of the call setting code to the slot.
Usage example
It is necessary to put the subscriber on hold in the parking slot number15.
• During a call, a transfer is made to the number *57*15#.
• Another party can take the party out of this parking slot number 15 by calling number *58*15#.
Service management from a telephone set
Putting into a slot * 57*<PARKING_SLOT_NUMBER>#
Removing from a slot * 58*<PARKING_SLOT_NUMBER>#
Where
NUMBER_PARKING_SLOT – the number of the parking slot in which the subscriber should be parked. If you
dial *57#, then NUMBER_PARKING_SLOT = number of initiator subscriber setting in the slot.
658
5.8.14 Voicemail
Description:
The "Voice mail" service allows subscriber A to leave a message to subscriber B (call from A to B) in case
subscriber B is unavailable/does not answer.
After fully listening to a new message, it is marked as old. Also, the message is marked as old if the user
pressed a number3 (Switch to next playback messages).
Upon activation, the following voice mail options are available to the subscriber:
• Unconditional – unconditionally forward an incoming call to the subscriber's voice mail;
• On no answer – redirect an incoming call to voice mail if the subscriber does not answer;
• Busy – forward an incoming call to voicemail when the subscriber is busy;
• When unavailable – forward an incoming call to voicemail when unavailable subscriber;
• Do Not Disturb - forward an incoming call to voicemail when activated. Do Not Disturb services.
659
-At the moment, the voice mailbox subscription mode is not implemented (MWI (RFC3842)), thus the
subscriber will not be able to find out if he has left a new voice message or not. To inform about the
presence of messages, you need to use the voice menu (*90# or *91*Voice mail number#).
-You can listen to mail from a remote phone only if the remote phone has the subscriber has
been given a password on their voicemail.
-When changing the password through the voice menu, if the old password is not set, you just need to press
lattice.
Message playback:
To play voice messages, the subscriber dials the code from his phone *90#, from someone else phone
dials the code *91# or *91*NUMBER# after which it enters the voice menu.
Usage example:
To activate voice mail, it is necessary to enable the VVO "Voice mail" on the subscriber:
660
Next, in the settings "VAR control" set the desired mode of operation:
Now, when a call is received by this subscriber, messages will go to voice mail, and the subscriber will be
able to listen to them by dialing *90# and following prompts voice menu.
The subscriber can also set up the voice mail operating mode on his own, using the voice menu and
following its prompts.
From the voice menu, the subscriber can:
• Listen to voice messages;

• Delete voice messages;
• Change the mode of voice mail;
• Set a password for voicemail.
661
5.8.15 Call recording on demand

The service allows the subscriber to start recording a conversation during a
conversation. Usage example:
Subscribers A and B are talking, and A has the on-demand call recording service enabled. When dialing
during the dialogue subscriber A code99, a beep sounds and the call recording starts. Recording of the
conversation stops when the dialogue ends or if subscriber A dials the code again during the dialogue99.
If the device is configured to record a conversation by a mask that the talking parties fall under, and one of
them tries to start recording on demand, an audio signal will be played, but a new conversation recording
will not start.
If call recording on demand is activated for both subscribers in the conversation and both subscribers dial
the code99 to start recording, the audio signal will be played for both subscriber A and for subscriber B, but
the recording will start only once - after the command of the subscriber who dialed the code first.
5.9 Appendix I. RADIUS CALL MANAGEMENT service
-Available with licenseRCM.
On the gateway, it is possible to change the parameters of a passing call using commands from RADIUS
servers sent in response to RADIUS-Authorization requests. Commands are sent to in text form using
Vendor-Specific attribute (see sectionCorrespondence tables for RADIUS responses and voice messages)
with the vendor number assigned to "LLC Enterprise" ELTEKS "and equal35265 and the attribute name
"Eltex-AVPair" with number 1.
The general format of an attributeEltex-AVPair looks like this: Vendor-
Specific(26): Eltex(35265): Eltex-AVPair(1):<$COMMAND-STRING>
By passing various commands in the $ lineCOMMAND-STRING, it is possible to control the following
parameters:
• Modification of CgPN and CdPN numbers:
Number modification can be done in two places during call handling:

• on an incoming call, before the call passes through the numbering plan, ie. in front of him routing. For
this, the values are usedCgPNin and CdPNin for Calling and Called numbers respectively.
• on outgoing calls, after the call has passed through the numbering plan and after it routing. For this,
the values are usedCgPNout and CdPNout for Calling and Called numbers respectively.
For roomsCgPN, in addition to the value of the number itself, you can change such parameters as:
• numtype– CgPN number type;
• plan type– numbering plan type CgPN;
• presentation– value of the presentation CgPN field.
For roomsCdPN, in addition to the value of the number itself, you can change such parameters as:
• numtype– CdPN number type;

• plan type– CdPN numbering plan type.
662
5.9.1 CgPN and CdPN modification request syntax

The command consists of a mandatory and an optional part. The mandatory part consists of the initial text
identifier of the command, the identifier of the modified number, and the modification mask.
• "CallManagement:" is a text identifier indicating that this attribute contains a call control command;
• "CgPNin=", "CdPNin=", "CgPNout=", "CdPNout=" – numbers identifiers, indicate to which apply the
modification to the number;
• Modification mask parameter – rule for modification of number digits (may be empty).
The optional part can consist of a single parameter or multiple parameters separated by a semicolon. The
required and optional parts are also separated by a semicolon if there is an optional part of the
command.
Possible options for the optional part:
• numtype.
• plantype.
• presentation
In general, the command format looks like this:
1. CallManagement:CgPNin=<$modifymask>;numtype=<$numtype>;plantype=<$plantype>;presentation=< $presentation>
Where:
"CallManagement:CgPNin=<$modify-mask>;" is a mandatory part,

"numtype=<$numtype>;plantype=<$plantype>;presentation=<$presentation>" is an optional part.
2. CallManagement:CdPNin=;numtype=<$numtype>;plantype=<$plantype>
Where:
"CallManagement:CgPNin=;" is a mandatory part with an empty modification mask,

"numtype=<$numtype>;plantype=<$plantype>" is an optional part.
3. CallManagement:CgPNin=<$modify-mask>;
Where:
"CallManagement:CgPNin=<$modify-mask>;" - obligatory part an

optional part is missing.
The values of the parameters used in the commands are presented below:
• $modify-mask – number modification rule (modification rule syntax is described in section
Modification Rule Syntax);
• $numtype – one of the following values: international, national, network-specific, subscriber, unknown;
• $plantype – one of the following values: isdn, national, private, unknown;
• $presentation is one of the following values: allowed, restricted, not-available, spare.
The gateway allows passing number modification command parameters in several attributes. So the
instruction set
"CallManagement:CgPNin=<$modify-mask>"
"CallManagement:CgPNin=;numtype=<$numtype>"
"CallManagement:CgPNin=;presentation=<$presentation>"
663
is equivalent to one command:
"CallManagement:CgPNin=<$modify-mask>;numtype=<$numtype>;presentation=<$presentation>"
-If any optional parameter (numtype, plantype, presentation) does not need modification, then it should
not be passed in the request, but an indication of the number type (CgPNin, CdPNin, CgPNout,
CdPNout) to which the transmitted fields belong, is mandatory in the beginning of the request.
Example:
By incoming call to the numberCgPN add +7383 prefix, change its number type to national and ask
presentation restricted.
To do this, it is enough to send in the responseAccess-Accept from the RADIUS server attribute with the following
value:
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:CgPNin=+7383

;numtype=national;presentation=restricted
Which is also equivalent to three attributes with values:

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:CgPNin=+7383 Vendor-Specific(26): Eltex(35265): Eltex-
AVPair(1): CallManagement:CgPNin=;numtype=national Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1):
CallManagement:CgPNin=;presentation=restricted
5.9.2 Call routing control

With commands fromRADIUS server, it is possible to control call routing, and namely, transfer it to another
gateway numbering plan or send it unconditionally to some prefix created in the configuration (equivalent
to the "direct prefix" parameter described in section Trunk groups).
The command to control routing consists of only the mandatory part:

• "CallManagement:" is a text identifier indicating that this attribute contains call control command.
• "NumberingPlan" – identifier indicating the command to change the numbering plan.

• "DirectRoutePrefix" is an identifier indicating the direct route prefix selection command.
routing.
CallManagement:NumberingPlan=<$numplan_idx>
CallManagement:DirectRoutePrefix=<$prefix_index>
Where:
$numplan_idx – sequence number of the numbering plan

$prefix_index – prefix ID created in the numbering plan. Example
Change call numbering plan to3rd.
664
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:NumberingPlan=3
5.9.3 Managing call categories

Using commands fromRADIUS server, it is possible to modify the category access and ANI category of the
subscriber (similar tocalling party category). For this, the following are used fields:
The command to change one of the categories consists only of the required part:
• "CallManagement:" is a text identifier indicating that this attribute contains a call control command;
• "AccessCategory" – identifier indicating the command to change the access category;

• "AONCategory" is an identifier indicating the command to change the subscriber's category (calling
party category).
CallManagement:AccessCategory=<$category_idx>
CallManagement:AONCategory=<$category_value>
Where:
• $category_idx – access category index;

• $category_value – ANI category index.
The priority of changing the ANI category depends on the subscriber
type. Dynamic subscriber:
1. Modification via RADIUS;

2. Modification through the tables of modifications on the incoming shoulder;
3. Modification through the tables of modifications on the outgoing shoulder.
Other subscribers:
1. Modification through the tables of modifications on the incoming shoulder;
2. Modification via RADIUS;
3. Modification through the tables of modifications on the outgoing shoulder.
Example
Set subscriber category (calling party category) equal to 7.
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:AONCategory=7
665
5.9.4 Managing parameters of dynamic subscribers
-Available with licensesSMG-PBX and SMG-VAS, no SMG-RCM license required.
For a dynamic subscriber, it is possible to set a parameter"Number of Lines"and mode of operation of the
lines at the stage of subscriber registration.
The command for managing subscriber parameters consists only of the mandatory part:
• UserManagement:– a text identifier identifying what the attribute contains a command for
managing a subscriber record;
• Max Active Lines– identifier indicating the number of active lines available to this subscriber to work in
the modecommon. If this parameter is specified, then the line restriction mode always set tocommon
even if separate constraints are specified at the same time for incoming/outgoing calls;
• Max Egress Lines– identifier indicating the number of outgoing lines available to this subscriber
to work in the modeseparate. May be combined with the MaxIngressLines parameter;
• Max Ingress Lines– identifier indicating the number of incoming lines available to this
subscriber to work in the modeseparate. Can be combined with the MaxEgressLines setting.
"UserManagement:MaxActiveLines=<$line_count>"
"UserManagement:MaxEgressLines=<$egress>;MaxIngressLines=<$ingress>;”
"UserManagement:MaxEgressLines=<$egress>”
"UserManagement:MaxIngressLines=<$ingress>”
Where:
$line_count - the number of simultaneously active connections available to the subscriber.
$egress - number of outgoing connections available to the subscriber;
$ingress - the number of incoming connections available to the subscriber.
Examples:
Set the normal mode of operation of the lines and the number of active lines per subscriber to three.
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): UserManagement:MaxActiveLines=3
Set the separate mode of operation of the lines, the number of outgoing lines equal to three and the number of
incoming lines equal to two:
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): essLines=2 UserManagement:MaxEgressLines=3;MaxIngr
Set the normal operation mode of the lines and the number of active lines per subscriber equal to two (note
that the parameterMaxActiveLines has unconditional precedence over MaxEgressLines and
MaxIngressLines):
666
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1):

UserManagement:MaxEgressLines=6;MaxActiveLines=2;MaxIngressLines=5
5.10 Appendix K. SNMP management and monitoring

Gateway supports monitoring and configuration via protocolSNMP (Simple Network Management
Protocol).
The following monitoring functions are implemented:
• collection of general information about the device, sensor readings, installed software;
• state of E1 streams and their channels;
• status of VoIP submodules and their channels;
• state of SS-7 linksets;
• state of SIP interfaces.
The following management functions are implemented:
• updating the device software;

• saving the current configuration;
• device reboot;
• management of SIP-subscribers;
• managing groups of dynamic SIP subscribers.
In tables with descriptionsOID in the "requests" column will take the following description format:
• Get - The value of an object or tree can be read by sending a GetRequest.
• Set - The object's value can be set by sending a SetRequest (note that when setting value via
SET to OID should be cast to the form “OID.0”);
• {} – object name or OID;
• N – the command uses a numeric parameter of type integer;
• U – the command uses a numeric parameter of the unsigned integer type;
• S – a string parameter is used in the command;
• A - the command uses an IP address (note that some commands that accept both argumentIP
address, use string data type “s”).
Table K1 - Command examples
Request Description Team
Get {} snmpwalk -v2c -c public -m +ELTEX-SMG $ip_smg activeCallCount
Get {}.x snmpwalk -v2c -c public -m +ELTEX-SMG $ip_smg pmExist.1
snmpwalk -v2c -c public -m +ELTEX-SMG $ip_smg pmExist.2
etc.
Set {} N snmpset -v2c -c public -m +ELTEX-SMG $ip_smg \
smgSyslogTracesCalls.0 i 60
Set {} 1 snmpset -v2c -c private -m +ELTEX-SMG $ip_smg smgReboot.0 i 1
667
Request Description Team
Set {} U snmpset -v2c -c public -m +ELTEX-SMG $ip_smg \
getGroupUserByID.0 u 2
Set{}S snmpset -v2c -c private -m +ELTEX-SMG $ip_smg \
smgUpdateFw.0s "smg1016m_firmware_3.8.0.1966.bin 192.0.2.2"
Set {} "NULL" snmpset -v2c -c private -m +ELTEX-SMG $ip_smg \
getUserByNumber.0 s "NULL"
Set {} A snmpset -v2c -c private -m +ELTEX-SMG $ip_smg \
smgSyslogTracesAddress.0 a 192.0.2.44
Examples of query execution:

The following queries are equivalent. On the example of an object requestactiveCallsCount, which
displays the number of current calls onSMG.
$ snmpwalk -v2c -cpublic-m +ELTEX-SMG192.0.2.1activeCallCount ELTEX-

SMG::activeCallCount.0= INTEGER:22
$ snmpwalk -v2c -cpublic-m +ELTEX-SMG192.0.2.1smg.42.1 ELTEX-

$ snmpwalk -v2c -cpublic-m +ELTEX-SMG192.0.2.1 1.3.6.1.4.1.35265.1.29.42.1 ELTEX-

$ snmpwalk -v2c -cpublic192.0.2.1 1.3.6.1.4.1.35265.1.29.42.1 SNMPv2-

SMI::enterprises.35265.1.29.42.1.0= INTEGER:22
5.10.1 OID description from ELTEX-SMG MIB

Table K2 - General information and sensors
Name OID Request Description

sy
smg 1.3.6.1.4.1.35265.1.29 Get {} The root object for the treeOID
smgDevName 1.3.6.1.4.1.35265.1.29.1 Get {} Device name
668

sy
smgDevType 1.3.6.1.4.1.35265.1.29.2 Get {} Device type
(Always29)
smgFwVersion 1.3.6.1.4.1.35265.1.29.3 Get {} Software version
smgEth0 1.3.6.1.4.1.35265.1.29.4 Get {} IP address of the main interface
smgUptime 1.3.6.1.4.1.35265.1.29.5 Get {} Software run time
smgUpdateFw 1.3.6.1.4.1.35265.1.29.25 Set{} Software Update. To do this, you need

S to make a requestSet with parameters
(separated by space):
– software file name without spaces;
– TFTP server address
smgReboot 1.3.6.1.4.1.35265.1.29.27 Set{} Hardware reboot

1
smgSave 1.3.6.1.4.1.35265.1.29.29 Set{} Saving a configuration

1
smgFreeSpace 1.3.6.1.4.1.35265.1.29.32 Get {} Free space on built-in flash

memory
smgFreeRam 1.3.6.1.4.1.35265.1.29.33 Get {} Amount of free RAM
smgMonitoring 1.3.6.1.4.1.35265.1.29.35 Get {} Display of temperature and fan speed

sensors, root object
smgTemperature1 1.3.6.1.4.1.35265.1.29.35.1 Get {} Temperature sensor1
smgTemperature2 1.3.6.1.4.1.35265.1.29.35.2 Get {} Temperature sensor2
smgFan0 1.3.6.1.4.1.35265.1.29.35.3 Get {} Fan speed sensor1
669

sy
smgPowerModuleTable 1.3.6.1.4.1.35265.1.29.36 Get {} Information about the state of the

power supplies, the root object.
For child objects, the BP number is

indicated:0 or 1
smgPowerModuleEntry 1.3.6.1.4.1.35265.1.29.36.1 Get {} cm.smgPowerModuleTable
pmExist 1.3.6.1.4.1.35265.1.29.36.1.2.x Get Is the PSU installed

{}.x
1 - installed
2 - not installed
pmPower 1.3.6.1.4.1.35265.1.29.36.1.3.x Get Is power being supplied to the PSU?

{}.x
1 - served
2 - not served
pmType 1.3.6.1.4.1.35265.1.29.36.1.4.x Get Type of PSU installed

{}.x
1 - PM48/12
2 - PM220/12
3 - PM220/12V
4 - PM150-220/12
smgCpuLoadTable 1.3.6.1.4.1.35265.1.29.37 Get {} LoadingCPU, root object. Shows

the percentage of CPU usage by
task type. For child objects, the
processor number is specified:
SMG1016M - 1
SMG2016 - 1..4
smgCpuLoadEntry 1.3.6.1.4.1.35265.1.29.37.1 Get {} cm.smgCpuLoadTable
cpuUsr 1.3.6.1.4.1.35265.1.29.37.1.2.x Get % CPU, user applications

{}.x
670

sy
cpuSys 1.3.6.1.4.1.35265.1.29.37.1.3.x Get % CPU, kernel applications

{}.x
cpuNic 1.3.6.1.4.1.35265.1.29.37.1.4.x Get % CPU, applications with changed

{}.x priority
cpuIdle 1.3.6.1.4.1.35265.1.29.37.1.5.x Get % CPU, idle

{}.x
cpuIo 1.3.6.1.4.1.35265.1.29.37.1.6.x Get % CPU IOPS

{}.x
cpuIrq 1.3.6.1.4.1.35265.1.29.37.1.7.x Get % CPU processing hardware

{}.x interrupts
cpuSirq 1.3.6.1.4.1.35265.1.29.37.1.8.x Get % CPU, software processing

{}.x interrupts
cpuUsage 1.3.6.1.4.1.35265.1.29.37.1.9.x Get % CPU, total usage

{}.x
smgSubscribersInfo 1.3.6.1.4.1.35265.1.29.42 Get {} General information about the number

of active calls and registrations
activeCallCount 1.3.6.1.4.1.35265.1.29.42.1 Get {} Current number of active calls
registrationCount 1.3.6.1.4.1.35265.1.29.42.2 Get {} Current number of registrations
tableOfDiskMonitor 1.3.6.1.4.1.35265.1.29.51 Get {} Information about external drives

connected toSMG, root an object
diskFullSize 1.3.6.1.4.1.35265.1.29.51.2 Get {} The amount of drives connected to

SMG
diskFreeSize 1.3.6.1.4.1.35265.1.29.51.3 Get {} Free space remaining on the drive
diskUsePercent 1.3.6.1.4.1.35265.1.29.51.4 Get {} Used disk space as a percentage
smgDevM4E1Modules 1.3.6.1.4.1.35265.1.29.52 Get {} Number of submodulesM4E1

installed on the device
671

sy
smgDevSMVPModules 1.3.6.1.4.1.35265.1.29.53 Get {} Number of submodulesSM-VP

installed on the device
tableOfLicenseMonitor 1.3.6.1.4.1.35265.1.29.156 Get {} Information about licenses

installed on the device, root
object
licenseName 1.3.6.1.4.1.35265.1.29.156.1.1.2 Get {} License name
licenseCount 1.3.6.1.4.1.35265.1.29.156.1.1.3 Get {} Number of licenses (65535 - without

restrictions)
licenseLeft 1.3.6.1.4.1.35265.1.29.156.1.1.4 Get {} Number of used licenses (65535 - no

restrictions)
672
Table K3 - syslog settings
sy
smgSyslog 1.3.6.1.4.1.35265.1.29.34 Get {} Settingssyslog, root an

object
smgSyslogTraces 1.3.6.1.4.1.35265.1.29.34.1 Get {} Tracing settings in syslog,

root object
smgSyslogTraceAddress 1.3.6.1.4.1.35265.1.29.34.1.1 Get {} syslog server IP address for

receiving traces
Set{}S
smgSyslogTracesPort 1.3.6.1.4.1.35265.1.29.34.1.2 Get {} Server Portsyslog for

receiving traces
Set {} N
smgSyslogTracesAlarms 1.3.6.1.4.1.35265.1.29.34.1.3 Get {} Accident tracing level:
Set {} N 1-99 - enable tracing
0 - disable tracing
smgSyslogTracesCalls 1.3.6.1.4.1.35265.1.29.34.1.4 Get {} Trace level

calls:
Set {} N
1-99 - enable tracing
0 - disable tracing
smgSyslogTracesISUP 1.3.6.1.4.1.35265.1.29.34.1.5 Get {} Trace level:
Set {} N OKS-7/ISUP
0 - disable tracing
smgSyslogTracesSIPT 1.3.6.1.4.1.35265.1.29.34.1.6 Get {} Trace levelSIPT:
0 - disable tracing
smgSyslogTracesQ931 1.3.6.1.4.1.35265.1.29.34.1.7 Get {} Trace levelQ.931:
0 - disable tracing
673

sy
smgSyslogTracesRTP 1.3.6.1.4.1.35265.1.29.34.1.8 Get {} Trace levelRTP:
0 - disable tracing
smgSyslogTracesMSP 1.3.6.1.4.1.35265.1.29.34.1.9 Get {} Voice submodule command

tracing level:
Set {} N
0 - disable tracing
smgSyslogTracesRadius 1.3.6.1.4.1.35265.1.29.34.1.10 Get {} Trace levelRADIO:
0 - disable tracing
smgSyslogTracesRowStatu 1.3.6.1.4.1.35265.1.29.34.1.11s Get {} Apply changes to

trace configurations
Set{} i
1
smgSyslogHistory 1.3.6.1.4.1.35265.1.29.34.2 Get {} Logging settings

command history in
syslog, root object
smgSyslogHistoryAddress 1.3.6.1.4.1.35265.1.29.34.2.1 Get {} syslog server IP address for

receiving command history
Set{}S
smgSyslogHistoryPort 1.3.6.1.4.1.35265.1.29.34.2.2 Get {} Server Portsyslog for

receiving command history
Set {} N
smgSyslogHistoryLevel 1.3.6.1.4.1.35265.1.29.34.2.3 Get {} Log verbosity level:
Set {} N 0 - disable logging
1 - standard
2 - full
smgSyslogHistoryRowStat 1.3.6.1.4.1.35265.1.29.34.2.4 Get {} Apply changes to

us command history logging
Set{} i
1
674

sy
smgSyslogConfig 1.3.6.1.4.1.35265.1.29.34.3 Get {} System settings

magazine
smgSyslogConfigLogsEnab 1.3.6.1.4.1.35265.1.29.34.3.1led Get {} Enable logging:
Set {} N 1 - enable
2 - disable
smgSyslogConfigSendToS 1.3.6.1.4.1.35265.1.29.34.3.2 Get {} Send messages to the

server serversyslog:
Set {} N
1 - enable
2 - turn off
smgSyslogConfigAddress 1.3.6.1.4.1.35265.1.29.34.3.3 Get {} syslog server IP address
Set{}S
smgSyslogConfigPort 1.3.6.1.4.1.35265.1.29.34.3.4 Get {} Server Portsyslog
Set {} N
smgSyslogConfigRowStatu 1.3.6.1.4.1.35265.1.29.34.3.5s Get {} Apply changes to

system settings
Set{} i magazine
1
675
Table K4 - Monitoring of flows E1
sy
smgEOneTable 1.3.6.1.4.1.35265.1.29.7 Get {} Table with the physical state of flows

E1
eOneLineInfoPhyState 1.3.6.1.4.1.35265.1.29.7.1.2 Get {} The physical state of flow E1. For

obtaining the state of a particular
1.3.6.1.4.1.35265.1.29.7.1.2.x Get {}.x thread must be supplementedOID it
number (0..15)
Flow states:
0 - the stream is disabled
1-ALARM
2-LOS
3 - AIS
4-LOM
5-LOMF
6 - flow in work
7 – PRBS test is enabled on the stream
eOneLineInfoRemAlarm 1.3.6.1.4.1.35265.1.29.7.1.3 Get {} The presence of a signal on the

streamRAI- error on the remote side.
1.3.6.1.4.1.35265.1.29.7.1.3.x Get {}.x To get the state of a particular
thread, you need to addOID it
number (0..15):
0 - normal state
1 - received RAI signal
eOneLineInfoRemAlarmTS 1.3.6.1.4.1.35265.1.29.7.1.4 Get {} The presence of a signal on the

16 streamRAI16- error on the remote
1.3.6.1.4.1.35265.1.29.7.1.4.x Get {}.x side16 channel interval. To get the
state of a particular thread, you need
to addOID it number (0..15):
0 - normal state
1 - RAI16 signal received
676

sy
eOneLineStateAlarm 1.3.6.1.4.1.35265.1.29.7.1.5 Get {} The state of accidents on the

stream. To get the state of a
1.3.6.1.4.1.35265.1.29.7.1.5.x Get {}.x particular thread, you need to add
OID it number (0..15):
0 – no alarms or the flow is off
1 – critical accident, the flow is not in

work
2 - accident, there are errors
3 - code is not used
4 - accident, RAI error
eOneLineStatePhyWork 1.3.6.1.4.1.35265.1.29.7.1.6 Get {} The state of the physical link on the

stream (signal reception). To get
1.3.6.1.4.1.35265.1.29.7.1.6.x Get {}.x the state of a particular thread, you
need to addOID it number (0..15):
0 - no signal
1 - there is a signal
eOneLinkState 1.3.6.1.4.1.35265.1.29.7.1.7 Get {} StateD-channel. For getting the state of

a particular thread must be
1.3.6.1.4.1.35265.1.29.7.1.7.x Get {}.x supplementedOID by its number (0..15):
0 - not working / disabled / not

both efficiencies work
1 - running / both efficiencies in operation
4 - KPD1 does not work
8 - KPD2 does not work
eOneStatistTimer 1.3.6.1.4.1.35265.1.29.7.1.9 Get {} Statistics collection time, seconds. To

get the state of a particular thread, you
1.3.6.1.4.1.35265.1.29.7.1.9.x Get {}.x need to addOID it number (0..15)
eOneSlipUp 1.3.6.1.4.1.35265.1.29.7.1.10 Get {} Slips (frame repeat). To get the state of

a particular thread, you need to addOID
1.3.6.1.4.1.35265.1.29.7.1.10.x Get {}.x it number (0..15)
677

sy
eOneSlipDown 1.3.6.1.4.1.35265.1.29.7.1.11 Get {} Slips (frame loss). To get the state of a

particular thread, you need to addOID it
1.3.6.1.4.1.35265.1.29.7.1.11.x Get {}.x number (0..15)
eOneBERCount 1.3.6.1.4.1.35265.1.29.7.1.12 Get {} Bit errors. To get the state of a

particular thread, you need to add
1.3.6.1.4.1.35265.1.29.7.1.12.x Get {}.x OID by its number (0..15)
eOneCVC 1.3.6.1.4.1.35265.1.29.7.1.13 Get {} Signal failure errors. To get the state of

a particular thread, you need to add
eOneCEC 1.3.6.1.4.1.35265.1.29.7.1.14 Get {} Error counterCRC/PRBS. For

obtaining the state of a particular
1.3.6.1.4.1.35265.1.29.7.1.14.x Get {}.x thread must be supplementedOID
it number (0..15)
eOneRxCount 1.3.6.1.4.1.35265.1.29.7.1.16 Get {} Bytes received. To get the state of a

particular thread, you need to add
eOneTxCount 1.3.6.1.4.1.35265.1.29.7.1.17 Get {} Bytes transferred. To get the state of

a particular thread, you need to add
eOneRxLow 1.3.6.1.4.1.35265.1.29.7.1.18 Get {} Accepted short packets. To get the

state of a particular thread, you
eOneRxBig 1.3.6.1.4.1.35265.1.29.7.1.19 Get {} Accepted long packets. To get the

state of a particular thread, you
eOneRxOvfl 1.3.6.1.4.1.35265.1.29.7.1.20 Get {} Receiver overflow. To get the state

of a particular thread, you need to
1.3.6.1.4.1.35265.1.29.7.1.20.x Get {}.x addOID it number (0..15)
eOneRxCRC 1.3.6.1.4.1.35265.1.29.7.1.21 Get {} MistakesCRC. For getting the state of a

particular thread must be
Get {}.x supplementedOID by its number (0..15)
678

sy
eOneTxUrun 1.3.6.1.4.1.35265.1.29.7.1.22 Get {} Transmission failures. To get the

state of a particular thread, you need
Get {}.x to addOID by its number (0..15)
eOneName 1.3.6.1.4.1.35265.1.29.7.1.23 Get {} Display information about the name of the

thread E1
Get {}.x
smgEOneChannelTable 1.3.6.1.4.1.35265.1.29.13 Get {} Stream Channel State Table E1, root

object
smgEOneChannelEntry 1.3.6.1.4.1.35265.1.29.13.1 Get {} cm.smgEOneChannelTable
channelEOneState 1.3.6.1.4.1.35265.1.29.13.1.2 Get {} Stream E channel status1.
1.3.6.1.4.1.35265.1.29.13.1.2.x Get {}.x To get the state of a particular thread,

you need to addOID number flow (
1.3.6.1.4.1.35265.1.29.13.1.2.xx Get 0..15).
{}.xx
To get the state of a particular channel,
you need to addOID number flow (0..15)
and channel number (0..31).
smgEOneBusyChannelsC 1.3.6.1.4.1.35265.1.29.31 Get {} Number of occupied stream channels

hunters E1, root object
smgEOneInstantCounters 1.3.6.1.4.1.35265.1.29.31.1 Get {} cm.smgEOneBusyChannelsCounters
smgEOneStream0BusyCh 1.3.6.1.4.1.35265.1.29.31.1.0 Get {} Number of occupied stream channels

annelsInstantCounter E1 0





679

sy




smgEOneStream10BusyC 1.3.6.1.4.1.35265.1.29.31.1.10 Get {} Number of occupied stream channels

hannelsInstantCounter E1 10





smgEOnePeriodicCounter 1.3.6.1.4.1.35265.1.29.31.2s Get {} Number of occupied stream channels E1

for the selected period (see
smgEOneCounterPeriod)

annelsPeriodicCounter E1 0 for the selected period (see


680

sy








hannelsPeriodicCounter E1 10 for the selected period (see



681

sy


smgEOneCounterPeriod 1.3.6.1.4.1.35265.1.29.31.2.16 Get {} Statistics collection period, minutes.
Set {} N Statistics will be accumulated in

periodic counters, while the counter
will display the value for the previous
period.
smgChannelsE1free 1.3.6.1.4.1.35265.1.29.41 Get {} Number of free stream channels

E1, root object
e1freeS0channels 1.3.6.1.4.1.35265.1.29.41.1 Get {} Number of free stream channels

E10

Eeleven

E12

E13

E14

E15

E16

E17

E18
682

sy

E19

E1 10

E1 11

E1 12

E1 13

E1 14

E1 15
Table K5 — Monitoring of OKS-7 linksets
Name OID Requests Description
smgLinkSetTable 1.3.6.1.4.1.35265.1. Get {} Linkset states

29.11
OKS-7, root object
linkSetEntry 1.3.6.1.4.1.35265.1. Get {} cm.smgLinkSetTable

29.11.1
linkSetState 1.3.6.1.4.1.35265.1. Get {} Linkset state

29.11.1.2
Get {}.x OKS-7.
To get the state of a particular linkset, you

need to addOID by its index (0..15)
linkSetName 1.3.6.1.4.1.35265.1. Get {} The name of the OKS-linksets7. To receive the

29.11.1.3 names of a specific linkset must be
Get {}.x supplementedOID by its index (0..15)
683
Table K6 - Monitoring of SM-VP submodules (VoIP submodules)
smgMspTable 1.3.6.1.4.1.35265. Get {} Status statisticsVoIP submodules, root

1.29.9 object
mspEntry 1.3.6.1.4.1.35265. Get {} cm.smgMspTable

1.29.9.1
mspState 1.3.6.1.4.1.35265. Get {} Working modeVoIP submodule.

1.29.9.1.2
Get {}.x To get the state of a particular submodule,
1.3.6.1.4.1.35265. you need to addOID by its number (0..5)
1.29.9.1.2.x
mspUsedConn 1.3.6.1.4.1.35265. Get {} The number of submodule channels used.

1.29.9.1.3
1.3.6.1.4.1.35265. you need to addOID by its number (0..5)
1.29.9.1.3.x
mspCreateReq 1.3.6.1.4.1.35265. Get {} Cumulative counter of requests to the module to

1.29.9.1.4 create connections.
Get {}.x
1.3.6.1.4.1.35265. To get the state of a particular submodule,
1.29.9.1.4.x you need to addOID by its number (0..5)
mspCreated 1.3.6.1.4.1.35265. Get {} Cumulative counter of completed requests to the

1.29.9.1.5 module to create connections.
Get {}.x
mspDestroyReq 1.3.6.1.4.1.35265. Get {} Cumulative counter of requests to the module to

1.29.9.1.6 delete connections.
Get {}.x
mspDestroyed 1.3.6.1.4.1.35265. Get {} Cumulative counter of completed requests to the

1.29.9.1.7 module to delete connections.
Get {}.x
684
mspPayload 1.3.6.1.4.1.35265. Get {} Submodule load in % of the total number of

1.29.9.1.8 channels.
Get {}.x
smgIpMspChannelTable 1.3.6.1.4.1.35265. Get {} Active Channel Status StatisticsVoIP

1.29.15 submodules, root object
smgMspIpChannelEntry 1.3.6.1.4.1.35265. Get {} cm.smgIpMspChannelTable

1.29.15.1
ipMspChannelState 1.3.6.1.4.1.35265. Get {} Status of active channels.

1.29.15.1.2
1.3.6.1.4.1.35265. you need to addOID by its number (0..5).
1.29.15.1.2.x Get {}.xx
1.3.6.1.4.1.35265. To get the state of a particular channel, you need

1.29.15.1.2.xx to addOID submodule number (0..5) and channel
number (0..127):
0 - free
1 - channel selection
2 - request to allocate a channel
3 - a request for channel allocation has been processed
4 - request to release the channel
5 - a request to disable the channel has been processed
6 - request to disable the channel
7 - request to activate the channel
8 - in progress
9 - activated
10 - request to join the conference
11 – conference is active
685
ipMspChannelSiptCallref 1.3.6.1.4.1.35265. Get {} The local ID of the call associated with the active
1.29.15.1.3 channel.
Get {}.x
1.29.15.1.3.x Get {}.xx you need to addOID by its number (0..5).
1.3.6.1.4.1.35265.
1.29.15.1.3.xx To get the state of a particular channel, you need
to addOID submodule number (0..5) and channel
number (0..127)
ipMspChannelSrcIp 1.3.6.1.4.1.35265. Get {} LocalThe IP address of the media stream.

1.29.15.1.4
1.29.15.1.4.x Get {}.xx

number (0..127)
ipMspChannelSrcPort 1.3.6.1.4.1.35265. Get {} The local port of the media stream.

1.29.15.1.5
1.29.15.1.5.x Get {}.xx

number (0..127)
ipMspChannelSrcMac 1.3.6.1.4.1.35265. Get {} LocalThe MAC address of the media stream.

1.29.15.1.6
1.29.15.1.6.x Get {}.xx

number (0..127)
ipMspChannelDstIp 1.3.6.1.4.1.35265. Get {} RemoteThe IP address of the media stream.

1.29.15.1.7
1.29.15.1.7.x Get {}.xx

number (0..127)
686
ipMspChannelDstPort 1.3.6.1.4.1.35265. Get {} Remote media stream port.

1.29.15.1.8
1.29.15.1.8.x Get {}.xx

number (0..127)
ipMspChannelDstMac 1.3.6.1.4.1.35265. Get {} RemoteThe MAC address of the media stream.

1.29.15.1.9
1.29.15.1.9.x Get {}.xx

number (0..127)
ipMspChannelCallingPart 1.3.6.1.4.1.35265. Get {} Caller number.

yNumber 1.29.15.1.10
1.29.15.1.10.x Get {}.xx

number (0..127)
1.3.6.1.4.1.35265. Get {} Called number.

1.29.15.1.11
ipMspChannelCalledPartyNumber
1.29.15.1.11.x Get {}.xx

number (0..127)
ipMspChannelOccupiedTi 1.3.6.1.4.1.35265. Get {} Call duration.

me 1.29.15.1.12
1.29.15.1.12.x Get {}.xx

number (0..127)
smgChannelsVoip 1.3.6.1.4.1.35265. Get {} The number of busy channels perVoIP

1.29.40 submodules, root object
687
voip0busyChannels 1.3.6.1.4.1.35265. Get {} The number of busy channels per

1.29.40.1
VoIP submodule 0

1.29.40.2
VoIP submodule 1

1.29.40.3
VoIP submodule 2

1.29.40.4
VoIP submodule 3

1.29.40.5
VoIP submodule 4

1.29.40.6
VoIP submodule 5
voip0freeChannels 1.3.6.1.4.1.35265. Get {} Number of free channels on

1.29.40.7
VoIP submodule 0

1.29.40.8
VoIP submodule 1

1.29.40.9
VoIP submodule 2

1.29.40.10
VoIP submodule 3

1.29.40.11
VoIP submodule 4

1.29.40.12
VoIP submodule 5
688
Table K7 - Monitoring of SIP interfaces
smgSipIntrfCallInfo 1.3.6.1.4.1.35265.1.29.43 Get {} Information about calls toSIP-

interfaces, root object
sipIntrfCount 1.3.6.1.4.1.35265.1.29.43. Get {} 1 QuantitySIP interfaces
sipIntrfActiveCallTable 1.3.6.1.4.1.35265.1.29.43. Get {} 2 Call table
(Withoutno sip interfaces displayed)
sipIntrfActiveCallTable 1.3.6.1.4.1.35265.1.29.43. Get {} cm.sipIntrfActiveCallTable

Entry 2.1
sipIntrfID 1.3.6.1.4.1.35265.1.29.43. Get {} SIP interface ID.

2.1.2
Get {}.x To get information about a
1.3.6.1.4.1.35265.1.29.43. specific interface, addOID is its
2.1.2.x index.
sipIntrfName 1.3.6.1.4.1.35265.1.29.43. Get {} NameSIP interface.

2.1.3
2.1.3.x index.
sipIntrfMode 1.3.6.1.4.1.35265.1.29.43. Get {} Operating mode.

2.1.4
2.1.4.x index.
0 - SIP
1 - SIP-T
2 - SIP-I
3 - SIP-Q
4 - SIP-profile
sipIntrfCallCount 1.3.6.1.4.1.35265.1.29.43. Get {} The number of active calls on the

2.1.5 interface.
Get {}.x
1.3.6.1.4.1.35265.1.29.43. To get information about a
2.1.5.x specific interface, addOID is its
index.
689
sipIntrfMaxCallCount 1.3.6.1.4.1.35265.1.29.43. Get {} The maximum number of calls on the

2.1.6 interface.
Get {}.x
1.3.6.1.4.1.35265.1.29.43. To get information about a
2.1.6.x specific interface, addOID is its
index.
0 - no limit
1..65535 – call limit
sipIntrfAccessible 1.3.6.1.4.1.35265.1.29.43. Get {} AvailabilitySIP interface (the

2.1.7 result of the control of the
Get {}.x opposite side byOPTIONS):
1.3.6.1.4.1.35265.1.29.43.
2.1.7.x 1 - available
2 - unavailable
Table K8 - Radius query statistics
radiusTotal 1.3.6.1.4.1.35265.1.29.47.1 Get {} General query statistics
radiusTotalSent 1.3.6.1.4.1.35265.1.29.47.2 Get {} Sent request statistics
radiusAccsReq 1.3.6.1.4.1.35265.1.29.47.3 Get {} general Statistics

requestsAccess Request
radiusAccsReqSent 1.3.6.1.4.1.35265.1.29.47.4 Get {} Sent request statistics

Access Request
radiusAccsRsp 1.3.6.1.4.1.35265.1.29.47.5 Get {} general Statistics

requestsAccess responses
radiusAccsAccept 1.3.6.1.4.1.35265.1.29.47.6 Get {} Statistics

requestsAccess Accept
radiusAccsReject 1.3.6.1.4.1.35265.1.29.47.7 Get {} Statistics

requestsAccess Reject
radiusAcctReq 1.3.6.1.4.1.35265.1.29.47.8 Get {} general Statistics

requestsAccounting Request
radiusAcctReqSent 1.3.6.1.4.1.35265.1.29.47.9 Get {} Sent request statistics

Accounting Request
690
radiusAcctRsp 1.3.6.1.4.1.35265.1.29.47.10 Get {} general Statistics

requestsAccounting responses
radiusAcctRspSuccess 1.3.6.1.4.1.35265.1.29.47.11 Get {} Request Statistics

Accounting Response Success
radiusDiscReq 1.3.6.1.4.1.35265.1.29.47.12 Get {} general Statistics

requestsDisconnect Request
radiusDiscReqSent 1.3.6.1.4.1.35265.1.29.47.13 Get {} Sent stats Disconnect

Request
radiusRspTimeout 1.3.6.1.4.1.35265.1.29.47.14 Get {} Timeouts while waiting for responses

fromRADIUS servers
radiusTimeoutExhst 1.3.6.1.4.1.35265.1.29.47.15 Get {} Retransmission end timeout
radiusProcTimeout 1.3.6.1.4.1.35265.1.29.47.16 Get {} Timeouts while processing the response.

Usually this "0"
radiusTimeThreshold 1.3.6.1.4.1.35265.1.29.47.17 Get {} Getting / setting the time threshold

for the received
Set{} statistics.0 - statistics for everything
time,5 - in the last 5 minutes, 60 - in
the last 60 minutes.
radiusClearStat 1.3.6.1.4.1.35265.1.29.47.18 Set{} Clear statistics:0 - clear permanent

statistics
Table K9 - Data about network interfaces
iftType 1.3.6.1.4.1.35265.1.29.19.1.2 Get {} Network interface type. To get

information about the type of a
1.3.6.1.4.1.35265.1.29.19.1.2.x Get {}.x particular interface, addOID by
its number
iftLabel 1.3.6.1.4.1.35265.1.29.19.1.3 Get {} Network interface name
Get {}.x To get information about the name of

a specific network interface, addOID it
number
691
iftIpaddr 1.3.6.1.4.1.35265.1.29.19.1.4 Get {} The IP address of the network

interface. For information aboutIP the
Get {}.x address of a specific network interface
must be completedOID it number
iftNetmask 1.3.6.1.4.1.35265.1.29.19.1.5 Get {} Network interface mask. To obtain

information about the mask of a
Get {}.x specific network interface, addOID
by its number
iftGateway 1.3.6.1.4.1.35265.1.29.19.1.6 Get {} Network interface gateway. To get

information about the gateway of a
1.3.6.1.4.1.35265.1.29.19.1.6.x Get {}.x particular network interface, add
OID by its number
iftBroadcast 1.3.6.1.4.1.35265.1.29.19.1.7 Get {} The broadcast address of the

interface. For information about the
1.3.6.1.4.1.35265.1.29.19.1.7.x Get {}.x broadcast address of a specific
network
interface needs to be addedOID it
number
iftWeb 1.3.6.1.4.1.35265.1.29.19.1.8 Get {} Access to the deviceweb via

network interface:
1.3.6.1.4.1.35265.1.29.19.1.8.x Get {}.x
0 - no access
1 - access is available
iftSsh 1.3.6.1.4.1.35265.1.29.19.1.9 Get {} Access to the devicessh via

network interface:
1.3.6.1.4.1.35265.1.29.19.1.9.х Get {}.x
0 - no access
IftTelnet 1.3.6.1.4.1.35265.1.29.19.1.10 Get {} Access to the devicetelnet via

network interface:
1.3.6.1.4.1.35265.1.29.19.1.10.x Get {}.x
0 - no access
iftSnmp 1.3.6.1.4.1.35265.1.29.19.1.11 Get {} Protocol usageSNMP via network

interface:
1.3.6.1.4.1.35265.1.29.19.1.11.x Get {}.x
0 - disabled
1 - allowed
692
IftRtp 1.3.6.1.4.1.35265.1.29.19.1.12 Get {} Ability to receive / transmitRTP- traffic

through the network interface:
1.3.6.1.4.1.35265.1.29.19.1.12.x Get {}.x
0 - disabled
1 - allowed
IftRadius 1.3.6.1.4.1.35265.1.29.19.1.13 Get {} Protocol usageRADIUS via network

interface:
1.3.6.1.4.1.35265.1.29.19.1.13.x Get {}.x
0 - disabled
1 - allowed
IftH323 1.3.6.1.4.1.35265.1.29.19.1.14 Get {} Using the N.323 via network

interface:
1.3.6.1.4.1.35265.1.29.19.1.14.x Get {}.x
0 - disabled
1 - allowed
iftDhcp 1.3.6.1.4.1.35265.1.29.19.1.16 Get {} UsageDHCP on network interface:
1.3.6.1.4.1.35265.1.29.19.1.16.x Get {}.x

0 - DHCP disabled
1 - DHCP enabled
iftDhcpNoGw 1.3.6.1.4.1.35265.1.29.19.1.17 Get {} Using the "Obtain Gateway

Automatically" option on a network
1.3.6.1.4.1.35265.1.29.19.1.17.x Get {}.x interface withDHCP:
0 – option enabled
1 – option disabled
iftDhcpDns 1.3.6.1.4.1.35265.1.29.19.1.18 Get {} Using the Get DNS automatically"

on the network interface with
1.3.6.1.4.1.35265.1.29.19.1.18.x Get {}.x DHCP:
iftDhcpNtp 1.3.6.1.4.1.35265.1.29.19.1.19 Get {} Using the Get NTP automatically"

on the network interface with
1.3.6.1.4.1.35265.1.29.19.1.19.x Get {}.x DHCP:
693
IftSip 1.3.6.1.4.1.35265.1.29.19.1.20 Get {} Protocol usageSIP via network

interface:
1.3.6.1.4.1.35265.1.29.19.1.20.x Get {}.x
0 - disabled
1 - allowed
IftServerIp 1.3.6.1.4.1.35265.1.29.19.1.21 Get {} IP address of the PPTP server. For get

address information PPTP server of a
1.3.6.1.4.1.35265.1.29.19.1.21.x Get {}.x specific network interface needs to be
addedOID it number
IftRunStup 1.3.6.1.4.1.35265.1.29.19.1.22 Get {} Using the "Enable" option onVPN/

pptp interface:
1.3.6.1.4.1.35265.1.29.19.1.22.x Get {}.x
0 - interface is disabled
1 – interface enabled
IftGwIgnore 1.3.6.1.4.1.35265.1.29.19.1.23 Get {} Using the option

"Ignore default gateway" onVPN/pptp
1.3.6.1.4.1.35265.1.29.19.1.23.x Get {}.x interface:
IftUseMppe 1.3.6.1.4.1.35265.1.29.19.1.24 Get {} Using the Enable Encryption

option onvpn/pptp- interface:
1.3.6.1.4.1.35265.1.29.19.1.24.x Get {}.x
IftUserIp 1.3.6.1.4.1.35265.1.29.19.1.25 Get {} VPN user IP address
1.3.6.1.4.1.35265.1.29.19.1.25.x Get {}.x
iftvid 1.3.6.1.4.1.35265.1.29.19.1.27 Get {} Network Interface VID
1.3.6.1.4.1.35265.1.29.19.1.27.x Get {}.x For information aboutVID specific

network interface must be added
OID by its number
IftCos 1.3.6.1.4.1.35265.1.29.19.1.28 Get {} network interface COS
1.3.6.1.4.1.35265.1.29.19.1.28.x Get {}.x For information aboutCOS specific

network interface must be added
OID by its number
694
IftFwProfile 1.3.6.1.4.1.35265.1.29.19.1.29 Get {} Profilenetwork firewall interface.

For profile informationfirewall
1.3.6.1.4.1.35265.1.29.19.1.29.x Get {}.x specific network interface must be
addedOID by its number
Table K10 — Monitoring of trunk groups
trunkName 1.3.6.1.4.1.35265.1.29.46.1.1.2 Get {} Trunk group name. To get

information about the name of
1.3.6.1.4.1.35265.1.29.46.1.1.2.x Get {}.x a specific trunk group, addOID
her number
trunkEntryType 1.3.6.1.4.1.35265.1.29.46.1.1.3 Get {} Trunk group type:
1.3.6.1.4.1.35265.1.29.46.1.1.3.x Get {}.x 0-CAS
1-PRI
2 - OKS-7
3-SIP
4 - flow channels E1
5-H323
6 – E1 streams from the group of lines

OKS-7
7 - IPNET
8-CSPG
9-fxo
To obtain information about the

type of a particular trunk group,
addOID her number
695
trunkEnable 1.3.6.1.4.1.35265.1.29.46.1.1.4 Get {} E flow status1 which tied to a

trunk group, used for types
1.3.6.1.4.1.35265.1.29.46.1.1.4.x Get {}.x
trunk groupCAS, PRI, OKS-7,
E1 flow channels, flows E1
from a group of lines OKS-7:
0 - stream disabled
1 - stream enabled
trunkCapacity 1.3.6.1.4.1.35265.1.29.46.1.1.5 Get {} The total number of channels in

the trunk group,
1.3.6.1.4.1.35265.1.29.46.1.1.5.x Get {}.x used for types
trunk groupCAS, PRI, OKS-7,
from a group of lines OKS-7
For information on the number

of channels
specific trunk group must be
supplementedOID her number
trunkCurrentIngressCalls 1.3.6.1.4.1.35265.1.29.46.1.1.6 Get {} The number of incoming calls in

the trunk group. For
1.3.6.1.4.1.35265.1.29.46.1.1.6.x Get {}.x information about
the number of incoming calls of a
trunkCurrentEgressCalls 1.3.6.1.4.1.35265.1.29.46.1.1.7 Get {} Number of outgoing

calls in a trunk group. For
1.3.6.1.4.1.35265.1.29.46.1.1.7.x Get {}.x information on the number of
outgoing
calls of a specific trunk group
must be supplementedOID her
number
trunkCurrentTotalCalls 1.3.6.1.4.1.35265.1.29.46.1.1.8 Get {} The total number of calls in the

trunk group. For
1.3.6.1.4.1.35265.1.29.46.1.1.8.x Get {}.x information about
number of calls
696
trunkCurrentCps 1.3.6.1.4.1.35265.1.29.46.1.1.9 Get {} Currentcps in trunk group.

For getting
1.3.6.1.4.1.35265.1.29.46.1.1.9.x Get {}.x information aboutcps specific
trunk group
supplementOID by her number
trunkStatus 1.3.6.1.4.1.35265.1.29.46.1.1.10 Get {} Trunk group status. For trunk

groups containing E streams1:
1.3.6.1.4.1.35265.1.29.46.1.1.10.x Get {}.x
0 - the thread is not running
1 - thread in progress
2 - no D-channel
For trunk groups that include

interfaces SIP:
0 - interface unavailable
1 - interface in operation
2 – interface state unknown

(off
controloptions)

status of a specific trunk group,
addOID her number
trunkUnavailableCicCount 1.3.6.1.4.1.35265.1.29.46.1.1.11 Get {} Number of non-working

channels (blocked /
1.3.6.1.4.1.35265.1.29.46.1.1.11.x Get {}.x unavailable / disabled), used
for types
trunk groupCAS, PRI, OKS7,
from a group of lines OKS-7

of non-working
channels of a specific trunk group
must be supplementedOID her
number
697
trunkCPSMax 1.3.6.1.4.1.35265.1.29.46.1.1.12 Get {} limit valueCPS in trunk group

1.3.6.1.4.1.35265.1.29.46.1.1.12.x
Get {}.x
For limit value informationCPS
in specific trunk group must be
trunkCPSAlarm 1.3.6.1.4.1.35265.1.29.46.1.1.13 Get {} Emergency valueCPS in

1.3.6.1.4.1.35265.1.29.46.1.1.13.x trunk group
Get {}.x
For information about the
alarm valueCPS in specific trunk
group must be supplemented
OID her number
trunkChansFree 1.3.6.1.4.1.35265.1.29.46.1.1.14 Get {} Number of free

1.3.6.1.4.1.35265.1.29.46.1.1.14.x channels in a trunk group. If
Get {}.x the trunk group containsSIP/
H323 interface and limitation
on the number of active
connections are not

configured, the value will be
returned 65535 (no limit)

of free
channels in a particular
trunk group needs
supplementOID by her number
trunkChansBusy 1.3.6.1.4.1.35265.1.29.46.1.1.15 Get {} The number of busy channels in

1.3.6.1.4.1.35265.1.29.46.1.1.15.x the trunk group
Get {}.x
number of busy channels in a
particular trunk group, addOID
her number
698
5.10.2 Monitoring and configuring SIP subscribers (static subscribers)

In the description of the functions of monitoring and configuring the commands for calling utilitiesSNMP
will are represented by the following scripts for brevity and clarity of presentation:
Scriptswalk, which implements reading values:
# !/bin/bash
/usr/bin/snmpwalk -v2c -cpublic-m +ELTEX-SMG192.0.2.1"$@"
Scriptsset, which implements setting values:
# !/bin/bash
/usr/bin/snmpset -v2c -cprivate-m +ELTEX-SMG192.0.2.1"$@"
5.10.2.1 Monitoring
Monitoring of a subscriber or a group of static subscribers can be carried out in several ways:
• By index or subscriber ID;

• According to the numbering plan and the full number of the subscriber;
• By numbering plan and partial subscriber number.
For monitoring:
• Reset search status;
• Set search criteria (optional);
• Display information.
5.10.2.2 Index search example
sset staticResetCheck.0 i 1 # reset search status

sset getUserByIndex.0 i 4 # set search at index 4
swalk tableOfUsers # query table with subscriber information
699
Result:
ELTEX-SMG::StaticResetCheck.0= INTEGER:0 ELTEX-

SMG::getUserByIndex.0= INTEGER:4 ELTEX-SMG::UserID.4=
INTEGER:5 ELTEX-SMG::RegState.4= INTEGER:2 ELTEX-
SMG::Numplan.4= INTEGER:0 ELTEX-SMG::Number.4=STRING:
20000 ELTEX-SMG::Ip.4=IPAddress:192.0.2.123 ELTEX-SMG::Port.
4= Gauge32:5063 ELTEX-SMG::Domain.4=STRING:192.0.2.1
ELTEX-SMG::MaxActiveLines.4= INTEGER:3 ELTEX-
SMG::ActiveCallCount.4= INTEGER:0 ELTEX-SMG::RegExpires.4=
INTEGER:0 ELTEX-SMG::TableOfUsersEntry.12.4= INTEGER:0
ELTEX-SMG::TableOfUsersEntry.13.4=INTEGER: -1 ELTEX-
SMG::TableOfUsersEntry.14.4=INTEGER: -1 ELTEX-
SMG::TableOfUsersEntry.16.4=INTEGER: -1
5.10.2.3 Dial plan and number search example
sset staticResetCheck.0 i 1 sset # reset search status

getUserByNumplan.0 i 2 sset # set second numbering plan
getUserByNumber.0 s 20001 swalk # setting the subscriber number
tableOfUsers # query table with subscriber information
Result:
ELTEX-SMG::UserID.9= INTEGER:10 ELTEX-SMG::RegState.9=

INTEGER:0 ELTEX-SMG::Numplan.9= INTEGER:2 ELTEX-
SMG::Number.9=STRING:20001 ELTEX-SMG::Ip.9=IPAddress:0.0.
0.0 ELTEX-SMG::Port.9= Gauge32:0 ELTEX-SMG::Domain.9=
STRING: sipp.domain ELTEX-SMG::MaxActiveLines.9= INTEGER:0
ELTEX-SMG::ActiveCallCount.9= INTEGER:0 ELTEX-
SMG::RegExpires.9= INTEGER:0 ELTEX-SMG::TableOfUsersEntry.
12.9= INTEGER:0 ELTEX-SMG::TableOfUsersEntry.13.9=INTEGER:
-1 ELTEX-SMG::TableOfUsersEntry.14.9=INTEGER: -1 ELTEX-
700
5.10.2.4 Dial plan and partial number search example
sset ttaticResetCheck.0 i 1 sset # reset search status

getUserByNumplan.0 i 0 sset # set numbering plan to zero
getUserBySubNumber.0 s 400 swalk # set part number
tableOfUsers # query table with subscriber information
701
Result:
ELTEX-SMG::UserID.0= INTEGER:1 ELTEX-SMG::UserID.1=

INTEGER:2 ELTEX-SMG::UserID.2= INTEGER:3 ELTEX-
SMG::RegState.0= INTEGER:1 ELTEX-SMG::RegState.1= INTEGER:
1 ELTEX-SMG::RegState.2= INTEGER:0 ELTEX-SMG::Numplan.0=
INTEGER:0 ELTEX-SMG::Numplan.1= INTEGER:0 ELTEX-
SMG::Numplan.2= INTEGER:0 ELTEX-SMG::Number.0=STRING:
40010 ELTEX-SMG::Number.1=STRING:40011 ELTEX-
SMG::Number.2=STRING:40012 ELTEX-SMG::Ip.0=IPAddress:
192.0.2.21 ELTEX-SMG::Ip.1=IPAddress:192.0.2.21 ELTEX-
SMG::Ip.2=IPAddress:0.0.0.0 ELTEX-SMG::Port.0= Gauge32:
23943 ELTEX-SMG::Port.1= Gauge32:23943 ELTEX-SMG::Port.2=
Gauge32:0 ELTEX-SMG::Domain.0=STRING:192.0.2.1 ELTEX-
SMG::Domain.1=STRING:192.0.2.1 ELTEX-SMG::Domain.2=
STRING: ELTEX-SMG::MaxActiveLines.0=INTEGER: -1 ELTEX-
SMG::MaxActiveLines.1= INTEGER:4 ELTEX-
SMG::MaxActiveLines.2= INTEGER:6 ELTEX-
SMG::ActiveCallCount.0=INTEGER: -1 ELTEX-
SMG::ActiveCallCount.1= INTEGER:0 ELTEX-
SMG::ActiveCallCount.2= INTEGER:0 ELTEX-SMG::RegExpires.0=
INTEGER:118 ELTEX-SMG::RegExpires.1= INTEGER:91 ELTEX-
SMG::RegExpires.2= INTEGER:0 ELTEX-SMG::TableOfUsersEntry.
12.0= INTEGER:1 ELTEX-SMG::TableOfUsersEntry.12.1=
INTEGER:0 ELTEX-SMG::TableOfUsersEntry.12.2= INTEGER:0
ELTEX-SMG::TableOfUsersEntry.13.0= INTEGER:2 ELTEX-
SMG::TableOfUsersEntry.14.0= INTEGER:0 ELTEX-
702
5.10.2.5 Viewing information without using search

swalk tableOfUsers # display all subscribers
swalk regState.3 # display registration status of subscriber with index 3
swalk ip.4 # display the IP address of the subscriber with index 4
swalk activeCallCount # display the number of active calls for everyone

subscribers
5.10.2.6 Configuration
Configuration involves the following operations on subscribers:
1. View settings;
2. Editing settings;
3. Creation of a new subscriber;
4. Removal.
To view settings:
1. Through the search, select a subscriber to view;
2. Select the configuration mode - view;
3. Display the required data.
To edit settings:
1. Through the search, select a subscriber for configuration;
2. Select the configuration mode - editing;
3. Set the necessary settings;
4. Apply settings.
To create a new subscriber:
1. Select the configuration mode - creation;
2. Set the necessary settings for the new subscriber (at least the number);
3. Apply settings.
To delete a subscriber:
1. Through the search, select the subscriber to delete;
2. Select the configuration mode - delete;
3. Apply settings.
If necessary, you can roll back unapplied changes by working in the modes of adding a new user or editing
the settings of an existing one.
-Deleting a subscriber is irreversible, only a complete rollback of the configuration is possible throughWEB
orCLI.
703
5.10.2.7 Example of creating a new subscriber

sset staticSetMode.0 i 3 # set add mode
sset stSetNumber.0 s 71234567890 # setting the subscriber number
sset staticSetApply.0 i 1 # apply settings

sset staticSetMode.0 i 0 # set mode to none
5.10.2.8 Example of viewing settings

sset getUserByIndex.0 i 4 # set search at index 4
sset staticSetMode.0 i 1 # set show mode
swalk tableOfStSetUser # view the settings table, or
swalk stSetAuth # separate registration mode, or
swalk stSetAccessMode # separate maintenance mode, etc. .
5.10.2.9 Example of editing settings

sset getUserByNumplan.0 i 0 # set numbering plan to zero
sset getUserByNumber.0 s 71234567890 # setting the subscriber number
sset staticSetMode.0 i 2 # setting mode set

sset stSetNumplan.0 i 1 # change numbering plan to first
sset stSetCliro.0 i 1 # connect CLIRO service
sset stSetAONtypeNumber.0 i 2 # set the type of AON number - National
sset staticSetApply.0 i 1 # apply settings
sset staticSetMode.0 i 0 # set mode to none
704
5.10.2.10 Example of deleting a subscriber

sset getUserByID.0 i 15 sset # set search by ID 15
staticSetMode.0 i 4 sset # set del mode
staticSetApply.0 i 1 # apply settings
# mode none manually set is not required
Table K11 — Monitoring and configuring SIP subscribers (static subscribers)
smgSipUser 1.3.6.1.4.1.35265.1.2 Get {} List of static subscribers, root object

9.38
staticCheckStatus 1.3.6.1.4.1.35265.1.2 Get {} Search status by criteria.

9.38.1
None - no search, displays all static
subscribers;
Find user by index – subscriber search by index;
Find user by ID – subscriber search by ID;
Find users by numplan - search for subscribers by plan

numbering;
Find user by numplan and number - subscriber search by

number and numbering plan;
Find users by numplan and substring number - search

subscribers by partial number and numbering plan
staticResetCheck 1.3.6.1.4.1.35265.1.2 Set {} N Reset search. Assigning any value sets the
9.38.2 search status toNone.
numActiveUsers 1.3.6.1.4.1.35265.1.2 Get {} Number of active (registered) subscribers

9.38.3
numAllUsers 1.3.6.1.4.1.35265.1.2 Get {} Number of registered subscribers in the system

9.38.4
705
getUserByIndex 1.3.6.1.4.1.35265.1.2 Set {} N Setting the index of the subscriber to search. Value in
9.38.5 the range [0:numAllUsers) sets the status search in "
Set {} -1 Find user by index".
Setting value -1 with active search status "Find user by

index" sets the status to "None"
getUserByID 1.3.6.1.4.1.35265.1.2 Set {} N InstallationThe user ID to search.

9.38.6
Set {} -1 Setting values from one or more sets the
search to the status "Find user by ID".
Setting value -1 with active search status "Find user by

ID" sets the status to "None"
getUserByNumplan 1.3.6.1.4.1.35265.1.2 Set {} N Setting the numbering plan for searching subscribers.
9.38.7
Set {} -1 Setting value -1 if the search status was "Find
users by numplan",
"Find user by numplan and number" or "Find users by
numplan and substring number" sets status in "none".
If the value is from zero or more, then the search

mode setting priority is as follows:
If givengetUserByNumber, the mode is activated

search"Find user by numplan and number"; If given
getUserBySubNumber, activated search mode"Find
users by numplan and substring number";
If not setgetUserByNumber and

getUserBySubNumber, the search mode "Find users
by numplan" is activated
getUserByNumber 1.3.6.1.4.1.35265.1.2 Set {}S Setting the number to search for a subscriber in conjunction with
9.38.8 the numbering plan.
Set{}
"NULL" Number length from1 to 32 digits.
When the numbering plan is set, the search status is

set to "Find user by numplan and number", otherwise
the search status is not is changing.
To reset the number, set the valueNULL, when this if
search status was "Find user by numplan and

number", the search status will change to "None".
706
getUserBySubNumber 1.3.6.1.4.1.35265.1.2 Set {}S Setting a partial number to search for subscribers
9.38.9 in conjunction with the numbering plan.
Set{}
"NULL" Number length from1 to 32 digits.
When the numbering plan is set, the search status

is set to "Find users by numplan and substring
number", otherwise status search does not change.
To reset the number, set the valueNULL, when this if

the search status was "Find users by numplan and
substring number", the status will change to "None".
tableOfUsers 1.3.6.1.4.1.35265.1.2 Get {} Table of static subscribers, root object

9.38.10
tableOfUsersEntry 1.3.6.1.4.1.35265.1.2 Get {} cm.TableOfUsers

9.38.10.1
userID 1.3.6.1.4.1.35265.1.2 Get {} Subscriber ID.

9.38.10.1.2
Get {}.x To get information on a specific subscriber,
1.3.6.1.4.1.35265.1.2 you need to addOID is its index.
9.38.10.1.2.x
userRegState 1.3.6.1.4.1.35265.1.2 Get {} Subscriber registration status.

9.38.10.1.3
9.38.10.1.3.x
0 - not registered
1 - registered
userNumplan 1.3.6.1.4.1.35265.1.2 Get {} subscriber's numbering plan.

9.38.10.1.4
9.38.10.1.4.x
userNumber 1.3.6.1.4.1.35265.1.2 Get {} Subscriber number.

9.38.10.1.5
9.38.10.1.5.x
707
userIp 1.3.6.1.4.1.35265.1.2 Get {} Subscriber's IP address.

9.38.10.1.6
9.38.10.1.6.x
If address is unknown, return value 0.0.0.0
userPort 1.3.6.1.4.1.35265.1.2 Get {} Subscriber port.

9.38.10.1.7
9.38.10.1.7.x
userDomain 1.3.6.1.4.1.35265.1.2 Get {} SIP domain of the subscriber.

9.38.10.1.8
9.38.10.1.8.x
userMaxActiveLines 1.3.6.1.4.1.35265.1.2 Get {} The number of incoming/outgoing lines in the

9.38.10.1.9 combined mode of operation.
Get {}.x
1.3.6.1.4.1.35265.1.2 To get information on a specific subscriber,
9.38.10.1.9.x you need to addOID is its index.
userActiveCallCount 1.3.6.1.4.1.35265.1.2 Get {} The number of active calls while working in

9.38.10.1.10 co-located mode.
Get {}.x
userRegExpires 1.3.6.1.4.1.35265.1.2 Get {} Time until registration expires in seconds. To get

9.38.10.1.11 information on a specific subscriber, you need to
Get {}.x addOID is its index.
1.3.6.1.4.1.35265.1.2
9.38.10.1.11.x
userLinesMode 1.3.6.1.4.1.35265.1.2 Get {} Line operation mode.

9.38.10.1.12
1.3.6.1.4.1.35265.1.2 you need to addOID by its index:
9.38.10.1.12.x
0 - combined
1 - separate
708
userMaxIngressLines 1.3.6.1.4.1.35265.1.2 Get {} The number of incoming lines when

9.38.10.1.13 working in split mode.
Get {}.x
userMaxEgressLines 1.3.6.1.4.1.35265.1.2 Get {} The number of outgoing lines when working

9.38.10.1.14 in split mode.
Get {}.x
userActiveIngressCount 1.3.6.1.4.1.35265.1.2 Get {} The number of active incoming calls when

Get {}.x
userActiveEgressCount 1.3.6.1.4.1.35265.1.2 Get {} The number of active outgoing calls when

Get {}.x
stSetAuthLog 1.3.6.1.4.1.35265.1.2 Get {} Authorization login

9.38.15.1.14
Set{}S
staticModeSettings 1.3.6.1.4.1.35265.1.2 Get {} Operating mode with subscriber settings.

9.38.11
None - work with settings is disabled
Show - show settings
Set - change settings
Add - add a subscriber
Del - delete a subscriber
Statuses "Show", "Set" and "Del" display the settings

only if search status by criteria is not equal "none"
709
staticSetMode 1.3.6.1.4.1.35265.1.2 Set {} N Setting the operating mode with subscriber settings.
9.38.12
0 - None mode
1 - Show mode
2 - Set mode
3 - Add mode
4 - Del mode
staticSetReset 1.3.6.1.4.1.35265.1.2 Set {} N Resetting the changes made to the settings (if they
9.38.13 have not been applied) in the operating modes "Set"
and "Add" are ignored in other modes.
staticSetApply 1.3.6.1.4.1.35265.1.2 Set {} N Apply settings, add or remove a subscriber.

9.38.14
In the “Set” new settings are activated;
In "Mode"Add" subscriber is created, index for

subscriber search is set to the index of the newly
created subscriber, the search status switches to "
Find user by index" and mode work with settings is
set to "show";
In the “Del” the user is deleted, status search and

operation mode with settings are set to “None"
In modes "None" and
"Show" is ignored.
tableOfStSetUser 1.3.6.1.4.1.35265.1.2 Get {} Static subscriber settings table, root object

9.38.15
tableOfStSetUserEntry 1.3.6.1.4.1.35265.1.2 Get {} cm.TableOfStSetUser

9.38.15.1
stSetId 1.3.6.1.4.1.35265.1.2 Get {} Subscriber ID

9.38.15.1.2
stSetName 1.3.6.1.4.1.35265.1.2 Get {} Caller Display Name

9.38.15.1.3
Set{}S
710
stSetIpAddr 1.3.6.1.4.1.35265.1.2 Get {} subscriber IP address

9.38.15.1.4
Set {} A
stSetSIPdomain 1.3.6.1.4.1.35265.1.2 Get {} SIP domain

9.38.15.1.5
Set{}S
stSetNumber 1.3.6.1.4.1.35265.1.2 Get {} Phone number

9.38.15.1.6
Set{}S
stSetNumplan 1.3.6.1.4.1.35265.1.2 Get {} Numbering plan

9.38.15.1.7
Set {} N
stSetAONnumber 1.3.6.1.4.1.35265.1.2 Get {} AON number

9.38.15.1.8
Set{}S
stSetAONtypeNumber 1.3.6.1.4.1.35265.1.2 Get {} AON number type:

9.38.15.1.9
Set {} N 0 - Unknown
1-Subscriber
2-National
3 – International
4 – Network specific
5 – No change (from call)
stSetProfile 1.3.6.1.4.1.35265.1.2 Get {} SIP profile

9.38.15.1.10
Set {} N
stSetCategory 1.3.6.1.4.1.35265.1.2 Get {} Caller ID category:

9.38.15.1.11
Set {} N 0 - No change (from call)
1..10 - Category selection
stSetAccessCat 1.3.6.1.4.1.35265.1.2 Get {} Access category

9.38.15.1.12
Set {} N
711
stSetAuth 1.3.6.1.4.1.35265.1.2 Get {} Authorization type:

9.38.15.1.13
Set{}S none - no authorization
register - authorization REGISTER
register_and_invite - REGISTER and INVITE authorization
stSetAuthLog 1.3.6.1.4.1.35265.1.2 Get {} Authorization login

9.38.15.1.14
Set{}S
stSetAuthPass 1.3.6.1.4.1.35265.1.2 Get {} Authorization password

9.38.15.1.15
Set{}S
stSetCliro 1.3.6.1.4.1.35265.1.2 Get {} ServiceCLIRO

9.38.15.1.16
Set {} N 0 - not installed
1 - installed
stSetPbxProfile 1.3.6.1.4.1.35265.1.2 Get {} PBX profile

9.38.15.1.17
Set {} N
712
stSetAccessMode 1.3.6.1.4.1.35265.1.2 Get {} Subscriber service mode:

9.38.15.1.18
Set {} N 0 - Enabled
1 - Off 1
2 - Off 2
3 - Ban 1
4 - Prohibition 2
5 - Prohibition 3
6 - Prohibition 4
7 - Prohibition 5
8 - Prohibition 6
9 - Prohibition 7
10 - Prohibition 8
11 - Eliminated
12 - Off
stSetLines 1.3.6.1.4.1.35265.1.2 Get {} Number of lines when working in combined

9.38.15.1.19 mode
Set {} N
stSetNoSRCportControl 1.3.6.1.4.1.35265.1.2 Get {} Ignore source port after registration

9.38.15.1.20
Set {} N 0 - take into account
1 - ignore
stSetBLFusage 1.3.6.1.4.1.35265.1.2 Get {} Event subscription (BLF)

9.38.15.1.21
Set {} N 0 - disable
1 - allow
stSetBLFsubScribers 1.3.6.1.4.1.35265.1.2 Get {} Number of event subscribers

9.38.15.1.22
Set {} N
713
stSetIntercomMode 1.3.6.1.4.1.35265.1.2 Get {} Intercom call type

9.38.15.1.23
Set {} N 0 - Single sided
1 - Double sided
2 - Normal call
3 - Reject
stSetIntercomPriority 1.3.6.1.4.1.35265.1.2 Get {} Intercom call priority (1..5)

9.38.15.1.24
Set {} N
stSetLinesMode 1.3.6.1.4.1.35265.1.2 Get {} Line operation mode:

9.38.15.1.25
Set {} N 0 - Combined
1 - Separate
stSetIngressLines 1.3.6.1.4.1.35265.1.2 Get {} Number of incoming lines when operating

9.38.15.1.26 in split mode
Set {} N
0 - unlimited
stSetEgressLines 1.3.6.1.4.1.35265.1.2 Get {} Number of outgoing lines when operating in

9.38.15.1.27 split mode
Set {} N
0 - unlimited
stSetMonitoringGroup 1.3.6.1.4.1.35265.1.2 Get {} Observation groupBLF

9.38.15.1.28
Set {} N
714
stSetIntercomHeader 1.3.6.1.4.1.35265.1.2 Get {} AskSIP header for intercom:

9.38.15.1.29
Set {} N 0 - Answer-Mode: Auto
1 - Alert-Info: Auto Answer
2 - Alert-Info: info=alert-autoanswer
3 - Alert-Info: Ring Answer
4 - Alert-Info: info=RingAnswer
5 - Alert-Info: Intercom
6 - Alert-Info: info=intercom
7 - Call-Info:=\;answer-after=0
8 - Call-Info: \\;answer-after=0
9 - Call-Info: ;answer-after=0
stSetIntercomTimer 1.3.6.1.4.1.35265.1.2 Get {} Set the pre-response pause passed in the

9.38.15.1.30 parameteranswer after
Set {} N
5.10.3 Monitoring and configuring groups of dynamic subscribers

In the description of the functions of monitoring and configuring the commands for calling utilitiesSNMP
will are represented by the following scripts for brevity and clarity of presentation:
Scriptswalk, which implements reading values:
# !/bin/bash
/usr/bin/snmpwalk -v2c -cpublic-m +ELTEX-SMG192.0.2.1"$@"
Scriptsset, which implements setting values:
# !/bin/bash
/usr/bin/snmpset -v2c -cprivate-m +ELTEX-SMG192.0.2.1"$@"
5.10.3.1 Monitoring
-When searching for dynamic subscribers, only registered subscribers will be displayed.
Dynamic subscriber monitoring can be done in several ways:

1. By group and index of the subscriber;
2. By subscriber ID;
715
3. According to the numbering plan and the full number of the subscriber;
4. According to the numbering plan and partial subscriber number.
For monitoring:
1. Reset search status;
2. Set search criteria (optional);
3. Display information.
5.10.3.2 Index search example
sset groupResetCheck.0 i 1 sset # reset search status

getGroupByIndex.0 i 0 sset # select zero group
getGroupUserByIndex.0 i 4 swalk # set search at index 4
tableOfGroupUsers # query table with subscriber information
Result:
ELTEX-SMG::GroupUserID.0.4= INTEGER:4 ELTEX-SMG::RegState.0.4=

INTEGER:1 ELTEX-SMG::Numplan.0.4= INTEGER:0 ELTEX-SMG::Number.
0.4=STRING:240011 ELTEX-SMG::Ip.0.4=IPAddress:192.0.2.32 ELTEX-
SMG::Port.0.4= Gauge32:5060 ELTEX-SMG::Domain.0.4= STRING:
dynsmg ELTEX-SMG::MaxActiveLines.0.4=INTEGER: -1 ELTEX-
SMG::ActiveCallCount.0.4=INTEGER: -1 ELTEX-SMG::RegExpires.0.4=
INTEGER:55 ELTEX-SMG::TableOfGroupUsersEntry.13.0.4= INTEGER:1
ELTEX-SMG::TableOfGroupUsersEntry.14.0.4= INTEGER:3 ELTEX-
SMG::TableOfGroupUsersEntry.15.0.4= INTEGER:4 ELTEX-
SMG::TableOfGroupUsersEntry.17.0.4= INTEGER:0
5.10.3.3 Example of searching by subscriber ID
sset groupResetCheck.0 i 1 # reset search status

sset getGroupUserByID.0 i 2 # setting subscriber ID
swalk tableOfGroupUsers # query table with subscriber information
716
5.10.3.4 Dial plan and partial number search example
sset groupResetCheck.0 i 1 sset # reset search status

getGroupUserByNumplan.0 i 0 sset # set numbering plan to zero
getGroupUserBySubNumber.0 s 24001 swalk # set part number
tableOfGroupUsers # query table with subscriber information
Result:
ELTEX-SMG::GroupUserID.0.0= INTEGER:0 ELTEX-SMG::GroupUserID.0.1

= INTEGER:1 ELTEX-SMG::RegState.0.0= INTEGER:1 ELTEX-
SMG::RegState.0.1= INTEGER:1 ELTEX-SMG::Numplan.0.0= INTEGER:0
ELTEX-SMG::Numplan.0.1= INTEGER:0 ELTEX-SMG::Number.0.0=STRING:
240015 ELTEX-SMG::Number.0.1=STRING:240014 ELTEX-SMG::Ip.0.0
=IPAddress:192.0.2.32 ELTEX-SMG::Ip.0.1=IPAddress:192.0.2.32 ELTEX-
SMG::Port.0.0= Gauge32:5060 ELTEX-SMG::Port.0.1= Gauge32:5060
ELTEX-SMG::Domain.0.0= STRING: dynsmg ELTEX-SMG::Domain.0.1=
STRING: dynsmg ELTEX-SMG::MaxActiveLines.0.0=INTEGER: -1 ELTEX-
SMG::MaxActiveLines.0.1=INTEGER: -1 ELTEX-SMG::ActiveCallCount.0.0
=INTEGER: -1 ELTEX-SMG::ActiveCallCount.0.1=INTEGER: -1 ELTEX-
SMG::RegExpires.0.0= INTEGER:98 ELTEX-SMG::RegExpires.0.1=
INTEGER:100 ELTEX-SMG::TableOfGroupUsersEntry.13.0.0= INTEGER:1
ELTEX-SMG::TableOfGroupUsersEntry.13.0.1= INTEGER:1 ELTEX-
SMG::TableOfGroupUsersEntry.17.0.1= INTEGER:0
5.10.3.5 Viewing information without using search
sset groupResetCheck.0 i 1 # reset search status

sset getGroupUserByID.0 i 2 # display all subscribers
717
5.10.3.6 Configuration
Configuration involves the following operations on groups of dynamic subscribers:
1. View settings;
2. Editing settings;
3. Creation of a new subscriber;
4. Removal.
To view settings:
1. Set a group by index or ID;
2. Select the configuration mode - view;
3. Display the required data.
To edit settings:
2. Select the configuration mode - editing;
3. Set the necessary settings;
4. Apply settings.
To create a new group:
1. Select the configuration mode - creation;
2. Set the necessary settings for the new group;
3. Apply settings.
To remove a group:
2. Select the configuration mode - delete;
3. Apply settings.
If necessary, you can roll back unapplied changes by working in the modes of adding a group or editing the
settings of an existing one.
-Deleting a group is irreversible, only a complete rollback of the configuration is possible throughWEB or
CLI.
718
5.10.3.7 Example of creating a new group
sset groupSetMode.0 i 3 # set add mode

sset groupSetApply.0 i 1 # apply settings
sset groupSetMode.0 i 0 # set mode to none
5.10.3.8 Example of viewing settings
sset groupByIndex.0 i 2 # select group by index - second

sset groupSetMode.0 i 1 # set show mode
swalk tableOfGroupSet # view the settings table, or
swalk groupSetMaxReg # the maximum number of subscribers in the group, or
swalk groupSetName # group name, etc.
5.10.3.9 Example of editing settings
sset groupByID.0 i 3 sset # select group by ID - third

groupSetMode.0 i 2 sset # set mode set
groupSetCliro.0 i 1 sset # connect CLIRO service
groupSetNumplan.0 i 3 sset # set the third numbering plan
groupSetIntercomMode.0 i 3 sset # disable intercom calls
groupSetApply.0 i 1 # apply changes
sset groupSetMode.0 i 0 # set mode to none
5.10.3.10 Delete group example
sset groupByID.0 i 3 sset # select group by ID - third

groupSetMode.0 i 4 sset # set del mode
groupSetApply.0 i 1 # apply changes
# no need to manually set the none mode
719
Table K12 - Monitoring and configuring groups of dynamic subscribers
smgSipUserGroup 1.3.6.1.4.1.35265.1. Get {} List of dynamic subscriber groups, root

29.39 object
groupCheckStatus 1.3.6.1.4.1.35265.1. Get {} Search status by criteria.

29.39.1
None - no search, displays all dynamic
subscribers
Find user by group and user index - search

subscriber by group index and subscriber
index in the group
Find user by ID - search for a subscriber by ID
Find user by numplan and number - search

subscriber by number and numbering plan
Find user by numplan and number - search

subscriber by partial number and numbering
plan
groupResetCheck 1.3.6.1.4.1.35265.1. Set {} N Reset search to status "None". To reset set

29.39.2 any value
numGroups 1.3.6.1.4.1.35265.1. Get {} Number of subscriber groups

29.39.3
numInGroup 1.3.6.1.4.1.35265.1. Set {} N The number of subscribers in the group.

29.39.4
To use, set the value to the group number.
The answer will return the number of
subscribers.
Returns -1 if non-existent is given group

number.
numActiveInGroup 1.3.6.1.4.1.35265.1. Set {} N The number of active (registered) subscribers

29.39.5 in the group.
To use, set the value to the group number.

The answer will return the number of
subscribers.
Returns -1 if non-existent is given group

number.
720
getGroupByIndex 1.3.6.1.4.1.35265.1. Set {} N Setting the subscriber index in the group to search
29.39.6 for a subscriber in conjunction with the group index.
Setting a value from zero or more sets the group
index and sets the search status to "Find user by
numplan and number".
Setting value -1 – with active status search"Find

user by group and user index" sets status to "
none".
Setting a non-existent group index resets the

search status to "none".
getGroupUserByIndex 1.3.6.1.4.1.35265.1. Set {} N Setting the subscriber index in the group to

29.39.7 search for a subscriber in conjunction with the
group index. The group index must be set before
use, seeGetGroupByIndex.
The search status is set to "Find user by

numplan and number".
Setting value -1 – with active status search"Find

user by group and user index" sets status to "
none".
getGroupUserByID 1.3.6.1.4.1.35265.1. Set {} U InstallationID to search for a subscriber.

29.39.8 Installation values from one or more sets the
search to the status "Find user by ID".
When set to zero if there was a search status

"Find user by ID", status is set to "None"
getGroupUserByNumplan 1.3.6.1.4.1.35265.1. Set {} N Setting the numbering plan to search for a

29.39.9 subscriber in conjunction with the number.
Setting value -1, when active status search"

Find user by numplan and number" sets status
to "none".
If the value is greater than zero and a number

is set
(cm.getGroupUserByNumber) - search set to

status "Find user by numplan and number",
otherwise, the search status does not change.
721
getGroupUserByNumber 1.3.6.1.4.1.35265.1. Set{}S Setting the number to search for a subscriber in

29.39.10 conjunction with the numbering plan.
Set{}
"NULL" Number length from1 to 32 characters.
When set to a value greater than or equal to zero,

the search status becomes "Find user by
numplan and number",
To reset the number, set the valueNULL,

meanwhile, if

number", the status will change to "None".
getGroupUserBySubNumber 1.3.6.1.4.1.35265.1. Set{}S Setting a partial number to search for a subscriber

29.39.11 in conjunction with the numbering plan.
Number length from1 to 32 characters.
When set to a value greater than or equal to zero,

the search status becomes "Find user by numplan
and substring number",
To reset the number, set the valueNULL,

meanwhile, if

number", the status will change to "None".
tableOfGroupUsers 1.3.6.1.4.1.35265.1. Get {} Table of dynamic subscribers, root object

29.39.12
tableOfGroupUsersEntry 1.3.6.1.4.1.35265.1. Get {} cm.TableOfGroupUsers

29.39.12.1
groupUserID 1.3.6.1.4.1.35265.1. Get {} Subscriber ID.

29.39.12.1.3
Get {}.xx To get information on a specific subscriber,
1.3.6.1.4.1.35265.1. you need to addOID by its index groups and
29.39.12.1.3.xx ID.
722
groupUserRegState 1.3.6.1.4.1.35265.1. Get {} Subscriber registration status.

29.39.12.1.4
29.39.12.1.4.xx ID.
0 - not registered
1 - registered
groupUserNumplan 1.3.6.1.4.1.35265.1. Get {} subscriber's numbering plan.

29.39.12.1.5
29.39.12.1.5.xx ID.
groupUserNumber 1.3.6.1.4.1.35265.1. Get {} Subscriber number.

29.39.12.1.6
29.39.12.1.6.xx ID.
groupUserIp 1.3.6.1.4.1.35265.1. Get {} Subscriber's IP address.

29.39.12.1.7
29.39.12.1.7.xx ID.
If address is unknown, return value

0.0.0.0
groupUserPort 1.3.6.1.4.1.35265.1. Get {} Subscriber port.

29.39.12.1.8
29.39.12.1.8.xx ID.
groupUserDomain 1.3.6.1.4.1.35265.1. Get {} SIP domain of the subscriber.

29.39.12.1.9
29.39.12.1.9.xx ID.
groupUserMaxActiveLines 1.3.6.1.4.1.35265.1. Get {} The number of incoming/outgoing lines in the

29.39.12.1.10 combined mode of operation.
Get {}.xx
1.3.6.1.4.1.35265.1. To get information on a specific subscriber,
29.39.12.1.10.xx you need to addOID by its index groups and
ID.
723
groupUserActiveCallCount 1.3.6.1.4.1.35265.1. Get {} The number of active calls while working in

29.39.12.1.11 co-located mode.
Get {}.xx
ID.
groupUserRegExpires 1.3.6.1.4.1.35265.1. Get {} Time until registration expires in seconds. To

29.39.12.1.12 get information on a specific subscriber, you
Get {}.xx need to addOID by its index groups andID.
1.3.6.1.4.1.35265.1.
29.39.12.1.12.xx
groupUserLinesMode 1.3.6.1.4.1.35265.1. Get {} Line operation mode.

29.39.12.1.13
29.39.12.1.13.xx ID.
0 - combined
1 - separate
groupUserMaxIngressLines 1.3.6.1.4.1.35265.1. Get {} The number of incoming lines when

Get {}.xx
ID.
groupUserMaxEgressLines 1.3.6.1.4.1.35265.1. Get {} The number of outgoing lines when working

29.39.12.1.15 in split mode.
Get {}.xx
ID.
groupUserActiveIngressCount 1.3.6.1.4.1.35265.1. Get {} The number of active incoming calls when

Get {}.xx
ID.
groupUserActiveEgressCount 1.3.6.1.4.1.35265.1. Get {} The number of active incoming calls when

Get {}.xx
ID.
724
groupUserGroupModeSettings 1.3.6.1.4.1.35265.1. Get {} Operation mode with settings of

29.39.13 groups of dynamic subscribers
None - work with settings is disabled
Show - show group settings
Set - change group settings
Add - add a group
Del - delete a group
groupUserGroupSetMode 1.3.6.1.4.1.35265.1. Set {} N Setting the mode of operation with a group of subscribers
29.39.14
0-None
1-Show
2 - set
3-Add
4 - Del
groupUserGroupSetReset 1.3.6.1.4.1.35265.1. Set {} N Resetting the changes made to the settings (if
29.39.15 they have not been applied) in the operating
modes "Set" and "Add", in other modes ignored.
groupUserGroupSetApply 1.3.6.1.4.1.35265.1. Set {} N Apply settings, add or remove a group.

29.39.16
In the “Set” new settings are activated;
In "Mode"Add" group is created, index for group

search is set to the index of the newly created
group, the search status switches to "Find group
settings by index" and how to work with settings
set to "show";
In the “Del” group is deleted, search status and

operation mode with settings are set to “None"
In modes "None" and
"Show" is ignored.
725
groupUserGroupFindStatus 1.3.6.1.4.1.35265.1. Get {} Group settings search status by criteria:

29.39.17
Without search - without search
Find group settings by Index - search for a group by

index
Find group settings by ID - search for a group by ID
groupFindStatus 1.3.6.1.4.1.35265.1. Get {} Group settings search status by criteria:

29.39.17
Without search - without search
Find group settings by Index - search for a group by

index
Find group settings by ID - search for a group by ID
groupResetFindStatus 1.3.6.1.4.1.35265.1. Set {} N Reset search to status "Without search". reset

29.39.18 set any value
groupByIndex 1.3.6.1.4.1.35265.1. Set {} N Setting the group index and search status in "Find
29.39.19 group settings by Index".
When installing -1, if the search status was "Find group

settings by Index", then the status becomes "Without
search"
groupByID 1.3.6.1.4.1.35265.1. Set {} N InstallationGroup ID (from one or more) and

29.39.20 search status in "Find group settings by ID".
When installing -1, if the search status was "Find group

settings by ID", then the status becomes "Without
search"
tableOfGroupSet 1.3.6.1.4.1.35265.1. Get {} Dynamic subscriber group settings table

29.39.21
tableOfGroupSetEntry 1.3.6.1.4.1.35265.1. Get {} cm.TableOfGroupSet

29.39.21.1
groupSetId 1.3.6.1.4.1.35265.1. Get {} group ID

29.39.21.1.2
groupSetName 1.3.6.1.4.1.35265.1. Get {} Group name

29.39.21.1.3
Set{}S
726
groupSetSIPdomain 1.3.6.1.4.1.35265.1. Get {} SIP domain

29.39.21.1.4
Set{}S
groupSetMaxReg 1.3.6.1.4.1.35265.1. Get {} Maximum number of subscribers in a group

29.39.21.1.5
Set {} N
groupSetProfile 1.3.6.1.4.1.35265.1. Get {} SIP profile

29.39.21.1.6
Set{}S
groupSetCategory 1.3.6.1.4.1.35265.1. Get {} Caller ID category:

29.39.21.1.7
Set {} N 0 - No change (from call)
1..10 - Category selection
groupSetAccessCat 1.3.6.1.4.1.35265.1. Get {} Access category

29.39.21.1.8
Set {} N
groupSetCliro 1.3.6.1.4.1.35265.1. Get {} ServiceCLIRO:

29.39.21.1.9
Set {} N 0 - not installed
1 - installed
groupSetPbxProfile 1.3.6.1.4.1.35265.1. Get {} PBX profile

29.39.21.1.10
Set {} N
727
groupSetAccessMode 1.3.6.1.4.1.35265.1. Get {} Subscriber service mode

29.39.21.1.11
Set {} N 0 - Enabled
1 - Off 1
2 - Off 2
3 - Ban 1
4 - Prohibition 2
5 - Prohibition 3
6 - Prohibition 4
7 - Prohibition 5
8 - Prohibition 6
9 - Prohibition 7
10 - Prohibition 8
11 - Eliminated
12 - Off
groupSetLines 1.3.6.1.4.1.35265.1. Get {} Number of lines when working in combined

29.39.21.1.12 mode
Set {} N
groupSetNumplan 1.3.6.1.4.1.35265.1. Get {} Numbering plan

29.39.21.1.13
Set {} N
groupSetNoSRCportControl 1.3.6.1.4.1.35265.1. Get {} Ignore source port after registration

29.39.21.1.14
Set {} N 0 - take into account
1 - ignore
groupSetBLFusage 1.3.6.1.4.1.35265.1. Get {} Event subscription (BLF)

29.39.21.1.15
Set {} N 0 - disable
1 - allow
groupSetBLFsubScribers 1.3.6.1.4.1.35265.1. Get {} Number of event subscribers

29.39.21.1.16
Set {} N
728
groupSetIntercomMode 1.3.6.1.4.1.35265.1. Get {} Intercom call type

29.39.21.1.17
Set {} N 0 - Single sided
1 - Double sided
2 - Normal call
3 - Reject
groupSetIntercomPriority 1.3.6.1.4.1.35265.1. Get {} Intercom call priority (1..5)

29.39.21.1.18
Set {} N
groupSetLinesMode 1.3.6.1.4.1.35265.1. Get {} Line operation mode:

29.39.21.1.19
Set {} N 0 - Combined
1 - Separate
groupSetIngressLines 1.3.6.1.4.1.35265.1. Get {} Number of incoming lines when operating

29.39.21.1.20 in split mode
Set {} N
groupSetEgressLines 1.3.6.1.4.1.35265.1. Get {} Number of outgoing lines when operating in

29.39.21.1.21 split mode
Set {} N
groupSetAONtypeNumber 1.3.6.1.4.1.35265.1. Get {} AON number type:

29.39.21.1.22
Set {} N 0 - Unknown
1-Subscriber
2-National
3 – International
4 – Network specific
5 – No change (from call)
groupSetMonitoringGroup 1.3.6.1.4.1.35265.1. Get {} Observation groupBLF

29.39.21.1.23
Set {} N
729
groupSetIntercomHeader 1.3.6.1.4.1.35265.1. Get {} AskSIP header for intercom:

29.39.21.1.24
Set {} N 0 - Answer-Mode: Auto
1 - Alert-Info: Auto Answer
2 - Alert-Info: info=alert-autoanswer
3 - Alert-Info: Ring Answer
4 - Alert-Info: info=RingAnswer
5 - Alert-Info: Intercom
6 - Alert-Info: info=intercom
7 - Call-Info:=\;answer-after=0
8 - Call-Info: \\;answer-after=0
9 - Call-Info: ;answer-after=0
groupSetIntercomTimer 1.3.6.1.4.1.35265.1. Get {} Set the pre-response pause passed in the

29.39.21.1.25 parameteranswer after
Set {} N
730
5.10.3.11 Obsolete OIDs

SomeOIDs have been changed and in subsequent releases old branches may be deleted or replaced by
new appointments. It is recommended to reconfigure monitoring systems and scripts to use newID.
Table K13 - Obsolete OIDs
eOneRSV 1.3.6.1.4.1.35265.1.29.7.1.8 Get {} Not used
1.3.6.1.4.1.35265.1.29.7.1.8.x Get {}.x
eOneRxEqualizer 1.3.6.1.4.1.35265.1.29.7.1.15 Get {} Not supported on newer hardware

versions, always -1
1.3.6.1.4.1.35265.1.29.7.1.15.x Get {}.x
smgCpuLoad 1.3.6.1.4.1.35265.1.29.17 Get {} Replaced bysmgCpuLoadTable
(1.3.6.1.4.1.35265.1.29.37)
smgTopCpuUsr 1.3.6.1.4.1.35265.1.29.17.1.x Get {} Replaced bycpuUsr
(1.3.6.1.4.1.35265.1.29.37.1.2.x)
smgTopCpuSys 1.3.6.1.4.1.35265.1.29.17.2.x Get {} Replaced bycpuSys
(1.3.6.1.4.1.35265.1.29.37.1.3.x)
smgTopCpuNic 1.3.6.1.4.1.35265.1.29.17.3.x Get {} Replaced bycpuNic
(1.3.6.1.4.1.35265.1.29.37.1.4.x)
smgTopCpuIdle 1.3.6.1.4.1.35265.1.29.17.4.x Get {} Replaced bycpuIdle
(1.3.6.1.4.1.35265.1.29.37.1.5.x)
smgTopCpuIo 1.3.6.1.4.1.35265.1.29.17.5.x Get {} Replaced bycpuIo
(1.3.6.1.4.1.35265.1.29.37.1.6.x)
smgTopCpuIrq 1.3.6.1.4.1.35265.1.29.17.6.x Get {} Replaced bycpuIrq
(1.3.6.1.4.1.35265.1.29.37.1.7.x)
smgTopCpuSirq 1.3.6.1.4.1.35265.1.29.17.7.x Get {} Replaced bycpuSirq

(1.3.6.1.4.1.35265.1.29.37.1.8.x)
731
smgTopCpuUsage 1.3.6.1.4.1.35265.1.29.17.8.x Get {} Replaced bycpuUsage
(1.3.6.1.4.1.35265.1.29.37.1.9.x)
5.10.3.12 MIB-2 OID Support (1.3.6.1.2.1) The

SMG supports the following MIB-2 branches:
• system (1.3.6.1.2.1.1) – general information about the system;
• interfaces (1.3.6.1.2.1.2) – information about network interfaces;
• snmp (1.3.6.1.2.1.11) – information about SNMP operation.
5.11 Appendix K. Provision of the SMG redundancy function
-Only available forSMG-2016/3016.
Starting from version3.14.0, the redundancy function has been implemented on the SMG. This function is
activated automatically installing an additional licenseSMG-RESERVE to master and SMG-RESERVE-SLAVE to
standby. The principle of operation is that the backup device is in sleep modeSLAVE), without carrying any
functions and not having its own IP address on the network, constantly monitors the main device (MASTER)
and, as soon as MASTER fails SLAVE, it takes over all functions, completely replacing the failed MASTER. For
a complete duplication of the function, the backup device constantly receives the current configuration and
other files necessary for operation from the main one.
ActivationA SLAVE device occurs after connecting it to a master device by creating a LAN and WAN
connection between them. As soon as the two devices see each other, it will lifetime updateSLAVE devices
up to 720 hours. This is the time for the full operation of SLAVE devices without a master (when the master
failed for any reason and was disconnected from SLAVE devices). If the pair is assembled successfully and
the gateway with the SMG-RESERVE license acts as the master, the time on the gateway with the SMG-
RESERVE-SLAVE license is restored to 720 hours.
-To restore the clock on the slave device, there must be two connections, as inLAN and WAN links.
Recovery time 5 minutes.
If the lifetimeSLAVE devices will end:

• If there is a connected gateway with an SMG-RESERVE license – change seniority (a gateway with an
SMG-RESERVE license will become a master device);
• In the absence of a connected gateway with an SMG-RESERVE license, active connections are terminated
and termination of operation (similar to the termination of the "demo" mode of operation).
-To provide redundancy functions, only the same type of devices are used SMG-2016.
732
Consider the connection diagrams:
Drawing54 - Single switch redundancy scheme
Drawing55 - Redundancy scheme for two switches in a stack

When redundant, the device is allocatedThere are 2 types of front port, local and global. On SMG-2016,
local ports are 0 and 1, global ports are 2 and 3. When connecting devices, you need to communication at
the same time on a local and global link. The redundancy scheme works according to the protocolIPv6,
during operation, devices exchange configuration and other files necessary to maintain up-to-date
information. To communicate via a local link, use4091 VLAN, global 4092 VLAN. In case of a break on a
local link devices exchange working files via a global link.
If the connection is broken on one of the links, the device initiates an accident.
733
Order of connection and reserve settings
The case of connecting to two switches will be consideredMES on the stack (drawing55). Initial condition:
two of the same typeSMG with reserve license, two MES switches in a stack. Stack setup on the switches is
made according to the documentation for the switches.
First you need to set up the passage of serviceVLANs on switches. At the ports where they will connected
global SMG links, VLAN 4092 should be allowed to pass through. In this case, the ports should skip and
othersVLANs configured on the SMG. Also the ports that the SMG will connect to are should be merged
intoport channel. The final scheme at this stage will look like this:
Drawing56 - Scheme of combining ports in a port-chanel

Next, the master is connected (master) SMG. At this stage, only global links. After thatThe SMG is put into
operation and becomes the master. Scheme at this stage will look like this:
Drawing57 - Connection diagram of the leading SMG (master)
734
After that, to the leading (master) SMG local link connects slave SMG. At this stage you should wait until
the devices detect each other and start working as a slave-master pair (see section Monitoring - Reserve).
The diagram at this stage will look like this:
Drawing58 – Wiring diagram of the slave SMG (slave)

After the master-slave pair has been formed, you can connectglobal links to slave device:
Drawing59 - Global links wiring diagram

The assembly of the reserve is completed. Monitoring should ensure that bothSMGs see each other both
locally and globally.
In case of problems with the establishment of master-slave relationships or lack of visibility on the local
and global links, you should check that all configuration steps have been completed correctly.
Determination of precedence
When determining which of the devices will beMASTER or SLAVE uses the following algorithm:
1. If the local links are not active when the device is turned on, the device becomes MASTER.
2. If global links are not active when the device is turned on, the device becomes SLAVE.
3. If, during operation, a SLAVE is connected to a device that is MASTER, then seniority will not
change.
4. If you connect MASTER to a device that is MASTER during operation, then seniority will be determined
based on the serial number, whoever has a higher serial number will become MASTER.
735
Block diagram for determining seniority:
Handling connection via global or local link.
736
-When connecting a device to an already working one, it is necessary to disable allWAN links to
connected device, connectLAN link to running (MASTER) SMG, wait agreement, connectWAN links
to the SLAVE, otherwise the newly connected device may defined asMASTER and transfer your
out-of-date working files.
Working files are transferred immediately after connecting toMASTER, every time after recording
configuration onflash, 10 seconds after each configuration change, and periodically every 180 seconds.
List of transferred files:

• configuration file written in flash;
• the current running configuration file;
• keys for creating ssh tunnels;
• database of registered subscribers;
• linux user files;
• password files for web-interface and CLI users;
• all dynamic firewall address lists;
• keys and certificates for the https protocol.
During operation, the user can accessSLAVE web interface, for this you need to go to tab "Monitoring" -
"Reservation" - "open Web" or by the link:http://192.168.0.100:8080/ login, where instead of 192.168.0.100
enter the MASTER IP address.
737
E stream redundancy1
Starting from version3.17.0, the E1 stream reservation function is implemented on the SMG. This function
activated automatically by installing an additional licenseSMG-RESERVE-E1 (required availability of a license
SMG-RESERVE or SMG-RESERVE-SLAVE). How it works: on a slave device flows are turned off E1, thus the
influence of additional threads on the master device stops. This shutdown allows you to connect two streams
on the patch panel to each other from the master and slave devices, which will not affect each other.
After the seniority change, the flows are switched between the master and slave gateways. Active
connections are destroyed during a precedence change.
Cable wiring diagram for redundancy E1
5.12 Appendix M - Safety recommendations

When installing and configuringSMG should pay attention to security settings - organizations access to
the management and monitoring of the PBX, as well as the security of call processing. You should also
pay attention to backing up the configuration.
Organization of access means:
• change of standard passwords for WEB and CLI;
• creation of limited accounts for certain types of settings and monitoring;
738
• configuring restrictions on IP addresses and/or subnets from which configuration and
monitoring;
• setting up a static firewall that restricts access to signaling interfaces and managing only trusted
nodes;
• setting up a dynamic firewall, which will automatically cut off unwanted access attempts for
public interfaces.
-ApplicationSMG on a public network is undesirable without the use of additional tools security, such as
the session border controller (SBC), firewall (firewall), etc.
5.12.1 Changing passwords on WEB and CLI
-Changing account passwordsadmin/root is required to ensure device security.
Changing passwords is done through the menu "Users: Management».

Change PasswordWEB for the admin account is made in the "Set password web interface
administrator.
Change PasswordCLI for the admin account is made in the "Set administrator password" block Fortelnet and
ssh. More detailed information on setting can be found in the Menu section. "Control".
Change account passwordroot is done via the shell. In order to change the password you need connect to
SMG via ssh/console and run the following commands:
SMG2016>
SMG2016> sh (exit cli mode to shell mode) /home/
admin #
/home/admin#
/home/admin # passwd root (command to change the root password)
Changing password for root
New password: (enter new password) Retype

password: (repeat new password) Password
for root changed by root
/home/admin#
/home/admin#
/home/admin#save
tar: removing leading '/' from member names
New image 0
Restored successful
/home/admin#
739
5.12.2 Creating restricted accounts

Create restricted accounts forweb is made through the menu "Users: Management».
• In the "Users of the web interface" block, click"Add";

• Set username and password;
• Select access permissions.
ForCLI creation of restricted accounts is not supported. More information on settings can be found under
"Control".
5.12.3 Restricting access to signaling and control interfaces

Restrictions are configured in the menu "SettingsTCP/IP -> "Network Interfaces".
• Go to network interface settings.
• In the "Services" block, disable all management protocols that are not used on the interface and
alarms.
• For the management interface, it is recommended to allow access only to the web interface and ssh
More detailed information on setting up can be found in the sectionNetwork interfaces. Access
to the device by protocoltelnet must be disabled via public IP address.
Management must be allowed NOT through public addresses. If you still use management through
publicIP, then it is necessary to use the list of allowed IP- addresses - you need to whitelist the address
from which the connection will be allowed. All others must be denied access.
CHANGING STANDARD PORTS TO ACCESS THE DEVICE The setting is made in the
menu"SettingsTCP/IP" -> "Network Settings"
• Change standard (22 for ssh and 23 for telnet) access ports to the device via ssh/telnet protocols
• The standard port for accessing the device via the web (http protocol) can be changed via the CLI. To
do this, you need to connect to the SMG via ssh/console and execute the following commands:
SMG2016>
SMG2016>config
Entering configuration mode.
SMG2016-[CONFIG]> network
Entering Network mode.
SMG2016-[CONFIG]-NETWORK>
PORT Number in the range 1-65535
SMG2016-[CONFIG]-NETWORK> set settings web (specify the required port in the range 1-65535)
To accessThe web interface is recommended to use the HTTPS protocol. Customize it to work can be in the
section"Security" → "SettingsSSL/TLS.In the SSL/TLS settings "Protocol interactions withweb configurator,
the "HTTPS only" mode must be selected. Also possible use authorization throughPAM/RADIUS. For more
information on setting up, see find in sectionSettingSSL/TLS.
740
SETTING THE LIST OF ALLOWEDIP ADDRESSES
The setting is made in the menu"Security" -> "List of allowedIP addresses.
• Whitelist the addresses from which access to the device is allowed via the web configurator and
protocolstelnet/ssh
• Enable the option "Access only for authorized IP addresses";
• Press buttons"Apply"And"Confirm".
More detailed information on setting up can be found in the sectionAllowed ListIP addresses.
5.12.4 Setting up a static firewall

A static firewall is used to restrict access to network interfaces according to a list of predefined rules.
The setting is made in the menu "Security" -> "Static firewall".

• Go to the firewall settings;
• Create a firewall profile by clicking the button"Add";
• Set profile name, press"Further";
• Set up filtering rules for incoming and outgoing traffic. At the same time, it must be remembered
that if the incoming or outgoing packet does not fall under any filtering rule, then the action is
applied to it"accept"(allow the packet to pass). Therefore, if required allow access to only some hosts
and deny all others, then you need to configure the firewall profile so that the last rule is a rule with
a source type and a destination of "Any" and an action"Reject"orDrop(drop packet with notification
byICMP or drop silently);
• In the "Interface" block, select the network interfaces for which filtering will be applied;
• Press the button"Save",located under the list of interfaces;
• Press the button"Apply"located at the top of the page;
• Press the button"Save"located above the filter tables.
More detailed information on setting up can be found in the sectionStatic firewall.
5.12.5 Configuring a dynamic firewall

A dynamic firewall is used to restrict access to network interfaces based on the analysis of requests to various
services. If repeated unsuccessful attempts to access the service from the sameIP addresses are temporarily
blocked by the dynamic firewall. If an address is temporarily blocked several times, it is permanently blocked
in the black list of addresses.
The setting is made in the menu "Security" -> "Dynamic Firewall".

• Go to the firewall settings;
• Whitelist addresses of trusted hosts and subnets;
• Check the box "Enable";
• Press the button"Apply".
More detailed information on setting up can be found in the sectionDynamic firewall.
Not recommended for signalingSIP use standard port 5060.

It is necessary to periodically check the information in the section"Security" → "Log of blocked addresses". It
displays a list of those blocked by the dynamic firewall addresses from which an unsuccessful attempt was
made to gain access to the device.
741
It is recommended to periodically change passwords to access the device throughweb/ssh. Shift policy
passwords must be determined by your security service.
-It is recommended to use the latest software version:https://eltex-co.ru/support/downloads/
742
TECHNICAL SUPPORT
For technical advice on the operation of the equipment of LLC "Enterprise" ELTEX ", you can
contact the Service Center of the company:
Feedback form on the site:https://eltex-co.ru/support/ service
desk:https://servicedesk.eltex-co.ru
On the official website of the company you can find technical documentation and software for
the products of ELTEX Enterprise LLC, refer to the knowledge base, leave an interactive
application or consult the Service Center engineers at the technical forum:
Official website of the company:https://eltex-co.ru/

Technical forum:https://eltex-co.ru/forum
Knowledge base:https://docs.eltex-co.ru/display/EKB/Eltex+Knowledge+Base
Download Center:https://eltex-co.ru/support/downloads

SMG-1016M 2016 3016 User Manual 3.20.5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SMG-1016M 2016 3016 User Manual 3.20.5

Uploaded by

Copyright:

Available Formats

Translated from Russian to English - www.onlinedoctranslator.

SMG-1016M, SMG-2016, SMG-3016

2 Conventions and target audience ............................................................... .................23

3 Description of products .................................................. ................................................. ............25

3.2 Product description .................................................. ................................................. .........................25

3.2.2.2 MiniIP PBX ............................................... ................................................. ................................................. ... 28

3.2.3.1 StructureSMG-1016M ............................................... ................................................. ................................... 31

3.2.3.3 StructureSMG-3016............................................... ................................................. ............................................... 33

3.2.3.4 Principle of operationSMG ................................................. ................................................. ................................... 34

3.2.4 Main technical parameters ............................................... ................................................. ..............35

3.2.6.5 Light indication of accidents .............................................. ................................................. .........................54

3.2.9.1 Password recoveryCLI ................................................. ................................................. ......................... 56

3.2.10.1 SMG-1016M ............................................... ................................................. ................................................. ...... 58

3.2.10.2 SMG-2016............................................... ................................................. ................................................. ........... 59

3.2.10.3 SMG-3016............................................... ................................................. ................................................. ........... 59

3.2.11 Safety Instructions ............................................................... ................................................. ...........59

3.2.11.2 Electrical safety requirements............................................................... ................................................. ................. 59

3.2.11.3 Precautions in the presence of static electricity .............................................................. ....................... 60

3.2.12.4 Installing power modules .................................................................. ................................................. .............................. 64

3.2.12.5 Opening the housing ............................................... ................................................. ............................................. 65

3.2.12.6 Installing submodules .................................................. ................................................. ................................... 67

3.2.12.8 Installing SSDs for SMG-1016M.................................................................. ................................................. ..... 73

3.2.12.9 Installing SATA drives for SMG-2016, SMG-3016 ................................... ................................................. 74

4 Device configuration .................................................................. ................................................78

4.1.2 Monitoring .................................................. ................................................. ................................................. ..88

4.1.2.5 MonitoringSFP modules.................................................................... ................................................. ............................... 96

4.1.2.6 Monitoringswitch front ports ............................................... ................................................. .........97

4.1.2.10 Drive information .............................................................. ................................................. .........................105

4.1.3 Flows E1 ................................................. ................................................. ................................................. ...107

4.1.3.2 Selecting the signaling protocol .................................................. ................................................. .................109

4.1.3.3 Setting physical parameters .................................................................. ................................................. ...........109

4.1.3.5 Setting up the SS-signaling protocol7 (SS7) ............................................... ...............................................115

4.1.4.1 Creating a dial plan prefix .................................................................. ................................................. .....122

4.1.4.3 Examples of how the mask works .............................................................. ................................................. ................................128

4.1.4.4 Example of how timers work .............................................................. ................................................. ...............................129

4.1.5 Routing ................................................... ................................................. ............................................131

4.1.5.2 OKS-line groups7 ................................................. ................................................. ...................................135

4.1.6.1 SIP subscribers.................................................... ................................................. ................................................. ...185

4.1.6.2 PRI profiles............................................... ................................................. ................................................. ....197

4.1.6.5 PRI subscribers.................................................... ................................................. ................................................. ...211

4.1.7 Internal resources .................................................................. ................................................. ....................................213

4.1.7.1 CDR records .................................................. ................................................. ................................................. ......213

4.1.7.2 Categories of ACS .......................................................... ................................................. ...............................................227

4.1.7.3 Access categories .................................................................. ................................................. ................................................228

4.1.7.4 Routing by access category .............................................................. ................................................. .......231

4.1.7.7 TimersQ.931.............................................. ................................................. ...............................................242

4.1.7.10 Scheduled Routing .......................................................... ................................................. ....................248

4.1.7.14 Voice messages ........................................................ ................................................. ...................................258

4.1.7.17 List of Q.850 recovery reasons .............................................. ................................................. .............261

4.1.8.2 Alert tasks.................................................................... ................................................. ................................................265

4.1.8.3 List of rooms .............................................................. ................................................. ...............................................267

4.1.8.4 Reports ................................................. ................................................. ................................................. ........269

4.1.8.5 Alert Records .................................................................. ................................................. ................................................270

4.1.9 LocalLDAP server ............................................... ................................................. ...............................271

4.1.10 Voice mail ................................................ ................................................. ............................................272

4.1.12.1 Recording options ............................................... ................................................. .........................................293

4.1.13 SettingsTCP/IP ............................................................... ................................................. .........................................303

4.1.13.1 Routing table............................................................... ................................................. ................................304

4.1.13.3 Network interfaces.................................................... ................................................. ....................................306

4.1.14 Network Services ................................................................ ................................................. .........................................310

4.1.14.1 NTP ............................................... ................................................. ................................................. .................310

4.1.14.4 Configuring trap (SNMP trap) .............................................. ................................................. .........................312

4.1.15.1 PING.................................................... ................................................. ................................................. ................318