From innovaphone wiki
Jump to navigation Jump to search
There are also other versions of this article available: Reference | Reference8 | Reference9 | Reference11r1 | Reference13r1 | Reference13r3 (this version)

On this page a physical interface (ISDN or FXS) can be configured for Gateway use. Number mapping may be configured to normalize the called and calling numbers for internal use. An interface may be registered to a gatekeeper. If this is configured a VOIP interface and routes are generated automatically.

General Configuration

Name of the interface. This name is used for local administration only (e.g. displayed in the routing table)
Used to disable the interface without deleting the config
By default (after a factory reset) enabled. It allows a user to enter a v13 provisioning code. If the interface is not configured through provisioning, the Provisioning checkmark must be disabled, otherwise outgoing calls are not possible (even if the interface is registered).
This configures the tone scheme for this interface
Send Date/Time
If this checkmark is set, the current local time will be transmitted within ISDN connect messages. There is ISDN equipment using this to set the local time
Set Date/Time
If this checkmark is set the Date/Time-information received in connect messages from this interface is used to set the system time.
This works only if the Date/Time information is provided as local time and the timezone is set according to this local time.
The accuracy of Date/Time information is +/- 1min, so the system time is changed only if it is more than 1.5min different from the received information.
Please note that it is strongly recommended to use an NTP server instead, as it has better accuracy.
Ack incoming call
If this checkmark is set, a SETUP-ACK or CALL-PROC message is sent back on incoming calls right away. This should not be necessary, but it can happen that a PBX object is sending a CONN as first message to incoming calls and even though this is perfectly according standard, some old style PBXs don't like it.

Interface Maps

The number mapping on the interface can be either configured manually, or predefined mappings for ISDN Point to Point or ISDN Point to Multipoint interfaces can be used. If predefined mappings are used they can be edited the same way as manual mappings, but if they are changed they are not recognized as predefined mapping any more. Please read also Reference13r3:Gateway/Interfaces#ISDN interfaces (PPP, TEL1-4, BRI1-4, PRI1-4)

Point to Point

With the use of a few parameters the Point to Point mapping maps between an external representation of the numbers using the type of number field and an internal representation using Unknown as type of number and prefixes.

Area Code The prefix used to convert from a subscriber number to a national number
Subscriber Number The prefix used to convert from an extension to a subscriber number
National Prefix The prefix used to mark a number as National
International Prefix The prefix used to mark a number as International

Point to Multipoint

With the use of a few parameters the Point to Point mapping maps between an external representation of the numbers using the type of number field and an internal representation using Unknown as type of number and prefixes. Three external numbers (MSNs) are mapped to internal extensions.

MSN1-3,Ext. The external subscriber numbers and the internal extensions they are mapped to.
National Prefix The prefix used to mark a number as National
International Prefix The prefix used to mark a number as International

Internal Registration


Registration to a Gatekeeper/PBX

Gatekeeper Address (primary/secondary)
The registration addresses of the PBX/Gatekeeper. If no adress is configured, Gatekeeper Discovery is used
Gatekeeper ID
ID of the Gatekeeper. On a innovaphone PBX, this is the System Name. It is recommended to configure this to avoid registration to the wrong PBX.
H.323 Id used for the registration. If no name and no number is configured a name of the form <product-short-name>-<last 3 Bytes of Mac Address>-<Interface Id> (e.g. IP800-08-03-01-TEL2) is used instead.
The number used for the registration. Typically only name or number is required.
Password used for authentication if needed.
Prefer installed certificate
Uses the installed certificate for H323/TLS registrations, instead of the device certificate signed by the innovaphone CA.


Registration to a SIP Server

Media Properties

The physical interface may be registered using H.323 or SIP. For the VOIP call the media properties can be configured.

General Coder Preference
The coder preference (Coder, Framesize, Silence Compression) to be used if a non-local media address is detected. If the preference is marked as exclusive no other coder is offered.
Local Network Coder
The coder preference if a local media address is detected.
Enable T.38
Switches on Fax detection and switchover to T.38
Audio FAX support
Switches on voice coder e.g. G.711 for the FAX interface. This feature requires two free DSP channels and is not available on all gateway models. See column Audio Fax Ch out of Fax Ch in the table Technical data and recommended number of users supported in How_to_implement_large_PBXs.
No DTMF Detection
Special mode to switch off DTMF detection during a call. If checked DTMF is transferred inband during a call. Use G711 coder and a link with no packet loss to transfer DTMF inband. This option can be used to transfer continuous DTMF tones for some special applications. Out of band DTMF tones have a fixed length of approx 150ms.
Enable PCM
Enable the media to be connected using the local timeslot switch if the call is between physical interfaces of the same gateway.
MOH Mode
Special mode to use a physical interface as Music on Hold Source. The media is one way only and multiple calls are connected to the same channel on the physical interface. In this case the configured coder is used exclusively, even if not marked as exclusive.
Record to (URL)
HTTP URL where the recording file is to be stored. HTTP server must allow write access (PUT) at this location. One PCAP file is written for every call via this interface containing both RTP streams. Audio streams can be played using Wireshark. PCAP file can be converted into WAV file using pcap2wav tool. The filename of the recording file has the form <conference ID>-<mac>-<seq>.pcap
conference ID
A guid identifying the call across different hops. It is forwarded within the signaling. The CDRs generated by the PBX contain this conference ID.
The Mac address of the device recording the call. Together with seq it is used to make sure the filename is unique if separate devices record the same call.
A sequence number of the record starting with 0 after power up of the recording device. Together with mac it is used to make sure the filename is unique, especially to cover the case, that one device records the same call multiple times (e.g. incoming and outgoing)

Feature Code Support

The Feature Code Support turns on Supplementary services for a single endpoint connected to the physical interface, which can be invoked using *# dial sequences. This is available on FXS interfaces only. See Reference:Feature Codes for details about features available.

Dynamic Group
The name of the group which membership can be changed using *# sequences from the endpoint.
Direct Dial
Number to be dialed on off-hook. This only works if feature code support is enabled.
Locked White List
A white-list of numbers, separated by ',' which may be still dialed if the endpoint is locked using *# sequences.