SmartNode™ 4830 Series
Analog VoIP IAD with up to 8 FXS/FXO ports and integrated WAN connectivity
The SmartNode 4830 Series Multiport Analog IAD connects up to 8 phone lines, VoIP, and Internet/VPN access across integrated synchronous PPP and Frame Relay links. Offering bundled voice, data, and VPN services, the SmartNode IAD delivers best-in-class VoIP quality for lowest cost networking.



Need help?
Call Patton at +1 301 975 1000 or email sales@patton.com.

Features & Benefits
  • Integrated Sync Serial Uplink—Built-in X.21, V.35 router with PPP, Frame Relay RFC-1490, 8 PVCs and FRF.12 fragmentation
  • Complete VoIP Gateway—SIPv3, H.323v4, T.38 & Fax bypass, G.723, G.729, G.726, G.711, echo cancellation, silence compression, comfort noise.
  • FXS, FXO, or Combinations—Up to 8 FXS ports connect to your standard telephone or PBX. 2 or 4 FXO ports allow local PSTN connections. Programmable call routing and switching.
  • Access & Network Routing—Connected to any broadband or access provider. IPv4, RIPv2, ICMP, NAT/PAT, Firewall, DHCP, DynDNS, IPSec VPN.
  • QoS Guaranteed Voice & Data—Quality of Service ensures voice traffic gets priority without shutting down your Ethernet LAN.
  • Management & Provisioning—Web based management, SNMP, Command Line Interface. Auto-Provisioning for automated configuration distribution and SW upgrades caller/called ID, and time of day.


Overview
The SmartNode™ 4830 Series Analog VoIP IADs let you add packet voice while providing access routing with native V.35/X.21 synchronous serial connection. Add up to 8 phone lines and combine Internet and VPN access on a single PPP or Frame-Relay based access line for the new standard in toll-bypass, remote/branch office connectivity, and enhanced carrier services.

The SN4830 Series offers models with combinations of 2 to 8 analog FXS phone ports and 2 or 4 FXO ports. The Dual 10/100baseT LAN ports can be used for LAN, IPSec VPN and DMZ connections. The integrated X.21/V.35 WAN port provides direct access to IP over PPP and Frame-Relay. Like every SmartNode the 4830 series supports the industry standard VoIP signaling protocols including SIP, H.323, T.38 Fax-Relay, plus Fax and Modem-Bypass and is interoperable with leading Softswitches and VoIP services.

Quality of Service (QoS) features include advanced voice prioritization and traffic management. DownStreamQoS™ ensures voice without interruptions even over best-effort internet connections. Packet labeling according to 802.1p, TOS and DiffServ enable integration into managed QoS networks.

The SN4830 is the solution for service providers and network integrators looking for the seamless integration of analog phones and PBXs into converged VoIP-Data networks. It ensures easy setup and continuous trouble-free operation and cost effective deployment. The support of the leading VoIP signaling protocols ensures interoperability with third-party equipment and protects your investments for the future.


Application - Remote Office/Branch Office Voice Extension and Access

Supporting voice from any local or remote connections with Quality of Service brings true access to all users. Now integrating into local DSL, Cable, or IP access services is clean and complete

SmartNode


Specifications

Voice Connectivity• 2, 4, 6, or 8 FXS ports
  • 2-wire Loopstart, RJ-11/12
  • Short haul loop 1.1 KM @3REN
  • EuroPOTS (ETSI EG201 188)
  • Programmable AC impedence, feeding, and ring voltage; On-Hook Voltage 29VDC
  • Caller-ID Type-1/2 FSK and ITU V.23/Bell 202 generation
• 2 or 4 FXO ports
  • 2-wire loop-start presented as an RJ-11/12
  • 2.5kV line isolation Surge Protection: Voice Ports: Tip & Ring protected by 270 V side actor
  • Off-hook and ring detection, Automatic line gain, Programmable ring count
  • End of Call detection, Line drop, busy tone, battery reversal detection
  • Hook-Flash Sending, H.245 Hook-Flash relay, DTMF send, detect, and relay
  • Caller ID FSK CLI reception and relay (Bellcore/ANSI and ETSI/ITU), Call routing based on Caller ID
  • Second dial-tone for two-stage DTMF dialing, Call routing based on DTMF numbers
Data Connectivity
  • Dual 10/100 Full Duplex, Autosensing, Ethernet RJ-45
  • V.35 or X.21 (depending on model) on a female connector (cable sold separately)
  • Frame-Relay (8 PVCs) # RFC1490, FRF.12 fragmentation
  • LMI, Q.933D, ANSI 617D, Gang of Four
  • PPP, PAP, CHAP, LCP, IPCP
  • Voice Processing (signalling dependent) • Voice codes
    • G.711 A-Law/µ-Law (64kbps)
    • G.726 (ADPCM 40, 32, 24, 16 kpbs)
    • G.723.1 (5.3 or 6.3 kbps)
    • G.729ab (8kbps)
    • Up to 8 parallel voice connections
    • G.168 echo cancellation
    • Carrier tone detection and generation
    • Silence suppression and comfort noise
    • Configurable dejitter buffer
    • Configurable tones (dial, ringing, busy)
    • RTP/RTCP (RFC 1889)
    Fax and Modem Support• G.711 Fax- and Modem-Bypass
    • T.38 Fax relay (9.6 k, 14.4 k)
    Voice Signalling • H.323v4
    • RAS, H.225, H.245
    • H.235 secure RAS
    • Fast-connect, early H.245
    • Gatekeeper autodiscovery, Alias registration
    • Overlap dialing
    • Empty capability set (call transfer, hold)
    • H.323v1 call transfer, hold
    • SIPv2
    • Supported RFCs: 2806, 2833, 2976, 3261, 3263, 3264, 3323, 3325, 3515
    • draft-ietf-sip-cc-transfer-02, draft-ietf-sip-cc-transfer-05
    • draft-ietf-sip-refer-02, draft-ietf-sip-replaces-01
    • draft-ietf-sip-session-timer-04, draft-ietf-sip-session-timer-08
    • Caller ID, CLIR (receive from PSTN)
    • Support for proxy and redirect servers
    • RFC2833: DTMF Relay, SIP INFO DTMF Relay, Fax-Bypass (G.711), T.38 Fax-Relay
    • Session Timer, Record-Routing, Authentication
    • Compression CODECs, Fax/Modem bypass
    Call Routing • Virtual Interfaces
    • Routing Criteria: Called party number (Destination) Calling party number (Source) Time of day, day of week, date
    • Longest prefix match, wildcard match, regular expression match
    • Number Manipulation Functions: Replace numbers Add/remove digits Regular Expressions
    • Fallback Routing: Soft Fallback to alternative interface or Call Router table
    IP Services • IPv4 router
    • Static Routes, ICMP redirect (RFC 792), RIPv1, v2 (RFC 1058 and 2453)
    • Static and dynamic NAT and NAPT
    • DHCP server and Client
    • Access Control Lists
    • IPSEC AH & ESP Modes, preshared Keys
    • AES/DES/3DES Encryption
    Quality of Services • Traffic classification by ACL
    • TOS and DiffServ labeling Configurable TOS/Precedence bits or DiffServ codepoints
    • IEEE 802.1p/Q
    • Traffic scheduling: Priority, Weighted fair queuing (WFQ), Hierarchical traffic classes
    • Policing of traffic classes
    • DownStreamQoS™ Dynamic restriction of inbound (downstream) TCP traffic to free bandwidth for voice packets.
    • Improves voice quality in the receiving direction
    Management • Web GUI
    • Industry standard CLI with local console (CRJ-45, RS-232) and remote Telnet access
    • TFTP configuration & firmware loading
    • SNMP v1 agent (MIB II and private MIB)
    • Built-in diagnostic tools (trace, debug)
    Operating Environment • Operating temperature: 0 - 40°C
    • Operating humidity: 5 - 80% (non condensing)
    System • CPU Motorola MPC875 @ 66 MHz
    • Memory 32MB SDRAM/8MB Flash
    • Power: External universal 100 - 240 VAC (50/60 Hz)
    • Power dissipation: 4 - 12W model dependent
    Compliance • EMC compliance: EN55022 and EN55024
    • Safety compliance: EN 60950
    • CE per RTTE 99/5/EC (EMC and LVD)
    • FCC Part 15 Class A
    • TBR-21 (FXS)



    Ordering Information Email: sales@patton.com    Tel: +1 301-975-1000
    SN4832/JOC/EUI SmartNode 2 FXO VoIP GW-Router, Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4832/JOD/EUI SmartNode 2 FXO VoIP GW-Router, Integrated X.21 WAN, H.323 and SIP, External UI Power.
    SN4832/JSC/EUI SmartNode 2 FXS VoIP GW-Router, Integrated V.35 WAN, SIP and H.323, External UI Power.
    SN4832/JSD/EUI SmartNode 2 FXS VoIP GW-Router, Integrated X.21 WAN, SIP and H.323, External UI Power.
    SN4834/2JS2JOC/EUI SmartNode 2 FXS & 2 FXO VoIP GW-Router, Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4834/2JS2JOD/EUI SmartNode 2 FXS & 2 FXO VoIP GW-Router, Integrated X.21 WAN, H.323. and SIP, External UI Power.
    SN4834/JOC/EUI SmartNode 4 FXO VoIP GW-Router Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4834/JOD/EUI SmartNode 4 FXO VoIP GW-Router, Integrated X.21 WAN, H.323 and SIP, External UI Power.
    SN4834/JSC/EUI SmartNode 4 FXS VoIP GW-Router, Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4834/JSD/EUI SmartNode 4 FXS VoIP GW-Router, Integrated X.21 WAN, H.323 and SIP, External UI Power.
    SN4836/4JS2JOC/EUI SmartNode 4 FXS & 2 FXO VoIP GW-Router, Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4836/4JS2JOD/EUI SmartNode 4 FXS & 2 FXO VoIP GW-Router, Integrated X.21 WAN, H.323 and SIP, External UI Power.
    SN4836/JSC/EUI SmartNode 6 FXS VoIP GW-Router, Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4836/JSD/EUI SmartNode 6 FXS VoIP GW-Router, Integrated X.21 WAN, H.323 and SIP, External UI Power.
    SN4838/4JS4JOC/EUI SmartNode 4 FXS & 4 FXO VoIP GW-Router, Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4838/4JS4JOD/EUI SmartNode 4 FXS & 4 FXO VoIP GW-Router, Integrated X.21 WAN, H.323 and SIP, External UI Power.
    SN4838/JSC/EUI SmartNode 8 FXS VoIP GW-Router, Integrated V.35 WAN, H.323 and SIP, External UI Power.
    SN4838/JSD/EUI SmartNode 8 FXS VoIP GW-Router, Integrated X.21 WAN, H.323 and SIP, External UI Power.
     

    Related Information
    Articles (PDF) -- Requires Adobe Acrobat to view
    Patton Brings Unified Communications to Boy Scouts of America Campground October 31, 2007
    SmartNode™ Delivers VoIP-over-VPN Network with Secure, Encrypted Voice for 1200-Site Retail Chain August 08, 2007
    SmartNode™ VoIP Delivers First-Line Business-Class Internet Telephony Services with green.ch February 06, 2006
    SmartNode™ VoIP Powers inode Business Service for ISDN Subscribers December 21, 2005

    Catalogs (PDF) -- Requires Adobe Acrobat to view
    Patton Electronics Product Line Catalog #21 (High resolution, print quality) August 25, 2008
    Patton Electronics Product Line Catalog #21 (Low resolution, for dial-up users) August 25, 2008

    Certifications (PDF) -- Requires Adobe Acrobat to view
    Declaration of Conformity - SmartNode™ SN4830, SN4520, SN4110 & IPLink™ 2800, 3210 September 29, 2008
    Declaration of Conformity - CE for SmartNodes May 10, 2005

    Data Sheets (PDF) -- Requires Adobe Acrobat to view
    SmartNode 4830 Series Datasheet July 27, 2009
    SmartNode 4830 Series Datasheet (A4 page size) July 27, 2009
    Enhanced Warranty March 01, 2006
    VoIP Glossary March 04, 2005
    VoIP Solutions Guide September 21, 2004

    Manuals (PDF) -- Requires Adobe Acrobat to view
    SmartWare R5.5 Software Configuration Guide March 16, 2010
    SmartWare R5.4 Software Configuration Guide October 13, 2009
    SmartWare R5.3 Software Configuration Guide January 29, 2009
    SmartNode 4830 Series Guide, Getting Started September 29, 2008
    SmartWare R5.2 Software Configuration Guide August 07, 2008
    SmartWare R5.1 Software Configuration Guide February 06, 2008
    SmartWare R4.2 Software Configuration Guide August 17, 2007
    SmartNode 4830 Guide, Quick Start May 16, 2007
    SmartWare R4.1 Software Configuration Guide April 05, 2007
    SmartWare R3.21 Software Configuration Guide April 05, 2007
    SmartWare R3.20 Software Configuration Guide August 01, 2006

    News Releases
    Patton's New VoIP IAD Wins Unified Communications 2007 Product of the Year March 17, 2008
    Patton Wins INTERNET TELEPHONY® Product of the Year for the Third Consecutive Year January 07, 2008
    Patton-Inalp Joins Triple Play Alliance, Promotes Multi-Vendor Interoperability October 01, 2007
    Patton Receives INTERNET TELEPHONY Excellence Award September 12, 2007
    With Over 1,000 Networking Products to Offer, Patton Publishes Dual Catalogs May 22, 2007
    Patton Launches High-Performance PRI VoIP Gateway August 14, 2006
    SmartNode™ VoIP CPEs Now Certified for Interoperability by Cirpack® July 31, 2006
    Patton Unveils Industrial First-mile-Ethernet and Outdoor-VoIP Equipment at GlobalComm 2006 June 06, 2006
    Massive VoIP Rollout Features Patton Equipment April 17, 2006
    Patton Hardens Communication Products April 05, 2006
    Patton and BroadSoft Deliver Interoperability to Carriers March 06, 2006
    Patton Adds Voice-Encryption to SmartNode™ VoIP Routers February 22, 2006
    Patton Receives Technology Champion Award February 01, 2006

    Tech Notes
    Understanding Echo Problems - (PDF) September 19, 2007
    SmartNode™ Quality of Service for VoIP on the Internet Access Link - (PDF) December 13, 2004
    VoIP: What Are FXS & FXO? - (PDF) April 02, 2003

    White Papers (PDF) -- Requires Adobe Acrobat to view
    VoIP in Industrial Networks - Implementing QoS for reliable voice over industrial Ethernet November 10, 2006
    White Paper - SmartWare Release Strategy June 07, 2006
    VoIP - Addressing QoS Beyond the Provider Network January 19, 2006

    Software Upgrades
    SmartNode 4830 Series
     
    Frequently Asked Questions
     SmartNode VoIP/ToIP 
     Call Routing 
     How can I remove or restrict Caller-ID (CLIP)? 
     There are two possibilities:
    1. Set the ISDN Presentation Indicator (PI) to restricted:
    172.16.40.125(ctx-cs)[switch]#mapping-table pi to pi MT-PI-TEST
    172.16.40.125(map-tab)[MT-PI-T~]#map default to restricted

    2. Delete the Calling-Party Nummer using a E.164 mapping table:
    172.16.40.125(map-tab)[MT-PI-T~]#ble calling-e164 to calling-e164 MT-CNPN-TEST
    172.16.40.125(map-tab)[MT-CNPN~]#map default to "" 
     Using Timeout and Termination Characters in Call-Routing Tabels 
     Call-Routing tables offer two possibilities to terminate overlap dialed numbers.
    1. A dialling timeout
    2. A special termination caracter like # or *
    The timout and the caracter can be configured as follows:

    172.16.40.125>enable
    172.16.40.125#configure
    172.16.40.125(cfg)#context cs
    172.16.40.125(ctx-cs)[switch]#digit-collection timeout 5
    172.16.40.125(ctx-cs)[switch]#digit-collection terminating-char #

    For example:
    172.16.40.125(ctx-cs)[switch]#routing-table called-e164 RT-CDPN-EX
    172.16.40.125(rt-tab)[RT-CDPN~]#route 123T dest-interface Line0

    According to this rule the dialed keys '12345#' will be immediatly matched and the number '12345' will be used without waiting for the timeout.

    Special Cases:
    The Termination Character can also be part of the rule, in which case it will NOT have the effect of cancelling the timeout period.

    Examples:
    Rule: #21#T
    Dialled Keys: #21#1234
    Effect: Timeout is aktive, used number: #21#1234

    Rule: #21#T
    Dialled Keys: #21#1234#
    Effect: No Timeout, used number: #21#1234

    Note: The first two dialled '#' do not cancell the timeout, they are part of the rule.

    For a general digit-collection with timeout or termination caracter without any restrictions use the following rule:
    Rule: T

    In this case...
    Dialled Keys: 1234
    Effect: Timeout active, used number: 1234

    or...
    Dialled Keys: 1234#
    Effect: No Timeout, used number: 1234

    Do NOT use a rule as follows:
    Rule: .*T

    In this case...
    Dialled Keys: 1234#
    Effect: Timeout is STILL active because '#' matches the regular expression '.T', the used number will be: 1234#

     
     Codecs 
     Why do I hear a crackling noise when using the G.729 codec? 
     On the SmartNodes (4110, 4520, 463X, 465X 4830, 491X, 492X, 493X, IC-4FXS) is not possible to use two low-bit-rate codecs at the same time on an FXS port. Thus you must choose to use either G.723 or G.729. G.711 is always supported.
    Try this:

    enable
    configure
    system

    ic voice 0
    low-bitrate-codec g729

    In your VOIP profiles, we suggest you use either the G.723 codec or the G.729 codec, but not both, and it should match your low-bitrate-codec selection. 
     Do the SmartNodes support G.729B?  
     G.729 is defined in a standard with two Annexes.
    G.729 is the original 8kb/s CS-ACELP Codec
    Annex A defines a reduced complexity Codec>br> Annex B defines the silence suppression scheme for G.729

    All versions are supported by the SmartNode family. The configuration allows selection of g729 and optional silence supression. The configuration maps as follows with the capability exchange in VoIP signalling.

    If g729 is selected in the VoIP profile:
    G.729 and G.729a are signaled

    If g729 and silence supression are selected in the VoIP profile:
    G.729, G.729a, G.729b and G.729ab are signaled

     
     Even if G.711 codecs are not specified in gateway (H.323, ISoIP), the SmartNode sends H.323 setups with G.711 (plus the additional explicitly specified codecs) to the remote H.323 party. Why? 
     The H.323 standard requires that H.323 endpoints (gateways, terminals etc.) be capable to process G.711. That is why the SmartNode always sends G.711 in the terminal capability set. If a specific codec is to be enforced a codec has to be specified in the interface (H.323) with the keywork exclusive.
     
     How much bandwidth does a VoIP call use? 
     The required bandwdidth depends on various factors such as:
    - Codec
    - Codec samle length
    - Protocol stack (IP, PPP, Frame-Relay, etc.)
    - Tranmission Network (DSL, ATM, etc.)
    - Echo Cancellation

    As a general rule of thumb the bandwdith for one call in one direction is between 10 and 110 kb/s.

    An excellent overview of how these parameters can be tuned and effect the VoIP bandwdith can be found in the following TechNote.
    http://www.patton.com/technotes/smartnode_qos.pdf
     
     What are the available Voice Codecs? 
     
    Codec
    Net Bandwidth per call (kbps)
    Used Bandwidth per call (kbps)
    Min. Compression Delay (ms)
    Usage
    G.711 a-law
    64
    96
    10
    Uncompressed, best voice quality, European audio-digitizing
    G.711 u-law
    64
    96
    10
    Uncompressed, best voice quality, American audio-digitizing
    G.723.1
    6.3
    17
    30
    Good voice quality at lowest bandwidth, like analog phone, acceptable delay

    G.729
    G.729a
    G.729b

    8
    40
    10
    Best relationship between voice quality and used bandwidth, low delay. G.729b is the silence suppression scheme for G.729a and is supported by the SmartNode family. For the sake of simplicity SmartWare and SmartNode always use the term G.729a, implicitly meaning G.729a and G.729b.
    transparent
    64
    96
    10
    Transparent ISDN data, no echo cancellation
     
     What must be observed with codec selection with H.323 FastConnect procedure in case of overlap dialing? 
     When using H.323 FastConnect (which is usually the case) together with overlap dialing the voice codec is sometimes not known to the B-side SmartNode in the route lookup. The configuration fragment below exemplifies how to configure a SmartNode such that it also accepts such incoming calls:
    context cs
    no number-prefix national
    no number-prefix international
    use tone-set-profile default
    ...
    interface h323 h323_1
    routing dest-interface bri1
    remoteip 172.19.128.21
    codec g711alaw64k
    interface h323 h323_2
    routing dest-interface bri1
    remoteip 172.19.128.21
    ...
    gateway h323
    codec g711alaw64k 10 20
    faststart
    no ras gatekeeper-discovery auto
    bind interface eth0 router
    use voip-profile default
    no shutdown

    The bold section shows an H.323 interface without codec. This interface is used by the B-side SmartNode in case overlap dialling is used on the A-side and FastConnect is enabled.

     
     How does voice codec selection for H.323 work with SmartWare? 
     The selection of a specific codec is somewhat tricky with the H.323 protocol. In SmartWare a specific codec can be entered at 2 different locations:
    a. in the h323 gateway configuration
    b. in the h323 interface configurationThe following example exemplifies a typical configuration:
    ...
    interface h323 myif
    routing dest-interface isdn
    codec g711alaw64k
    use tone-set-profile default
    ...
    gateway h323
    alias h323-id inalp1400
    alias e164 01233000
    codec g723_6k3 30 30
    codec g729
    faststart
    ras
    gatekeeper-discovery manual 172.19.32.42 1719 RRS
    bind interface eth0 router
    no shutdown
    use voip-profile default

    The codec configuration in the gateway specifies the 2 codecs G.723 6.3kbps and G.729 as the set of allowed codecs. This set of codecs is sent to the remote H.323 gateway (or gatekeeper) during the capability exchange phase. The codec specified in the interface 'myif' is the preferred codec to be used. SmartWare places this codec is on top of the list of allowed codecs which is sent during the capability exchange phase. Note that the preferred codec specification only works when FastConnect procedure is used. Otherwise it is without effect.

     
     Debug and Logging 
     How do I debug QoS? 
     Debugging QoS is different from any other debug commands. It is a two step process. You must be in configuration mode.
    1) Go into your service policy and specify "debug queue statistics detail 7"
    2) Then do a show command: "show service-policy interface eth0". You can repeat this command as often as you want to view the current statistics. 
     General 
     How can I check if the routing tables are loaded successfully? 
     In the context cs the command 'no shutdown' causes the routing tables to be re-loaded and errors to be printed to the telnet/console (if command 'debug session-router' entered before). 
     What TCP & UDP Service Ports do I need to open to my SmartNode? 
     
    Function/Application Protocol Source Port Destination Port Transport Port
    H.323 - H.225 call setup (default) any 1720 tcp
    SIP and H.323 Audio data streams (RTP and RTCP) 4864-5119 4864-5119 except 5060 udp
    H.323 - Gatekeeper RAS (default) any 1719 tcp
    H.323 - RAS Gatekeeper discovery (optional) any 1718 tcp, udp
    ISoIP (Patton-Inalp ISDN over IP) ports (optional) any 1106 and 1107 tcp, udp
    SNMP–Network Mgmt (optional) any 161 tcp, udp
    NTP–Network Time Protocol (optional) any 123 tcp, udp
    SIP–Internet to Phone (optional) any 5060 tcp, udp
    SIP–Phone to Internet (optional) 5060 any tcp, udp
    TFTP–Used for software upgrades and saving or loading configuration files (optional-for admin) any 69 udp
    Telnet for administration (optional-for admin) any 23 tcp
    ping (optional-for troubleshooting) any 8 icmp
    tracert (optional-for troubleshooting) any 11 icmp
     
     Can I setup multiple VoIP Gateways on a SmartNode? 
     It is possible to configure multiple SIP gateways on a SmartNode and register them with individual settings to different SIP Servers (multiple domain support). With H.323 only ONE gateway can be configured. The SmartNode can register with a single Gatekeeper. 
     DynDNS is expiring my dynamic DNS enteries. How do I refresh to prevent this? 
     DynDNS.org removes dynamic entries if it is not refreshed or changed after 35 days. Some ISP's i.e., Comcast only changes the IP address about every 3 months. According to dyndns.org the "Static DNS" service should be used in such cases. The "static" service still allows an update, it just takes a bit longer to propagate. So even if you really have a dynamic address but it changes in intervals larger than 30 days, use the static service. 
     Sometimes a command entered into the CLI does not appear in the 'show running-config'. 
     If the command entered happens to be a default value (e.g. sntp-client poll-interval 60) the command is not displayed in the running-config but nevertheless active. This means that only commands and values other than defaults are displayed in the running-config.

     
     How does a SmartNode work in combination with IP-Phones? 
     SmartNodes and IP-Phones can operate in the same H.323 Zone. IP-Phones may be connected to the customer LAN or directly to the access Network. If the SmartNode is used as an ISDN over IP access device, it works independently of H.323 IP phones connected to the same network.

     
     How can the SmartNode be remotely managed when the IP network is down? 
     SmartNodes offer a local console interface which can be connected to a separate device, for example analog modem. In this way the SmartNode can be managed through a dial-up connection if the IP Network is down or the SmarNode is mis-configured.

     
     Keypad facility does not work with H.323. 
     In ISDN supplementary service can be invoked by means of thekeypad protocol. A service can be invoked with the digitsequence *21#. The phone sends these digits as information element 'Keypad Facility' and not as informationelement 'called party number'. As the H.323 protocol does not dispose of a way to transport 'keypad facility'information it gets lost.On the contrary H.323+ (H.323 Annex M3) is a tunneling protocol for the transparent transport of ISDN over H.323and thus inherently supports 'keypad facility'.Note that on some phones it is required to explicitly switch to keypad facility mode in order to send a specificdigit sequence as info element 'keypad facility'.

     
     Is DTMF supported in SmartWare? 
     Yes. Generally, DTMF can always be transported either out-of-band or in-band. in-band provides the most accurate timing reproduction of DTMF, but it is not suitable when a compressing codec is used, e.g. G.729 or G.723. In these cases, out-of-band has to be used for reliable DTMF transport. Smartware supports all mechanisms available today: In H.323: SmartWare uses a mechanism called H.245 alphanumeric for the transparent (i.e. loss-less) transport of dialed DTMF digits across an H.323 network. DTMF digits are extracted from the (digital) ISDN signal, transported to the remote H.323 party which inserts the DTMF digit into the signal again. SmartWare allows to configure an H.323 interface to 'relay' DTMF signals as described above or to leave the signal unchanged. The latter may cause problems when compression codecs are in use which may distort the DTMF signal such that a receiving IVR application is no longer able to decode the signal properly.

    In SIP: You can choose between RFC2833 transport of DTMF, within the real-time data (default and most commonly used), or you can choose to have DTMF sent as SIP INFO messages - this way a SIP proxy that does not route RTP traffic will be able to see it. 
     The routes on my MS Windows machines suddenly change when a SmartNode is booted on the same subnet. Why? 
     The SmartNode is a router as per RFC1812/RFC1256 and thus sends "ICMP Router Discovery" messages to the subnet to which it is attached. Some MS Windows versions react to such messages and automatically adjust their routing tables. In order to avoid such unwanted routing table changes on MS Windows machines the "ICMP Router Discovery" can be switched off as follows (per interface):
    context ip
    interface eth0
    no icmp router-discovery
     
     How does the gatekeeper registration work in detail? 
     Up to 3 different gatekeeper IP addresses can be configured on a SmartNode.If the SmartNode is unregistered from the gatekeeper by means of an URQ message, after sending a UCF message the SmartNode tries (instantaneously) up to 3 times (every 20s) with an RRQ message to register with the next configured gatekeeper (round robin). Once successfully registered the SmartNode re-registers every 90s again with a RRQ message. If 3 RRQ registration requests in a row fail the SmartNode switches to the next configured gatekeeper. If a RRQ is not answered with a RCF or RRJ the SmartNode resends 2 further RRQ messages in 20s intervals.

     
     Signaling works fine but there is no voice at all. What is the problem? 
     When using NAPT on a SmartNode there is one global IP interface (with the public IP address) and one local IP interface (with the private IP address). The H.323 gateway must be bound to one of the interfaces since it needs to know on which interface it must send broadcast RAS messages for gatekeeper discovery. When the gateway is bound to the local interface (the one with the private IP address) then signaling with a gateway or gatekeeper in the public network works fine, but RTP packets (voice packets) will use the private IP address and thus voice will not be routed to the destination. Thus make sure that the gateway is bound to the correct interface (generally the global interface when using NAPT).

     
     I need to know the Ethernet MAC address but do not have physical access to the SmartNode. Is there a way to retrieve the MAC address remotely? 
     Yes, the command 'show port ethernet' shows the current Ethernet configuration along with the MAC addresses.

     
     Hardware Interfaces 
     Why does Ethernet not work when connected a Laptop with PC-Card Ethernet interface to a SmartNode using a crossover cable? 
     Some PC-Card Ethernet interfaces do not provide enough voltage to be recognised as a proper Ethernet signal by the SmartNode network interface. We recommend to connect the Laptop to the SmartNode using straight cables via Ethernet hubs or switches.

     
     What is FXS & FXO? 
     In analog telephony there are two common types of interfaces: FXS and FXO. FXS stands for "Foreign eXchange Subscriber" interface is used to connect subscriber equipment such as telephones, modems and Fax machines. FXO stands for "Foreign eXchange Office" is used to connect to the Public Switched Telephone Network (PSTN) and can also be used to connect to a PABX or multiplexer FXS port. Another third interface, which we will not discuss here, is known as an E&M (Ear & Mouth) interface which is used to provide a leased line or tie-line interface connection between PABX systems.

    An FXO device plugs always plugs into an FXS line. You cannot plug FXS into FXS, or FXO into FXO; it will not work.

    FXS Information

    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.

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

    Typically FXS devices do not indicate when they want to clear a call down, they rely on the two parties noticing that the call has ended (through the other party saying goodbye or the line going quiet) and each end device clearing itself down.

    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

    FXO receives a call by:
    • 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.
    Examples
    • 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 2300 IC-4FXS card is FXS

     
     Licenses 
     Why do I need a License Key for Release 3.10? 
     SmartWare is the embedded software running on the SmartNodes. SmartWare offers a number of feature options such as QSIG, VPN and IP forwarding.
    Up to SmartWare release 2.20 feature options had to be paid but where not keyed. Starting with release 3.10 a license key has to be installed to enable the feature options.

    Note that some product bundles include some of the feature options i.e. SN1200/2VIL/UI includes IP Forwarding. The "I" in the model code stands for the IP forwarding license.

    Q. Do I need a License Key for every SmartNode?
    Yes the License Keys are specific to the feature option and the serial number of the SmartNode. The keys can not be transferred from one unit to another.

    Q. Where can I buy Licenses?
    Feature Options can be purchased through the regular SmartNode distribution channels.

    Q. Where can I get License Keys for feature options purchased together with SmartWare 2.20?
    The License Keys for SmartNodes delivered with SmartWare 2.20 can be requested using the following web form:
    Liscense Request Form

     
     How do I install a license key? 
     License Key installation is described in the Software Configuration Guide 3.10 in the Chapter "Basic System Management" section "Managing Feature License Keys".

    To install the licenses, simply copy the install command and license key ("install license 00010001gB...") from this message and paste them into an open CLI telnet or console session. Note that the CLI session must be in the "configure" mode.
    You can verify that your license are installed using the following command:
      show licenses

    Occasionally, e-mail clients can add spaces or tabs that will currupt a license key. If you have problems with the cut and paste method, you can alternatively copy a license file from your TFTP server as follows:
      copy tftp://tftp-server-ip-address/tftp-server-path/license-file licenses:

    Example:
     copy tftp://192.168.1.1/sn4xxx_00a0ba001234.lic licenses:

      You should then see:
      Download...100% 
     When installing the License the SmartNode returns an error 
     There are two possible reasons for that. 1. You may be trying to install the wrong key. Make sure the keys you are installing match the serial number of the SmartNode. 2. You may have an early access build of SmartWare release 3.00 or 3.10. Please upgarde to a commercial release build number and try again.

     
     I have two different keys for the same feature on the same SmartNode. Which one is correct? 
     When a licence key is issued several times the resulting cipher key is different. However both keys will work and enable the same feature.

     
     The License does not work correctly on my SmartNode 4000 Series? 
     Some SmartNode 4000 series units have a serial number notation using colons ":" that do not work with the early access builds of Release 3.10. Upgrade first to the commercial version of 3.10 and the install the license keys.

     
     Network Address Translation (NAT) 
     Do SmartNodes have a built-in NAPT application level gateway for H.323? 
     H.323 is a non-well behaving protocol in that it signals transport ports (RTP ports) inband in IP packets. When using NAPT (Network Address and Port Translation) this poses a problem since the ports are used by NAPT for address mapping. Thus H.323 does usually not pass a NAPT unless the NAPT is enhanced with H.323 aware functionality that leaves H.323 port ranges untouched.SmartNodes have NAPT but no H.323 aware application level gateway. However, it is possible to run NAPT and H.323 gateway concurrently on a SmartNode since NAPT affects only packets that are routed from IP interface to another (WAN to LAN).

     
     Can I do VoIP over NAT (Network Address Translation)? 
     Yes, If you are on a private network, your firewall or NAT (Network Address Translation) router must be “H.323 aware” or you'll need a SIP proxy if you are using SIP. To help determine if your LAN uses NAT, you can use a web browser and go to the following URL: http://www.patton.com/support/showmyip
    This shows both the public and private IP address of your PC.

    Note: H.323 aware routers and firewalls support "snooping", in which the H.323 control channel is continuously examined and session requests are authenticated. Once authenticated, the requested ports to be used for the H.323 session are opened for the duration of the conference. Upon termination of the conference, the ports are immediately closed by the firewall.
    This is often referred to as an Application Level Gateway since this operation requires the firewall to be protocol-aware. Your H.323 aware router must support H.323v3. Both the firewall and the NAT/PAT software in your router must be H.323v3 aware.  
     SIP 
     How many SIP users can be supported on a SmartNode? 
     For all intents and purposes a maximum number of 100 "SIP users" can be supported on a SmartNode 
     Can I bind multiple SIP Gateways to the same IP Interface? 
     In some cases you may want to create multiple SIP gateways to subscribe to multiple SIP Telephony Services at the same time, or to seperate LAN SIP calls from Global/Internet SIP calls.

    In order to bind multiple SIP gateways to the same IP interface the signaling port of the different gateways has to be different. Use the "call-signaling-port" command for this purpose

    172.16.40.125(cfg)#gateway sip SIP1
    172.16.40.125(gw-sip)[SIP1]#bind interface eth0
    172.16.40.125(gw-sip)[SIP1]#no shutdown

    172.16.40.125(cfg)#gateway sip SIP2
    172.16.40.125(gw-sip)[SIP2]#bind interface eth0
    172.16.40.125(gw-sip)[SIP2]#call-signaling-port 5062
    172.16.40.125(gw-sip)[SIP2]#no shutdown

    If you do not change the signalling port you will get the following error message when you try to bind or activate the second gateway:

    % ANOTHER GATEWAY IS ALREADY BOUND TO THE SAME PORT

    Note: The ports are allocated even if a gateway is in shutdown. You must still use different signalling ports on each gateway!

    Note: The signalling port numbers must be even values e.g. 5060, 5062, 5064 etc.
    As an alternative, you may want to create different SIP "services" within one gateway - this allows to have mulitple virtual gateways on the same interface, using all the same call signaling port. 
     Supplementary Calling Features 
     How do I send a hook FLASH to a SIP Provider to use services like three-way conferencing? 
     By default the SmartNode handles hook FLASH events by itself, i.e. a call is held locally, and if it is transferred, it is looped locally as well.

    If you want to transmit the DTMF towards the far end, you must disable the additional servivces on the fxs interfaces.

    Example:

    interface fxs IF_FXS_00
    no call-hold
    no call-waiting
    no call-transfer
    no additional-call-offering

    This is often used in fxs/fxo line extensions.
    To transport a hook flash to the SIP network, you also need to set the option in your voip profile.
    Example:

    profile voip default
    dtmf-relay rtp


    Options:

    dtmf-relay rtp - DTMF's and flash are transmitted by RFC2833 RTP events. This is the default setting.
    dtmf-relay signaling - DTMF's and flash are transmitted by SIP INFO messages.
    Regardless of what is configured, the SmartNode accepts incoming events of both methods.  
     How can a FLASH be relayed from an FXS port to the PSTN on an FXO port? 
     A common application is to accept calls from a PSTN on an FXO port and then ring a telephone connected to a FXS port. In order to send a FLASH out the FXO port to the PSTN, you must disable all supplementary calling features on the FXS interface. For example:

    interface fxs IF-FXS-PHONE1
    route call dest-table TAB-OUTGOING-LINE1
    no call-hold
    no call-waiting
    no additional-call-offering
    caller-id-presentation mid-ring
    use profile tone-set US
     
     How can I do Call Transfer and FLASH codes on the SmartNode? 
     SmartWare FLASH Codes

    -FLASH 0 - keep current, reject incoming
    -FLASH 1 - drop current, accept incoming
    -FLASH 2 - hold current, accept incoming
    To toggle between the active and the held call, press flash-hook, followed by the "2" key.

    Additional Call Offering

    To enable aditional call offering, configure the fxs port of the SN with the command: additional-call-offering

    1) Press FLASH, then the first call is placed on hold and you will hear a new dial tone.
    2) Dial the number of the second call.
    3) If you press FLASH, you may change between the two calls.
    4) When you hang-up on the phone, the two other parties are connected together. Sorry, three way conferencing is not yet supported. 
     Upgrading/TFTP 
     Using Encrypted TFTP 
     

    Encrypted Configuration Download

    - 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:

    show 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

     
     What happens if the software upgrade on a SmartNode fails? 
     Each SmartNode is equipped with a bootloader application. If an upgrade fails and no valid firmware is available on the system the SmartNode will start in this bootloader mode. The bootloader will allow you to install a new firmware.
    Please refer to the user documentation on how to operate in bootloader mode.
    Note that the bootloader can not be replaced. 
     Where can I get a TFTP Server to load in my configuration or upgrade my SmartNode Software? 
     We recommed two good TFTP Servers: First the Solar Winds TFTP Server is found on the SmartWare CD. You can also download it from the SolarWinds web site. Use SolarWinds version 3.0.9 or higher. SolarWinds is especially nice if you want it to run a TFTP server all the time as an NT service.

    Additionally,
    TFTPD is available on-line for easy download. Use version 2.60 or higher. TFTPD32 a very small, fast, easy to use and contains a TFTP Client, TFTP Server, Syslog, and SNTP server which are all useful for testing. TFTPD32 is a stand-alone executable that is quick to get running.

    Thank you SolarWinds and Philippe Jounin! See their web sites for more great software.

     
     The software download fails in the middle of the process. Why? 
     Some firewalls may reset a session when it takes too much time to complete. On low speed links the software download via TFTP may indeed take a long time and thus the firewall on the link may prematurely reset the session.

     
     VPN 
     Can I do encrypted VoIP calls with the SmartNode IPSec? 
     Yes, with SmartWare software releases dated 3/1/06 and later. For earlier relases, VoIP calls terminated on the SmartNode route the RTP outside the VPN tunnel. A VPN feature license has to be installed for this feature to work. 
     How many VPN tunnels can I configure on a SmartNode? 
     The number of VPN tunnels that you are able to create is only limited to the amount of available RAM. The SmartNode does not have a preset limitation of VPN tunnels. In practice the SmartNode will support a minimum of 10 VPN tunnels but also 100 tunnels are working. Keep in mind that with a large number of tunnels the available bandwidth for each tunnel is reduced. Note that you have to install the VPN license key to have access to the VPN configuration.