System answers but voice quality is poor, System answers but pops or buzzes, Modem connection has garbage characters – Reliant Octel 200 and Octel 300 Message Servers PB6001401 User Manual
Page 511
DTIC 10-19
Octel Overture 200/300 Serenade 3.0
PB60014–01
Call into System, Phone Rings but Is Never Answered
This problem is unlikely, but it could be caused by the DTIC being operational but not being allowed to
report ringing to the main system. A possible source of this problem is that the signaling method for the
DTIC is not set to the correct value. The signaling method is set in LSP Table parameter 24 and should be
10 for the ACULAB. If the problem occurs, contact Technical Support.
System Answers but Voice Quality Is Poor
This problem probably means that the PCM encoding law is incorrectly set. Check whether System Parameter
198 — PCM ENCODING FOR THE SYSTEM, is set to 1, for A-law. If not, change the value to 1.
System Answers but Pops or Buzzes
This problem probably means that the setting of the DTIC as a clock sync source is not correct. If only
one DTIC is configured in the system, check that the DTIC is configured as the primary clock sync
source. If the DTIC is not configured as the primary clock sync source and the PBX has another clock,
the clock rates may not be the same.
If more than one DTIC is configured in the system, check that the DTIC is configured as the primary
clock sync source and also check that the PBX is using the same clock rate.
Modem Connection Has Garbage Characters
This problem occurs when log on is via a modem connection and the characters that appear on the screen
are random characters and digits.
The source of the problem and solution are the same as given for the System Answers But Pops or Buzzes.
Ports on the DTIC Configured for Ringing but Do Not Answer Calls
This problem could be caused by the message server expecting dial tone when initializing the ports. The
message server, as part of initialization, tells each port to go off hook, listen for dial tone, send a DTMF
string, and then go on hook.
At the @ prompt, use the
PS
command to see whether the port in question has the code NDT for no dial
tone or ERR for error. To determine whether the failing port number is actually on the DTIC or on
another line card instead, use the
LIST SLOT x
command, where
x
is the DTIC slot number.
If NDT or ERR is present, check System Parameter 33 — PBX INITIALIZE CODE. The value for this
parameter should be NONE.
Restart the system to reinitialize the DTIC. Then test that the card accepts phone calls.