Teams Direct Routing w/ Avaya

[Chris Krafcky]

We are currently in the POC stage, and I was hoping to get some guidance from those who have successfully configured direct routing with an on premises PSTN/PBX such as Avaya.  After all configurations within our Avaya PBX and Audiocodes, I am able to make outbound calls.  I am however not able to make inbound calls.  When tracing the call, I notice that I am getting the error: SIP/2.0 480 Temporarily Unavailable (User not registered) as well as: SIP/2.0 404 Not Found (No route available).  Can inbound calling be utilized for just the Teams client, or does it require a paired compatible telephone such as Polycom, Audiocodes, or Yealink?

[#2]

Hi Chris,
 
from your description I understood that outbound calls from Teams to the PSTN are working.
Teams -> AudioCodes -> Avaya -> PSTN
To make the inbound calls work you need to assign a PSTN number to the Teams user.
Set-CsUser -Identity “Spencer Low" -OnPremLineURI tel:+14255388797 -EnterpriseVoiceEnabled $true -HostedVoiceMail $true
https://docs.microsoft.com/en-us/MicrosoftTeams/direct-routing-configure#configure-the-phone-number-...
 
You also need to ensure that the routing for the inbound path is working
PSTN -> Avaya -> AudioCodes -> Teams

May be the following AudioCodes Guide helps:
https://www.audiocodes.com/media/13253/connecting-audiocodes-sbc-to-microsoft-teams-direct-routing-e...
 
The telephony part can be all done using the teams client. There is no need to use a desk phone.
 
Regards,
 
Paul

[#3]

Paul,

Thanks for your reply. Yes, all of the necessary configuration has been completed on the Microsoft side as well as the Avaya side (that I can think of). I've even worked with both an Audiocodes and Microsoft engineer to look at things. The DID is properly configured to the Teams user as when an outbound call is made, the caller ID is properly applied. The inbound calling is of another matter. I have provided a snippet from a recent trace below.

12:18:26.317 │──INVITE──►│ │ │ (2) T:6320 F:9179745965 U:6320 P:terminating
12:18:26.318 │◄──Trying──│ │ │ (2) 100 Trying
12:18:26.321 │◄──INVITE──│ │ │ (2) T:6320 F:9179745965 U:6320 P:imsterm
12:18:26.322 │──INVITE──►│ │ │ (2) T:6320 F:9179745965 U:6320 P:termdone
12:18:26.323 │◄──Trying──│ │ │ (2) 100 Trying
12:18:26.324 │──Trying──►│ │ │ (2) 100 Trying
12:18:26.324 │◄──Tempora─│ │ │ (2) 480 Temporarily Unavailable (User not registered)
12:18:26.325 │────ACK───►│ │ │ (2) sip:6320@10.100.14.45:5078
12:18:26.325 │──Tempora─►│ │ │ (2) 480 Temporarily Unavailable (User not registered)
12:18:26.365 │◄────ACK───│ │ │ (2) sip:6320@voice.hugheshubbard.com
12:18:26.366 │◄──Tempora─│ │ │ (2) 480 Temporarily Unavailable (User not registered)
12:18:26.367 │────ACK───►│ │ │ (2) sip:6320@voice.hugheshubbard.com
12:18:26.368 │──PUBLISH─►│ │ │ (4) sip:+2128376320@voice.hugheshubbard.com:5085
12:18:26.370 │◄──Not Fou─│ │ │ (4) 404 Not Found (No route available)

[#4]

Hi Chris,

this is good news.

So from the PSTN to Teams you get a 480 Temporarily Unavailable and from Avaya you get 404 Not Found? Both messages are send from Teams to your SBC?

Did you get any additional diagnostics info in the sip error messages that probably helps?

Things I would also check:

Certificate of SBC OK?

Baltimore CA trusted?

Codecs match?

Number manipulating okay? Called number match?

Check syslog of Audiocodes SBC for errors

Hope this helps to narrow down the reason for the failure.

Regards,

Paul

[#5]

Paul,

To answer your questions:

From PSTN to Teams: Successful / No Errors

From Teams to PSTN: 480 Temporarily Unavailable (User not registered) / 404 Not Found (No route available)

The SBC syslog doesn't produce anything which makes me think that it isn't even hitting the SBC.

Certificate of SBC OK? Yes

Baltimore CA trusted? Yes, this is installed

Codecs match? All codecs appear to match.

Number manipulating okay? Not sure.  I'd imagine that this is done at the SBC level.

Called number match? Not sure.

Note: We've created a SIP Trunk on the PBX side, but does a SIP Trunk need to be configured on the Audiocodes SBC?  If so, this is probably where the issue is.

[#6]

Update:

I am now able to get inbound and outbound calling to work, however after migrating from an old PRI circuit to a SIP trunk circuit, I get no audio on the outbound call.  Thoughts?

[#7]

Just first ideas I would have:
SIP trunk supports codec which is not on the list of codecs from Teams.
There are fw rules blocking media stream ports from SBC IP interface in DMZ
to SIP trunk.
It depends really on how the trunk is set on Avaya side too.
That's kind of reading from magic crystal ball, I would prefer to read the logs from various point of these connections :)

[#8]

Chris made already some progress and currently Linus and Alex are helping him in this thread:

https://techcommunity.microsoft.com/t5/Microsoft-Teams/Teams-Direct-Routing/m-p/320239#M24028

[#9]

Hello Paul, yeap I found out later that there is another thread where it came to attention that Avaya is just middle point that tries to open the session again with SBC to use SIP trunk on the very same SBC for outgoing calls. 

[#10]

David
Are you implementing Teams Direct Routing with Avaya?

[#11]

Hey Chris, no unofortunately not. 

Now I am focused on integration with Openscape Voice and Cisco UCM using AudioCodes SBC. Exploring all possibilities and bottlenecks. 

[#12]

Hi Chris,

I hope this meets you well. Can you share any guide with regards to integration with Avaya Ip Office.

Please assist.

Regards,

[#13]

Hi,
My integration is going well after a lot of hurdles. I was fortunate enough to have contacts who were able to share there experience in both Avaya and AudioCodes programming. The integration however was with Avaya CM 6.3 and not IP Office. The overall steps may be the same though. I will attempt to create a document that you can put to use. Let me know if that works for you.

[#14]

Hi Chris,

Wow, that was fast. Thank you for your prompt response.

I think the steps will be same, I will appreciate the document, Let me give you a little info of what I have achieved. I've been able to pair the SBC with Microsoft Teams Phone System. I can make inbound and outbound PSTN calls via a SIP trunk. So, when someone calls a DID assigned to a user on Teams, it works perfectly. I can also use my Teams client and dial PSTN lines and it works perfectly.

However, we have an Avaya IP Office PBX in my Office and I will like Teams client to be able to call Avaya Extensions. I've setup all necessary SIP Profile, IP group, Proxy set etc but the Alarm keeps flagging an error about the IP group "IP Group is temporarily blocked. IPGroup(IP-PBX) Blocked Reason: No Working Proxy"

I look forward to the document.

Thank you so much.

Regards,

Ijeoma

[#15]

@Chris Krafckyany update on the document?

Kindly assist. I hope to read from you soon.

Regards,

Ijeoma

[#16]

@Chris Krafcky,

Hi Chris,

I hope this meets you well.

Any update with regards to the document you intend to share?

Kindly respond.

Regards,

Ijeoma

[#17]

Hi @Chris Krafcky, did you have some time to create this document? We're trying to configure our Avaya CM to Direct Routing but we're looking some guide about this subject.

Did you try to use Avaya SBC to connect to MS Direct Routing or just AudioCodecs?

Thanks,

RM

[#18]

@Chris Krafcky 

I am now tasked with finding a replacement for traditional RCC with on prem Lync via Avaya AES - Avaya CM.  The closest thing looks to be the direct routing option.  Few questions:

1. For the SBC, what type of licensing is required for that? 

2. Do you have any documentation for the Avaya setup? Also running CM 6.3

[#19]

@Ijeoma1735 

did you ever finish the connection between AVAYA IP Office and Teams? 

Would appreciate it if you could share any documentation and useful links...

- Marty

[#20]

@MarketingMarty  Hi, I have the same doubt. If you know of any information please share it. Thank you very much.