Direct Routing with AudioCodes - PSTN Call Transferred to Teams user fails

%3CLINGO-SUB%20id%3D%22lingo-sub-332245%22%20slang%3D%22en-US%22%3EDirect%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332245%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20the%20thing...%20Transfer%20of%20PSTN%20calls%20from%20Direct%20Routing%20just%20does%20not%20simply%20work%20as%20I%20would%20assume.%20Searching%20and%20reading%20articles%20and%20blogs%20does%20not%20really%20provide%20clear%20way%20how%20I%20should%20setup%20my%20SBC%20in%20order%20to%20properly%20support%20transfer%20of%20call%20from%20Teams%20user%20side.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1%2F%20If%20I%20understand%20correctly%20the%20setup%20there%20is%20now%20way%20how%20to%20transfer%20PSTN%20Direct%20Routing%20Call%20to%20Teams%20user%20who%20is%20not%20enabled%20with%20Enterprise%20Voice%2C%20correct%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2%2F%20If%20user%20is%20enabled%20for%20Enterprise%20voice%20I%20should%20be%20able%20to%20transfer%20him%2Fher%20the%20PSTN%20call%20which%20was%20routed%20to%20my%20Teams%20user%2C%20correct%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20see%20from%20current%20behavior.%20Using%20transfer%20function%20and%20aiming%20to%20Teams%20user%20I%20do%20see%26nbsp%3Bthe%20call%20is%20going%20back%20to%20SBC%20with%20REFER%20and%20based%20on%20configuration%20guide%20of%20Audiocodes%20there%20should%20be%20IP-to-IP%20routing%20rule%20which%20is%20terminating%20the%20REFER%20back%20to%20Teams%20interface.%20It%20would%20mean%20that%20the%20transfer%20should%20not%20hit%20the%20local%20interface%20and%20local%20PBX%20but%20what%20if%20the%20call%20is%20transferred%20to%20local%20registered%20SIP%20phone%20on%20PBX%20side%3F%20Or%20what%20if%20I%20want%20to%20xfer%20to%20external%20number%20which%20is%20also%20done%20on%20the%20PBX%20side.%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20even%20if%20I%20have%20now%20the%20setup%20basically%20as%20described%20from%20Audiocodes%20I%20see%20the%20REFER%20is%20sent%20to%20my%20PBX%20and%20if%20the%20destination%20of%20the%20call%20should%20be%20Teams%20user%20it's%20failing%20because%20my%20PBX%20does%20not%20know%20symbols%20in%20Contact-to%2C%20Refer-By%20fields%20and%20sends%20403%20Forbidden.%20If%20I%20do%20the%20transfer%20to%20number%20of%20the%20same%20user%20it%20works.%3C%2FP%3E%3CP%3E(PBX%20interface%20is%20set%20to%20handle%20SBC%20Refer%20as%20Regular%20and%20Teams%20interface%20as%20Handle%20Locally.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20just%20say%20that%20if%20the%20call%20is%20transferred%20to%20Teams%20user%20I%20wouldn't%20involve%20the%20SBC%20with%20REFER%2C%20I%20do%20not%20know%20why%20it%20should%20go%20back%20and%20just%20not%20simply%20on%20side%20of%20Teams%20the%20transfer%20is%20done.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20kind%20of%20insight%3F%20Or%20just%20recommendation%20about%20how%20to%20tune%20the%20configuration%20with%20some%20additional%20manipulation%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-332245%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDirect%20Routing%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833097%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833097%22%20slang%3D%22en-US%22%3EHi%20%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%2C%20I'm%20facing%20the%20same%20issue%20described%20by%20you%20I'm%20deploying%20Teams%20Direct%20Routing%20and%20PSTN%20linked%20to%20Audiocodes%20gateway%20Have%20you%20fixed%20it%3F%20How%3F%20Thanks%20in%20advance%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-840800%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-840800%22%20slang%3D%22en-US%22%3E%3CP%3E%2CHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F355978%22%20target%3D%22_blank%22%3E%408alemas63_%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3Estill%20facing%20that%20issue%20and%20I%20haven't%20received%20any%20clear%20idea%20from%20any%20consultant%20or%20forum%20so%20far%20why%20my%20SBC%20is%20not%20handling%20that%20request%20locally%20if%20everything%20is%20set%20according%20to%20guide.%3C%2FP%3E%3CP%3EI%20will%20get%20in%20few%20weeks%20professional%20services%20from%20Audiocodes%20so%20I%20hope%20they%20will%20lead%20me%20into%20correct%20configuration.%20%3B)Lets%20see%20I%20basically%20need%20to%20have%20two%20rules.%20One%20will%20say%20REFER%20for%20Teams%20user%20sent%20back%20to%20Teams%20and%20REFER%20to%20external%20number%20just%20will%20go%20to%20our%20internal%20whatever%20PBX%20where%20it%20will%20be%20handled%20properly.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-841936%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-841936%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%2F355978%22%20target%3D%22_blank%22%3E%408alemas63_%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%3CP%3Eyou%20forced%20me%20to%20have%20a%20look%20today%20more%20deeply%20into%20that%20topic%20again%20and%20do%20some%20try%2Ffail%2Ftry%20configuration%20changes%20%3A)I%20focused%20on%20the%20handling%20of%20the%20REFER%20messages%20on%20the%20Audiocodes%20SBC.%3C%2FP%3E%3CP%3ESo%20I%20have%20setup%20REFER%20handling%20on%20the%20SBC%20IP%20profile%20for%20my%20SIP%20trunk%20of%20the%20PBX%20to%20Handle%20Locally%20(It's%20in%20the%20section%20SBC%20Forward%20and%20Transfer%20of%20IP%20Profile%20configuration).%26nbsp%3B%3C%2FP%3E%3CP%3ERemote%20REFER%20Mode%20-%20Handle%20Locally%3CBR%20%2F%3ERemote%20Replaces%20Mode%20-%20Handle%20Locally%3CBR%20%2F%3ERemote%203xx%20Mode%20-%20Handle%20Locally%3C%2FP%3E%3CP%3ELets%20see%20what%20it%20brings%20in%20addition%20to%20fact%20that%20transfer%20to%20Teams%20user%20started%20to%20work!%3C%2FP%3E%3CP%3EAlso%20transfer%20of%20other%20Teams%20user%20to%20external%20PSTN%20number%20works!%20But%20the%20call%20is%20initiated%20by%20Teams%20Proxy%20as%20new%20invite%20and%20not%20sent%20by%20PBX%20as%20REFER%20to%20my%20PBX.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20also%20transfer%20external%20caller%20from%20my%20Teams%20user%20to%20another%20external%20PSTN%20number%20but%20I%20failed%20with%20media%2C%20there%20was%20no%20audio.%20Might%20be%20different%20issue%20now%20in%20setup.%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20check%20how%20do%20you%20handle%20the%20REFER%20on%20SBC%20on%20IP%20Profile%20of%20the%20other%20side%20of%20the%20connection%20(usually%20downside%2C%20local%20PBX%20or%20provider%20SIP%20trunk...)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-858508%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-858508%22%20slang%3D%22en-US%22%3E%3CP%3EHi%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%3EI%20fixed%20the%20issue%20with%20Audiocodes%20team%3C%2FP%3E%3CP%3EThey%20have%20changed%20the%20manipulation%20rule%20%3A%20dest%20number%20Tel-%26gt%3BIP%3C%2FP%3E%3CP%3EPreviously%20Destination%20Phone%20Pattern%20was%20set%20*%20%2C%20now%20it%20is%200%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-866920%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-866920%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F355978%22%20target%3D%22_blank%22%3E%408alemas63_%3C%2FA%3E%26nbsp%3Bfor%20update%20on%20this.%3C%2FP%3E%3CP%3EI%20will%20have%20AudioCodes%20guys%20also%20soon%20over%20my%20configuration%20for%20review.%3C%2FP%3E%3CP%3ENot%20sure%20if%20I%20got%20right%20the%20point%20about%20change%20of%20message%20manipulation%2C%20could%20you%20please%20be%20more%20specific%20please%3F%20Did%20they%20just%20change%20the%20routing%20rule%20for%20REFER%20like%20that%3F%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3ESource%20IP%20Group%3C%2FTD%3E%3CTD%3ETeams_IPG%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ERequest%20Type%3C%2FTD%3E%3CTD%3EAll%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ESource%20Username%20Pattern%3C%2FTD%3E%3CTD%3E*%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ESource%20Host%3C%2FTD%3E%3CTD%3E*%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ESource%20Tag%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EDestination%20Username%20Pattern%3C%2FTD%3E%3CTD%3E0%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EDestination%20Host%3C%2FTD%3E%3CTD%3E*%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EDestination%20Tag%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EMessage%20Condition%3C%2FTD%3E%3CTD%3E--%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ECall%20Trigger%3C%2FTD%3E%3CTD%3EREFER%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EReRoute%20IP%20Group%3C%2FTD%3E%3CTD%3ETeams_IPG%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20the%20IP%20profiles%20are%20then%20set%20to%20handle%20REFER%3F%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20IP%20profile%20to%20handle%20locally%2C%20right%3F%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20the%20other%20SIP%20profile%20for%20SIP%20trunk%20or%20PBX%20is%20set%20also%20Handle%20Locally%20or%20Regular%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-867324%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867324%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%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%3EI%20fixed%20after%20setting%20%22Destination%20Phone%20Pattern%22%20to%20zero%20(p%3CSPAN%3Ereviously%20it%20was%20set%20*)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThis%20parameter%20is%20in%20Gateway%20%26gt%3B%20Manipulation%20%26gt%3B%20Dest%20Number%20Tel-to-IP%3C%2FP%3E%3CP%3EI%20set%20the%20following%20parameters%20as%20suggested%20by%20you%3C%2FP%3E%3CP%3E%3CEM%3E%3CSPAN%3ERemote%20REFER%20Mode%20-%20Handle%20Locally%3C%2FSPAN%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSPAN%3ERemote%20Replaces%20Mode%20-%20Handle%20Locally%3C%2FSPAN%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSPAN%3ERemote%203xx%20Mode%20-%20Handle%20Locally%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20SBC%26nbsp%3B%20%26gt%3B%20Routing%20%26gt%3B%20IP-to-IP%20Routing%20I%20configured%20%22Destination%20Username%20Pattern%22%26nbsp%3B%20%22*%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%3EOthers%20values%20are%20as%20in%20table%20posted%20by%20you%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%3ELet%20me%20know%20if%20you%20need%20further%20details%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1369926%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1369926%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%3BDid%20you%20ever%20manage%20to%20get%20this%20resolved%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20the%20same%20issue%20with%20a%20AudioCodes%20M800b%2C%20calling%20inbound%20%2F%20outbound%20is%20working%20fine%2C%20but%20transfers%20will%20not%20function.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20configured%20the%20REFER%20rule%20in%20the%20ip-to-ip%20table%2C%20what%20rule%20did%20you%20setup%20in%20the%20Tel-to-ip%20to%20get%20this%20fixed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20at%20the%20logs%2C%20when%20we%20receive%20the%20REFER%2C%20the%20system%20sends%20a%20INVITE%20back%20to%20sip.pstn.microsoft.com%20but%20it%20sends%20out%20of%20another%20interface%2C%20not%20the%20WAN%20port%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20gratefully%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1376949%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1376949%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%2F131785%22%20target%3D%22_blank%22%3E%40Michael%20Mettam%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%3CP%3Ethis%20is%20really%20old%20post.%20Since%20that%20I%20was%20able%20to%20get%20deep%20into%20how%20this%20works%20and%20was%20able%20to%20find%20out%20that%20my%20main%20issue%20was%20wrongly%20setup%20hairpin%20on%20firewall%20%3A)%3C%2Fimg%3E%20while%20SBC%20wanted%20to%20send%20media%20to%20its%20own%20public%20IP%20it%20just%20dropped%20the%20media%20on%20the%20firewall%20interface.%3C%2FP%3E%3CP%3EI%20do%20not%20use%20Gateway%20on%20our%20Audiocodes%20SBC%2C%20so%20we%20set%20only%20IP%20to%20IP%20rules%20for%20routing.%3C%2FP%3E%3CP%3EBut%20correct%20setup%20for%20Teams%20REFER%20handling%20was%20as%20I%20described%20earlier%20and%20once%20you%20see%20that%20SBC%20sends%20after%20REFER%20Invite%20back%20to%20MS%20SIP%20proxy%20it%20is%20correct%20behavior.%20If%20your%20experience%20is%20that%20incorrect%20interface%20is%20in%20use%20then%20I%20would%20check%20again%20the%20part%20of%20Destination%20IP%20Group%20configuration%20in%20REFER%20rule%20and%20if%20that%20IP%20Group%20has%20correct%20SIP%20Interface%20with%20WAN%20network%20interface%20in%20its%20configuration.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20not%20say%20the%20issue%20is%20in%20Tel-to-IP%20routing%20in%20your%20case.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1376975%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20with%20AudioCodes%20-%20PSTN%20Call%20Transferred%20to%20Teams%20user%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1376975%22%20slang%3D%22en-US%22%3EHello%2C%3CBR%20%2F%3EMany%20thanks%20for%20coming%20back%20to%20me%2C%20we%20can%20see%20the%20REFER%20invite%20to%20the%20SBC%20via%20the%20public%20ip%20etc%2C%20but%20the%20INVITE%20message%20rule%20appears%20to%20not%20being%20honoured%20as%20it%20sends%20it%20from%20the%20incorrect%20interface.%3CBR%20%2F%3EI%E2%80%99ll%20simply%20have%20to%20raise%20a%20case%20with%20AudioCodes%20as%20the%20rules%20are%20all%20there%2C%20but%20for%20some%20reason%20it%20just%20doesn%E2%80%99t%20do%20as%20it%E2%80%99s%20told.%3CBR%20%2F%3EMany%20thanks%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Here is the thing... Transfer of PSTN calls from Direct Routing just does not simply work as I would assume. Searching and reading articles and blogs does not really provide clear way how I should setup my SBC in order to properly support transfer of call from Teams user side. 

 

1/ If I understand correctly the setup there is now way how to transfer PSTN Direct Routing Call to Teams user who is not enabled with Enterprise Voice, correct? 

 

2/ If user is enabled for Enterprise voice I should be able to transfer him/her the PSTN call which was routed to my Teams user, correct?

 

What I see from current behavior. Using transfer function and aiming to Teams user I do see the call is going back to SBC with REFER and based on configuration guide of Audiocodes there should be IP-to-IP routing rule which is terminating the REFER back to Teams interface. It would mean that the transfer should not hit the local interface and local PBX but what if the call is transferred to local registered SIP phone on PBX side? Or what if I want to xfer to external number which is also done on the PBX side. 

But even if I have now the setup basically as described from Audiocodes I see the REFER is sent to my PBX and if the destination of the call should be Teams user it's failing because my PBX does not know symbols in Contact-to, Refer-By fields and sends 403 Forbidden. If I do the transfer to number of the same user it works.

(PBX interface is set to handle SBC Refer as Regular and Teams interface as Handle Locally.)

 

I would just say that if the call is transferred to Teams user I wouldn't involve the SBC with REFER, I do not know why it should go back and just not simply on side of Teams the transfer is done.

 

Any kind of insight? Or just recommendation about how to tune the configuration with some additional manipulation?  

9 Replies
Highlighted
Hi @DaveChomi, I'm facing the same issue described by you I'm deploying Teams Direct Routing and PSTN linked to Audiocodes gateway Have you fixed it? How? Thanks in advance
Highlighted

,Hi @8alemas63_ ,

still facing that issue and I haven't received any clear idea from any consultant or forum so far why my SBC is not handling that request locally if everything is set according to guide.

I will get in few weeks professional services from Audiocodes so I hope they will lead me into correct configuration. ;) Lets see I basically need to have two rules. One will say REFER for Teams user sent back to Teams and REFER to external number just will go to our internal whatever PBX where it will be handled properly. 

Highlighted

Hi @8alemas63_

you forced me to have a look today more deeply into that topic again and do some try/fail/try configuration changes :) I focused on the handling of the REFER messages on the Audiocodes SBC.

So I have setup REFER handling on the SBC IP profile for my SIP trunk of the PBX to Handle Locally (It's in the section SBC Forward and Transfer of IP Profile configuration). 

Remote REFER Mode - Handle Locally
Remote Replaces Mode - Handle Locally
Remote 3xx Mode - Handle Locally

Lets see what it brings in addition to fact that transfer to Teams user started to work!

Also transfer of other Teams user to external PSTN number works! But the call is initiated by Teams Proxy as new invite and not sent by PBX as REFER to my PBX. 

I tried also transfer external caller from my Teams user to another external PSTN number but I failed with media, there was no audio. Might be different issue now in setup. 

So check how do you handle the REFER on SBC on IP Profile of the other side of the connection (usually downside, local PBX or provider SIP trunk...)

Highlighted

Hi@DaveChomi 

I fixed the issue with Audiocodes team

They have changed the manipulation rule : dest number Tel->IP

Previously Destination Phone Pattern was set * , now it is 0

 

 

Highlighted

Thank you @8alemas63_ for update on this.

I will have AudioCodes guys also soon over my configuration for review.

Not sure if I got right the point about change of message manipulation, could you please be more specific please? Did they just change the routing rule for REFER like that? 

 
 
Source IP GroupTeams_IPG 
Request TypeAll 
Source Username Pattern* 
Source Host* 
Source Tag  
Destination Username Pattern0 
Destination Host* 
Destination Tag  
Message Condition-- 
Call TriggerREFER 
ReRoute IP GroupTeams_IPG

 

How the IP profiles are then set to handle REFER? 

Teams IP profile to handle locally, right? 

And the other SIP profile for SIP trunk or PBX is set also Handle Locally or Regular? 

 

Highlighted

Hi @DaveChomi 

I fixed after setting "Destination Phone Pattern" to zero (previously it was set *)

This parameter is in Gateway > Manipulation > Dest Number Tel-to-IP

I set the following parameters as suggested by you

Remote REFER Mode - Handle Locally
Remote Replaces Mode - Handle Locally
Remote 3xx Mode - Handle Locally

In SBC  > Routing > IP-to-IP Routing I configured "Destination Username Pattern"  "*"

Others values are as in table posted by you

Let me know if you need further details

Highlighted

@DaveChomi Did you ever manage to get this resolved?

 

Having the same issue with a AudioCodes M800b, calling inbound / outbound is working fine, but transfers will not function.

 

We have configured the REFER rule in the ip-to-ip table, what rule did you setup in the Tel-to-ip to get this fixed?

 

Looking at the logs, when we receive the REFER, the system sends a INVITE back to sip.pstn.microsoft.com but it sends out of another interface, not the WAN port?

 

Any help would be gratefully appreciated.

Highlighted

Hi @Michael Mettam

this is really old post. Since that I was able to get deep into how this works and was able to find out that my main issue was wrongly setup hairpin on firewall :) while SBC wanted to send media to its own public IP it just dropped the media on the firewall interface.

I do not use Gateway on our Audiocodes SBC, so we set only IP to IP rules for routing.

But correct setup for Teams REFER handling was as I described earlier and once you see that SBC sends after REFER Invite back to MS SIP proxy it is correct behavior. If your experience is that incorrect interface is in use then I would check again the part of Destination IP Group configuration in REFER rule and if that IP Group has correct SIP Interface with WAN network interface in its configuration. 

I would not say the issue is in Tel-to-IP routing in your case. 

Highlighted
Hello,
Many thanks for coming back to me, we can see the REFER invite to the SBC via the public ip etc, but the INVITE message rule appears to not being honoured as it sends it from the incorrect interface.
I’ll simply have to raise a case with AudioCodes as the rules are all there, but for some reason it just doesn’t do as it’s told.
Many thanks