This incidence shows a SIP message flow, where 200 OK and ACK are sent back and forth several times.

context cs switch

         routing-table called-e164 RT_IN

                  route .T2 dest-interface IF_SIP
                  route T!2 dest-interface IF_SIP MAP_NR

         routing-table called-e164 RT_OUT

                  route .T2 dest-service HG_ISDN

         mapping-table called-e164 to called-e164 MAP_NR

                  map default to 0

         interface isdn IF_BRI_01

                  route call dest-table RT_IN
                  address-complete-indication accept clear

routing-table called-e164 OUT

       route 1234 dest-interface IF_BRI_03
       route 123 dest-interface IF_SIP

To avoid this, following can be set to succeed the entry for 123.

routing-table called-e164 OUT

       route 1234 dest-interface IF_BRI_03
       route 123T!0 dest-interface IF_SIP

Adding the T!0 forces the entry 123, although there is another entry which incompletely matches. 

Example:

service distribution-group SER_DIST_ISDN
cyclic
max-concurrent 1
route call 1 dest-interface "interface-name"
route call 2 dest-interface "interface-name"

DHCP Option

 Name

 Description

1

 Subnet Mask 

 Specifies the clients subnet mask 

3

 Router 

 Specifies a list of routers for the clients subnet 

6

 Domain Name Server 

 Specifies a list of Doman Name servers 

12

 Host Name 

 Specifies the name of the client 

15

 Domain Name 

 Specifies te domain name to be used when resolving hostnames 

50

 DHCP Requested IP Address 

 Used if the client requests a particular IP address to be assigned 

51

 DHCP IP Address Lease Time 

 Specifies the lease time for the IP address in seconds 

52

 DHCP Option Overlaod 

 Specifies if the 'file' and/or 'sname' fields are used for DHCP options 

53

 DHCP Message Type 

 Specifies the type of the DHCP message 

54

 DHCP Server Identifier 

 Identifies a particular DHCP server, thus the client can distinguish multiple DHCP servers 

55

 DHCP Parameter Request List 

 Used if the DHCP client requests values for specifeid configuration parameters 

56

 DHCP Message 

 Used to provide an error message 

57

 DHCP Maximum DHCP Message Size 

 Specifies the maximum length DHCP message it is willing to accept 

58

 DHCP Renewal (T1) Time Value 

 Specifies the time interval until the client goes to the RENEWING state 

59

 DHCP Rebinding (T2) Time Value 

 Specifies the time interval until the client goes to the REBINDING state 

60

 DHCP Vendor Class Identifier 

 Used to transport vendor specific information 

61

 DHCP Client-identifier 

 The unique identifier of a client, thus the server can distinguish multiple DHCP clients 

66

 DHCP TFTP Server Name 

 Specifies the TFTP server name when the 'sname' field has been used for DHCP options 

67

 DHCP Bootfile Name 

 Specifies the bootfile when the 'file' field has been used for DHCP options 

1. Connect to the SmartNode using the console cable.
2. Cycle the power
3. At the prompt "Press ^C to abort boot script, press enter to start immediately" press ctrl and c.
4. Type in the command 'fis load'
5. Type in the command 'go -s factory-config'

 In installations where a PBX is connected to the PSTN and to a SmartNode ISDN VoIP Gateway at the same time, synchronization problems can occure. The problem exists beacuse the PBX expects a synchronous clock on all trunk lines. The SmartNode ISDN VoIP Gateway however can only deliver a synchronous clock if it is connected to a reference network/clock. If this is not the case the SmartNode clock and the PSTN clock will not be synchronous leading to bit slips between different trunk lines of the PBX. These slips do not cause problems with voice calls, however fax and modem calls are impaired.

- The only universally applicable solution to this problem is to have one SmartNode BRI (or PRI) port connected to a reference clock . This solution will work with every PBX. The reference clock may come from an internal S-Bus on the PBX or from a PSTN connection

- In the case of one BRI port used for Voice, Fax and Modem over IP, many SmartNode models provide an extra BRI port for this refclock connection. E.g. the SN4552 and SN4630 series.

- If more then 4 active BRI ports are required, the solution can be provided with the SN2400 and 1-4 IC-4BRV interface cards.

- With some PBXs a reconfiguration of the trunk ports is possible that allows to deliver the ref clock to the SmartNode over the trunk line (PBX port Layer3 Usr (TE) but Layer 2 clock-master). This requires a reconfiguration of the PBX which is not possible on all PBX systems.

FXS is what is most commonly known as Plain Old Telephone Service (POTS). It is what your local phone company delivers to your home on a twisted pair. In other words, FXS looks a line from the telephone company switch (PSTN); it hooks to a telephone.

FXS interfaces provide to the subscriber:

• Battery current and ring voltage
• Dial tone (knows when to give dial-tome (seizure) when it sees current flowing from an FXO port closure.
• Optional: CallerID (both caller number and name)
• Optional: Call Waiting / Call Waiting ID
• Optional: Message waiting indicator

FXS interfaces receive:

• Hook Flash (to be notified of features, e.g, to set-up a three-way conference call or toggle between two incoming calls)
• DTMF (touch tones)

FXS "alterts" an incoming call by:

• Presenting ringing voltage to the line (attached device) – just like a PBX it does not and cannot pass any dialed digits.

• Loop closure - Identifying that the line has been seized by the attached telephone going off hook. It can then receiving dialed digits (via DTMF).

FXO Information

Your telephone is an FXO device and it connects to the FXS of the telephone company. Your phone provides on-hook/off-hook indication (loop closure) to the phone company. This is why you get a dial-tone when you pick up the phone.

FXO interfaces provide:

• onhook/off-hook indication (loop closure)
• HookFlash (to request features of PBX or PSTN, e.g., three-way conference calling) A quick loop closure or wink which is about a quarter of a second.
• DTMF (touch tones)

FXO interfaces receive:

• Dial tone as an indication from the FXS port that it achknowldeges the loop-closure.
• Optional: Ring indication (voltage to ring the phone)
• Optional: CallerID (both caller number and caller name)
• Optional: Call Waiting Indicator (tone indicating a second incoming call)
• Optional: Call Waiting ID (Caller ID of second incoming call)
• Optional: Message waiting indicator (blinking light to indicate voice mail)

FXO makes a call by:

• Seizing the telephone line (going off hook)
• Dialing DTMF digits to identify the destination to call
• Hanging up at the end of the call

• Identifying when ringing voltage is being supplied by the PBX / CO switch (ringing the telephone)
• Answers the call by “going off hook”. Call is then connected.

• A standard analog (plain old telephone) is FXO
• PBX/Switch lines from a PBX (that drive current) that you plug analog phones into are FXS
• The PBX analog ports lines that plug into the CO are FXO
• The SmartNode 4110 Analog VoIP Media Gateway provides up to eight FXS or FXO ports

- An external encryption tool on the PC is used to encrypt the configuration file:

enctool encrypt <plain-config-file> <enc-config-file> [<key>]

- The encrypted confiugration file can then be downloaded with TFTP triggered by

- the CLI copy command:

copy tftp://<host>/<path> <config-file>

- Auto Provisioning

- SNMP

- HTTP

- On the SmartNode the encryption is detected and the configuration file is automatically decrypted
before stored to flash.

- A custom encryption key can be

- downloaded to the SmartWare

- specified with the PC encryption tool

- The encryption key may include the MAC address and/or serial number of the SmartNode using the
placeholders $(system.mac) and $(system.serial) resp.

- An encrypted configuration file can be uploaded to a TFTP server on request, specifying the encrypted
flag:

copy <config-file> tftp://<host>/<path> encrypted

- On the PC the encryption tool can be used to decrypt the file:

enctool decrypt <enc-config-file> <plain-config-file> [<key>]

- A log file lists the last up/downloads:

how log file-transfer

Use Cases

Install a custom encryption key (optional)

You can install a custom encryption key with the SmartNode. The encryption key is used to automatically

decrypt an encrypted configuration file that is downloaded later. A default encryption key is already

installed on the SmartNode.

To install an encryption key you have to create a file on your TFTP server that contains the key. Then you
have to download this key file to the SmartNode using the ‘copy’ command of the SmartNode:

The key file shall contain a key string of at most 24 characters on a single line. Spaces, tabs and LF/CR
characters are trimmed.

The key must not contain LF/CR or the null character and must not start or end
with a space or tab. If the key contains more than 24 characters, only the first 24 characters are
considered.

Part Nr. 80-0165, Rev. 1.13 12-07-05 49/54

The key may contain variables that are resolved when the key file is downloaded to a SmartNode. Using

this mechanism you can specify device-specific encryption keys. We currently support the following
variables:

- $(system.mac): The MAC address of the first ethernet port. Execute the show port ethernet

command on a SmartNode to display the MAC address of a SmartNode. This value without the colon

separators and with all lower-case hexadecimal letters is used instad of the variable on the SmartNode.

- $(system.serial): The serial number of the SmartNode. Execte the show version command on
the SmartNode to display the serial number.

When your key file contains the following line…

123$(system.serial)abc$(system.mac)XYZ

show port ethernet shows the following…

Ethernet Configuration
-------------------------------------
Port : ethernet 0 0 0

State : OPENED

MAC Address : 00:0C:F1:87:D9:09

Speed : 10MBit/s

Duplex : Half

Encapsulation : ip

Binding : interface eth0 router

and show version the following….

Productname : SN1200

Software Version : R3.20 TB2005-06-24_MEYER SIP

Supplier :

Provider :

Subscriber :

Information for Slot 0:

SN1200

Hardware Version : 0004, 0001

Serial number : 100000020002

Software Version : R3.20 TB2005-06-24_MEYER SIP

the encryption key on this SmartNode will be interpreted as…

123100000020002abc000cf187d909XYZ

Then you have to download the created key file to the SmartNode. Open a telnet session and type in the

following commands:  

>enable

#copy tftp://<ip>/<path> key:

where <ip> is the IP address of your TFTP server and <path> is the path to the key file relative to the

TFTP root.  

Encrypt a configuration file

Use the encryption tool to encrypt a configuration file on your PC. Therefore you have to enter the

following command.  

enctool encrypt <plain-file> <encrypted-file> [<key>]

where <plain-file> is the path of the non-encrypted input configuration file and <encrypted-file> is the path

of the encrypted output configuration file. <key> specifies the encryption key which shall be used to

encrypt the configuration file. If ommitted the default key is used.  

Download an encrypted configuration file

Now you can download the configuration file as usual using the CLI copy-command, the autoprovisioning

feature, HTTP or SNMP download. The SmartNode automatically detects that a downloaded

file is encrypted and tries to decrypt the file using the pre-installed key.  

Upload an encrypted configuration file

The SmartNode immediately decrypts a configuration file after downloading it. This is the configuration

file is stored non-encrypted in the flash memory. Thus when you upload a configuration it is uploaded
non-encrypted.

You may upload an encrypted configuration file specifying the encrypted flag at the end of the copy
command:  

#copy startup-config tftp://<ip>/<path> encrpted

This encrypts the configuration file before sending it to the TFTP server. Use the enctool decrypt

command on the PC to regain the original configuration.  

File Transfer Logs

We introduced an additional log file that stores the history of all file transfers (up to 50 entries). To show

all recently executed file transfer operations enter the following command:  

#show log file-transfer
 

If a firmware update fails, or the reset button is held for more than 5 seconds, the SmartNode will enter the redboot mode. Connect a computer to the console interface and restart the SmartNode. You will see the Prompt "RedBoot".  Follow the steps below to restore your SmartNode.

Method 1:

From the console interface, enter these commands.

• RedBoot> fis load
• RedBoot> go -s factory-config

Method 2: 

• Reset and how to access the bootloader/redboot Restart the unit with the current startup configuration—Press (for less than 1 second) and release the Reset button to restart the unit with the current startup configuration.
  • The reset button has three functions:
• Restart the unit with factory default configuration—Press the Reset button for 5 seconds until the Power LED starts blinking to restart the unit with factory default configuration.
• Restart the unit in bootloader mode (to be used only by trained SmartNode technicians)— Starting with the unit powered off, press and hold the Reset button as you apply power to the unit. Release the Reset button when the Power LED starts blinking so the unit will enter bootloader mode.
• Download the required .bin file at:
  • Image for SN4552; SN4554; SN4562; S-DTA
  • Image for SN4120; SN-DTA
  • Image for SN4xxx_FXS_FXO
  • Image for SN4xxx_BRI
  • Image for SN4830 FXS_FXO
  • Image for SN4960; SN4940; SN4950 and SN5400
  • Image for SN5200

** Default IP Address WAN port 172.16.40.1 netmask 255.255.0.0 for SmartNodes without console port **

** Some SmartNode devices, such as the SN4112s, use port 9000 for Telnet instead of port 23 **

• Type in 'fis list'
• If there is an entry type 'fis delete -n 1'

Optional:

• Set the IP address using
  • 'ip_address -l (ip-address)/(masklength) -g (gateway-address)'
• Load the new firmware
  • For the SN4xxx / SN-DTA Series (SN4110, SN4520, SN4120, SN-DTA, SN4600, SN4960)
    'load -r -b 0x1800100 -h (ip-address) /image.bin' 
  • For the SN4552, SN4554, SN4562, S-DTA
    'load -r -b 0xc00100 -h (ip-address) /image.bin'

** Replace (ip-address) with the ip-address of your tftp-server. **

• Program the firmware into the flash with the command 'fis create' when prompted type 'yes'
• Load the new firmware with 'fis load'
• Restart the smartnode with 'go'

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.

Command Sequence to copy, edit and paste

# 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 ntp.saard.net port 123 version 4
sntp-client server secondary 203.21.84.4 port 123 version 4
sntp-client poll-interval 36000
sntp-client local-clock-offset
sntp-client gmt-offset + 11:00:00

Command Sequence to copy, edit and paste

# 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 swisstime.ethz.ch port 123 version 4
sntp-client server secondary 192.36.143.150 port 123 version 4
sntp-client poll-interval 36000
sntp-client local-clock-offset

Commande Sequence to copy, edit and paste

# 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 ntp.psn.ru port 123 version 4
sntp-client server secondary 193.233.46.10 port 123 version 4
sntp-client poll-interval 36000
sntp-client local-clock-offset
sntp-client gmt-offset + 03:00:00

Commande Sequence to copy, edit and paste

# DNS server must come for DHCP or the a specific sntp-client server primary ntp.is.co.za port 123 version 4
sntp-client server secondary 146.64.241.228 port 123 version 4
sntp-client anycast-address 224.0.1.1 port 123
sntp-client poll-interval 36000
sntp-client local-clock-offset
sntp-client gmt-offset + 02:00:00

Commande Sequence to copy, edit and paste

# 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 ntp.linux.org.ve port 123 version 4
sntp-client server secondary 200.144.121.33 port 123 version 4
sntp-client poll-interval 36000
sntp-client local-clock-offset
sntp-client gmt-offset - 02:00:00

Command Sequence to copy, edit and paste

# 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 pool.ntp.org port 123 version 4
sntp-client server secondary 88.198.124.92 port 123 version 4
sntp-client poll-interval 36000
sntp-client local-clock-offset
sntp-client gmt-offset - 05:00:00

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.

Command Sequence to copy, edit and paste

profile ipsec-transform DES
esp-encryption des-cbc 64

profile ipsec-policy-manual VPN_DES
use profile ipsec-transform DES
session-key inbound esp-encryption A242353012531297
session-key outbound esp-encryption B242353012531297
spi inbound esp 1111
spi outbound esp 2222

# SET IP ADDRESS of SIDE #2
peer X.X.X.X
mode tunnel

profile acl VPN_Out
permit ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255 ipsec-policy VPN_DES
permit ip any any

profile acl VPN_In
permit esp any any
permit ah any any
permit ip 192.168.2.0 0.0.255.255 192.168.1.0 0.0.0.255
permit ip any any

context ip
interface eth0
use profile acl VPN_In in
use profile acl VPN_Out out

context ip router
route 192.168.2.0 255.255.255.0 eth0

Command Sequence to copy, edit and paste

profile ipsec-transform DES
esp-encryption des-cbc 64

profile ipsec-policy-manual VPN_DES
use profile ipsec-transform DES
session-key inbound esp-encryption B242353012531297
session-key outbound esp-encryption A242353012531297
spi inbound esp 2222
spi outbound esp 1111

# SET IP ADDRESS of SIDE #1
peer X.X.X.X
mode tunnel

profile acl VPN_Out
permit ip 192.168.2.0 0.0.0.255 192.168.1.0 0.0.0.255 ipsec-policy VPN_DES
permit ip any any

profile acl VPN_In
permit esp any any
permit ah any any
permit ip 192.168.1.0 0.0.255.255 192.168.2.0 0.0.0.255
permit ip any any

context ip
interface eth0
use profile acl VPN_In in
use profile acl VPN_Out out

context ip router
route 192.168.1.0 255.255.255.0 eth0

Definitions:

SIP Leg                         A SIP Leg covers a SIP Signalling connection between two devices                                   
SIP Session                   A SIP Session covers a back-to-back call through the ESBR / SmartNode using two SIP legs                                   
Voice Channel                DSP resources for 1 bi-directional VoIP call                                   
Transcoding Channel      1 Transcoding Channel = 2 Voice Channels

SmartNode model descriptions (SKU):

V        VoIP channel - DSP resources for 1 bi-directional VoIP call                                       
B        SIP Session or back-to-back call using 2 SIP legs                                       
P        Transcoding channel - equivalent to 2 VoIP channels with Transcoding enabled  

SN4960 / SN4940 / SN4950

• Number of supported SIP Sessions = Number of VOIP channels (V) + 6 SIP Legs /2
  • Example: SN4960/4E60V --> 60V+6 /2 = 33 SIP Sessions

SN4970 / SN4980 / SN4990

• With transcoding license: Number of supported SIP Sessions = Number of VOIP channels (V) x 3 /2
  • Example: SN4970/1E30V --> 30V x 3 /2 = 45 SIP Sessions
• Without transcoding license: Number of supported SIP to SIP calls = Number of VOIP channels (V) x 1.5 /2
  • Example: SN4991/4E120V --> 120V x 1.5 /2 = 90 SIP Sessions

SN4110, SN4120, SN4520, SN4830, SN4300, SN4400, SN4900, S-DTA, SN-DTA, SN4630, SN4650

• 16 Number of supported SIP Sessions (no transcoding is supported)

SN466X, SN467X

• 16 Number of supported SIP Sessions
• DSP channel /2 = supported transcoded channels

SN5200/ SN5221/ SN5400 / SN5480 / SN5490

• See the model description for more details --> Link

Example:

The total amount of SIP sessions includes the 16 transcoded calls. With the following licenses

SNSW-54P1    the number of transcoded calls can be increased
SNSW-4B       the number of SIP Sessions can be increased

If a firmware update fails the SmartNode will enter the u-boot mode. Connect a computer to the console interface and restart the SmartNode. You will see the Prompt "=>".

How to force the SmartNode entering the bootloader/u-boot mode

While connected with your computer to the console interface, perform a restart of the SmartNode. The following will appear on the console
Hit any key to stop autoboot:
When doing so, the boot process will be aborted and the SmartNode remains in u-boot mode. 

From u-boot mode a firmware upgrade or firmware recovery, is done as per the following instructions.
First of all the image file you may download and store in a folder of your TFTP server.

• Download the required .bin file at

• Image for SN4660 and SN4670

• Image for SN4970, SN4980, SN4990 and SN5480 / SN5490

1. Set the IP of the SmartNode: setenv ipaddr <device ip address>
2. Set the netmask for the SmartNode: setenv netmask <device netmask>
3. Set the TFTP server IP: setenv serverip <tftp server ip address>
4. Specify the right folder of your TFTP server where the image file is located: setenv tftproot <path>
   The SmartNode will automatically select the image.bin 
5. Type in: run getimage
   wait for the image to be downloaded
   
6. Type in: reset

Now the SmartNode will perform a reboot. Afterwards it will boot up with the regular firmware.

How to force the SmartNode entering the bootloader/u-boot mode

While connected with your computer to the console interface, perform a restart of the SmartNode. The following will appear on the console
Hit any key to stop autoboot:
When doing so, the boot process will be aborted and the SmartNode remains in u-boot mode. 

• Download the required .bin file at

• Image for SN4660 and SN4670

• Image for SN4970, SN4980 and SN4990

1. Erase the potentially stored evironment variables from u-boot, to get the default behavior:

1. Set the IP of the SmartNode: setenv ipaddr <device ip address>
2. Set the netmask for the SmartNode: setenv netmask <device netmask>
3. Set the TFTP server IP: setenv serverip <tftp server ip address>
4. Specify the right folder of your TFTP server where the image file is located: setenv tftproot <path>
   The SmartNode will automatically select the image.bin 
5. Type in: run getimage
   wait for the image to be downloaded
   
6. Type in: reset

Now the SmartNode will perform a reboot. Afterwards it will boot up with the regular firmware.

This example includes a basic configuration for the SmartNode SN411X/FXS to be used as an FXS gateway in combination with a Cisco Call Manager. The configuration contains variables in brackets <>. Please Replace the variables including the brackets. Unused lines or variables have to be commented out or deleted

This cofiguration note gives an overview about configuring the SN411x with Cisco Unified Communications Manager (CUCM).

G723 and G729
 

On some of the SmartNodes, only one low bitrate codec is supported at the time, systemwide.
There the following setting is required to make the G729 codec work.

By default the G723 codec is systemwide enabled.

The following SmartNodes DO NOT require this setting, since they can handle both low bitrate codec at the same time in the system.

SN4940 / SN4950 / SN4960
SN4970 / SN4980 / SN4990
SN4660 / SN4670
SN4120/2V
SN-DTA/2V

Gateway/Routers will also route between two dissimilar network types, but they also regulate traffic between similar networks, in this case the TCP/IP network.  These devices will need to have at least two Ethernet ports so that the IP traffic can be routed from one network to another.

Most companies already have a router in place for the IP traffic, so they will need only the Gateway feature to convert their old Telephony equipment to IP (SIP) and vice versa.

http://www.3cx.com/blog/voip-howto/patton-fxs-gateway-at/



To configure a Trinity SmartNode FXS Gateway within 3CX, please visit the link below.

https://www.patton.com/support/kb_art.asp?art=478&p=0

This example includes a basic configuration for the SmartNode SN4118/JS to be used as a FXS gateway in combination with two Cisco Call Manager. The configuration contains variables in brackets <>. Please Replace the variables including the brackets. Unused lines or variables have to be commented out or deleted

This configuration note gives an overview about configuring the SN4118/JS with Cisco Unified Communications Manager (CUCM).

Commande Sequence to copy, edit and paste

#----------------------------------------------------------------#
# #
# SN4118/JS/EUI #
# R6.X #
# Handmade configuration file #
# #
# Cisco Call Manager #
# #
# This example includes a basic configuration for the SmartNode #
# SN4118/JS in combination with two Cisco Call Manager with #
# SIP authentication and registration. #
# This example can be used for other SmartNodes too. The only #
# thing which needs to be adjusted, are the ports and interfaces #
# as far as required. #
# #
# Author: Thomas Tlapak #
# Patton-Inalp Neworks #
# CH-3172 Niederwangen #
# www.patton.com; support@patton.com #
# #
# Date: 11/06/2014 #
# #
#----------------------------------------------------------------#

cli version 3.20
clock local default-offset +00:00
timer PROVISIONING now + 3 minutes "provisioning execute PF_PROVISIONING_CONFIG"
webserver port 80 language en
sntp-client
sntp-client server primary pool.ntp.org port 123 version 4

system

ic voice 0
low-bitrate-codec g729

profile ppp default

profile tone-set default

profile voip default
codec 1 g711alaw64k rx-length 20 tx-length 20
codec 2 g711ulaw64k rx-length 20 tx-length 20

profile pstn default

profile ringing-cadence default
play 1 1000
pause 2 4000

profile sip default
no autonomous-transitioning

profile aaa default
method 1 local
method 2 none

profile provisioning PF_PROVISIONING_CONFIG
destination configuration
location 1 http://redirect.patton.com/$(system.mac);mac=$(system.mac);serial=$(system.serial);hwMajor=$(system.hw.major);hwMinor=$(system.hw.minor);swMajor=$(system.sw.major);swMinor=$(system.sw.minor);swDate=$(system.sw.date);productName=$(system.product.name);cliMajor=$(cli.major);cliMinor=$(cli.minor);osName=$(cli.major>=4|Trinity|SmartWare);subDirTrinity=$(cli.major>=4|/Trinity);subDirSmartWare=$(cli.major<4|/SmartWare);dhcp66=$(dhcp.66);dhcp67=$(dhcp.67)
location 2 $(dhcp.66)
location 3 $(dhcp.66)/$(system.mac).cfg
location 4 http://$(dhcp.66)/$(dhcp.67)
location 5 http://$(dhcp.66)/$(system.mac).cfg
location 6 tftp://$(dhcp.66)/$(dhcp.67)
location 7 tftp://$(dhcp.66)/$(system.mac).cfg
activation reload immediate

context ip router

interface eth0
ipaddress dhcp
tcp adjust-mss rx mtu
tcp adjust-mss tx mtu

context ip router

context cs switch

routing-table called-e164 RT_TO_SIP_00
route .T dest-interface IF_SIP

routing-table called-e164 RT_TO_SIP_01
route .T dest-interface IF_SIP_01

routing-table called-e164 RT_TO_SIP_02
route .T dest-interface IF_SIP_02

routing-table called-e164 RT_TO_SIP_03
route .T dest-interface IF_SIP_03

routing-table called-e164 RT_TO_SIP_04
route .T dest-interface IF_SIP_04

routing-table called-e164 RT_TO_SIP_05
route .T dest-interface IF_SIP_05

routing-table called-e164 RT_TO_SIP_06
route .T dest-interface IF_SIP_06

routing-table called-e164 RT_TO_SIP_07
route .T dest-interface IF_SIP_07

routing-table called-e164 RT_TO_FXS
route <username 2> dest-interface IF_FXS_01
route <username 3> dest-interface IF_FXS_02
route <username 4> dest-interface IF_FXS_03
route <username 5> dest-interface IF_FXS_04
route <username 6> dest-interface IF_FXS_05
route <username 7> dest-interface IF_FXS_06
route <username 8> dest-interface IF_FXS_07
route <username 1> dest-interface IF_FXS_00

interface sip IF_SIP
bind context sip-gateway GW_SIP_00
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface sip IF_SIP_01
bind context sip-gateway GW_SIP_01
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface sip IF_SIP_02
bind context sip-gateway GW_SIP_02
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface sip IF_SIP_03
bind context sip-gateway GW_SIP_03
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface sip IF_SIP_04
bind context sip-gateway GW_SIP_04
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface sip IF_SIP_05
bind context sip-gateway GW_SIP_05
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface sip IF_SIP_06
bind context sip-gateway GW_SIP_06
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface sip IF_SIP_07
bind context sip-gateway GW_SIP_07
route call dest-table RT_TO_FXS
remote <IP of the callmanager>
local <IP of the callmanager>

interface fxs IF_FXS_00
route call dest-table RT_TO_SIP_00
subscriber-number <username 1>

interface fxs IF_FXS_01
route call dest-table RT_TO_SIP_01
subscriber-number <username 2>

interface fxs IF_FXS_02
route call dest-table RT_TO_SIP_02
subscriber-number <username 3>

interface fxs IF_FXS_03
route call dest-table RT_TO_SIP_03
subscriber-number <username 4>

interface fxs IF_FXS_04
route call dest-table RT_TO_SIP_04
subscriber-number <username 5>

interface fxs IF_FXS_05
route call dest-table RT_TO_SIP_05
subscriber-number <username 6>

interface fxs IF_FXS_06
route call dest-table RT_TO_SIP_06
subscriber-number <username 7>

interface fxs IF_FXS_07
route call dest-table RT_TO_SIP_07
subscriber-number <username 8>

context cs switch
no shutdown

authentication-service AUTH_SRV_00
username <username 1> password <password>

authentication-service AUTH_SRV_01
username <username 2> password <password>

authentication-service AUTH_SRV_02
username <username 3> password <password>

authentication-service AUTH_SRV_03
username <username 4> password <password>

authentication-service AUTH_SRV_04
username <username 5> password <password>

authentication-service AUTH_SRV_05
username <username 6> password <password>

authentication-service AUTH_SRV_06
username <username 7> password <password>

authentication-service AUTH_SRV_07
username <username 8> password <password>

location-service LOC_SRV_00
domain 1 <IP of the callmanager> 5060

identity-group default
identity <username 1>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_00 username <username 1>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

location-service LOC_SRV_01
domain 1 <IP of the callmanager> 5060

identity <username 2>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_01 username <username 2>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

location-service LOC_SRV_02
domain 1 <IP of the callmanager> 5060

identity <username 3>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_02 username <username 3>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

location-service LOC_SRV_03
domain 1 <IP of the callmanager> 5060

identity <username 4>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_03 username <username 4>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

location-service LOC_SRV_04
domain 1 <IP of the callmanager> 5060

identity <username 5>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_04 username <username 5>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

location-service LOC_SRV_05
domain 1 <IP of the callmanager> 5060

identity <username 6>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_05 username <username 6>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

location-service LOC_SRV_06
domain 1 <IP of the callmanager> 5060

identity <username 7>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_06 username <username 7>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

location-service LOC_SRV_07
domain 1 <IP of the callmanager> 5060

identity <username 8>

authentication outbound
authenticate 1 authentication-service AUTH_SRV_07 username <username 8>

registration outbound
registrar <IP of the callmanager>
lifetime 300
register auto
retry-timeout on-system-error 10
retry-timeout on-client-error 10
retry-timeout on-server-error 10

context sip-gateway GW_SIP_00

interface IF_GW_SIP
bind interface eth0 context router port 5060

context sip-gateway GW_SIP_00
bind location-service LOC_SRV_00
no shutdown

context sip-gateway GW_SIP_01

interface IF_GW_SIP_5061
bind interface eth0 context router port 5061

context sip-gateway GW_SIP_01
bind location-service LOC_SRV_01
no shutdown

context sip-gateway GW_SIP_02

interface IF_GW_SIP_5062
bind interface eth0 context router port 5062

context sip-gateway GW_SIP_02
bind location-service LOC_SRV_02
no shutdown

context sip-gateway GW_SIP_03

interface IF_GW_SIP_5063
bind interface eth0 context router port 5063

context sip-gateway GW_SIP_03
bind location-service LOC_SRV_03
no shutdown

context sip-gateway GW_SIP_04

interface IF_GW_SIP_5064
bind interface eth0 context router port 5064

context sip-gateway GW_SIP_04
bind location-service LOC_SRV_04
no shutdown

context sip-gateway GW_SIP_05

interface IF_GW_SIP_5065
bind interface eth0 context router port 5065

context sip-gateway GW_SIP_05
bind location-service LOC_SRV_05
no shutdown

context sip-gateway GW_SIP_06

interface IF_GW_SIP_5066
bind interface eth0 context router port 5066

context sip-gateway GW_SIP_06
bind location-service LOC_SRV_06
no shutdown

context sip-gateway GW_SIP_07

interface IF_GW_SIP_5067
bind interface eth0 context router port 5067

context sip-gateway GW_SIP_07
bind location-service LOC_SRV_07
no shutdown

port ethernet 0 0
medium auto
encapsulation ip
bind interface eth0 router
no shutdown

port fxs 0 0
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_00 switch
no shutdown

port fxs 0 1
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_01 switch
no shutdown

port fxs 0 2
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_02 switch
no shutdown

port fxs 0 3
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_03 switch
no shutdown

port fxs 0 4
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_04 switch
no shutdown

port fxs 0 5
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_05 switch
no shutdown

port fxs 0 6
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_06 switch
no shutdown

port fxs 0 7
use profile fxs us
encapsulation cc-fxs
bind interface IF_FXS_07 switch
no shutdown

The WEB Wizard file can be downloaded from the following LINK.

For more details about the WEB Wizard, please see the WEB Wizard Documentation / Programmers Guide.

The command sequence below enables SmartNode to provide the Austria 450Hz style tone set for dial-tones and call-progress tones.

Command Sequence to copy, edit and paste

profile call-progress-tone AUT450_Dialtone
  play 5000 450 -12 450 -12

profile call-progress-tone AUT450_Alertingtone
  play 1000 450 -12
  pause 5000

profile call-progress-tone AUT450_Busytone
  play 300 450 0
  pause 300
 
profile tone-set default
  map call-progress-tone dial-tone AUT450_Dialtone
  map call-progress-tone ringback-tone AUT450_Alertingtone
  map call-progress-tone busy-tone AUT450_Busytone
  map call-progress-tone release-tone AUT450_Busytone
  map call-progress-tone congestion-tone AUT450_Busytone

Smartnode platform:
On the Web GUI, under your SIP interface; select "Address-translation outgoing-call" and on the first row (TO) enter in the DID(User-part) and hit apply

On the CLI:

enable

configure 

context cs

interface sip <Your SIP interface name>

address-translation outgoing-call to-header user-part fix <Your DID>

To understand why Patton received a recent Product of the Year Award for these models, and to see where YOU might want to use them (keywords: DECT and fax), let‘s start with a little background in telecom network clocking.

In normal ISDN telephony networks, the public network ("Amt") provides an 8kHz clock signal to all connected equipment. This clock is ultra-stable and precise, as it derives from an atomic master clock.

In the picture above, the entire PBX system is clocked from the atomic master clock. Now, there is a little think we have to know: For SME PBX systems with integrated DECT base station, it happens to be best practice to use the ISDN clock and derive the DECT base frequency from it. This way, PBX manufacturers save in cost - they don‘t have to include in their system an expensive frequency generator for the DECT base frequency.

So what happens when an enterprise moves to VoIP? You got it. A SmartNode VoIP gateway replaces the ISDN line. Now, the SmartNode provides clock to the PBX - and thus, the DECT base frequency is derived from the SmartNode‘s internal clock:

Is this an issue? Yes it is. VoIP gateway‘s clocks are standardized to an accuracy of 50ppm. This is way enough to allow for best-quality voice conversations. But it‘s not enough to be used as source to generate a DECT base frequency. The resulting DECT frequency is not precise enough, resulting in the handset not being able to register to the base station.

Patton enables you to solve this problem in two ways:

       1)  Through the most flexible clocking configuration in the industry on SmartNodes, it is possible to select any ISDN port as clock source. The clock from the clock source is then distributed to all other ISDN ports. Thus it is possible to either keep one public ISDN line as clock master, or to feed a clock signal from another source to the SmartNode.   

       2)  Through use of the new high precision models it is possible to increase the SmartNode internal clock accuracy to Stratum 3. This is very precise and way enough to serve as source for the DECT frequency.

Here is an overview of the SmartNode models that are available with high precision clock:

 Compared to high precision solutions from other vendors, which are modular based systems, SmartNode‘s integrated system design offers a very cost effective solution. 

• Selects the best matching entry
• Sets/Changes the value of the defined Information Element
• Mapping tables together with regular expressions are more powerful

Mapping-Table Types:





Creating/Entering and changing a Mapping-Table:

To do this, you must be in the 'context cs' section of the configuration.

(ctx-cs)# mapping-table <input-type> to <output-type> <name>
(map-tab)[MAP]#map <input-value> to <output-value>



Sample Mapping-Tables:

mapping-table called-e164 to called-e164 REM_PREFIX_911
map .(.%) to \1

ex.  If you have to dial a 9 to get an outside line
9911 converts to 911 
(Helps comply with the newly enacted 'Keri's Law')


mapping-table calling-e164 to calling-e164 ADD_00
map (.%) to 00\1

ex.  If you want to have a prefix added to every number dialed (For accounting purposes, least call routing, etc...)
3019751000 gets mapped to 003019751000


mapping-table called-e164 to calling-pi CNPN_PI
map *31*(.%) to restricted

ex.  If you need to change the presentation for Privacy reasons
When *31*1234567 is dialed, the Presentation Indicator is mapped to restricted.


To use multiple mapping-tables, a Complex-Function can be configured. This is an ordered list so be aware of this when creating this complex-function.

complex-function CF_TO_PSTN
execute 1 CNPN_PI
execute 2 REM_PREFIX


How to use a Mapping-Table:

Mapping-Tables are best used within a routing-table.  See the example below that uses the mapping-table listed above (REM_PREFIX_911).

routing-table called-e164 OUTBOUND
     route .T dest-interface IF_SIP REM_PREFIX_911

Atlas small
SN4970
SN4980
SN4990
SN5480
SN5490

(FXO and PRI)

Step 1: Create a “VoIP Gateway trunk” on 3CX

1. From the Admin panel, click on“Voice & Chat” and then on “Add Gateway”.
2. Specify a name.
3. Enter the gateway’s “Main Trunk Number”.
4. In “Registrar/Server”enter the SmartNode’s IP address.
5. Set the "Default Route".
6. Take note of the Authentication ID and password

7. Click on the “Options” tab and enter the “Number of sim calls per trunk” for this gateway. (This must not exceed the number of lines the gateway supports, e.g. a T1 gateway supports 23 lines.)
8. Click “Save” and the gateway is now configured in 3CX.
9. The last step is to create an Outbound Rule for this gateway. Once complete, click “Save”.

Step 2: Configure your SmartNode with 3CX

1. Run the configuration WEB WIZARD for your SmartNode device and fill in the required information. 

• Trinity FXO SmartNode WEB WIZARD 
• Trinity ISDN PRI SmartNode WEB WIZARD 
• SmartWare FXO SmartNode WEB WIZARD
• SmartWare ISDN SmartNode WEB WIZARD

2. Trinity FXO WEB WIZARD

• Fill in the following tabs of the web wizard

• Device Management Tab
  • Here you can change the default admin password.

• Network Settings Tab
  • Set the IP address as either DHCP client or a Static address.

• FXO Port Settings Tab
  • Select the number of FXO ports (1-8)
  • Select the country tone-set profile (United States and Europe)

• 3CX SIP Settings Tab
  • Server IP Address: Enter the IP/FQDN of 3CX
  • Set the Authentication ID and Password (This was previously configured in 3CX for this gateway)

• Once everything is filled out, you can select “Save” and the config file will be downloaded.

3. ISDN WEB WIZARD

• Fill in the following tabs of the web wizard

• Device Management Tab
  • Here you can change the default admin password.

• Network Settings Tab
  • Set the IP address as either DHCP client or a Static address.

• ISDN Port Settings Tab
  • Select the number of ISDN ports (1-4)
  • Select the PRI Line Type (E1 or T1)
  • Select what the ISDN port is connecting to (PBX or PSTN)
  • Select the country tone-set profile (United States and Europe)

• 3CX SIP Settings Tab
  • Server IP Address: Enter the IP/FQDN of 3CX
  • Set the Authentication ID and Password (This was previously configured in 3CX for this gateway)

• Once everything is filled out, you can select “Save” and the config file will be downloaded.

• Load in Config File
  • Enter the IP Address of the SmartNode into a web browser
  • Login using the default username and password of admin/<no password>
  • Click the top left-hand menu and navigate to “System/Configuration Files” and click the “+” button
  • Browse to the file generate and import in as the “startup-config” and click OK
  • Reboot the unit without saving

The unit should boot up and register to 3CX to make a receive calls.

CLI

For connection use:

telnet <ip> 7001

Use <TAB> for completion commands and "?" for external info.

for example:

SIP2TDM# stat ?

Subcommands list:

show - show call statistics

clear - clear call statistics

Common tasks

SIP subscribers

abonent show - subscribers list

Е1 ports

pcm info - show E1 port state

pcm stat show - show error counters

SIP and TDM channels info

chan map all - show all channels summary map

chan map legend - legend for summary channel map

Common info

version - version info

acodes info - show RTP media cores state

stat show - show call statistics

Enable debug info

for V5 protocol

showdbg v5 on

trace pcm start -1
 

for SIP protocol

showdbg sip on

trace sip start
 

for SS7 protocol

showdbg ss7 on

showdbg mtp3 on

showdbg isup on

trace pcm start -1

CLIP

showdbg aon on

showdbg mfr on

 
access to subscriber database

showdbg abon on
 

dialplan routines

showdbg dplan on


Display HDLC messages exchange (for SS7, PRI)

set message length diapason

hdlc dump length <port> <minlength> <maxlength>

hdlc dump length 1 7 9991
 

set display format to HEX

hdlc dump format term


set display format to humman readable

hdlc dump format ascii


enable HDLC debug

trace hdlc 0xffff 0xffff


disable HDLC debug

trace hdlc 0 0





SdCard filesystem

list of main files

list of log Files