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

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

context ip
  interface eth0
  no icmp router-discovery

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 2300 IC-4FXS card is FXS

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