Hi,
Hope this is a suitable forum to ask this question! I have very recently installed Lync 2013 Enterprise (separate SQL, Front End and Mediation Servers) in a virtual environment and have connected the Lync 2013 environment to an Avaya PBX environment. All the voice traffic etc., is mostly working and generally I have no major issues with two way voice between Lync and Avaya(via Sip trunk-Although this shows as a PSTN Gateway on the Lync Topology). I have a couple of scenarios that I want to look at in more detail however which sends me installing and running OCS Logger on the Front End / Med Server environments to obtain trace traffic. Although OCS Logger appears to have installed OK, and when I open the screens I can choose the relevant data to capture i.e. MediaStack RTP, S4 etc,. when it comes to running the analyse function I am getting a whole bunch of problems inside OCS which are not helping me look at other problems.
If I run OCS and capture a trace between Lync to Lync extensions, then the Snooper shows some info on the trace tab, but NO info on the Messages tab. (Which I kind of expect being a Lync to Lync call)
If I run OCS and capture a trace between Lync to Avaya SIP/H.323 extension (or vice versa) I either get NO messages on the Messages tab or a message stating Error/warning “parsing error:Emtpy SDP Offer” or “illegal character/S4”. Please note, however that the voice is OK – I do have two way audio between the two devices.
I also have 2xLync 2010 setups here and we have no issue with either of the OCS loggers that were installed on them. I have used the latest OCS Logger.msi I can find on Microsoft’s website and it installed just fine.
I have compared the fields available in the OCS logger used by Lync 2010 and the OCS used by Lync2013 and there are differences i.e.
Lync 2010 Front End Server – has fields S4, ServerAgent, ServerConfiguration, ServerTransportAdaptor SIPStack and SIPStackPerf
Lync2013 Front End Server has fields S4, ServerAgent, ServerConfiguration, ServerTransportAdaptor SIPStackBUT NOT SIPStackPerf
There are some other fields present in Lync2010, but not in 2013. It is the same when comparing OCS on the Med Servers on a 2010 and a 2013. I do realise that being a later version, things may well change, so this might not even be an issue at all.
I have tried very hard to see if anyone else is having the same problems with OCS via various google searches / looking/reading in forums but have come across very little. (I have been trying to resolve this for about 6 weeks now, with no luck.If anyone has any advice regarding the OCS and what might be wrong, be it the software or something I have not ticked during installation I would appreciate it.
Kind regards, HppcFan