Teams call transfer failed - Audiocodes VE
Dear Colleagues, I have setup an Audiocodes VE Direct Routing SBC, but during the tests I noted that I was not able to forward calls. As I can see, during the REFER process there is a 488 Not Acceptable answer, because of media mismatch between the Mediant and the O365. The p2p calls are working properly in every direction. Have you experienced this kind of problem? I have attached the SIP log (in .xlsx format, since .txt is not allowed), and the participants are: 10055 – Teams (Transferor) 20055 – CUCM registered phone (Transferee) 80000 – Mediant registered phone (Transfer target) Thanks, Laszlo
PSTN calls drop with-in 15 - 30 mins with Audiocodes SBC
Hi Community, Recently, I have come across a scenario worth sharing. PSTN calls drops after 15 mins or 30 mins with Audio Codes SBC or Gateway. This can be related or occur due to numerous reason, however if everything is in place (Network to Configuration) and still the call fails, then you can try the below and if it makes the difference. User makes PSTN call > the flow and connectivity is established > after 15 or 30 mins you see BYE message generated resulting in call drop. changing/modifying the "RTCPActiveCalls" and "EnableSessionTimer" may help or simple does't make any difference. Upon isolation, found that issue is mostly triggered due to a setting in Audio Codes S.B.C "Reset SRTP Upon Re-Key" is enabled (usually disabled by default) By going in to the IP profiles > disabling the setting in AudioCodes the issue was resolved and calls no longer were dropped. P.S - This solution may or may not help you (no harm in trying), But its best recommended to contact support and take assistance if needed 🙂Media Optimization for Direct Routing: Failover of ProxySBC for PSTNGateway
We are currently building Direct Routing voice infra for MS Teams with Media Optimization and Always Bypass mode using Audiocodes SBCs. Aim is to have two centralized ProxySBCs, primary and standby, shared over many PSTNGateways. When we define PSTN Gateway and Virtual Network Topology in Teams we can only define a single ProxySBC parameter for each PSTNGateway: PS C:\> Set-CsOnlinePSTNGateway -Identity <Identity> -GatewaySiteID <site ID> -MediaBypass <true/false> -BypassMode <Always/OnlyForLocalUsers> -ProxySBC <proxy SBC FQDN or $null> We would like to define geographical failover strategy for Calls to use standby ProxySBC. Are you aware about any possible option to achieve automatic ProxySBC failover? Options that comes to my mind, we could: Duplicate PSTNGateways once with Primary ProxySBC and second with Standby ProxySBC and play with VoicePolicies, but that would involve 2 different FQDNs and 2 Certificates for 1 same thing. Do Manual failover to Standby ProxySBC with a script but that misses automation. Build HA Pair but that's not available in two geographical different locations in our environment. Any option I overlooked how Microsoft plan ProxySBC failover? Any comments greatly appreciated.Default Security permissions for Audiocodes Mediant in Azure
After troubleshooting an issue with our OVOC server not being able to access an SBC in Azure and modifying a few firewall restrictions discovered the default network port permissions on Azure. Added SNMP and allowed OVOC to talk to the SBC. This is a quick example of the rule we added, instead of using any on the source we did modify that to match the IP address of the OVOC server. Hope this helps someone else when spinning up an AudioCode SBC within Azure.
