1. Network Topology / Environment

Explain how the product is being used and what it is connected to in terms of PSTN circuits, PBXs and ITSPs.
If you have a complex topology, a diagram and dialling plan would be appreciated.

2. Fault / Issue Description

Explain the problem, behaviour and symptoms that you observe. If the problem is reproducible please explain
exactly the steps required to do so. If the problem is infrequent or intermittent, please provide details.

3. Capture Debug Logs

Before starting the debug process please minimize the number of live calls being made; ideally there should be no
other calls in progress so we get a clean trace of the test call only.

Please document exactly the call flow of the test call you are going to make; this make it easier to follow what is
happening in the logs and identify any unexpected behaviour.

• calling number/extension
• how you expect the call to route and/or be modified through the Patton SmartNode
• destination number/extension
• firmware versionnumber

Telnet to the Patton SmartNode using Putty or another good-quality telnet client (not Microsoft Telnet)
Log the telnet session to a text file so everything is recorded, including the commands you type.

To get the backspace key working in Putty, go to Configuration > Terminal > Keyboard and change the option to
‘Control-H’. Logging can be found in Session > Logging. Set to ‘Printable output’.

The exact commands depend on the SmartNode model and the problem being reported, however in the first
instance we suggest the following debug flags are used. We will ask you for more specific logs if necessary.

  Enterprise Session Border Controller (ESBC)

ISDN Gateways (BRI/PRI)

After completing the test, type “no debug all” to disable the debug output.

We look forward to receiving an email with two attachments that contain everything
we need to quickly help you solve your problem.

contact: support@patton-inalp.com

Just download the below .xml file and import it in to your SmartNode, using the "Wizard Config" import function located under "System" in the SmartNode WEB interface. After that, click on the magic wand on the top right of the WEB interface, select the previously imported WEB Wizard, to configure the SmartNode.
When done with entering the values of the WEB Wizard form, hit "Save & Reboot", to generate and apply the SmartNode Configuration.

Download of SN4970 / SN4971 WEB Wizard File

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

Materials needed

 

You'll need a Cat5 cable end, some Cat 5 cable (just a few inches needed), and a Cat 5 cable crimper & cutter.

 

2 Steps:

1. Cut off about 2 to 4 inches of a Cat 5 cable 
2. Take off the casing 
3. Separate 2 of the 8 wires for use... usually same colors (brown and brown/white, etc.) 
4. Identify the pin order on the Cat 5 end: hold it with the movable/press-side of the clip away from you and the metal contacts facing left. If you are looking at it this way, the bottom slot is pin 1 and the top is pin 8. 
5. Put one end of the first wire (either one will do) into pin 1 and bend it in half and put the other end of it into pin 4. 
6. Put one end of the second wire into pin 2 and bend it in half and put the other end into pin 5. 
7. You should now have 2 wires "looped" in the cat 5 blank end with pin 1 connecting pin 4 and pin 2 connecting pin 5 
8. Put the Cat 5 end into the crimper and verify all of the wires are pushed all the way into the pin slots and then crimp it down. 
9. Test it on a "known good" router with a CSU/DSU (T1 interface). Place the loopback plug into the T1 port and you should see the unit "synch" to itself by indicating either "Link" or having whatever is used for the WAN interface to show the unit now has sync. If it does, you've successfully built the plug. If it doesn't work, you've either built it wrong or the CSU/DSU isn't working properly.

 

3 Steps:

How to use the loop plug

1. Let your ISP know you have a loopback plug. 
2. They will likely want you to plug it into the "smart jack" (the final hand-off point from the local phone company. 
3. The loopback plug will allow the local phone company to test THROUGH THE SMART JACK and verify if the service is working properly through that point. 
4. Once service is verified through the Smart Jack, you should see if you can plug the loopback plug at the end of your Internal (or Inside) wiring. If you have a buscuit jack at the end of an extension from the smart jack, you can plug the loopback plug into it and the ISP can tell you if you are "clean" through the Inside Wiring.

 

4 Steps:

Exception

It IS possible for the test to be good through the loopback plug and there STILL BE AN ISSUE with the local phone company's wiring. In rare cases, the copper pairs may be "rolled." This means that the 4 wires used to provide the T1 service are wired in reverse where Transmit 1/Receive 1 are actually wired to Transmit 2/Receive 2 somewhere along the route. In this case, the loop test will perform properly, but the T1 service will not work. If you suspect this, you should ask the ISP to dispatch the local phone company to "Prove through the demarc/Smart Jack." This will force the local phone company to dispatch to your site and test head-to-head with the local Central Office to prove the service is good. There sometimes may be a charge associated with this dispatch IF IT IS FOUND THAT YOUR EQUIPMENT OR WIRING IS THE CAUSE OF THE OUTAGE.

 

Conclusion

Ultimately, the ISP is "responsible." However, having this simple piece of network test gear can speed up the process of a T1 repair and troubleshooting. In the end, restoring your service as quickly as possible is the ultimate goal and this will help you achieve that goal!

1. Certification test:

The tests were executed between both a Patton Trinity SmartNode 4130 (BRI) and Trinity SmartNode 4170 (PRI)  and two SwyxWare installations in Master-Standby operation.

Versions

The following combinations were tested:

• SwyxWare2015 R3, with Patton Trinity SmartNode SN4130, Firmware Trinity 3.9.3 (June 2016); test date: 10.06.2016
• SwyxWare2015 R3, with Patton Trinity SmartNode SN4170, Firmware Trinity 3.9.3 (June 2016); test date: 16.06.2016

Endpoints:

• SwyxIt!
• SwyxIt! (via RemoteConnector at SwyxWare2015)
• SwyxPhone      L615
• SwyxSIPPhone S315
• SwyxPhone D510 via DECT500

1.1 Executed tests

Inbound and outbound calls with the above endpoints from and to PSTN / GSM

• Signaling
• CLIP
• CLIR
• CLIP No Screening
• Long duration calls
• Hold / Retrieve
• Call toggeling
• Transfer
• Conferencing
• Call forwarding internal/external
• DTMF Signaling
• T.38 negotiation and FAX transmission
• CTI+

All test cases were completed successfully.

Restrictions:

If a call through CTI+ is not accepted by the called party, a timeout occurs in both the Patton GW and the SwyxWare. This leads to the situation that the auxiliary call is not terminated automatically, but has to be terminated manually by the user on the controlled device.

2. Start-up:

The following steps are necessary for a start-up:

• Creation of a SIP gateway trunk und SwyxWare user; configuration of SwyxWare locations if necessary
• Preparation of the Patton Trinity SmartNode
• Adjustment and installation of the Patton Trinity SmartNode configuration file

2.1. Preparation of SwyxWare

1. Using the configuration assistant, create a new SIP Gateway Trunk group within the SwyxWare. Select the Trunk Group Profile "SwyxConnect" that fits to your PSTN connection.
2. Create a new SIP Gateway Trunk for the newly created SIP Gateway Trunk Group.
3. Configure "SIP-User-ID" and "SIP Username" with a value of your choice, use the same value for both items.
4. Configure the SIP password.
5. Configure the available range of external numbers.
6. Activate all codecs.
7. Configure the number of available channels.
8. Set the local NetBIOS name as "Computername".

Afterwards, open the properties of the newly created SIP Gateway Trunk.

1. In the tab "Encryption", set the encryption mode to "No Encryption".

2.2. Preparation of Patton Trinity SmartNode

Update the firmware of the Patton Trinity SmartNode to the tested version Firmware Trinity 3.9.3 (June 2016) before adjusting the configuration. The appropriate firmware can be found here. You need an account and password from Patton to download the firmware.

Connect the Trinity SmartNode through the network interface ETH 0/0, which defaults as a DHCP client, with your LAN. Please check the lease table of your DHCP server to detect the assigned IP address.  You may also use our SmartNode Discovery Tool to find this device on your network as well.  Note: Please read the release notes on how to use this tool)

Log in through the web interface of the Trinity SmartNode:

Username: administrator
No password (leave blank)

Left in the menu (three horizontal lines) select "System -> Firmware upgrade" Use the field "Browse" to select and upgrade the firmware.
The filename contains the model of the Trinity Smartnaode and the firmware version, i.e. SN4130_3.9.3.tar.  Afterwards, the Trinity SmartNode is restarted and uses the new firmware.

2.3. Configuration and Installation of the INI Files

At the end of this article, you can download a zip-file with several configuration templates. Download the one that fits to your PSTN-Connection.

2.3.1 Configuration of the INI file

Open the chosen configuration template with a text editor, find the following terms and replace them with the appropriate settings. 

Note: A term may occur several times in the configuration template and must be replaced accordingly.

STANDALONE:

• IP-PBXSERVER
  • IP Address of your SwyxWare server
• SIP-NAME
  • SIP-User-ID / Username of your trunk
• SIP-PASSWORD
  • Password of your trunk
• SIP-REALM
  • Standard realm for SIP clients

MASTER-STANDBY:

• IP-PBXSERVER-MASTER
  • IP Address of your Master SwyxWare server
• IP-PBXSERVER-STANDBY
  • IP Address of your Standby SwyxWare server
• SIP-NAME
  • SIP-User-ID / Username of your trunk
• SIP-PASSWORD
  • Password of your trunk
• SIP-REALM
  • Standard realm for SIP clients

Save the changes after adjusting the configuration file.

2.3.2 Installation of the INI file

After the reboot, logon with the Trinity SmartNode once again and upload the adopted configuration file.  In the left menu (three horizontal lines), select "System -> Configuration files".  On the left side of the dialog, first select "startup-config", then select the item "Upload".  In the following dialog, click "Browse" to upload the configuration file.  Afterwards, close all open configuration dialogs. On the left menu (three horizontal lines), select "Reboot".

The Trinity SmartNode will restart with the new configuration file and will register on the SwyxWare.

Links:

• Trinity Smartnode Templates (27.06.2016)
• Trinity SmartNode Wizard Templates
• Swyx Certificates
  • SN4130
  • SN4170
• Patton SmartWare SmartNode support with SwyxWare
• Contact Patton Support:
  • Website
  • Email
• Swyx KB Article KB4824

SmartNodes running SmartWare:

rtp-port-range 4864 5375

Configuration:

10.10.50.17>enable
10.10.50.17#configure
10.10.50.17(cfg)#context ip
10.10.50.17(ctx-ip)[router]#rtp-port-range <start> <end>

*<start> [2..65534] Enter start of range. The number must be even. (Def: 4864)
*<end> [3..65535] Enter end of range. The number must be odd. (Def: 5375)

SmartNodes running Trinity:

rtp-port-range 6000 9999

Configuration:

0B97AA>enable
0B97AA#configure
0B97AA(cfg)#rtp-port-range <portRangeLow> <portRangeHigh>

*<portRangeLow> [2..65534] Enter start of range. The number must be even. (Def: 6000)
*<portRangeHigh> [3..65535] Enter end of range. The number must be odd. (Def:7023)

SETUP (DSS1 User)
[04038090A3]
Bearer capability : speech - CCITT
circuit mode - 64kBit/s - G.711 A-law
[1E028583]
Progress indicator : origination address is non-ISDN
private network serving remote user - CCITT
[6C03008030]
Calling party number : 0
unknown number - unknown numbering plan
presentation allowed - user provided not screened
[700480313233]
Called party number : 123
unknown number - unknown numbering plan
[7D029181]
High layer compatibility : telephony
CCITT

To change this behaviour, you will need to configure the following mapping tables in your configuration.  This configuation works for both SmartWare and Trinity VoIP devices.

routing-table called-e164 RT_FROM_SIP
  route default dest-interface IF_ISDN_0 ISDN_NATIONAL

mapping-table calling-type-of-number to calling-type-of-number MAP_TO_NATIONAL
  map unknown to national

mapping-table calling-numbering-plan to calling-numbering-plan NATIONAL
  map unknown to isdn-telephony

complex-function ISDN_NATIONAL
  execute 1 MAP_TO_NATIONAL
  execute 2 NATIONAL

Once you have implemented these config changes, you will simply have to route your SIP interface to the routing-table RT_FROM_SIP, as seen below.

interface sip IF_SIP
  bind context sip-gateway GW_SIP
  route call dest-table RT_FROM_SIP
  remote 192.168.0.1

The SETUP message will now look like this.

SETUP (DSS1 Ntwk)
[04038090A3]
Bearer capability : speech - CCITT
circuit mode - 64kBit/s - G.711 A-law
[1E028183]
Progress indicator : origination address is non-ISDN
private network serving local user - CCITT
[6C03218030]
Calling party number : 55555
national number - E.164 numbering plan
presentation allowed - user provided not screened
[70058031323233]
Called party number : 44444
unknown number - unknown numbering plan
[7D029181]
High layer compatibility : telephony
CCITT

Instructions to load Trinity Templates into 3CX (WINDOWS)

1. Download the NewTemplate.zip file attached to this article.
2. Extract the contents of the zip file into the ‘Downloads’ folder on your Windows machine.
3. Once there, execute the .bat file
   • 3CX_Template_Move.bat

The template files are now added to the following Windows directories for your 3CX Phone System:

C:\ProgramData\3CX\Instance1\Data\Http\Templates\gateway
C:\ProgramData\3CX\Instance1\Data\Http\Templates\fxs

Instructions to load Trinity Templates into 3CX (LINUX)

The gateway templates are stored in the following directory:

/var/lib/3cxpbx/Instance1/Data/Http/Templates/gateway/

To add these new templates, copy and paste the following into the CLI of your Linux machine.

cd /var/lib/3cxpbx/Instance1/Data/Http/Templates/gateway/
wget https://patton.com/files/support/3cx-templates/NewTemplates.zip
unzip NewTemplates.zip



UPDATES

You can now add a Default IP Gateway and DNS Server within 3CX using the new templates.  The new sections will be under the 'Options' tab.





*** Patton Gateways can be used with your 3CX Phone System.  However, the templates are created, tested and supported by Patton.  Please contact our Support Team with any questions. ***

Instructions to load Trinity configurations into SmartNodes

1. Enter in the IP Address of your SmartNode device
2. Click the menu button () from the upper left-hand side
3. Select System/Configuration Files and a window will pop-up. Click the + sign to add a new config.

• Browse to the file and then add it as the ‘startup-config’ and click ‘OK’. The config will now be saved and loaded on next bootup.
• To reboot the device, click the menu button () and select ‘Reboot’. Answer ‘Yes’ to the pop-up window to initiate the reboot.

Your SmartNode will now be successfully configured and registered to use 3CX.

Please contact Patton Support if you have any questions.

support@patton.com




Note From 3CX on Templates:

• 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

routing-table called-e164 RT_HOTLINE

  route T!5 dest-interface <target interface> MT_CALLED_HOTLINE

mapping-table called-e164 to called-e164 MT_CALLED_HOTLINE

  map ^$ to 12345

Follow these instructions to switch the bootloader from one image to another one.

• HOLD the reset button during boot
• The power LED flashes quickly for 5 seconds, during which time the reset button must remain pressed
• The power LED will begin a blink pattern (described below)
• Pressing the reset button will change the blink pattern
• 10 seconds after the last reset button press, an action will be performed based on the selected pattern

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.

• CPU over a specific threshold
• Ethernet cable is connected or loses connection
• Hardware sensor failure
• SIP overload
• SIP registration failure
• CPU Temperature over threshold (~75°C)

The traps will always be sent with the same OID (1.3.6.1.4.1.1768.18.10) and contain a string describing the alarm that was raised. This is a part of Pattons custom enterprise subtree (1.3.6.1.4.1.1768).