Page 2
COPYRIGHT This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by copyright. No information contained herein may be copied, translated, transcribed or duplicated for any commercial purposes or disclosed to third parties in any form without the prior written consent of SAMSUNG Electronics Co., Ltd.
FCC REQUIREMENTS Thie equipment, the Ubigate iBG2016, complies with Part 68 of the FCC rules and the requirements adopted by the ATCA. On the top of this equipment is a label that contains, among other information, a product identifier in the format US: A3LIS00BiBG2016.
Page 5
For earlier products, the REN is separately shown on the label. INCIDENCE OF HARM If this equipment, the Ubigate iBG2016, causes harm to the telephone network, the telephone company will notify you in advance that temporary discontinuance of service may be required. But if advance notice isn’t practical, the telephone company will notify the customer as soon as possible.
Page 7
American Society of Composers, Authors and Publishers(ASCAP) or other similar organizations if copyright music is transmitted through the Music on Hold feature. SAMSUNG ELECTRONICS, CO., LTD. hereby disclaims any liability arising out of failure to obtain such a license. DISA WARNING Lines that are used for the Direct Inward System Access feature must have the disconnect supervision options provided by the telephone company.
Page 8
Every wire for communication should be larger than 26 AWG. Double pole/neutral fusing. UNDERWRITERS LABORATORIES The Ubigate iBG2016 system has been tested to comply with safety standards in the United States and Canada. This system is listed with Underwriters Laboratories. The cUL Mark is separately shown on the label.
Page 9
Ubigate iBG2016 Configuration Guide/Ed.00 Warning to service personnel: ‘CAUTION: Double pole/neutral fusing’ Telephone line cord: ‘CAUTION: To reduce the risk of fire, use only No. 26 AWG or larger(e.g., 24 AWG) UL Listed or CSA Certified Telecommunication Line Cord’ Leakage currents due to ringing voltage - Earthing installation instructions: ‘1.A supplementary equipment earthing conductor is to be...
This document provides the command usage of routing applications supported by the Ubigate iBG2016. This manual is for engineers, technicians, and others involved with the planning and operation of the Ubigate iBG2016. Document Content and Organization This manual contains the following chapters: PART I.
Ubigate iBG2016 Configuration Guide TABLE OF CONTENTS GENERAL USER INFORMATION 오류! 책갈피가 정의되어 있지 않습니다. RADIO FREQUENCY INTERFERENCE ..오류! 책갈피가 정의되어 있지 않습니다. FCC REQUIREMENTS ........오류! 책갈피가 정의되어 있지 않습니다. MUSIC ON HOLD WARNING......오류! 책갈피가 정의되어 있지 않습니다. DISA WARNING ..........오류! 책갈피가 정의되어 있지 않습니다.
Page 24
Introduction to Security ....................24 Securing Remote Access Using IPSec VPN..............24 Access Methods......................24 Securely Managing the Ubigate iBG2016 System Example ........24 Joining Two Private Networks Example ............... 24 Joining Two Networks using Multiple IPSec Proposals Example ......... 24 Supporting Remote User Access Example ..............
Page 25
Ubigate iBG2016 Configuration Guide/Ed.00 CHAPTER 3. SIP Gateway Management Introduction to SIP Gateway Features ................. 24 Configuring Basic SIP Gateway................... 24 Configuring Enhanced SIP Gateway Features ..............24 Configuring SIP Security Features................24 Verifying and Troubleshooting SIP Features..............24 CHAPTER 4. H.323 Gateway Management Introduction to H.323 Gateway Features ..............
Page 27
Ubigate iBG2016 Configuration Guide/Ed.00 LIST OF FIGURES PART I Figure 2.1 LAN Port Numbering................24 Figure 2.2 20-port Network Module Port Numbering..........24 Figure 2.3 1-Port WAN Network Module Port Numbering ......... 24 Figure 2.4 4-Port WAN Network Module Port Numbering ......... 24 Figure 2.5 Voice Carrier and Mini Module Ports Numbering ........
Page 28
Figure 5.2 Tunnel Mode Between Two Security Gateways-Single Proposals ... 24 Figure 5.3 Tunnel Mode Between Two Security Gateways-Multiple Proposals..24 PART V Figure 1.1 Ubigate iBG2016 Network Diagram............24 Figure 1.2 Example of Call Manager Intworking Mode Network Configuration ..24 XXVI...
Page 29
Ubigate iBG2016 Configuration Guide/Ed.00 Figure 1.3 Example of Stand-alone mode network configuration ......24 Figure 1.4 Toll Bypass for Voice and Fax services ............ 24 Figure 1.5 Connection to IP Phone, Analog Phone and FAX ........24 Figure 1.6 Management using CLI/GUI/NMS............24 Figure 2.1 Architecture of VoIP Network ..............
Page 30
Figure 8.3 Call Legs from the Perspective of the Terminating Router ....... 24 Figure 8.4 Matching Call Legs to Dial Peers ............. 24 Figure 8.5 Dial Peers from the Perspective of the Originating Ubigate iBG2016 ..24 Figure 8.6 Dial Peers from the Perspective of the Terminating Ubigate iBG2016 ..24 Figure 8.7 Communication Between Dial Peers Sharing the...
Page 31
Ubigate iBG2016 Configuration Guide/Ed.00 LIST OF TABLES PART V Table 1.1 High Availability Cases ................24 Table 3.1 Call Setup and Disconnect ................ 24 Table 3.2 Call via Redirect Server ................24 Table 3.3 Call via Proxy Server ................. 24 Table 3.4 Table Default PSTN cause code to SIP status code mapping ....
PART I. System Configuration Chapter 1. Basic Configuration Chapter 2. Port Numbering Chapter 3. Management Configuration Chapter 4. System Logging Chapter 5. RMON Configuration...
Changing Login Parameters The System Administrator login consists of two components: the account name and the password. The initial login name is always samsung, but you can change this to suit the needs of your facility after logging in. The default administrative password, samsung, should be changed as soon as possible to ensure only authorized access to the system.
The system prompts you to verify and then press Return the new password. Changing Administrator Account This procedure changes the system administrator login name to a user-specific name. Note that the default is samsung. Step Command Description Router# configure terminal...
Ubigate iBG2016 Configuration Guide/Ed.00 Setting Date and Time There are three commands in ‘configure’ mode to support date and time setting. To set the current time for the router in Universal Time Coordinated time, specify the time zone offset ahead(+) or behind(-) the time in Greenwich(England), the number of hours ahead or behind Greenwich time, and the number of minutes ahead or behind the time in Greenwich.
Page 39
Ubigate iBG2016 Configuration Guide/Ed.00 Syntax Help The CLI can complete the spelling of command or parameter keywords. Begin typing the command or parameter then press TAB. At the CLI command prompt type sh: Router# sh Press TAB. The CLI shows:...
Page 41
Ubigate iBG2016 Configuration Guide/Ed.00 If you don’t give a file name after ‘local’, it is save in the default filename, ‘system.cfg’. You also can set the Router system parameters from a configuration file on a network server. This method downloads files via the TFTP protocol, then executes the commands from that file without operator intervention.
Ubigate iBG2016 Configuration Guide CHAPTER 2. Port Numbering This Chapter describes the port number conventions used on the iBG2016. Ports on any Network modules or Mini modules are numbered from right to left starting with port number zero. If there is more than one row of ports on a...
Ubigate iBG2016 Configuration Guide/Ed.00 VCU-A 1/0/0 1/1/1 1/1/0 1/0/1 Figure 2.5 Voice Carrier and Mini Module Ports Numbering Mini Modules Ports Numbering Mini-modules have one, two or four ports. Port numbering is from right to left starting with port number zero: (X=0, 1, 2, or 3)
Configuring Simple Network Management Protocol Ubigate iBG2016 provides two classes of SNMP Management Information Bases(MIBs) to provide you with the ability to manage Ubigate iBG2016 routers. The two MIBs are the Enterprise MIB and the Standard MIB. Enterprise MIBs The Enterprise mibs should be compiled in the following order: 1.
Page 49
Ubigate iBG2016 Configuration Guide/Ed.00 SUBMARINE-DSX-TE3-MIB.mib This MIB manages T3/E3 interfaces. Use this MIB to Be notified when an alarm is generated(dsxT3E3AlarmOnTrap) Be notified when an alarm is turned off(dsxT3E3AlarmOffTrap) SUBMARINE-ENVIRON-MIB.mib This MIB manages the chassis environment such as temperature, fan function.
Page 51
Ubigate iBG2016 Configuration Guide/Ed.00 SUBMARINE-AAA-MIB.mib This MIB defines objects related to manage the Authenticatoin, Authorization, and Accounting method lists. This MIB does not contain any traps SUBMARINE-USERS-MIB.mib This MIB defines objects related to manage the user account and current user lists.
Page 55
Ubigate iBG2016 Configuration Guide/Ed.00 rfc1471.mib Implementation of this group is mandatory for all PPP entities. rfc1473.mib Implementation of this group is mandatory for all PPP implementations that support operating IP over PPP. rfc1215.mib This is really only part of RFC-1215. The other part is built into the Emissary MIB compiler as of Emissary release 4.0.
NetCool Configuring SNMP This section describes how to configure Simple Network Management Protocol on an Ubigate iBG2016. snmp-server community This command sets the SNMP community name and access privileges. This entry is a password string that assigns access privileges to SNMP MIBs.
Ubigate iBG2016 Configuration Guide CHAPTER 4. System Logging Logging System Events The Ubigate iBG2016 supports event logging as well as the industry-standard syslog logging. Event Logging The following commands are useful for configuring event logging on the Ubigate iBG2016. system logging This command accesses next-level commands for configuring consolelogging and syslog event reporting.
Page 60
This command shows system logging information. Syslog Events Ubigate iBG2016 supports logging events to a syslog server. For more information on syslog, see RFC 3164. The following bable shows the different levels of syslog message impact. The first five message levels(Emergency through Warning) have the potential for affecting system performance or normal functionality.
Page 61
Ubigate iBG2016 Configuration Guide/Ed.00 For more information of syslog events, refer to the Ubigate iBG2016 Message Reference Manual. Use the following commands to configure and manage syslog. system logging syslog This command accesses next-level commands for configuring syslog on the Router system.
Ubigate iBG2016 Configuration Guide CHAPTER 5. RMON Configuration Configuring Remote Monitoring Remote Monitoring(RMON) is an Internet standard for monitoring network activity.(See RFC 1757 and RFC 2021.) RMON specifies how various network agents collect and exchange data in an SNMP environment.
Page 65
Ubigate iBG2016 Configuration Guide/Ed.00 To add an RMON events(which can be a log, a trap, or log-trap) enter: Router/configure/rmon# event 1 log To add an RMON events(which can be a log, a trap, or log-trap) with additional information of community for sending traps, event description and owner, enter: Router/configure/rmon# event 2 log community ABC description “event 2”...
DCE or DTE mode: EIA 232C, EIA 449, EIA 530, EIA 530A, V.35, and X.21. A Multi-Protocol Transceiver in Ubigate iBG2016 constains all the necessary drivers and receivers for one port to support the appropriate interface types, levels, and termination for the different modes. Each SmartSerial DB26 leaf-...
Ubigate iBG2016 Configuration Guide/Ed.00 V.35 V.35 is a combination of single-ended and differential synchronous interface. It uses V.35 electrical characteristics for clock and data(differential) and V.28(EIA-232) electrical characteristics for control signals(single-ended). It is typically limited to a maximum throughput of 10Mbps. For the interface, separate clock lines are used for receiving and transmitting data and MRAC- 34 connector is used.
This section describes how to configure a serial interface, V.35. The other serial interfaces such as RS-232, X.21, 449 and 530 are to be configured in the similar way. Configuring V.35 as a DCE The following figure illustrates a connection of Ubigate iBG2016 configured as a DCE. Configuring Step Step...
Page 76
Returns to the ‘Router#’ prompt. 35# end Router# show module configuration Show configured information of serial [slot/port] the [slot/plort] serial interface. Configuring Example The following figure illustrates a connection of Ubigate iBG2016 configured as a DCE. (V.35 DTE) (V.35 DCE) V.35 Router iBG2016 The following example shows the commands used to configure the connection in The figure.
Ubigate iBG2016 Configuration Guide/Ed.00 Bundle Configuration This section describes how to configure a bundle interface. The interface bundle specifies the physical connection to be linked, an encapsulation protocol(Layer 2) and, optionally, Layer 3 parameters. Configuring a HSSI frame relay bundle The following example creates a simple interface bundle utilizing the HSSI interface and Frame Relay(Layer 2) parameters.
Page 79
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring a HSSI PPP Bundle The following example creates a simple interface bundle utilizing the HSSI interface with PPP(Layer 2) parameters. Configuring Step Step Command Purpose Router# configure terminal Goes into the terminal configuration mode. Router/configure# interface bundle Sets a bundle interface.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring HSSI The primary use of HSSI is for WAN interfaces such as T3(45 Mbps), and OC-1 (52 Mbps) of the synchronous digital hierarchy. The HSSI interface can be configured as a DTE or a DCE. Each way to configure HSSI interface is shown in the following.
Page 82
CHAPTER 1. Serial Interfaces Configuring Example The following figure illustrates a connection of Ubigate iBG2016 configured as a HSSI DTE. (HSSI DCE) (HSSI DTE) HSSI Network FR Switdh iBG2016 The following example shows the commands used to configure the connection in the figure.
Page 83
Goes back to the ‘Router#’ prompt. Router# show module Show configured information of the configuration hssi [slot/port] [slot/plort] HSSI interface. Configuring Example The following figure illustrates a connection of Ubigate iBG2016 configured as a DCE. (HSSI DTE) (HSSI DCE) HSSI Router...
Ubigate iBG2016 Configuration Guide CHAPTER 2. WAN Interfaces Ubigate iBG2016 is available with T1, Channelized T3, and Clear Channel DS3 WAN interfaces. Consult the Ubigate iBG2016 Installation Manual for details on WAN interface types, cabling, and pinouts. This document outlines the configuration of module parameters(Layer 1) and, to a lesser degree, the configuration of bundle parameters(Layer 2).
Page 87
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring E1 Module Before configuring E1 module, the system carrier type must be changed to E1 by using ‘system carrier-type’ command in the configuration terminal mode. After setting the system carrier type, the system must be reboot to take effect.
Page 89
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Example The following example shows the commands used to configure the connection in the figure. Router# configure terminal Router/configure# module ct3 2/0 Router/configure/module/ct3 (2/0)# cable_length 1 Router/configure/module/ct3 (2/0)# framing c_bit Router/configure/module/ct3 (2/0)# end Router# show module configuration ct3 2/0 Configuring T1’s within CT3...
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring CT3 bundle Configuration of an interface bundle is required for WAN interfaces. Multiple physical interfaces may be linked to a single interface bundle; multi- link protocols, including MLPPP and Multilink Frame Relay, make use of NxT1 interfaces to create single logical interfaces.
Ubigate iBG2016 Configuration Guide CHAPTER 3. PPP, MLPPP, and HDLC Ubigate iBG2016 provides Point-to-point protocol over WAN interfaces feature. The Point-to-Point Protocol(PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. These links provide full- duplex simultaneous bi-directional operation and are assumed to deliver packets in order.
Page 94
CHAPTER 3. PPP, MLPPP, and HDLC PPP is comprised of 3 main components: Framing, LCP, NCP. A method for encapsulating multi-protocol datagrams. In Ubigate iBG2016, PPP is used on the links that use HDLC-like framing(on the WAN side over T1/T3 physical interfaces). The details of the encapsulations can be found in RFC1662 and RFC2516.
Ubigate iBG2016 Configuration Guide/Ed.00 Protocol Configuration Ubigate iBG2016 Routers may be configured for a variety of Layer 2 protocols. This document outlines HDLC, PPP, and Multilink PPP(MLPPP) configurations. Ubigate iBG2016 Router systems are often used at POPs(point of presents) to aggregate data for WAN transmission.
CHAPTER 3. PPP, MLPPP, and HDLC MLPPP Configuration This section shows how to confiure the router at site 1 with MLPPP. Configuring Ubigate iBG2016 at Site 1 Configuring Step Step Command Purpose Router# configure terminal Goes into the terminal configuration mode.
Ubigate iBG2016 Configuration Guide/Ed.00 PPP and MLPPP Configuration This section shows how to configure interfaces with PPP and MLPPP. Configuring MLPPP for Ubigate iBG2016 at Main Site Configuring Step Step Command Purpose Router# configure terminal Goes into the terminal configuration mode.
Ubigate iBG2016 Configuration Guide CHAPTER 4. FR and MFR Layer Two Configurations The following figure outlines a Multilink Frame Relay(MFR) configuration with three sites. PVC 16 connects Site 1 to Site 3, while PVC 31 connects Site 2 to Site 3.
Page 105
Ubigate iBG2016 Configuration Guide/Ed.00 Router B at Site 2 serves as the Frame Relay termination point, connecting the Site 2 IP network to Router A. This MFR bundle utilizes 2 T1 links for an approximate 3 Mbps bandwidth. Since it is the Frame Relay terminating point and is defined as a DTE frame relay interface, an IP address is assigned to the WAN bundle.
Ubigate iBG2016 Configuration Guide CHAPTER 1. Layer-2 Switching Layer 2 LAN Switching and Bridging Local Area Network(LAN) is a data communications network connecting terminals, computers and printers within a building or other geographically limited areas. These devices could be connected through wired cables or wireless links.
Ubigate iBG2016 Configuration Guide/Ed.00 Protocol Configuration This section shows a configuration example for Multiple Spanning Tree Protocol(MSTP) with VLAN. Bridge Configurations This example gives a simple multi-bridge topology and how to configure it. Bridge a Bridge b Bridge c Bridge d Configuring MSTP The following steps show general configuration steps to configure MSTP.
The router is the physical path between the two clients and the RADIUS server. The Ubigate iBG2016 relays information to the Server and then back to each client.
Ubigate iBG2016 Configuration Guide/Ed.00 LACP Configuration LACP is based on the 802.3ad IEEE specification. It allows bundling of several physical interfaces to form a single logical channel providing enhanced performance and redundancy. The aggregated interface is viewed as a single link to each router. Spanning tree views it as one interface.
Ubigate iBG2016 Configuration Guide/Ed.00 eth2/1 eth0/1 Multicast eth1/1 Router Multicast Host A Figure 1.4 IGMP Snooping Example As a result of this configuration, the queries received on the router by Ethernet 1/1 will not be forwarded to Ethernet 0/1 and Ethernet 2/1. The router itself will reply back with Membership report message.
Page 125
Ubigate iBG2016 Configuration Guide/Ed.00 show ip igmp snooping last-member-query-interval shows the last-member- query-interval processing for IGMP hosts. show ip igmp snooping max-response-time shows the maximum response time setting. show ip igmp snooping mrouter shows the multicast router interfaces. show ip igmp snooping other-querier-interval shows the querier interval setting.
CHAPTER 2. DHCP Relay Ubigate iBG2016 Modular Router’s DHCP relay feature eliminates the need for a DHCP server on every LAN, because DHCP requests can be relayed to a single remote DHCP server. The relay agent forwards traffic between clients and servers when they are located on different subnets.
Ubigate iBG2016 Configuration Guide/Ed.00 Using DHCP Relay with NAT When NAT is enabled, the DHCP server may discard packets because the giaddr does not match the source of the packet. Additionally, it may not know how to route the packet back to the client. See Figure 11.4. The solution is that the gateway address(giaddr) field needs to have IP address 192.168.20.1...
Compared to Static Routing, Dynamic Routing, on the other hand, is typically used when static routing entries should be unwieldy in a large network, where the administrator would have to operate complex manual tasks. This chapter describes how to configure static routing in the Ubigate iBG2016 Router. Configuring Static Routes Static routes are specified by adding and deleting route entries to and from the route table.
Ubigate iBG2016 Configuration Guide CHAPTER 4. Routing Information Protocol(RIP) is a classical distance-vector routing protocol. It is simple to implement and performs good for small networks. Distance Vector Routing requires that each node maintain the distance from itself to each possible destination. The distances are computed using the information in neighbor’s distance vectors.
Configuring RIP This section describes the steps to configure RIP and show a simple example. R1 and R2 are two Ubigate iBG2016 routers connecting to a common network 10.10.11.0/24. They are also connected to network 10.10.10.0/24 and 10.10.12.0/24, respectively.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring RIPv2 authentication The Ubigate iBG2016 provides RIPv2 authentication and the choice of a single key or multiple keys for the authentication. This section describes a simple example to configure RIPv2 authentication with a single key.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring RIP on a bundle interface Configuring Step Step Command Purpose Router# configure terminal Enters the terminal configuration mode. Router/configure# router rip Enters the RIP setup mode. Router/configure/router rip# network Designates a bundle [IP address]/[number of bit masks] or interface to run RIP on.
Page 141
Ubigate iBG2016 Configuration Guide CHAPTER 5. OSPF The Open Shortest Path First(OSPF) protocol is an interior gateway protocol(IGP) that routes packets within a single autonomous system(AS). OSPF uses link-state information to make routing decisions, making route calculations using the shortest path first(SPF) algorithm(also referred to as the Dijkstra algorithm).
Page 143
Ubigate iBG2016 Configuration Guide/Ed.00 The following example shows the commands used to configure the host name in the figure. Router# configure terminal Router/configure# hostname iBG2016 iBG2016/configure# Configuring Local Network Interface Configuring Step Step Command Purpose iBG2016/configure# interface ethernet Enters the ethernet interface [slot/port] configuration mode.
Page 147
Ubigate iBG2016 Configuration Guide CHAPTER 6. The Border Gateway Protocol(BGP) is an exterior gateway protocol(EGP) that is used to exchange routing information among routers in different autonomous systems(ASs). BGP routing information includes the complete route to each destination. BGP uses the routing information to maintain a database of network reachability information, which it exchanges with other BGP systems.
Protocol Features The following BGP features such as aggregation, route reflection, AS confederation, and etc will be supported on the Ubigate iBG2016 system. Aggregation is the process of combining the characteristics of several different routes in such a way that a single route can be advertised. Aggregation reduces the amount of information a BGP speaker stores and exchanges with other speakers.
Page 151
Ubigate iBG2016 Configuration Guide/Ed.00 Prefix lists are yet another way of implementing BGP policy. A Prefix List enables filtering of route advertisements based on IP prefixes. This is a group of BGP neighbors that share update policies. Instead of defining the same policies for several individual peers, a peer group is defined and policies are assigned to the group.
[IP address] remote-as ip address and antonomous [Autonomous Number] number. Configuring Example In the figure, R1 and R2 are two Ubigate iBG2016 Routers belonging to the same AS(autonomous system) with the ID of 200. AS : 200 10.10.10.1 Network 10.10.10.2...
Page 153
R2# configure terminal R2/configure# router bgp 200 R2/configure/bgp 200# neighbor 10.10.10.1 remote-as 200 Configuring BGP in the different AS Configuring Example The following figure shows two Ubigate iBG2016 Routers in the different AS. AS : 200 AS : 300 10.10.10.1 10.10.10.2 The following example shows the commands used to configure the BGP for R1 in the figure.
Applies a route-map to routes for neighbor [IP address] route-map incoming advertisements. [prefix name] in Configuring Example In the figure, R1 and R2 are the Ubigate iBG2016 Routers in the different antonomous systems. AS : 200 AS : 300 1.1.1.0/24 192.168.10.1...
Page 155
Ubigate iBG2016 Configuration Guide/Ed.00 R2 is connected to two different routers and their subnets are The following example shows the commands used to configure the BGP using Route-Map for R1. R1# configure terminal R1/configure# ip prefix-list inpf seq 5 deny 1.1.1.0/24 ge...
There are two modes of PIM protocol - Dense mode(DM) and Sparse mode (SM). Ubigate iBG2016 supports SM but not DM. PIM-DM floods multicast traffic throughout the network initially and then generates prune messages as required.
Page 159
Ubigate iBG2016 Configuration Guide/Ed.00 Reverse Path Forwarding Reverse Path Forwarding(RPF) is a concept of an optimized form of flooding, where the router accepts a packet from SourceA through Interface IF1 only if IF1 is the interface the router would use in order to reach SourceA.
Page 161
Ubigate iBG2016 Configuration Guide/Ed.00 (S,G,rpt) Entries: 0 (*, 224.0.1.3) RP: 10.10.1.5 RPF nbr: 172.16.1.2 RPF idx: ethernet 2/1 Upstream State: JOINED Local ........ Joined j....... Asserted ........ Outgoing o....... At Router_E, Ethernet 2/1 is the incoming interface of the(*, G) entry, and Ethernet 1/1 is on the outgoing interface list of the(*, G) entry.
Page 163
Ubigate iBG2016 Configuration Guide/Ed.00 PIM Group-to-RP Mappings Use the show ip pim sparse-mode rp mapping command to display the group- to-RP mapping details. The output displays information about RP candidates. There are two RP candidates for the group range 224.0.0.0/4. RP Candidate 10.10.1.5 has a default priority of 192, whereas, RP Candidate...
Page 165
Ubigate iBG2016 Configuration Guide/Ed.00 To set the RP static IP address to 10.10.1.1, enter: Router/configure#ip pim rp-address 10.10.1.1 To set the flag for the RP to switch to the SPT for(S, G) upon receipt of the first Register message(default: on). To turn on this feature, enter:...
Page 167
Ubigate iBG2016 Configuration Guide/Ed.00 ip pim ignore-rp-set-priority − ip pim rp-register-kat − ip pim register-suppression − ip pim cisco-register-checksum group-list − clear ip mroute clear ip pim sparse-mode bsr rp-set all debug pim all debug pim sparse-mode all debug pim sparse-mode events...
Following is a brief description of terms and concepts used to describe the DVMRP protocol. DRIB Ubigate iBG2016 DVMRP is a separate daemon serviced by the NSM daemon. It maintains the DVMRP Routing Information Base(DRIB). The DRIB contains the table of routes for multicast sources learned through DVMRP route exchanges.
Ubigate iBG2016 Configuration Guide/Ed.00 Neighbor Table The Neighbor table is a list of detected DVMRP neighbors on an interface. Neighbors announce themselves using the Probe message. Route Report Arrays of Lists Because route reporting is done by grouping together all routes that belong to the same mask, a Route Report Array of Lists(AOL) is used to expedite general route reporting.
Ubigate iBG2016 Configuration Guide/Ed.00 Interface Information The show ip dvmrp interface command displays the interface information for Router_C. For example: Router_C# show ip dvmrp interface Neighbor Information The show ip dvmrp neighbor command displays the neighbor information for Router_C. For example:...
Ubigate iBG2016 Configuration Guide/Ed.00 IGMP Commands The IGMP commands supported in Ubigate iBG2016 OS are: ip igmp access-group ip igmp immediate-leave ip igmp last-member-query-count ip igmp last-member-query-interval ip igmp querier-timeout ip igmp query-interval ip igmp query-max-response-time ip igmp version debug igmp all...
Page 175
Ubigate iBG2016 Configuration Guide/Ed.00 Example 5 The following example configures Ethernet(0/1) with the last-member- querycount to be 3. Router/configure/interface/ethernet (0/1)# ip igmp last- memberquery-count 3 Example 6 The following example configures Ethernet(0/1) with the last-member- query¬interval to be 2000 seconds.
Ubigate iBG2016 Configuration Guide CHAPTER 8. VRRP In statically routed networks, when a router fails, all the network devices connected to this router are unable to have traffic routed. Typically this means these devices cannot reach the Internet or other networks.
2 automatically takes over routing traffic between the subnets labeled Host A, B, and C, and the Gateway Router providing Internet connectivity. To configure VRRP in this environment, you need to configure Ubigate iBG2016 1 as the Master virtual router, and Ubigate iBG2016 2 as the backup virtual router. Host A...
Page 179
2 Router/configure/interface/ethernet(0/1)/vrrp 10# enable Verifying and Troubleshooting Ubigate iBG2016 provides commands to verify VRRP status and configuration. To display detailed status of all VRRP groups on the router. Router# show vrrp detailed To display a brief status of all VRRP groups on the router.
Ubigate iBG2016 Configuration Guide CHAPTER 9. MPLS MPLS Overview Multiple Protocol Label Switching(MPLS) is an IETF standards-based approach built on the efforts of the various proprietary multilayer switching solutions. In MPLS, data transmission occurs on label-switched paths(LSPs). Forwarding Equivalent Class(FEC) determines traffic mapping into MPLS LSPs at the ingress point of the MPLS network.
Ubigate iBG2016 Configuration Guide/Ed.00 MPLS Forwarding MPLS forwarding consists of 3 main operations: Mapping of data packets into LSPs based on destination FEC bypushing MPLS labels. For Martini case, a VC label followed by a tunnel label will be pushed.
Class(FEC) corresponding to that LSP. LDP assigns labels to every destination address and destination prefix provided by Ubigate iBG2016. The LDP interface to the MPLS forwarder adds labels to and deletes labels from the forwarding tables. Running LDP on a system, requires the following tasks: Enabling label-switching on the interface on NSM.
Ubigate iBG2016 Configuration Guide/Ed.00 Enabling label-switching-minimal configuration To establish a trunk on a system: Enable label-switching and RSVP-TE on all participating interfaces. Configure a trunk on the ingress router to use the best available IGP path. In this example, the Label Switched Path(LSP) is configured using minimal configuration and is setup using the best IP nexthop available.
Ubigate iBG2016 Configuration Guide/Ed.00 Establishing a Trunk-CSPF disabled In the Ubigate iBG2016 implementation, Constrained Shortest Path First(CSPF) is enabled by default.Typically, CSPF is disabled when all the participating nodes do not support the required traffic engineering extensions and configure LSPs manually to use an explicit path. In this case, LSP is established only along the path specified by the operator.
Explicit Route Object(ERO). Each router along the path sends a Path message only to the nexthop specified in the ERO. In the Ubigate iBG2016 implementation, CSPF is enabled by default and if no-cspf is not specified, the trunk is CSPF enabled automatically.
Ubigate iBG2016 Configuration Guide/Ed.00 Establishing a Trunk-Using Explicitly Defined Path The Explicit Route hops can be configured explicitly in the trunk configuration. In this case, the RSVP daemon uses the configured hops as ERO. It sets up the LSP using specified hops only. For a detailed description of the path parameters refer to the RSVP-TE Command Reference.
Ubigate iBG2016 Configuration Guide CHAPTER 10. iBG2016 Quality of Service The iBG2016 supports software-based QoS in the operating system. It also supports hardware-based QoS which is enforced in the chipset. Each type of QoS support has its own configuration capability in the CLI.
Ubigate iBG2016 Configuration Guide/Ed.00 Peak Rate Every traffic class can be configured with a peak rate parameter, which is the bandwidth that can be offered to that class if unused bandwidth is available from other classes. This provides for very efficient bandwidth utilization.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuration The following is the configuration for the topology shown in Figure 19.2. Create bundle VLANtest Router# conf terminal Router/configure# interface bundle VLANtest Router/configure/interface/bundle VLANtest# link t3 1/23 Router/configure/interface/bundle VLANtest# encap ppp Router/configure/interface/bundle VLANtest# ip addr 200.1.1.1255.255.255.252...
Ubigate iBG2016 Configuration Guide/Ed.00 Traffic Policing versus Traffic Shaping Policing controls the traffic by dropping packets or marking down their priority when the configured rate is exceeded. Shaping controls the traffic by delaying packets using a queuing mechanism when they arrive faster than the configured rate.
Ubigate iBG2016 Configuration Guide/Ed.00 Verifying Policing Status and Configuration The two CLI display commands below can be used to check the policing configuration and status for a class and for an interface. show qos bundle bundle_name shows the policing status on the interface and the bandwidth each class is getting along with its configured policing rate.
Ubigate iBG2016 Configuration Guide/Ed.00 Multi-Field Classification The Multi-Field(MF) classifier is an important component of QoS. Its purpose is to help define flows for which appropriate service parameters can be configured. Flow classification is the first step in the QoS process.
Page 219
Ubigate iBG2016 Configuration Guide/Ed.00 The user configures MF classification for a specific interface and for a specific traffic direction. He constructs the class hierarchy by specifying the parent- class for each new class he wants to create. In order to create a new class, the user must specify the class-name of the new class, the class name of the parent-class and a match rule.
Page 221
Ubigate iBG2016 Configuration Guide/Ed.00 The ether-type value of 0x8847 is added to the hash table and a pointer to class ‘mpls’ is stored in that entry. For any classification type, it is possible for the match rule to have a range of values or multiple, non-contiguous values.
Page 223
Ubigate iBG2016 Configuration Guide/Ed.00 Some clarification on acronyms will be helpful before going into the design discussion about policing. Committed Information Rate Committed Burst Size Committed Burst Time Excess Burst Size Peak Information Rate Peak Burst Size Peak Burst Time Burst Size Burst Interval.
Ubigate iBG2016 Configuration Guide/Ed.00 The trTCM (Two Rate Three Color Marker) The trTCM algorithm uses two rates CIR and PIR, and two burst sizes, CBS and PBS. The trTCM is typically implemented using two token buckets, Tc of size CBS, and Tp of size PBS. A packet is marked red if it exceeds PBS, yellow if it exceeds CBS but not PBS, otherwise it is green.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring trTCM To enable policing using trTCM, CIR, CBS, PIR and PBS need to be configured. CIR and PIR configuration will be mandatory and CBS and PBS parameters will be optional. CBS will have a default value equal to ‘CIR’...
Page 231
Ubigate iBG2016 Configuration Guide/Ed.00 For understanding of CBQ operation, let us first consider all classes to be of equal priority. The scheduler runs every 5 msec to service the queues on each interface.(Each leaf class is associated with a queue). In every scheduling interval, the scheduler makes two passes on the classes of each interface.
Ubigate iBG2016 Configuration Guide/Ed.00 Buffer Management for Class Queues It is not possible for a class to guarantee bandwidth if it doesn’t have enough buffers for its queue, because the packets can be dropped even before they have a chance to be scheduled. Therefore it is essential to have a good buffer management scheme along with a good scheduling algorithm.
Ubigate iBG2016 Configuration Guide/Ed.00 Buffer Reservation for Interfaces When a wan interface is created, a certain amount of queue buffers will be reserved for it’s transmitting queue from the global buffer pool. Buffer reservation is only done for wan interfaces and not GE interfaces because we expect congestion and hence queue build-ups only on wan interfaces.
Page 237
Ubigate iBG2016 Configuration Guide/Ed.00 The minimum # of buffers required for one class = bbr/100 = 20 buffers With 20 classes on the bundle,(20 * 20) = 400 buffers would be required for the bundle. With 14 bundles on a t3 interface, the total buffers requirement...
Page 239
Ubigate iBG2016 Configuration Guide/Ed.00 A single class by itself should not be allowed to borrow all of the available common pool buffers. So we need to enforce a maximum limit on the buffer consumption of each class. Since we have allocated(10 * BCR average_...
Page 241
Ubigate iBG2016 Configuration Guide/Ed.00 Average Queue Size Calculation for Interface Queues The average queue size computation for interface is done for every packet sent on the interface. Before deciding whether packet needs to be dropped or not, the average queue size is calculated using the following formula and by reading the current driver queue size and current average queue size.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring RED parameters This section discusses which RED parameters are configurable and how are their default values set. It also explains the effect of changing these parameter values and guidelines about how to set their values.
Page 245
Ubigate iBG2016 Configuration Guide/Ed.00 The average internet packet size is probably between 200-300 bytes, for which the buffering would be up to twice the amount mentioned above. The minimum permissible value for minth is L, where L corresponds to Ts msec of buffering(for 200 byte packets) at CR Kbps or L = 3, whichever is higher.
Ubigate iBG2016 Configuration Guide/Ed.00 L2 Bridge Based CoS Marking The first stage that assigns CoS attributes is the Bridge processing stage. To configure the bridge port TC assignment, enter: Router/configure/interface/ethernet (3/0)/qos# [no] override-outq <queue-id(1..8)> Using the no form will switch off TC override. When TC override is ‘off’, the TC gets reassigned based on the UP of the packet in the next stage.
Ubigate iBG2016 Configuration Guide/Ed.00 InLIF Based CoS Marking The inLIF is a logical context assigned to a user port. InLIF-based CoS marking allows you to override the marking done at the bridge stage and assign CoS based purely on the ingress interface.
Ubigate iBG2016 Configuration Guide/Ed.00 Verifying the Configuration To verify the configuration, enter: Router/configure/qos# show qos global-config Router/configure/qos/policy-map map1# show qos policer policy-name map1 policy-class class1 Egress Queuing, Scheduling and Shaping Two queuing disciplines are supported namely Strict Priority Queuing and Weighted Round Robin.
Ubigate iBG2016 Configuration Guide CHAPTER 11. VLAN forwarding with QoS Overview Untagged Customer LANs Channelized Ethernet Switch T3 Router Channelized T3 Gigabit Ethernet Ethernet Switch Internet Telco Tagged VLAN Trunk Multilink T1 Router Multi-Tenant Bullding Figure 11.1 VLAN Forwarding: Multi-Tenant Internet Access The example above shows each multi-tenant customer represented as a separate VLAN on the Ethernet switch.
Ubigate iBG2016 Configuration Guide/Ed.00 Virtual LAN Domain The iBG2016 supports VLAN-based data forwarding. Essentially, this feature forwards the packets from one network to another based on the VLAN identifier(rather than routing) contained in the VLAN header, as defined by IEEE 802.1q. The VLAN packets are generally termed as tagged packets referring to the VLAN encapsulation of the Ethernet packets.
Page 271
PART IV. Security Chapter 1. Authentication Authorization and Accounting Chapter 2. Packet Filtering Chapter 3. Firewall and NAT Chapter 4. Chapter 5. IPSEC...
Page 273
Ubigate iBG2016 Configuration Guide CHAPTER 1. Authentication Authorization Accounting The combination of accounting controls, authorization requirements, and authentication checks(AAA) is a framework for configuring security functions across the network in a consistent fashion. Each component of AAA can be implemented separately.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Authentication The Ubigate system is configured to authenticate users on a port basis. For example, if you want to configure a port of Ethernet 2/3 with a RADIUS authentication method, you may follow the example shown below.
Page 277
Ubigate iBG2016 Configuration Guide/Ed.00 Verifying TACACS Configuration To confirm the access method, enter: Router/configure/aaa# show aaa authentication login List Name Methods Order ------------------------------------------- default NOT CONFIGURED list1 tacacs local none To confirm the protocols list, enter: Router/configure/aaa# show aaa authentication protocols...
An example would be a filter that prohibits external users from establishing Telnet sessions to the Ubigate iBG2016, and allows only specific internal users Telnet access to the system. At the end of every rule list is an implied ‘deny all traffic’ statement.
200.1.1.1) to an ISP, with Ethernet 0/1(IP address 222.199.19.3) connected to the internal network. The network administrator wants to completely block Telnet access to the Ubigate iBG2016 from all external networks as well as from all internal networks except 222.199.19.0/28. All other TCP/IP traffic, such as FTP, Ping, and HTTP, is to flow unrestricted through the Ubigate iBG2016.
Ubigate iBG2016 Configuration Guide CHAPTER 3. Firewall NAT Overview Security module in Ubigate iBG2016 consists of various components such as Stateful inspection firewall, IPSec VPN, Public Key Infrastructure and Access Control List(ACL). This chapter introduces Ubigate iBG2016’s firewall and its typical configuration.
Ubigate iBG2016 Configuration Guide/Ed.00 Many-to-one reverse NAT(NAT record attached to in bound policy) One-to-one reverse NAT(NAT record attached to in bound policy) Many-to-many regular NAT(NAT record attached to out bound Policy) Multiple policies can share single NAT address, provided NAT address is of type many to one only.
Consider a PC on the LAN sending a packet destined for some.server.com. The source IP address and port are in the packet together with the destination IP address and port. When the packet arrives at the Ubigate iBG2016 it will be de-encapsulated, modified, and re-encapsulated.
Page 289
Ubigate iBG2016 Configuration Guide/Ed.00 The Ubigate iBG2016 also adds an entry into a table it keeps, which maps the internal address and source port number that the PC generated against the port number it allocated to this session. Therefore, when some.server.com sends a reply packet to the PC, the Ubigate iBG2016 can quickly determine how it needs to re-write the packet before transmitting it back on to the LAN.
Figure 3.5 Mapping Multiple NAT Addresses to One Public IP Address There are two methods to configure Port Address Translation(PAT) on the Ubigate iBG2016 gateway. In the first method, specify the IP address to the nat-ip parameter in the policy command. In the second method, create a pool of type PAT and then attach it to the policy.
Ubigate iBG2016 Configuration Guide/Ed.00 Static NAT (one to one) 10.1.1.1 OPAL 10.1.1.2 Internet 50.1.1.1.50.1.1.3 10.1.1.3 Figure 3.6 Static NAT In static(one-to-one) NAT type, for each IP address in the corporate network, one NAT IP address will be used. For example, for the three IP addresses from 10.1.1.1 to 10.1.1.3, there is a set of three NAT IP address from...
Page 294
Static NAT also requires a public address from the upstream service provider. Individual PCs within a LAN are assigned RFC 1918 reserved IP addresses to enable access to other PCs within the LAN. The Ubigate iBG2016 is configured with static mapping, which maps the internal RFC 1918 IP addresses for each PC to the appropriate public IP address.
Ubigate iBG2016 Configuration Guide CHAPTER 4. Generic Routing Encapsulation(GRE) is a standards-based(RFC1701, RFC2784) tunneling protocol that can encapsulate a wide variety of protocol packet types inside IP tunnels, creating a virtual point-to-point link between routers at remote points over an IP network. A tunnel is a logical interface that provides a way to encapsulate passenger packets inside a transport protocol.
Figure 4.1 Simple GRE configuration Configuring Site to Site Tunnel To configure GRE in a site to site tunnel configuration: Configure the interface. Ubigate iBG2016# configure terminal Router/configure# interface bundle wan1 Router/configure/interface/bundle wan1# link t1 0/2/0 Router/configure/interface/bundle wan1# encapsulation ppp Router/configure/interface/bundle wan1# ip address 192.168.94.220...
Page 301
Ubigate iBG2016 Configuration Guide/Ed.00 Configure the IP routes. Router/configure# ip route 0.0.0.0 0.0.0.0 192.168.94.254 Router/configure# ip route 40.1.1.0 255.255.255.0 t0 The peer of a local WAN interface cannot be used as a tunnel destination. Verify that the tunnel is up and running.(If it is not, check the Gateway and Source Address fields.)
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring GRE Site to Site with IPSec This example extends the first example by adding encryption to the tunnel. Prepare the WAN link: Router# configure terminal Router/configure# interface bundle wan1 Router/configure/interface/bundle wan1# link t1 0/2/0 Router/configure/interface/bundle wan1# encapsulation ppp Router/configure/interface/bundle wan1# ip address 192.168.94.220 255.255.255.0...
This example extends the previous IPSec configuration example by enabling Open Shortest Path First(OSPF) protocol which provides redundant paths for the tunnel. To enable OSPF, add to the Ubigate iBG2016 configuration above: Router# configure terminal Router/configure# router-id 2.2.2.2 Router/configure# router ospf Router/configure/router/ospf# network 103.1.1.0/24 area 0...
Ubigate iBG2016 Configuration Guide CHAPTER 5. IPSEC Need to develop CLNS VPNs and Secure Packet Exchange topics-new material Introduction to Security SNOS introduces a wide range of robust industry-standard security features including: Virtual Private Networking IPSec encryption and tunneling Generalized Router Encryption...
Ubigate iBG2016 supports two types of IPSec remote access using VPNs. Remote Access: User Group One of the methods to achieve IPSec remote access in Ubigate iBG2016 is the user group method. In this method, the administrator creates an IKE policy for a logical group of users such as a department in an organization.
Page 307
Ubigate iBG2016 Configuration Guide/Ed.00 Remote Access: Mode Configuration The other method to achieve IPSec remote access in Ubigate iBG2016 is the mode configuration method. This method makes the VPN client an extension of the LAN being accessed by the VPN client. The remote client appears as a network accessing some resource behind the VPN server.
CHAPTER 5. IPSEC Securely Managing the Ubigate iBG2016 System Example This example demonstrates how to manage a router through an IP security tunnel. Steps are presented for configuring the Router and NW2 routers to assist any host on the LAN side of Networks-2 to manage the Router router through the IP security tunnel.
Page 309
Ubigate iBG2016 Configuration Guide/Ed.00 Display the crypto interfaces. Router# show crypto interfaces Interface Network Name Type --------- ------- ethernet 0/1 trusted wan1 untrusted Add the route to the peer LAN. Router/configure# ip route 10.0.2.0 255.255.255.0 wan1 Configure IKE to the peer gateway.
Page 311
Ubigate iBG2016 Configuration Guide/Ed.00 Display the policies. Router# show crypto ipsec policy all Policy Peer Match Proto Transform ------ ---- ----- ----- --------- NW2 172.16.0.2 S 172.16.0.1/32/any Any P1 esp-aes-sha1-tunl D 10.0.2.0/24/any INNW2 172.16.0.2 S 10.0.2.0/24/any Any P1 esp-aes-sha1-tunl D 172.16.0.1/32/any Display IPSec policies in detail.
Page 313
Ubigate iBG2016 Configuration Guide/Ed.00 1000 in any any snmp PERMIT SE 1002 in any any telnet PERMIT SE 1003 in any any any any icmp PERMIT SE 1024 out any any any any any PERMIT SE Display firewall policies in the internet map in detail.
Page 315
Ubigate iBG2016 Configuration Guide/Ed.00 Router# show crypto ike sa all detail Crypto Policy name: NW2 Remote ident 172.16.0.2 Peer Address is 172.16.0.2 Transform: 3des, sha1, pre-shared-key DH Group: group1 Bytes Processed 2020 State is SA_MATURE Mode is Main Remaining Time in Sec: 86084...
Page 319
Ubigate iBG2016 Configuration Guide/Ed.00 Display IPSec policies. Router# show crypto ipsec policy all Policy Peer Match Proto Transform ------ ---- ----- ----- --------- NW2 172.16.0.2 S 10.0.1.0/24/any Any P1 esp-aes-sha1-tunl D 10.0.2.0/24/any INNW2 172.16.0.2 S 10.0.2.0/24/any Any P1 esp-aes-sha1-tunl D 10.0.1.0/24/any...
Page 321
Ubigate iBG2016 Configuration Guide/Ed.00 Bytes In 0, Bytes Out 0 Policy with Priority 1024 is enabled, Direction is outbound Action permit, Traffic is self Logging is disable Source Address is any, Dest Address is any Source Port is any, Dest Port is any, any...
Page 323
Ubigate iBG2016 Configuration Guide/Ed.00 Repeat steps 1-16 with suitable modifications on NW2 prior to passing traffic. Test the IPSec tunnel between Router and NW2 by passing traffic from the 10.0.1.0 to the 10.0.2.0 network. After transit traffic is passed through the tunnel, display the IKE and IPSec SA tables.
Ubigate iBG2016 Configuration Guide/Ed.00 Joining Two Networks using Multiple IPSec Proposals Example The following example demonstrates how a security gateway can use multiple IPSec(phase2) proposals to form an IP security tunnel to join two private networks: 10.0.1.0/24 and 10.0.2.0/24. IKE Proposal offered by both Router and NW2:...
Page 327
Ubigate iBG2016 Configuration Guide/Ed.00 Display the IKE policies. Router# show crypto ike policy all Policy Peer Mode Transform NW2 172.16.0.2 Main P1 pre-g1-3des-sha1 Display the IKE policies in detail. Router# show crypto ike policy all detail Policy name NW2, Local addr 172.16.0.1, Peer addr 172.16.0.2...
Page 329
Ubigate iBG2016 Configuration Guide/Ed.00 Policy name INNW2 is enabled, Direction is inbound Peer Address is 172.16.0.2, Action is Apply Key Management is Automatic PFS Group is disabled Match Address: Protocol is Any Source ip address(ip/mask/port):(10.0.2.0/255.255.255.0/any) Destination ip address(ip/mask/port):(10.0.1.0/255.255.255.0/any) Proposal of priority 1...
Page 333
Ubigate iBG2016 Configuration Guide/Ed.00 After traffic is passed through the tunnel, display the IKE and IPSec SA tables. Router# show crypto ike sa all Policy Peer State Bytes Transform -------- ---------- -------- ------ ---------------- NW2 172.16.0.2 SA_MATURE 1796 pre-g1-3des-sha1 Router# show crypto ike sa all detail Crypto Policy name: NW2 Remote ident 172.16.0.2...
Page 335
Ubigate iBG2016 Configuration Guide/Ed.00 Display the crypto interfaces. Networks1# show crypto interfaces Interface Network Name Type ethernet 0/1 trusted wan1 untrusted Add the route to the peer LAN. Networks2Router/configure# ip route 10.0.1.0 24 wan1 Configure IKE to the peer gateway.
Ubigate iBG2016 Configuration Guide/Ed.00 Supporting Remote User Access Example The following example demonstrates how to configure a router to be an IPSec VPN server using user group method with extended authentication(XAUTH) for remote VPN clients. The client could be any standard IPSec VPN client.
Page 339
Ubigate iBG2016 Configuration Guide/Ed.00 Display dynamic IKE policies. Router# show crypto dynamic ike policy all Policy Remote-id Mode Transform Address-Pool ------ --------- ---- --------- ------------ sales U david@tabc... Aggressive P1 pre-g1-3des-sha1 Display dynamic IKE policies in detail. Router# show crypto dynamic ike policy all detail...
Page 343
Ubigate iBG2016 Configuration Guide/Ed.00 Display firewall policies in the corp ma. Router# show firewall policy corp Advanced: S-Self Traffic, F-Ftp-Filter, H-Http-Filter, R-Rpc-Filter, N-Nat-Ip/Nat-Pool, L-Logging, E-Policy Enabled, M-Smtp-Filter Pri Dir Source Addr Destination Addr Sport Dport Proto Action Advanced 1000 in any 10.0.1.0/24...
Page 345
Ubigate iBG2016 Configuration Guide/Ed.00 Router# show crypto ike sa all detail Crypto Policy name: sales Remote ident david@abc-corp.com Peer Address is 192.168.107.105 Transform: 3des, sha1, pre-shared-key DH Group: group1 Bytes Processed 1772 State is SA_MATURE Mode is Aggressive Life Time in Sec is unlimited, Life Time in Bytes is...
Page 349
Ubigate iBG2016 Configuration Guide/Ed.00 Display dynamic IKE policies in detail. Router# show crypto dynamic ike policy all detail Policy name sales, Modeconfig group Aggressive mode, Response Only, PFS is not enabled, Shared Key is ***** Local addr: 192.168.55.52, Local ident 192.168.55.52(ip- address) Remote idents are david@abc-corp.com(email-id), mike@abc-...
Page 353
Ubigate iBG2016 Configuration Guide/Ed.00 Display firewall policies in the corp map in detail. Router# show firewall policy corp detail Policy with Priority 1000 is enabled, Direction is inbound Action permit, Traffic is transit Logging is disable Source Address is 20.1.1.100-20.1.1.150, Dest Address is 10.0.1.0/24...
Page 355
Ubigate iBG2016 Configuration Guide/Ed.00 Router# Router# show crypto ipsec sa all detail Crypto Policy name: INsales Protocol is Any Local ident(ip/mask/port):(20.1.1.1/255.255.255.255/any) Remote ident(ip/mask/port):(10.0.1.0/255.255.255.0/any) Peer Address is 172.16.0.1, PFS Group is disabled inbound ESP sas Spi: 0xbba97427 Transform: aes256(key length=256 bits), sha1...
Page 360
PhoNe IVR, AA, VMS UMS, Conference Figure 1.1 Ubigate iBG2016 Network Diagram The external entities which interwork with Ubigate iBG2016 over a network is as follows: Ubigate iBG2016 Ubigate iBG2016 acts as the interface between a traditional voice network and the IP network.
Page 361
IP Network method. CLI/Web It is the OAM interface provided by the Ubigate iBG2016 system, which can control various OAM functions of Ubigate iBG2016, after accessing a Ubigate iBG2016 via CLI or web from a desktop or notebook computer.
CHAPTER 1. Voice Feature Operation Mode When the Ubigate iBG2016 runs as SIP gateway, it can work in an Call Manager Interworking mode where it interworks with SIP network via Call Manager, or in a Stand-alone Mode(or Toll Bypass Mode) where it directly interworks with other SIP gateway with Call Manager.
Page 364
Manager(or Proxy Server). Therefore, it is connected to other network entities without separate dependency registration procedure. If Ubigate iBG2016 operates in a Stand-alone mode, the remote office can be multiple different Ubigate iBG2016s, and the Ubigate iBG2016 directly determines call routing according to the dial plan settings.
Page 366
CHAPTER 1. Voice Feature If a Ubigate iBG2016 runs in a gateway mode, a Ubigate iBG2016 performs a general GK registration procedure using RRQ, a gatekeeper identifies the Ubigate iBG2016 as a gateway to be managed in a zone, and a Ubigate iBG2016 provides the H.323 Gateway characteristics necessary for default...
Page 367
Q.SIG(PRI) − Support of Voice Codec Ubigate iBG2016 acts as a VoIP gateway converting the TDM to packets and vice versa, and supports following Voice Codec: ITU-T G.711-Pulse code modulation(PCM) of voice frequencies ITU-T G.711 Appendix I-A high quality low-complexity algorithm for packet loss concealment with G.711...
Page 368
Call Routing and Digit Manipulation Call Routing The calls incoming to a Ubigate iBG2016 can be outbound to PSTN such as Port and Trunk Group, or to the VoIP network such as H.323 Session Target or SIP Session Target. Routing Control is the procedure to determine the route, out of various destinations, where a call will be outbound.
Ubigate iBG2016 system matches a dial string to an outbound POTS dial peer For prefixes, the Ubigate iBG2016 system may add specific digits to the front of the dialed string before it is forwarded to the telephony interface.
Page 370
The Ubigate iBG2016 system provides Call Admission Control based on Maximum Call Number per System Wide. The Call Admission Control Based on Max. Call feature permits the Ubigate iBG2016 system to deny incoming calls exceeding a preconfigured threshold, permitting the selection of a system max.
Page 371
For SIP, initially a normal VoIP call is established using SIP INVITEs. The DSP of the Ubigate iBG2016 system needs to be informed that it can support T.38 mode while it is put into voice mode. Then, during the call, when...
Page 372
CHAPTER 1. Voice Feature FAX Pass-through The Ubigate iBG2016 system does not distinguish a fax call from a voice call. Fax communication between the two fax machines is carried in its entirety in- band over a voice call. Fax up-speed is similar to pass-through in the sense that the fax call is carried in-band over the voice call.
Page 373
PBX. LVBO (Local Voice Busy Out) LVBO provides the Ubigate iBG2016 with the ability to monitor the state of various network interfaces, both LAN and WAN, and busy back the trunk to the PSTN interface if any of the monitored links should fail.
Call Manager Interworking mode, Survivable Telephony Mode and Stand Alone Mode. Call Manager Interworking Mode When running in a Call Manager Interworking mode, a Ubigate iBG2016 provides the supplementary services under the control of Call Manager. Calling Line Identification(CLID) Call Forward-All...
Page 375
Call Waiting and Retrieve Call Transfer-Blind Call Transfer-Consultative Distinctive Ring Stand Alone Mode When running in a Stand Alone mode, a Ubigate iBG2016 provides the following supplementary services to the FXS subscribers connected to itself. CLID Call Hold and Retrieve Call Pickup Group...
CHAPTER 1. Voice Feature E911 Support Ubigate iBG2016 supports an E911 feature. E911 is an emergency telephone system capable of automatically displaying the callback number(and in some cases the location) of a person who dials emergency call numbers(911) to request emergency help from public safety agencies.
Page 377
If Ubigate iBG2016 detects connection fail, it changes to Survivable Telephony mode automatically. In Survivable Telephony mode, Ubigate iBG2016 acts as a SIP server for local call. Using IP phone location and subscriber profile information, Ubigate iBG2016 provides basic call and restricted supplementary service.
Ubigate iBG2016 VoIP system. PSTN Toll Bypass Ubigate iBG2016 provides voice and fax toll bypass capabilities as shown in Figure 26.4. In this scenario a telephonic device attached to a PBX or Key Phone System will be connected to Ubigate iBG2016 through an analog or digital trunk connection.
Page 379
Ubigate iBG2016 Configuration Guide/Ed.00 IP Phones The second scenario of an IP phone attached to Ubigate iBG2016 as shown in Figure 26.5. The SIP phone communicates directly with the Call Manager using SIP Protocol that is passed through Ubigate iBG2016. The Call Managers communicate with each other across the IP network via SIP to establish and maintain the call.
Page 380
The Network Management System uses Simple Network Management Protocol(SNMP) to communicate with Ubigate iBG2016 systems. The SNMP ‘get’ and ‘set’ commands can be used to configure either system and retrieve current configuration and status information.
Ubigate iBG2016 Configuration Guide CHAPTER 2. VoIP Gateway Management Introduction to VoIP Gateway Features VoIP Gateway function is used to deliver voice calls between PSTN and IP network. For interwork with PSTM over IP network, such call processing protocols as SIP, H.323, MGCP, etc. are used over IP network. Ubigate iBG2016 supports SIP and H.323 out of VoIP Call processing protocols.
Page 383
Ubigate iBG2016 Configuration Guide/Ed.00 Step Command Purpose configure terminal Enters global configuration mode. Example) # configure terminal Interface type number Enters interface configuration mode to configure specific Example) interface. /configure# interface Ethernet 0/0 ip address ip_address subnet_mask Configure a IP Address for an interface.
Page 385
Ubigate iBG2016 Configuration Guide/Ed.00 bind media To specify the source address of media stream, you have to do the followings. Configuration Steps configure terminal − voip-gateway − bind media − exit − Detailed Steps Step Command Purpose configure terminal Enters global configuration mode.
Page 387
Ubigate iBG2016 Configuration Guide/Ed.00 Enabling or Disabling Voip Services There are two ways of enabling or shutting down VoIP service. One uses a shutdown command in voip-gateway configuration mode, the other one uses a shutdown command in sip-ua configuration mode or h323-gateway configuration mode.
Page 388
Manager. All calls of Ubigate iBG2016 in a Call Manager Inter-working mode pass through Call Manager. If a Call Manager is not set, a Ubigate iBG2016 runs in a Stand Alone mode. You can specify the SIP signaling IP Address and port of Call Manager using ip-address command in a call-server configuration mode, and also specify optionally the registration expire value in a Call Manager Inter-working mode.
Ubigate iBG2016 Configuration Guide CHAPTER 3. SIP Gateway Management Introduction to SIP Gateway Features Information about SIP SIP is a simple, Text-based protocol that uses requests and responses to establish communication among the various components in the network and to...
Page 393
Ubigate iBG2016 Configuration Guide/Ed.00 From an architectural standpoint, the physical components of a SIP network can be grouped into two categories: clients(endpoints) and servers. Figure 28.1 illustrates the architecture of a SIP network. SIP Client Phones User agent which can attempt or receive a call voluntarily.
Page 395
Ubigate iBG2016 Configuration Guide/Ed.00 How SIP Works with a Proxy Server If a proxy server is used, the caller user agent sends an INVITE request to the proxy server, the proxy server determines the path, and then forwards the request to the called party. The called party responds to the proxy server, which in turn, forwards the response to the caller.
Page 397
Ubigate iBG2016 Configuration Guide/Ed.00 How SIP Works with a Redirect Server If a redirect server is used, the caller user agent sends an INVITE request to the redirect server, the redirect server contacts the location server to determine the path to the called party, and then the redirect server sends that information back to the caller.
Page 399
Ubigate iBG2016 Configuration Guide/Ed.00 SIP Call Flows This section describes the basic SIP call flow in an SIP gateway. SIP Gateway to SIP Gateway-Call Setup and Disconnect Figure 28.7 shows a successful gateway-to-gateway call setup and disconnect. The two end users are User A and User B. User A is located at PBX A, which is connected to SIP gateway 1 via a T1/E1.
Page 401
Ubigate iBG2016 Configuration Guide/Ed.00 Table 3.1 Call Setup and Disconnect (Continued) Message Description Connect ACK Upon receiving ACK, SIP Gateway2 sends Connect ACK to PBX B. Disconnect If a subscriber hangs up the phone, SIP Gateway 2 receives Disconnect from PBX B. Disconnect indicates that User B requested a call release.
Ubigate iBG2016 Configuration Guide/Ed.00 Table 3.2 Call via Redirect Server Message Description Setup SIP Gateway 1 receives Setup from PBX A. Setup indicates the call attempt from User A to User B. INVITE SIP Gateway 1 sends INVITE request to a redirect server.
Page 405
Ubigate iBG2016 Configuration Guide/Ed.00 SIP Gateway to SIP Gateway-Call via Proxy Server Figure 28.9 shows the call of SIP Gateway to SIP Gateway using SIP Proxy server. Table28.3 briefly describes the messages used in the call flow. User B User A PBX A...
Page 407
Ubigate iBG2016 Configuration Guide/Ed.00 Table 28.3 Call via Proxy Server (Continued) Message Description SIP Gateway 1 sends ACK request to a Proxy server. ACK request indicates that SIP Gateway 1 received 200 OK response normally. Proxy server sends ACK request to a SIP Gateway2.
Page 409
Ubigate iBG2016 Configuration Guide/Ed.00 Ability to hide the identity of the calling party by RFC 3325-Private Extensions to the Session Initiation Protocol(SIP) for Asserted Identity within Trusted Networks. Support for sips uri over TLS. capability to periodically refresh SIP sessions by sending repeated UPDATE requests.
Page 411
Ubigate iBG2016 Configuration Guide/Ed.00 Step Command Purpose configure terminal Enters global configuration mode. Example) # configure terminal Interface type number Enters interface configuration mode to configure specific Example) interface. /configure# interface Ethernet 0/0 ip address ip_address subnet_mask Configure a IP Address for an interface.
Page 413
Ubigate iBG2016 Configuration Guide/Ed.00 bind media To specify the source address of media stream, you have to do the followings. Configuration Steps configure terminal − voip-gateway − bind media − exit − Detailed Steps Step Command Purpose configure terminal Enters global configuration mode.
Page 415
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Basic SIP Call Services This section describes the basic configuration necessary for SIP gateway functions. Since it is essential for SIP call signaling, it should be done before other settings. This section describes how to specify the domain name used in SIP signaling, and the function to enable/disable SIP service.
Page 417
Ubigate iBG2016 Configuration Guide/Ed.00 shutdown in sip-ua configuration mode The procedure to enable or disable SIP service is as follows. Configuration Steps configure terminal − voip-gateway − sip-ua − [no] shutdown − exit − exit − Detailed Steps Step Command...
Page 418
Configuring Call Manager This section describes the configuration necessary for interworking with Call Manager. All calls of Ubigate iBG2016 in a Call Manager Inter-working mode pass through Call Manager. You can specify the SIP signaling IP Address and port of Call Manager using ip-address command in a call-server configuration mode, and also specify optionally the registration expire value in a Call Manager Inter-working mode.
Page 421
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring SIP Proxy This section describes how to set the SIP proxy used in a Stand-Alone mode. If you set a sip-server as a session target of dial-peer together with SIP proxy setting, it is possible to send an outbound call to SIP proxy.
Page 425
Ubigate iBG2016 Configuration Guide/Ed.00 How to Configure Dial-Peer for Registration The procedure of registration in SIP Registrar per dial-peer is as follows. Configuration Steps configure terminal − dial-peer − destination-pattern − register {e164 | uri} − exit − Detailed Steps...
Page 426
3xx class of response. In a Call Manager Inter-working mode, all SIP incoming calls of Ubigate iBG2016 is redirected to Call Manager. This means that all calls are controlled by Call Manager.
Page 427
Ubigate iBG2016 Configuration Guide/Ed.00 How to Configure Dial-Peer for SIP Redirect Processing You can limit the Redirect processing count per dial-peer in the following way. Configuration Steps configure terminal − dial-peer − max-redirects − exit − Detailed Steps Step Command...
The opposite is also true: SIP status codes or events are mapped to PSTN cause codes. A Ubigate iBG2016 provides a SIP- PSTN default mapping table. The method for an operator to change the mapping is also provided. You can change the mapping using set pstn-cause command and set sip-status command.
Page 429
Ubigate iBG2016 Configuration Guide/Ed.00 Table 28.4 Table Default PSTN cause code to SIP status code mapping (Continued) PSTN Cause Description SIP Event Code Number changed 410 Gone Non-selected user clearing 404 Not found Destination out of order 404 Not found...
Page 433
Ubigate iBG2016 Configuration Guide/Ed.00 How to Configure SIP Status Code to PSTN Cause Code Mapping You can change the SIP Status code to PSTN Cause code mapping in the following way. Configuration Steps configure terminal − voip-gateway − sip-ua −...
Page 434
SIP-UA configuration mode, you can control the method for Ubigate iBG2016 to handle the SDP delivered via 180 response. To the contrary, it is possible to control whether, when Ubigate iBG2016 sends a 18x provisional response including SDP, to send 180 or 183 response, or send it together with SDP, by using the alert-cut-through command.
Page 435
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose [no] disable-early-media 180 Disables or re-enables early media processing for 180 Example) provisional response. Default is /configure/voip-gateway/sip-ua# enable. disable-early-media 180 exit Exits the current mode Example) /configure/ voip-gateway/sip-ua# exit exit Exits the current mode...
Page 436
Min-SE, which is used to limit the minimum value of the session update cycle. Restrictions for Session Timer Ubigate iBG2016 uses a UPDATE method as the method of session update. Even though Session update is not done using INVITE, when INVITE for session update is received, it is processed normally.
Page 437
Ubigate iBG2016 Configuration Guide/Ed.00 How to Configure Session Timer Feature To enable the Session Timer Feature, you can set Min-Se in the following way. Configuration Steps configure terminal − voice service sip − min-se − exit − Detailed Steps Step...
Page 438
This section describes how to set the use of Reason header in SIP message. To deliver the Q.850 Cause of PSTN via SIP message in SIP-PSTN interworking, a reason header is added to SIP message. Ubigate iBG2016 loads the Q.850 Cause received from PSTN to the reason header of SIP message;...
Page 439
To complement this, an additional method called PRACK is used to ensure reliability of Provisional response. Ubigate iBG2016 supports this function by default, or it can disable or forcibly provide the function.
Page 440
Exits the current mode Example) /configure/voice/service/sip# exit Configuring SIP DTMF Relay This section describes how to set the method of delivering DTMF tone via SIP signaling. To relay DTMF tone, Ubigate iBG2016 supports the 4 methods as follows. inband rtp-nte sip-notify...
Page 441
Ubigate iBG2016 Configuration Guide/Ed.00 Field Description event The DTMF event that is between 0-9, A, B, C, D, #, * and flash. E signifies the end bit. If E is set to a value of 1, the NOTIFY message contains the end of the DTMF event. Thus, the duration parameter in this final NOTIFY message measures the complete duration of the event.
Page 445
Configuring QSIG tunneling over SIP This section describes how to make the settings necessary to deliver QSIG message via SIP signaling. Ubigate iBG2016 provides the function to load QSIG message in SIP message. Its purpose is for QSIG message to be delivered transparently in SIP section, when different QSIG network is connected to SIP.
Page 446
And, MWI function should be set for each FXS voice port. Restrictions for SIP MWI Feature The MWI feature of Ubigate iBG2016, via interworking with MWI server, only notifies if a waiting message exists via audible or visible indication, but does not provide the ‘Call redirection to the voice-mail server when the line is...
Page 447
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose mwi-server ip-address ip-address Sets the ip address of MWI Server. [udp | tcp | tls] [sip | sips] and you can configure transport and uri type. Example) /configure/voip-gateway/sip-ua# mwi-server ip-address ipv4:90.90.90.200 exit...
Page 448
Configuring Calling-Info for SIP Calls This section describes how to set the calling informations for SIP Calls forcibly. Ubigate iBG2016 ignore the caling name and number received from Calling party and change them to what configured. To change the calling...
Page 451
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring SIP Entity Monitoring Features This section describes how to enable SIP Entity Monitoring Features. Ubigate iBG2016 send OPTIONS message to monitor SIP remote entities. If no response received, that entity is concidered as not operating status and new call is not routed to that entity.
Page 453
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Miscellaneous Features This section describes the miscellaneous SIP settings not discussed in the previous section. These commands are available in SIP UA Configuration mode and SIP Service Configuration mode. For the information how to use the commands, see the Command Reference.
SIP server in advance. SIP server requesting the authentication of SIP client response to the request sent from Ubigate iBG2016 with 401 response. Using the information contained in 401 response and UserName/Password, Ubigate iBG2016 adds Authorization Token to a request.
Page 455
Ubigate iBG2016 Configuration Guide/Ed.00 Step Command Purpose configure terminal Enters global configuration mode. Example) # configure terminal dial-peer voice {pots | voip} tag Enters POTS dial-peer configuration mode Example) /configure# dial-peer voice pots 11 authentication username username Configure a user name and...
Page 457
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring SIPS URI with TLS transport This section describes how to set SIP signaling via TLS connection. To do this, set URI type to SIPS, and change the transport type to TLS. You can change the URI type and transport type in two ways. That is, you can make a setting which applies to the entire SIP signaling, or individual dial-peers of SIP type.
Page 459
SIP Signaling. Prerequisites for S/MIME Configuration Before specifying a certificate and private key to POTS Dial-peer, a certificate and private key should be saved in the file system of Ubigate iBG2016 in a PEM format. How to Configure S/MIME Support You can specify the certificate and private key to a desired dial-peer where S/MIME will be used, in the following way.
Verifying and Troubleshooting SIP Features This section describes how to use the show command and debug command to verify and troubleshoot the SIP feature of Ubigate iBG2016. Using show commands You can use the show command commands as follows to confirm or see the current status of the SIP feature settings.
Page 462
3600 uri type is system show sip-ua registration Shows the registration status of Ubigate iBG2016 and each dial-peer. Example) # show sip-ua registeration line peer expires registered Call Server sip:90.90.90.100...
Page 463
Ubigate iBG2016 Configuration Guide/Ed.00 show sip-ua parameters Shows other SIP settings. Example) # show sip-ua parameters SIP configuration SIP-UA : up operation mode = Call-server mode auth username = samsung auth password = samsung SIP-UA is use call-server SIP-UA use ip address for call-server : ipv4:10.254.139.50...
Ubigate iBG2016 Configuration Guide CHAPTER 4. H.323 Gateway Management Introduction to H.323 Gateway Features This section describes how H.323 gateway works in regard to the features stated below. Call Setup Procedure RAS Signalling Codec Negotiation Support for Supplementary Services Call Statistics Conformance H.323 gateway basically follows the recommendations below.
Signalling and Gatekeeper Routed Call Signalling depending on the call model supported by a gatekeeper. This section will discuss how Ubigate iBG2016 performs a call setup procedure in dial-peer depending on the registered information(session target). The H.225.0 SETUP message from the H.323 Endpoint registered as a session target on dial-peer follows the call procedure illustrated in Figure 29.1.
Page 469
Ubigate iBG2016 Configuration Guide/Ed.00 If H.323 gateway is not registered in a gatekeeper, the H.225.0 SETUP message from the H.323 Endpoint not registered as a session target on dial- peer reject calls as in Figure 29.2. iBG2016 a known H.323 endpoint...
Page 471
Ubigate iBG2016 Configuration Guide/Ed.00 When H.323 gateway is registered in a gatekeeper, the H.225.0 SETUP message from gatekeeper follows the call procedure illustrated in Figure 29.4. Figure 29.4 shows the case where a gatekeeper usually uses a Gatekeeper Routed Call Signalling.
Page 473
Ubigate iBG2016 Configuration Guide/Ed.00 When a ‘gatekeeper’is designated as a session target, the H.225.0 SETUP message sent from H.323 gateway follows the call procedure illustrated in Figure 29.6. Figure 29.6 shows the case where a gatekeeper usually uses a Gatekeeper Routed Call Signalling.
Page 475
Ubigate iBG2016 Configuration Guide/Ed.00 H.323 gateway, using the primary and secondary Gatekeeper information, performs registration as shown in Figure 29.7.(However, the Alternative Gatekeeper Procedure is omitted from the flowchart.) start current-gatekeeper is primary gatekeeper send full-RRQ to current-gatekeeper recv RCF?
Page 477
Ubigate iBG2016 Configuration Guide/Ed.00 Codec Negotiation Codec Negotiation reports multiple codecs, which H.323 gateway can support in the H.245 capability exchange stage, to a remote H.323 endpoint, so that a single codec can be selected ultimately in a call establishment stage. Supply of multiple codecs in the H.245 capability exchange stage increases the...
Page 485
Ubigate iBG2016 Configuration Guide/Ed.00 bind media To specify the source address of media stream, you have to do the followings. Configuration Steps configure terminal − voip-gateway − bind media − exit − Detailed Steps Step Command Purpose configure terminal Enters global configuration mode.
Ubigate iBG2016 Configuration Guide/Ed.00 Shutting Down and Enabling H.323 Services This section describes the basic configuration necessary for H.323 gateway functions. Since it is essential for H.323 call signaling, it should be done before other settings. This section also describes how to enable or disable H.323 service.
Page 491
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose destination-pattern number Specifies the telephone number associated with the dial peer Example) Matches dialed digits to a telephony /configure/dial-peer/voice/voip device. 100#destination-pattern 02.T The string argument is a series of digits that specifies the E.164 or private dialing plan telephone number.
Page 493
Ubigate iBG2016 Configuration Guide/Ed.00 Prerequisites for Configuring RAS The followings should be done first before H.323 gateway performs RAS signalling. H.323 services should be already enabled. The information of the H.323 gateway should be previously set on the gatekeeper to interwork.
Page 497
Ubigate iBG2016 Configuration Guide/Ed.00 How to configure RAS Retries and Timers ‘ras timeout’ command sets the time(in second) for H.323 gateway to wait before resending a RAS message to gatekeeper. ‘ras retry’ command specifies the number of retransmissions of RAS message when the specified timeout value is exceeded.
Page 499
Ubigate iBG2016 Configuration Guide/Ed.00 How to configure RRQ TimeToLive ‘ras rrq-ttl’ command specifies the time which should be considered as that H.323 gateway is running after a gatekeeper receives the lightweight RRQ for the last time. H.323 gateway sets this value(TimeToLive value) within a RRQ message and sends it to a gatekeeper.
Page 501
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose exit Exits the current mode Example) /configure/voice/class/codec 100# exit dial-peer voice voip tag Enters dial-peer configuration mode for the VoIP peer designated by tag Example) /configure#dial-peer voice voip 1000 voice-class codec tag...
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Enhanced H.323 Services The additional control of H.323 gateway call processing can be done in a ‘voice service h323’ configuration mode or ‘voice class h323’ configuration mode. ‘voice service h323’ configuration is applied to all H.323 calls, while ‘voice class h323’...
Verifying and Troubleshooting H.323 Features This section describes how to use the show command and debug command to verify and troubleshoot the H.323 feature of Ubigate iBG2016. Using show commands You can use the show command commands as follows to confirm or see the current status of the H.323 feature settings.
Page 511
Ubigate iBG2016 Configuration Guide/Ed.00 show h323-gateway detailed It shows all the setting values of ‘voice class h323’. Example) # show h323-gateway detailed ========================================================= VOICE SERVICE H323 ========================================================= dtmf-relay: [rtp-nte] tech-prefix: [] h225 call-start : fast h245-tunnel : on early-h245 : off...
Page 513
Ubigate iBG2016 Configuration Guide/Ed.00 Using debug commands You can use the following debug commands to view the debugging messages of an application, or the H.323 message sent or received. debug h323 log Command to view the H.323 message. You can display messages by filtering them with calling number or called number.
Ubigate iBG2016 Configuration Guide CHAPTER 5. Analog Voice Port Introduction to Analog Voice Port Features This chapter describes Analog Voice port Features. Analog Voice port plays a role to transmit voice and call signal between a packet-based network and the existing telephony network.
Page 517
Ubigate iBG2016 Configuration Guide/Ed.00 Ground Start Signaling It works by using ground and current detectors that allow the network to indicate off-hook or seizure of an incoming call independent of the ringing signal and allow for positive recognition of connects and disconnects.
Page 519
Ubigate iBG2016 Configuration Guide/Ed.00 Analog E & M Interface Analog E & M Interface Analog E&M interface, which uses special signaling paths that are separate from the trunk’s audio path to convey information about the calls. The signaling paths are known as the E-lead and the M-lead. The name E&M is thought to derive from the phrase Ear and Mouth or rEceive and transMit although it could also come from Earth and Magnet.
Page 521
Ubigate iBG2016 Configuration Guide/Ed.00 Delay-Dial Method Delay-dial method enters ‘seizure’ action by hooking off E-lead from the calling side, after a given time, about 200msec, when the calling side takes a look at the status of terminating side, if the terminating side is on hook status (or he/she awaits till the terminating side enters into on-hook status), calling side sends address information.
Ubigate iBG2016 Configuration Guide/Ed.00 Analog Voice Port Monitoring This section describes the configuration of analog voice port. Analog voice port have an architecture to create a basic configuration of a voice port by which Submarine automatically detects H/W information. Accordingly, when starting up the system, port number of analog voice port is shown automatically to an operator, and it is able to enters into a basic service.
Ubigate iBG2016 Configuration Guide/Ed.00 Telephony signaling interface: Analog FXO, FXS or E & M Locale Code(usually the country) for Call Progress Tone or DTMF/MF Variant If FXO, type of Signal: loop-start or ground-start If FXS, type of Signal: loop-start or ground-start or DID If E &...
Page 527
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose timeouts timer-name interdigit - Configures the number of seconds that timer-value the system waits after the caller has input the initial digit or a subsequent digit of the dialed string. If the timeout ends before the Destination is identified, a tone sounds and the call ends.
Page 529
Ubigate iBG2016 Configuration Guide/Ed.00 Predefined ring cadence patterns. Ring Cadence of Analog FXS have a predefined patterns as follow, and can be set up by on-net , or off-net respectively. On-net means an inbound call coming from FXS line in the inside of submarine, on the while, off-net means inbound transit call except that.
Page 531
Ubigate iBG2016 Configuration Guide/Ed.00 Cadence To define the tone-on and tone-off duration for a call-progress tone, use the cadence command in call-progress dualtone configuration mode. Configure>voice class custom-cptone tag dualtone busy cadence {cycle-1-on- time cycle-1-off-time [cycle-2-on-time cycle-2-off-time] [cycle-3-on-time cycle-3-off-time] [cycle-4-on-time cycle-4-off-time]} cycle-1-on-time - Tone-on duration for the first cycle of the cadence pattern, in milliseconds(ms).
Page 533
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose ring number number (FXO only) Specifies the maximum number of rings to be detected before an incoming call is answered by the router. The default is 1. locale locale Selects the two-letter locale for the voice call...
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Analog E & M Voice Port This section describes the configuration of analog E&M voice port. How to Configure Analog E&M Voice Port Unlike FXO, FXS, E & M voice port is not enough to send voice data as a default value, the set up values of E&N voice port should be sure to be...
Page 537
Ubigate iBG2016 Configuration Guide/Ed.00 Type I, II, III, V There are five different E&M interface types or models: Type I, II, III, IV, and V (Type IV is not supported. Each type has a different wiring arrangement, hence a different approach to transmit E & M supervision signaling(on-hook /off-hook signaling).
Page 539
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose timing {wait- To change timing parameters. wink|wink- wait-wink - Specifies maximum amound of time to wait|wink- wait wink for Outbound Call duration|delay- wink-wait - Specifies maximum wink-wait duration, in duration|delay- milliseconds, for a wink-start signal start } timing-value Valid entries are from 100 to 5000.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Analog DID This section describes the configuration of analog DID Feature. DID Feature Overview This section describes the analog DID Feature Direct Inward Dialing(DID), which is the service proposed by Telephone service providers, is the service to allow a caller to dial to extension of PBX without help of an attendant.
Page 543
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose timeouts timer-name timer- To change timeouts parameters value initial - Sets the number of seconds that the system waits between the caller input of the initial digit and the subsequent digit of dialed string.
Page 545
Ubigate iBG2016 Configuration Guide/Ed.00 For further information on E911, see ‘American National Standard T1.422- 2001’. End Office 9-1-1 Service Provider Selective PSAP ANI/ALI Router CAMA Trunks Controller Tandem Aquired for 911 Traffic PSTN Traffic ALI Database Analog Phone IP Phone Public Safety Answering Point Figure 5.9 E911 Network Diagram...
Page 549
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose timeouts timer-name To change timeouts parameters timer-value initial - Sets the number of seconds that the system waits between the caller input of the initial digit and the subsequent digit of dialed string.
Ubigate iBG2016 Configuration Guide CHAPTER 6. Digital Voice Port This chapter describes the digital voice port Features. The digital voice port commands discussed in this section configure channelized T1 or E1 connections. Digital Trunk E1-R2 Features Digital Trunk T1-CAS Features...
Page 553
Ubigate iBG2016 Configuration Guide/Ed.00 Network Diagram PSTN SIP, H.323 E1 R2 Figure 6.3 E1-R2 Network Diagram Configure E1 Trunk This section shows the process of configuring physical layer of E1 trunk. Configuring E1 Trunk Settings To make a E1 connection with a neighboring equipment interwoking on the PSTN, the configuration should be set up to a characteristic specific to E1 trunk line.
Page 555
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose system carrier-type Input the slot# which is qualified to be E1 trunk card. slot # e1 And if the previous carrier-type of the slot is configured E1, rebooting is not required. Otherwise the system will prompt you to reboot the system for the change to take effect.
Page 557
Ubigate iBG2016 Configuration Guide/Ed.00 Voice Port PSTN Voice PSTN Signaling Packet Properties Properties PSTN PCM Voice Properties Figure 6.4 Conceptual view of voice port DS0 group is a concept of a logical voice port controllable in a system by combining several DS0 channels in a digital trunk.
Page 559
Ubigate iBG2016 Configuration Guide/Ed.00 Configure R2 on DS0 group R2 Signaling R2 signaling is channelized E1 signaling used in Europe, Asia, and South America. It is equivalent to channelized T1 signaling in North America. There are two types of R2 signaling: line signaling and interregister signaling.
Page 561
Ubigate iBG2016 Configuration Guide/Ed.00 By using show module configuration, it is possible to check out carrier type of the trunk working. v239# show module configuration t1 0/1/0 T1 0/1/0 is ENABLED Alarm Hierarchy: TRUE, Yellow Alarm: DISABLE Framing:ESF, LineCode:B8ZS, ClockSource: INT, LineMode:CSU, LBO:0 db...
Page 563
Ubigate iBG2016 Configuration Guide/Ed.00 OPER indicates status changes while voice port or DS0 channel works. This appears as ‘up’ in case that the voice port or DS0 channel is normally in service, and as ‘down’ while the voice port is out of service due to failure of voice card.
Page 565
Ubigate iBG2016 Configuration Guide/Ed.00 Trunk Voice port Management This section describes management of logical voice ports configured in digital E1 trunk. create a DS0 group delete a DS0 group configure DS0 group Create Trunk Voice Port logically combines DS0 channels in a digital trunk to manage ds0 group.
Page 567
Ubigate iBG2016 Configuration Guide/Ed.00 The presence of echo occurs whenever the replicated signal delay exceeds 10 msecs, and becomes apparent to the speaker as reflected voice when the delay exceeds as little as 16 msec. It is manifested to the far end as an altered replica of the speaker original.
Page 569
Ubigate iBG2016 Configuration Guide/Ed.00 Step Command Purpose configure terminal Enter the global configuration mode. dial-peer voice Enter the dial-peer configuration mode. voip number playout-delay Determines the mode in which the jitter buffer will mode {adaptive | operate for calls on this dial-peer.
Page 571
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose caller-digits Specifies the number of digits needed to be collected before it requests ANI. default Sets a command to its default setting. dnis-digits Specifies the expected number of DNIS digits. invert-abcd Specifies the inversion of the ABCD bits before tx and after rx.
Page 575
Prerequisites Before you attempt this configuration, ensure that you meet these prerequisites: T1-CAS signaling applies to T1 trunk only In order to run T1-CAS signalings on the UBIGATE IBG2016 routers, these hardwards are required: WTE-2M or WTE-4 − Define the command cas-ds0-group on the T1 trunk(module) to create ds0- group.
Page 577
Ubigate iBG2016 Configuration Guide/Ed.00 This procedure is much like the same as the configuration of E1 trunk. Step Command Purpose show voice card all List all the voice cards installed in the system. If you find any of the WTE_XX card you can choose the one to use a T1 trunks card.
Page 579
Ubigate iBG2016 Configuration Guide/Ed.00 Trunk Status Monitoring This procedure is much like the same as the configuration of E1 trunk. Details in each following section refer to ‘Trunk Status Monitoring’. Physical Layer Status Using show voice card all, check all the voice card installed in the system...
Page 581
Ubigate iBG2016 Configuration Guide/Ed.00 Trunk Voice port Management This section describes management of logical voice ports configured in digital E1 trunk. create a DS0 group delete a DS0 group configure DS0 group Create Trunk Voce Port It manages with ds0 group by logically combining DS0 channel, which belongs to digital trunk.
Page 583
Ubigate iBG2016 Configuration Guide/Ed.00 Configure Advanced Trunk Voice Port Parameters It is the same as creation of E1 trunk voice port, and for T1 CAS signaling, and the following advanced setting is possible. T1-CAS Bit Modification Settings The bit modification commands for digital voice ports modify sent or received bit patterns.
Page 585
Ubigate iBG2016 Configuration Guide/Ed.00 Step Command Purpose voice-port slot/sub- To set up the attribute values of created ds0- slot/port:ds0-group-no group, enter voice-port configuration mode. shutdown Shuts down the voice port to manipulate ‘timeslots’ and ‘signal cas’ command. calling-number Specifies ANI to be sent out when the T1-CAS...
Page 587
Ubigate iBG2016 Configuration Guide/Ed.00 Timing Settings To change timing parameters, use the following commands as appropriate, in voice-port configuration mode. Step Command Purpose voice-port slot/sub- To set up the attribute values of created ds0- slot/port:ds0-group-no group, enter voice-port configuration mode.
Page 589
Ubigate iBG2016 Configuration Guide/Ed.00 Ground Start Ground Start signaling was originally developed to aid in resolving Glare. In Loop Start the only way to indicate an inbound call from the network is to Ring the phone. During a full 6-second ringing cycle there is a 4-second period when the phone is not physically ringing.
Page 591
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose timeslots timeslot-list timeslots-Specifies the single time slot number, single range of numbers, or multiple ranges of numbers separated by commas. For T1, allowable values are from 1 to 24. Examples are as follows:...
Page 593
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose timeslots timeslot-list timeslots-Specifies the single time slot number, single range of numbers, or multiple ranges of numbers separated by commas. For T1, allowable values are from 1 to 24. Examples are as follows:...
Ubigate iBG2016 Configuration Guide CHAPTER 7. ISDN Overview Integrated Services Digital Network(ISDN) is composed of data service and telephone service provided by telephone carrier. Since ISDN includes digitalization of telephone, it can transmit voice, data, text, graphic, music, video and data transmissible by various telephone line. The appearance of ISDN enables standardizing subscriber service standard, user network interface, the capacity of network and inter-network.
Page 601
Ubigate iBG2016 Configuration Guide/Ed.00 Calling Calling Called Called Called Router router call Pick up Set up Set up Set up ACK Information Call Proceeding Ringing Alerting Alerting Pick up Ring back indication Connect Connect Stop ring back indication Connect ACK...
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring the ISDN BRI Switch To configure the switch type, use the following command. Step Command Purpose configure terminal Configures to set up bundle. interface bundle sets up bundle name. bundle-name Link bri 0/0/0:1 sets up the pertinent physical link.
Page 605
Ubigate iBG2016 Configuration Guide/Ed.00 Actviate the ISDN To activate the ISDN, use the following command. Step Command Purpose configure terminal Configures to set up bundle. interface bundle Sets up bundle name. bundle-name link bri 0/0/0:1 Sets up the pertinent physical link.
Page 607
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Inclusion of the Sending Complete Information Element In some geographic locations, such as Hong Kong and Taiwan, ISDN switches require that the Sending Complete information element be included in the outgoing Setup message to indicate that the entire number is included.
Page 609
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Command Purpose show isdn status Displays the ISDN Line Status WORD v239# show isdn status bri000 ==== NETWORK side configuration === Layer 1 Status: NOT ACTIVE Layer 2 Status: NOT ACTIVE TEI MODE MULTIPOINT Layer 3 Status:...
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring ISDN PRI Requirements Prerequisites Before you attempt this configuration, ensure that you meet these prerequisites: If the router will be the only device attached to the PRI, ask for point-to- point service and a data-only line.
Page 615
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Voice type To configure the voice type, use the following command. Step Command Purpose configure terminal Configures to set up bundle. interface bundle bundle-name Sets up bundle name. link [pri_t1|pri_e1] 0/0/0:1 Sets up the pertinent physical link.
Page 617
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Inclusion of the Sending Complete Information Element In some geographic locations, such as Hong Kong and Taiwan, ISDN switches require that the Sending Complete information element be included in the outgoing Setup message to indicate that the entire number is included.
Page 619
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Command Purpose show isdn status Displays the ISDN Line Status WORD v239# show isdn status pri000 ==== NETWORK side configuration === Layer 1 Status: NOT ACTIVE Layer 2 Status: NOT ACTIVE TEI MODE POINT-TO-POINT Layer 3 Status:...
Ubigate iBG2016 Configuration Guide CHAPTER 8. Routing and Digit Manipulation This chapter describes how to implement dial plans by configuring dial peers and using dial peer matching, digit manipulation, access group, trunk-group, PLAR and COR features. Dial Peer Management Dial Peer Overview To configure dial peer is an important task for establishing dial plan and transmitting voice on packet network.
Ubigate iBG2016. Both figure 33.2 and figure 33.3 are the cases to be applied to call through packet network. If originating and terminating POTS interface are in the same Ubigate iBG2016, it is sufficient with two POTS dial peers. Source...
Page 625
Ubigate iBG2016 matches POTS dial peer with inbound call leg. Also it matches VoIP dial peer with outbound call leg. Against incoming call from packet network, Ubigate iBG2016 matches POTS dial peer to make a call and it matches VoIP dial peer with inbound call leg to apply configuration elements such as codec.
Page 627
When it is POTS dial peer, input port command to transmit call. When it is VoIP dial peer, input session target command to transmit call. In the case of POTS incoming call, Ubigate iBG2016 selects outbound dial peer based on whether it is DID of inbound POTS dial peer. Both cases support longest matching.
Page 628
Configuring Dial Peers Configuring Dial Peers for Call Legs When call enters Ubigate iBG2016, it is necessary to do dial-peer matching for routing. On call bound to packet network after entering POTS interface, Ubigate iBG2016 should do matching POTS dial-peer against inbound call leg.
Page 629
4:10.1.1.2 Figure 8.6 Dial Peers from the Perspective of the Terminating Ubigate iBG2016 The above setup information shows that in VoIP dial peer of Ubigate iBG2016 B the last four digits of desitination parttern is replaced as wild card.
Page 630
Inbound call leg does not match, use the already defined default dial peer as inbound dial peer. Dial peer 2 of Ubigate iBG2016 B in the figure 33.6 is necessary when call is tried with A only in Ubigate iBG2016 B.
Page 631
Ubigate iBG2016 Configuration Guide/Ed.00 In most cases, it is sufficient in connecting call with the basic value of POTS dial peer configuration command except the above setup. To configure POTS dial peer, use the following command starting in global configuration mode.
Page 633
Valid entries for the string argument are 0 string through 9. Configuring VoIP Dial Peers VoIP dial peer makes possible call with the particular Ubigate iBG2016 telephony device. To set VoIP dial peer, the followings should be done. Assign dial peer with the tag number only.
Page 635
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Step Command Purpose codec { g711alaw | Defines the codec for the dial peer. g711ulaw | g723r53 | Ptime means the time between frames g723r63 | g726 | g729 } transmitted. The unit is msec and has the...
Page 637
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Command Purpose h225 h245-tunnel {on|off|system} Specifies the H.245 Tunnelling support. h225 T301 seconds Maximum time to wait for CONNECT or RELCOMP message, after receiving ALERT message. h225 T303 seconds Maximum time to wait for CALLPROCEEDING or ALERTING or PROGRESS or RELCOMP message, after sending SETUP message.
Page 639
VoIP dial peer is routed to session target. Against Outbound VoIP dial peer, destination pattern determines dialed digit Ubigate iBG2016 should collect and transmit. The entire dial peer created in Ubigate iBG2016 should possess destination pattern. Destination pattern should possess full telephone number or the partial number together with wildcard digit(ex: period-‘.’).
Page 641
Ubigate iBG2016 Configuration Guide/Ed.00 Session Target Session target is the network address of remote Ubigate iBG2016, which is a call intended to transmit. Set up in VoIP dial-peer with ‘session target’ command. Destination-pattern is telephone number of telephone attempting to connect in outbound dial-peer.
Page 642
POTS dial-peer, called number attempts to automatically match with destination pattern to find outbound call leg. If DID is not setup on the moment of incoming call, Ubigate iBG2016 transmits dial tone to caller and collects additionally numbers to find outbound dial-peer.
Page 643
3 If priority should be given between dial peers within the set hunt group, use preference command. Ubigate iBG2016 first makes possible call in terms of dial peer, which possesses preference in hunt group. Low preference number gets higher priority. When the same preference number in hunt group occurs, it is selected randomly.
Page 645
Ubigate iBG2016 Configuration Guide/Ed.00 Numbering Type Matching Dial peer checks number type matching in addition to the condition such as incoming called number, answer address, destination pattern, port and ip- addresss. It determines dial-peer number type with ‘numbering-type’ dial- peer configuration command.
Input T-indicator representing timeout at the end of destination of outbound voice-network dial peer and wait for inputting additional digit after receiving the Ubigate iBG2016-fixed length of dial string. Timeout letter is ‘T’ in capital letter. The following dial-peer configuration is the example of configuring T-indicator to enable variable-length dial string.
Digit Strip and Prefixes When the Ubigate iBG2016 of the receiver side matches with dial string as outbound POTS dial peer, Ubigate iBG2016 basically takes out digit matching specifically with destination pattern. The remaining digit is transmitted to either PBX or PSTN.
Page 649
Ubigate iBG2016 Configuration Guide/Ed.00 For example, Let’s assume that E.164 called number is 82(02)3438-4968. In the office, call is made possible by pressing number 14968, which is the extension number of the telephone. If users set destination-pattern with ‘82023438’ in outbound POTS dial peer which is associated with the telephone, termination GW strips ‘82023438’after receiving call with...
Page 650
The figure 33.9 shows the network of the small company which desires to use VoIP for integrating the telephone network in the current ip network. Destination-pattern of Ubigate iBG2016 A is 408 115-xxxx, 408 116-xxxx, 408 117-xxxx. Destination-pattern against Ubigate iBG2016 B is 729 555- xxxx.
Ubigate iBG2016 Configuration Guide/Ed.00 In the above circumstances, configuring table to apply number expansion is the same as the following. Table 8.2 Number Expansion Commands Extension Destination Pattern Num-exp Command 5…. 408115…. numexp 5…. 408115…. 6…. 408116…. numexp 6…. 408116….
Page 653
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Translation Rule Set By using ‘voice translation-rule’ global command, creating rule set is possible. Using ‘rule-match-replace’ voice translation-rule command, it is possible to designate match & replace rule in rule set. Equally, users can designate reject rule using ‘rule-reject’ voice translation-rule.
Ubigate iBG2016 Configuration Guide/Ed.00 Access Group Management Introduction Applying the call block function to determine whether it permits call or not based on Ip address prior to inbound dial peer matching against VoIP incoming call is used. Executing classification function is possible by setting Permit and deny.
Ubigate iBG2016 Configuration Guide/Ed.00 Trunk Group Management Introduction Trunk group is the logical group of interface having the same signal type. Thus, even though a single channel is in operation or in failure call is made through other channels. The type of signal type is as follows.
Page 660
Hunt scheme is the selection method for selecting voice port or channel. Trunk group having various members uses hunt scheme to find idle channel for routing outgoing call. Hunt scheme provided in Ubigate iBG2016 is random, round-robin, sequential. Assume the three trunk groups. A has the preference value which is the smallest.
Page 661
Ubigate iBG2016 Configuration Guide/Ed.00 Round-Robin Trunk group finds idle channel in sequence. By remembering the previously selected channel, follow the sequence when finding channel afterwards. This method meets channel load balance between trunk group elements. With optional parameter, it is possible to change to find either channels or the even, odd channel in either ascending or descending order.
Page 664
By using this option, local voice port provides the local response before the remote voice port receives answer. The PLAR-OPX connection makes possible call before user makes dialing. The Ubigate iBG2016 uses the digits that follow the command internally to send to a dial peer Voice port PLAR...
Page 667
Ubigate iBG2016 Configuration Guide/Ed.00 To set up COR, use commands on the bottom of global configuration mode. Configuration Steps configure terminal − dial-peer cor custom − name − exit − dial-peer cor list − member − exit − dial-peer voice {pots|voip} −...
Page 669
Ubigate iBG2016 Configuration Guide/Ed.00 Verifying Classes of Restrictions To check COR configuration, follow the below procedures. To check the configured COR and list, use ‘show dial-peer cor’ command. <<< Class of Restriction >>> < COR Custom NAME > name: corname1...
Ubigate iBG2016 Configuration Guide CHAPTER 9. Extended VoIP Services This chapter provides an overview of Voice over IP(VoIP) services. The chapter contains the following sections: Fax Relay with VoIP Supplementary services for Call Manager Interworking mode Supplementary services for Survivable telephony mode...
Supplementary Services for Call Manager Interworking Mode Service Descriptions Ubigate iBG2016 provides supplementary services like Table 34.1 through control of Call Manager in Call Manager interworking mode. For the methods of using services not mentioned in this document, see the Call Manager Operation Manual.
Page 679
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Service Description Call Forwarding This is the function that transfers the incoming call to voice mail to VMS – device, so an extension subscriber can leave a voice message in NoAnswer the voice message box when the subscriber cannot answer the phone.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Services All the configuring service of Call Manager Interworking mode are done in the Call Manager. But, for CLID Service enable the function that transfers a Caller Id to a FXS phone in FXS voice-port.
Page 682
Configuring Feature Codes To support smooth provision of services, the following feature codes should be set in a Ubigate iBG2016. The feature codes regarding Call Pickup and Call Waiting are commonly used regardless of the operation mode. For more information on feature code settings, see the Command Reference.
Page 683
Ubigate iBG2016 Configuration Guide/Ed.00 (Continued) Command Purpose group-call-pickup It is a feature code used for Group call pickup or Universal call pickup. Dial the group-cal- pickup feature code to pick up the call terminating toward the subscriber in the pickup group which is the same as yours.
Supplementary services for Survivable Telephony Mode Service Descriptions Even in Survivable telephony mode, Ubigate iBG2016 independently provides some supplementary services provided by Call Manager control in Call Manager interworking mode. The services provided in survivable telephony mode are like Table 34.2 below.
Page 687
Ubigate iBG2016 Configuration Guide/Ed.00 Table 34.2 Supplementary services for Survivable telephony mode (Continued) Service Description Call Waiting and Call waiting lets users receive a second incoming call on Retrieve the same line without disconnecting the first call. When the second call arrives, the user receives a brief call waiting indicator tone.
Page 688
CHAPTER 9. Extended VoIP Services Configuring Services Ubigate iBG2016 does not require a user to set up separately for services of survivable telephony mode. In the Call Manager Interworking mode, it controls services on the basis of subscriber profiles downloaded from Call Manager.
Ubigate iBG2016 Configuration Guide/Ed.00 Supplementary Services for Stand Alone Mode Service Descriptions Ubigate iBG2016 independently provides services in Stand Alone mode as Table 34.3 below. Table 9.3 Supplementary services for Stand Alone mode Service Description CLID Calling Line Identification(CLID) function displays a calling party’s phone number on a terminal of a called party.
Page 691
Ubigate iBG2016 Configuration Guide/Ed.00 How to Configure Voice-Port for CLIDB To block Caller Id in an originating call of FXS phone, follow the procedures as below. Configuration Steps configure terminal − voice-port − caller-id block − exit − Detailed Steps...
This function does not operate when applied to the whole Ubigate iBG2016 system. This is because the call limitation function that permits max calls is used in the Call Manager.
Page 697
Ubigate iBG2016 Configuration Guide/Ed.00 DS0 Limitation DS0 Limitation limits available physical interface. To limit a certain amount of max calls coming through PBX, it blocks a part of the channels in E1/T1 trunk, which is connected to PBX, in order to decrease DS0 in the system.
Ubigate iBG2016 Configuration Guide/Ed.00 Voice Bandwidth When WAN link is used for processing VoIP call, this is the function to calculate media bandwidth used as WAN link by using voice bandwidth set up, and control in order that the bandwidth that is more than the permitted bandwidth may not be used in VoIP media.
Page 701
Ubigate iBG2016 Configuration Guide/Ed.00 If you want to check current busyout monitor list, use ‘show voice busyout monitor’ command. Using show voice busyout port, a user is able to check voice port list currently busyout set and information on the reason why voice port is busyported.
Page 703
Ubigate iBG2016 Configuration Guide/Ed.00 interface-number Identifies an interface to be monitored for the voice port busyout function. in-service(Optional) Configures the voice port to be busied out when any monitored interface comes into service(its state changes to up). If the keyword is not entered, the voice port is busied out when all monitored interfaces go out of service(their state changes to down).
To monitor utilization which is the global resource of Ubigate iBG2016 gateway. A user can set it up using ‘call-admission threshold global’ command that is the global CAC configuration, and release it using ‘no’...
Page 707
To monitor memory which is the global resource of Ubigate iBG2016 gateway. A user can set it up using ‘call-admission threshold global’ command that is the global CAC configuration, and release it using ‘no’...
Ubigate iBG2016 Configuration Guide/Ed.00 Call-admission Spike This is the function that cuts calls, monitoring when incoming calls reach their peak in a certain period. To set up this function, use ‘call-admission spike’ which is global CAC configuration command, to release it use ‘no’ command.
Ubigate iBG2016 Configuration Guide CHAPTER 11. Management Alarm There are 7 alarms and 2 faults in relation to voice from Ubigate iBG2016 Gateway. Alarm There are mainly 5 types of alarms in relation to voice. The alarms are in relation to Call Count, DSP channel, SIP entity, H323 gatekeeper, and FXS port.
Voice task fail When operating the Ubigate iBG2016 system, this fault occurs in case that task related to voice processing suspends. In this case, Ubigate iBG2016 system cannot be used as voice gateway.
CHAPTER 11. Management Statistics Ubigate iBG2016 statistics displays the numerical value of accumulation after booting up of the system. The objects of Ubigate iBG2016 statistics are as followings. Call statistics-whole call statistics, POTS call statistics, VoIP call statistics. Protocol statistics-SIP, H323 protocol statistics.
Page 715
Ubigate iBG2016 Configuration Guide/Ed.00 Table 36.4 Call Statistics Item (Continued) Item Object explanation Outbound POTS, VoIP, Call Outgoing failed calls Failed Calls - number of outgoing calls that failed Inbound Call Incoming abnormal terminated calls Abnormal - number of incoming answered calls...
Page 717
Ubigate iBG2016 Configuration Guide/Ed.00 Table 36.6 SIP protocol Statistics command (Continued) Item Explanation Ok Notify Num 200 Successful response to a Notify request Ok Options Num 200 Successful response to an Options request Ok Prack Num 200 Successful response to a PRACK request...
Page 719
Ubigate iBG2016 Configuration Guide/Ed.00 Table 36.6 SIP protocol Statistics command (Continued) Item Explanation Request Terminated Num 487 The request is canceled Not Acceptable Here Num 488 Call was contacted, but some aspect of the session description was unacceptable Bad Event Num...
Page 721
Ubigate iBG2016 Configuration Guide/Ed.00 Table 36.8 H.225.0 CS Statistics command (Continued) Item Explanation Notify Number of Notify messages the gateway has received and transmitted Status Number of Status messages the gateway has received and transmitted Status Inquiry Number of StatusInquiry messages the gateway has...
Page 723
Ubigate iBG2016 Configuration Guide/Ed.00 Table 36.9 H.225.0 RAS Statistics command (Continued) Item Explanation ServiceControlIndication Number of SCI messages the gateway has received and transmitted ServiceControlResponse Number of SCR messages the gateway has received and transmitted Unknown Number of unknown messages the gateway has received and transmitted Table 11.10 H.245Statistics command...
Ubigate iBG2016 Configuration Guide/Ed.00 Debug Management This section describes commands that show Debug related to voice. Following contents are displayed: Voice Call Control Debug. Voice Protocol Module Debug. H323 Debug. SIP Debug. Voice Debug. Voice Call log Debug Voice Call Control Debug Mode This is the function that shows an appropriate call log after a voice call.
CHAPTER 11. Management CDR Management Ubigate iBG2016 system transmits CDR made by processing a call to RADIUS server. This section describes the method of configuration to manage CDR and CDR attribute. Configuration Restrictions for CDR Management Works only when an Authentication, Authorization, and Accounting(AAA) RADIUS server is enabled for VoIP calls.
Page 730
CHAPTER 11. Management CDR Attributes The CDR in the Ubigate iBG2016 system transmits accounting request packet according to RADIUS specification described in RFC2865, RFC2866. The attribute described in Table 36.1 below is used and numerous Vendor Specific Attributes are included.
Page 731
NAS MUST use the same Acct-Session-Id in the Accounting-Request packets for that session. vendor specific attribute Vendor specific attributes used in the Ubigate iBG2016 system are arranged in the following table and the values of VSA attribute field are as followings. Type field = 26 Length field >=7 byte(vendor-string field has to be more than 1byte)
Page 732
CHAPTER 11. Management System ID VSA No: 4 Length: 32 Ubigate iBG2016 system ip address or domain-name Call ID VSA No: 3 Length: 12 Call ID Calling party type VSA No: 22 Length: 4 Calling party category. Information on a category of calling party.
Call Manager interworking mode. Besides, in case a subscriber does not set up Ubigate iBG2016, it generally provides a method to set up Call-Forwarding Service. That is, in the situation that a call is...
CHAPTER 12. Survivable Telephony Configuring System Message for Survivable Telephony When Ubigate iBG2016 is converting between Call Manager interworking mode and Survivable Telephony mode, to inform that mode is converting, it sends designated messages through MESSAGE method with SIP phone.
Page 737
Ubigate iBG2016 Configuration Guide/Ed.00 How to Configure System Message for Call Manager interworking mode When Survivable Telephony mode is converted to Call Manager interworking mode, it sets up the message that would be sent to SIP phone as following procedures. The basic message is ‘Normal Mode’.
Ubigate iBG2016 Configuration Guide/Ed.00 Configuring Translation for Survivable Telephony Digit translation is also applicable in Survivable telephony mode. This is a mechanism that handles numbers, automatically modifying or adding area code or prefix of calling and called number. It is applicable not only to translation rule but also translation profile.