AudioCodes MP-11 User manual

Document #: LTRT-57601 January 2009
CPE Troubleshooting Guide

Version 5.2/5.4 3 January 2009
Troubleshooting Guide Contents
Contents
1Introduction......................................................................................................... 7
2IP Connectivity.................................................................................................... 9
2.1I Cannot Access Web or Ping the Device ................................................................9
2.2How Do I Ping a Network Entity from the Device...................................................10
3TDM (PSTN) Connectivity ................................................................................ 13
3.1How Do I Clear Trunk Alarms.................................................................................13
3.2How Do I Check a Trunk's Physical Integrity..........................................................15
3.3How Do I Check for E1/T1 Clock Slips...................................................................15
3.4How Do I Switch Between E1 and T1 Trunk Protocol Types .................................16
3.5Why Can't I Stop an Active Trunk...........................................................................17
3.6How Do I Configure PSTN Clock Synchronization.................................................17
4Call Setup.......................................................................................................... 19
4.1How Do I Troubleshoot IP-to-Tel Call Setup..........................................................19
4.1.1Initial IP-to-Tel Troubleshooting..............................................................................20
4.1.2Advanced IP-to-Tel Troubleshooting for Digital Interfaces.....................................23
4.1.3Advanced IP-to-Tel Troubleshooting for FXS Interfaces........................................24
4.1.4Advanced IP-to-Tel Troubleshooting for FXO Interfaces (1-Stage Dialing) ...........25
4.1.5Advanced IP-to-Tel Troubleshooting for FXO Interfaces (2-Stage Dialing) ...........27
4.2How Do I Troubleshoot Tel-to-IP Call Setup..........................................................28
4.2.1How Do I Check Device (Tel-to-IP) Connectivity....................................................28
4.2.2Initial Call Setup Troubleshooting...........................................................................28
4.2.3Advanced Tel-to-IP Troubleshooting for Digital Interfaces.....................................32
4.2.4Advanced Tel-to-IP Troubleshooting for FXO Interfaces........................................34
4.2.5Advanced Tel-to-IP Troubleshooting ...................................................................... 36
5Caller ID............................................................................................................. 39
5.1Why Doesn't the FXO Device Detect Caller ID ......................................................39
5.2Why Doesn't the Phone Detect Caller ID (FXS).....................................................41
5.3Why Doesn't Digital Device Detect Tel-to-IP Caller ID...........................................42
5.4Why Doesn't Digital Device Generate Caller ID to Tel...........................................42
6Voice Quality..................................................................................................... 43
6.1How Do I Troubleshoot Distorted Voice.................................................................43
6.2How Do I Troubleshoot Voice Echo .......................................................................44
6.3How Do I Troubleshoot Voice Delay ......................................................................46
7Call Disconnect................................................................................................. 47
7.1Why Doesn't the FXO End a PBX/PSTN Call ........................................................47
7.2Why Do Calls Randomly Disconnect?....................................................................49
7.3Why Don't Calls Disconnect Upon ISDN Disconnect Message..............................50
7.4Why Does the PBX Disconnect IP-to-Tel Calls......................................................50

Troubleshooting Guide 4 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
8Fax and Modem ................................................................................................ 51
8.1Why Do Fax Sessions Fail.....................................................................................51
9Call Transfer...................................................................................................... 55
9.1Why Does PBX Terminate Call Transfer by the FXO Device.................................55
9.2Why Can't I Transfer a Call Between FXS Interfaces.............................................56
10IP Voice Mail and Unified Messaging.............................................................. 57
10.1I Cannot Retrieve Voice Mail Messages ................................................................57
10.2Why Does IP Voice Mail Request My Extension Number for Retrieving Voice Mail
57
10.3I Cannot Leave Voice Mail Messages....................................................................58
10.4Message Waiting Indication Does Not Function.....................................................59
10.5I Cannot Transfer Calls to Users in Unified Messaging..........................................60
11Common Web, SNMP and ini File Issues ....................................................... 61
11.1How Do I Restore Web Interface Username and Password Without Losing
Configuration ...................................................................................................................61
11.2How Do I Obtain the Complete ini File ...................................................................61
11.3Where Do I Place a Parameter in the ini File.........................................................61
11.4How Can I Update the ini File Via SNMP...............................................................61
11.5How Do I Obtain the ini File Via SNMP..................................................................62
11.6How Do I Change Web Username and Password Via SNMP................................62
11.7How Do I Reset the Device Via SNMP
...................................................................62
11.8How Do I Force the Device to Send a SIP REGISTER via SNMP.........................62
11.9How Do I Remove/Insert Mediant 1000 Modules Via SNMP .................................63
11.10How Do I View PSTN Alarms Via SNMP................................................................63
11.11How Do I Work with Row-Status ............................................................................63
11.12Why Doesn't BootP Install on Windows Vista ........................................................64
12Traffic Debug Analysis.................................................................................... 65
12.1Why Can't I Record the Device's Traffic.................................................................65
12.2Why Doesn't Wireshark Decode Messages...........................................................65
13Debugging Procedures.................................................................................... 67
13.1Case Reporting Procedures...................................................................................67
13.2Syslog.....................................................................................................................68
13.3Wireshark Network Sniffer......................................................................................69
13.4CLI Debug Recording.............................................................................................73
14Management Utilities........................................................................................ 77
14.1CPTWizard.............................................................................................................77
14.2BootP/TFTP Server................................................................................................77

Version 5.2/5.4 5 January 2009
Troubleshooting Guide Notices
Notice
This document provides troubleshooting procedures for AudioCodes customer premises
equipment (CPE), Voice-over-IP (VoIP) media gateway devices.
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published nor can it accept responsibility
for errors or omissions. Updates to this document and other documents can be viewed by
registered customers at http://www.audiocodes.com/downloads.
© Copyright 2009 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: January-05-2009
Tip: When viewing this manual on CD, Web site or on any other electronic copy,
all cross-references are hyperlinked. Click on the page or section numbers
(shown in blue) to reach the individual cross-referenced item directly. To
return back to the point from where you accessed the cross-reference, press
the ALT and Åkeys
Trademarks
AC logo, Ardito, AudioCoded, AudioCodes, AudioCodes logo, CTI², CTI Squared, InTouch,
IPmedia, Mediant, MediaPack, MP-MLQ, NetCoder, Netrake, Nuera, Open Solutions
Network, OSN, Stretto, 3GX, TrunkPack, VoicePacketizer, VoIPerfect, What's Inside
Matters, Your Gateway To VoIP, are trademarks or registered trademarks of AudioCodes
Limited. All other products or trademarks are property of their respective owners.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.
Customer Support
Customer technical support and services are provided by AudioCodes’ Distributors,
Partners, and Resellers from whom the product was purchased.
For technical support for products purchased directly from AudioCodes and for
customers registered to AudioCodes’ iSupport, logon to http://crm.audiocodes.com.
For all other AudioCodes’ customers, contact [email protected].

Troubleshooting Guide 6 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
Reader’s Notes

Version 5.2/5.4 7 January 2009
Troubleshooting Guide 1. Introduction
1 Introduction
This guide is intended to assist you in troubleshooting various problems that may arise in
your network environment in which AudioCodes' VoIP gateway (hereafter referred to as
device) is deployed.
This guide includes troubleshooting concerning the following AudioCodes SIP CPE devices:
MediaPack Series MP-11x and MP-124
Mediant 600
Mediant 1000
Mediant 2000
This guide is organized into topics based on troubleshooting areas, for example,
troubleshooting voice quality or troubleshooting caller ID, and includes topics describing
various debugging and management tools that can aid you in the troubleshooting process:
''IP Connectivity'' on page 9
''TDM (PSTN) Connectivity'' on page 13
''Call Setup'' on page 19
''Caller ID'' on page 39
''Voice Quality'' on page 43
''Call Disconnect'' on page 47
''Fax and Modem'' on page 51
''Call Transfer'' on page 55
''IP Voice Mail and Unified Messaging'' on page 57
''Common Web, SNMP and ini File Issues'' on page 61
''Traffic Debug Analysis'' on page 65
''Debugging Procedures'' on page 67
''Management Utilities'' on page 77
The troubleshooting topics are presented either in table format or FAQ format. The table
format (shown below), includes possible causes of the problem and corresponding
solutions to the problem. These causes and solutions are organized in chronological order,
starting from the top of the table.
Table 1-1: Example of a Table Format for Troubleshooting
Possible Cause Solution
a. Cause 1 Solution 1
b. Cause 2 Solution 2
For the procedure on how to report troubleshooting issues, refer to ''Case Reporting
Procedures'' on page 67.

Troubleshooting Guide 8 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
Reader’s Notes

Version 5.2/5.4 9 January 2009
Troubleshooting Guide 2. IP Connectivity
2 IP Connectivity
This section discusses troubleshooting for IP connectivity problems:
''I Cannot Access Web or Ping the Device'' on page 9
''How Do I Ping a Network Entity from the Device'' on page 10
2.1 I Cannot Access Web or Ping the Device
Table 2-1: No Web Access or Ping to the Device Troubleshooting
Possible Cause Solution
1. The device is not receiving
power. 1 Verify that the LED for power is on.
2 If the Power LED is off, verify that the power cable is
securely connected to the device and that the power
source is functional. If both the cable and power source
are ok, replace the device.
2. The software version is not
loaded to the device. 1 Verify that the Fail LED is off.
2 If the Fail LED is lit red, use a BootP application to burn
the firmware version to the device's flash memory (refer
to ''BootP/TFTP Server'' on page 77).
3 If the LED is still on, replace the device.
3. The Ethernet link is down. 1 Verify that the device's Link LED is on.
2 If the Link LED is off:
a. Ensure that the Ethernet cable is securely
connected to the device's Ethernet port.
b. Use a direct network crossover cable to connect
directly the device to a PC to rule out any potential
network issues.
c. Ensure that the port on the Ethernet switch is
functioning (and the switch is powered on).
d. Ensure that the speed and connection mode of the
switch is the same as the speed and connection
mode of the device (for example, if the switch is
configured for 100 Mbps full-duplex and the device
is configured for 10 Mbps half-duplex, no Ethernet
link can be established). the device's Ethernet speed
and mode is configured by the ini file parameter
EthernetPhyConfiguration.
e. If necessary, use the reset button on the device's
front panel to restore the configuration to its factory
default settings (refer to the device's User's Manual).

Troubleshooting Guide 10 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
Possible Cause Solution
4. The IP address assigned to the
device is not suitable for your
network environment, or the
device's IP address is unknown
(forgotten).
1 Discover the device's IP address: The simplest method
is to start the Wireshark application (refer to ''Wireshark
Network Sniffer'' on page 69), reset the device and wait
for it to startup. When the device boots, it sends a
Gratuitous ARP (GARP) message with its IP address.
2 Assign a new IP address to the device, using BootP or
DHCP.
Note: The device may change its IP address each time it is
reset even though DHCP is disabled. Many DHCP servers
are backward-compatible with BootP protocol and can be
used for device configuration. These DHCP servers reply to
BootP requests sent by the device. To configure the device
to ignore these BootP replies, set the ini file parameter
BootPSelectiveEnable to 1. The Selective BootP
mechanism enables the device's integral BootP client to
filter unsolicited BootP/DHCP replies (accepts only BootP
replies that contain the text ‘AUDC’ in the Vendor Specific
Information field).
2.2 How Do I Ping a Network Entity from the Device
The procedure below describes how to ping a network entity from the device.
¾To ping a network entity from the device:
1. Access the device's FAE page: in your Web browser's URL field, append the case-
sensitive suffix "FAE" to the device's IP address (e.g., http://10.1.229.17/FAE).
Figure 2-1: FAE Page
2. On the left pane, click the Cmd Shell link; the 'CmD Shell' window opens.

Version 5.2/5.4 11 January 2009
Troubleshooting Guide 2. IP Connectivity
3. In the 'Command-Line' field, enter the following command:
ping [IP address of the remote destination]
For example, ping 10.33.2.34.
4. Wait several seconds and then enter the following command:
show ping
The following information is displayed:
ping 10.33.2.34
Ping process started for address 10.33.2.34. Process ID - 23.
Reply from 10.33.2.34: bytes=0 time=0ms
Reply from 10.33.2.34: bytes=0 time=0ms
Reply from 10.33.2.34: bytes=0 time=0ms
Reply from 10.33.2.34: bytes=0 time=0ms
Ping statistics for 10.33.2.34:
Packets: Sent = 4, Received = 4, Lost 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Troubleshooting Guide 12 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
Reader’s Notes

Version 5.2/5.4 13 January 2009
Troubleshooting Guide 3. TDM (PSTN) Connectivity
3 TDM (PSTN) Connectivity
This section discusses troubleshooting for TDM (PSTN) connectivity:
''How Do I Clear Trunk Alarms'' on page 13
''How Do I Check a Trunk's Physical Integrity'' on page 15
''How Do I Check for E1/T1 Clock Slips'' on page 15
''How Do I Switch Between E1 and T1 Trunk Protocol Types'' on page 16
''Why Can't I Stop an Active Trunk'' on page 17
3.1 How Do I Clear Trunk Alarms
The status of the E1/T1 Trunks is displayed in the Home page of the device's Web
interface. The Trunk status icon should be lit green for normal functioning; otherwise, refer
to the table below for possible alarms.
RJ-48c trunk connectors are wired according to the figure below:
Figure 3-1: RJ-48c Connector Pinouts for E1/T1

Troubleshooting Guide 14 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
Table 3-1: No Access or Ping to Gateway
Trunk Icon Status Possible Cause Solution
Color Alarm
Gray Trunk
Disabled The Trunk is not configured Configure the Trunk in the Web interface's 'Trunk Settings' page.
Note: If the ‘Protocol Type’ field displays 'NONE' (i.e.,
no protocol type selected) and no other trunks have
been configured, after selecting a PRI protocol type, you
must reset the device.
Red Loss of
Signal
(LOS)
or
Loss of
Frame
(LOF)
LOS: Indicates a
physical problem.
LOF: Indicates that
the Trunk port is
not receiving
framing, or has lost
synchronization on
the received
framing.
To clear the LOS alarm, ensure the following:
1 The E1/T1 cable is connected securely between the
device's PSTN ports and the service provider's
equipment (PSTN network).
2 The E1/T1 trunk cable is not physically damaged; if
so, replace the cable.
3 The E1/T1 cable is crimped correctly (refer to the
figure above).
4 The correct E1/T1 cable is used (crossover /
straight). If a straight cable is being used and LOS is
still present, try a crossover cable, and vice versa.
To clear the LOF alarm, ensure the following:
1 The PBX and device are configured to use the same
Trunk type (E1 or T1).
2 The Framing method of the PBX and device is
identical.
3 The Line code of the PBX and device is identical.
4 The clocks are synchronized (refer to ''How Do I
Check for E1/T1 Clock Slips'' on page 15).
Yellow Remote
Alarm
Indication
(RAI)
The far-end
equipment (e.g.,
PBX) has a
problem with the
signal that it
receives from the
local equipment.
Contact the PBX/PSTN provider and report this alarm to
resolve the problem.
Orange D-Channel -- To clear this alarm, perform the following:
1 Ensure that the correct ISDN variant is selected.
2 If the device is configured as User side, ensure that
the PBX/PSTN is configured as Network side, and
vice versa.
3 Ensure that the Framing method configured for the
device is the same as the Framing method on the
PBX/PSTN.
4 If the D-channel alarm isn’t cleared, contact the
AudioCodes Technical Support team and provide
them with the ini file of the device and a PSTN trace
(refer to ''CLI Debug Recording'' on page 72).

Version 5.2/5.4 15 January 2009
Troubleshooting Guide 3. TDM (PSTN) Connectivity
3.2 How Do I Check a Trunk's Physical Integrity
¾To check the trunks physical integrity (no hardware problem),
perform the following test:
1. Use a crossover RJ-48 cable to make a loop between two active Trunks on the device.
2. In the Web interface's ‘Trunk Settings’ page (Web path SW Ver. 5.2: Advanced
Configuration menu > Trunk Settings; Web path SW Ver. 5.4 and later: Configuration
tab > PSTN Settings menu > Trunk Settings), configure the following:
a. In the 'Protocol Type' field, configure the same protocol type for both Trunks to E1
(or T1) Transparent 30 (or set the ini file parameter ProtocolType to 6).
b. In the 'Clock Master' field, configure any one of the Trunks to "Recovered" and
the other to "Generated" (or set the ini file parameter ClockMaster to 0 and 1
respectively).
3. Verify that the LEDs of both Trunks are lit green.
3.3 How Do I Check for E1/T1 Clock Slips
If timing between devices is not maintained, a condition known as clock slippage (or clock
slips) can occur. By definition, a clock slip is the repetition or deletion of a bit (or block of
bits) in a synchronous data stream, due to a discrepancy in the read and write rates at a
buffer. Slips arise because an equipment buffer store, or other mechanisms, cannot
accommodate differences between the phases or frequencies of the incoming and outgoing
signals. This occurs in cases where the timing of the outgoing signal is not derived from that
of the incoming signal.
¾To check for clock slips on the trunk and that the clock is
synchronized:
1. Access the command shell, and then at the CLI prompt, enter the following
commands:
pstn
physical
PstnGetPerformanceMonitoring [trunk number] 0
Note: Trunks are numbered from 0 to 7.
2. Copy the information that appears in the CLI output window and send it to the
Technical Support Department.

Troubleshooting Guide 16 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
Below is an example of the CLI output when using these commands:
pstn
CAS/ PHysical/ PstnCOmmon/
/PStn>
physical
IsdnGetDChannelStatus PstnQueryTrunkStatus PstnSendAlarm
PstnLoopCommands PstnGetPerformanceMonitoring
PstnStoPPerformanceMonitoring PstnStarTPerformanceMonitoring
/PStn/PHysical>
PstnGetPerformanceMonitoring 0 0
TrunkId = 0
Interval = 0
3.4 How Do I Switch Between E1 and T1 Trunk Protocol
Types
¾To switch from E1 to T1 (or vice versa):
1. Save the device's current configuration (ini file) to a folder on your PC, using the Web
interface's 'Configuration File' page (Web path SW Ver. 5.2: Save Configuration menu;
Web path SW Ver. 5.4 and later: Management tab > Software Update submenu >
Configuration File).
2. Open the saved ini file, using a plain text editor (such as Notepad).
3. Change the value of the parameter ProtocolType_x to the required protocol type.
4. Reload the modified ini file to the device, using the Web interface's 'Configuration File'
page.

Version 5.2/5.4 17 January 2009
Troubleshooting Guide 3. TDM (PSTN) Connectivity
3.5 Why Can't I Stop an Active Trunk
Table 3-2: Active Trunk Can't be Stopped Troubleshooting
Possible Cause Solution
1. The Trunk provides the device's
clock. When the clock source is internal (i.e., the device receives clock synchronization from a specific Trunk), you cannot
stop this Trunk (assuming that the device is synchronized
with the E1/T1 clock). When you try stopping a Trunk that
provides clock synchronization, the Web interface displays a
warning message notifying you of this.
A Trunk that is not used to supply the clock can be stopped
and if the clock source is from the network, any Trunk can
be stopped.
In the Web interface's 'TDM Bus Settings' page (Web path
SW Ver. 5.2: Advanced Configuration menu > TDM Bus
Settings; Web path SW Ver. 5.4 and later: Configuration tab
> TDM Configuration menu > TDM Bus Settings), perform
one of the following:
Assign a different E1/T1 Trunk to provide the device's
clock, using the 'TDM Bus Local Reference' field (or the
ini file parameter TDMBusLocalReference).
Enable the PSTN Trunk auto-fallback clock feature,
using the ‘TDM Bus PSTN Auto Clock’ field (or the ini file
parameter TDMBusPSTNAutoClockEnable).
3.6 How Do I Configure PSTN Clock Synchronization
In a PSTN network, it is important to verify that all components are synchronized to a
single clock source. Several problems (such as, echo, fax and modem failures) can be
caused if the clocks aren’t synchronized. Incorrect configuration can occur for example,
when the device is configured to provide a clock source to a specific E1 Trunk and at the
same time, the PBX is also configured to provide a clock source on the same Trunk.
Refer to ''How Do I Check for E1/T1 Clock Slips'' on page 15 for information on how to
verify whether the device's clocks are synchronized.
The device can be configured to generate its own timing signals using an internal clock, or
recover them from one of the E1/T1 trunks.
¾To use the device's internal clock source:
To generate the clock from a local source, set the ini file parameter
TDMBusClockSource to 1 (or the corresponding Web interface parameter 'TDM Bus
Clock Source' to "Internal").

Troubleshooting Guide 18 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
For all Trunks, set the ini file parameter ClockMaster to 1 (or the corresponding Web
interface parameter 'Clock Master ' to "Recovered"). This parameter determines the Tx
clock source of the E1/T1 lines.
Figure 3-2: Clock Synchronization from Device
¾To use the recovered clock option:
1. Set the ini file parameter TDMBusClockSource to 4 (or the corresponding Web
interface parameter 'TDM Bus Clock Source' to "Network").
2. For all ‘slave’ trunks connected to the PSTN, set the ini file parameter ClockMaster_x
to 0 (or the corresponding Web interface parameter 'Clock Master' to "Recovered").
3. For all ‘master’ trunks connected to the PBX, set the ini file parameter ClockMaster_x
to 1 (or the corresponding Web interface parameter 'Clock Master' to "Generated").
Figure 3-3: Clock Synchronization from PSTN
The example above assumes that the device recovers its internal clock from one of the
‘slave’ trunks connected to the PSTN and provides a clock source to the PBX on its ‘master’
trunks. In addition, you must define from which of the ‘slave’ Trunks the device recovers its
clock. The following two options are available:
To recover the clock from a specific E1/T1 line, use the ini file parameter
TDMBusLocalReference (range: 1-8 on the Web interface, 0-7 on ini file)
Set the ini file parameter TDMBusPSTNAutoClockEnable to 1 to recover the clock
from any connected synchronized slave E1/T1 line. If this Trunk loses its
synchronization, the device attempts to recover the clock from the next Trunk. Note
that initially, the device attempts to recover the clock from the Trunk defined by the ini
file parameter TDMBusLocalReference.

Version 5.2/5.4 19 January 2009
Troubleshooting Guide 4. Call Setup
4 Call Setup
This section discusses troubleshooting for call setup (or call establishment):
''How Do I Troubleshoot IP-to-Tel Call Setup'' on page 19
''How Do I Troubleshoot Tel-to-IP Call Setup'' on page 27
4.1 How Do I Troubleshoot IP-to-Tel Call Setup
This sections deals with troubleshooting for IP-to-Tel call setup:
''Initial IP-to-Tel Troubleshooting'' on page 20
''Advanced IP-to-Tel Troubleshooting for Digital Interfaces'' on page 23
''Advanced IP-to-Tel Troubleshooting for FXS Interfaces'' on page 24
''Advanced IP-to-Tel Troubleshooting for FXO Interfaces (1-Stage Dialing)'' on page 25
''Advanced IP-to-Tel Troubleshooting for FXO Interfaces (2-Stage Dialing)'' on page 27

Troubleshooting Guide 20 Document #: LTRT-57601
MediaPack, Mediant 1000, Mediant 2000
4.1.1 Initial IP-to-Tel Troubleshooting
Table 4-1: Initial Troubleshooting for IP-to-Tel Call Setup
Possible Cause Solution
1. The ports/Trunks/B-channels
are not defined. Ensure that the ports, Trunks, or B-channels involved in the call are defined (enabled) for the device. This is performed in
the Web interface:
For digital devices: 'Trunk Group Table' page (Web path
SW Ver. 5.2: Protocol Management menu > Trunk
Group; Web path SW Ver. 5.4 and later: Configuration
tab > Protocol Configuration menu > Trunk Group
submenu > Trunk Group)
For MediaPack Series devices: 'Endpoint Phone Number
Table' page (Web path SW Ver. 5.2: Protocol
Management menu > Endpoint Phone Numbers; Web
path SW Ver. 5.4 and later: Configuration tab > Protocol
Configuration menu > Endpoint Number submenu >
Endpoint Phone Number)
2. IP-to-Tel call routing are not
defined or incorrectly
configured.
If you have defined Trunk/Hunt Groups (in the Web
interface's 'Trunk Group Table' page for digital devices, and
in the 'Endpoint Phone Number Table' page for MediaPack
Series devices), ensure that you have also defined IP-to-
Trunk/Hunt Group routing on the Web interface's 'IP to
Trunk/Hunt Group Routing Table' page (Web path SW Ver.
5.2: Protocol Management menu > Routing Tables submenu
> IP to Trunk/Hunt Group Routing; Web path SW Ver. 5.4
and later: Configuration tab > Protocol Configuration menu >
Routing Tables submenu > IP to Trunk/Hunt Group Routing).
If no Trunk/Hunt Groups are defined, the device routes IP
calls to the default Trunk Group (i.e., 0).
3. The SIP transport layer of the
device and remote SIP User
Agent (UA) are not identical.
Ensure that the device and the remote UA use the same SIP
transport layer (i.e., UDP, TCP or TLS). The SIP transport
type is configured by the ini file parameter
SIPTransportType.
4. The voice coders of the device
and remote SIP UA are not
identical.
Ensure that the coders used by the device are the same as
the coders used by the remote UA. The device's coders are
configured in the Web interface's 'Coders Table' page (Web
path SW Ver. 5.2: Protocol Management menu > Protocol
Definition submenu > Coders; Web path SW Ver. 5.4 and
later: Configuration tab > Protocol Configuration menu >
Protocol Definition submenu > Coders).