Difference between revisions of "AlphaCom Integration Troubleshooting"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
[[File:Alphacom integration group call 1.PNG|thumb|left|500px|Allow SIP Stations in Group Calls]] | [[File:Alphacom integration group call 1.PNG|thumb|left|500px|Allow SIP Stations in Group Calls]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | In '''Exchange & System''' | + | In '''Exchange & System''' > '''System''' > '''VoIP''' <br> |
Tick of '''Allow SIP Stations in Group Calls and as default speakers in SX Conference''' <br> | Tick of '''Allow SIP Stations in Group Calls and as default speakers in SX Conference''' <br> | ||
Latest revision as of 10:01, 8 May 2018
This article describes the most common challenges with Exigo - AlphaCom integration.
Changes to SIP configuration require a reboot of both Exigo System Controller and AlphaCom.
Updating from Exigo v. 1.3.2.10 LA (Limited Availability) to Exigo v. 1.3.3.0 GA (General Availability)
Allow SIP Stations in Group Call
By default SIP Stations cannot be part of a group call.
In Exchange & System > System > VoIP
Tick of Allow SIP Stations in Group Calls and as default speakers in SX Conference
In the Group Call to Exigo the Automatic M-key must be ticked of.
Automatic M-key from all stations (or alternative Automatic M-key only from SIP calls).
Exigo unable to call groups in AlphaCom
In order for Exigo to be able to call groups in AlphaCom the Exigo Node flag must be enabled.
Go to Exchange & System > AlphaCom node > Net Routing > Exigo node > Change
Enable the Exigo Node flag.