MS Teams Direct Routing - Internal call transfer failure

%3CLINGO-SUB%20id%3D%22lingo-sub-754902%22%20slang%3D%22en-US%22%3EMS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754902%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20organisation%20is%20planning%20a%20move%20to%20direct%20routing.%20We%20have%20an%20AudioCodes%20VE%20SBC.%20I've%20been%20working%20on%20this%20for%20awhile%20and%20got%20everything%20to%20a%20pretty%20decent%20state.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20come%20across%20an%20issue%20which%20is%20fairly%20new%20as%20I%20remember%20testing%20this%20months%20ago%2C%20when%20I%20was%20still%20trying%20to%20figure%20out%20how%20to%20deal%20with%20REFERs%20coming%20from%20MS%20Teams%20on%20call%20transfers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20the%20call%20flow%20is%20as%20follows%3A%3C%2FP%3E%3CP%3EIncoming%20call%20from%20SBC%20to%20MS%20Teams%20-%26gt%3B%20MS%20Teams%20user%20transfers%20the%20call%20to%20internal%20user%20-%26gt%3B%20Call%20fails%20as%20MS%20Teams%20generates%20a%20REFER%20back%20to%20the%20SBC%20rather%20than%20route%20the%20call%20internally%20to%20MS%20Teams%20user%20target.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20issue%20I'm%20observing%20aside%20from%20MS%20Teams%20routing%20the%20transfer%20leg%20of%20the%20call%20is%20that%20the%20REFER-TO%20user%20part%20of%20the%20URI%20is%20blank.%20Please%20see%20the%20attached%20screenshot.%3CBR%20%2F%3E%3CBR%20%2F%3EIts%20as%20if%20MS%20Teams%20is%20treating%20this%20as%20an%20external%20transfer%20and%20does%20not%20know%20how%20to%20populate%20the%20user%20part%20of%20the%20REFER-TO%20header.%20I've%20tested%20this%20with%20both%20users%20set%20up%20with%20Phone%20system%20and%20DDIs%20assigned%20to%20the%20user%20and%20users%20which%20have%20no%20phone%20system%20add-on%20or%20assigned%20DDI.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EPlease%20note%20that%20if%20you%20tried%20to%20transfer%20the%20call%20to%20a%20PSTN%20number%2C%20that%20works%20fine.%20I'm%20unsure%20if%20this%20would%20be%20something%20config%20related%20within%20our%20Teams%20tenancy%20or%20a%20genuine%20bug.%20I'm%20more%20inclined%20that%20this%20is%20the%20former%20rather%20than%20the%20latter%20as%20it%20does%20seem%20like%20fairly%20basic%20functionality%20and%20I'm%20confident%20this%20used%20to%20work%20a%20few%20months%20ago.%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20advice%20would%20be%20appreciated.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EKind%20Regards%2C%3C%2FP%3E%3CP%3ESim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-754902%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-756217%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-756217%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Sim%2C%3C%2FP%3E%3CP%3EWe've%20got%20exactly%20the%20same%20behaviour%20when%20trying%20to%20transfer%20calls%20that%20came%20from%20PSTN%20network%20and%20got%20answered%20by%20one%20of%20our%20Teams%20users%20and%20when%20they%20try%20to%20transfer%20to%20another%20Teams%20user.%20REFER-TO%20doesn't%20contain%20any%20LineURI%20or%20telephone%20number%20to%20complete%20the%20transfer.%20Did%20you%20have%20any%20luck%20fixing%20this%20issue%3F%20Also%2C%20I'm%20not%20sure%20if%20this%20was%20working%20before%20or%20not.%20But%20you%20seem%20to%20be%20correct%20in%20regards%20to%20Teams%20treating%20internal%20transfer%20as%20external%20one%20and%20sending%20SIP%20REFER%20back%20to%20SBC%20without%20providing%20any%20additional%20details%20in%20regards%20where%20the%20call%20should%20be%20actually%20connected%20or%20transferred%20to.%20When%20transferring%20to%20external%20number%20this%20works%20perfectly%20fine%2C%20REFER-TO%20contains%20an%20external%20number%20and%20can%20be%20processed%20by%20our%20SBC.%20BTW%2C%20can%20you%20tell%20what%20SBC%20are%20you%20using%3F%20Is%20it%20AudioCodes%20or%20Ribbon%20one%3F%20Or%20something%20not%20currently%20certified%20by%20Microsoft%3F%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-756503%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-756503%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3BWe're%20using%20AudioCodes%2C%20and%20config%20wise%20its%20fine.%20It%20handles%20REFERs%20just%20fine.%20The%20issue%20here%20is%20that%20MS%20Teams%20should%20never%20had%20sent%20this%20REFER%20out%20the%20SBC%2C%20it%20should%20have%20handled%20it%20within%20the%20Teams%20environment%20as%20its%20a%20transfer%20from%20one%20Teams%20user%20to%20another.%20This%20only%20thing%20I%20suspect%20config%20wise%20is%20voice%20route%20regex%20I'm%20using%2C%20as%20its%20pretty%20much%20a%20catch%20all%20e.g.%20%22%3CSPAN%20class%3D%22s1%22%3E.*%22%26nbsp%3B%3CBR%20%2F%3EI've%20now%20made%20it%20more%20strict%20to%20capture%20digit%20patterns%20rather%20than%20all%20chars%20to%20see%20if%20the%20issue%20persists.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22s1%22%3EIt%20makes%20no%20sense%20as%20I%20can%20call%20users%20internally%2C%20it%20only%20happens%20when%20PSTN%20call%20comes%20in%20from%20the%20direct%20Routing%20SBC%2C%20so%20Teams%20appears%20to%20be%20applying%20a%20different%20call%20routing%20logic%20when%20applying%20the%20transfer.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22s1%22%3EOut%20of%20curiosity%20can%20you%20let%20me%20know%20what%20your%20voice%20route%20pattern%20looks%20like%3F%20Was%20it%20a%20catch%20all%20like%20mine%20or%20is%20it%20more%20strict%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22s1%22%3EThanks%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22s1%22%3ESim%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-756562%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-756562%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20I'm%20using%20the%20same%20voice%20pattern%2C%20%22.*%22%20to%20send%20all%20digits%20without%20any%20normalization%20to%20our%20SIP%20trunk.%20You're%20right%2C%20maybe%20the%20issue%20is%20because%20of%20that%2C%20I%20will%20update%20voice%20rules%20tomorrow%20to%20make%20it%20strictly%20country-based%2C%20like%20'%5E%2B44.*'%20to%20see%20if%20that%20helps!%20Good%20point%2C%20mate!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20yes%2C%20SIP%20REFER%20shouldn't%20be%20coming%20back%20to%20PBX%20when%20we're%20doing%20an%20internal%20transfer%20from%20one%20Teams%20User%20to%20another%20one%2C%20but%20it%20does%20for%20some%20reason%2C%20that's%20the%20problem.%3CBR%20%2F%3E%3CBR%20%2F%3EI'll%20let%20you%20know%20here%20how%20it%20goes%20and%20thanks%20for%20your%20reply!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-760045%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-760045%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Sims%2C%3C%2FP%3E%3CP%3EI've%20removed%20the%20%22.*%22%20rule%20from%20my%20installation%20and%20created%20all%20specific%20rules%20for%20DIDs%20and%20still%20no%20luck%2C%20I%20can%20see%20SIP%20REFER%20coming%20back%20to%20PBX%20when%20I'm%20trying%20to%20transfer%20call%20that%20came%20from%20PSTN%20to%20Teams%20user.%20No%20luck%20here%2C%20unfortunately.%20Did%20you%20have%20any%20luck%20with%20this%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772977%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772977%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3BI%20had%20no%20luck%20with%20changing%20the%20voice%20route%2C%20so%20ended%20up%20raising%20it%20with%20MS%20support.%3C%2FP%3E%3CP%3EApparently%20if%20you%20disable%20REFER%20as%20an%20allowed%20method%20within%20your%20SBC's%20signalling%20messages%2C%20then%20MS%20Teams%20does%20not%20use%20REFER%20for%20transfers%20and%20just%20re-INVITEs%20to%20the%20SBC.%20That%20way%20the%20internal%20transfers%20work%20perfectly%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-773103%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-773103%22%20slang%3D%22en-US%22%3EHow%20did%20you%20disable%20REFER%3F%20I%20mean%20-%20does%20your%20SBC%20sends%20some%204xx%20code%20when%20MS%20sends%20a%20SIP%20REFER%20message%3F%20Or%20somehow%20different%3F%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-773127%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-773127%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%2C%20not%20by%20rejecting%20the%20REFER%20with%20a%20response%20code.%20I%20basically%20did%20a%20message%20manipulation%20rule%20to%20re-build%20the%20Allow%20header%20for%20calls%20to%20MS%20Teams%20without%20including%20REFER.%20Which%20vendor%20are%20you%20using%3F%20If%20you%20have%20an%20AudioCodes%20as%20well%2C%20I%20can%20give%20you%20the%20rule%20syntax.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-773167%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-773167%22%20slang%3D%22en-US%22%3ENo%2C%20we're%20using%20a%20custom%20SBC%2C%20but%20yes%2C%20that%20was%20my%20second%20guess%20-%20to%20strip%20REFERs%20from%20packets.%20Thanks%20a%20lot%2C%20I'll%20give%20it%20a%20go%20and%20let%20you%20know%20if%20it%20works%20for%20me!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-773659%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-773659%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3Byou%20seem%20to%20be%20correct!%20I've%20just%20edited%20all%20messages%20that%20were%20coming%20from%20PSTN%20side%20of%20our%20SBC%20and%20stripped%20'REFER'%20on%20SBC%20in%20'Allow'%20field%20-%20and%20yes%2C%20Microsoft%20started%20to%20transfer%20calls%20correctly!%20Thanks%20a%20lot%2C%20mate%2C%20I've%20already%20read%20that%20disabling%20SIP%20REFER%20method%20helped%20some%20people%2C%20but%20I%20was%20trying%20to%20reply%20with%204xx%20or%205xx%20when%20receiving%20REFER%20from%20MS%20side%2C%20while%20I%20should%20have%20just%20removed%20that%20REFER%20method%20from%20SIP%20'Allow'%20list!%20By%20the%20way%2C%20looking%20at%20the%20packets%20coming%20from%20Microsoft%20side%20I%20can%20see%20that%20they%20don't%20send%20REFER%20in%20allowed%20method%20list!%20Here's%20an%20example%3A%3CBR%20%2F%3E%3CBR%20%2F%3ECONTENT-LENGTH%3A%20685%3CBR%20%2F%3EMIN-SE%3A%2090%3CBR%20%2F%3ESUPPORTED%3A%20timer%3CBR%20%2F%3EUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2019.7.4.9%20i.USWE2.4%3CBR%20%2F%3ECONTENT-TYPE%3A%20application%2Fsdp%3CBR%20%2F%3EALLOW%3A%20INVITE%3CBR%20%2F%3EALLOW%3A%20ACK%3CBR%20%2F%3EALLOW%3A%20OPTIONS%3CBR%20%2F%3EALLOW%3A%20CANCEL%3CBR%20%2F%3EALLOW%3A%20BYE%3CBR%20%2F%3EALLOW%3A%20NOTIFY%3CBR%20%2F%3ESESSION-EXPIRES%3A%201800%3Brefresher%3Duas%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EThanks%20again%20for%20your%20help%20and%20I'm%20glad%20everything%20is%20working%20fine%20for%20you%20too%20now!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783634%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783634%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20confirm%20this%20behavior%2C%20just%20that%20REFER%20triggered%20transfer%20is%20most%20common%20way%20for%20it%20and%20only%20fully%20standardized%20one.%20If%20your%20SBC%20is%20capable%20to%20terminate%20REFER%20note%20that%20MS%20still%20clearly%20indicates%20in%20Refer-To%20where%20to%20send%20INVITE%20back%3A%26nbsp%3B%3C%2FP%3E%3CP%3EREFER-TO%3A%20%26lt%3B5061%26gt%3B%26lt%3B5061%26gt%3Bsip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Aorgid%3Afce2158f-0e99-4ff7-a0b3-5b6b87d16689%3C%2FP%3E%3C%2FLINGO-BODY%3E%26lt%3B5061%26gt%3B%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20and%20making%20sure%20you%20fill%20RURI%20with%20Refer-To%20and%20Contact%20uri-host%20correctly%20you%20will%20see%20MS%20does%20rest%20of%20the%20job%20nicely%20for%20REFER%20case%20too.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783723%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783723%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380677%22%20target%3D%22_blank%22%3E%40Matej_Maric%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20shows%20where%20to%20send%20INVITE%20to%2C%20but%20it%20doesn't%20have%20a%20DID%20or%20username%20in%20SIP%20R-URI%20so%20SBC%20can't%20figure%20out%20where%20to%20dial%20to.%20SBC%20uses%20PSTN-type%20dialing%2C%20so%20it%20needs%20some%20LineURI%20or%20DID%20to%20send%20INVITE%20to%2C%20like%20%2B44XXXXXXXX%40sip.pstnhub.microsoft.com.%20Otherwise%20it%20can't%20decide%20what%20to%20put%20in%20SIP%20INVITE%20method%20as%20'To'%20field.%20I've%20tried%20to%20update%20SIP%20INVITE%20to%20whatever%20is%20in%20REFER-TO%20header%20and%20send%20it%20back%20to%20Microsoft%2C%20but%20I%20was%20getting%20a%20400%20Bad%20Request%20back.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EREFER-TO%3A%20%26lt%3B5061%26gt%3B%26lt%3B5061%26gt%3Bsip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Aorgid%3Afce2158f-0e99-4ff7-a0b3-5b6b87d16689%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%26lt%3B5061%26gt%3B%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThere's%20no%20user%20part%20in%20this%20SIP%20RURI%2C%20only%20host.%20What%20should%20be%20put%20in%20To%20header%3F%20Contact%20header%20is%20obvious%2C%20it's%20our%20SBC%20Contact.%3C%2FSPAN%3E%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783753%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783753%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20thing%20is%20that%20SBC%20should%20only%20respect%20Refer-to%20header%20by%20means%20of%20SIP.%20REFER%20comes%20without%20user%20part%20but%20it's%20still%20fair%20enough%20and%20legal.%20So%20what%20my%20SBC%20does%20as%20last%20resort%20to%20send%20INVITE%20out%20is%20DNS%20query%20for%20hostname%20in%20Refer-To%20and%20fills%20RURI%20and%20To%20in%20same%20fashion%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EINVITE%20sip%3Asip.pstnhub.microsoft.com%3A5061%3Bx-m%3D8%3Aorgid%3Afce2158f-0e99-4ff7-a0b3-5b6b87d16689%3Btransport%3Dtls%20SIP%2F2.0%3CBR%20%2F%3EVia%3A%20SIP%2F2.0%2FTLS%20192.168.65.100%3A5061%3Bbranch%3Dz9hG4bKvahihb0040adpr8tb320.1%3CBR%20%2F%3ECSeq%3A%201%20INVITE%3CBR%20%2F%3EContact%3A%20%26lt%3B5061%26gt%3B%3Bsip.ice%3CBR%20%2F%3EFrom%3A%20%26lt%3B%26gt%3B%3Btag%3D11241SIPpTag011%3CBR%20%2F%3ETo%3A%20%26lt%3B5061%26gt%3B%3CBR%20%2F%3EContent-Type%3A%20application%2Fsdp%3CBR%20%2F%3EContent-Length%3A%20425%3CBR%20%2F%3EReferred-By%3A%20%26lt%3B5061%26gt%3B%3CBR%20%2F%3ECall-ID%3A%208f09e11d9183f754c525a0d4ce2aea46%3CBR%20%2F%3ESupported%3A%20replaces%3CBR%20%2F%3EMax-Forwards%3A%2070%3C%2FP%3E%3C%2FLINGO-BODY%3E%26nbsp%3B%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20that's%20just%20enough...%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783755%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783755%22%20slang%3D%22en-US%22%3E%3CP%3Eobviously%20we%20dont%20use%20same%20vendor%20SBC%20but%20standard%20wise%20logic%20should%20remain%20the%20same%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-784350%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-784350%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380677%22%20target%3D%22_blank%22%3E%40Matej_Maric%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20detailed%20description%2C%20I%20will%20try%20to%20reproduce%20this%20behaviour%20on%20my%20SBC%2C%20but%20it%20looks%20really%20strange%20to%20me%20that%20MS%20sends%20a%20SIP%20REFER%20packet%20back%20to%20SBC%20that%20connects%20calls%20to%20PSTN%20and%20uses%20LineURI%20telephone%20numbers%20for%20that.%20According%20to%20RFC%20it%20should%20provide%20a%20proper%20username%20or%20DID%20in%20such%20case.%20From%20what%20I%20can%20see%20now%20it's%20much%20simpler%20to%20just%20disallow%20REFER%20method%20and%20let%20Microsoft%20Teams%20handle%20internal%20call%20transfers%20on%20their%20side%2C%20which%20is%20more%20logical%2C%20rather%20than%20implementing%20such%20call%20forking.%20Anyway%2C%20your%20help%20is%20much%20appreciated%20and%20SIP%20INVITE%20packet%20is%20a%20perfect%20example%20on%20what%20I%20should%20try%20to%20achieve.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785272%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785272%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380677%22%20target%3D%22_blank%22%3E%40Matej_Maric%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%2C%20something%20is%20not%20working%20for%20me%2C%20I've%20got%20an%20INVITE%20sent%20same%20way%20as%20you're%20doing%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EINVITE%20sip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Aorgid%3A7709b36f-1f10-4b1c-8a0f-9c0e5390c86c%20SIP%2F2.0%3CBR%20%2F%3EVia%3A%20SIP%2F2.0%2FTLS%20X.X.X.X%3A5061%3Bbranch%3Dz9hG4bKf26f.503bdc4.0%3Bi%3D54849946%3CBR%20%2F%3EFrom%3A%20%22XXXXXXXXXXXX%22%20%26lt%3B0421273494%26gt%3B%3Btag%3Da1d8a1ca-d330-4251-811d-35fa1a797c64%3CBR%20%2F%3ETo%3A%20%26lt%3B%26lt%3B5061%26gt%3Bsip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Aorgid%3A7709b36f-1f10-4b1c-8a0f-9c0e5390c86c%26gt%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%26lt%3B5061%26gt%3B%3CBR%20%2F%3ECall-ID%3A%201fa2f0d0-ba41-4e4d-83be-fbef9d0739c6%3CBR%20%2F%3ECSeq%3A%2010432%20INVITE%3CBR%20%2F%3EAllow%3A%20OPTIONS%2C%20REGISTER%2C%20SUBSCRIBE%2C%20NOTIFY%2C%20PUBLISH%2C%20INVITE%2C%20ACK%2C%20BYE%2C%20CANCEL%2C%20UPDATE%2C%20PRACK%2C%20REFER%3CBR%20%2F%3ESupported%3A%20100rel%2C%20timer%2C%20replaces%2C%20norefersub%3CBR%20%2F%3ESession-Expires%3A%201800%3CBR%20%2F%3EMin-SE%3A%2090%3CBR%20%2F%3EMax-Forwards%3A%2069%3CBR%20%2F%3EContent-Type%3A%20application%2Fsdp%3CBR%20%2F%3EContent-Length%3A%20346%3CBR%20%2F%3EContact%3A%20%3CGATEWAY%3E%3CGATEWAY%3E%3C%2FGATEWAY%3E%3C%2FGATEWAY%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20I'm%20getting%20following%20reply%20back%20from%20Microsoft%3A%3CBR%20%2F%3E%3CBR%20%2F%3ESIP%2F2.0%20400%20Bad%20Request%3CBR%20%2F%3EFROM%3A%20%22XXXXXXXXX%22%26lt%3B0421273494%26gt%3B%3Btag%3Da1d8a1ca-d330-4251-811d-35fa1a797c64%3CBR%20%2F%3ETO%3A%20%26lt%3B5061%26gt%3B%26lt%3B5061%26gt%3B%26nbsp%3B%3CBR%20%2F%3ECSEQ%3A%2010432%20INVITE%3CBR%20%2F%3ECALL-ID%3A%201fa2f0d0-ba41-4e4d-83be-fbef9d0739c6%3CBR%20%2F%3EVIA%3A%20SIP%2F2.0%2FTLS%20X.X.X.X%3A5061%3Bbranch%3Dz9hG4bKf26f.503bdc4.0%3Bi%3D54849946%3CBR%20%2F%3EREASON%3A%20Q.850%3Bcause%3D111%3Btext%3D%22a5d458f9-14c0-4cc4-8c10-202277af11e9%3BUnable%20to%20parse%20RURI.%22%3CBR%20%2F%3ECONTENT-LENGTH%3A%200%3CBR%20%2F%3EALLOW%3A%20INVITE%3CBR%20%2F%3EALLOW%3A%20ACK%3CBR%20%2F%3EALLOW%3A%20OPTIONS%3CBR%20%2F%3EALLOW%3A%20CANCEL%3CBR%20%2F%3EALLOW%3A%20BYE%3CBR%20%2F%3EALLOW%3A%20NOTIFY%3CBR%20%2F%3ESERVER%3A%20Microsoft.PSTNHub.SIPProxy%20v.2019.7.4.9%20i.USWE2.3%20%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20sure%20what%20I'm%20doing%20wrong%2C%20any%20ideas%3F%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785275%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785275%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380677%22%20target%3D%22_blank%22%3E%40Matej_Maric%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EUnfortunately%2C%20that%20doesn't%20work%20for%20me%2C%20I'm%20sending%20same%20INVITE%20packet%20as%20you%20do%20but%20I'm%20getting%20back%20a%20'400%20Bad%20Request'%20with%20a%20REASON%3A%3CBR%20%2F%3E%3CBR%20%2F%3EREASON%3A%20Q.850%3Bcause%3D111%3Btext%3D%22a5d458f9-14c0-4cc4-8c10-202277af11e9%3BUnable%20to%20parse%20RURI.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3ETo%3A%26nbsp%3Bsip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Aorgid%3A7709b36f-1f10-4b1c-8a0f-9c0e5390c86c%3C%2FP%3E%3CP%3ECall-ID%3A%201fa2f0d0-ba41-4e4d-83be-fbef9d0739c6%3C%2FP%3E%3CP%3ECSeq%3A%2010432%20INVITE%3C%2FP%3E%3CP%3EAllow%3A%20OPTIONS%2C%20REGISTER%2C%20SUBSCRIBE%2C%20NOTIFY%2C%20PUBLISH%2C%20INVITE%2C%20ACK%2C%20BYE%2C%20CANCEL%2C%20UPDATE%2C%20PRACK%2C%20REFER%3C%2FP%3E%3CP%3ESupported%3A%20100rel%2C%20timer%2C%20replaces%2C%20norefersub%3C%2FP%3E%3CP%3ESession-Expires%3A%201800%3C%2FP%3E%3CP%3EMin-SE%3A%2090%3C%2FP%3E%3CP%3EMax-Forwards%3A%2069%3C%2FP%3E%3CP%3EContent-Type%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Length%3A%20346%3C%2FP%3E%3CP%3EContact%3A%20sip%3Agateway%40sbc.xxx.xxx.com%3A5061%3Btransport%3DTLS%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785284%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785284%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380677%22%20target%3D%22_blank%22%3E%40Matej_Maric%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20my%20INVITE%20packet%2C%20I%20had%20to%20remove%20triangle%20brackets%20to%20make%20post%20clear%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EINVITE%20sip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Aorgid%3A7709b36f-1f10-4b1c-8a0f-9c0e5390c86c%20SIP%2F2.0%3C%2FP%3E%3CP%3EVia%3A%20SIP%2F2.0%2FTLS%20X.X.X.X%3A5061%3Bbranch%3Dz9hG4bKf26f.503bdc4.0%3Bi%3D54849946%3C%2FP%3E%3CP%3EFrom%3A%20%22XXXXXXX%22%3Btag%3Da1d8a1ca-d330-4251-811d-35fa1a797c64%26amp%3B%3B%3C%2FP%3E%3CP%3ETo%3A%26nbsp%3Bsip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Aorgid%3A7709b36f-1f10-4b1c-8a0f-9c0e5390c86c%3C%2FP%3E%3CP%3ECall-ID%3A%201fa2f0d0-ba41-4e4d-83be-fbef9d0739c6%3C%2FP%3E%3CP%3ECSeq%3A%2010432%20INVITE%3C%2FP%3E%3CP%3EAllow%3A%20OPTIONS%2C%20REGISTER%2C%20SUBSCRIBE%2C%20NOTIFY%2C%20PUBLISH%2C%20INVITE%2C%20ACK%2C%20BYE%2C%20CANCEL%2C%20UPDATE%2C%20PRACK%2C%20REFER%3C%2FP%3E%3CP%3ESupported%3A%20100rel%2C%20timer%2C%20replaces%2C%20norefersub%3C%2FP%3E%3CP%3ESession-Expires%3A%201800%3C%2FP%3E%3CP%3EMin-SE%3A%2090%3C%2FP%3E%3CP%3EMax-Forwards%3A%2069%3C%2FP%3E%3CP%3EContent-Type%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Length%3A%20346%3C%2FP%3E%3CP%3EContact%3A%20sip%3Agateway%40sbc.xxx.xxx.com%3A5061%3Btransport%3DTLS%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785329%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785329%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380677%22%20target%3D%22_blank%22%3E%40Matej_Maric%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20right%2C%20just%20to%20clarify%2C%20I've%20got%20this%20sorta%20working%2C%20I%20was%20removing%20REFERRED-BY%20header%20when%20placing%20a%20new%20INVITE%20and%20that's%20why%20it%20couldn't%20connect%20the%20call%2C%20after%20leaving%20that%20header%20intact%20the%20call%20can%20be%20transferred.%20But%20this%20far%20for%20us%20it's%20much%20easier%20just%20to%20remove%20REFER%20method%20from%20the%20list%20of%20allowed%20methods%2C%20otherwise%20it's%20quite%20a%20complex%20setup%20with%20our%20SBC.%20Thanks%20everyone%20for%20replies%2C%20now%20we%20have%20two%20working%20methods%20that%20allow%20call%20to%20be%20transferred%20to%20internal%20MS%20Teams%20users!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785524%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785524%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eyep%2C%20tend%20to%20be%20with%20you%20on%20conclusions.%20being%20forced%20to%20implement%20both%20in%20real%20life%20felt%20like%20sharing%20things%20people%20find%20useful%20%3A)Most%20important%20is%20we%20understand%20now%20how%20to%20implement%20both%20methods%20and%20logic%20MS%20uses%20to%20trigger%20each.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Echeers!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anybody%20have%20an%20idea%2C%20why%203pip%20Phones%20or%20SfB%20Client%20for%20that%20matter%20(i%20know%20it's%20not%20supported%20but%20if%203pip%20should%20work%2C%20the%20SfB%20Client%20should%20also%20work)%20does%20not%20send%20a%20Refer%20to%20number%20to%20our%20SBC%3F%20Or%20is%20there%20anyone%20around%20who%20can%20test%20it%20and%20tell%20me%20if%20it's%20working%20with%20their%20SBC%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3Emozzie%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785753%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785753%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20for%20us%20it's%20the%20other%20way%20around.%20Internal%20calls%20transfer%20perfectly%20fine%20and%20transfer%20to%20PSTN%20only%20works%20via%20the%20Teams%20Client.%20We%20do%20use%20some%203PIP%20Phones%20from%20AudioCodes%2C%20Yealink%20and%20Poly%20and%20if%20we%20try%20to%20transfer%20a%20call%20to%20an%20external%20Number%2C%20our%20SBC%20does%20not%20receive%20a%20refer-to%20number%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20i%20have%20heard%20from%20someone%2C%20that%20their%20AudioCodes%20SBC%20receives%20this%20from%20Number%20even%20when%20it's%20coming%20from%20a%203PIP%20Phone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHad%20to%20put%20%26lt%3B%20and%20%26gt%3B%20into%20%22%26lt%3B%22%20in%20order%20to%20paste%20it%20here...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26lt%3B443%26gt%3B%26lt%3B%26gt%3B%26lt%3B5061%26gt%3B%26lt%3B5061%26gt%3B%26lt%3B%26gt%3B%26lt%3B443%26gt%3B%26lt%3B%26gt%3B%26lt%3B5061%26gt%3B%26lt%3B5061%26gt%3B%26lt%3B%26gt%3BREFER%20sip%3Asbc.*hiddendomain*.ch%3A5999%3Btransport%3Dtls%3Bmaddr%3D172.16.1.12%20SIP%2F2.0%3CBR%20%2F%3EAllow%3A%20INVITE%3CBR%20%2F%3EAllow%3A%20ACK%3CBR%20%2F%3EAllow%3A%20OPTIONS%3CBR%20%2F%3EAllow%3A%20CANCEL%3CBR%20%2F%3EAllow%3A%20BYE%3CBR%20%2F%3EAllow%3A%20NOTIFY%3CBR%20%2F%3ECall-Id%3A%20dfeb9b46-4de2-4cbd-a6ec-fee2d527c833%3CBR%20%2F%3EContact%3A%20%22%26lt%3B%22sip%3Aapi-du-b-euwe.pstnhub.microsoft.com%3A443%3Btransport%3Dtls%3Bx-i%3D07055b65-a904-4768-9aa8-cc862e28b518%3Bx-c%3D%2Fv1%2Fngc%2Fcall%2Fd620b0a22008514389800e30823e21d7%2Fs%2F1%2F0be3272839bd4aa0944084e9a0ad45a4%22%26gt%3B%22%3CBR%20%2F%3EContent-Length%3A%200%3CBR%20%2F%3ECseq%3A%203%20REFER%3CBR%20%2F%3EFrom%3A%20%22%26lt%3B%22sip%3A%2B41445203631%40sip.pstnhub.microsoft.com%22%26gt%3B%22%3Btag%3D4b85270aa7b246e388c532f96fb6662c%3CBR%20%2F%3EMax-Forwards%3A%2070%3CBR%20%2F%3ERefer-To%3A%20%22%26lt%3B%22sip%3Asip.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Bx-m%3D8%3Asfb%3A9de069dc-faac-54d5-26e4-2615f37bda97%22%26gt%3B%22%3CBR%20%2F%3EReferred-By%3A%20%22%26lt%3B%22sip%3Asip.pstnhub.microsoft.com%3A5061%3Bx-m%3D8%3Aorgid%3A76606d0b-4d28-4246-9c08-2a0f95f96141%3Bx-t%3D4bffbf87-53a0-4fce-b58b-4179cb3a3b7d%3Bx-ti%3D07055b65-a904-4768-9aa8-cc862e28b518%3Bx-tt%3DaHR0cHM6Ly9hcGktZHUtYi1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9ODVjMTRiYzNhNTZjNGRhZjkxY2Y2MDg1NDdlYzY5YzA%253D%22%26gt%3B%22%3CBR%20%2F%3ETo%3A%20%22%26lt%3B%22sip%3A%2B41788578660%40sbc.mozzism.ch%3A5999%3Btransport%3Dtls%3Bmaddr%3D172.16.1.12%22%26gt%3B%22%3Btag%3D884f0b5e-37b4-4d90-924f-b9e73f645362%3CBR%20%2F%3EUser-Agent%3A%20Microsoft.PSTNHub.SIPProxy%20v.2019.7.4.9%20i.EUWE.1%3CBR%20%2F%3EVia%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Breceived%3D52.114.75.24%3Bbranch%3Dz9hG4bK8164e79b%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anybody%20have%20an%20idea%2C%20why%203pip%20Phones%20or%20SfB%20Client%20for%20that%20matter%20(i%20know%20it's%20not%20supported%20but%20if%203pip%20should%20work%2C%20the%20SfB%20Client%20should%20also%20work)%20does%20not%20send%20a%20Refer%20to%20number%20to%20our%20SBC%3F%20Or%20is%20there%20anyone%20around%20who%20can%20test%20it%20and%20tell%20me%20if%20it's%20working%20with%20their%20SBC%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3Emozzie%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-786749%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-786749%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386416%22%20target%3D%22_blank%22%3E%40mozziemozz%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20you%20typing%20in%20full%20E.164%20external%20number%3F%20I%20have%20an%20issue%20with%20SFB%20where%20it's%20not%20sending%20calls%20to%20SBC%20unless%20I%20type%20in%20full%20'%2B44XXXXX'%20number%20even%20though%20Teams%20works%20fine%20with%20local%20numbers%20starting%20with%20'0'%20or%20any%20other%20number%20because%20we%20have%20'.*'%20VoiceRoute%20configured.%20Can't%20figure%20out%20why%20it's%20doing%20so%2C%20cooperation%20mode%20is%20set%20to%20Islands%20and%20SFB%20can%20send%20and%20receive%20calls%20but%20only%20when%20using%20full%20E.164%20numbers.%20Some%20MS%20built-in%20normalization%20rules%20for%20the%20country%20are%20kicking%20in%20by%20the%20looks%20of%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-786756%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-786756%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386416%22%20target%3D%22_blank%22%3E%40mozziemozz%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20maybe%20your%20SBC%20has%20a%20rule%20to%20remove%20Refer-To%20header%20and%20sometimes%20that%20rule%20is%20applied%20by%20incorrectly%20configured%20Match%20policy%3F%20Have%20you%20tried%20sniffing%20traffic%20and%20decoding%20TLS%20to%20see%20the%20actual%20SIP%20packet%20coming%20from%20MS%20before%20it's%20handled%20by%20SBC%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-786770%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-786770%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3Bfor%20me%20it%20doesn't%20make%20a%20difference%20if%20the%20number%20starts%20with%20%2B4144%20or%20044.%20from%20the%20looks%20of%20it%2C%20the%20normalization%2Ftranslation%20of%20the%20number%20works%20fine%20with%20the%20SfB%20Client%20too.%20Also%20works%20when%20just%20dialing%20044%20(national%20format)%20instead%20of%20transferring.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20work%20for%20you%20when%20you%20enter%20full%20E.164%20with%20the%20SfB%20Client%20or%203PIP%20Phone%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-786783%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-786783%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3BI%20don't%20think%20that%20the%20SBC%20removes%20the%20refer%2C%20because%20when%20I%20do%20it%20via%20the%20Teams%20Client%2C%20everything%20works%20fine.%20If%20I%20disable%20Referred-By%20on%20the%20SBC%20transfers%20stop%20working%2C%20even%20internal%20Teams%20Transfers.%20I'm%20not%20sure%20who%20to%20do%20TLS%20sniffing%20and%20decoding.%20What%20do%20I%20need%20to%20do%3F%20Run%20wireshark%20while%20i%20transfer%20and%20filter%20for%20TLS%2FTCP%20packets%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-786784%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-786784%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386416%22%20target%3D%22_blank%22%3E%40mozziemozz%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20not%20that%20easy%2C%20you%20will%20need%20your%20SSL%20certificate%20and%20private%20key%20in%20order%20to%20decrypt%20the%20traffic%2C%20you%20need%20to%20google%20about%20that.%20But%20maybe%20you%20just%20disable%20REFER%20support%20like%20we%20did%3F%20That's%20much%20simpler%20and%20works%20much%20better%20and%20requires%20less%20rules%20on%20SBC%20to%20make%20calls%20work.%20Just%20strip%20'REFER'%20from%20any%20'Allow%3A'%20header%20coming%20from%20SBC%20on%20requests%20and%20responses.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-812905%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-812905%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20turned%20out%2C%20that%20there%20was%20in%20fact%20something%20wrong%20with%20how%20Microsoft%20%2F%203PIP%20SfB%20Phones%20sent%20the%20refer%20to%20our%20SBC.%20(Our%20SBC%20did%20not%20receive%20a%20refer-to%20number)%20Microsoft%20has%20now%20fixed%20the%20issue%20and%20we%20can%20correctly%20transfer%20calls%20to%20external%20numbers%20via%20the%20Teams%20Desktop%20Client%20and%203PIP%20Modes%20with%20users%20in%20TeamsOnly%20mode.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-816342%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-816342%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386416%22%20target%3D%22_blank%22%3E%40mozziemozz%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20mate%2C%3C%2FP%3E%3CP%3EGood%20to%20know%20it's%20all%20fixed!%20Yes%2C%20the%20biggest%20problem%20when%20dealing%20with%20Microsoft%20is%20that%20you%20never%20know%20if%20that's%20an%20issue%20with%20your%20phone%20or%20software%20or%20with%20their%20end.%20I%20was%20speaking%20to%20their%20official%20support%20as%20we%20are%20an%20official%20partner%20and%20all%20I%20got%20in%20the%20end%20was%20'Please%20post%20into%20our%20techcommunity'.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-847075%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-847075%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20post%20how%20to%20do%20message%20manipulation%20to%20re-build%20the%20allow%20header%20for%20this%20on%20AudioCodes%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-848127%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-848127%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30375%22%20target%3D%22_blank%22%3E%40Jason%20Turpin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESure%20-%20here%20it%20is%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAction%20Subject%20-%26nbsp%3BHeader.Allow%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAction%20Type%20-%20Modify%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAction%20Value%20-%26nbsp%3B'PUBLISH%2CMESSAGE%2CUPDATE%2CPRACK%2CSUBSCRIBE%2CINFO%2CNOTIFY%2CREGISTER%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL'%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EYou%20can%20strip%20out%20any%20method%20you%20like%20or%20match%20what%20Microsoft%20send%20in%20their%20messages%20if%20you'd%20like.%20Its%20working%20fine%20for%20me%20with%20these.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESim%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-848140%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-848140%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYep%2C%20works%20pretty%20much%20same%20way%20for%20me%2C%20even%20though%20right%20now%20I'm%20not%20using%20AudioCodes%20any%20more.%20And%20I'm%20analyzing%20each%20Allow%20string%20to%20strip%20only%20REFER%20from%20it%20instead%20of%20replacing%20Allow%20with%20generic%20one%20that%20allows%20everything.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-851396%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-851396%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20from%20curiosity%2C%20do%20you%20use%20mediabypass%20already%3F%3C%2FP%3E%3CP%3EI%20have%20encountered%20interesting%20issue%20which%20is%20causing%20on%20PSTN%20calls%20to%20Teams%20user%20over%20SBC%20and%20transferred%20to%20my%20internal%20PBX%20extension%20or%20external%20number%20simply%20No%20Audio.%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20the%20call%20flow%20-%20PSTN%20-%20myPBX%20-%20SBC%20-%20Teams%20user%20REFER-%20SBC%20-%20myPBX%20-%20phone%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnce%20I%20manipulated%20my%20SBC%20that%20Microsoft%20takes%20care%20about%20sending%20re-Invite%20instead%20of%20REFER%20it%20sends%20new%20Invite%20as%20you%20observe%20BUT%20obviously%20as%20media%20source%20it%20uses%20the%20public%20IP%20of%20my%20SBC%20in%20the%20initial%20offer%20(it%20simply%20takes%20the%20info%20from%20original%20session%20leg).%3C%2FP%3E%3CP%3EMy%20SBC%20is%20behind%20NAT.%20Properly%20configured.%26nbsp%3B%20And%20it%20does%20not%20recognize%20that%20this%20new%20Invite%20is%20dedicated%20to%20media%20channel%20reserved%20already%20on%20the%20SBC%20%3A)%3C%2Fimg%3E%26nbsp%3B%20so%20it%20attempts%20to%20establish%20new%20channel%20between%20private%20IP%20and%20public%20IP%20of%20its%20own%20interface%20-sending%20the%20media%20out%20to%20its%20own%20public%20IP%20-%20which%20is%20then%20visible%20on%20our%20firewall%20as%20traffic%20that%20is%20dropped.%20Even%20if%20I%20allow%20this%20traffic%20between%20private%20IP%20to%20public%20IP%20of%20the%20same%20interface%20it%20would%20cause%20flow%20which%20does%20not%20make%20sense%20at%20all.%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20mediabypass%20is%20not%20used%20then%20it%20is%20fine%2C%20also%20for%20Teams%20caller%20transferred%20to%20myPBX.%20Just%20in%20case%20it%20is%20PSTN%20caller%20transfered%20back%20to%20SBC.%20(same%20problem%20occures%20also%20once%20the%20Teams%20user%20set%20Forwarding%20to%20his%20mobile%20for%20example...call%20connected%20but%20no%20audio)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-851551%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-851551%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263389%22%20target%3D%22_blank%22%3E%40DaveChomi%3C%2FA%3E%26nbsp%3B-%20Not%20I'm%20not%20using%20media%20bypass.%20If%20I%20have%20to%20be%20honest%2C%20I%20fail%20to%20see%20the%20benefits%20of%20media%20bypass.%20High%20bandwidth%20data%20line%20prices%20have%20dramatically%20decreased%20over%20the%20last%20couple%20of%20years%2C%20so%20by%20using%20media%20bypass%20you%20just%20save%20Microsoft%20a%20tone%20of%20bandwidth%20and%20infrastructure%20within%20their%20DCs%2C%20which%20I'm%20more%20than%20sure%20they%20have%20the%20money%20to%20pay%20for%20and%20maintain%20anyway.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMedia%20bypass%20would%20probably%20work%20in%20your%20model%20for%20a%20simple%20Teams%20-%26gt%3B%20SBC%20-%26gt%3B%20PSTN%20or%20other%20way%20around%20model%2C%20when%20you%20start%20hair-pinning%20both%20legs%20of%20the%20call%20(existing%20and%20transfer)%20through%20existing%20infrastructure%20like%20your%20SBC%20and%20PBX%20you're%20just%20asking%20for%20trouble.%20I'd%20just%20disable%20media%20bypass%20if%20I%20were%20you%2C%20unless%20you're%20really%20struggling%20for%20bandwidth.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ESim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-853422%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-853422%22%20slang%3D%22en-US%22%3EI%20got%20your%20point.%20%3A)%3C%2Fimg%3E%20It's%20just%20about%20reasonable%20routing%20of%20calls%20also%20to%20internal%20infrastructure%20and%20trying%20to%20keep%20media%20path%20short%20from%20central%20sip%20services%20towards%20clients.%20So%20far%20it%20really%20brings%20headaches%20to%20me%20but%20also%20it%20brought%20better%20quality%20of%20calls%20so%20I%20have%20seen%20benefit%20in%20get%20over%20the%20pain%20to%20make%20proper%20setup.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-857266%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-857266%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263389%22%20target%3D%22_blank%22%3E%40DaveChomi%3C%2FA%3E%26nbsp%3BThat's%20very%20interesting%20I%20guess%20it%20really%20depends%20on%20what%20your%20deployment%20looks%20like.%26nbsp%3B%20We%20do%20more%20of%20a%20multi-tenanted%20carrier%20deployment%20in%20which%20RTP%20would%20never%20leave%20the%20customer%20LAN%20for%20internal%20calls%20and%20for%20external%20calls%20it%20would%20always%20go%20from%20the%20Customer%20LAN%20%26lt%3B-%26gt%3B%20MS%20%26lt%3B-%26gt%3B%20us.%20If%20you've%20deployed%20an%20enterprise%20model%2C%20where%20your%20SBC%20is%20deployed%20within%20your%20LAN%20there%20really%20is%20no%20point%20in%20flinging%20media%20packets%20all%20the%20way%20to%20MS%20just%20to%20receive%20them%20back%20to%20your%20LAN%20and%20then%20send%20them%20out%20again%20via%20your%20SBC.%20I%20can%20see%20how%20that%20can%20have%20an%20impact%20on%20quality.%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20share%20the%20syslog%20for%20a%20call%20like%20that%20from%20the%20AudioCodes%20SBC%3F%20I'd%20be%20very%20interested%20to%20see%20what%20its%20doing%20hone%20its%20trying%20to%20negotiate%20the%20call%20transfer%20leg.%3CBR%20%2F%3E%3CBR%20%2F%3ERegards%2C%3C%2FP%3E%3CP%3ESim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-866943%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-866943%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20provide%20later%20the%20syslog%2C%20just%20do%20not%20want%20to%20publish%20all%20our%20IP%20addresses%20etc.%20on%20forum%3C%2FP%3E%3CP%3ECurrently%20if%20I%20set%20our%20SBC%20to%20handle%20all%20REFERs%20locally%20it%20simply%20takes%20REFER%20from%20Teams%2C%20SBC%20accept%20and%20sends%20new%20Invite%20to%20Teams.%20Teams%20takes%20that%20and%20create%20new%20SIP%20call%20where%20as%20source%20IP%20for%20media%20presents%20public%20IP%20of%20our%20SBC.%20This%20call%20will%20come%20as%20new%20SIP%20call%20to%20our%20SBC%20and%20SBC%20simply%20tries%20to%20connect%20media%20between%20private%20IP%20and%20public%20IP%20of%20our%20WAN%20interface.%20And%20this%20is%20failing%20basically%20because%20SBC%20sends%20the%20traffic%20to%20its%20own%20public%20IP%20through%20WAN%20interface%20out%20of%20the%20SBC.%20There%20is%20then%20firewall%20which%20is%20dropping%20that%20from%20obvious%20reason.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-866948%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-866948%22%20slang%3D%22en-US%22%3E%3CP%3EScreenshots%20are%20basically%20refering%20to%20call%20from%20%2B420702XXXXXX%20to%20Teams%20user%20on%20number%20%2B420544137XXX%20which%20was%20transffered%20to%20%2B420723XXXXXX.%3C%2FP%3E%3CP%3ENew%20call%20is%20visible%20on%20SBC.%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20on%20that%20second%20call%20the%20SBC%20refers%20to%20Teams%20hey%20the%20media%20are%20on%20my%20public%20IP%20and%20Teams%20refers%20hey%20and%20I%20have%20media%20on%20your%20public%20IP.%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-921219%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-921219%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%26nbsp%3B%20We%20are%20having%20a%20similar%20transfer%20issue%20and%20I%20see%20you%20have%20the%20Audiocodes%20syntax%20to%20remove%20this%20in%20the%20ALLOW%20header.%26nbsp%3B%20Any%20chance%20you%20could%20send%20this%20across%20so%20I%20can%20try%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E'No%2C%20not%20by%20rejecting%20the%20REFER%20with%20a%20response%20code.%20I%20basically%20did%20a%20message%20manipulation%20rule%20to%20re-build%20the%20Allow%20header%20for%20calls%20to%20MS%20Teams%20without%20including%20REFER.%20Which%20vendor%20are%20you%20using%3F%20If%20you%20have%20an%20AudioCodes%20as%20well%2C%20I%20can%20give%20you%20the%20rule%20syntax.'%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECheers%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EDarren%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-961653%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-961653%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F166350%22%20target%3D%22_blank%22%3E%40Darren%20Ellis%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20setup%20on%20the%20opposite%20trunk%20(IP%20Profile%20for%20provider%20SIP%20trunk%20or%20your%20internal%20PBX%20not%20Teams%20side)%20Handle%20Locally%20of%20the%20REFER%20messages%3F%3C%2FP%3E%3CP%3EThis%20will%20do%20the%20same%20job%20basically%20and%20you%20do%20not%20need%20this%20special%20manipulation%20which%20I%20personally%20consider%20as%20too%20much%20because%20it%20does%20not%20give%20you%20any%20chance%20then%20manipulate%20REFER%20messages.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20for%20IP%20profile%20of%20the%20SIP%20trunk%20towards%20your%20provider%2Fon-prem%20PBX%3C%2FP%3E%3CP%3EI%20would%20setup%20these%20parameters%20on%20Audiocodes%20SBC%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3ERemote%20REFER%20Mode%3C%2FTD%3E%3CTD%3EHandle%20Locally%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ERemote%20Replaces%20Mode%3C%2FTD%3E%3CTD%3EHandle%20Locally%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EPlay%20RBT%20To%20Transferee%3C%2FTD%3E%3CTD%3EYes%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ERemote%203xx%20Mode%3C%2FTD%3E%3CTD%3EHandle%20Locally%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-961727%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-961727%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376486%22%20target%3D%22_blank%22%3E%40Sims_Krastev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%20in%20meantime%20I%20got%20this%20resolved.%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20basically%20correct%20behavior%20that%20Microsoft%20sends%20public%20IP%20of%20my%20SBC%20as%20source%20of%20media%20on%20new%20call%20leg%20for%20that%20transferred%20call%2C%20while%20mediabypass%20is%20enabled.%20It%20just%20really%20require%20that%20you%20will%20setup%20enterprise%20firewall%20to%20communicate%20from%20NATed%20private%20IP%20to%20its%20own%20public%20IP%20and%20loopback%20this%20communication.%20This%20is%20what%20basically%20SBC%20does%2C%20Sends%20the%20media%20stream%20from%20its%20own%20private%20IP%20to%20its%20own%20public%20IP%20and%20expects%20the%20media%20back%20%3A)%3C%2Fimg%3E%26nbsp%3B%20So%20it%20is%20very%20ugly%20hairpin%20on%20firewall%20even%20not%20documented%20in%20firewall%20prerequisites.%20I%20would%20say%20SBC%20should%20have%20some%20logic%20to%20handle%20this%20by%20itself%20by%20as%20long%20as%20this%20is%20the%20only%20way%20we%20need%20to%20make%20security%20guys%20believe%20this%20is%20absolutely%20normal%20request%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408077%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408077%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%20Your%20reply's%20allowed%20me%20to%20get%20transfers%20to%20teams%20users%20working.%20Thanks%20very%20much!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20currently%20stuck%20with%20on-hold%2C%20we%20send%20the%20refer%20back%20as%20we%20do%20for%20the%20teams%20transfer%2C%20but%20the%20hold%20fails.%26nbsp%3B%20Could%20you%20share%20part%20of%20a%20sip%20trace%20of%20a%20successful%20hold%2C%20or%20share%20an%20invite%20generated%20by%20your%20sbc%20for%20a%20teams%20hold%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380677%22%20target%3D%22_blank%22%3E%40Matej_Maric%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408116%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408116%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263389%22%20target%3D%22_blank%22%3E%40DaveChomi%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20we%20basically%20got%20this%20working%20with%20a%20firmware%20update%20on%20the%20Audiocodes%20direct%20routing%20SBCs%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408736%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408736%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F675467%22%20target%3D%22_blank%22%3E%40davidmcgrath%3C%2FA%3E%26nbsp%3BHi%2C%3C%2FP%3E%3CP%3EI'm%20glad%20that%20transfers%20are%20working%20for%20you!%20Basically%2C%20holds%20are%20working%20same%20way%2C%20you%20need%20to%20strip%20off%20'REFER'%20method%20from%20all%20'Allow'%20headers%20on%20packets%20in%20BOTH%20directions%20-%20from%20MS%20side%20and%20to%20MS%20side%2C%20make%20sure%20you're%20doing%20that!%20Often%20people%20block%20it%20just%20in%20one%20way%20and%20the%20response%20packets%20are%20not%20modified%20and%20thus%20nothing%20works.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20regards%20to%20putting%20call%20on%20hold%20when%20REFER%20is%20prohibited%20-%20MS%20would%20be%20sending%20Re-INVITE%20with%20a%3Dinactive%20field%20and%20on%20resume%20it%20sends%20a%3Dsendrecv%20in%20Re-INVITE%20packet.%20Here's%20an%20example%20of%20such%20packet%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ESIP%20packet%20from%2052.114.7.24%3A3200%2C%20Method%20is%20INVITE%2C%20RU%3A%20sip%3Aasterisk%40xxxxxxxxx%3A7061%3Btransport%3DTLS%2C%20message%20is%3CBR%20%2F%3EINVITE%20sip%3Agateway%40sbc29356.xxxxxxxxx%3A5061%3Btransport%3DTLS%20SIP%2F2.0%3CBR%20%2F%3EFROM%3A%20%26lt%3B%26gt%3B%3Btag%3D9b78f08b34304f01a31dd37a672d0666%3CBR%20%2F%3ETO%3A%20%26lt%3B%26gt%3B%3Btag%3D4d0e1385-8a08-432b-aab9-ab3db28ae9a4%3CBR%20%2F%3ECSEQ%3A%201%20INVITE%3CBR%20%2F%3ECALL-ID%3A%20f9697203-ea28-4fbc-a231-aee1aa966150%3CBR%20%2F%3EMAX-FORWARDS%3A%2069%3CBR%20%2F%3EVIA%3A%20SIP%2F2.0%2FTLS%2052.114.7.24%3A5061%3Bbranch%3Dz9hG4bKb18bed37%3CBR%20%2F%3ECONTACT%3A%20%26lt%3B443%26gt%3B%3CBR%20%2F%3ECONTENT-LENGTH%3A%20689%3CBR%20%2F%3EMIN-SE%3A%2090%3CBR%20%2F%3ESUPPORTED%3A%20timer%3CBR%20%2F%3EUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2020.5.13.3%20i.ASEA.3%3CBR%20%2F%3ECONTENT-TYPE%3A%20application%2Fsdp%3CBR%20%2F%3EALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3CBR%20%2F%3ESESSION-EXPIRES%3A%203600%3Brefresher%3Duac%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3Ev%3D0%3CBR%20%2F%3Eo%3D-%20216948%202%20IN%20IP4%20127.0.0.1%3CBR%20%2F%3Es%3Dsession%3CBR%20%2F%3Ec%3DIN%20IP4%2052.114.23.32%3CBR%20%2F%3Eb%3DCT%3A10000000%3CBR%20%2F%3Et%3D0%200%3CBR%20%2F%3Em%3Daudio%2052762%20RTP%2FSAVP%20104%20117%209%20103%20111%2018%200%208%2097%20101%2013%20118%3CBR%20%2F%3Ec%3DIN%20IP4%2052.114.23.32%3CBR%20%2F%3Ea%3Drtcp%3A52763%3CBR%20%2F%3Ea%3Dlabel%3Amain-audio%3CBR%20%2F%3Ea%3Dmid%3A1%3CBR%20%2F%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3Ac0XKJbLpvv1%2FIjlH73TVf3fH2qA8YIfulNDFhal4%7C2%5E31%3CBR%20%2F%3E%3CFONT%20size%3D%225%22%20color%3D%22%23FF0000%22%3E%3CSTRONG%3Ea%3Dinactive%3C%2FSTRONG%3E%3C%2FFONT%3E%3CBR%20%2F%3Ea%3Drtpmap%3A104%20SILK%2F16000%3CBR%20%2F%3Ea%3Drtpmap%3A117%20G722%2F8000%2F2%3CBR%20%2F%3Ea%3Drtpmap%3A9%20G722%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A103%20SILK%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A111%20SIREN%2F16000%3CBR%20%2F%3Ea%3Dfmtp%3A111%20bitrate%3D16000%3CBR%20%2F%3Ea%3Drtpmap%3A18%20G729%2F8000%3CBR%20%2F%3Ea%3Dfmtp%3A18%20annexb%3Dno%3CBR%20%2F%3Ea%3Drtpmap%3A0%20PCMU%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A97%20RED%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3CBR%20%2F%3Ea%3Dfmtp%3A101%200-16%3CBR%20%2F%3Ea%3Drtpmap%3A13%20CN%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A118%20CN%2F16000%3CBR%20%2F%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20here%20it's%20taking%20call%20off-hold%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ESIP%20packet%20from%2052.114.7.24%3A3200%2C%20Method%20is%20INVITE%2C%20RU%3A%20sip%3Aasterisk%40xxxxxxx%3A7061%3Btransport%3DTLS%2C%20message%20is%3CBR%20%2F%3EINVITE%20sip%3Agateway%40sbc29356.xxxxxxxxxxxx%3A5061%3Btransport%3DTLS%20SIP%2F2.0%3CBR%20%2F%3EFROM%3A%20%26lt%3B%26gt%3B%3Btag%3D9b78f08b34304f01a31dd37a672d0666%3CBR%20%2F%3ETO%3A%20%26lt%3B%26gt%3B%3Btag%3D4d0e1385-8a08-432b-aab9-ab3db28ae9a4%3CBR%20%2F%3ECSEQ%3A%203%20INVITE%3CBR%20%2F%3ECALL-ID%3A%20f9697203-ea28-4fbc-a231-aee1aa966150%3CBR%20%2F%3EMAX-FORWARDS%3A%2069%3CBR%20%2F%3EVIA%3A%20SIP%2F2.0%2FTLS%2052.114.7.24%3A5061%3Bbranch%3Dz9hG4bKa3cf90b1%3CBR%20%2F%3ECONTACT%3A%20%26lt%3B443%26gt%3B%3CBR%20%2F%3ECONTENT-LENGTH%3A%20689%3CBR%20%2F%3EMIN-SE%3A%2090%3CBR%20%2F%3ESUPPORTED%3A%20timer%3CBR%20%2F%3EUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2020.5.13.3%20i.ASEA.3%3CBR%20%2F%3ECONTENT-TYPE%3A%20application%2Fsdp%3CBR%20%2F%3EALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3CBR%20%2F%3ESESSION-EXPIRES%3A%203600%3Brefresher%3Duac%3C%2FP%3E%3CP%3Ev%3D0%3CBR%20%2F%3Eo%3D-%20216948%203%20IN%20IP4%20127.0.0.1%3CBR%20%2F%3Es%3Dsession%3CBR%20%2F%3Ec%3DIN%20IP4%2052.114.23.32%3CBR%20%2F%3Eb%3DCT%3A10000000%3CBR%20%2F%3Et%3D0%200%3CBR%20%2F%3Em%3Daudio%2052762%20RTP%2FSAVP%20104%20117%209%20103%20111%2018%200%208%2097%20101%2013%20118%3CBR%20%2F%3Ec%3DIN%20IP4%2052.114.23.32%3CBR%20%2F%3Ea%3Drtcp%3A52763%3CBR%20%2F%3Ea%3Dlabel%3Amain-audio%3CBR%20%2F%3Ea%3Dmid%3A1%3CBR%20%2F%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3Ac0XKJbLpvv1%2FIjlH73TVf3fH2qA8YIfulNDFhal4%7C2%5E31%3CBR%20%2F%3E%3CFONT%20size%3D%225%22%20color%3D%22%23FF0000%22%3E%3CSTRONG%3Ea%3Dsendrecv%3C%2FSTRONG%3E%3C%2FFONT%3E%3CBR%20%2F%3Ea%3Drtpmap%3A104%20SILK%2F16000%3CBR%20%2F%3Ea%3Drtpmap%3A117%20G722%2F8000%2F2%3CBR%20%2F%3Ea%3Drtpmap%3A9%20G722%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A103%20SILK%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A111%20SIREN%2F16000%3CBR%20%2F%3Ea%3Dfmtp%3A111%20bitrate%3D16000%3CBR%20%2F%3Ea%3Drtpmap%3A18%20G729%2F8000%3CBR%20%2F%3Ea%3Dfmtp%3A18%20annexb%3Dno%3CBR%20%2F%3Ea%3Drtpmap%3A0%20PCMU%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A97%20RED%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3CBR%20%2F%3Ea%3Dfmtp%3A101%200-16%3CBR%20%2F%3Ea%3Drtpmap%3A13%20CN%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A118%20CN%2F16000%3CBR%20%2F%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20I%20recommend%20turning%20off%20SIP%20session%20timers%20on%20PBX%20side%20or%20else%20you%20may%20encounter%20calls%20dropping%20at%2059%20mins%20and%2028%20seconds%20(in%20case%20with%20Asterisk%20PBX)%20as%20Asterisk%20can't%20correctly%20negotiate%20who%20would%20be%20session%20refresher%20in%20many%20cases.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps!%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408887%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408887%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reply.%20After%20reading%20your%20reply's%20above%2C%20we%20enabled%20REFER%20support%20on%20our%20SBC.%20We%20use%20the%20refer-to%20tag%20to%20work%20out%20who%20to%20send%20the%20refer%20back%20to%20as%20you%20suggested.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20have%20REFER%20enabled.%20If%20teams%20calls%20PSTN%2C%20then%20teams%20clicks%20hold%2C%20wee%20get%20a%20re-invite%20and%20then%20a%20refer.%20we%20respond%20to%20the%20refer%20is%20the%20same%20way%20we%20would%20do%20for%20a%20transfer%20to%20another%20teams%20user%20(that%20works)%20but%20when%20we%20do%20the%20teams%20client%20is%20unable%20to%20take%20the%20call%20off%20hold.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wondered%20if%20you%20had%20an%20example%20of%20on%20hold%20with%20REFER%20support%20works%20with%20teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20useful%20documentation%20about%20how%20to%20handle%20transfers%20to%20teams%20uses%20with%20REFER%20support%20but%20nothing%20about%20on-hold.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1409238%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1409238%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F675467%22%20target%3D%22_blank%22%3E%40davidmcgrath%3C%2FA%3E%26nbsp%3BWell%2C%20in%20first%20place%2C%20why%20is%20it%20sending%20REFER%20if%20you're%20putting%20call%20on%20hold%3F%20It%20should%20just%20send%20a%20SIP%20re-INVITE%20with%20SDP%20a%3Dinactive.%20SIP%20REFER%20is%20used%20for%20blind%20and%2For%20attended%20transfers%20as%20per%20RFC5589.%20If%20you're%20getting%20an%20INVITE%20and%20then%20REFER%20-%20probably%20INVITE%20has%20SDP%20with%20a%3Dinactive%20thus%20putting%20call%20on%20hold%2C%20but%20REFER%20is%20definitely%20for%20transferring%20calls%20somewhere%20else%2C%20can%20you%20post%20a%20tcpdump%20of%20these%20two%20packets%20you're%20seeing%3F%20And%20what%20happens%20after%20you%20press%20un-hold%20in%20Teams%20client%20-%20do%20you%20get%20any%20packets%20coming%20from%20MS%20side%20to%20your%20SBC%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1409292%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1409292%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20share%20a%20fill%20PCAP%20for%20a%20call%2C%20but%20don't%20want%20to%20share%20it%20publicly.%20Is%20there%20a%20way%20I%20can%20share%20it%20directly%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E.%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20attached%20a%20screen%20shot%20of%20the%20sip%20flows%20from%20wire-shark.%20I%20have%20also%20added%20the%20refer%20and%20invite%20packets%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20don't%20understand%20why%20MS%20Sends%20a%20REFER%20after%20the%20re-invite.%20If%20you%20look%20at%20the%20attached%20png%20%2CI%20click%20the%20hold%20button%20in%20teams%20at%2012.205%20secs%2C%20we%20respond%20to%20the%20re-invite%2C%20then%20MS%20sends%20us%20a%20REFER%2C%20which%20we%20respond%20to%20in%20the%20same%20way%20as%20we%20respond%20to%20a%20teams%20transfer%20request%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20attempts%20to%20un-hold%20the%20call%20do%20not%20work%20after%20this.%20The%20call%20drops%20and%20a%20popup%20appears%20in%20the%20top%20left%20corner%20of%20teams%20client%20showing%20the%20call%20is%20on%20hold.%20MOH%20plays%20on%20the%20pstn%20leg.%20No%20more%20packets%20are%20sent%20from%20MS%20to%20my%20SBC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1419739%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1419739%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F675467%22%20target%3D%22_blank%22%3E%40davidmcgrath%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3EPutting%20call%20on%20hold%20you%20are%20transferring%20the%20call%20to%20music%20on%20hold%20entity%20which%20is%20playing%20the%20MoH%20for%20PSTN%20calling%20party.%20That%20is%20the%20reason%20why%20you%20see%20REFER%20afrer%20putting%20call%20on%20hold.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1419822%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1419822%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263389%22%20target%3D%22_blank%22%3E%40DaveChomi%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reply%2C%20that%20makes%20a%20lot%20of%20sense%20now!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20it%20be%20possible%20to%20share%20an%20example%20of%20the%20invite%20that%20you%20generate%20from%20the%20on%20hold%20REFER.%20We%20handle%20this%20refer%20in%20the%20same%20way%20that%20we%20handle%20the%20refer%20that%20is%20generated%20when%20you%20transfer%20a%20call%20to%20a%20teams%20user.%26nbsp%3B%20We%20are%20clearly%20being%20transferred%20to%20the%20MOH%20server%2C%20but%20the%20call%20in%20the%20teams%20client%20hangs%20up%20when%20the%20call%20goes%20on%20hold%20and%20then%20its%20not%20possible%20to%20retentive%20the%20call.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1736127%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1736127%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20have%20the%20same%20issue%2C%20could%20you%20please%20send%20me%20the%20manipulation%20you%20did%20to%20the%20response%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1742496%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1742496%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F67765%22%20target%3D%22_blank%22%3E%40Mohamed%20Hussein%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20need%20to%20modify%20'Allow'%20header%20in%20original%20message%20coming%20from%20MS%20Teams%20to%20your%20PBX%2C%20removing%20'REFER'%20method%20and%20then%20in%20any%20responses%20from%20PBX%20you%20also%20need%20to%20remove%20'REFER'%20method.%20In%20this%20case%20MS%20Teams%20will%20be%20sending%20Re-INVITE%20packet%20instead%20of%20REFER%20packets.%20Hope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1742497%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1742497%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F675467%22%20target%3D%22_blank%22%3E%40davidmcgrath%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%2C%20somehow%20I%20have%20missed%20your%20reply%20and%20didn't%20receive%20a%20notification%20about%20your%20answer.%20You%20need%20to%20block%20'REFER'%20method%20in%20both%20initial%20requests%20coming%20from%20PBX%20or%20MS%20side%20and%20in%20replies%20too%2C%20in%20that%20case%20MS%20will%20be%20sending%20just%20Re-INVITES%20as%20per%20my%20SIP%20dump%20above.%20But%20currently%2C%20in%20October%202020%2C%20it%20looks%20like%20they've%20fixed%20REFERs%2C%20we're%20actually%20testing%20if%20they're%20working%20fine%20now%2C%20but%20haven't%20come%20to%20conclusion%20yet.%20Looks%20like%20REFERs%20are%20working%2C%20but%20we%20haven't%20finished%20full%20testing%20procedure%20in%20our%20company.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1860842%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1860842%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263389%22%20target%3D%22_blank%22%3E%40DaveChomi%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20having%20similar%20issues%20with%20AudioCodes%20direct%20routing%20to%20Teams.%3C%2FP%3E%3CP%3EAll%20unhold%20(resume)%20action%20from%20Teams%20creates%20a%20net%20new%20call%20leg%20in%20Teams%20(new%20call%20ID%2C%20cseq%3A1).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%20other%20hand%2C%20the%20transfer%20and%20the%20cons%20transfer%20works%20nicely.%20We%20did%20not%20have%20to%20mess%20with%20REFERs%20(as%20we%20have%20no%20refer%20in%20the%20allowed%20list%20at%20all%2C%20in%20any%20part%20of%20the%20messaging).%3C%2FP%3E%3CP%3EIs%20it%20a%20known%20issue%2C%20you%20think%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22G_____0-1604670252364.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231884iC92383E91D8389C8%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22G_____0-1604670252364.png%22%20alt%3D%22G_____0-1604670252364.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22G_____1-1604670269622.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231886iF2128F375636494C%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22G_____1-1604670269622.png%22%20alt%3D%22G_____1-1604670269622.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22G_____2-1604670409466.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231887i6AF7D81135931C7B%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22G_____2-1604670409466.png%22%20alt%3D%22G_____2-1604670409466.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20the%20same%20story%20working%20nicely%20with%20Skype%20(all%20the%20rest%20is%20the%20same%2C%20the%20only%20difference%20is%20Teams%20instead%20of%20Skype%20on%20prem%20endpoint).%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22G_____3-1604670631073.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231888i6FBBA4EBE2EF1486%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22G_____3-1604670631073.png%22%20alt%3D%22G_____3-1604670631073.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3ECONTENT-LENGTH%3A%20960%3C%2FP%3E%3CP%3EMIN-SE%3A%2090%3C%2FP%3E%3CP%3ESUPPORTED%3A%20timer%3C%2FP%3E%3CP%3EUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2020.10.12.5%20i.EUWE.0%3C%2FP%3E%3CP%3ECONTENT-TYPE%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3ESESSION-EXPIRES%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3D-%20818192%202%20IN%20IP4%20127.0.0.1%3C%2FP%3E%3CP%3Es%3Dsession%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Eb%3DCT%3A10000000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Em%3Daudio%2049374%20RTP%2FSAVP%20104%209%20103%20111%2018%200%208%2097%20101%2013%20118%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Ea%3Drtcp%3A49375%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Aqf6h%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AcAKaay5mszWiR21QAfhitBtA%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%201%20UDP%201862270719%2052.113.9.255%2049374%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049374%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%202%20UDP%201862270462%2052.113.9.255%2049375%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049375%3C%2FP%3E%3CP%3Ea%3Dremote-candidates%3A1%20200.000.000.000%206020%202%20200.000.000.000%206021%3C%2FP%3E%3CP%3Ea%3Dlabel%3Amain-audio%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AL2vBEmXqbgm9EvI%2BCr1o49ICZ4FJafwFnddUrI51%7C2%5E31%3C%2FP%3E%3CP%3Ea%3Dinactive%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A104%20SILK%2F16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A9%20G722%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A103%20SILK%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A111%20SIREN%2F16000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A111%20bitrate%3D16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A18%20G729%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A18%20annexb%3Dno%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A0%20PCMU%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A97%20RED%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-16%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A118%20CN%2F16000%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E200%20OK%20SDP%20back%20to%20device%20after%20setting%20up%20hold%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A31.985%20----%20Outgoing%20SIP%20Message%20to%2052.114.75.24%3A2368%20from%20SIPInterface%20%233%20(Teams)%20TLS%20TO(%231575)%20SocketID(13138)%20----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESIP%2F2.0%20200%20OK%3C%2FP%3E%3CP%3EVia%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Bbranch%3Dz9hG4bK87c1ea93%3C%2FP%3E%3CP%3EFrom%3A%20%22John%20McClane%22%20%26lt%3B%26gt%3B%3Btag%3D5dad766e6f574758b8316e3bc83b4fb7%3C%2FP%3E%3CP%3ETo%3A%20%26lt%3B%26gt%3B%3Btag%3D3813645846-1203322466%3C%2FP%3E%3CP%3ECall-ID%3A%206008f33f815e51cfac31a797b7eace65%3C%2FP%3E%3CP%3ECSeq%3A%204%20INVITE%3C%2FP%3E%3CP%3EContact%3A%20%26lt%3B%26gt%3B%3C%2FP%3E%3CP%3ESupported%3A%20sdp-anat%3C%2FP%3E%3CP%3EAllow%3A%20UPDATE%2CPRACK%2CINFO%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3ERequire%3A%20timer%3C%2FP%3E%3CP%3ESession-Expires%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3EServer%3A%20Mediant%204000B%2Fv.7.20A.260.095%3C%2FP%3E%3CP%3EAccept%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Type%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Length%3A%20588%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3DMSX123%20986564814%2057709579%20IN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Es%3Dsip%20call%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Ea%3Dice-lite%3C%2FP%3E%3CP%3Em%3Daudio%206020%20RTP%2FSAVP%208%2013%20101%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%3CSPAN%3Ea%3Dinactive%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Ab8R5wxoJkXYTLfyh%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AU6Y4nSE6QuMxd2icJpcXW51e%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%201%20udp%202130706431%20200.000.000.000%206020%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%202%20udp%202130706430%20200.000.000.000%206021%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-15%2C16%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AWohABz54vXekdjP0u2BlGfgxthlk0lZByrVzBBDl%7C2%5E31%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20the%20extra%20re-invite%20after%201%20000%20ms%20with%20full%20voice%20in%20it%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A33.016%20----%20Incoming%20SIP%20Message%20from%2052.114.75.24%3A2368%20to%20SIPInterface%20%233%20(Teams)%20TLS%20TO(%231575)%20SocketID(13138)%20----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EINVITE%20sip%3A%2B447777777777%40customer.sbc.hoster.co.uk%3A5061%3Btransport%3Dtls%20SIP%2F2.0%3C%2FP%3E%3CP%3EFROM%3A%20John%20McClane%26lt%3B%26gt%3B%3Btag%3D5dad766e6f574758b8316e3bc83b4fb7%3C%2FP%3E%3CP%3ETO%3A%20%26lt%3B%26gt%3B%3Buser%3Dphone%3Btag%3D3813645846-1203322466%3C%2FP%3E%3CP%3ECSEQ%3A%206%20INVITE%3C%2FP%3E%3CP%3ECALL-ID%3A%206008f33f815e51cfac31a797b7eace65%3C%2FP%3E%3CP%3EMAX-FORWARDS%3A%2070%3C%2FP%3E%3CP%3EVIA%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Bbranch%3Dz9hG4bK4665a2fb%3C%2FP%3E%3CP%3ECONTACT%3A%20%26lt%3B443%26gt%3B%3C%2FP%3E%3CP%3ECONTENT-LENGTH%3A%20960%3C%2FP%3E%3CP%3EMIN-SE%3A%2090%3C%2FP%3E%3CP%3ESUPPORTED%3A%20timer%3C%2FP%3E%3CP%3EUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2020.10.12.5%20i.EUWE.0%3C%2FP%3E%3CP%3ECONTENT-TYPE%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3ESESSION-EXPIRES%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3D-%20818192%203%20IN%20IP4%20127.0.0.1%3C%2FP%3E%3CP%3Es%3Dsession%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Eb%3DCT%3A10000000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Em%3Daudio%2049374%20RTP%2FSAVP%20104%209%20103%20111%2018%200%208%2097%20101%2013%20118%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Ea%3Drtcp%3A49375%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Aqf6h%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AcAKaay5mszWiR21QAfhitBtA%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%201%20UDP%201862270719%2052.113.9.255%2049374%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049374%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%202%20UDP%201862270462%2052.113.9.255%2049375%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049375%3C%2FP%3E%3CP%3Ea%3Dremote-candidates%3A1%20200.000.000.000%206020%202%20200.000.000.000%206021%3C%2FP%3E%3CP%3Ea%3Dlabel%3Amain-audio%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AL2vBEmXqbgm9EvI%2BCr1o49ICZ4FJafwFnddUrI51%7C2%5E31%3C%2FP%3E%3CP%3Ea%3Dsendrecv%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A104%20SILK%2F16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A9%20G722%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A103%20SILK%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A111%20SIREN%2F16000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A111%20bitrate%3D16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A18%20G729%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A18%20annexb%3Dno%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A0%20PCMU%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A97%20RED%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-16%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A118%20CN%2F16000%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2nd%20200%20OK%20SDP%20back%20the%20device%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A33.141%20----%20Outgoing%20SIP%20Message%20to%2052.114.75.24%3A2368%20from%20SIPInterface%20%233%20(Teams)%20TLS%20TO(%231575)%20SocketID(13138)%20----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESIP%2F2.0%20200%20OK%3C%2FP%3E%3CP%3EVia%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Bbranch%3Dz9hG4bK4665a2fb%3C%2FP%3E%3CP%3EFrom%3A%20%22John%20McClane%22%20%26lt%3B%26gt%3B%3Btag%3D5dad766e6f574758b8316e3bc83b4fb7%3C%2FP%3E%3CP%3ETo%3A%20%26lt%3B%26gt%3B%3Btag%3D3813645846-1203322466%3C%2FP%3E%3CP%3ECall-ID%3A%206008f33f815e51cfac31a797b7eace65%3C%2FP%3E%3CP%3ECSeq%3A%206%20INVITE%3C%2FP%3E%3CP%3EContact%3A%20%26lt%3B%26gt%3B%3C%2FP%3E%3CP%3ESupported%3A%20sdp-anat%3C%2FP%3E%3CP%3EAllow%3A%20UPDATE%2CPRACK%2CINFO%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3ERequire%3A%20timer%3C%2FP%3E%3CP%3ESession-Expires%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3EServer%3A%20Mediant%204000B%2Fv.7.20A.260.095%3C%2FP%3E%3CP%3EAccept%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Type%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Length%3A%20611%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3DMSX123%20986564814%2057709580%20IN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Es%3Dsip%20call%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Ea%3Dice-lite%3C%2FP%3E%3CP%3Em%3Daudio%206020%20RTP%2FSAVP%208%20101%2013%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-15%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Dsendrecv%3C%2FP%3E%3CP%3Ea%3DsilenceSupp%3Aon%20-%20-%20-%20-%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Ab8R5wxoJkXYTLfyh%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AU6Y4nSE6QuMxd2icJpcXW51e%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%201%20udp%202130706431%20200.000.000.000%206020%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%202%20udp%202130706430%20200.000.000.000%206021%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AWohABz54vXekdjP0u2BlGfgxthlk0lZByrVzBBDl%7C2%5E31%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1864303%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1864303%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F360557%22%20target%3D%22_blank%22%3E%40G____%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20more%20details%20on%20it%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%3CP%3ETesting%20the%20Teams%20Direct%20Routing%20functionality%20I%20have%20came%20across%20an%20issue%20in%20the%20Hold%20sequence.%20In%20nutshell%20MS%20does%20not%20unhold%20the%20call%20but%20it%20creates%20a%20new%20session%20(new%20call)%20to%20the%20same%20endpoint.%3C%2FP%3E%3CP%3ECould%20anyone%20help%20me%20with%20a%20SIP%20log%20of%20a%20working%20call%20-%26gt%3B%20accept%20-%26gt%3B%20Teams%20hold%20-%26gt%3B%20Teams%20unhold%20sequence%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDetails%3A%3C%2FP%3E%3CP%3EStandard%20MS%20public%20tenant%20with%20the%20regular%20sip.pstnhub.microsoft.com%20public%20endpoints.%20On%20our%20side%20it%20is%20an%20ACodes%20SBC%20with%20multiple%20PSTN%20side%20trunks.%20No%20media%20bypass%20or%20other%20media%20optimization%20is%20in%20place.%20All%20other%20call%20scenarios%20(simple%20call%2C%20blind%20and%20assisted%20transfer%2C%20etc)%20work%20nicely.%26nbsp%3B%20SBC%20setup%20is%20to%20handle%20call%20hold%20locally%20(as%20per%20ACodes%20guidance).%20The%20same%20trunks%20work%20nicely%20for%20SfB%20on%20prem%20(with%20slightly%20different%20setup%20for%20the%20Skype%20side%20IP%20Group)%3C%2FP%3E%3CP%3Ea%3Dinactive%20is%20handled%20by%20our%20SBC%20(remote%20PSTN%20gets%20the%20sendonly%20and%20their%20response%20of%20receive%20only%20is%20converted%20back%20to%20inactive)%2C%20no%20other%20error%20shows%20up.%20Even%20so%20MS%20sends%20out%20a%20second%20re-invite%20on%20the%20top%20of%20the%20OK-d%20and%20acknowledged%20hold%20inactive%20invite.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20high%20level%20flow%20is%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A06%20Initial%20invite%20from%20Teams%20to%20pstn%3C%2FP%3E%3CP%3ETeams%20-%26gt%3B%20SBC%3C%2FP%3E%3CP%3EInvite%20SDP%20ALLOW%3A%20INVITE%2CACK%2C%3CSPAN%3EOPTIONS%3C%2FSPAN%3E%2C%3CSPAN%3ECANCEL%3C%2FSPAN%3E%2C%3CSPAN%3EBYE%3C%2FSPAN%3E%2C%3CSPAN%3ENOTIFY%3C%2FSPAN%3E%2C%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bsupported%3A%20timer%3C%2FP%3E%3CP%3ESBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3EInvite%20SDP%20Allow%3A%20INVITE%2CACK%2C%3CSPAN%3EOPTIONS%3C%2FSPAN%3E%2CCANCEL%2CBYE%2C%3CSPAN%3ENOTIFY%3C%2FSPAN%3E%2C%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bsupported%3A%20timer%2C%20sdp-anat%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%20%26lt%3B-%20pstn%3C%2FP%3E%3CP%3E183%20Session%20Progress%20SDP%20Allow%3A%20UPDATE%2CPRACK%2CINFO%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%20%26lt%3B-%20pstn%3C%2FP%3E%3CP%3E183%20Session%20Progress%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BAllow%3A%20UPDATE%2CPRACK%2CINFO%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%20%26lt%3B-%20pstn%3C%2FP%3E%3CP%3E180%20Ringing%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BAllow%3A%20UPDATE%2CPRACK%2CINFO%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A08%20Call%20acceptance%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%20%26lt%3B-%26nbsp%3B%3CSPAN%3Epstn%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E200%20OK%20SDP%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BAllow%3A%26nbsp%3B%3CSPAN%3EUPDATE%2CPRACK%2CINFO%3C%2FSPAN%3E%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3E%3CSPAN%3ETeams%3C%2FSPAN%3E%26nbsp%3B-%26gt%3B%20SBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3EACK%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3EInvite%20SDP%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%20%26lt%3B-%26nbsp%3B%3CSPAN%3Epstn%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E200%20OK%20SDP%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BAllow%3A%26nbsp%3B%3CSPAN%3EUPDATE%2CPRACK%3C%2FSPAN%3E%2C%3CSPAN%3EINFO%3C%2FSPAN%3E%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3E%3CSPAN%3ETeams%3C%2FSPAN%3E%26nbsp%3B-%26gt%3B%20SBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3EACK%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECall%20runs%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B10%3A04%3A31-33%20Hold%20on%20Teams%20side%3C%2FP%3E%3CP%3E%3CSPAN%3ETeams%3C%2FSPAN%3E%26nbsp%3B-%26gt%3B%20SBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3E%3CSPAN%3EInvite%20SDP%3C%2FSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3ETeams%20-%26gt%3B%20SBC%3C%2FP%3E%3CP%3Ea%3Dlabel%3Amain-audio%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AL2vBEmXqbgm9EvI%2BCr1o49ICZ4FJafwFnddUrI51%7C2%5E31%3C%2FP%3E%3CP%3E%3CSPAN%3Ea%3Dinactive%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ESBC-%20%26gt%3B%20pstn%3C%2FP%3E%3CP%3E%3CSPAN%3Ea%3Dsendonly%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Ea%3Dlabel%3Amain-audio%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%20%26lt%3B-%26nbsp%3B%3CSPAN%3Epstn%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E200%20OK%20SDP%3C%2FSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BAllow%3A%26nbsp%3B%3CSPAN%3EUPDATE%2CPRACK%2CINFO%3C%2FSPAN%3E%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3E%3CSPAN%3ESBC%20%26lt%3B-%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Epstn%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Em%3Daudio%208456%20RTP%2FAVP%208%2013%20101%3C%2FP%3E%3CP%3Ea%3Drecvonly%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%3C%2FP%3E%3CP%3Em%3Daudio%206020%20RTP%2FSAVP%208%2013%20101%3C%2FP%3E%3CP%3E%3CSPAN%3Ea%3Dinactive%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3E%3CSPAN%3ETeams%3C%2FSPAN%3E%26nbsp%3B-%26gt%3B%20SBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3E%3CSPAN%3EACK%3C%2FSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProcesssing%20it%20(after%201%20000%20ms)%20MS%20sends%20out%20a%3C%2FP%3E%3CP%3E%3CSPAN%3E2nd%20re-invite%20!!%20from%20Teams%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ETeams%3C%2FSPAN%3E%26nbsp%3B-%26gt%3B%20SBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3E%3CSPAN%3EINVITE%20SDP%3C%2FSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3Ea%3Dsendrecv%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20%26lt%3B-%20SBC%20%26lt%3B-%26nbsp%3B%3CSPAN%3Epstn%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E200%20OK%20SDP%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BAllow%3A%26nbsp%3B%3CSPAN%3EUPDATE%2CPRACK%2CINFO%3C%2FSPAN%3E%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3Ea%3Dsendrecv%3C%2FP%3E%3CP%3Ea%3DsilenceSupp%3Aon%20-%20-%20-%20-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ETeams%3C%2FSPAN%3E%26nbsp%3B-%26gt%3B%20SBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3E%3CSPAN%3EACK%3C%2FSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3ECall%20plays%20MS%20hold%20music%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A59%20Teams%20Onhold%20%2F%20resume%20MS%20sends%20out%20a%20second%20invite%20creating%20a%20separate%20session%20(new%20call%20practically)%3C%2FP%3E%3CP%3E%3CSPAN%3ETeams%3C%2FSPAN%3E%26nbsp%3B-%26gt%3B%20SBC%20-%26gt%3B%20pstn%3C%2FP%3E%3CP%3EInvite%20SDP%3C%2FP%3E%3CP%3ECSEQ%3A%201%20INVITE%2C%20CALL%20ID%20%26lt%3B%3CNET%20new%3D%22%22%3E%26gt%3B%3C%2FNET%3E%3C%2FP%3E%3CP%3ESo%20new%20call%20leg%20is%20being%20created%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BThe%20above%20setup%20seems%20to%20be%20inline%20with%20the%20MS%20documentation%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ee%3C%2FA%3Even%20so%20MS%20does%20proxy%20is%20confused%20and%20sends%20out%20a%20second%20call.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EINVITE%20SDP%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A31.860%20----%20Incoming%20SIP%20Message%20from%2052.114.75.24%3A2368%20to%20SIPInterface%20%233%20(Teams)%20TLS%20TO(%231575)%20SocketID(13138)%20----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EINVITE%20sip%3A%2B447777777777%40customer.sbc.hoster.co.uk%3A5061%3Btransport%3Dtls%20SIP%2F2.0%3C%2FP%3E%3CP%3EFROM%3A%20John%20McClane%26lt%3B%26gt%3B%3Btag%3D5dad766e6f574758b8316e3bc83b4fb7%3C%2FP%3E%3CP%3ETO%3A%20%26lt%3B%26gt%3B%3Buser%3Dphone%3Btag%3D3813645846-1203322466%3C%2FP%3E%3CP%3ECSEQ%3A%204%20INVITE%3C%2FP%3E%3CP%3ECALL-ID%3A%206008f33f815e51cfac31a797b7eace65%3C%2FP%3E%3CP%3EMAX-FORWARDS%3A%2070%3C%2FP%3E%3CP%3EVIA%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Bbranch%3Dz9hG4bK87c1ea93%3C%2FP%3E%3CP%3ECONTACT%3A%20%26lt%3B443%26gt%3B%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3ECONTENT-LENGTH%3A%20960%3C%2FP%3E%3CP%3EMIN-SE%3A%2090%3C%2FP%3E%3CP%3ESUPPORTED%3A%20timer%3C%2FP%3E%3CP%3EUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2020.10.12.5%20i.EUWE.0%3C%2FP%3E%3CP%3ECONTENT-TYPE%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3ESESSION-EXPIRES%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3D-%20818192%202%20IN%20IP4%20127.0.0.1%3C%2FP%3E%3CP%3Es%3Dsession%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Eb%3DCT%3A10000000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Em%3Daudio%2049374%20RTP%2FSAVP%20104%209%20103%20111%2018%200%208%2097%20101%2013%20118%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Ea%3Drtcp%3A49375%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Aqf6h%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AcAKaay5mszWiR21QAfhitBtA%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%201%20UDP%201862270719%2052.113.9.255%2049374%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049374%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%202%20UDP%201862270462%2052.113.9.255%2049375%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049375%3C%2FP%3E%3CP%3Ea%3Dremote-candidates%3A1%20200.000.000.000%206020%202%20200.000.000.000%206021%3C%2FP%3E%3CP%3Ea%3Dlabel%3Amain-audio%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AL2vBEmXqbgm9EvI%2BCr1o49ICZ4FJafwFnddUrI51%7C2%5E31%3C%2FP%3E%3CP%3Ea%3Dinactive%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A104%20SILK%2F16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A9%20G722%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A103%20SILK%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A111%20SIREN%2F16000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A111%20bitrate%3D16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A18%20G729%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A18%20annexb%3Dno%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A0%20PCMU%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A97%20RED%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-16%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A118%20CN%2F16000%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E200%20OK%20SDP%20back%20to%20device%20after%20setting%20up%20hold%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A31.985%20----%20Outgoing%20SIP%20Message%20to%2052.114.75.24%3A2368%20from%20SIPInterface%20%233%20(Teams)%20TLS%20TO(%231575)%20SocketID(13138)%20----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESIP%2F2.0%20200%20OK%3C%2FP%3E%3CP%3EVia%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Bbranch%3Dz9hG4bK87c1ea93%3C%2FP%3E%3CP%3EFrom%3A%20%22John%20McClane%22%20%26lt%3B%26gt%3B%3Btag%3D5dad766e6f574758b8316e3bc83b4fb7%3C%2FP%3E%3CP%3ETo%3A%20%26lt%3B%26gt%3B%3Btag%3D3813645846-1203322466%3C%2FP%3E%3CP%3ECall-ID%3A%206008f33f815e51cfac31a797b7eace65%3C%2FP%3E%3CP%3ECSeq%3A%204%20INVITE%3C%2FP%3E%3CP%3EContact%3A%20%26lt%3B%26gt%3B%3C%2FP%3E%3CP%3ESupported%3A%20sdp-anat%3C%2FP%3E%3CP%3EAllow%3A%20UPDATE%2CPRACK%2CINFO%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3ERequire%3A%20timer%3C%2FP%3E%3CP%3ESession-Expires%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3EServer%3A%20Mediant%204000B%2Fv.7.20A.260.095%3C%2FP%3E%3CP%3EAccept%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Type%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Length%3A%20588%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3DMSX123%20986564814%2057709579%20IN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Es%3Dsip%20call%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Ea%3Dice-lite%3C%2FP%3E%3CP%3Em%3Daudio%206020%20RTP%2FSAVP%208%2013%20101%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%3CSPAN%3Ea%3Dinactive%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Ab8R5wxoJkXYTLfyh%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AU6Y4nSE6QuMxd2icJpcXW51e%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%201%20udp%202130706431%20200.000.000.000%206020%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%202%20udp%202130706430%20200.000.000.000%206021%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-15%2C16%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AWohABz54vXekdjP0u2BlGfgxthlk0lZByrVzBBDl%7C2%5E31%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20the%20extra%20re-invite%20after%201%20000%20ms%20with%20full%20voice%20in%20it%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A33.016%20----%20Incoming%20SIP%20Message%20from%2052.114.75.24%3A2368%20to%20SIPInterface%20%233%20(Teams)%20TLS%20TO(%231575)%20SocketID(13138)%20----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EINVITE%20sip%3A%2B447777777777%40customer.sbc.hoster.co.uk%3A5061%3Btransport%3Dtls%20SIP%2F2.0%3C%2FP%3E%3CP%3EFROM%3A%20John%20McClane%26lt%3B%26gt%3B%3Btag%3D5dad766e6f574758b8316e3bc83b4fb7%3C%2FP%3E%3CP%3ETO%3A%20%26lt%3B%26gt%3B%3Buser%3Dphone%3Btag%3D3813645846-1203322466%3C%2FP%3E%3CP%3ECSEQ%3A%206%20INVITE%3C%2FP%3E%3CP%3ECALL-ID%3A%206008f33f815e51cfac31a797b7eace65%3C%2FP%3E%3CP%3EMAX-FORWARDS%3A%2070%3C%2FP%3E%3CP%3EVIA%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Bbranch%3Dz9hG4bK4665a2fb%3C%2FP%3E%3CP%3ECONTACT%3A%20%26lt%3B443%26gt%3B%3C%2FP%3E%3CP%3ECONTENT-LENGTH%3A%20960%3C%2FP%3E%3CP%3EMIN-SE%3A%2090%3C%2FP%3E%3CP%3ESUPPORTED%3A%20timer%3C%2FP%3E%3CP%3EUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2020.10.12.5%20i.EUWE.0%3C%2FP%3E%3CP%3ECONTENT-TYPE%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%3C%2FP%3E%3CP%3ESESSION-EXPIRES%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3D-%20818192%203%20IN%20IP4%20127.0.0.1%3C%2FP%3E%3CP%3Es%3Dsession%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Eb%3DCT%3A10000000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Em%3Daudio%2049374%20RTP%2FSAVP%20104%209%20103%20111%2018%200%208%2097%20101%2013%20118%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%2052.113.9.255%3C%2FP%3E%3CP%3Ea%3Drtcp%3A49375%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Aqf6h%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AcAKaay5mszWiR21QAfhitBtA%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%201%20UDP%201862270719%2052.113.9.255%2049374%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049374%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A1%202%20UDP%201862270462%2052.113.9.255%2049375%20typ%20prflx%20raddr%2010.0.140.250%20rport%2049375%3C%2FP%3E%3CP%3Ea%3Dremote-candidates%3A1%20200.000.000.000%206020%202%20200.000.000.000%206021%3C%2FP%3E%3CP%3Ea%3Dlabel%3Amain-audio%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AL2vBEmXqbgm9EvI%2BCr1o49ICZ4FJafwFnddUrI51%7C2%5E31%3C%2FP%3E%3CP%3Ea%3Dsendrecv%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A104%20SILK%2F16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A9%20G722%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A103%20SILK%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A111%20SIREN%2F16000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A111%20bitrate%3D16000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A18%20G729%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A18%20annexb%3Dno%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A0%20PCMU%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A97%20RED%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-16%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A118%20CN%2F16000%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2nd%20200%20OK%20SDP%20back%20the%20device%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E10%3A04%3A33.141%20----%20Outgoing%20SIP%20Message%20to%2052.114.75.24%3A2368%20from%20SIPInterface%20%233%20(Teams)%20TLS%20TO(%231575)%20SocketID(13138)%20----%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESIP%2F2.0%20200%20OK%3C%2FP%3E%3CP%3EVia%3A%20SIP%2F2.0%2FTLS%2052.114.75.24%3A5061%3Bbranch%3Dz9hG4bK4665a2fb%3C%2FP%3E%3CP%3EFrom%3A%20%22John%20McClane%22%20%26lt%3B%26gt%3B%3Btag%3D5dad766e6f574758b8316e3bc83b4fb7%3C%2FP%3E%3CP%3ETo%3A%20%26lt%3B%26gt%3B%3Btag%3D3813645846-1203322466%3C%2FP%3E%3CP%3ECall-ID%3A%206008f33f815e51cfac31a797b7eace65%3C%2FP%3E%3CP%3ECSeq%3A%206%20INVITE%3C%2FP%3E%3CP%3EContact%3A%20%26lt%3B%26gt%3B%3C%2FP%3E%3CP%3ESupported%3A%20sdp-anat%3C%2FP%3E%3CP%3EAllow%3A%20UPDATE%2CPRACK%2CINFO%2CNOTIFY%2COPTIONS%2CBYE%2CINVITE%2CACK%2CCANCEL%3C%2FP%3E%3CP%3ERequire%3A%20timer%3C%2FP%3E%3CP%3ESession-Expires%3A%203600%3Brefresher%3Duas%3C%2FP%3E%3CP%3EServer%3A%20Mediant%204000B%2Fv.7.20A.260.095%3C%2FP%3E%3CP%3EAccept%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Type%3A%20application%2Fsdp%3C%2FP%3E%3CP%3EContent-Length%3A%20611%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ev%3D0%3C%2FP%3E%3CP%3Eo%3DMSX123%20986564814%2057709580%20IN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Es%3Dsip%20call%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Et%3D0%200%3C%2FP%3E%3CP%3Ea%3Dice-lite%3C%2FP%3E%3CP%3Em%3Daudio%206020%20RTP%2FSAVP%208%20101%2013%3C%2FP%3E%3CP%3Ec%3DIN%20IP4%20200.000.000.000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A8%20PCMA%2F8000%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3C%2FP%3E%3CP%3Ea%3Dfmtp%3A101%200-15%3C%2FP%3E%3CP%3Ea%3Drtpmap%3A13%20CN%2F8000%3C%2FP%3E%3CP%3Ea%3Dsendrecv%3C%2FP%3E%3CP%3Ea%3DsilenceSupp%3Aon%20-%20-%20-%20-%3C%2FP%3E%3CP%3Ea%3Dptime%3A20%3C%2FP%3E%3CP%3Ea%3Dice-ufrag%3Ab8R5wxoJkXYTLfyh%3C%2FP%3E%3CP%3Ea%3Dice-pwd%3AU6Y4nSE6QuMxd2icJpcXW51e%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%201%20udp%202130706431%20200.000.000.000%206020%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dcandidate%3A780296392%202%20udp%202130706430%20200.000.000.000%206021%20typ%20host%3C%2FP%3E%3CP%3Ea%3Dmid%3A1%3C%2FP%3E%3CP%3Ea%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AWohABz54vXekdjP0u2BlGfgxthlk0lZByrVzBBDl%7C2%5E31%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1937443%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1937443%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376841%22%20target%3D%22_blank%22%3E%40Lt_Flash%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EI%20don't%20see%20any%20issue%20with%20REFER%20over%20the%20last%20year%20on%20our%20infrastructure%20and%20we%20are%20using%20almost%20every%20type%20of%20DR%20configuration%20even%20with%20Local%20Media%20Optimization%20and%20proxy%20SBC.%20The%20only%20issue%20I%20had%20with%20REFER%20was%20that%20our%20firewall%20was%20setup%20all%20the%20time%20wrongly%20for%20mediabypass%20(first%20version)%20when%20SBC%20wanted%20to%20reach%20it's%20own%20public%20IP%20for%20media%20flow%20and%20crazy%20hairpin%20was%20needed%20over%20the%20FW.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1937461%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1937461%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F360557%22%20target%3D%22_blank%22%3E%40G____%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20I%20already%20stated%20I%20do%20not%20see%20any%20issue%20with%20using%20REFER%20so%20I%20would%20not%20remove%20REFER%20from%20Allow%20in%20Sp%20headers.%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20the%20description%20which%20I%20wrote%20last%20year%20I%20believe%20and%20there%20is%20also%20working%20SIP%20flow%20of%20Hold%20with%20REFER.%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20member%20of%20community%20mentioned%20issues%20in%20APAC%20region%20due%20to%20missing%20MoH%20bot%20there%20which%20was%20also%20causing%20issues%20for%20them.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams%2Fmusic-on-hold-in-teams-amp-4-seconds-until-hold-is-in-place-for%2Fm-p%2F977517%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams%2Fmusic-on-hold-in-teams-amp-4-seconds-until-hold-is-in-place-for%2Fm-p%2F977517%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1939188%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Routing%20-%20Internal%20call%20transfer%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1939188%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263389%22%20target%3D%22_blank%22%3E%40DaveChomi%3C%2FA%3E%26nbsp%3BYes%2C%20since%20the%20time%20of%20this%20topic%20I%20can%20confirm%20that%20call%20transfers%2C%20including%20internal%20ones%2C%20are%20working%20fine.%20We%20just%20had%20to%20figure%20out%20that%20Teams%20would%20send%20REFER%20back%20to%20SBC%20and%20expect%20SBC%20to%20send%20new%20INVITE%20back%20to%20Teams%20using%20passed%20Refer-To%20header%20with%20MS-style%20'x-t'%20and%20'x-m'%20tags.%20Also%20original%20Referred-By%20header%20must%20be%20preserved%20on%20new%20call.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi all,

 

My organisation is planning a move to direct routing. We have an AudioCodes VE SBC. I've been working on this for awhile and got everything to a pretty decent state.

 

I've come across an issue which is fairly new as I remember testing this months ago, when I was still trying to figure out how to deal with REFERs coming from MS Teams on call transfers.

 

So the call flow is as follows:

Incoming call from SBC to MS Teams -> MS Teams user transfers the call to internal user -> Call fails as MS Teams generates a REFER back to the SBC rather than route the call internally to MS Teams user target.

The issue I'm observing aside from MS Teams routing the transfer leg of the call is that the REFER-TO user part of the URI is blank. Please see the attached screenshot.

Its as if MS Teams is treating this as an external transfer and does not know how to populate the user part of the REFER-TO header. I've tested this with both users set up with Phone system and DDIs assigned to the user and users which have no phone system add-on or assigned DDI.

Please note that if you tried to transfer the call to a PSTN number, that works fine. I'm unsure if this would be something config related within our Teams tenancy or a genuine bug. I'm more inclined that this is the former rather than the latter as it does seem like fairly basic functionality and I'm confident this used to work a few months ago.

Any advice would be appreciated.

Kind Regards,

Sim

54 Replies
Highlighted

Hi Sim,

We've got exactly the same behaviour when trying to transfer calls that came from PSTN network and got answered by one of our Teams users and when they try to transfer to another Teams user. REFER-TO doesn't contain any LineURI or telephone number to complete the transfer. Did you have any luck fixing this issue? Also, I'm not sure if this was working before or not. But you seem to be correct in regards to Teams treating internal transfer as external one and sending SIP REFER back to SBC without providing any additional details in regards where the call should be actually connected or transferred to. When transferring to external number this works perfectly fine, REFER-TO contains an external number and can be processed by our SBC. BTW, can you tell what SBC are you using? Is it AudioCodes or Ribbon one? Or something not currently certified by Microsoft? Thanks!

Highlighted

@Lt_Flash We're using AudioCodes, and config wise its fine. It handles REFERs just fine. The issue here is that MS Teams should never had sent this REFER out the SBC, it should have handled it within the Teams environment as its a transfer from one Teams user to another. This only thing I suspect config wise is voice route regex I'm using, as its pretty much a catch all e.g. ".*" 
I've now made it more strict to capture digit patterns rather than all chars to see if the issue persists.

It makes no sense as I can call users internally, it only happens when PSTN call comes in from the direct Routing SBC, so Teams appears to be applying a different call routing logic when applying the transfer.

 

Out of curiosity can you let me know what your voice route pattern looks like? Was it a catch all like mine or is it more strict?

 

Thanks,

Sim

Highlighted

@Sims_Krastev 

Yes, I'm using the same voice pattern, ".*" to send all digits without any normalization to our SIP trunk. You're right, maybe the issue is because of that, I will update voice rules tomorrow to make it strictly country-based, like '^+44.*' to see if that helps! Good point, mate!

 

Also, yes, SIP REFER shouldn't be coming back to PBX when we're doing an internal transfer from one Teams User to another one, but it does for some reason, that's the problem.

I'll let you know here how it goes and thanks for your reply!

Highlighted

@Sims_Krastev 

Hi Sims,

I've removed the ".*" rule from my installation and created all specific rules for DIDs and still no luck, I can see SIP REFER coming back to PBX when I'm trying to transfer call that came from PSTN to Teams user. No luck here, unfortunately. Did you have any luck with this? Thanks.

Highlighted

@Lt_Flash I had no luck with changing the voice route, so ended up raising it with MS support.

Apparently if you disable REFER as an allowed method within your SBC's signalling messages, then MS Teams does not use REFER for transfers and just re-INVITEs to the SBC. That way the internal transfers work perfectly fine.

 

Highlighted
How did you disable REFER? I mean - does your SBC sends some 4xx code when MS sends a SIP REFER message? Or somehow different? Thanks!
Highlighted

@Lt_Flash 

No, not by rejecting the REFER with a response code. I basically did a message manipulation rule to re-build the Allow header for calls to MS Teams without including REFER. Which vendor are you using? If you have an AudioCodes as well, I can give you the rule syntax.

 

 

Highlighted
No, we're using a custom SBC, but yes, that was my second guess - to strip REFERs from packets. Thanks a lot, I'll give it a go and let you know if it works for me!
Highlighted

@Sims_Krastev you seem to be correct! I've just edited all messages that were coming from PSTN side of our SBC and stripped 'REFER' on SBC in 'Allow' field - and yes, Microsoft started to transfer calls correctly! Thanks a lot, mate, I've already read that disabling SIP REFER method helped some people, but I was trying to reply with 4xx or 5xx when receiving REFER from MS side, while I should have just removed that REFER method from SIP 'Allow' list! By the way, looking at the packets coming from Microsoft side I can see that they don't send REFER in allowed method list! Here's an example:

CONTENT-LENGTH: 685
MIN-SE: 90
SUPPORTED: timer
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2019.7.4.9 i.USWE2.4
CONTENT-TYPE: application/sdp
ALLOW: INVITE
ALLOW: ACK
ALLOW: OPTIONS
ALLOW: CANCEL
ALLOW: BYE
ALLOW: NOTIFY
SESSION-EXPIRES: 1800;refresher=uas

Thanks again for your help and I'm glad everything is working fine for you too now!

Highlighted

@Lt_Flash 

 

I can confirm this behavior, just that REFER triggered transfer is most common way for it and only fully standardized one. If your SBC is capable to terminate REFER note that MS still clearly indicates in Refer-To where to send INVITE back: 

REFER-TO: <sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689><sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689>sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689</sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689></sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689><sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689>
</sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689>

 

  and making sure you fill RURI with Refer-To and Contact uri-host correctly you will see MS does rest of the job nicely for REFER case too.  

Highlighted

@Matej_Maric 

 

It shows where to send INVITE to, but it doesn't have a DID or username in SIP R-URI so SBC can't figure out where to dial to. SBC uses PSTN-type dialing, so it needs some LineURI or DID to send INVITE to, like +44XXXXXXXX@sip.pstnhub.microsoft.com. Otherwise it can't decide what to put in SIP INVITE method as 'To' field. I've tried to update SIP INVITE to whatever is in REFER-TO header and send it back to Microsoft, but I was getting a 400 Bad Request back.

 

REFER-TO: <sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689><sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689>sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689</sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689></sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689><sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689></sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689>

 

There's no user part in this SIP RURI, only host. What should be put in To header? Contact header is obvious, it's our SBC Contact.

Highlighted

@Lt_Flash 

 

the thing is that SBC should only respect Refer-to header by means of SIP. REFER comes without user part but it's still fair enough and legal. So what my SBC does as last resort to send INVITE out is DNS query for hostname in Refer-To and fills RURI and To in same fashion:

 

INVITE sip:sip.pstnhub.microsoft.com:5061;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.65.100:5061;branch=z9hG4bKvahihb0040adpr8tb320.1
CSeq: 1 INVITE
Contact: <sip:sbc.customers.matejandfriends.com:5061;transport=tls>;sip.ice
From: <sip:+18572996345@sip.pstnhub.microsoft.com:5060;user=phone>;tag=11241SIPpTag011
To: <sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689>
Content-Type: application/sdp
Content-Length: 425
Referred-By: <sip:sip.pstnhub.microsoft.com:5061;x-m=8:orgid:bdc0511a-4a8d-48aa-bf1d-5ea6ef316e2a;x-t=2d88cb42-f810-417a-a0fc-80244a7fdd61;x-ti=9cfa2ad6-c73e-402d-b621-90d9af6ffea2;x-tt=ahr0chm6ly9hcgktzhutys1ldxdllnbzdg5odwiubwljcm9zb2z0lmnvbs92ms9uz2mvy2fsbg5vdglmawnhdglvbj9ky2k9yje2odmxntuwyjuwndg3mzk4nja4ndhlmgflyznimwq%3d>
Call-ID: 8f09e11d9183f754c525a0d4ce2aea46
Supported: replaces
Max-Forwards: 70</sip:sip.pstnhub.microsoft.com:5061;x-m=8:orgid:bdc0511a-4a8d-48aa-bf1d-5ea6ef316e2a;x-t=2d88cb42-f810-417a-a0fc-80244a7fdd61;x-ti=9cfa2ad6-c73e-402d-b621-90d9af6ffea2;x-tt=ahr0chm6ly9hcgktzhutys1ldxdllnbzdg5odwiubwljcm9zb2z0lmnvbs92ms9uz2mvy2fsbg5vdglmawnhdglvbj9ky2k9yje2odmxntuwyjuwndg3mzk4nja4ndhlmgflyznimwq%3d></sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:fce2158f-0e99-4ff7-a0b3-5b6b87d16689></sip:+18572996345@sip.pstnhub.microsoft.com:5060;user=phone></sip:sbc.customers.matejandfriends.com:5061;transport=tls> 

 

and that's just enough...

Highlighted

obviously we dont use same vendor SBC but standard wise logic should remain the same

Highlighted

@Matej_Maric 

Thanks for detailed description, I will try to reproduce this behaviour on my SBC, but it looks really strange to me that MS sends a SIP REFER packet back to SBC that connects calls to PSTN and uses LineURI telephone numbers for that. According to RFC it should provide a proper username or DID in such case. From what I can see now it's much simpler to just disallow REFER method and let Microsoft Teams handle internal call transfers on their side, which is more logical, rather than implementing such call forking. Anyway, your help is much appreciated and SIP INVITE packet is a perfect example on what I should try to achieve. Thanks!

Highlighted

@Matej_Maric 

Hi,

Unfortunately, that doesn't work for me, I'm sending same INVITE packet as you do but I'm getting back a '400 Bad Request' with a REASON:

REASON: Q.850;cause=111;text="a5d458f9-14c0-4cc4-8c10-202277af11e9;Unable to parse RURI."

Highlighted

@Matej_Maric 

 

Here's my INVITE packet, I had to remove triangle brackets to make post clear:

 

INVITE sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:7709b36f-1f10-4b1c-8a0f-9c0e5390c86c SIP/2.0

Via: SIP/2.0/TLS X.X.X.X:5061;branch=z9hG4bKf26f.503bdc4.0;i=54849946

From: "XXXXXXX";tag=a1d8a1ca-d330-4251-811d-35fa1a797c64&;

To: sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:7709b36f-1f10-4b1c-8a0f-9c0e5390c86c

Call-ID: 1fa2f0d0-ba41-4e4d-83be-fbef9d0739c6

CSeq: 10432 INVITE

Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REFER

Supported: 100rel, timer, replaces, norefersub

Session-Expires: 1800

Min-SE: 90

Max-Forwards: 69

Content-Type: application/sdp

Content-Length: 346

Contact: sip:gateway@sbc.xxx.xxx.com:5061;transport=TLS

 

Highlighted

@Matej_Maric 

All right, just to clarify, I've got this sorta working, I was removing REFERRED-BY header when placing a new INVITE and that's why it couldn't connect the call, after leaving that header intact the call can be transferred. But this far for us it's much easier just to remove REFER method from the list of allowed methods, otherwise it's quite a complex setup with our SBC. Thanks everyone for replies, now we have two working methods that allow call to be transferred to internal MS Teams users!

Highlighted

@Lt_Flash 

 

yep, tend to be with you on conclusions. being forced to implement both in real life felt like sharing things people find useful :) Most important is we understand now how to implement both methods and logic MS uses to trigger each.

 

cheers!

Highlighted

@Sims_Krastev 

 

Hi for us it's the other way around. Internal calls transfer perfectly fine and transfer to PSTN only works via the Teams Client. We do use some 3PIP Phones from AudioCodes, Yealink and Poly and if we try to transfer a call to an external Number, our SBC does not receive a refer-to number.

 

Now i have heard from someone, that their AudioCodes SBC receives this from Number even when it's coming from a 3PIP Phone.

 

Does anybody have an idea, why 3pip Phones or SfB Client for that matter (i know it's not supported but if 3pip should work, the SfB Client should also work) does not send a Refer to number to our SBC? Or is there anyone around who can test it and tell me if it's working with their SBC?

 

Thanks,

mozzie