Default setting of supporting SIP REFER and using an unsupported gateway with LYNC 2010

I recently worked an issue where the default setting of “Enable refer support” caused a routing failure with an Enterprise Voice scenario.  The customer is configured with a direct SIP trunk from their ISP that’s pointed to their Lync Mediation role.  In this scenario, an inbound call from an external PSTN user hits the Exchange Unified Messaging 2010 (EUM) Auto Attendant (AA).  The EUM AA was configured with a Lync Dial Plan.  When the AA tried to connect the inbound caller to the Lync enabled internal user by the SIP REFER method, it failed to connect.


SIP Stack tracing from the Mediation Server logged the following SIP error:

SIP /2.0 400 Refer-To: user name not found


When reviewing a network capture from the Lync client, the VoIP call graph analysis showed the following:

|30.916   |         REFER     |                   |SIP Request

|         |(5060)   <------------------  (63788)  |

|30.964   |         400 Refer-To: user name not found          |SIP Status

|         |(5060)   ------------------>  (63788)  |


As stated before, the “Enable refer support” switch is enabled by default.



If you have deployed Lync with Enterprise Voice and utilize a “supported” gateway, SIP REFER works as expected.  However, you are not using a “supported” gateway or have a SIP trunk being provided by a ISP that is not using a “supported” gateway or a gateway that does not support SIP REFER, you will need to disable the default setting for SIP REFER support.  It is recommended that you verify whether or not the SIP trunk provider supports SIP REFER.

Comments (4)

  1. alex says:

    I have exactly this issue – call cannot be transferred to Operator when pressing "0" if the caller is outside Lync. If the caller is Lync user – no problem, call transfer works. But if the caller is PSTN or PBX user (i.e. not a Lync user) – call transfer using extensions does not work. Both Media Bypass and Refer support are disabled in Lync. Is it possible that Exchange is trying to do REFER when transferring call? Can this be disabled as well? My SIP Trunking provider does not support REFER. Thanks!

  2. Ben says:

    I would check your dial plan to make sure that the Gateway understands how to normalize "0".

    @ Wes – this fixed my issue, not sure why I was so focused on making refer work when disabling it fixes the issue!!!!

    If it hurts, dont do it.


  3. Wes B says:

    This fixed my issue. Thanks for posting this I have been struggling for a week with this.

  4. Johnny D says:

    I've seen where  REFER was already disabled, but it still didn't work. I had to enable it and commit, then disable and commit again. Then is started working. Must have been a stale SQL record or something.

Skip to main content