restamp
Member
- Joined
- Apr 24, 2016
- Messages
- 97
- Reaction score
- 53
I'm currently running an old 13-12.3 version of PIAF (green) (Asterisk 13.8) on an external VPS (CentOS 6). This version has worked fine for me, but I am in the process of trying to add encryption on all my pjsip extensions, and am having no luck with it. However, if I load the latest version of IncrediblePBX13-12 on a local Virtualbox, encryption (TLS/SDES) works fine. (To be honest, I modified the Virtualbox install script slightly to pull the latest pjproject code (2.6).) In any event, I am looking at upgrading my external VPS workhorse, but before I take that plunge I have a couple questions:
+ The current incrediblePBX13-12R.sh grabs Asterisk 13.13 and pjproject 2.5.5, so upgrading from it is not a very good test of whether an upgrade would have a similarly high probability of being successful on my more ancient existing system. Anyone out there have any empirical evidence that points one way or the other?
+ The upgrade script seems to step us back down to pjproject 2.3. Is there a reason for this? I've heard that 2.5.5 is the first pjsip that works well with encryption. (Oddly, when you query asterisk "rasterisk -x 'pjsip show version'", it invariably indicates it is running against pjproject 2.3 regardless of what resides in /usr/src, so maybe I am missing something important here.)
+ We are told backup, backup, backup before attempting such an upgrade, but what sort of backup is appropriate? I doubt "incrediblebackup" would be enough, since it doesn't appear to save /usr/src. Do I need to backup the entire VPS including CentOS or is there a simpler way?
+ Bottom line: I'd like to update my pjsip code and probably bring Asterisk up to its latest release as well. If I simply run the "upgrade-asterisk13-to-current-rhel" script on my field VM -- most likely after substituting pjproject 2.6 for 2.3 in the script itself -- what is the probability of success?
+ One more question: Is there any CLI (or other) command that can be used to show definitively that the RTP media is being encrypted? I'm presuming that when I set up Asterisk to squawk sdes on an extension and it breaks the voice path until I turn on SRTP in my local ATA boxes that that means encryption is indeed working.
I can't stress enough how much I've enjoyed using PIAF over the past year and, as I learned again today, the instructions for loading it are crystal clear. Thanks again to all the principals who make it possible.
+ The current incrediblePBX13-12R.sh grabs Asterisk 13.13 and pjproject 2.5.5, so upgrading from it is not a very good test of whether an upgrade would have a similarly high probability of being successful on my more ancient existing system. Anyone out there have any empirical evidence that points one way or the other?
+ The upgrade script seems to step us back down to pjproject 2.3. Is there a reason for this? I've heard that 2.5.5 is the first pjsip that works well with encryption. (Oddly, when you query asterisk "rasterisk -x 'pjsip show version'", it invariably indicates it is running against pjproject 2.3 regardless of what resides in /usr/src, so maybe I am missing something important here.)
+ We are told backup, backup, backup before attempting such an upgrade, but what sort of backup is appropriate? I doubt "incrediblebackup" would be enough, since it doesn't appear to save /usr/src. Do I need to backup the entire VPS including CentOS or is there a simpler way?
+ Bottom line: I'd like to update my pjsip code and probably bring Asterisk up to its latest release as well. If I simply run the "upgrade-asterisk13-to-current-rhel" script on my field VM -- most likely after substituting pjproject 2.6 for 2.3 in the script itself -- what is the probability of success?
+ One more question: Is there any CLI (or other) command that can be used to show definitively that the RTP media is being encrypted? I'm presuming that when I set up Asterisk to squawk sdes on an extension and it breaks the voice path until I turn on SRTP in my local ATA boxes that that means encryption is indeed working.
I can't stress enough how much I've enjoyed using PIAF over the past year and, as I learned again today, the instructions for loading it are crystal clear. Thanks again to all the principals who make it possible.