locked
Caller ID for Dialin Conferencing RRS feed

  • Question

  • We have a Standard Front End server with and Edge server for outside presence. We just deployed the PSTN to talk to our Lync system. We are using Asterisk for a voice system and Trixbox to handle the conversion from UDP to TCP. We would move all to Trixbox, but that is another story. We have the dial in conferencing working along with the phone features of Lync, but we have noticed that the Caller ID is not working for dial in conference calls. It works just fine for inside and outside direct dial calls, but not the conference calls. It just leaves Unknown next to each caller who dials in. We tested the same numbers to dial direct into a single URI and not the conference number, and it shows the number and possible name. Is there a way to turn this feature on for conference calls? We did not see a separate policy or config for setting that option to be on. If anyone has any information about this,  please let me know. Thank you.

     

    Wednesday, January 18, 2012 2:27 PM

Answers

  • Yes it is the same sip trunk. We used the logging tools and saw the Caller ID making it to the Lync Front End. So, when we had the time over a weekend, we rebooted all the systems just to start fresh, and it started to work. I guess it just needed a kick in the butt. Thank you for all the great feedback.
    • Marked as answer by Noya Lau Tuesday, February 7, 2012 8:57 AM
    Friday, February 3, 2012 4:30 PM

All replies

  • Hi,

    Probably the problem does not originate in Lync but originates in the Tribox or Asterix may be the problem.
    Lync does normally show all this information...

    You can use the OCSLogger.exe to get more on info on the SIP Messages sent to the MCU (on Front-End) or Mediation Server. The use snooper.exe (Resource Kit Lync) to look at the logs

    Grts,
    Johan


    - Belgian Unified Communications Community : http://www.pro-lync.be -
    • Proposed as answer by Noya Lau Wednesday, February 1, 2012 6:44 AM
    • Marked as answer by Noya Lau Friday, February 3, 2012 12:47 PM
    • Unmarked as answer by jisenberg Friday, February 3, 2012 3:59 PM
    Thursday, January 19, 2012 1:06 AM
  • Hi jisenberg,

    Agree with Johan.

    The Caller ID Controls feature controls the phone number that is displayed to called party. The enterprise administrator can choose to suppress caller ID per route by providing an alternative number. The alternative number will be displayed as the caller ID for all the calls going out through that route. An example for this would be when an end user makes a call from their personal work phone number, the called party will see the general company number instead of the user’s personal work number.


    Noya Liu

    TechNet Community Support

    Monday, January 23, 2012 6:20 AM
  • Are all the lines in the same SIP trunk or ISDN30 bundle?? If not it could also be blocked at a network level.
    Monday, January 30, 2012 4:44 PM
  • Yes it is the same sip trunk. We used the logging tools and saw the Caller ID making it to the Lync Front End. So, when we had the time over a weekend, we rebooted all the systems just to start fresh, and it started to work. I guess it just needed a kick in the butt. Thank you for all the great feedback.
    • Marked as answer by Noya Lau Tuesday, February 7, 2012 8:57 AM
    Friday, February 3, 2012 4:30 PM