No MoH from SBC when transferring

%3CLINGO-SUB%20id%3D%22lingo-sub-2404360%22%20slang%3D%22en-US%22%3ENo%20MoH%20from%20SBC%20when%20transferring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2404360%22%20slang%3D%22en-US%22%3E%3CP%3EFound%20an%20interesting%20scenario%20that%20breaks%20your%20SBC%20MoH%20for%20call%20transfers.%20If%20you%20are%20using%20the%20Teams%20desktop%20client%20to%20answer%20calls%2C%20and%20you%20happen%20to%20put%20a%20call%20on%20hold%20and%20then%20resume%20it%2C%20you%20will%20then%20no%20longer%20receive%20re-invites%20from%20Teams%20when%20you%20press%20the%20Transfer%20or%20Consult%20then%20Transfer%20buttons%20for%20the%20rest%20of%20the%20call.%20This%20means%20your%20SBC%20has%20no%20idea%20that%20it%20is%20meant%20to%20start%20the%20local%20playback%20of%20its%20local%20MoH%20file%20for%20transfers.%20This%20will%20only%20happen%20if%20you%20put%20a%20call%20on%20hold%20and%20resume%20it%20before%20attempting%20transfers.%20If%20you%20attempt%20a%20transfer%20without%20using%20hold%20beforehand%20then%20there%20is%20no%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20that%20Teams%20no%20longer%20sends%20re-invites%20for%20calls%20that%20are%20placed%20on%20hold%20and%20resumed%20in%20the%20desktop%20client%2C%20but%20then%20it%20forgets%20that%20it's%20meant%20to%20do%20it%20if%20you%20want%20to%20transfer%20the%20calls%20afterwards.%20Not%20and%20issue%20on%20the%20Poly%20CCX%20400%20desk%20phones%20that%20I%20tested%20with%20as%20they%20still%20send%20re-invites%20for%20call%20hold%20and%20resume.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20come%20across%20this%20and%20is%20there%20anyway%20to%20change%20the%20Teams%20behavior%20of%20no%20re-invites%20for%20Hold%20and%20Resume%20with%20the%20desktop%20clients%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tested%20this%20on%202%20separate%20Teams%20tenants%20with%20SBCs%20from%20different%20vendors%20for%20validation.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2404360%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDesktop%20Client%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHold%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETransfer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

Found an interesting scenario that breaks your SBC MoH for call transfers. If you are using the Teams desktop client to answer calls, and you happen to put a call on hold and then resume it, you will then no longer receive re-invites from Teams when you press the Transfer or Consult then Transfer buttons for the rest of the call. This means your SBC has no idea that it is meant to start the local playback of its local MoH file for transfers. This will only happen if you put a call on hold and resume it before attempting transfers. If you attempt a transfer without using hold beforehand then there is no issue.

 

It seems that Teams no longer sends re-invites for calls that are placed on hold and resumed in the desktop client, but then it forgets that it's meant to do it if you want to transfer the calls afterwards. Not and issue on the Poly CCX 400 desk phones that I tested with as they still send re-invites for call hold and resume.

 

Has anyone else come across this and is there anyway to change the Teams behavior of no re-invites for Hold and Resume with the desktop clients?

 

I have tested this on 2 separate Teams tenants with SBCs from different vendors for validation. 

0 Replies