Topic: SARK/SAIL 2.2.1-752 & 2.3.1.2

[SARK devs]

Hi all,

We've done some more work on analogue circuit handling and put up the above two releases.  Pre DAHDI (asterisk 1.4.22) and DAHDI (asterisk 1.4.23) are both covered.  We've also harmonised the 2.2 and 2.3 AGI's with a bit of conditional C bridgework.  This doesn't mean that the executeables are the same - they aren't, it just makes our life a little easier.

The main target of this release was to simplify analogue (FXO) inbound processing and to fix single line automatic fax detection for SOHO users.  If fax is your thing then please give it a go.  Don't firget to turn fax detection ON for the trunk (by checking the fax detection box in the trunk edit window).  You can set the fax detection delay time in globals and hopefully, begin to receive fax and voice over the same circuit.

get these releases from http://sarkpbx.com/sail

Next out will be enhancements to voice recording and we will be asking for testers, so if recording is your thing then let us know and we'll put you on the early release list.

Kind Regards

S

     

[soprom]

Hi!

I'd need some help with this...

Will it be enough to issue
rpm -Uvh http://sarkpbx.com/sail/sail-2.3.1/sail-2.3.1-2.noarch.rpm ?

or
wget http://sarkpbx.com/sail/sail-2.3.1/sail-2.3.1-2.noarch.rpm
yum localinstall sail-2.3.1-2.noarch.rpm

Thanks

[SARK devs]

Hi Sophie

In both cases do

 wget http://sarkpbx.com/sail/.....

then do

 yum localinstall sail-2.whatever  --enablerepo=base

Use 2.2.1-752 if you have asterisk 1.4.22 or earlier.  Use 2.3.1 if you have asterisk 1.4.23 (DAHDI)

Best

Jeff

[soprom]

I'm wondering if 2.3.1 and asterisk 1.4.23 (DAHDI) are still in testing.
I want to keep upto date and I'm not sure if it's the right time to go with 1.4.23 (DAHDI) in production.

Your comments on this matter will be more than welcome!

[SARK devs]

Leave it a week or two Sophie.

It's almost ready but we aren't putting into production with our customers just yet.  We have it running here on our internal phone system and we are testing quite heavily.  You can put it onto a test machine if you have one and become familiar with it.

In any event,  we are back-porting all new features into 2.2.1 for the moment so you won't miss anything by staying with 2.2.1 for a little longer

Best

Jeff

[compsos]

We have applied the sail-2.3.1-2 with asterisk-1.4.23.1-72.el4. As we ran into problems with the 2.3.1 we

• removed zaptel and zaptel-kmdl which also removed asterisk (last time not removing zaptel caused problems loading the hardware as both kernel modules appeared to be present. Also had both dahdi and zap extensions and trunks, of which none worked)
• post-upgrade and rebooted
• installed the new sail, asterisk-1.4.23.1-72.el4 and dahdi modules

Did not loose Sail settings
Initially had trouble getting the dahdi extensions and trunks to show but a couple of initialises it came good. Note the command line dahdi_scan showed no hardware channels until we did a dahdi_genconf. All the features we had before appear to be running OK except

• appear to have lost CDR to MYSQL data.
• and sip reload reports all sip trunks as having "lacks type"
• an outgoing call shows but works (they may not be related to the upgrade)

Code: [Select]

[Apr 20 07:47:03] WARNING[29044]: channel.c:3316 ast_channel_make_compatible: No path to translate from SIP/peerwdp_out-09a03c00(256) to SIP/5001-09a31490(8)
[Apr 20 07:47:09] WARNING[20939]: channel.c:2948 set_format: Unable to find a codec translation path from 0x4 (ulaw) to 0x100 (g729)
[Apr 20 07:47:09] WARNING[20939]: channel.c:2948 set_format: Unable to find a codec translation path from 0x4 (ulaw) to 0x100 (g729)
    -- SIP/peerwdp_out-09a03c00 is making progress passing it to SIP/5001-09a31490
[Apr 20 07:47:09] WARNING[29044]: channel.c:2948 set_format: Unable to find a codec translation path from 0x8 (alaw) to 0x100 (g729)
[Apr 20 07:47:09] WARNING[29044]: channel.c:2948 set_format: Unable to find a codec translation path from 0x8 (alaw) to 0x100 (g729)
  == Spawn extension (default, 0429338896, 1) exited non-zero on 'SIP/5001-09a31490'


So far the lines sound "cleaner" (less echo). Could this be the change in the dahdi code?

[compsos]

Less echo spoke too soon.
Outgoing calls are good but incoming calls via PSTN to the TDM422B card echo on our side. The system is trying to apply
echocanceller=mg2,1
for each port card mounted on the TDM400 card.
We did not see this under the zaptel driver.

[SARK devs]

Hi Gordon

Thanks for this... 

You should remove asterisk entirely before going up to 2.3 so you did the correct thing

You don't need to manually run scan or genconf (although it won't hurt anything if you do - see the quickstart docs) - SAIL will run these for you if you run sail PCI detection.  PCI detection is non-dectructive so you can run it as many timws as you like to get familiar with it and what it does.

Looking at the sip output you've included, you look to have lost your G729 codec. 

One of the few immediate benefits of DAHDI is that choice of echo-canceller is no longer done at zaptel compile time.  It is now set by genconf.  Also, cancellation is set at the individual line level (at least for analogue), so you are free to use different cancellers on different lines.  Right now, we simply default to mg2 because that is the Digium default.  However, in theory you can use any canceller that you have an image for, including the likes of HPEC and OSLEC.

Best

S

   



 

[compsos]

Hi S

Is there a module for OSLEC to work with DAHDI? Most is working very well but an incoming PSTN call has crippling echo on our side. Should try a pstn out and see if it does the same.

G

[SARK devs]

There is but I believe that it is still somewhat experimental.  You can try their website.  HPEC should work now but there is a fee for using it.

S
 

[compsos]

Yes Have been doing some searching but the highest version I found of Oslec is 0.2 with a lot of patches and references to zaptel. So not sure they would work with Dahdi.

We were only looking at the echo canceller as we have this new problem of local echo since changing to dahdi.

Thank you for all the great work. You guys must be hating the so called "name change". It really has put us somewhere in between but almost working!!

[SARK devs]

keeps us off the streets...

[David Harper]

HPEC should work now but there is a fee for using it.

According to http://store.digium.com/productview.php?product_code=HPECLIC it's only US$10 per channel. Does anyone know whether HPEC works with OpenVox BRI cards?

[SARK devs]

HPEC shouldn't be hardware dependent.  It is used within zaptel as a soft plugin.  We haven't used HPEC but we have had success with OSLEC for ISDN2 cards (including the OpenVox items - although they needed a small patch to be applied to the bristuff software) using Bristuff (which is just a heavily patched zaptel and a special kmod for Cologne chipped cards). 

Best

S


 

[compsos]

Our echo seems to have subsided. Not sure but we remove ulaw from the trunks. Now just using alaw and g729.
Also upgraded to Sail 2.3.1-3.