Need help? Call Patton at +1 301 975 1000 or email sales@patton.com.
Features & Benefits
4 ISDN BRI S/T, RJ-45
G.168 echo cancellation
DTMF detection and generation
Support of various voice codecs: G.711 A-Law/µ-Law, G.723.1, G.729A, Transparent
Voice Signalling: Euro ISDN EDSS-1 / ETSI BRI / NET3; Q-SIG (PSS-1)
EMC & CE Compliant
1-year warranty
Optional Upgrade: 2-5 year Warranty
Optional Upgrade: 1-5 year Enhanced Warranty (includes free Advance Replacements)
Overview
The IC-4BRV is a PMC standard compatible interface card for the SmartNode 2000 series. It provides 4 ISDN BRI interfaces and connects through a PCI packet and PCM circuit interface to the SmartNode base unit.
The IC-4BRV supports up to 8 simultaneous voice or fax calls. It is a flexible ISDN networking card designed to meet the needs of small enterprises that want to connect their ISDN equipment, such as an ISDN PBX, via multiple BRI interfaces to a multi-service IP network.
The ISDN interfaces can be configured as user or network side interfaces. Its on board dedicated micro-controller and DSPs offload the CPU of the SmartNode 2000 base unit and hence guarantee the conversion of voice/fax circuits into related IP-packets in real-time and with least delay and jitter values.
Configuration Example The example shows the connection of a PBX via an IC-4BRV Card in a 2Net : 2Usr configuration into an IP Network.
How to extend dial tone (dial tone extension) from one location to another location without a SIP server.
The dial tone generated by a PSTN connection or a PBX can be extended over the Internet or an Intranet by using a pair of Smartnode 452x units or a Smartnode 452x and a Smartlink 402x unit. This FAQ describes how to perform dial tone extension using a Smartnode 452x and a Smartlink 402x. Smartnode to Smartnode configuration information is available under "Line Extensions" of the SN452x applications notes page. Once the setup is complete, the end user will be able to lift the handset on the analog phone, hear the dial tone from the PSTN or PBX and then dial a number just as if they were directly connected to the PSTN or PBX. Flash-hook is supported so features like call waiting and call hold will work. Tax pulse tone (not typically used in the USA) is not supported.
The guide below assumes that WAN and LAN connectivity has already been established.
Hardware –
Smartlink 4021 or Smartlink 4022
Smartnode 4522, 4524, 4526 or 4528 with FXO ports (order code “JO” indicates FXO ports)
PSTN analog connection OR PBX with analog phone port
Analog phone
Physical Connectivity
Analog phone ----SL402x----- Internet/Intranet -----SN452x-------PSTN or PBX
In the SL4020
Under Telephony, SIP –
Set “SIP Registration Server Address:” to the IP address or domain name of the SmartNode 4520
Uncheck “Send Registration Request with Expire Time:”
Save the changes
Under Telephony, Phone 1
Set the phone number to the phone extension (example 111).
Optional - You can set caller id if you wish.
Under “Dial Out Type” , select Hotline from the drop down menu
Under “Hot Line Number”, enter the phone number that has been routed to the FXO port on the SN452x.
Save the changes
Go to System,Reload and restart the SL4020
In the SmartNode 452x....Please use the Smartnode CO configuration information under "Line Extensions" of the SN452x applications notes. You will need to add call routing and mapping table to strip the called number that is passed from the Smartlink.
routing-table called-e164 TAB-IN
route ... dest-interface IF_FXO0 STRIP
mapping-table called-e164 to called-e164 STRIP
map ...% to \1
map default to ''
How many VPN tunnels can be configured on the SL4020
The configurable limit is 8 now. Based on our preliminary study of code and hardware we believe this limit could be extended significantly. It will eventually be limited by memory and network resources.
Telephones
I would like to be able to push one button and immediately get a dial tone from the PSTN so that I can make calls. I DO NOT have SIP server.
Sounds like you want to do something like press "9" for an outside line and then dial number......
This can be accomplished by using a combination of features on the Smartlink phones or gateways along with a Smartnode serving as the gateway to the PSTN. The resulting design results in two calls being made - one SIP call from the Smartlink device to the SmartNode gateway and a second PSTN call from the Smartnode gateway to the destination address on the PSTN. How it works- The SL4050/SL4020 makes a SIP call to the Smartnode when the speed dial button is pushed. The Smartnode accepts the SIP call and presents dial tone from the FXO line. The user enters the number to be dialed which is transmitted as DMTF tones to the Smartnode that passes the tones to the PSTN. The PSTN completes the call to the number dialed.
Since there isn't SIP server, direct IP address or DNS calling can be used to send the SIP call directly to a Smartnode gateway with an PSTN connection.
To make calling easier on on the end user associate a speed dial button, like the telephone keypad number "9", with the IP address or DNS name of Smartnode.
Optionally the SL4050/10 phone has 10 line buttons that can be set as speed dial buttons. All the end user would do is push a line button and the next thing they would hear is a PSTN dial tone pass through by the Smartnode.
Please see the "FXO Interface Configuration" in the Smartnode configuration guide for information on setting up the Smartnode to pass dialtone from the PSTN to a SIP call.
From the SL4050 web configuration interface -
Select Line Key Settings
Pick a free line key and select "one touch dial"
Enter the DNS name or IP address of the Smartnode gateway that has the PSTN FXO connection
Click on "submit" to save the changes
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:
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
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.
General
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.
Overflow handling, if input to SmartNode is higher than maximum output. Can the overflowing calls be sent via the fall-back ISDN-line?
The WAN access speed is expected to be large enough to handle all voice connections on the SmartNode. Moreover the voice portion of the used access bandwidth is expected to be small with respect to total bandwidth. For example a DSL access with 700kbps or more may be used for 4 voice channels (SOHO, SME) applications. A subscriber with an ISDN PRI interface is expected to have at least 2Mbps access speed. In such a configuration there can be no voice overflow in the SmartNode. The fallback connection is used if a call cannot be established at set-up, because the network is down or congested or because the opposite gateway is not available.
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.
Hardware Interfaces
When do I need ISDN line power?
An ISDN S-Bus can provide up to 8W of 40V DC power. Many ISDN Phones draw their operating power from the ISDN S-Bus. This is usually not the case for PBX systems which are typically local mains powered. Check the technical specifications of your ISDN terminal equipment to find out if line power is required.
Does the ISDN port provide ISDN line power?
It depends on the model.
SmartNode 4634 and 4638 can be software configured to provide line power to terminals. Smart-DTA always provides line power.
All other SmartNodes don't provide line power. However, they do forward
line power received on the TE port to the NT port. So if a public ISDN-PSTN line is connected
to the TE port and this line provides power then the power will be available to the Terminals
connected to the NT port of e.g. the SN4552.
Optionally if there is no line connected to the TE port you can install the PM-BRI-EXT S-Bus
phantom power supply to power Terminals connected to the NT port.
An ISDN S-Bus can provide up to 8W of 40V DC power. Many ISDN Phones draw their operating power from the ISDN S-Bus.
This is usually not the case for PBX systems which are typically local mains powered. Check the technical specifications of your ISDN terminal equipment to find out if line power is
required.
What is the difference between BRI NT and TE?
The ISDN BRI interface is a User-Network Interface (UNI). It has an asymmetric behavior. The two sides are denominated by NT and TE.
TE ports Are found on ISDN Terminals (ISDN phones or PBX trunk ports) NT ports Are found on the NT (Network Termination) box. An NT port always connects to a TE port and vice versa. The pinout of the ports is such that you can use straight cable to connect to the respective ISDN equipment.
The analog facsimile attached to a terminal adapter (which in turn is connected to a S0 interface of the SmartNode) does not send the called party number. Why?
Analog faxes wait for a dial tone prior to send the called party number. Despite this the terminal adapter sends a setup message when hooking off the phone receiver (without called party number information element). If the routing tables of the SmartNode are configured such that any called party number is accepted no dial tone will be sent to the fax which means that the fax never sends the called party number dialled. Make sure that the routing tables are programmed such that a dial tone (continuous tone signal) is generated.
When connecting a BRI SMartNode to a PBX trunk line I have bit-slips and problems with fax connections. How to solve this synchronization problem?
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.
Is a reboot required when changing the mode of the ISDN interfaces (net/usr)?
Yes, even twice since the PLDs must be reprogrammed before parsing the CLI file.
Licenses
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.
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
Upgrading/TFTP
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.
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.
Gateways 