Incoming Call Audio Delay
-
15 februarie 2011 16:16
We're running Lync Standard Edition and we're integrating with a Nortel CS1000E.
From my Lync client, I can successfully make calls to external numbers and internal numbers with no problems. I can even call from a Nortel desk phone to my Lync client with no problems. I cannot for the life of me though figure out why incoming calls to my Lync client from external numbers have the audio delayed.
Specifically, the calls are connected immediately but I can't hear the external caller's voice for approximately 20 seconds. It's like clockwork in that I can all of the sudden hear the external caller audio after 20 seconds of being connected in the call. The external caller however can hear me through my Lync client from the beginning of the call.
Any help with this issue would be greatly appreciated. Thanks!
Toate mesajele
-
16 februarie 2011 00:28
Hi Buddy,
I had exactly the same result during a migration from OCS R2 to Lync 2010. As I have a SIP trunk directly connected to the Mediation server in a production environment things got really uneasy.
After heaps of blogs on early media I found that in my case, disabling the windows firewall on the Mediation box did the trick.
Let me know how you get on.
- Propus ca răspuns de KB 123 16 februarie 2011 22:15
- Anulare propunere ca răspuns de Buddy Searcy 19 februarie 2011 15:45
-
19 februarie 2011 15:19Thanks, Philopolis. I already tried disabling the firewall on our Lync server but unfortunately that hasn't helped.
-
25 februarie 2011 16:02
Similar issue here, only it's forwarded or transferred calls from the CS1000 and Firewall is off on all the servers.
-
24 aprilie 2011 09:16Have you tried to use the early media settings in the Nortel CS1000,may be it helps.
regards Holger Technical Specialist UC -
2 noiembrie 2011 10:01
Hi Buddy Searcy,
Do you have resolved the problem? I have the same issue.
Thanks,
Elia.
-
3 noiembrie 2011 17:44
Hi, Elia,
Unfortunately we haven't resolved the issue. I heard there's a Nortel patch to resolve the issue but haven't had a chance to get our service partner to apply it yet. Sorry.
Buddy
-
27 martie 2012 21:17
Apparently this update won't help. In fact it is already embedded into version 6.0 or later of CS1000. We have CS1000 v7.0 and having exactly the same issue for over a year now. This issue preventing us from starting migration from CS1000 to Lync as we need to keep existing (AVAYA) and new (LYNC) users connected all the time so they can cll each other.
In 3 weeks we will try replacing new MC32S (where "S" stands for "Secure") media cards with older MC32 cards as we suspect that the issue may be caused by incompatible media cards. Also we are planning to upgrade CS1000 to final version - 7.5. Apparently it will no more new versions and this product is going to be discontinued some time in the near future.
Finally if nothing will help, we probably will try to purchase Media Gateway, something like AudioCodes Mediant 1000. I heared from some people that Media Gateway may fix this issue. Anyway just trying to be helpful and if anybody who had this issue were able to resolve it.
Thanks!
P.S. AVAYA and MICROSOFT are not friends any more!
-
14 aprilie 2012 15:19
Hi
We had the same problem with CS1K v5.5 and Lync 2010 after Mediation server migration from OCS2k7r2. The gateway helped to solve the problem. We used Audiocodes MSBG1000 with 1 E1 interface.
It seems there is a solution from Avaya (patch, new software etc) but from the rational point of view there is no reason to invest into legacy PBX. Furthermore we've got some new Lync features working, like Media Bypass.
- Propus ca răspuns de Nick Bobuh 14 aprilie 2012 15:19
-
15 aprilie 2012 20:42
Hi Nick,
Thanks for your reply. Next weekend we will be doing two changes to our PBX in attempt to resolve 20 seconds delay issue:
1. We will be upgrading CS1000 PBX from version 7.0 to latest version 7.5. I also believe that 7.5 will be last version in this PBX and no more updates in the future
2. We will try disabling all MC32S cards and install one MC32 media card, hoping that the issue may be caused by newer "S"ecure cards MC32S
If none of the changes will help, we will need to try next step - Audiocodes Mediant 1000 media gateway. May I ask you a preliminary question about using Media Gateway between Lync and PBX - how this does exactly work?
I assume gateway will have 2 NICs, one connected to PBX VLAN (all those TLAN, ELAN etc.) and another connected to Lync VLAN. Lync will point to gateway, and PBX will point to gateway. Right? Is there anything special to be configured, or out-of-the-box is all good to go? Any special hints?
Thanks!
-
16 aprilie 2012 14:53
Hi
At first – the platform and software release(especially). We have Mediant 1000 – MSBG with 3 IPMEDIA cards, 1 E1 PRI card, CRMX module(1 WAN + 4 LAN IF). Also check whether you’ve purchased this device with the IP2IP GW license key (or this could be SBC license if you plan to connect your infrastructure to the external SIP provider) if you plan to connect to CS1000 via IP. The Audiocodes firmware version - 6.20A.049.004. We had some SRTP problems with earlier versions.
Second – you should decide how to connect the GW to the PBX. IP2IP looks as the simplest way if you have already purchased lot of Nortel SIP trunk licenses. If not – think about E1 PRI – that could be cheaper and less risky in future(almost impossible to invent something new in that technology J – so it will definitely work for years and there will be no need to upgrade the PBX). Another reason – even with the gateway in IP2IP mode there were some “small” problems (“hold” and “parking” didn’t work etc). Considering that Avaya has no plans to support the CS1000 platform and we had just a few Nortel SIP connection licenses we left this IP2IP connection just for backup route or testing.
Third – connection to the Lync Mediation Server: IP or TLS. We have Mediation servers collocated with Front-Ends and Microsoft recommends to use secure connection to the GW so we use TLS. Anyway if you can allocate separate VLAN for Nortel <> Audiocodes it’s better to do that. You just need to connect one of your Mediant CRMX Ethernet interface to this VLAN and configure it in the Mediant webadmin as IP2IP (as I mentioned before it has 4 LAN NICs so it won't be a problem).
Then – everything according to the documentation (SIP proxies, coders config, routing, number manipulation, AD based routing if you need it etc.). You may not find the specific Audiocodes document – like “How to connect Nortel CS1K version XX.XX to Lync via IP or PRI EuroISDN” but you may use lot of other stuff that describes various Lync interoperability scenarios from Audiocodes. A little trick I've spent few hours to find:) – if you use +XXXXXXXXX;ext=YYYY format for the LineURI – you’ll need to set EnableMicrosofExt parameter to “1” from the admin console on the GW. Don’t forget to set up the syslog on the Mediant – it helps greatly.
-
16 aprilie 2012 15:57
Can you run a wireshark trace on your Lync server and post the results
http://lync2010tips.blogspot.com - ucottonk@hotmail.com - If this post has been useful please click the green arrow to the left or click 'Propose as answer'
.png)
