Jan 04 2019 05:59 AM
Jan 04 2019 05:59 AM
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?
Jan 04 2019 10:34 AM
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
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:
The telephony part can be all done using the teams client. There is no need to use a desk phone.
Jan 04 2019 10:38 AM
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:email@example.com:5078
12:18:26.325 │──Tempora─►│ │ │ (2) 480 Temporarily Unavailable (User not registered)
12:18:26.365 │◄────ACK───│ │ │ (2) sip:firstname.lastname@example.org
12:18:26.366 │◄──Tempora─│ │ │ (2) 480 Temporarily Unavailable (User not registered)
12:18:26.367 │────ACK───►│ │ │ (2) sip:email@example.com
12:18:26.368 │──PUBLISH─►│ │ │ (4) sip:+firstname.lastname@example.org:5085
12:18:26.370 │◄──Not Fou─│ │ │ (4) 404 Not Found (No route available)
Jan 04 2019 11:08 AM
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?
Number manipulating okay? Called number match?
Check syslog of Audiocodes SBC for errors
Hope this helps to narrow down the reason for the failure.
Jan 04 2019 12:49 PM
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.
Jan 17 2019 06:29 AM
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?
Jan 18 2019 04:24 AM
Jan 18 2019 05:03 AM
Chris made already some progress and currently Linus and Alex are helping him in this thread:
Jan 20 2019 11:56 PM
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.
Jan 23 2019 03:25 AM
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.
May 16 2019 07:53 AM
May 16 2019 08:07 AM
May 16 2019 08:20 AM
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.
Jul 11 2019 10:41 AM
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?
Jul 23 2019 02:47 PM
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