locked
Lync 2010 Dual forking with Cisco Call manager and Missed call notifications RRS feed

  • Question

  • Dears,

    I have a scenario were :-

           - Integration was done between Lync 2010 and Cisco CUCM

           - Single Number Reach using CUCM Remote Destination profile is Configured

           - Exchange 2007 UM is Integrated with Lync 2010

    The issue we are facing is that when ever a Cisco User Receives a call, it rings also the Lync Client  then when the User picks the call from his Cisco Phone, a Missed Call notification appears On Lync client and Email is Sent to the User's Inbox.

    any idea how to overcome this Issue ?


    Sunday, December 30, 2012 11:25 AM

Answers

  • Hello,

    Cisco does not end the communication with a Call Answered SIP message in your case, thus Lync is right when it log it as a "missed call".

    Here is some proposition you have to overcome this problem:

    1. Configure the integration as an RCC or RCC only with Cisco, but it should be carefully thought because RCC/RCC Only have only a part of the full lync functionnality/features.
    2. Delay the fork ringing on the CUCM, this will allow user to pick the call before Lync ring.
    3. Disable missed call notification in Lync :(

    It's an old problem without real solution:

    http://social.technet.microsoft.com/Forums/en-US/ocsvoice/thread/58a89af7-c071-4154-80cc-30c9ceb789da

    By the way you would have the exact same problem by interconnecting two PBX of another brand.

    Maybe you can send a call answered to Lync from the CUCM, but i don't know how.


    MCITP: Enterprise Messaging Administrator 2010 MCTS: Lync Server 2010, Configuring MCSE

    • Proposed as answer by Sharon.Shen Monday, December 31, 2012 8:41 AM
    • Marked as answer by Sean_Xiao Monday, January 7, 2013 5:35 AM
    Sunday, December 30, 2012 3:24 PM
  • Hi,Fathy

    Per my knowledge it's by design,as Timil said there is no real solution for this.If you are skilled at developping maybe you can have a look at Lync SDK documentation and send an ansewered SIP message to Lync aftr the call is picked up from Cisco client.

    More details about Lync SDK you can check http://msdn.microsoft.com/en-us/library/lync/gg421054(v=office.14).aspx

    Any further question about Lyn SDK you can post it to MSDN UC forum

    Regards,

    Sharon


    Sharon Shen
    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.

    • Marked as answer by Sean_Xiao Monday, January 7, 2013 5:35 AM
    Monday, December 31, 2012 8:50 AM

All replies

  • Hello,

    Cisco does not end the communication with a Call Answered SIP message in your case, thus Lync is right when it log it as a "missed call".

    Here is some proposition you have to overcome this problem:

    1. Configure the integration as an RCC or RCC only with Cisco, but it should be carefully thought because RCC/RCC Only have only a part of the full lync functionnality/features.
    2. Delay the fork ringing on the CUCM, this will allow user to pick the call before Lync ring.
    3. Disable missed call notification in Lync :(

    It's an old problem without real solution:

    http://social.technet.microsoft.com/Forums/en-US/ocsvoice/thread/58a89af7-c071-4154-80cc-30c9ceb789da

    By the way you would have the exact same problem by interconnecting two PBX of another brand.

    Maybe you can send a call answered to Lync from the CUCM, but i don't know how.


    MCITP: Enterprise Messaging Administrator 2010 MCTS: Lync Server 2010, Configuring MCSE

    • Proposed as answer by Sharon.Shen Monday, December 31, 2012 8:41 AM
    • Marked as answer by Sean_Xiao Monday, January 7, 2013 5:35 AM
    Sunday, December 30, 2012 3:24 PM
  • Hi,Fathy

    Per my knowledge it's by design,as Timil said there is no real solution for this.If you are skilled at developping maybe you can have a look at Lync SDK documentation and send an ansewered SIP message to Lync aftr the call is picked up from Cisco client.

    More details about Lync SDK you can check http://msdn.microsoft.com/en-us/library/lync/gg421054(v=office.14).aspx

    Any further question about Lyn SDK you can post it to MSDN UC forum

    Regards,

    Sharon


    Sharon Shen
    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.

    • Marked as answer by Sean_Xiao Monday, January 7, 2013 5:35 AM
    Monday, December 31, 2012 8:50 AM
  • Hi,

    If you wish to avoid undesired Missed Call Notification, the Carrier (or SBC) should add a reason header (RFC 3326) in a CANCEL message, to indicate the reason for the CANCEL message.

    The following reason headers are supported:
    Reason: SIP ;cause=200 ;text="Call completed elsewhere"
    Reason: SIP; cause=181 ;text="Call is being forwarded"  

    Upon receiving a CANCEL message with one of the reasons that are listed above, the Lync client won’t show a missed call notification. 

    Hope that helps.

    AB

    Friday, June 13, 2014 3:17 PM
  • Indeed Lync Server 2013 does not handle a CANCEL with Reason: SIP;cause=200.

    We have a SIP trunk between Lync and Asterisk. Asterisk is correctly sending a CANCEL with the reason above, but Lync is generating a "missed call" email.

    Best regards,

    Fabiano

    Tuesday, July 1, 2014 7:31 PM