TIPS GVSIP Issue on RasPi

Discussion in 'Help' started by Waffull, Jul 17, 2018.

  1. Waffull

    Waffull New Member

    Joined:
    Jul 2, 2018
    Messages:
    27
    Likes Received:
    1
    So I did a fresh install of Raspian/IncrediblePBX for my RasPi3B+. I used the latest incrediblepbx13.13-raspbian8.img, dated June 2, 2018. I went through the initial setup with no problems. I then installed Webmin. I then did an apt-get update/upgrade. This is the same process I ran through a couple of weeks ago.

    After that I created a trunk for a line I have with PhonePower and the corresponding extension/inbound/outbound. All tested and working properly.

    My first go around a couple of weeks ago, I followed this guide: http://nerdvittles.com/?p=26267. This time around I followed this guide: http://nerdvittles.com/?p=26315.

    I'm not including all the output, only the sections with errors... See image below for what the final result looks like:
    Code:
    This appears to be a fresh install of GVSIP for Incredible PBX.
    Do you wish to install all of the required components? (y/n) y
    Preparing for GVSIP initialization...
    cp: cannot create regular file ‘/root/COPYING’: Operation not permitted
    
    Please wait...
    
    Creating symlink for fwconsole
    ln: failed to create symbolic link ‘/usr/local/sbin/fwconsole’: File exists
    !!!!amportal is depreciated. Please use fwconsole!!!!
    forwarding all commands to 'fwconsole'                                                                                  
    
    ****** WARNING WARNING WARNING WARNING ******                                                                                      
    
    Window size is too small: 80 x 24
    
    It was actually 121 x 43 or 141 x 43 (both sizes cause this. I've received this error before and the build has bee just fine.)
    Code:
                     
    Resize console window to at least 82 x 30.                                                                                                  
    Do it NOW before continuing with the install.                                                                                              
    Otherwise, Asterisk may fail to build.                                                                                                      
    ****** WARNING WARNING WARNING WARNING ******                                                                                              
    Press Enter to proceed at your own risk...                                                                                                  
                                                                                                                                              
    Updating Asterisk with NAF gvsip patches for PJSIP...
    rm: cannot remove ‘/usr/lib/asterisk/modules’: Is a directory                                                                    
    asterisk-13.22.0/                                                                                                                          
    ...
    patching file main/sdp_srtp.c
    --2018-07-17 16:03:02--  https://github.com/naf419/asterisk/compare/master...naf419:gvsip.patch
    Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
    Connecting to github.com (github.com)|192.30.253.113|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: unspecified [text/plain]
    Saving to: ‘master...naf419:gvsip.patch’
    
        0K .......... .......... .......... .......... ..........  833K
       50K .......... .......... .......... .......... .......... 1.87M
       100K .......... .......... .......... .......... .......... 1.42M
       150K .......... ........                                    1.57M=0.1s
    
    2018-07-17 16:03:02 (1.25 MB/s) - ‘master...naf419:gvsip.patch’ saved [172334]
    
    patching file README.md
    Hunk #1 FAILED at 1.
    1 out of 1 hunk FAILED -- saving rejects to file README.md.rej
    patching file include/asterisk/res_pjsip.h
    Hunk #1 succeeded at 397 (offset -4 lines).
    Hunk #2 succeeded at 417 (offset -4 lines).
    patching file res/res_pjsip.c
    Hunk #1 succeeded at 1072 (offset -23 lines).
    patching file res/res_pjsip/config_auth.c
    Hunk #4 succeeded at 314 (offset -61 lines).
    patching file res/res_pjsip/config_system.c
    Hunk #1 succeeded at 127 (offset 17 lines).
    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 README.md
    Hunk #1 FAILED at 5.
    Hunk #2 FAILED at 48.
    2 out of 2 hunks FAILED -- saving rejects to file README.md.rej
    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_outbound_registration.c
    Hunk #3 succeeded at 1001 (offset 1 line).
    Hunk #4 succeeded at 1014 (offset 1 line).
    Hunk #5 succeeded at 1025 (offset 1 line).
    Hunk #6 succeeded at 1417 (offset 1 line).
    Hunk #7 succeeded at 1494 (offset 1 line).
    Hunk #8 succeeded at 2295 (offset 1 line).
    Hunk #9 succeeded at 2309 (offset 1 line).
    Hunk #10 succeeded at 2342 (offset 1 line).
    Hunk #11 succeeded at 2358 (offset 1 line).
    Hunk #12 succeeded at 2421 (offset 1 line).
    Hunk #13 succeeded at 2451 (offset 3 lines).
    ...
    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 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
    ...
    checking for -Wshadow... yes
    checking for -march=native support... *** Error in `gcc': double free or corruption (top): 0x01510610 ***
    no
    checking whether to use rpath... not needed
    checking for sysinfo... yes
    ...
    checking pkg-config is at least version 0.9.0... yes
    checking for GTK2... yes
    configure: creating ./config.status
    config.status: creating makeopts
    config.status: creating autoconfig.h
    configure: Menuselect build configuration successfully completed
                  .$$$$$$$$$$$$$$$=..    
               .$7$7..          .7$$7:.  
             .$$:.                 ,$7.7  
           .$7.     7$$$$           .$$77
        ..$$.       $$$$$            .$$$7
       ..7$   .?.   $$$$$   .?.       7$$$.
       $.$.   .$$$7. $$$$7 .7$$$.      .$$$.
     .777.   .$$$$$$77$$$77$$$$$7.      $$$,
     $$$~      .7$$$$$$$$$$$$$7.       .$$$.
    .$$7          .7$$$$$$$7:          ?$$$.
    $$$          ?7$$$$$$$$$$I        .$$$7
    $$$       .7$$$$$$$$$$$$$$$$      :$$$.
    $$$       $$$$$$7$$$$$$$$$$$$    .$$$.
    $$$        $$$   7$$$7  .$$$    .$$$.  
    $$$$             $$$$7         .$$$.  
    7$$$7            7$$$$        7$$$    
     $$$$$                        $$$      
      $$$$7.                       $$  (TM)    
       $$$$$$$.           .7$$$$$$  $$    
        $$$$$$$$$$$$7$$$$$$$$$.$$$$$$    
          $$$$$$$$$$$$$$$$.              
    
    configure: Package configured for:
    configure: OS type  : linux-gnueabihf
    configure: Host CPU : armv7l
    configure: build-cpu:vendor:os: armv7l : unknown : linux-gnueabihf :
    configure: host-cpu:vendor:os: armv7l : unknown : linux-gnueabihf :
    CC="cc" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" LDFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect
    make[1]: Entering directory '/usr/src/asterisk-13.22.0/menuselect'
    gcc  -g -D_GNU_SOURCE -Wall -I/usr/include/libxml2   -c -o menuselect.o menuselect.c
    gcc  -g -D_GNU_SOURCE -Wall   -c -o strcompat.o strcompat.c
    gcc  -g -D_GNU_SOURCE -Wall   -c -o menuselect_stub.o menuselect_stub.c
    gcc  -o menuselect menuselect.o strcompat.o menuselect_stub.o -lxml2
    make[1]: Leaving directory '/usr/src/asterisk-13.22.0/menuselect'
    Generating input for menuselect ...
    
    ... (There's more here, but can't catch it before the screen below opens. Once it opens, it stays like this, even after being left for a half hour. In the past, the entire build/install only too 10 mins.)

    [​IMG]

     
  2. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    14,343
    Likes Received:
    2,440
    Take a look at the log in /root. The GVSIP-NAF upgrade is NOT a 10 minute procedure on a Raspberry Pi. On a 3B+, it takes more than 40 minutes. On early hardware, it takes considerably longer.
     
  3. Waffull

    Waffull New Member

    Joined:
    Jul 2, 2018
    Messages:
    27
    Likes Received:
    1
    Sorry, I had to leave town to take care of my ailing parents. I'll check the logs when I get back home. I haven't timed any of the GVSIP-NAF upgrades I've run, it's been good number, but I'm pretty sure the slowest was probably 20 mins. They are generally fast enough that I can watch the progress and it finishes before I feel the need to do other things or get up and get a drink, lol. I'll try to remember to time them because now I'm curious... :)

    Have a goodnight.
     
  4. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    14,343
    Likes Received:
    2,440
    We don't have access to a RasPi for the next several days, but we've uploaded a new installer this morning that may fix the issues on the Raspberry Pi platform. If someone could walk through the tutorial using the latest installer on a clean Incredible PBX for RasPi platform and let us know if GVSIP now is working, we'd appreciate it.

    You can ignore the resize warning if, in fact, your console is sized larger than the recommended dimensions.
     
  5. weenus500

    weenus500 Member

    Joined:
    Dec 28, 2014
    Messages:
    33
    Likes Received:
    1
    I would like to try this again very much, but I can only find the image from 06-02-2018. Could you please post a link to the image you just uploaded today? Thank you.
     
  6. toddhutch

    toddhutch New Member

    Joined:
    Jul 12, 2008
    Messages:
    24
    Likes Received:
    0
    Good morning Ward,

    I think the issue is with the raspi install not the generic. The gvsip-naf-raspi.tar.gz, not the - gvsip-naf-gui.tar.gz. Ward if you could upload a new gvsip-naf-raspi.tar.gz I can confirm that it will work this morning. I've confirmed it works if I download the corrupt file from the archive below.

    Sorry for the double post, new to this forum format.

    I think you are running into the same issue I've found, the file you download here - http://incrediblepbx.com/gvsip-naf-raspi.tar.gz has a corrupt install file in it.
    [​IMG]

    The asterisk-13.21.1.tar file has a data error.

    I haven't been able to get this to work either, with a fresh install on a rPi 3 b+ and the above.

    I can confirm that it works if you download the file from https://downloads.asterisk.org/pub/telephony/asterisk/old-releases/

    https://downloads.asterisk.org/pub/telephony/asterisk/old-releases/asterisk-13.21.1.tar.gz

    cd /root/gvsip-naf-raspi
    wget https://downloads.asterisk.org/pub/telephony/asterisk/old-releases/asterisk-13.21.1.tar.gz

    then run the script again it will work.

    ./install-gvsip.sh


    Best Regards,
    Todd
     
  7. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    14,343
    Likes Received:
    2,440
    With the RasPi platform, this is a two-step process at the moment. First, you must create a RasPi platform using the image you referenced. Then you must update it using the GVSIP-NAF installer available here. There is no longer a separate GVSIP upgrader for the RasPi. It's included in the generic GVSIP-NAF installer.

    Let me know here how it goes. I won't have access to a RasPi until late this weekend. Thanks for being pioneers.
     
  8. toddhutch

    toddhutch New Member

    Joined:
    Jul 12, 2008
    Messages:
    24
    Likes Received:
    0
    Good morning,

    I'm installing it now, and I'll let you know how the fresh install on a rPi 3 b+ goes.
     
  9. toddhutch

    toddhutch New Member

    Joined:
    Jul 12, 2008
    Messages:
    24
    Likes Received:
    0
    Good morning,

    I can confirm that this works on a fresh install of rPi 3 b+.
     
  10. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    14,343
    Likes Received:
    2,440
    Serenity now!
     
  11. Hawkmeister

    Hawkmeister New Member

    Joined:
    Jul 20, 2018
    Messages:
    2
    Likes Received:
    0
    I went through the two step install procedure on a Raspberry Pi. The installation works fine. I am, however, having an issue with obtaining an Oauth 2 refresh token. I keep getting an error that says "Invalid Container" when I try to authorize API's with the following: //www.googleapis.com/auth/googletalk

    It appears that Googletalk may not be a valid API any longer. Can anyone shed some light on this?
     
  12. Waffull

    Waffull New Member

    Joined:
    Jul 2, 2018
    Messages:
    27
    Likes Received:
    1
    I just ran through the process and it worked. Make sure you are using the correct link https://www.googleapis.com/auth/googletalk and follow all the instructions from this forum.
     
  13. weenus500

    weenus500 Member

    Joined:
    Dec 28, 2014
    Messages:
    33
    Likes Received:
    1
    o
    ok. I ran through that process twice and "asterisk> pjsip show registrations" showed gvsip1 unregistered.
     
  14. Hawkmeister

    Hawkmeister New Member

    Joined:
    Jul 20, 2018
    Messages:
    2
    Likes Received:
    0
  15. RSDunn

    RSDunn New Member

    Joined:
    Aug 4, 2013
    Messages:
    11
    Likes Received:
    1
    I just ran through the installer on a newly imaged RasPi3 and all is good except all outbound calls from IncredPBX via GVSIP trunk show as "no caller id:, "unknown caller" etc ... I see from the asterisk live logs using asterisk -vvvr
    From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=23426a43-1353-4572-8f3c-99043e86exxx
    To: <sip:XXXXXXXXXX@obihai.sip.google.com>
    Contact: <sip:asterisk@xx.xx.xx.xx:5061;transport=TLS>
    Call-ID: 8acb8ecd-0900-47d1-86d6-5da431df7940

    I have tried all methods from all posts and am unable to find where/why the Google Voice CallerID isn't being sent through with the calls?

    Any ideas?


    I found my issue was with my SIPURA ATA... Caller ID is now functioning outbound as expected for all gvsip trunks I have implemented!
     
    #15 RSDunn, Jul 21, 2018
    Last edited: Aug 14, 2018
  16. toddhutch

    toddhutch New Member

    Joined:
    Jul 12, 2008
    Messages:
    24
    Likes Received:
    0
    @RSDunn

    Have you looked are you GV settings on the Google website to see if you are sending the callerID vs your GV number down?
     
  17. RSDunn

    RSDunn New Member

    Joined:
    Aug 4, 2013
    Messages:
    11
    Likes Received:
    1
    Hi and thanks... Yes it is sending and this used to work with Simonics GV gateway b4 they shut their services causing me to make the change with GVSIP... I also rechecked on the Google side to ensure the CallerID is set to send.
     
  18. weenus500

    weenus500 Member

    Joined:
    Dec 28, 2014
    Messages:
    33
    Likes Received:
    1
    I used the pi 2 model B with no luck. Do you suppose it would make a difference if I did it on the rPi 3?
     
  19. RSDunn

    RSDunn New Member

    Joined:
    Aug 4, 2013
    Messages:
    11
    Likes Received:
    1
    I re-imaged using the precompiled gvsip image for RaspPi 3 from source forge added the gvsip trunk via the installer and still have no caller id being sent when dialing out via GVSIP trunk...

    where else can I look in the settings?

    EDIT:
    My problem was a setting on my Sipura ATA... once discovered caller ID outbound is working as expected!!

    Thanks to everyone who offered assistance.
     
    #19 RSDunn, Jul 23, 2018
    Last edited: Aug 14, 2018
  20. weenus500

    weenus500 Member

    Joined:
    Dec 28, 2014
    Messages:
    33
    Likes Received:
    1
    Stupid Question: Does GV work for incoming and outgoing call without the caller id? thanks!
     

Share This Page