ALERT GV: The Sky Has Fallen... Really

chris_c_ · Jul 31, 2018

jerrm said:
Other than possible confusion to the user, there is no reason to disable or delete the motif trunks & accounts. GVSIP and Motif have zero dependency or conflict between each other.

On the other hand the Motif accounts/trunks are useless at this point, so I don't know of any valid reason keep them.

I guess you could keep the Motif custom trunk definitions and change the dial stings to point to the appropriate gvsip instances, then you shouldn't have to touch any in/out routes. We elected to delete them to avoid confusion, I wanted it immediately clear a system was no longer on Motif. I guess we could have just edited the dial string renamed them.

The reason for not deleting the Motif trunks and just disabling them, is to not lose the OAUTH Refresh token saved with each trunk.
QUESTION: Which config file (or database table) contains each Motif trunk config data and OAUTH Refersh tokens?! These trunk config data + OAUTH keys are missing from /etc/asterisk/motif.conf

jerrm · Jul 31, 2018

chris_c_ said:
QUESTION: Which config file (or database table) contains each Motif trunk config data and OAUTH Refersh tokens?! These trunk config data + OAUTH keys are missing from /etc/asterisk/motif.conf

xmpp.conf

Also, you can delete the trunk without deleting the Motif account.

chris_c_ · Jul 31, 2018

Some selected errors from running install-gvsip on CentOS 7 x86 32 bit:
This script is assuming 64 bit.
The make works fine on this 32 bit VM
The install-gvsip script should adapt to OS bit width 32/64, just as the make does...
Once updated, it'll install GVSIP smoothly with no errors...

Code:

mv: cannot stat ‘/usr/lib64/libssl.so’: No such file or directory
mv: cannot stat ‘/usr/lib64/libcrypto.so’: No such file or directory

Code:

:~# locate libssl.so
/usr/lib/.libssl.so.0.9.8e.hmac
/usr/lib/.libssl.so.1.0.2k.hmac
/usr/lib/.libssl.so.10.hmac
/usr/lib/.libssl.so.6.hmac
/usr/lib/libssl.so
/usr/lib/libssl.so.0.9.8e
/usr/lib/libssl.so.1.0.2k
/usr/lib/libssl.so.10
/usr/lib/libssl.so.6

:~# openssl version
openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Code:

/usr/bin/ld: cannot find -ltsan
collect2: error: ld returned 1 exit status
make[1]: *** [astcanary] Error 1
make: *** [utils] Error 2
CC="cc" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" LDFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" makeopts
make[1]: Entering directory `/usr/src/asterisk-13.22.0/menuselect'
make[1]: `makeopts' is up to date.
make[1]: Leaving directory `/usr/src/asterisk-13.22.0/menuselect'
   [LD] astcanary.o -> astcanary
/usr/bin/ld: cannot find -ltsan
collect2: error: ld returned 1 exit status
make[1]: *** [astcanary] Error 1
make: *** [utils] Error 2

Please wait...

SETTING FILE PERMISSIONS.................Done
Removing any dangling symlinks
Dangling symlinks removed

STARTING ASTERISK
Asterisk Started
grep: /var/www/html/admin/modules/core/functions.inc/drivers/PJSip.class.php: No such file or directory
sed: can't read /var/www/html/admin/modules/core/functions.inc/drivers/PJSip.class.php: No such file or directory

Please wait...

Successfully reloaded

Please wait...

Successfully reloaded
GVSIP initialization is complete.

wardmundy · Jul 31, 2018

@chris_c_: Send code and we'll add it.

chris_c_ · Jul 31, 2018

@wardmundy Noted. :thumbsup:

About the grep/sed errors above:
/var/www/html/admin/modules/core/functions.inc/drivers/PJSip.class.php
does not exist on ipbx 12.0.70.
/var/www/html/admin/modules/core/functions.inc/PJSip.class.php
exists on ipbx 12.0.70.
Did the code file PJSip.class.php really move into the drivers folder?
Or is the path used by that grep/sed incorrect/bug?
EDIT: Answer my own question:
freepbx12 has functions.inc/PJSip.class.php .
freepbx13, 14, 15, 16... have functions.inc/drivers/PJSip.class.php .

Eliad · Jul 31, 2018

I am setting a local VM for Google Voice Hosting. I use Centos 6.10. I installed incrediblepbx Lean and run the installer twice. Then I installed GV-Naf. GV trunks are registered ok. I created GV SIP trunk on the GVSIP-Host. When creating the inbound route for GVSIP-Host on destination tab I can not find the option for Trunks.
What am I missing?

chris_c_ · Jul 31, 2018

Eliad said:
I am setting a local VM for Google Voice Hosting. I use Centos 6.10. I installed incrediblepbx Lean and run the installer twice. Then I installed GV-Naf. GV trunks are registered ok. I created GV SIP trunk on the GVSIP-Host. When creating the inbound route for GVSIP-Host on destination tab I can not find the option for Trunks.
What am I missing?

INBOUND route usually goes to Ring Group, Extension, Queue, Directory, IVR, etc...
OUTBOUND route usually first matches a dial pattern, then goes to the least expensive or most suitable Trunk you want it to go to, depending on the user's intended destination number.

Eliad · Jul 31, 2018

I followed the instructions on Nerdvittles for Google Voice Hosting and the screen shoot inbound shows destination to go to trunk created in the prior step. This is the part I do not get it, how to make trunk option show in the destination list.

chris_c_ · Jul 31, 2018

Eliad said:
I followed the instructions on Nerdvittles for Google Voice Hosting and the screen shoot inbound shows destination to go to trunk created in the prior step. This is the part I do not get it, how to make trunk option show in the destination list.

Are you sure?
On this tutorial: http://nerdvittles.com/?page_id=26511
This shows INBOUND destination is EXTENSION (701), and OUTBOUND route goes to TRUNK (GVSIP2).

chris_c_ · Aug 1, 2018

Anyone else seeing errors while the script is trying to patch the asterisk 13.22.0 tarball with the diff it downloads from naf419 github repo?! @jerrm @wardmundy
It gives FAILED errors while the install-gvsip srcipt is trying to patch the GVSIP (pjsip) asterisk code files (critical bug) and README.md (not critical yet a symptom of some kind of seriously incorrect assumption about what to patch):
EDIT: It looks like install-gvsip downloads the patch as a dynamic "compare" of asterisk/asterisk/master and github/naf419/gvsip (56 commits ahead and 78 commits behind asterisk/asterisk/master )- both are patched versions of ASTERISK 16 ?! And then, install-gvsip tries to apply this patch (based on Asterisk 16) to the ASTERISK 13 tar ball !? No wonder it FAILED so many times during the patching process?!

Code:

patching file res/res_pjsip_outbound_registration.c
Hunk #6 succeeded at 609 (offset 1 line).
Hunk #7 succeeded at 997 (offset 1 line).
Hunk #8 succeeded at 1352 (offset 1 line).
Hunk #9 succeeded at 1492 (offset 1 line).
Hunk #10 succeeded at 2298 (offset 1 line).
Hunk #11 succeeded at 2438 with fuzz 2 (offset 3 lines).
Hunk #12 succeeded at 2501 (offset 3 lines).
Hunk #13 FAILED at 2550.
1 out of 13 hunks FAILED -- saving rejects to file res/res_pjsip_outbound_registration.c.rej
patching file third-party/pjproject/patches/0100-oauth.patch


patching file res/res_pjsip.c
Hunk #1 succeeded at 1092 (offset -23 lines).
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 2438 with fuzz 2 (offset 3 lines).
Hunk #2 succeeded at 2499 (offset 3 lines).
Hunk #3 FAILED at 2547.
1 out of 3 hunks FAILED -- saving rejects to file res/res_pjsip_outbound_registration.c.rej


patching file res/res_pjsip/config_system.c
Hunk #1 FAILED at 52.
Hunk #2 succeeded at 127 (offset 17 lines).
Hunk #3 FAILED at 187.
2 out of 3 hunks FAILED -- saving rejects to file res/res_pjsip/config_system.c.rej
patching file res/res_pjsip_outbound_authenticator_digest.c
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 2355 (offset 1 line).


patching file res/res_pjsip.c
Hunk #1 succeeded at 1665 with fuzz 2 (offset 5 lines).
patching file res/res_pjsip/config_system.c
Hunk #1 FAILED at 52.
Hunk #2 succeeded at 127 (offset 15 lines).
Hunk #3 FAILED at 186.
2 out of 3 hunks FAILED -- saving rejects to file res/res_pjsip/config_system.c.rej
patching file README.md
Hunk #1 FAILED at 12.
Hunk #2 FAILED at 64.
2 out of 2 hunks FAILED -- saving rejects to file README.md.rej
patching file README.md
Hunk #1 FAILED at 31.
Hunk #2 FAILED at 43.
2 out of 2 hunks FAILED -- saving rejects to file README.md.rej
patching file res/res_pjsip_outbound_registration.c
Hunk #3 succeeded at 624 (offset 1 line).
Hunk #4 succeeded at 1379 (offset 1 line).
Hunk #5 succeeded at 1415 (offset 1 line).
Hunk #6 succeeded at 1438 (offset 1 line).
Hunk #7 succeeded at 1463 (offset 1 line).
Hunk #8 succeeded at 1532 (offset 1 line).
Hunk #9 succeeded at 2349 (offset 1 line).
Hunk #10 succeeded at 2376 (offset 1 line).
patching file README.md
Hunk #1 FAILED at 35.
1 out of 1 hunk FAILED -- saving rejects to file README.md.rej
patching file res/res_pjsip_outbound_registration.c
Hunk #5 succeeded at 648 (offset 1 line).
Hunk #6 succeeded at 1587 (offset 1 line).
Hunk #7 succeeded at 2487 (offset 3 lines).
patching file res/res_pjsip_outbound_registration.c
Hunk #5 succeeded at 636 (offset 1 line).
Hunk #6 succeeded at 938 (offset 1 line).
Hunk #7 succeeded at 1368 (offset 1 line).
Hunk #8 succeeded at 1411 (offset 1 line).
Hunk #9 succeeded at 1446 (offset 1 line).
Hunk #10 succeeded at 2317 (offset 1 line).
patching file include/asterisk/res_pjsip.h
Hunk #1 succeeded at 397 (offset -4 lines).
patching file res/res_pjsip.c
Hunk #2 succeeded at 2086 (offset 5 lines).
patching file res/res_pjsip/config_auth.c
Hunk #4 succeeded at 314 (offset -61 lines).
patching file res/res_pjsip/pjsip_configuration.c
Hunk #1 succeeded at 1756 (offset -41 lines).
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 1374 (offset 1 line).
Hunk #2 succeeded at 1434 (offset 1 line).
patching file README.md
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file README.md.rej
patching file README.md
Hunk #1 FAILED at 6.
1 out of 1 hunk FAILED -- saving rejects to file README.md.rej
patching file README.md
Hunk #1 FAILED at 6.
1 out of 1 hunk FAILED -- saving rejects to file README.md.rej
patching file README.md
Hunk #1 FAILED at 30.
Hunk #2 FAILED at 85.
2 out of 2 hunks FAILED -- saving rejects to file README.md.rej
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 2387 (offset 1 line).
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 610 (offset 1 line).
Hunk #2 succeeded at 656 (offset 1 line).
Hunk #3 succeeded at 771 (offset 1 line).
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 613 (offset 1 line).
Hunk #2 succeeded at 654 (offset 1 line).
Hunk #3 succeeded at 769 (offset 1 line).
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 1745 (offset 1 line).
patching file README.md
Hunk #1 FAILED at 35.
Hunk #2 FAILED at 64.
2 out of 2 hunks FAILED -- saving rejects to file README.md.rej
patching file res/res_pjsip_outbound_registration.c
Hunk #2 succeeded at 975 (offset 1 line).
Hunk #3 succeeded at 2401 (offset 1 line).
patching file third-party/pjproject/patches/0110-pjsip_dest_info.patch
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 2404 (offset 1 line).
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 2409 (offset 1 line).
patching file res/res_pjsip_outbound_registration.c
Hunk #1 succeeded at 1386 (offset 1 line).
patching file README.md
Hunk #1 FAILED at 37.
1 out of 1 hunk FAILED -- saving rejects to file README.md.rej
patching file res/res_pjsip_outbound_registration.c
Hunk #4 succeeded at 1486 (offset 1 line).
Hunk #5 succeeded at 1608 (offset 1 line).
Hunk #6 succeeded at 2541 (offset 3 lines).
patching file third-party/pjproject/patches/0130-contact-params.patch


patching file third-party/pjproject/patches/0120-contact-params.patch (renamed from third-party/pjproject/patches/0130-contact-params.patch)
The next patch would delete the file third-party/pjproject/patches/0120-pjsip_dest_info.patch,
which does not exist!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file res/res_pjsip.c
Hunk #1 succeeded at 2528 with fuzz 2 (offset -272 lines).
Hunk #2 succeeded at 3066 (offset -224 lines).
Hunk #3 succeeded at 3211 (offset -224 lines).
patching file res/res_pjsip_outbound_registration.c
Hunk #5 FAILED at 692.
Hunk #6 succeeded at 701 (offset 1 line).
1 out of 6 hunks FAILED -- saving rejects to file res/res_pjsip_outbound_registration.c.rej

chris_c_ · Aug 1, 2018

@wardmundy @jerrm
Are these errors expected?!

Code:

menuselect/menuselect --check-deps menuselect.makeopts
member 'LOADABLE_MODULES' in category 'MENUSELECT_CFLAGS' not found, ignoring.

***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'app_jack' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'cdr_tds' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'cel_tds' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'codec_opus' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'codec_silk' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'codec_siren7' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'codec_siren14' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'codec_g729a' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'res_config_sqlite' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'res_digium_phone' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'test_bridging' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'test_file' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'test_named_lock' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************


***********************************************************
  The existing menuselect.makeopts file did not specify
  that 'test_res_pjsip_scheduler' should not be included.  However, either some
  dependencies for this module were not found or a
  conflict exists.

  Either run 'make menuselect' or remove the existing
  menuselect.makeopts file to resolve this issue.
***********************************************************

WARNING: Always run Incredible PBX behind a secure hardware-based firewall.
make: *** [menuselect.makeopts] Error 255

chris_c_ · Aug 1, 2018

@wardmundy @jerrm
Sorry if a dumb question.
Why is this "make" of the patched asterisk tar ball (from install-gvsip) erroring out and failing to do actually compile the source code?!:
Have you encountered this error?!

Code:

 make
CC="cc" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" LDFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" makeopts
make[1]: Entering directory `/usr/src/asterisk-13.22.0/menuselect'
make[1]: `makeopts' is up to date.
make[1]: Leaving directory `/usr/src/asterisk-13.22.0/menuselect'
   [LD] astcanary.o -> astcanary
astcanary.o: In function `main':
/usr/src/asterisk-13.22.0/utils/astcanary.c:93: undefined reference to `__tsan_func_entry'
/usr/src/asterisk-13.22.0/utils/astcanary.c:113: undefined reference to `__tsan_read4'
/usr/src/asterisk-13.22.0/utils/astcanary.c:115: undefined reference to `__tsan_read4'
/usr/src/asterisk-13.22.0/utils/astcanary.c:117: undefined reference to `__tsan_read4'
/usr/src/asterisk-13.22.0/utils/astcanary.c:133: undefined reference to `__tsan_func_exit'
/usr/src/asterisk-13.22.0/utils/astcanary.c:98: undefined reference to `__tsan_read4'
/usr/src/asterisk-13.22.0/utils/astcanary.c:98: undefined reference to `__tsan_read4'
astcanary.o: In function `_GLOBAL__sub_I_00099_0_main':
/usr/src/asterisk-13.22.0/utils/astcanary.c:134: undefined reference to `__tsan_init'
collect2: error: ld returned 1 exit status
make[1]: *** [astcanary] Error 1
make: *** [utils] Error 2

wardmundy · Aug 1, 2018

chris_c_ said:
@wardmundy @jerrm
Sorry if a dumb question.
Why is this "make" of the patched asterisk tar ball (from install-gvsip) erroring out and failing to do actually compile the source code?!:
Have you encountered this error?!

I haven't compiled this in the last couple days so something may have become unglued. Before spending time on this, may I ask if you are using a stock build of Incredible PBX 13-13 and, if so, which one. Then I can attempt to replicate the error.

Eliad · Aug 1, 2018

I followed http://nerdvittles.com/?p=26445. At step 3. if you look at the screen shot at the bottom Set Destination is Trunks. This is the option that I do not know how to make it happen.

wardmundy · Aug 1, 2018

Eliad said:
I followed http://nerdvittles.com/?p=26445. At step 3. if you look at the screen shot at the bottom Set Destination is Trunks. This is the option that I do not know how to make it happen.

There are two pull-down windows to the right of Set Destination. When you click in the top window, one of the options will be Trunks. When you click in the bottom window, you then pick the desired inbound trunk.

chris_c_ · Aug 1, 2018

wardmundy said:
I haven't compiled this in the last couple days so something may have become unglued. Before spending time on this, may I ask if you are using a stock build of Incredible PBX 13-13 and, if so, which one. Then I can attempt to replicate the error.

This is a functionally stock build of IncrediblePBX13-12R-OAUTH.sh installed on CentOS 7 x86 32 bit, I fixed this bash shell install script to auto detect 32/64 bit and then it installs the correct 32 bit or 64 bit packages, rather than blindly assume 64 bit as it had been doing (bug).
Now that we talk about this, I remember I found and fixed bugs in the make menuselect command stage of the install script to get them to run correctly on both 64 and 32 bit. Going to check and see if the script has regressed back to that bug.

Eliad · Aug 1, 2018

wardmundy said:
There are two pull-down windows to the right of Set Destination. When you click in the top window, one of the options will be Trunks. When you click in the bottom window, you then pick the desired inbound trunk.

I apologize. Darn it, I need more coffee. I forgot to scroll down that top window.

chris_c_ · Aug 1, 2018

@wardmundy @jerrm I nailed it, install-gvsip failed because the make menuselect command block had regressed to the bugged version. This is why it failed to even begin to compile asterisk on 32 bit linux CentOS 7. Fixed it again. It's compiling asterisk with the gvsip-naf patch right now.

I realize a minority of power users runs IPBX on 32 bit linux in order to achieve 2x less PHP memory usage and almost 2x better speed for the web phone portal User Control Panel app. IMHO, these installer and patch scripts can and should work equally without error on all, or at the very least the top 10, linux CPU architectures... amd64, i686 32 bit, raspi, etc.

wardmundy · Aug 1, 2018

Dale Carnegie Award: Polycom's PR Man of the Year on the Demise of Google Voice

chris_c_ · Aug 1, 2018

@jerrm @wardmundy
Here's the Espace Networks fixed update version of this gvsip-naf, it works correctly on 32 bit linux. Should also work right on 64 bit linux - not tested (yet).
apt install git -y
yum install git -y
cd ~
rm -rf gvsip-naf
git clone https://github.com/EspaceNetworks/gvsip-naf
cd gvsip-naf
./install-gvsip

ALERT GV: The Sky Has Fallen... Really

Active Member

Guru

Active Member

Nerd Uno

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Nerd Uno

Active Member

Nerd Uno

Active Member

Active Member

Active Member

Nerd Uno

Active Member

Forum statistics