<B><I>Thomas Sandford <thomas@paradisegreen.co.uk></I></B> wrote: <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">It is evident that a number of people are seeing these warnings with the new <BR>port version, but also that others are _not_.<BR><BR>In order to track down the problem it would be really useful if people who <BR>are using the 1.2.12.1 version on FreeBSD could provide the following <BR>information:<BR><BR>1) Whether they see these warnings or not.<BR>2) The version of FreeBSD installed<BR>3) Whether they are running the GENERIC, or a patched kernel (and if <BR>patched, in what way).<BR>4) Any options used in building the asterisk port<BR>5) The versions of libpri, zaptel and any other asterisk related ports - eg <BR>asterisk-addons<BR>6) Any zaptel (or similar, eg Sangoma) hardware installed<BR>7) The codecs they believe are actually in use.<BR>8) Anything else that would help determine the
circumstances, eg<BR><BR>"I see the problem when calling an external IAX (IaxTel) number using a <BR>Sipura 841 registered directly with the * box. I can hear the called party <BR>but they cannot hear me" [nb this is an example given purely for <BR>illustration - I am _not_ seeing any problems here].<BR><BR>I'm principally after results from people using the FreeBSD port, but if <BR>anyone has seen the same warnings with a native compilation of 1.2.12.1 on <BR>FreeBSD (ie not using the port framework) or on another OS that would be a <BR>useful datapoint.<BR><BR>[please reply to my original message unless there is a specific <BR>configuration/results change you are trying to highlight, and snip my <BR>results below to keep the thread relatively simple]<BR><BR>To start the ball rolling with my setup:<BR>1) Whether they see these warnings or not.<BR>No<BR>2) The version of FreeBSD installed<BR>5.4-RELEASE, with freebsd-update security patches<BR>3) Whether they are running
the GENERIC, or a patched kernel (and if <BR>patched, in what way).<BR>GENERIC kernel, plus OPTIONS SMP<BR>4) Any options used in building the asterisk port<BR>No<BR>5) The versions of libpri, zaptel and any other asterisk related ports - eg <BR>asterisk-addons<BR>libpri-1.2.3 , openh323-1.18.0_1 , pwlib-1.10.0,1 , spandsp-0.0.2.p26 , <BR>zaptel-1.0<BR>6) Any zaptel (or similar, eg Sangoma) hardware installed<BR>TDM400P with one FXS, one FXO module installed<BR>7) The codecs they believe are actually in use.<BR>ulaw<BR>8) Anything else that would help determine the circumstances<BR>Calls tried:<BR>Sipura 841 registered with Asterisk instance, limited to ulaw in sip.conf, <BR>to asterisk demo<BR>[ditto] to a remote asterisk (conference room) via IAX (also tried with <BR>SIP).<BR><BR>-- <BR>Thomas Sandford <BR><BR><BR>_______________________________________________<BR>Asterisk-BSD mailing list<BR>Asterisk-BSD@lists.digium.com<BR><A
href="http://lists.digium.com/mailman/listinfo/asterisk-bsd">http://lists.digium.com/mailman/listinfo/asterisk-bsd</A><BR></BLOCKQUOTE> <div><BR> </div> <div>Since I got this whole thread started here's my information:</div> <div> </div> <div>1) Whether they see these warnings or not.</div> <div>Yes, not only yes but hell yes. Sometimes only 1 set of messages, sometimes a whole slew of them scroll by on the screen.</div> <div> </div> <div>2) The version of FreeBSD installed</div> <div>6.1-RELEASE</div> <div><BR>3) Whether they are running the GENERIC, or a patched kernel (and if patched, in what way).</div> <div>GENERIC kernel</div> <div> </div> <div>4) Any options used in building the asterisk port<BR>No<BR>5) The versions of libpri, zaptel and any other asterisk related ports - eg <BR>asterisk-addons<BR>libpri-1.2.3</div> <div>openh323-1.18.0_1</div> <div>pwlib-1.10.0,1</div> <div>spandsp-0.0.2.p26 , <BR>zaptel-1.0</div>
<div><BR>6) Any zaptel (or similar, eg Sangoma) hardware installed<BR>X101P FXO card that I picked up from DigitalNetworks for $18</div> <div> </div> <div>7) The codecs they believe are actually in use.<BR>ulaw<BR></div> <div>8) Anything else that would help determine the circumstances<BR>Nothing I can think of.</div> <div><BR> </div><p> 
<hr size=1><a href="http://us.rd.yahoo.com/evt=43256/*http://advision.webevents.yahoo.com/mailbeta"> All-new Yahoo! Mail </a>- Fire up a more powerful email and get things done faster.