1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

TIPS Wazo 17.14 GV Issues

Discussion in 'Bug Reporting and Fixes' started by JFrost, Oct 11, 2017.

  1. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    Thread Summary: WiP

    There's two issues here that have been co-mingled. They may or may not be related. Still trying to work that out.

    Issue 1 - Running the GV Trunks update code on my Wazo install after upgrading from 17.13 to 17.14 broke my setup by causing the Asterisk service to fail to start.

    Issue 1.1 - Found that issue 1 happens also on a fresh 17.14 install - all is well until I go through ./add-gvtrunk then Asterisk refuses to start. This leads me to believe that issue 1 was not unique to my install but something related to the GV trunk code.

    I have successfully installed 17.09 and created trunks, installed 17.13 and created trunks, then upgraded that 17.13 to 17.14 and trunks kept working.
    In contrast to my first upgrade from 17.13 to .14 where after the upgrade to .14 I ran teh xmpp update code and Asterisk refused to restart from there forward.
    Another user reports same symptoms on a clean install of 17.14 whereby after install and running add-gvtrunk, Asterisk refuses to start.​


    [RESOLVED] Issue 2 - Getting a recursive view in the new admin add-ons view combined with a 500 server error. This occurs too on fresh virgin install. Can't say if it was happening on my old install pre-upgrade.

    Issue discussed (and possibly solved) with Francois here: https://projects.wazo.community/boards/1/topics/11728?r=11767

    The IncrediblePBX script, after it runs and completes and presents you with the final screen of info (your knock.faq, etc.) requires another reboot and login to finish running scripts. IPBX does not prompt you to reboot nor does it indicate a reboot is needed anywhere however without it the new admin (and idk what else) is broken till then.​




    -------------------------
    Ok, looks like I screwed the pooch. After the fix above upgrade seems to have gone well. After, I inadvertently ran the second part (for when Asterisk version changes) and now Asterisk won't start. :(:confused:

    How bad did I screw this up and can I/how do I get it back?


    Output:
    2017-10-11 14:17:14 root@pbx:~# wazo-service restart all
    Closing port 5060.
    Waiting for services to stop successfully...
    Waiting for services to start successfully...
    starting rabbitmq-server ... OK
    starting consul ... OK
    starting postgresql@9.4-main ... OK
    starting nginx ... OK
    starting mongooseim ... OK
    starting dahdi ... OK
    starting wazo-admin-ui ... OK
    starting wazo-plugind ... OK
    starting wazo-webhookd ... OK
    starting xivo-sysconfd ... OK
    starting xivo-confgend ... OK
    starting xivo-confd ... OK
    starting wazo-auth ... OK
    starting xivo-dxtora ... OK
    starting xivo-provd ... OK
    starting xivo-agid ... OK
    starting asterisk ...Job for asterisk.service failed. See 'systemctl status asterisk.service' and 'journalctl -xn' for details.
    NOK
    Opening port 5060.​



    2017-10-11 14:25:16 root@pbx:~# systemctl status asterisk
    ● asterisk.service - Asterisk PBX
    Loaded: loaded (/lib/systemd/system/asterisk.service; enabled)
    Active: failed (Result: resources) since Wed 2017-10-11 14:19:41 EDT; 8min ago
    Process: 6430 ExecStartPost=/bin/bash -c for i in {1..10}; do /usr/sbin/asterisk -rx "core waitfullybooted" &>/dev/null && exit 0; sleep 1; done; exit 1 (code=exited, status=0/SUCCESS)
    Process: 6408 ExecStart=/usr/sbin/asterisk -g -U asterisk (code=exited, status=0/SUCCESS)
    Main PID: 6410 (code=exited, status=127)

    Oct 11 14:19:36 pbx systemd[1]: Starting Asterisk PBX...
    Oct 11 14:19:37 pbx systemd[1]: asterisk.service: main process exited, code=exited, status=127/n/a
    Oct 11 14:19:37 pbx systemd[1]: PID 6410 read from file /var/run/asterisk/asterisk.pid does not exist or i...ombie.
    Oct 11 14:19:41 pbx systemd[1]: asterisk.service never wrote its PID file. Failing.
    Oct 11 14:19:41 pbx systemd[1]: Failed to start Asterisk PBX.
    Oct 11 14:19:41 pbx systemd[1]: Unit asterisk.service entered failed state.
    Hint: Some lines were ellipsized, use -l to show in full.
    2017-10-11 14:28:33 root@pbx:~# journalctl -xn
    -- Logs begin at Wed 2017-10-11 14:11:48 EDT, end at Wed 2017-10-11 14:28:35 EDT. --
    Oct 11 14:26:46 pbx python3[6175]: 2017-10-11 14:26:46,957 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
    Oct 11 14:26:46 pbx systemd[1]: Starting Cleanup of Temporary Directories...
    -- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit systemd-tmpfiles-clean.service has begun starting up.
    Oct 11 14:26:46 pbx systemd[1]: Started Cleanup of Temporary Directories.
    -- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit systemd-tmpfiles-clean.service has finished starting up.
    --
    -- The start-up result is done.
    Oct 11 14:27:01 pbx CRON[10594]: pam_unix(cron:session): session opened for user root by (uid=0)
    Oct 11 14:27:01 pbx CRON[10595]: (root) CMD (/root/ipchecker > /dev/null 2>&1)
    Oct 11 14:27:01 pbx CRON[10594]: pam_unix(cron:session): session closed for user root
    Oct 11 14:27:13 pbx python3[6175]: 2017-10-11 14:27:13,993 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
    Oct 11 14:27:41 pbx python3[6175]: 2017-10-11 14:27:41,013 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
    Oct 11 14:28:08 pbx python3[6175]: 2017-10-11 14:28:08,030 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
    Oct 11 14:28:35 pbx python3[6175]: 2017-10-11 14:28:35,049 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
    2017-10-11 14:29:21 root@pbx:~#


     
    #1 JFrost, Oct 11, 2017
    Last edited: Oct 21, 2017
  2. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    Kyle,

    Dollars to donuts I'm the one who screwed the pooch here.
    The original issue was simply needing to 'apt-get update' before running wazo-upgrade - not a big deal at all.

    Once I did that the upgrade was fine.

    The second snippet of code - intended for when the Asterisk version changes (which from .13 to .14 it did not) - is what borked me. I was looking to edit the script. I used a command line from my shell history and accidentally ended up running the script instead of editing it.
    I guess this is part of the price of being a linux newbie....

    Anyway, not sure *why* that second snippet borked my Asterisk but it did and I didn't need to even run it. :(

    Maybe if I understood exactly what that second script fully *does* I can figure out what it broke. I will spend some time on that now.

    In the meantime, if anybody has any insight into the errors above and/or how to get my Asterisk service running again, I'm open.

    Thanks,
     
  3. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    13,819
    Likes Received:
    2,293
    The "second script" provides support for Google Voice OAuth 2 authentication in Wazo. It is an add-on to the traditional Asterisk package distributed with Wazo. When a new release of Wazo upgrades the version of Asterisk packaged in their software, we also need to rebuild the OAuth 2 module to maintain connectivity with Asterisk.
     
    #3 wardmundy, Oct 12, 2017
    Last edited: Oct 25, 2017
  4. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    That is my understanding of it's purpose however why would running it then break Asterisk from starting? Asterisk was running fine after the script upgrade to .14 and before I accidentally ran the second script.

    Now I can't get asterisk to start no matter what.

    I did go back and check the "second script's" behavior by running it by hand. One thing that did pop up was asking me to diff /etc/asterisk/indications.conf.
    The 'new' one only had one line - an #include for /etc/asterisk/indications.d/* (which doesn't exist.)
    My old indications.conf had a bunch of lines in it. I think they are defining tones (pitch/notes and durations) so I don't think that should stop Asterisk svc from starting but I did merge them anyway.
    Still no joy.

    So - Any concept of how the second code snippet might have affected Asterisk from starting?
    Can I 'remove' the Google OAuth and start again or how do I attack this? My Wazo's down for 2 days now so I'd really like to figure out at least where I should be looking.

    If you need any logs or anything to help please lmk.

    thank you.
     
  5. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    13,819
    Likes Received:
    2,293
    You'll need to post the commands you are running. The OAuth script doesn't affect the basic Asterisk install at all. It merely adds another module. The indications alert arises during the original update, not the OAuth update. And it's harmless. You've done something else to hose the system. Have you checked the Asterisk logs??
     
  6. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    I don't deny it's possible I did bork it somehow but I know that Asterisk svc was running up until I ran the second script. It wouldn't restart on the last line and my phones went down. Phones and calls were working up until then.

    Doesn't mean I didn't do something earlier that contributed. It's just that I'm certain that Asterisk (the service) was running till the restart in the second snippet.

    Here it is verbatim as it was run and is stored on my machine:
    Code:
    2017-10-12 18:04:53 root@pbx:/var/log/asterisk# cat /root/upgrade-wazo-ipbx.runPostUpgrade_when_Asterisk_upgraded.sh
    # Taken from  https://pbxinaflash.com/community/threads/incredible-wazo-upgrade-to-17-13.19952/page-3#post-128374
    
    
    cd /tmp
     git clone https://github.com/sboily/asterisk-res-xmpp-oauth.git
     cd asterisk-res-xmpp-oauth
     make patch
     make
     make install
    /etc/init.d/asterisk restart
    
    
    2017-10-12 18:05:28 root@pbx:/var/log/asterisk#
    
    As far as checking Asterisk logs, I have not. Not sure how or what I'd be looking for but I will try to Google my way through that now.


    EDIT-
    Did 'wazo-services restart'. Output from /var/log/asterisk/messages
    Code:
    [Oct 12 19:19:52] Asterisk 14.6.2 built by builder @ builder-64 on a x86_64 running Linux on 2017-09-20 19:02:15 UTC
    [Oct 12 19:19:53] NOTICE[11421] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
    [Oct 12 19:19:53] NOTICE[11421] cdr.c: CDR simple logging enabled.
    [Oct 12 19:19:53] NOTICE[11421] loader.c: 230 modules will be loaded.
    [Oct 12 19:19:54] NOTICE[11421] res_odbc.c: Registered ODBC class 'xivo' dsn->[xivo]
    [Oct 12 19:19:54] NOTICE[11421] res_odbc.c: Registered ODBC class 'SQLITE3-asteridex' dsn->[SQLITE3-asteridex]
    [Oct 12 19:19:54] NOTICE[11421] res_odbc.c: res_odbc loaded.
    [Oct 12 19:19:54] NOTICE[11475] res_xmpp.c: Connecting to client token : 1/gp1IZClYmC9ZI2uwsWLtoa-J5CKZSVspnNDFWEpbx90
    [Oct 12 19:19:54] NOTICE[11475] res_xmpp.c: Command CURL(https://www.googleapis.com/oauth2/v3/token,client_id=466295438629-prpknsovs0b8gjfcrs0sn04s9hgn8j3d.apps.googleusercontent.com&client_secret=4ewzJaCx275clcT4i4Hfxqo2&refresh_token=$
    [Oct 12 19:19:54] ERROR[11475] pbx_functions.c: Function CURL not registered
    [Oct 12 19:19:54] NOTICE[11475] res_xmpp.c: Command status :
    [Oct 12 19:19:54] ERROR[11475] res_xmpp.c: object is NULL
    [Oct 12 19:19:54] NOTICE[11474] res_xmpp.c: Connecting to client token : 1/h0zMQYW0uDj1R1X-C5ywHrNswutjG_ymGMZxHt8rvk8
    [Oct 12 19:19:54] NOTICE[11474] res_xmpp.c: Command CURL(https://www.googleapis.com/oauth2/v3/token,client_id=466295438629-prpknsovs0b8gjfcrs0sn04s9hgn8j3d.apps.googleusercontent.com&client_secret=4ewzJaCx275clcT4i4Hfxqo2&refresh_token=$
    [Oct 12 19:19:54] ERROR[11474] pbx_functions.c: Function CURL not registered
    [Oct 12 19:19:54] NOTICE[11474] res_xmpp.c: Command status :
    [Oct 12 19:19:54] ERROR[11474] res_xmpp.c: object is NULL
    
     
    #6 JFrost, Oct 12, 2017
    Last edited: Oct 12, 2017
  7. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    So with few leads and getting really nowhere on my own (https://projects.wazo.community/boards/1/topics/11687?r=11706) I asked the Wazo team for help. Sylvain Boily (a true gentleman! Really, I've found the whole Wazo team to be awesome!) shelled into my server and determined that the XMPP module needed recompile.

    I'm not sure how that came to be the problem but I see the second snippet of code I ran is specifically grabbing some XMPP stuff from github so it seems likely that this is what broke it. The question still unanswered is why?


    Did it grab the wrong version from git?
    Bad compile?
    Copied to wrong place in file system?
    ...

    I'm no expert (in Linux, I'm just mildly functional) but it does look like something went wrong when running that patching bit (second snippet). Maybe it needs a version check or maybe something else was wrong, idk. But I think it's worth figuring out in case there is a bug, so it doesn't hit anyone else.

    J.
     
    #7 JFrost, Oct 14, 2017
    Last edited: Oct 14, 2017
  8. kyle95wm

    kyle95wm Active Member

    Joined:
    Apr 16, 2016
    Messages:
    358
    Likes Received:
    71
    So how did he wind up fixing it? I ran an upgrade on my dev server and all went well with no problems.
     
    wardmundy likes this.
  9. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    Sylvain said he just recompiled XMPP module. Asterisk (the service) came up after that and all services came up after wazo-services restart.

    I didn't notice at the time but my google trunks weren't working (inside calling worked but not inbound or outbound). I've been working on that today after getting some backups done.

    Since the problem was google trunks I tried dropping and re-adding in Wazo ui, dropping from the ui and from the cli, reboot and re-add, no go. Asterisk keeps saying something to the effect of 'no channel type exists for Motif'.

    As a last ditch I reran the xmpp update script and again, broke Asterisk and it's complaining about the xmpp module.

    Whatever it is that's different on my system I don't know but there's no question that xmpp upgrade code broke Asterisk from starting. Now twice.
     
  10. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    Now confirmed that this happens on a fresh, brand new OVH VPS installing 7.14 from IPBX sources (per http://nerdvittles.com/?p=20675&cpage=1#comment-175636)
    Per my comment on that thread:


    Immediately after install completes (with nothing else done and before and after a reboot) the new admin doesn’t work. See here: https://projects.wazo.community/boards/1/topics/11728

    Assuming the problem was localized to the new UI I proceeded to add 1 GV trunk. I’ve done this multiple times both running the install code from http://nerdvittles.com/?p=19169 and not.

    In either case after adding my GV trunk Asterisk fails to start. I’ve repeated this now many multiple times.
    Code:
    2017-10-18 18:22:05 :~# wazo-service status all
    Checking database...
            OK
    Checking services...
            running         rabbitmq-server
            running         consul
            running         postgresql
            running         nginx
            running         mongooseim
            running         dahdi
            running         wazo-admin-ui
            running         wazo-plugind
            running         wazo-webhookd
            running         xivo-sysconfd
            running         xivo-confgend
            running         xivo-confd
            running         wazo-auth
            running         wazo-call-logd
            running         xivo-dxtora
            running         xivo-provd
            running         xivo-agid
            failed          asterisk
            running         xivo-amid
            running         xivo-agentd
            failed          xivo-ctid
            running         xivo-dird
            running         xivo-dird-phoned
            failed          xivo-ctid-ng
            running         xivo-websocketd
    
    Is there any way to install an older version (eg 17.13 or 17.12)
     
  11. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    13,819
    Likes Received:
    2,293
    Wazo generates nightly backups. :idea:
     
  12. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    How is that relevant?
    I'm report to you that this happens on a fresh clean install from scratch with no history or backups.
    Did I miss something?
     
  13. Ramsey F

    Ramsey F New Member

    Joined:
    Feb 11, 2017
    Messages:
    23
    Likes Received:
    5
    I've experienced the same thing with a new installation on Vultr. After Wazo and IncrediblePBX get installed, "pbxstatus" shows that asterisk is running. After "add-gvtrunk", asterisk is down. After "del-gvtrunk xxxxx", asterisk is again running. I haven't found the key to getting it working.

    All of this is after 8 attempted installations on a dedicated PC that all failed. On my old installation, the voicemail system stopped doing what it was supposed to do, so I decided to start fresh. Used the Wazo snapshot 3 times and then the manual installation 5 times and always had "wizard.py" errors and the error "Input Error - registrar: [u'Field may not be null.']" when saving User info.

    What little bit of hair I had when I started this yesterday is now almost gone.

    Can anyone tell me how to recompile XMPP? I've seen the same errors reported in post #6 above. I've even gotten a new refresh token to see whether that helps.

    Ward, you say you've updated a half dozen servers. How about during the past 2 days? Could something have changed in code somewhere?
    Code:
    [Oct 19 18:05:47] Asterisk 14.6.2 built by builder @ builder-64 on a x86_64 running Linux on 2017-09-20 19:02:15 UTC
    [Oct 19 18:05:47] NOTICE[10236] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
    [Oct 19 18:05:47] NOTICE[10236] cdr.c: CDR simple logging enabled.
    [Oct 19 18:05:47] NOTICE[10236] loader.c: 231 modules will be loaded.
    [Oct 19 18:05:48] NOTICE[10236] res_odbc.c: Registered ODBC class 'xivo' dsn->[xivo]
    [Oct 19 18:05:48] NOTICE[10236] res_odbc.c: Registered ODBC class 'SQLITE3-asteridex' dsn->[SQLITE3-asteridex]
    [Oct 19 18:05:48] NOTICE[10236] res_odbc.c: res_odbc loaded.
    [Oct 19 18:05:48] NOTICE[10287] res_xmpp.c: Connecting to client token : <removed>
    [Oct 19 18:05:48] NOTICE[10287] res_xmpp.c: Command CURL(https://www.googleapis.com/oauth2/v3/token,client_id=466295438629-prpknsovs0b8gjfcrs0sn04s9hgn8j3d.apps.googleusercontent.com&client_secret=4ewzJaCx275clcT4i4Hfxqo2&refresh_token=<removed>&grant_type=refresh_token)
    [Oct 19 18:05:48] ERROR[10287] pbx_functions.c: Function CURL not registered
    [Oct 19 18:05:48] NOTICE[10287] res_xmpp.c: Command status : 
    [Oct 19 18:05:48] ERROR[10287] res_xmpp.c: object is NULL
    
     
    #13 Ramsey F, Oct 19, 2017
    Last edited: Oct 19, 2017
  14. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    Thanks Ramsey. Glad to know I'm not alone.
    Sylvain recomiled the module so I couldn't tell you how but it may not matter. After Sylvain recompiled, Asterisk ran but my trunks were still useless. To my judgement this happened exactly with release of 17.14. I upgraded from .13 and all was still well. Until I ran the xmpp update code - that's when Asterisk broke. I believe the problem doesn't exist on 17.13. If I could figure out how to install .13 or .12 for example I'd try right now. If I were a bettin' man I'd gamble that one of those will install w/o issue.
    As the xmpp update code seems meant for when Asterisk version changes/updates I can only guess that something changed in xmpp code or something changed with Asterisk.

    Thanks for chiming in.
    J.
     
  15. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    @wardmundy Can you tell us who is responsible for that xmpp code? Wazo project, is it part of Incredible (so you I guess?) or ?
    I'd like to ask whomever it is to please see if/when something changed.
    I suppose the same is in order for the asterisk service. Guessing that falls to the Wazo guys, yes?

    Thanks.
     
  16. Ramsey F

    Ramsey F New Member

    Joined:
    Feb 11, 2017
    Messages:
    23
    Likes Received:
    5
    Inside IncrediblePBX14-Wazo.sh is the following line. I am going to try it with 17.13:
    Code:
    bash wazo_install.sh -a 17.14
     
  17. Ramsey F

    Ramsey F New Member

    Joined:
    Feb 11, 2017
    Messages:
    23
    Likes Received:
    5
    OK, so I changed the line in the file above to 17.13. That is what got installed. Running "add-gvtrunk" and asterisk is still up. I haven't tested any further.

    When add-gvtrunk runs, it appears to download a git for xmpp and does some compiling. I saw errors during this, but then the screen got cleared and I couldn't copy them. I'll have to be faster in the future.

    Code:
    git clone https://github.com/sboily/asterisk-res-xmpp-oauth.git
     cd asterisk-res-xmpp-oauth
     make patch
     make
     make install
    
     
  18. Ramsey F

    Ramsey F New Member

    Joined:
    Feb 11, 2017
    Messages:
    23
    Likes Received:
    5
    Falling back to 17.13 solved all problems on Vultr. Tomorrow, I'll test the dedicated PC.
     
    wardmundy likes this.
  19. Ramsey F

    Ramsey F New Member

    Joined:
    Feb 11, 2017
    Messages:
    23
    Likes Received:
    5
    On a dedicated PC, installing Wazo 17.13 allows asterisk to remain running after "add-gvtrunk". To install 17.13, when you download the Wazo install script, run this modified command for the installation:
    Code:
    bash wazo_install.sh -a 17.13
    But there are still problems with the dedicated installation.

    When I save a User, I still get this error: Input Error - registrar: [u'Field may not be null.']

    I have tried everything I could find on the forum to fix this error without success. I notice one thing about the new installation which is different from the old installation and different from the Vultr installation: When I select the following: Users -> (edit a user) -> Lines, the Site field is empty on the new installation and contains "local" on the successful installations. I don't know how to make that fill. I've played around with locales and FQDN, but no success.

    After installing IncrediblePBX and rebooting, pbxstatus installs an update for the external IP. I see warnings about xmpp in the output:
    Code:
    patch -p0 < debian/patches/oauth_support.diff
    patching file res_xmpp.c
    cc -c -Wall -Wextra -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wmissing-format-attribute -Wformat=2 -g -fPIC -D_GNU_SOURCE -D'AST_MODULE="res_xmpp"' -D'AST_MODULE_SELF_SYM=__internal_res_xmpp_oauth_self' -o res_xmpp.o res_xmpp.c
    res_xmpp.c: In function ‘xmpp_client_change_state’:
    res_xmpp.c:622:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
      if (state == client->state) {
                ^
    res_xmpp.c: In function ‘xmpp_action_hook’:
    res_xmpp.c:3559:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
      for (i = 0; i < ARRAY_LEN(xmpp_state_handlers); i++) {
                    ^
    res_xmpp.c:3560:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
       if ((xmpp_state_handlers[i].state == client->state) && (xmpp_state_handlers[i].component == (ast_test_flag(&clientcfg->flags, XMPP_COMPONENT) ? 1 : 0))) {
                                         ^
    res_xmpp.c:3570:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
      for (i = 0; i < ARRAY_LEN(xmpp_pak_handlers); i++) {
                    ^
    res_xmpp.c:3571:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
       if (xmpp_pak_handlers[i].type == pak->type) {
                                     ^
    cc -Wall -shared res_xmpp.o -o res_xmpp_oauth.so -liksemel
    mkdir -p /usr/lib/asterisk/modules
    install -m 644 res_xmpp_oauth.so /usr/lib/asterisk/modules/
     +-------- res_xmpp_oauth installed ---------+
     +                                           +
     + res_xmpp_oauth has successfully           +
     + been installed.                           +
    I would prefer to run a dedicated PC, but my only success is with Wazo 17.13 on Vultr.
     
  20. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    50
    Likes Received:
    3
    Try falling back a few more points maybe. I installed Wazo 17.03 or .04 I think on a local Debian on Hyper-V here once before moving to OVH. You should be able to upgrade, at least all the way to 17.13 from there I think.

    Thanks for all your testing above. Gonna give your instructions a spin shortly and see if I can get 17.13 running and then up to 17.14 without touching xmpp code and see if that works. If not I'll have to run with 17.13 for the moment.

    J.
     

Share This Page