Zulu - Unable to Establish Call

Commercial Modules Zulu
1

Hi All,

We’ve come up a bit of an odd issues that has started on our PBX.

No calls connect via Zulu. When making a call it rings on both sides, you can pick up, but the calling side has a message that says “Connecting…” and then after 20-30 seconds the call disconnects.

Checking the debug log and nothing is jumping out as being wrong. There is nothing logged in the zulu_err log during the call or disconnection either.

image

zulu_out shows:

2023-05-04 09:09 +01:00: [2023-5-4 09:09:39.934] [INFO] console - Getting mobile tokens of 741

2023-05-04 09:09 +01:00: [2023-5-4 09:09:40.124] [INFO] console - Call Event of 'inbound' from Test-1 <740> to 741

2023-05-04 09:09 +01:00: [2023-5-4 09:09:40.125] [WARN] console - Rejecting call notification to client as previous notification already sent

2023-05-04 09:09 +01:00: [2023-5-4 09:09:40.312] [INFO] console - Sending Call event message 'inbound' to 741 [gPugvMXgXpOXjgyoY/qPxg==]

2023-05-04 09:09 +01:00: [2023-5-4 09:09:40.314] [INFO] console - Sending Call event message 'inbound' to 741 [EhSj3I0FGuOwQg+0JUXbnw==]

2023-05-04 09:09 +01:00: [2023-5-4 09:09:42.913] [INFO] console - Call Event of 'answered' from Test-1 <740> to 741

2023-05-04 09:09 +01:00: [2023-5-4 09:09:42.913] [INFO] console - Sending Call event message 'answered' to 741 [gPugvMXgXpOXjgyoY/qPxg==]

2023-05-04 09:09 +01:00: [2023-5-4 09:09:42.914] [INFO] console - Sending Call event message 'answered' to 741 [EhSj3I0FGuOwQg+0JUXbnw==]

2023-05-04 09:10 +01:00: [2023-5-4 09:10:07.375] [WARN] console - Unable to parse SIP/SIP-Out-00001dd5 for channel tracking!

2023-05-04 09:10 +01:00: [2023-5-4 09:10:09.796] [INFO] console - Call Event of 'hangup' from Test-1 <740> to 741

2023-05-04 09:10 +01:00: [2023-5-4 09:10:09.797] [INFO] console - Sending Call event message 'hangup' to 741 [gPugvMXgXpOXjgyoY/qPxg==]

2023-05-04 09:10 +01:00: [2023-5-4 09:10:09.798] [INFO] console - Sending Call event message 'hangup' to 741 [EhSj3I0FGuOwQg+0JUXbnw==]

There are two points from the above though, which I am unsure about:

“Unable to parse SIP/SIP-Out-00001dd5” - I can’t find anything online about this error. It is a warning and not an error, so could be nothing

“Sending Call event message” - This appears twice, again, may not be anything to be concerned about.

I have reinstalled Zulu several times, including with the --force switch. As the PBX has over 100 users I haven’t completely uninstalled Zulu and reinstalled, as when I was testing this all the users got deleted and would need creating again.

Up until recently Zulu was working absolutely fine, this seemed to randomly occur, but we are unware of any changes that could have caused it.

2

Additionally, I watched the asterisk log while the call was made (specifically for anything with the extension 741 in it). Here is the output:

3

Is moving to Sangoma Talk an option for you? Works so much better then Zulu did.

4

Unfortunately not - its a large PBX with 100’s of users who are currently on Zulu Desktop, switching out would be a large task.

It seems the issue is sorted, but to help others out let me go through what happened:

  1. Configured 2 extensions for testing
  2. Tried to make calls between the two extensions, from either side
  3. Number wouldn’t connect
  4. Contacted Sangoma support (the PBX has platinum support)
  5. Told Zulu is no longer developed, ticket closed with no further comment.
  6. Spoke to our Sangoma account manager - advised the same that Zulu is not EOL but no support will be given. I am still battling with this point as how can something no longer be supported but not EOL.

How I “fixed” the issue:

  1. Checked the forums for other people with the same issue
  2. Reinstalled webrtc module
  3. Calls between the two test extensions still wouldn’t connect - i.e. webrtc didn’t fix the issue
  4. Opened this forum post
  5. Told on the following working day that the extensions are working and received thanks for fixing the issue
  6. Checking the test extensions it seems there was a local firewall blocking port 8002 (facepalm on my part)
  7. Fixed firewall issue and extensions were working.

Previous tests done by my colleagues, who definitely did not have any firewall issues as they use Zulu daily with no issues, were not working. I believe that reinstalling webrtc was the fix for us, nothing else worked.

5

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.