MS Teams Direct Transfer fails -- Audiocodes SBC --> Cisco Cube --> ITSP

%3CLINGO-SUB%20id%3D%22lingo-sub-1707852%22%20slang%3D%22en-US%22%3EMS%20Teams%20Direct%20Transfer%20fails%20--%20Audiocodes%20SBC%20--%26gt%3B%20Cisco%20Cube%20--%26gt%3B%20ITSP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1707852%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20There%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20per%20my%20subject%20we%20have%20a%20client%20with%20a%20particular%20setup.%3C%2FP%3E%3CP%3EThey%20are%20still%20running%20SfB%20and%20busy%20with%20a%20MS%20Teams%20POC.%20So%20what%20I%20understand%20is%20they%20cannot%20make%20any%20REFER%20changes%20on%20the%20AudioCodes%20SBC%20due%20to%20the%20SfB%20still%20running%20over%20it%20and%20now%20we%20need%20to%20make%20the%20REFER%20and%20not%20sure%20what%20else%20manipulations%20on%20the%20Cisco%20Cube.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESfb%20----------%3C%2FP%3E%3CP%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%20%7C%20--------%26gt%3B%20AudioCodes%20SBC%20--%26gt%3B%20Cisco%20CUBE%20--%26gt%3B%20ITSP%20--%26gt%3B%20Mobile%20device%3C%2FP%3E%3CP%3EMS%20Teams---%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESfB%20works%20like%20a%20charm.%3C%2FP%3E%3CP%3EMS%20Teams%20can%20make%20and%20receive%20calls%20via%20this%20setup%20no%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChallenge%20is%20making%20a%20direct%20transfer%20to%20a%20mobile%20number%20or%20external%20number%20for%20that%20means.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20the%20following%20on%20the%20Cisco%20CUBE%20under%20the%20voice%20class%20sip-profiles%3C%2FP%3E%3CP%3Evoice%20class%20sip-profiles%20200%3C%2FP%3E%3CP%3Erequest%20INVITE%20sip-header%20From%20modify%20%22(%26lt%3B.*%40domain.com)%22%20%22%5C1%3Buser%3Dphone%22%3CBR%20%2F%3Erequest%20OPTIONS%20sip-header%20Max-Forwards%20modify%20%2270%22%20%220%22%3CBR%20%2F%3Erequest%20INVITE%20sip-header%20Contact%20modify%20%22(%26lt%3B.*)%40%22%20%22%5C1%3Btgrp%3Dxxxxxxxx%3Btrunk-context%3Ddomain.com%40%22%3CBR%20%2F%3Erequest%20INVITE%20sip-header%20SIP-Req-URI%20copy%20%22%40(.*%3A5061)%22%20u01%3CBR%20%2F%3Erequest%20INVITE%20sip-header%20From%20copy%20%22%40(.*)%26gt%3B%22%20u02%3CBR%20%2F%3Erequest%20INVITE%20sip-header%20SIP-Req-URI%20modify%20%22sip%3A%5C1%40%22%20%22sip%3A%22%3CBR%20%2F%3Erequest%20INVITE%20sip-header%20SIP-Req-URI%20modify%20%22sip%3A%5C1%22%20%22sip%3A%2B%22%3CBR%20%2F%3Erequest%20INVITE%20sip-header%20History-Info%20modify%20%22%26lt%3B%26gt%3Brequest%20INVITE%20sip-header%20History-Info%20modify%20%22%26lt%3B%26gt%3Brequest%20INVITE%20sip-header%20To%20modify%20%22%26lt%3B%26gt%3B%22%20%22%26lt%3B%26gt%3B%22%3CBR%20%2F%3Erequest%20INVITE%20sip-header%20To%20modify%20%22%26lt%3B%26gt%3B%22%20%22%26lt%3B%26gt%3B%22%3CBR%20%2F%3Erequest%20ANY%20sip-header%20Contact%20modify%20%22%40.*%3A%22%20%22%40%5Cu02%3A%22%3CBR%20%2F%3Eresponse%20ANY%20sip-header%20Contact%20modify%20%22%40.*%3A%22%20%22%40%5Cu02%3A%22%3CBR%20%2F%3Erequest%20ANY%20sdp-header%20Audio-Attribute%20modify%20%22a%3Dsendonly%22%20%22a%3Dinactive%22%3CBR%20%2F%3Eresponse%20200%20sdp-header%20Session-Owner%20copy%20%22IN%20IP4%20(.*)%22%20u03%3CBR%20%2F%3Eresponse%20200%20sdp-header%20Audio-Connection-Info%20modify%20%220.0.0.0%22%20%5Cu03%3CBR%20%2F%3Erequest%20REFER%20sip-header%20From%20copy%20%22%40(.*com)%22%20u04%3CBR%20%2F%3Erequest%20REFER%20sip-header%20Refer-To%20modify%20%22sip%3A%5C%2B(.*)%40.*%3A5061%22%20%22sip%3A%2B%5C1%40%5Cu04xxx.xxx.xxx.xxx%3A5061%22%3CBR%20%2F%3Erequest%20REFER%20sip-header%20Refer-To%20modify%20%22%3CSIP.%3E%3C%2FSIP.%3Erequest%20ANY%20sip-header%20Contact%20modify%20%22%40.*%3A%22%20%22%40%5Cu04xxx.xxx.xxx.xxx%3A%22%3CBR%20%2F%3Eresponse%20ANY%20sip-header%20Contact%20modify%20%22%40.*%3A%22%20%22%40%5Cu04xxx.xxx.xxx.xxx%3A%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20still%20I%20get%20a%20SIP%2F2.0%20403%20Forbidden%20from%20the%20ITSP%20(Still%20waiting%20for%20the%20ITSP%20logs%20to%20see%20what%20they%20reject)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReceived%3A%3CBR%20%2F%3ESIP%2F2.0%20403%20Forbidden%3CBR%20%2F%3EVia%3A%20SIP%2F2.0%2FUDP%20xxx.xxx.xxx.xxx%3A5060%3Bbranch%3Dz9hG4bK268E32CC7%3CBR%20%2F%3EFrom%3A%20%22Luke%20Stoodley%22%20%26lt%3B48xxxxxx%26gt%3B%3Btag%3DAEC8D03C-122B%3CBR%20%2F%3ETo%3A%20%26lt%3B027xxxxxxx%26gt%3B%3Btag%3DSD5jtie99-1627562496-1600939053022%3CBR%20%2F%3ECall-ID%3A%209C943598-FD7D11EA-98839CE5-F9CD41D5%40xxx.18.150.78%3CBR%20%2F%3ECSeq%3A%20105%20REFER%3CBR%20%2F%3ETimestamp%3A%201600939152%3CBR%20%2F%3EContent-Length%3A%200%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3EMy%20SIP%20REFER%20looks%20like%20the%20following%20after%20the%20manipulation%3C%2FP%3E%3CP%3ESent%3A%3CBR%20%2F%3EREFER%20sip%3A027xxxxxxx%40xxx.xxx.254.199%3A5060%3Btransport%3Dudp%20SIP%2F2.0%3CBR%20%2F%3EVia%3A%20SIP%2F2.0%2FUDP%20xxx.18.150.78%3A5060%3Bbranch%3Dz9hG4bK268E32CC7%3CBR%20%2F%3EFrom%3A%20%22Demo%20user%22%20%26lt%3B48xxxxxx%26gt%3B%3Btag%3DAEC8D03C-122B%3CBR%20%2F%3ETo%3A%20%26lt%3B027xxxxxxx%26gt%3B%3Btag%3DSD5jtie99-1627562496-1600939053022%3CBR%20%2F%3ECall-ID%3A%209C943598-FD7D11EA-98839CE5-F9CD41D5%40xxx.18.150.78%3CBR%20%2F%3ECSeq%3A%20105%20REFER%3CBR%20%2F%3EMax-Forwards%3A%2070%3CBR%20%2F%3EContact%3A%20%26lt%3B48xxxxxx%26gt%3B%3CBR%20%2F%3EUser-Agent%3A%20Cisco-SIPGateway%2FIOS-16.3.2%3CBR%20%2F%3ETimestamp%3A%201600939152%3CBR%20%2F%3EAuthorization%3A%20Digest%20username%3D%22xxxxxxx%22%2Crealm%3D%22domain.com%22%2Curi%3D%22sip%3A027xxxxxxx%40xxx.xx.254.199%3A5060%3Btransport%3Dudp%22%2Cresponse%3D%223874cdbd2254ed03d1eefec89fc355b5%22%2Cnonce%3D%22BroadWorksXkfglrz0xThivf6wBW%22%2Ccnonce%3D%22FFFFFFFF%22%2Cqop%3Dauth%2Calgorithm%3DMD5%2Cnc%3D00000004%3CBR%20%2F%3ERefer-To%3A%20sip%3A%2B64210xxxxxx%40xxx.xxx.254.167%3A5061%3CBR%20%2F%3EReferred-By%3A%20%3CXXX.18.150.78%3E%3CBR%20%2F%3EContent-Length%3A%200%3C%2FXXX.18.150.78%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20I%20need%20to%20change%20the%20Reffered-By%20address%20as%20well%20and%20if%20so%20anyone%20have%20any%20idea%20how%20on%20the%20Cisco%3F%3C%2FP%3E%3CP%3EOr%20is%20there%20anyway%20the%20Audiocodes%20can%20have%20SfB%20and%20Ms%20Teams%20co-exist%20and%20both%20working%2C%20one%20using%20the%20REFER%20and%201%20don't%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20feedback%20will%20greatly%20be%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1707852%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-1714192%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20Direct%20Transfer%20fails%20--%20Audiocodes%20SBC%20--%26gt%3B%20Cisco%20Cube%20--%26gt%3B%20ITSP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1714192%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F807249%22%20target%3D%22_blank%22%3E%40Sirkalliemarie%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BI'm%20going%20to%20see%20if%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25085%22%20target%3D%22_blank%22%3E%40Carolyn%20Blanding%20(MS%20TEAMS)%3C%2FA%3E%26nbsp%3Bcan%20assist.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi There,

 

As per my subject we have a client with a particular setup.

They are still running SfB and busy with a MS Teams POC. So what I understand is they cannot make any REFER changes on the AudioCodes SBC due to the SfB still running over it and now we need to make the REFER and not sure what else manipulations on the Cisco Cube.

 

Sfb ----------

                     | --------> AudioCodes SBC --> Cisco CUBE --> ITSP --> Mobile device

MS Teams---

 

SfB works like a charm.

MS Teams can make and receive calls via this setup no problem.

 

Challenge is making a direct transfer to a mobile number or external number for that means.

 

I have tried the following on the Cisco CUBE under the voice class sip-profiles

voice class sip-profiles 200

request INVITE sip-header From modify "(<.*@domain.com)" "\1;user=phone"
request OPTIONS sip-header Max-Forwards modify "70" "0"
request INVITE sip-header Contact modify "(<.*)@" "\1;tgrp=xxxxxxxx;trunk-context=domain.com@"
request INVITE sip-header SIP-Req-URI copy "@(.*:5061)" u01
request INVITE sip-header From copy "@(.*)>" u02
request INVITE sip-header SIP-Req-URI modify "sip:\1@" "sip:"
request INVITE sip-header SIP-Req-URI modify "sip:\1" "sip:+"
request INVITE sip-header History-Info modify "<sip:\1@" "<sip:"
request INVITE sip-header History-Info modify "<sip:\1" "<sip:+"
request INVITE sip-header To modify "<sip:\1@(.*)>" "<sip:\u01>"
request INVITE sip-header To modify "<sip:\1(.*)@.*>" "<sip:+\1@\u01>"
request ANY sip-header Contact modify "@.*:" "@\u02:"
response ANY sip-header Contact modify "@.*:" "@\u02:"
request ANY sdp-header Audio-Attribute modify "a=sendonly" "a=inactive"
response 200 sdp-header Session-Owner copy "IN IP4 (.*)" u03
response 200 sdp-header Audio-Connection-Info modify "0.0.0.0" \u03
request REFER sip-header From copy "@(.*com)" u04
request REFER sip-header Refer-To modify "sip:\+(.*)@.*:5061" "sip:+\1@\u04xxx.xxx.xxx.xxx:5061"
request REFER sip-header Refer-To modify "<sip:sip.*:5061" "<sip:+@\u04xxx.xxx.xxx.xxx:5061"
request ANY sip-header Contact modify "@.*:" "@\u04xxx.xxx.xxx.xxx:"
response ANY sip-header Contact modify "@.*:" "@\u04xxx.xxx.xxx.xxx:"

 

but still I get a SIP/2.0 403 Forbidden from the ITSP (Still waiting for the ITSP logs to see what they reject)

 

Received:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK268E32CC7
From: "Luke Stoodley" <sip:48xxxxxx@xxx.xxx.254.199>;tag=AEC8D03C-122B
To: <sip:027xxxxxxx@xxx.xxx.254.199>;tag=SD5jtie99-1627562496-1600939053022
Call-ID: 9C943598-FD7D11EA-98839CE5-F9CD41D5@xxx.18.150.78
CSeq: 105 REFER
Timestamp: 1600939152
Content-Length: 0

My SIP REFER looks like the following after the manipulation

Sent:
REFER sip:027xxxxxxx@xxx.xxx.254.199:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP xxx.18.150.78:5060;branch=z9hG4bK268E32CC7
From: "Demo user" <sip:48xxxxxx@xxx.xxx.254.199>;tag=AEC8D03C-122B
To: <sip:027xxxxxxx@xxx.xxx.254.199>;tag=SD5jtie99-1627562496-1600939053022
Call-ID: 9C943598-FD7D11EA-98839CE5-F9CD41D5@xxx.18.150.78
CSeq: 105 REFER
Max-Forwards: 70
Contact: <sip:48xxxxxx@xxx.xxx.254.167:5060>
User-Agent: Cisco-SIPGateway/IOS-16.3.2
Timestamp: 1600939152
Authorization: Digest username="xxxxxxx",realm="domain.com",uri="sip:027xxxxxxx@xxx.xx.254.199:5060;transport=udp",response="3874cdbd2254ed03d1eefec89fc355b5",nonce="BroadWorksXkfglrz0xThivf6wBW",cnonce="FFFFFFFF",qop=auth,algorithm=MD5,nc=00000004
Refer-To: sip:+64210xxxxxx@xxx.xxx.254.167:5061
Referred-By: <sip:xxx.18.150.78>
Content-Length: 0

 

Do I need to change the Reffered-By address as well and if so anyone have any idea how on the Cisco?

Or is there anyway the Audiocodes can have SfB and Ms Teams co-exist and both working, one using the REFER and 1 don't?

 

Any feedback will greatly be appreciated.

 

 

1 Reply
Highlighted