03-21-2017 06:31 PM
Call Events indicate a RAS disengageRequest received
Would like to know what triggered the disengage request that caused all endpoints to be disconnected
03-21-2017 08:16 PM
welcome to the Polycom Community.
It is always useful to include the currently used Software version as issues experienced or a question asked may already be addressed in a newer release.
Please also include if you are using any other Polycom infrastructure and the software version of this.
This also allows yourself and others to check against current software release notes, Administrator Guides or FAQ post’s.
The above is also stated in the "Read First"
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
03-27-2017 06:55 PM
These signals are pretty ubiquitous and if you dive into most of your call details on dma you should see them at the end of every h323 session. If all your sites dropped at the same time and it wasn't initiated by someone ending the conference from RMX, web app, or dtmf tone you should look at network issues.
03-27-2017 08:21 PM
Yes from the DMA perspective the logging indicates ‘Endpoint ended the call normally.’
We do not operate an RMX MCU but instead have a Pexip Infinty MCU, in which audio calls & WebRTC calls which are both forwarded directly to the Pexip MCU did not drop. So the common denominator is the endpoints going via the DMA.
So I can rule out someone ending the conference from the RMX. This could only be done idividually from the pexip interface & they all have the same time stamp so I rule that out.
I guess you can never rule out the network but it is a bit of a cope out. What network events can initiate 4 endpoints to drop simultaniously, xxx amount of milliseconds without a packet being received? One would think the DMA would log that as an event.
Full logs have been passed onto Polycom, so will see what they come back with