Hey guys. I made a ticket yesterday for this but thought I’d also see if someone in the community has any ideas while I wait on a response.
Scenario: we were on Zulu 2. Everything was functional. Yesterday I followed the steps for upgrading to Zulu 3. Server/clients are updated. Most features appear to work fine, and audio works fine both ways. I can initiate calls without a problem.
Issue: the Zulu app doesn’t appear to give any indication or ability to answer an incoming call. Fortunately our primary users that depend on Zulu are remote for the next few days, so I have some time to troubleshoot.
Other details: We are on FreePBX 14 and fully updated in terms of system updates and module updates. No other issues are noticed at this time. We looked at wireshark but it appears the client and server are communicating freely.
I ended up having support SSH in. But the end result was they uninstalled Zulu completely and reinstalled it. Then it worked just fine. I am unsure if the result would be any different from uninstalling/reinstalling via the GUI.
I’m having this problem too. I can make out going calls via the Zulu client (I’ve tried Windows/Android and iOS). But none of them provide any indication of an incoming call, all though they do followup with a missed call notification when the call ends (in voicemail) or is abandoned.
Currently running FreePBX 14.0.5.27 with the latest System and Module updates - and Zulu Clients (eg 3.2.1 for Windows).
I have uninstalled Zulu and run through all the steps here to no avail:
FWIW, I get a log entry in /var/log/asterisk/zulu_err.log like the one below for each failing inbound call attempt.
Thanks,
Stuart
2019-01-24 15:07 +00:00: [2019-1-24 15:07:00.403] [ERROR] console - {“message”:"{“message”:“Write access denied”}",“stack”:“Error: {“message”:“Write access denied”}\n at SwaggerRequest.swaggerError [as errorCallback] (/var/www/html/admin/modules/zulu/node/node_modules/ari-client/lib/client.js:246:23)\n at Object.error (/var/www/html/admin/modules/zulu/node/node_modules/ari-client/node_modules/swagger-client/lib/swagger.js:1077:24)\n at EventEmitter.error (/var/www/html/admin/modules/zulu/node/node_modules/ari-client/node_modules/swagger-client/lib/swagger.js:1296:19)\n at emitOne (events.js:116:13)\n at EventEmitter.emit (events.js:211:7)\n at emit (/var/www/html/admin/modules/zulu/node/node_modules/ari-client/node_modules/swagger-client/node_modules/shred/lib/shred/request.js:454:21)\n at /var/www/html/admin/modules/zulu/node/node_modules/ari-client/node_modules/swagger-client/node_modules/shred/lib/shred/request.js:473:9\n at setBodyAndFinish (/var/www/html/admin/modules/zulu/node/node_modules/ari-client/node_modules/swagger-client/node_modules/shred/lib/shred/response.js:103:7)\n at IncomingMessage. (/var/www/html/admin/modules/zulu/node/node_modules/ari-client/node_modules/swagger-client/node_modules/shred/lib/shred/response.js:120:7)\n at emitNone (events.js:111:20)\n at IncomingMessage.emit (events.js:208:7)\n at endReadableNT (_stream_readable.js:1064:12)\n at _combinedTickCallback (internal/process/next_tick.js:138:11)\n at process._tickDomainCallback (internal/process/next_tick.js:218:9)”,“isOperational”:true,"__error_callsites":[{},{},{},{},{},{},{},{},{},{},{},{},{},{}]}
I’m still encountering this. A complete reinstall didn’t fix it in my case. I’m not getting the same symptoms as skwlilac, however.
From ‘fwconsole pm2 --log zulu --lines 50’ I get these errors/warns on incoming calls:
2019-01-24 18:14 +00:00: [1/24/2019 6:14:13 PM.578] [ERROR] console - {"message":"Invalid/unknown command: PJSIPShowRegistrationInboundContactStatuses. Use Action: ListCommands to show available commands.","stack":"Error: Invalid/unknown command: PJSIPShowRegistrationInboundContactStatuses. Use Action: ListCommands to show available commands.\n at EventEmitter.<anonymous> (/var/www/html/admin/modules/zulu/node/index.js:1:30941)\n at EventEmitter.g (events.js:199:16)\n at EventEmitter.emit (events.js:110:17)\n at process._tickDomainCallback (node.js:381:11)"}
OUT > 2019-01-24 18:14 +00:00: Unhandled rejection Error: Invalid/unknown command: PJSIPShowRegistrationInboundContactStatuses. Use Action: ListCommands to show available commands.
at EventEmitter.<anonymous> (/var/www/html/admin/modules/zulu/node/index.js:1:30941)
at EventEmitter.g (events.js:199:16)
at EventEmitter.emit (events.js:110:17)
at process._tickDomainCallback (node.js:381:11)
OUT >
==> /var/log/asterisk/zulu_out.log <==
2019-01-24 18:14 +00:00: [1/24/2019 6:14:13 PM.579] [INFO] console - Sending call push notification to 391
OUT >
==> /var/log/asterisk/zulu_err.log <==
2019-01-24 18:14 +00:00: Unhandled rejection Error: Invalid/unknown command: PJSIPShowRegistrationInboundContactStatuses. Use Action: ListCommands to show available commands.
at EventEmitter.<anonymous> (/var/www/html/admin/modules/zulu/node/index.js:1:30941)
at EventEmitter.g (events.js:199:16)
at EventEmitter.emit (events.js:110:17)
at process._tickDomainCallback (node.js:381:11)
OUT >
==> /var/log/asterisk/zulu_out.log <==
2019-01-24 18:14 +00:00: [1/24/2019 6:14:13 PM.722] [INFO] console - Sending Call event message 'inbound' to 391 [xgLM2l3kMgEURg+Rz6lPQw==]
OUT > 2019-01-24 18:14 +00:00: [1/24/2019 6:14:21 PM.864] [INFO] console - Call Event of 'missed' from WACO <xxxxxxxx> to 391
OUT > 2019-01-24 18:14 +00:00: [1/24/2019 6:14:21 PM.865] [INFO] console - Sending Call event message 'missed' to 391 [xgLM2l3kMgEURg+Rz6lPQw==]
OUT > 2019-01-24 18:14 +00:00: [1/24/2019 6:14:22 PM.004] [WARN] console - Unable to parse SIP/fpbx-1-wCrpQPHkhsKK-00000057 for channel tracking!
Common threads I’m seeing are being ‘unable to parse channel tracking’ and the ‘Invalid/Unknown command’ error. I’m having difficulty interpreting this to find the root cause, however. Any help or thoughts are appreciated.
Thanks for responding. I’m afraid that your response is too cryptic for me. I don’t understand what your suggesting I/we try doing to investigate further.
Thanks Andrew… forgive my ignorance, I don’t see how you do that. My System and Modules are all up-to-date according to the Web UI. I can see that the core asterisk package is indeed behind 13.24.
Thank you for your replies, Andrew.
I’m assuming I fall into the same boat then, since its an asterisk 13 command?
For future reference, what would be the best way to go about updating asterisk?
Through a FreePBX interface/process or directly through asterisk CLI?
I’m using Distro 10.13.66-17
FWIW I have resolved my situation. It seems that at some point Edge Mode had been switched on and several of my installed modules were ahead of the most recent stable modules. I have ‘knocked’ everything back to stable and Zulu inbound call indications has come back to life.
