Version 5.2/5.4 29 January 2009
Troubleshooting Guide 4. Call Setup
Possible Cause Solution
When a Proxy server isn’t used, the destination IP address
must be defined in the Web interface's 'Tel to IP Routing'
page (Web path SW Ver. 5.2: Protocol Management menu >
Routing Tables submenu > Tel to IP Routing; Web path SW
Ver. 5.4 and later: Configuration tab > Protocol Configuration
menu > Routing Tables submenu > Tel to IP Routing).
3.
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's '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 digital devices, and in the '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) for
MediaPack Series devices.
4.
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.
5.
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).
6.
The device is operating behind
NAT (a STUN server is not
available).
Verify that public IP address declared for the device
appears in the SDP of the SIP INVITE message. To verify
and configure the setting, use the 'NAT IP Address'
parameter in the Web interface's 'IP Settings' page (Web
path SW Ver. 5.2: Advanced Configuration menu > Network
Settings submenu > IP Settings; Web path SW Ver. 5.4 and
later: Configuration tab > Network Settings menu > IP
Settings).
7.
The remote peer is operating
behind NAT.
If no SIP messages are received, check that the
Firewall/NAT server forwards incoming traffic from the
public IP address to the internal IP address of the device.
If a SIP 200 OK message is received, verify that it contains
the public IP address of the remote peer. If the remote peer
uses an internal IP address, contact the Firewall/NAT server
administrator to verify that the remote peer uses and
declares its public IP address.
To Next Page
Loading...
Need help?
General
