User`s manual
Table Of Contents
- Mediant 2000 & TP-1610 & TP-260/UNI SIP User’s Manual Version 5.0
- Table of Contents
- List of Figures
- List of Tables
- Notices
- 1. Overview
- 2. Physical Description
- 3. Installation
- 4. Getting Started
- 5. Web Management
- Computer Requirements
- Protection and Security Mechanisms
- Accessing the Embedded Web Server
- Getting Acquainted with the Web Interface
- Protocol Management
- Advanced Configuration
- Status & Diagnostic
- Software Update Menu
- Maintenance
- Logging Off the Embedded Web Server
- 6. Gateway's ini File Configuration
- Secured ini File
- Modifying an ini File
- The ini File Content
- The ini File Structure
- The ini File Example
- Networking Parameters
- System Parameters
- Web and Telnet Parameters
- Security Parameters
- RADIUS Parameters
- SNMP Parameters
- SIP Configuration Parameters
- Voice Mail Parameters
- ISDN and CAS Interworking-Related Parameters
- Number Manipulation and Routing Parameters
- E1/T1 Configuration Parameters
- Channel Parameters
- Configuration Files Parameters
- 7. Using BootP / DHCP
- 8. Telephony Capabilities
- Working with Supplementary Services
- Configuring the DTMF Transport Types
- Fax & Modem Transport Modes
- Event Notification using X-Detect Header
- ThroughPacket™
- Dynamic Jitter Buffer Operation
- Configuring the Gateway’s Alternative Routing (based on Conn
- Call Detail Report
- Supported RADIUS Attributes
- Trunk to Trunk Routing Example
- Proxy or Registrar Registration Example
- SIP Call Flow Example
- SIP Authentication Example
- 9. Networking Capabilities
- 10. Advanced PSTN Configuration
- 11. Advanced System Capabilities
- 12. Special Applications
- 13. Security
- 14. Diagnostics
- 15. SNMP-Based Management
- SNMP Standards and Objects
- Carrier Grade Alarm System
- Cold Start Trap
- Third-Party Performance Monitoring Measurements
- TrunkPack-VoP Series Supported MIBs
- Traps
- SNMP Interface Details
- SNMP Manager Backward Compatibility
- Dual Module Interface
- SNMP NAT Traversal
- SNMP Administrative State Control
- AudioCodes’ Element Management System
- 16. Configuration Files
- Appendix A. Selected Technical Specifications
- Appendix B. Supplied SIP Software Kit
- Appendix C. SIP Compliance Tables
- Appendix D. The BootP/TFTP Configuration Utility
- Appendix E. RTP/RTCP Payload Types and Port Allocation
- Appendix F. RTP Control Protocol Extended Reports (RTCP-XR)
- Appendix G. Accessory Programs and Tools
- Appendix H. Release Reason Mapping
- Appendix I. SNMP Traps
- Appendix J. Installation and Configuration of Apache HTTP Server
- Appendix K. Regulatory Information

SIP User's Manual 10. Advanced PSTN Configuration
Version 5.0 245 October 2006
10.3.1 NFAS Interface ID
Several ISDN switches require an additional configuration parameter per T1 trunk that is
called ‘Interface Identifier’. In NFAS T1 trunks the Interface Identifier is sent explicitly in
Q.931 Setup / Channel Identification IE for all NFAS trunks, except for the B-channels of
the Primary trunk (refer to note 1 below).
The Interface ID can be defined per each member (T1 trunk) of the NFAS group, and must
be coordinated with the configuration of the Switch.
The default value of the Interface ID is identical to the number of the physical T1 trunk (0
for the first gateway trunk, 1 for the second gateway T1 trunk etc. up to 7).
To define an explicit Interface ID for a T1 trunk (that is different from the default), use the
following parameters:
ISDNIBehavior_x = 512 (x = 0 to 7 identifying the gateway's physical trunk)
ISDNNFASInterfaceID_x = ID (x = 0 to 255)
Notes:
• Usually the Interface Identifier is included in the Q.931 Setup/Channel
Identification IE only on T1 trunks that doesn’t contain the D-channel.
Calls initiated on B-channels of the Primary T1 trunk, by default, don’t
contain the Interface Identifier. Setting the parameter ‘ISDNIBehavior_x’
to 2048’ forces the inclusion of the Channel Identifier parameter also for
the Primary trunk.
• The parameter ‘ISDNNFASInterfaceID_x = ID’ can define the ‘Interface
ID’ for any Primary T1 trunk, even if the T1 trunk is not a part of an NFAS
group. However, to include the Interface Identifier in Q.931
Setup/Channel Identification IE configure ‘ISDNIBehavior_x = 2048’ in the
ini file.
10.3.2 Working with DMS-100 Switches
The DMS-100 switch requires the following NFAS Interface ID definitions:
InterfaceID #0 for the Primary trunk
InterfaceID #1 for the Backup trunk
InterfaceID #2 for a 24 B-channel T1 trunk
InterfaceID #3 for a 24 B-channel T1 trunk
Etc.
For example, if four T1 trunks on a gateway's are configured as a single NFAS group that
is used with a DMS-100 switch, the following parameters should be used:
ISDNNFASInterfaceID_0 = 0
ISDNNFASInterfaceID_1 = 2
ISDNNFASInterfaceID_2 = 3
ISDNNFASInterfaceID_3 = 4
NFASGroupNumber_0 = 1
NFASGroupNumber_1 = 1
NFASGroupNumber_2 = 1
NFASGroupNumber_3 = 1
DchConfig_0 = 0 ;Primary T1 trunk
DchConfig_2 = 2 ;24 B-channel NFAS trunk
DchConfig_3 = 2 ;24 B-channel NFAS trunk
DchConfig_4 = 2 ;24 B-channel NFAS trunk