martes, 03 de abril de 2012 13:06
In the OCS we got the following feature:
The ABNF, as defined in [RFC5234], for the ms-call-source SIP header is as follows:
Ms-Call-Source = "Ms-Call-Source" HCOLON ("ms-rtc" / "non-ms-rtc")
The supported tokens for the ms-call-source header are "ms-rtc" and "non-ms-rtc". The first token designates that the call originated from a protocol server network, and the latter means that the call originated from a non–protocol server network, such as a PSTN or IP-PBX.
The syntax of this header is illustrated as follows:
This information it's on page 14 of MS-OCPSTN documment - http://msdn.microsoft.com/en-us/library/cc431499(v=office.12).aspx
I would like to know feature is applied to Lync Server 2010 Mediation Server too. I've see this flag "Ms-Call-Source" already in some internal traces of Lync Server Logging but this is not send to external SIP devices (ie. PSTN Gateways).
Could we enable this with an option config? This feature was used to handle dual forking scenarios with the PSTN Gateway.
Or this function it's only available on OCS 2007 R2 and it was removed from Lync Server 2010 Mediation Server.
Hope my question was clear.
Todas las respuestas
jueves, 05 de abril de 2012 9:15Moderador
As I know,Lync doesn't support Dual-forking,but you can read through the Lync RCC deployment guide if you would like enable remote call control for your Lync users.
Besides,I suggest you post the question on MSDN forum with the following link for more professional help.
TechNet Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
- Marcado como respuesta Sharon.ShenMicrosoft Contingent Staff, Moderator martes, 08 de mayo de 2012 3:27