Add Escalation from P2P PSTN Call to Conference with SfB CCE
Currently this is not possible, needs hybrid or on-prem deployment.
You can host PSTN + Skype conference, but it must not start from a P2P PSTN Call (either a P2P Skype call, or directly a conference you planned, in that case the PSTN call will go throug dial-in conference service in the cloud).
I understand the reason: since the PSTN call leg goes from the on-prem voice GW for the P2P call, it's an issue to transfer it to the conference dial-in service which is at Microsoft.
An alternative would be to add conference service in Cloud Connector (Even if it is limited to a certain amount of users) to host conference on-prem, just like a normal hybrid deployment.
Hi guys. It is possible to escalate a CCE P2P PSTN Call to conference. Just you have tu configure the tenant as described here: https://technet.microsoft.com/en-us/library/0e2f2395-b890-4d16-aa2d-99d52438b89c#BKMK_ConfigureMediationServer
The problem i have is when I schedule a PSTN Conference, the dial out is done by the cloud service and not the CCE and i'm not able to dial-out to local extensions where the CCE is connected (legacy PBX). And there is no option to select the Dial-out route (cloud or CCE)
Anthony Bates commented
I have recently come across this issue. A P2P call can be escalated to a PSTN Conference call since it is originating in the cloud. A P2P PSTN call cannot be escalated due to the fact it is originating in CCE. The article, https://technet.microsoft.com/en-us/library/mt740658.aspx is misleading but is clarified in the link Peter has reference since it does not state P2P PSTN call. Does anyone know when this will be addressed?
Peter Grau commented
Hi there, We also just hit this bump in the road. Just finished migrating mail, skype and PSTN to the cloud last week. We've been used to on-premise Skype with local PSTN. Now with Cloud PBX and PSTN via Cloud Connector, this is a drawback.
I fell over the last item in this article: https://technet.microsoft.com/en-us/library/mt740651.aspx but I cannot get it to work. The info seems a bit misleading, as the mediation server doesn't have an internal FQDN as such. I tried with IP. The "system" accepts the command, but it doesn't help with the problem.