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 5. Web Management
Version 5.0 109 October 2006
Table 5-13: Call Counters Description (continues on pages 108 to 109)
Counter Description
Number of Failed Calls
due to a Busy Line
This counter indicates the number of calls that failed as a result of a busy line. It is
incremented as a result of the following release reason:
GWAPP_USER_BUSY (17)
Number of Failed Calls
due to No Answer
This counter indicates the number of calls that weren’t answered. It is incremented as a
result of one of the following release reasons:
GWAPP_NO_USER_RESPONDING (18)
GWAPP_NO_ANSWER_FROM_USER_ALERTED (19)
And (when the call duration is zero) as a result of the following:
GWAPP_NORMAL_CALL_CLEAR (16)
Number of Failed Calls
due to No Route
This counter indicates the number of calls whose destinations weren’t found. It is
incremented as a result of one of the following release reasons:
GWAPP_UNASSIGNED_NUMBER (1)
GWAPP_NO_ROUTE_TO_DESTINATION (3)
Number of Failed Calls
due to No Matched
Capabilities
This counter indicates the number of calls that failed due to mismatched gateway
capabilities. It is incremented as a result of an internal identification of capability
mismatch. This mismatch is reflected to CDR via the value of the parameter
‘DefaultReleaseReason’ (default is GWAPP_NO_ROUTE_TO_DESTINATION (3)), or
by the GWAPP_SERVICE_NOT_IMPLEMENTED_UNSPECIFIED(79) reason.
Number of Failed Calls
due to Other Failures
This counter is incremented as a result of calls that fail due to reasons not covered by
the other counters.
Percentage of
Successful Calls
The percentage of established calls from attempted calls.
Average Call Duration
[sec]
The average call duration of established calls.
Attempted Fax Calls
Counter
This counter indicates the number of attempted fax calls.
Successful Fax Calls
Counter
This counter indicates the number of successful fax calls.
5.7.1.3 Call Routing Status
The Call Routing Status screen provides you with information on the current routing
method used by the gateway. This information includes the IP address and FQDN (if used)
of the Proxy server the gateway currently operates with.
Figure 5-37: Call Routing Status Screen
Table 5-14: Call Routing Status Parameters
Parameter Description
Current Call-Routing Method
Proxy = Proxy server is used to route calls.
Routing Table preferred to Proxy = The Tel to IP Routing table takes
precedence over a Proxy for routing calls (PreferRouteTable = 1).
Routing Table = The Tel to IP Routing table is used to route calls.
Current Proxy
Not Used = Proxy server isn’t defined.
IP address and FQDN (if exists) of the Proxy server the gateway currently
operates with.
Current Proxy State
N/A = Proxy server isn’t defined.
OK = Communication with the Proxy server is in order.
Fail = No response from any of the defined Proxies.