locked
Lync Call Forwarding & Simultaneously Ring does not work due to Lync preserving original caller ID RRS feed

  • Question

  • Format:
    A calls B to forward to C

    The SIP Trunking provider is reporting a 604 not found because Lync is preserving the original caller's (A in this case) number as the FROM address, and since that number is not on their network, the call is dropped.  They recommended putting in a SIP diversion header or configure Lync to use B's number as the caller ID instead of A.  I tried enabling REFER support and also suppressing the caller ID number for an alternative DID number that is on their network, but neither worked.  Is a SIP diversion header suppose on the Lync platform?

    Tuesday, December 27, 2011 2:47 PM

Answers

  • Problem resolved, provider's Acme Packet had some invalid strings that prevent forwarding and simultaneous ring from working.  Provider also put in a SIP diversion header on their end to resolve the number not on their network issue when call forwarding is enabled.
    • Marked as answer by Solignis Wednesday, January 4, 2012 4:09 PM
    Wednesday, January 4, 2012 4:09 PM

All replies

  • Which Lync server patchlevel do you use. In Lync CU4 the passerted identiy information can be configured. May be this will hellp.

    Here is described how to configure the mediation server to send the reffered-by Information.

    http://support.microsoft.com/kb/2500421


    regards Holger Technical Specialist UC
    Tuesday, December 27, 2011 3:11 PM
  • I run CU4 since that is mandatory for Lync Mobile.

    I forgot to mention, but I did see a blog regarding KB2500421 and adding the following config into the mediation configuration file; however the mediation service fails to start with the below added.  I figured it was no longer compatible with CU4.

    <appSettings>
                    <add key="<var style="font-family: 'Segoe UI', Arial, Verdana, Tahoma, sans-serif; font-size: 11px; line-height: 16px; text-align: left;"><FQDN or IP address of the PSTN gateway></var>.ReferredBySupported" value="true"/>
        </appSettings>

    Tuesday, December 27, 2011 3:20 PM
  • The change works with CU4 are you sure you haven't made a mistake entering the change?
    Chris Clark - | MCTS:OCS & UC Voice Specialization | MCSE | MCSA | CCNA http://www.unitycomms.com
    Tuesday, December 27, 2011 4:32 PM
  • Same in my Lab enviroment the changing of the configuration file works in my lab. be sure you dont change the file format of the config file.
    regards Holger Technical Specialist UC
    Tuesday, December 27, 2011 4:43 PM
  • Thanks Chris & Holger, I checked the code syntax again and mediation service was able to start afterwards, but didn't seem to fix the original issue.  Calls made to Lync client user are either returning invalid number message or instant disconnect.
    • Edited by Solignis Tuesday, December 27, 2011 6:39 PM
    Tuesday, December 27, 2011 6:38 PM
  • Hi Johnny,

    here is the doc for direct sip

    http://www.microsoft.com/download/en/details.aspx?id=22644

    You can also check the trafic with wireshark and the ocsloggertool to trace the Lync mediationserver traffic. The log can be read with the snooper.exe from the Lync reskit


    regards Holger Technical Specialist UC
    Tuesday, December 27, 2011 7:21 PM
  • The change doesn't fix the problem unless your trunking provider supports it. Mine modified their code of their SBC to support it. If you use an approved provider then it should work anyway.
    Chris Clark - | MCTS:OCS & UC Voice Specialization | MCSE | MCSA | CCNA http://www.unitycomms.com
    Tuesday, December 27, 2011 7:27 PM
  • Hello Chris,

    We use Level3 Sip Trunking which is a UCOIP provider for Lync.  They told me that there is nothing else they can do on their end, which sounds pretty skeptical.  The only solution they provided for me is to either create a SIP diversion header or make Lync advertise the middle party's number instead of the original caller's number.

    Tuesday, December 27, 2011 7:40 PM
  • I also want to add that call forwarding and simultaneously ring doesn't work when trying to forward the call to a PSTN or cell number; however, when forwarding to a DID number on another SIP trunk, it does work.
    Tuesday, December 27, 2011 8:02 PM
  • Sounds like you answered your own question if it works for other SIP trunks but not the Level 3 then it must be their issue. It seems like a lot of providers they have very few people that understand the Microsoft integration. Might be worth escalating with them.


    Chris Clark - | MCTS:OCS & UC Voice Specialization | MCSE | MCSA | CCNA http://www.unitycomms.com
    Tuesday, December 27, 2011 8:24 PM
  • Problem resolved, provider's Acme Packet had some invalid strings that prevent forwarding and simultaneous ring from working.  Provider also put in a SIP diversion header on their end to resolve the number not on their network issue when call forwarding is enabled.
    • Marked as answer by Solignis Wednesday, January 4, 2012 4:09 PM
    Wednesday, January 4, 2012 4:09 PM
  • Johnnyc3,

     

    We also have Level 3 and I have been having the same issue.  Would you mind contacting me at pross@hyphensolutions.com with a ticket # you placed with them so I can refer to it on my ticket I am putting in?  I would truly appreciate it!!!

     

    Paul

    Thursday, January 26, 2012 9:36 PM
  • Very useful article!! Glad MS has a solution for this as we cannot bill calls to users without this.

    Andrew

    Friday, February 17, 2012 8:14 PM
  • Can you also send me Level 3 ticket # as we are having same issue with Level 3..  Raymond.Feliciano@ipc.com

    Thanks!!

    Wednesday, April 24, 2013 10:09 PM
  • Hi RayFel,

    I do not have a ticket # with the Level3 as I was working our customer care rep and their tech directly via email.  In the end, it took a Microsoft engineer, two Level 3 technicians and myself on the same conference for one of the Level 3 techs to realize that there was an improper formatted string on their Acme Packet SBC that prevented Lync call forwarding and simultaneous ring from working properly.  I know it's pretty vague but L3 usually don't provide any other information other than the normal traces.  On the other hand, we have been pretty solid for 2 years running following this fiasco and have recently migrated to 2013 without a hitch.


    • Edited by Solignis Thursday, April 25, 2013 9:15 PM
    Thursday, April 25, 2013 9:13 PM