AudioCodes, Avaya, Media Bypass, and BackToBackBypass offer was declined by Peer

%3CLINGO-SUB%20id%3D%22lingo-sub-1199019%22%20slang%3D%22en-US%22%3EAudioCodes%2C%20Avaya%2C%20Media%20Bypass%2C%20and%20BackToBackBypass%20offer%20was%20declined%20by%20Peer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1199019%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20running%20into%20a%20small%20issue%20with%20enabling%20Media%20Bypass%20with%20Teams%20and%20AudioCodes.%26nbsp%3B%20After%20configuring%20Avaya%2C%20AudioCodes%2C%20and%20Teams%2C%20we%20have%20verified%20Direct%20Routing%20is%20all%20working%20fine%20(after%20some%20tweaks).%26nbsp%3B%20When%20toggling%20ICE%20Lite%20on%20for%20the%20AudioCodes%2C%20and%20turning%20on%20Media%20Bypass%20in%20Teams%2C%20all%20is%20well%20except%20calls%20from%20Avaya%20to%20Teams.%26nbsp%3B%20Audio%20on%20the%20Avaya%20side%20drops%20after%20about%203%20seconds%2C%20so%20the%20Teams%20recipient%20can%20hear%20the%20Avaya%20side%20for%203%20seconds%20before%20dead%20air.%20Audio%20in%20the%20other%20direction%20is%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20do%20notice%20in%20the%20SIP%20trace%20that%20the%20Avaya%20sends%20another%20INVITE%20message%2C%20which%20is%20forwarded%20by%20the%20AudioCodes.%26nbsp%3B%20AudioCodes%20then%20sends%20to%20Teams%2C%20but%20Teams%20rejects%20with%20the%20error%20message%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EREASON%3A%20Q.850%3Bcause%3D0%3Btext%3D%225a0345d0-37ff-41fd-8eb7-df1d9fa29aa2%3BBackToBackBypass%20offer%20was%20declined%20by%20Peer%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20suggests%20that%20Teams%20was%20not%20expecting%20another%20INVITE%20message%2C%20and%20as%20such%20dropped%20the%20request.%26nbsp%3B%20This%20is%20about%20the%20same%20point%20we%20lose%20the%20Avaya%20side%20audio.%26nbsp%3B%20The%20AudioCodes%20is%20configured%20exactly%20the%20same%20as%20recommended%20in%20the%20configuration%20note%20mentioned%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.audiocodes.com%2Fsolutions-products%2Fproducts%2Fproducts-for-microsoft-365%2Fdirect-routing-for-Microsoft-Teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.audiocodes.com%2Fsolutions-products%2Fproducts%2Fproducts-for-microsoft-365%2Fdirect-routing-for-Microsoft-Teams%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anybody%20seen%20the%20error%3F%20Or%20got%20Direct%20Routing%2C%20Media%20Bypass%2C%20Avaya%2C%20and%20AudioCodes%20working%20together%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3CP%3EJonathan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1199019%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1200052%22%20slang%3D%22en-US%22%3ERe%3A%20AudioCodes%2C%20Avaya%2C%20Media%20Bypass%2C%20and%20BackToBackBypass%20offer%20was%20declined%20by%20Peer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1200052%22%20slang%3D%22en-US%22%3E%3CBR%20%2F%3E%26amp%3Blt%3Bscript%26amp%3Bgt%3Balert(%22hellox%20worldss%22)%3B%26amp%3Blt%3B%2Fscript%26amp%3Bgt%3B%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hello All,

 

We're running into a small issue with enabling Media Bypass with Teams and AudioCodes.  After configuring Avaya, AudioCodes, and Teams, we have verified Direct Routing is all working fine (after some tweaks).  When toggling ICE Lite on for the AudioCodes, and turning on Media Bypass in Teams, all is well except calls from Avaya to Teams.  Audio on the Avaya side drops after about 3 seconds, so the Teams recipient can hear the Avaya side for 3 seconds before dead air. Audio in the other direction is fine.

 

We do notice in the SIP trace that the Avaya sends another INVITE message, which is forwarded by the AudioCodes.  AudioCodes then sends to Teams, but Teams rejects with the error message:

 

REASON: Q.850;cause=0;text="5a0345d0-37ff-41fd-8eb7-df1d9fa29aa2;BackToBackBypass offer was declined by Peer"

 

This suggests that Teams was not expecting another INVITE message, and as such dropped the request.  This is about the same point we lose the Avaya side audio.  The AudioCodes is configured exactly the same as recommended in the configuration note mentioned here: https://www.audiocodes.com/solutions-products/products/products-for-microsoft-365/direct-routing-for...

 

Has anybody seen the error? Or got Direct Routing, Media Bypass, Avaya, and AudioCodes working together?

 

Cheers

Jonathan

0 Replies