locked
SIP/2.0 491 Proxy side reinvite failed, pass result to GW RRS feed

  • Question

  • I have Skype for Business 2015 configured for Call-via-Work. The trunk is direct SIP from the FE pool Cisco Call Manager 8.6.2. Inbound outbound calls work without any problems for EV users. When I turn on Call-via-Work I get the following error:

    SIP/2.0 491 Proxy side reinvite failed, pass result to GW

    My SIP trunk is configured has Media Bypass enabled and REFER support disabled. The same trunks are configured in my lab and they are working correctly. Has anyone run into this and been able to fix it?

    Thank you

    Monday, October 17, 2016 6:54 PM

All replies

  • If you activate call via work, the mediation server will setup the call to the cisco phone and than call the SFB user.

    You should make a complete clslogging trace and also a trace from the CUCM to look whats happened.

    You can also deactivate media bypass for testing.


    regards Holger Technical Specialist UC

    Tuesday, October 18, 2016 6:45 AM
  • Hi Jeremy_McCarthy,

    Welcome to post in our forum.

    Would you please tell us did the issue only appeared to the specific user?

    If the issue only appeared to the specific user, please try to update your SFB client with the latest update and test again.

    If multiple users have the issue, please check the steps for deploying the call via work, please refer to

    https://technet.microsoft.com/en-us/library/dn933908.aspx

    Please also check if there are any error messages in your Lync FE server

    If there are any questions or issues, please be free to let me know and we will pleasure to help you. If the above suggestions are helpful to you, please mark it as answer so that someone who has similar issue could find this thread as soon as possible.


    Alice Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 18, 2016 8:01 AM
  • Hi Jeremy, 

    Call Via work will first trigger to the connected PBX , so as Holger suggested could you take the logs and see if you find any issue 


    Linus || Please mark posts as answers/helpful if it answers your question.

    Tuesday, October 18, 2016 1:21 PM
  • Thank you for the response. I have run a cslogger trace on the FE pool and grabbed the logs from CUCM. The SIP message that I originally posted is originated on the FE server. The initial INVITE is accepted by CUCM and then the FE sends the REFER, which is accepted by CUCM. CUCM sends a NOTIFY and the FE sends OK and TRYING back to CUCM. CUCM then sends an INVITE, to which FE sends Proxy side reinvite failed, pass result to GW. CUCM Acknowledges that and the FE sends a BYE.

    Both the cslogger and the capture from CUCM show the same series of events.

    Wednesday, October 19, 2016 8:16 PM
  • Hi Jeremy_McCarthy,

    Thanks for your response.

    Would you please tell us did you check the deployment process of call via work?

    Regarding your issue, please try to check whether the call via work global policy is enabled in your environment.

    For details, please refer to

    http://masteringlync.com/2015/05/01/call-via-work/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Alice Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 25, 2016 1:24 AM
  • Hello Alice,

    The Global call via work policy is not enabled on my system. I have a specific policy configured for assigning to users. I have this same configuration set up on my UAT system, which is working correctly. 

    Thank you


    Monday, October 31, 2016 2:36 PM
  • Hi Jeremy,

    Would you please tell us did you try the method that disable media bypass?


    Alice Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, November 3, 2016 6:39 AM
  • Yes, I have tried disabling media bypass and got the same error. From the Snooper logs it appears that the UCWA is the party that is responsible for sending the 491 SIP message, which terminates the call. 
    Thursday, November 3, 2016 12:54 PM
  •   Emm, you could log a case to Microsoft support.
    Monday, November 7, 2016 9:37 AM