locked
Microsoft Lync and Nortel CS1000 integration RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am looking deploy Microsoft Lync into an environment that uses Nortel CS1000 PBXs in the environment and test either a direct sip connection, RCC, and if possible. dual forking.  The CS1000s have a mix of version 5.5 and 6.0 deployed at this time.  We have OCS 2007 R2 but do not have enterprise voice configured at this time.

    I am aware that the CS1000 needed the OCS Proxy (and/or?) the Multimedia Convergence Manager (MCM) to get functionality going for OCS 2007.  What I can't find out yet is what it will take to get Lync to talk to these same CS1000s.  

    Does anyone have any pointers or ideas about the prerequisites we may need?  I've put in calls to Avaya but I've not gotten a clear answer yet.

    Thanks!!!

    Friday, January 28, 2011 11:12 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The Nortel CS1000 has not yet been certified for Lync Server 2010 to date. 

    If your goals are to get Direct SIP, RCC and/or Dual Forking you will require a Lync FE server, Mediation Server (Can colocate with the FE server now) and Nortel MCM.  Most of the guidance for OCS 2007 R2 can be followed with this deployment until the point where you are configuring the static route and RCC configuration in Lync. 

    Mark

    Mark King | MVP: Lync Server | MCTS:UC Voice | MCSE: Messaging | MCITP:Enterprise Messaging | www.unplugthepbx.com
    • Marked as answer by Ted_Weiss Tuesday, February 1, 2011 3:24 PM
    Monday, January 31, 2011 5:30 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    The Nortel CS1000 has not yet been certified for Lync Server 2010 to date. 

    If your goals are to get Direct SIP, RCC and/or Dual Forking you will require a Lync FE server, Mediation Server (Can colocate with the FE server now) and Nortel MCM.  Most of the guidance for OCS 2007 R2 can be followed with this deployment until the point where you are configuring the static route and RCC configuration in Lync. 

    Mark

    Mark King | MVP: Lync Server | MCTS:UC Voice | MCSE: Messaging | MCITP:Enterprise Messaging | www.unplugthepbx.com
    • Marked as answer by Ted_Weiss Tuesday, February 1, 2011 3:24 PM
    Monday, January 31, 2011 5:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Depending on the model of CS1k and the feature sets installed on each chassis, you will need a gateway.  Other SIP capable models may be able to do a direct SIP trunk.  The OCS restrictions and needs for MCM were more Nortel than OCS.  For Lync the exact same is true.

    John Weber [Lync MVP]
    • Marked as answer by Ted_Weiss Tuesday, February 1, 2011 3:24 PM
    • Unmarked as answer by Ted_Weiss Wednesday, February 23, 2011 3:21 AM
    Monday, January 31, 2011 5:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Lync 2010 does not have an "application proxy" server role like OCS2007 or OCS2007 R2. But MCM service is dependent on "OCS Proxy" service.

    Also, Lync 2010 does not support "dual mode" (both RCC and Enterprise Voice), so if you hope to integrate with Lync 2010 with Nortel CS1K, I suggested that you can Direct SIP for enterprise voice mode,which do not required a MCM/OCS Proxy server at all.

    Jacky Fan
    Friday, February 4, 2011 2:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I wanted to update this post for anyone else that needs this information.

    I was successful getting the Nortel environment working and can now make calls both in and out to PSTN.  Basically this is what was needed:

    For a Direct SIP connection - a SIP Trunk pointed from the Nortel PBX to the Lync mediation server.  The trunk was simply configured to use port 5060 over TCP, had DTMF enabled, and enabled Redirection instead of 'Proxy' for our connection settings.  Even though we could have had the Nortel add the '+' sign, we decided to use rules on Lync to add it.  Naturally we added the PBX as our allowed gateway for Lync at 5060 TCP and configured the needed dialing rules.

    Once we got everything lined up - after a lot of trial and error - I can happily say that a Nortel PBX running on 6.0 rev. software works just fine with Lync 2010 and does not require any additional software to get it to work. 

     

    • Edited by Ted_Weiss Wednesday, February 23, 2011 3:22 AM spelling correction
    • Marked as answer by Ted_Weiss Tuesday, March 29, 2011 7:32 PM
    • Unmarked as answer by Ted_Weiss Tuesday, March 29, 2011 7:32 PM
    Wednesday, February 23, 2011 3:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Are you running an MGC or MC32S cards for your DSPs?

    -jonmck

    http://www.t2mdev.com/jonmck/
    Wednesday, February 23, 2011 3:56 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    HI Ted,

    Quick question about your thread? Did you just get voice going via Sip Trunk to the Nortel or did you get RCC working with MCM? With the loss of the Application Proxy I am unsure if this wll be possible in the same way as it worked in OCS2007 R2? Any advice greatly appreciated.

     

    Thursday, February 24, 2011 10:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    There is no sign of the application proxy role in Lync.

    I think it is more interesting as to the direction that Avaya is taking things by reading the CS 1000 7.5 Product Bulletin that was released in December. This is one of two docs that I've seen from Avaya that mentions Lync.

    http://support.avaya.com/css/P8/documents/100124119

    Key areas of the document that you will be interested in

    The product bulletin states on page 30 that the NRS is no longer supported (except in certain circumstances). NRS is a key component to Converged Office with MCM implementations.

    Also on page 30 is the statement that OCS 2007 R2 with NRS is no longer supported.

    On page 93 is the statement that Converged Office users will require ACE 2.3. If you want to get a taste of the ACE implementation here is the doc that pertains to it... http://support.avaya.com/css/P8/documents/100120512

    Integration with Lync is supported only with ACE as stated on page 35

    Bottom line is that the integration with CS 1000 has completely changed and RCC with dual forking is not supported on Lync. Also, RCC with dual forking on the Avaya side is not supported starting with Release 7.5.

    I wrote a blog post that may give you an idea of an alternative approach with a pure Lync/OCS solution. http://blog.lyncdialog.com/2011/01/how-to-replicate-remote-call-control.html

    Feel free to contact me if you have additional questions.

    -jonmck

    http://blog.lyncdialog.com
    Thursday, February 24, 2011 10:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ted,

    Could you please provide some more details as to how you were able to integrate Lync with you CS1000?  The more details you could provide, the better.

     

    Thanks.

    Thursday, March 10, 2011 8:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You are correct in stating that CS1000 R7.5 NRS is no longer supported for converged office with OCS 2007 R2.  That only means NRS SIP redirect is no longer supported, but NRS using SIP Proxy Server (SPS) is still supported.  In CS1000 R7.5, NRS SIP Proxy Server (SPS) has moved in to Session Manager (SM).  CS1000 Converged Office (with RCC & dual forking) lives on and is supported with OCS 2007 R2 in this manner.  For more integration specifics, refer to the latest R7.5 Avaya technical publication NN43001-121 - Converged Office Fundamentals appendix C.

    Now when it comes to CS1000/Lync integration, using Avaya's Agile Communication Environment (ACE) will probably be the only Avaya suggested approach due to the elimination of the OCS Application Proxy Server in a Lync network.  That OCS proxy provided the only SIP CTI (via TR/87) path between the CS1000 and OCS worlds and is now gone.

     

    Monday, March 21, 2011 10:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We created a SIP trunk from the Nortel to the Mediation server and simply used the Nortel as our gatway.  Since MCM is no longer available there is no longer RCC like it would be in OCS.  From there we were able to fully implement all the Lync EV features and found that our pilot users were very satified with the experience overall.

    Ted Weiss
    Tuesday, March 29, 2011 7:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Which version of CS 1000 are you running?
    http://blog.lyncdialog.com/
    Tuesday, March 29, 2011 7:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    More info for those that care :-)

    I have good news for CS 1000 6.0.

    A Direct SIP patch is available, but only by request to Avaya support. Request MPLR28305. This patch is only used for Direct SIP with OCS and disables Early Media on the Nortel side.

    The same patch seems to work well with Lync, but of course if any problems arise with it may not be something that support will fix.

    The CS 1000 that I installed this patch on, uses MGC cards for DSP resources.

    The same patch may be available for 7.0, but I'm not sure on that.

    -jonmck

    http://blog.lyncdialog.com/
    • Proposed as answer by lyncdialogMVP Thursday, March 31, 2011 8:06 PM
    • Edited by lyncdialogMVP Tuesday, September 25, 2012 5:29 PM
    Thursday, March 31, 2011 8:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We have a nortel cs1k/mcm/ocs infrastructure that has been wroking well for the past little while and I decided that I wanted to test the LYNC client on my laptop so I uninstalled my office communicator and installed LYNC (I did not make any other changes to infrastructure).  Now any inbound calls I recieve go straight to vocemail as I'm not notified of an inbound call.  It does not ring on my laptop.  I can make outbound calls without issue.  Has anyone seen this behaviour before?

    Thanks!

    Friday, May 20, 2011 1:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You can provide a unified desktop experience with Avaya/Nortel real-time communications to Microsoft Lync, OCS, Office 365 and other Microsoft applications. Tight integration keeps the client interface consistent and allows users to communicate from their preferred devices.

     Avaya ACE 3.0 for MS Lync becomes officially available December 2011.

    See full details and online demo at: http://voxns.blogspot.com/2011/10/avayas-new-ace-30-for-microsoft-lync.html

    Friday, October 28, 2011 5:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ggilkison, can you provide how ACE allows a user to escalate to Video, Desktop Sharing, Lync Meetings? All those features are disabled in the video you provided.

    How does ACE interact with Microsoft's Edge environment to extend the ability to make and and receive calls without the user of a VPN?

    With voice disabled in the Lync client, how does ACE provide "Computer Mode" calls... is there another softphone installed behind the scenes?

    -jonmck

    http://blog.lyncdialog.com/
    Friday, October 28, 2011 6:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Jonmckdenver

    thanks to share information about this integration.

    customer is asking to integrate a CS1000E system Running 5.5.

    as I saw in the 7.5 bulletin you sahre with us, integration with CS1000 R6 is posible through SM.

    and I would like to know if it is posible to integrate MS Lync with CS1000E R5.5

    any comment will be really appreciated.

    regards.

    Wednesday, November 9, 2011 3:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The answers I've given for 6.0 integration to Lync would apply to 5.5. There is a specific patch for "Direct SIP" that you will need to obtain from Avaya support. It is an LTD patch and is not publically available. I do not know what the latest version is... but in the Direct SIP 5.5 bulletin it is MPLR28305

    Other than that follow the Documentation and you should have success.

    Keep in mind that Lync is not supported with CS1000 5.5. You will also find that Microsoft will not officially support it either. In general if you call support for help, they will try to help you... but they will always have the ability to fall back on the "It isn't supported" reason.

    -jonmck

    http://blog.lyncdialog.com/
    Wednesday, November 9, 2011 4:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Jonmckdenver

    thanks for your comments.

    the information you provided to me is very useful.

    regards.

    Wednesday, November 9, 2011 4:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are having the same issue. In fact we have two issues: PBX user cannot call Lync user, and when Lync user call PBX user he cannot hear PBX user for 20 seconds if the PBX user is using black digital phone or attandand service (a.k.a. queue: for sales press 1 etc.).

    I don't know what this magical hotfix can fix, but I got tired waiting for a magic and just called AVAYA directly. They asked me for some "Sold to" number (kind of service agreement number) and I told them that I don't have one, so the guy searched through his records and somehow found my organization in his list and agreed to open a ticket. So will see how is going. I mentioned that I need MPLR28305 for CS1K version 7.0.

    In several days (December 1) I will celebrate 1 year sine I started my attempts to integrate Lync 2010 with AVAYA PBX. O boy, I can tell you: this is not an easy one. AVAYA is not an easy cookie! They are hard! But what can I do? I have to keep trying. I want Lync 2010 eventually replace this metal robot that sitting there, eating lots of power and money!

    I wish Microsoft and AVAYA will talk to each other and release one document: How to integrate AVAYA CS1000 with Lync 2010: Step-by-step. Am I asking for too much? Looks like...I guess enemies never talk to each other. Especially today when AVAYA's days are counted... :-)

    Wednesday, November 9, 2011 10:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are piloting Lync right now.

    I have a CS1K on 6.0 that I can call from Lync over SIP via an AudioCodes gateway to the NRS with no problem and vice versa.

    But I also have a CS1K on 5.5 as an end point on the same NRS that calls will not connect completely from the Lync to and vice versa .

    It rings the far end and the call can be answered but there is no media path. A PCAP indicates that the CS1K on 5.5 is not negotiating the codec.

    I’m using G711 or G729.

    Neither work.

    Any advice would be helpful.

    Tuesday, November 22, 2011 6:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    One thing that comes to mind is to make sure you have DSP resources available. Either an MC32S or MGC.

    -jonmck

    http://blog.lyncdialog.com/
    Tuesday, November 22, 2011 6:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    RayJDG

    what type of AudioCodes GW do you have. Can you share your config (INI) file?

    Thanks

    Thursday, March 22, 2012 8:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ted, we are trying to configure the same scenario and I am having problems getting out over the PSTN.  I am wondering if you can assist me with the lync setup?

    Wednesday, August 22, 2012 11:31 AM