locked
Inbound call from PSTN, "Calling number" normalization on Lync RRS feed

  • Question

  • I should know this but...

    For an inbound call from the PSTN, the called number is being normalized fine via a site based dial plan

    However the calling number is not normalizing correctly. ie toast shows the number corectly but the missed call notification shows the un-normalized number.

    eg PSTN is presenting number as 208 998 xxx. It should be normalized to +44 208 998 xxx

    Missed call notification states call missed from 208 998 xxx

    Regards


    Alistair

    Monday, February 13, 2012 5:02 PM

Answers

  • Hello,

    Do you have Exchange UM in your environment or just Lync. If you have just Lync the missed call is generated by Lync, you can verify this by looking at the missed call notification and at the bottom of the email you will see: "microsoft Lync 2010"

    Now when you get an inbound call, the gateway sends a sip invite with the From header which has the caller number. Once the sip invite reaches the Mediation server and then to Front End (FE), the FE normalizes the number in the To header and the number in the From Header in the sip invite but does not change the From Header or To Header in the sip invite, but adds the normalized From number in the P-Asserted-Identity Field of the sip invite which is sent to the communicator client. Once the caller disconnects the communicator will generate the missed call notification, which will show the normalized number.

    If you have Exchagne UM,and the Lync user is enabled for UM,  UM is responsible for generating the missed call notification and you will see  "sent by microsoft exchange" at the bottom of the missed call notification

    Now once the caller disconnects, a sip info packet is sent by lync server to Exchange UM with the caller number and this contains the number from the From Header of the sip invite, which is not normalized number.


    If you are in doubt you can take following logs from the Lync server sipstack,s4, mediationserver
    Trace the call and it will answer your question

    More information here http://blogs.technet.com/b/jenstr/archive/2008/05/29/missed-called-notifications.aspx

    • Proposed as answer by Sean_Xiao Tuesday, February 21, 2012 2:53 AM
    • Marked as answer by Sean_Xiao Thursday, February 23, 2012 1:34 AM
    Thursday, February 16, 2012 11:41 AM

All replies

  • I should know this but...

    For an inbound call from the PSTN, the called number is being normalized fine via a site based dial plan

    However the calling number is not normalizing correctly. ie toast shows the number corectly but the missed call notification shows the un-normalized number.

    eg PSTN is presenting number as 208 998 xxx. It should be normalized to +44 208 998 xxx

    Missed call notification states call missed from 208 998 xxx

    Regards


    Alistair

    • Merged by Sean_Xiao Wednesday, February 15, 2012 8:08 AM
    Monday, February 13, 2012 5:02 PM
  • The same dial plan rules apply to inbound and outbound numbers have you created a rule to normalise 208 998 xxx?

    Chris Clark - | MCTS:OCS & UC Voice Specialization | MCSE | MCSA | CCNA http://www.unitycomms.com

    Monday, February 13, 2012 6:52 PM
  • Monday, February 13, 2012 7:33 PM
  • As far as I know, Lync Server cannot normalize a calling number (Caller's ID). I recommend to check whether a voice gateway can do it.

    Regards,


    Yutaka

    Monday, February 13, 2012 10:14 PM
  • Hello,

    Do you have Exchange UM in your environment or just Lync. If you have just Lync the missed call is generated by Lync, you can verify this by looking at the missed call notification and at the bottom of the email you will see: "microsoft Lync 2010"

    Now when you get an inbound call, the gateway sends a sip invite with the From header which has the caller number. Once the sip invite reaches the Mediation server and then to Front End (FE), the FE normalizes the number in the To header and the number in the From Header in the sip invite but does not change the From Header or To Header in the sip invite, but adds the normalized From number in the P-Asserted-Identity Field of the sip invite which is sent to the communicator client. Once the caller disconnects the communicator will generate the missed call notification, which will show the normalized number.

    If you have Exchagne UM,and the Lync user is enabled for UM,  UM is responsible for generating the missed call notification and you will see  "sent by microsoft exchange" at the bottom of the missed call notification

    Now once the caller disconnects, a sip info packet is sent by lync server to Exchange UM with the caller number and this contains the number from the From Header of the sip invite, which is not normalized number.


    If you are in doubt you can take following logs from the Lync server sipstack,s4, mediationserver
    Trace the call and it will answer your question

    More information here http://blogs.technet.com/b/jenstr/archive/2008/05/29/missed-called-notifications.aspx

    • Proposed as answer by Sean_Xiao Tuesday, February 21, 2012 2:53 AM
    • Marked as answer by Sean_Xiao Thursday, February 23, 2012 1:34 AM
    Thursday, February 16, 2012 11:41 AM
  • To add to my previous reply, you can configure the gateway to send the normalized From Header and that should fix the issue
    Friday, February 17, 2012 6:11 AM