Troubleshooting
235
No Server…
• Ensure that the Server/ Registrar addresses are correctly configured
! page 214 and can be pinged ! page 206 – do not attempt to ping
domain names used when configuring the phone for DNS-SRV.
If the SIP Server or SIP Registrar can not be pinged and are configured
as host names see ! page 240.
• Ensure that the phone is displaying the same time as the SIP Server. If
not see ! page 240.
• Ensure that the "Register By Name" setting ! page 210 is correct. This
should be "On" if the phone is using the Terminal Name and "Off" if the
phone is using the Terminal Number.
• Ensure that the Terminal Name ! page 222 or Number ! page 222
(depending on the "Register By Name" setting) is the same as that held
by the SIP Server.
• Ensure that the SIP Transport is correctly configured ! page 217.
• Ensure that the Outbound Proxy setting is correctly configured
! page 205. If the Outbound Proxy setting is On, the Default OBP Do-
main should be correctly configured ! page 173.
Status Reporting Error
• The most likely cause of this problem is that the phone can not contact
the SIP Server. Ensure that the SIP Server is active and can be pinged
by the phone ! page 206.
Authentication Failure or Password Error
• Check SIP Username ! page 218, SIP Password ! page 215 and SIP
Realm ! page 215 against information held in SIP Server.
• Ensure the correct time and date is displayed by the phone.
Terminal Incompatible" whenever call is attempted
To avoid compatibility problems try the following:
• Ensure that all IP endpoints in your system, including SIP Gateways,
are using compatible codec ! page 165 and/or compression
! page 169 settings. If problems persist configure all endpoints to
G.711 speech with no Silence Suppression ! page 188.
• Use packet size "Auto" for RTP ! page 212.
To Next Page
Loading...
Need help?
General