Patton provides this SmartWare Configuration Library as a free service to SmartNode administrators. The library contains example command sets for configuring and activating such SmartWare services as DHCP, QoS, VPNs, Frame-Relay, and many others. Patton offers these examples to help you implement selected features and functions from within SmartWare's rich set of software services.
The SmartWare commands displayed here are valid and applicable with all models in Patton's SmartNode family of VoIP solutions. SmartNode administrators may freely copy and paste these examples into your own SmartWare configuration files. While some examples can be applied to your SmartNode exactly as shown (Tone Sets, SNTP, etc.), others are templates that require you to modify certain details to reflect your specific network environment (SIP, DHCP, DynDNS, etc).
NOTE: For some of these configuration templates to work with your SmartNode, you must make site-specific modifications that reflect the unique requirements of your application environment.
SmartWare™ CLI Style Guide Patton has published a concise style guide in PDF format for the SmartWare Command Line Interface (CLI). The brief guide offers Patton's recommended naming conventions and style guidelines for creating configuration elements such as profiles, interfaces, gateways, etc. using SmartWare's CLI. Adhering to these recommendations will make your SmartWare configuration files easier to read and re-use, further enhancing the usefulness of the configuration examples below.
It is possible to store call logs with quality information in the local aaa data sink. To do so, a service aaa is needed where the calls are routed through. Create a profile aaa with the method local. Then create a service aaa to route the calls through.
To see the collected logs use the command show accounting or use the Web-GUI to see the logs. In the Web-GUI, go to the 'Reports' page and select “Call Quality Log” in the tab bar on top of the page. On that page, you will also have the option to export the log as a comma separated text file.
The service ‘priority’ can automatically free resources if a high priority call needs to be established while no resources are available. The service ‘priority’ can have multiple ports. You can assign a priority level for each port. This priority level defines the priority level of each call, which is received through the port. If a call with higher priority fails to be established, the service tries dropping lower priority calls to free resources for the higher priority call. Subsequently it tries to establish the higher priority call again. The configuration below is a typical application for this service in which non-.emergency calls are dropped to free resources for emergency calls.
The configuration below routes every call from the fxs-ports to a routing-table and if it is an emergency call (number 112, 117, 118, 119) to the higher port with the higher priority. Every other call can be dropped if an emergency call needs to be placed.
The call-router ‘limiter’ service limit offers a flexible technique to limit the maximum number of concurrent
calls within the system. It also limits the call-setup rate within a system. Calls exceeding the defined limits can
either be simply dropped or they can be handled differently. A call is counted as an active call as soon as the
call-setup message reaches the limiter service. The call remains active until the signaling has completed tearing
down the call.
The SmartNode sends a CDR message if a incoming or outgoing Call-Setup passes the SIP-Interface.
You may define and configure a independent CDR-services-element for each call-routing-leg.
Allows you to pick up Phone 0 and ring all other 7 ohones at the same time. Then once one of the other 7 phones is answered the call is connected and the other phones cease ringing.
The command sequence below enables SmartNode to provide second-dial-tone service. Once a user connects to a SmartNode FXO port, SmartNode will generate and deliver a second dialtone to the user. The routing-table RT_CDPN decides where to deliver the call.
ENFORCE THE TRANSPARENT CODEC FOR ISDN UD-64 CALLS:
Incoming ISDN calls will be split into two call-router paths to enforce transparent codec for ISDN unrestricted digital calls.
Note that the VOIP-DATA interface has no route into the call-router, it operates as a one-way interface. However it has a special Voip-Profile linked, which only contains the transparent codec.
The VOIP-DEFAULT interface will be used for incoming voip calls. It uses the default voip profile, which is linked in the voip gateway.
The default profile contains the transparent codec with the lowest priority to ensure that voice calls never uses the transparent codec.
Command Sequence to Copy, Edit, and Paste
SN2X00 / 2*IC-E1Voip Gateway PBX to SIP with PSTN Fallback ( Link to this Config )
Configuration Description
SmartNode 2X00 used as an ISDN E1 gateway between a PBX and a SIP Network. The second E1 port may be used for Fallback to the PSTN.
Please read the comment before using the configuration.
Command Sequence to Copy, Edit, and Paste
SN1X00 / SN4552 / SN46XX; Phone Gateway to a SIP network with PSTN Fallback ( Link to this Config )
Configuration Description
SmartNode used as gateway between a SIP network
and a phone, connected to port 0/1. The Port 0/0 is configured
as user and can be used as fallback to a PSTN.
Command Sequence to Copy, Edit, and Paste
SN1X00 / SN4552 / SN46XX; Phone Gateway to a SIP network with PSTN Fallback and Emercency call routing ( Link to this Config )
Configuration Description
SmartNode used as gateway between a SIP network and a phone, connected to port 0/1. The Port 0/0 is configured as user and can be used as fallback to a PSTN. Emercency calls will be routed to PSTN instead of VOIP.
SN46X8
R3.20 SIP
Sample configuration
SmartNode connected as trunk gateway between a SIP network
and PBX with 4 S0 port. The Port S0 slot 0 port 0 is configured
as fallback and sync-port. It is configured in the user mode
and should be connected to a PSTN.
The ports slot 0 port 1 to 4 are configured as net and should
be connected to a PBX. Not all the ports have to be connected
The command sequence below enables SmartNode to operate as a DHCP client by pointing a SmartNode IP-interface to a DHCP server on the directly connected LAN. As a DHCP client, upon power-up the SmartNode can automatically retreive an IP address, default gateway address, and DNS server address from the specified DHCP server.
NOTE: Before you point a SmartNode IP-Interface [IF-NAME] to a DHCP server, you must ensure the interface is bound to an Ethernet port.
Command Sequence to Copy, Edit, and Paste
Connect SmartNode to the LAN via static IP addressing with a default gateway address ( Link to this Config )
Configuration Description
The command sequence below enables static-IP-addressing by assigning a fixed IP address, netmask, and default gateway address to a SmartNode IP interface.
To complete this configuration you will need the following information:
The IP-Address and network mask for the SmartNode: [IF-IP], [IF-MASK]
The Gateway address of the default gateway:[GW-IP]
Use the command "show ip route" to display the routing table.
10.10.22.53(ctx-ip)[router]#show ip route
Route Table of IP context 'router':
Validity state (V): * valid, (*) duplicate
Flags: U up, H host, G Gateway, L local, D default
--------------------------------------------------------------
V Destination Nexthop Protocol Metric Flags
--------------------------------------------------------------
* 10.10.22.53/32 loopback local 0 ULH
* 192.168.2.1/32 loopback local 0 ULH
* 127.0.0.1/32 loopback local 0 ULH
* 192.168.2.0/24 eth1 local 1 UL
* 10.10.0.0/16 eth0 local 1 UL
* 127.0.0.0/8 loopback local 1 UL
* 0.0.0.0/0 10.10.1.10 static 0 UDG
(*) 0.0.0.0/0 10.10.1.1 dhcp 12 DG
--------------------------------------------------------------
Sometimes you need to specify default routes for traffic in specific traffic-classes. SmartNodes have three built-in traffic-classes (expendable in configuration) which are used for Quality-of-Service purposes.
For each traffic-class you can configure a default route. If your configure a default-route without mentioning of a traffic-class t is the default route for every untagged traffic.
The command sequence below enables SmartNode to operate as a DHCP server. In networks where the SmartNode is the Internet Gateway Router, this configuration is the best way to provide user devices with Internet access. Once enabled as a DHCP server, The SmartNode can provide a dynamically assigned IP address, DNS Server address, and Default Gateway address to users that are configured as DHCP clients (e.g. PCs, Laptops).
NOTE: You must ensure the network address and the IP addresses in the DHCP server profile match one of the IP interfaces defined in the IP Context.
When you start a DHCP server for the first time you will see the following warning:
2004-12-02T15:56:17 : LOGERROR : Error while loading lease database
This is only a warning does not indicate a problem.
The command sequence below enables SmartNode to support dynamic service via DynDNS (i.e. http://www.dyndns.org). If your IP address changes more often than once every 28 days you should use this Service Dynamic configuration. If your IP address changes less often you should use the Service-Static configuration (shown below on this web page). When in doubt, use static configuration.
NOTE: You must replace the following variables with your site-specific values:
The command sequence below enables SmartNode to support static service via DynDNS (i.e. http://www.dyndns.org). If your IP address changes less often than every 28 days, you should use this Service-Static configuration. If your IP address changes more often, you should use ths Service Dynamic configuration. (shown above, on this web page). When in doubt, use static configuration.
NOTE: You must replace the following variables with your site-specific values:
!Additional license required for Dial-up!
This example configuration can be used as a backup solution, in case a specific host in a specific network is not available anymore. In this case an ISDN Dial-up connection will be set up.
The default route will be removed and the default route with the next higher metric will be used.
This is done by the feature "link supervision" in addition with "dial-up".
As soon as the specified host is available again, the Dial-up connection will be terminated. The traffic will be routed over the regular IP interface as it was initially. The default route with the lower metric is used again.
Relpace:
Z IP-Address WAN-port SmartNode
Y IP-Address Specific host (which needs to be checked)
X IP-Address default Gateway for Network Z
W Username for Dial-up connection
V Password for Dial-up connetion
U Local e164 Number
T Remote e164 Number to dial (ISP)
The following will take calls in the FXO port, and send it out sip.
It will also take calls in SIP and then hunt across all the FXO ports to find a open port
This config also contains the USA tonesets, you can change that as needed for local tones.
Finally, if you choose to use DNS names in the SIP interfaces or in the SIP gateway, you will need to specify a DNS server for any config to work.
Command Sequence to Copy, Edit, and Paste
SmartNode 4552 with SIP-Proxy Sipgate.de and fallback to PSTN ( Link to this Config )
Configuration Description
Configuration for SN4552 with registration to www.sipgate.de
Every national and international long distance call goes to www.sipgate.de.
Every local call goes out to www.sipgate.de.
All emergency calls and special Service Numbers like 110 = police germany, 112 = firebrigade, Health Car germany, 18XX = costable Service numbers are going out directly to local PSTN ISDN interface.
In case of sipgate failure, all sipgate numbers goes as fallback to the local PSTN ISDN Interface.
Replace ‹3015551212› with telephone number
Replace ‹PASSWORD› with Password
Replace ‹SMARTNODE IP = x.x.x.x› with SmartNode IP
Replace ‹GATEWAY IP = x.x.x.x› with Gatway IP
Replace ‹DNS IP = x.x.x.x› with DNS IP
Uncommment lines in SVC-DG-BROADVOICE for ports used
The command sequence below will create a NAPT profile and apply it to the SmartNode's global IP Interface. A home office with the following characteristics will typically use Dynamic NAPT configuration:
- a single global IP address (whether static or dynamic)
- multiple host workstations (PCs, laptops) connected to the home LAN
The command sequence below will create a NAPT profile with port mappings and apply it to the SmartNode's global IP Interface. This configuration allows SmartNode to forward incoming IP connections on specified ports of the global IP Interface to a private host behind NAPT.
NOTE: To determine which ports need to be mapped, please refer to the documentation for the applications you are running behind NAPT.
The command sequence below will create a NAT profile with static address mappings and apply it to an IP interface on the SmartNode. This configuration allows SmartNode to translate IP adresses one-to-one for incoming and outgoing packets. When SmartNode is configured for NAT, the defined port numbers remain unchanged.
Note that he mapped IP addresses must be reachable on their respective interfaces.
Remote should be changed to the IP Address of your Alitgen PBX.
Once you log in with your extension # and password...press 4 for personal options and 8 to enable/disable IP extension.
Port and context ip configuration for a Frame-Relay connection over a V.35 or X21 serial link.
The transmit-data-on-edge setting depends on the remote modem device
Port and context ip configuration for a PPP connection over a V.35 or X21 serial link.
The transmit-data-on-edge setting depends on the remote modem device.
This configuration checks 2 minutes after boot up for new firmware and if available downloads and istalls it. Furthermore the server will be checked every minute for new firmware.
Furthermore SmartNode checks 30 minutes after bootup and then every minute for a new configuration on the specified server. Should a newer configuration be available it will be download, installed and the SmartNode rebooted to activate the new configuration.
Note: Reload takes only effect as long as there is no phone call ongoing.
# Replace all <>-variables with appropriate IP-address or dns-name
Quality-of-Service needs to be configured carefully. Especially the rate-limit values needs to be exact as this is the base for prioritizing the data/voice traffic.
All the values in brackets <> needs to be replaced. Please have a look in the user-guide in order to see what exactly is possible to be configured in this profile...
Note: The voice-margin MUST NOT be configured in the outgoing profile
Command Sequence to Copy, Edit, and Paste
SIP Services and Providers
General example configuration for INBOUND registrations in firmware 5.X ( Link to this Config )
Configuration Description
The firmware 5.X supports the registrar function what allows SmartNode to accept registration from any kind of SIP-clients (telephones, soft-clients).
The example configuration shows how such an so called identity needs to be configured. Please refer to the configuration guide for a complete overview of what is possible. The example below does only show how to configure the SmartNode in order to accept inbound-registrations and how to route a call to such a registered client.
Note: To register more than 3 SIP users, the SIP-registrar license needs to be installed. To get such a license please contact our sales-departement.
Command Sequence to Copy, Edit, and Paste
General example configuration for OUTBOUND registrations and authentication for a SIP trunk firmware 5.X ( Link to this Config )
Configuration Description
This configuration examples may be used in applications, where the gateway has to use the SIP-Username, e.g. root calling number, for registration and outbound authentication but the content of the SIP-From-Header may change;
e.g. root calling number together with the extension.
Command Sequence to Copy, Edit, and Paste
General example configuration for OUTBOUND registrations in firmware 5.X ( Link to this Config )
Configuration Description
This configuration shows an example for how to route calls beetwen an ISDN and SIP network including registration on a SIP server using the new SIP gateway configuration architecture within the SWR5.T software version.
Command Sequence to Copy, Edit, and Paste
General example configuration for SIP-gateway configuration in firmware 3.2x / 4.x ( Link to this Config )
Configuration Description
Below you will find different configuration examples for a SIP-Proxy configuration. The type of the proxy does not matter as the configuration is the same. Please note the configuration is different depending of what firmware you use.
In the examples below there are some variables what need to be adapted to fit into your requirements. The variables and their meaning are:
# Replace ‹x.x.x.x› with IP address of registrar, e.g. 192.168.1.1
# Replace ‹user-account› with account, e.g., 1234
# Replace ‹user-password› with account password, e.g., mysecret
# Replace ‹network-interface› with the corresponding network interface
# Replace ‹interface-type› with fxs or isdn depending of the type of your SmartNode
A Simple Asterisk Registration into PBX T1 on Port 2 0
#
# Replace ‹x.x.x.x› with IP address or dns name of the registrar, e.g. 192.168.1.1
# Replace ‹user-account› with account, e.g., 1234
# Replace ‹user-password› with account password, e.g., mysecret
# Replace < ethernet-interface > with the ethernet interface you use
#
# Example configuration is based on firmware 4.2
A Simple Asterisk Registration into PBX E1 on Port 0 0
#
# Replace ‹x.x.x.x› with IP address or dns name of the registrar, e.g. 192.168.1.1
# Replace ‹user-account› with account, e.g., 1234
# Replace ‹user-password› with account password, e.g., mysecret
# Replace < ethernet-interface > with the ethernet interface you use
#
# Example configuration is based on firmware 4.2 for a SN4960
SNTP configuration recomendation for Australia. This configuration uses a combination of one DNS name in Australia and one IP address in Australia. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
----
# DNS server must come for DHCP or the a specific DNS server configured in the line below (remove the line or change xxx.xxx.xxx.xxx to the IP address of the DNS server.)
dns-client server sntp-client xxx.xxx.xxx.xxx
sntp-client server primary cronos.cenam.mx port 123 version 4
sntp-client server secondary 192.43.244.18 port 123 version 4
sntp-client poll-interval 36000
sntp-client local-clock-offset
sntp-client gmt-offset - 05:00:00
SNTP configuration recomendation for Europe. This configuration uses a combination of one DNS name in Europe and one IP address in Europe. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
SNTP configuration recomendation for Japan. This configuration uses a combination of one DNS name in Japan and one IP address in Japan. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
SNTP configuration recomendation for Mexico. This configuration uses a combination of one DNS name in Mexico and one IP address in USA. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
SNTP configuration recomendation for Russia. This configuration uses a combination of one DNS name in Russia and one IP address in Russia. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
SNTP configuration recomendation for South Africa. This configuration uses a combination of one DNS name in Africa and one IP address in Africa. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
SNTP configuration recomendation for South America. This configuration uses a combination of one DNS name in South Americaand one IP address in South America. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
SNTP configuration recomendation for USA. This configuration uses a combination of one DNS name in the USA and one IP address in USA. DNS server must work work for DNS to be resolved. SNTP should continue to work if DNS breaks or the IP address changes of either SNTP provider.
DD
There are Three distinct tones sets used in Bulgaria.
Bulgaria1, Bulgaria2 & Bulgaria3.
The command sequence below enables SmartNode to provide the standard Norway1 style tone set for dial-tones and call-progress tones.
There are Three distinct tones sets used in Bulgaria.
Bulgaria1, Bulgaria2 & Bulgaria3.
The command sequence below enables SmartNode to provide the standard Norway1 style tone set for dial-tones and call-progress tones.
There are Three distinct tones sets used in Bulgaria.
Bulgaria1, Bulgaria2 & Bulgaria3.
The command sequence below enables SmartNode to provide the standard Norway1 style tone set for dial-tones and call-progress tones.
There are Two distinct tones sets used in Norway.
Norway1 and Norway2.
The command sequence below enables SmartNode to provide the standard Norway1 style tone set for dial-tones and call-progress tones.
There are Two distinct tones sets used in Norway.
Norway1 and Norway2
The command sequence below enables SmartNode to provide the standard Norway2 style tone set for dial-tones and call-progress tones.
The command sequence below defines a VPN Tunnel that uses AES-128 to route traffic from Side #1 (192.168.1.0) to Side #2 (192.168.2.0).
NOTE:
-You must replace ‹X.X.X.X› in the template with the IP address for Side #2.
-You must replace ‹MySharedKey› in the template with text string as the initial shared key
-You must replace ‹nnnn› in the template with unique number from 1-99999 like 12345
-You must purchase the appropriate software license for your SmartNode to support VPN service. To see the current licenses active for your SmartNode, execute the "show license" command.
The command sequence below defines a VPN Tunnel that uses AES-128 to route traffic from Side #2 (192.168.4.0) to Side #1 (192.168.1.0).
NOTE:
-You must replace ‹X.X.X.X› in the template with the IP address for Side #2.
-You must replace ‹MySharedKey› in the template with text string as the initial shared key
-You must replace ‹nnnn› in the template with unique number from 1-99999 like 12345
-You must purchase the appropriate software license for your SmartNode to support VPN service. To see the current licenses active for your SmartNode, execute the "show license" command.
The command sequence below defines a VPN Tunnel that uses DES to route traffic from Side #1 (192.168.1.0) to Side #2 (192.168.2.0).
NOTE: You must replace X.X.X.X in the template with the IP address for Side #2.
NOTE: You must purchase the appropriate software license for your SmartNode to support VPN service. To see the current licenses active for your SmartNode, execute the "show license" command.
The command sequence below defines a VPN Tunnel that uses DES to route traffic from Side #2 (192.168.2.0) to Side #1 (192.168.1.0).
NOTE: You must replace X.X.X.X in the template with the IP address for Side #1.
NOTE: You must purchase the appropriate software license for your SmartNode to support VPN service. To see the current licenses active for your SmartNode, execute the "show license" command.