[Home]

Summary:ASTERISK-09022: Translator paths are unregistered on a reload for the TC400P
Reporter:John Bigelow (jbigelow)Labels:
Date Opened:2007-03-15 12:15:30Date Closed:2007-04-09 10:54:50
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/CodecInterface
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Using Asterisk 1.2.16 and Zaptel 1.2.15 with wctc4xxp loaded.

After starting Asterisk if you issue a reload it shows:
  -- codec_zap: using generic PLC
 == Found transcoder 'DTE Decoder'.
 == Found transcoder 'DTE Encoder'.
 == Unregistered translator 'zapulawtog723' from format ulaw to g723
 == Unregistered translator 'zapalawtog723' from format alaw to g723
 == Unregistered translator 'zapg723toulaw' from format g723 to ulaw
 == Unregistered translator 'zapg729toulaw' from format g729 to ulaw
 == Unregistered translator 'zapg723toalaw' from format g723 to alaw
 == Unregistered translator 'zapg729toalaw' from format g729 to alaw
 == Unregistered translator 'zapulawtog729' from format ulaw to g729
 == Unregistered translator 'zapalawtog729' from format alaw to g729

snip from 'show translation':
      g723   gsm  ulaw  alaw  g726 adpcm  slin lpc10  g729 speex  ilbc
  g723     -     -     -     -     -     -     -     -     -     -     -


Issuing another 'reload' shows the translators as registered again and 'show translation' shows the paths again. You can keep issuing a reload to have it unregister and register over and over.

Comments:By: Tusar Ahmed (tusar) 2007-03-30 13:17:31

Same thing is happening with Asterisk-1.2.17 and Zaptel-1.2.16 'Or' Asterisk-1.4.2  and Zaptel-1.4.1.

By: Serge Vecher (serge-v) 2007-03-30 14:21:53

did you guys contact support@digium.com?

By: Joshua C. Colp (jcolp) 2007-04-02 14:24:37

angler is support ^_^ it was agreed to put this bug on here.

By: Joshua C. Colp (jcolp) 2007-04-09 10:54:50

Fixed in 1.2 as of revision 60398, 1.4 as of revision 60399, and trunk as of revision 60400 by none other then kpfleming!