From: Steve K. <st...@st...> - 2004-11-08 02:46:04
|
On Nov 7, 2004, at 12:02 PM, Dan wrote: > Hi, > > There is someone else having problems with the uLaw codec in iaxclient > livbrary? > This is the scenario for me: > - ATA186 SIP, uLaw preferred codec, uLaw and aLaw only supported > - DIAX with the latest iaxclient library, iLBC preferred codec, > uLaw/GSM/Speex supported. > > Calling from DIAX to ATA, iLBC codec is used, Asterisk make the > conversion. Ths ound is ok in both directions. > Calling from ATA to DIAX, uLaw is selected. > The sound from DIAX to ATA is perfect. > The sound from ATA to DIAX is very choppy and with very high latency > (several seconds). > > Some thoughs about that? There should be four different audio situations, but you're only reporting the result in two cases: Call from iaxclient to ATA, with iLBC on the iaxclient side, and asterisk translating: Case 1: Audio from iaxclient to ATA. Case 2: Audio from ATA to iaxclient. Call from ATA to iaxcleint, uLaw all the way Case 3: Audio from iaxclient to ATA. Case 4: Audio from ATA to iaxclient. Which audio cases result in problems? In those cases, you should take a look at the network traffic via ethereal, and see if the times and timestamps being sent into iaxclient make sense. For uLaw, you should get frames about every 20ms, and the timestamps should be separated by 20ms. For iLBC, it should be 30ms with the way asterisk works. -SteveK |