Topic: Is there a new FOP?

[compsos]

Hi S
I see in the latest sail rpms references to fop and there is a copy of cdr under /opt/sark/stat/asterisk-stat-v2. Is this operational yet or do we need to make some apache adjustments to test it?

So far asterisk18-1.8.7.0-2_centos5, smesailenv-1.0.0-28 and sail-3.1.0-145 are all working well. Thank you.

[SARK devs]

Good question

We had wanted to put CDR into the V3 iso but the new version was, at least last time I looked, a bit of a drama to install under EL5.  In the end, we modified the old V2 Stat and it is in sail-144 or 145 (can't remember which) .    It's also in the new iso which will go up shortly.

FOP also has a new version.  It is very nice and that is what our UK distributor uses on commercial installs.   It requires a licence fee (quite low) and we always run it on a separate server (it's a bit of a CPU Hog) so it isn't in the iso or the rpm I'm afraid.

Best

S

   

[compsos]

Thanks Jeff the CDR looks good. Not to worried about the FOP as not many used it.

[del]

Hi Selintra,

If I upgrade from my sail v128 to 145 will I get the CDR like it used to be? Can I access it by http://serverIP/cdr ?

Cheers,
Del

[SARK devs]

If I upgrade from my sail v128 to 145 will I get the CDR like it used to be?

yes - although it is better integrated into the menu system and uses SAIL's css 

Can I access it by http://serverIP/cdr

No, there is no separate entry point for it. 

Kind Regards

S

[del]

Hi Selintra,

Thanks again, if I want to upgrade to 145 do I need to unistall 128 first? Is there anything else I need to upgrade at the same time? I assume my DB will not be effected Funny thing is I've never done an update to SAIL, only ever installed from scratch, usually when I've messed up something

Kind regards,
Del

[SARK devs]

To upgrade to -145 you will need to install -145 and the latest release of smesailenv, which is -28

No need to remove anything but a good idea to back up the sail database before you begin - you will find it here

/opt/sark/db/sark.db

here's a way you might do it...

Code: [Select]

mkdir /home/software
cd /home/software
wget http://www.sailpbx.com/sail/sail-3.1/smesailenv-1.0.0-28.noarch.rpm
wget http://www.sailpbx.com/sail/sail-3.1/sail-3.1.0-145.noarch.rpm
yum localinstall *
signal-event post-upgrade
reboot
Kind Regards

S

[del]

Hi Selintra,

Thanks again for your help and advice. I'll give it a try.

Kind regards,
Del

[groutley]

Hi Sel.
  I'm confused..
running -145 and the latest release of smesailenv -28
but I seen no CDR anywhere ?

[SARK devs]

did you run post-upgrade and reboot?

S

[groutley]

did you run post-upgrade and reboot?

Well don't I feel silly !
I could have sworn I had done that, but after aplying the latest SME updates and running a post-upgrade and reboot,
CDR menu item is there !
 

[SARK devs]

Ah OK, all good. 

I was worried in case we'd missed something so thanks for letting me know.

S

[groutley]

I have to say.. I am loving having CDR back !

Thank you !!

[SARK devs]

Thanks! Appreciate the feedback.
wait 'till you see some of the stuff 3.2 can do! 

Best

S

[del]

To upgrade to -145 you will need to install -145 and the latest release of smesailenv, which is -28

No need to remove anything but a good idea to back up the sail database before you begin - you will find it here

/opt/sark/db/sark.db

here's a way you might do it...

Code: [Select]

mkdir /home/software
cd /home/software
wget http://www.sailpbx.com/sail/sail-3.1/smesailenv-1.0.0-28.noarch.rpm
wget http://www.sailpbx.com/sail/sail-3.1/sail-3.1.0-145.noarch.rpm
yum localinstall *
signal-event post-upgrade
reboot
Kind Regards

S

Tried this on my test server and everything seems great, thanks for all the hard work.

Kind regards,
Del