- Joined
- Nov 28, 2018
- Messages
- 1
- Reaction score
- 0
Hi,
Some of my clients reported a weird behaviour regarding the conference system, especially when connecting to a conference call via dial-in with PIN.
The situation:
Client A (Webclient, No Chrome Extension, in this scenario audio only via built-in macbook speakers and mic) schedules a conference call where participants can enter by dialing our conference number and providing the conference PIN. All participants receive an email invitation, containing the necessary information.
Client B now tries to enter the conference:
Client B -internal,Webclient, Extension installed, Plantronics Blackwire 520 Headset - calls the conference extension. As expected, the PIN is asked, and when entered, the normal waiting music plays. So this works as intended.
But as soon as Client A tries to enter the conference via dial-in to the conference extension, it connects, but there is no sound at all, and the dialpad is grayed out. I can see in the admin console that the call connected.
For testing purposes, i disconnected Client B's hardware and tried to dial-in via built-in mic and speakers - same result. No sound, and dialpad grayed out. In this setup, I tried switching to the macOS App instead of webclient, which allowed me to connect to the conference extension with sound, asking for the PIN, but when entering it, after a brief delay it just returns "invalid PIN", even though I just connected to the same conference with the same PIN a few minutes earlier.
I also tried multiple conferences with different PINs, but the issue is reproducable every time.
At first I thought this might be an issue of audio Input/Output because of the disconnected headset, but the dialpad should not be grayed out if only the sound was "misdirected". Also, the colleague reported that external calls also work just fine.
For the moment, I am out of ideas to what would cause this.
We are running a locally hosted PBX on 16.0.5.619 on Linux, there are no firewall issues. We just updated 2 weeks ago from I think it was 16.04.
Any input is greatly appreciated, as I am out of ideas right now
Some of my clients reported a weird behaviour regarding the conference system, especially when connecting to a conference call via dial-in with PIN.
The situation:
Client A (Webclient, No Chrome Extension, in this scenario audio only via built-in macbook speakers and mic) schedules a conference call where participants can enter by dialing our conference number and providing the conference PIN. All participants receive an email invitation, containing the necessary information.
Client B now tries to enter the conference:
Client B -internal,Webclient, Extension installed, Plantronics Blackwire 520 Headset - calls the conference extension. As expected, the PIN is asked, and when entered, the normal waiting music plays. So this works as intended.
But as soon as Client A tries to enter the conference via dial-in to the conference extension, it connects, but there is no sound at all, and the dialpad is grayed out. I can see in the admin console that the call connected.
For testing purposes, i disconnected Client B's hardware and tried to dial-in via built-in mic and speakers - same result. No sound, and dialpad grayed out. In this setup, I tried switching to the macOS App instead of webclient, which allowed me to connect to the conference extension with sound, asking for the PIN, but when entering it, after a brief delay it just returns "invalid PIN", even though I just connected to the same conference with the same PIN a few minutes earlier.
I also tried multiple conferences with different PINs, but the issue is reproducable every time.
At first I thought this might be an issue of audio Input/Output because of the disconnected headset, but the dialpad should not be grayed out if only the sound was "misdirected". Also, the colleague reported that external calls also work just fine.
For the moment, I am out of ideas to what would cause this.
We are running a locally hosted PBX on 16.0.5.619 on Linux, there are no firewall issues. We just updated 2 weeks ago from I think it was 16.04.
Any input is greatly appreciated, as I am out of ideas right now