none
Call forwarding not working for external mobile number RRS feed

  • Question

  • Hi 

    I have set up the call forwarding to external mobile number and it is failing with ms-diagnostics: 13008;reason="Diagnostic headers removed for privacy.";source=;appName="InboundRouting"

    i saw 2 error message in snooper

    1. SIP/2.0 199 Early Dialog Terminated

    2. ms-diagnostics: 13008;reason="Diagnostic headers removed for privacy.";source="";appName="InboundRouting"

    can someone pls advise what might be the issue. Thanks in advance. 

    Wednesday, September 5, 2018 10:02 AM

Answers

All replies

  • Hi Michelle_May,

    Could you upload all the logs about this issue in Snppoer?

    According to the information you provided, I want to confirm with you about the questions below: Did this issue only occur on the specific client or specific user?
    If this issue only occur to the specific client, you could try to update the client to the latest version, you could download the latest version from the following link:
    https://technet.microsoft.com/en-us/office/dn788954?f=255&MSPPError=-2147217396 
    If most of users have this issue, you could check the ports in the SFB Server, details you could refer to the following document:
    https://technet.microsoft.com/en-us/library/gg398798%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396 
    In addition, you could try to check whether the Call is reaching to your gateway from mediation server and your gateway has accepted the call. You could contact your gateway vendor to check this.

    Best Regard,
    Evan

    • Marked as answer by Michelle_May Wednesday, September 12, 2018 5:46 AM
    Thursday, September 6, 2018 2:51 AM
    Moderator
  • Agree with Evan...

    Also I would ask you to check if the affected user have the Call forwarding capability, you may run the below command to check the same for the affected user.

    Get-CsUser -Identity "sip:User@domain.com" | Select-Object SamAccount, SipAddress,@{Name='AllowCallForwarding';Expression={[String]::join(";",(Get-CsVoicePolicy –identity $_.voicepolicy.FriendlyName). AllowCallForwarding)}} 
    


    Neeranjan Shettar (MyPage)

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Thursday, September 6, 2018 6:51 AM
  • Hi Evan, 

    Thanks for your reply and time. Kindly see my reply below. 

    May be i should explain the whole Lync infra. 

    I have main FE pool with SBC01  (singapore). i also have branches site with (SBA02 and SBC02) in Korea.

    I tested below situation

    1. SBA Lync account forward to SG mobile number using SBC01 - OK

    2. SBA Lync account forward to Korea mobile number using SBC02 - not working. 

    3. FE Lync account forward to Korea mobile number using SBC01 - not working. 

    4. FE Lync account forward to SG mobile number using SBC01 - working. 

    5. When i make direct call to that Korea mobile number using SBC01 and SBC02. Both are working. 

    The issue is call forwarding to Korea mobile number is not working whether i am use SBC01 or SBC02. 

    Could you upload all the logs about this issue in Snppoer?

    09/06/2018|15:56:57.914 2EA8:1650 INFO  :: Data Received -10.2.18.111:5061 (To Local Address: 10.2.12.45:64767) 681 bytes:
    09/06/2018|15:56:57.914 2EA8:1650 INFO  :: 
    SIP/2.0 199 Early Dialog Terminated
    Authentication-Info: TLS-DSK qop="auth", opaque="567E1715", srand="CE6608BA", snum="65", rspauth="9fae6d21dc9647d7c60a213dfb87e5fc9f83f0d9", targetname="servername.domain.com", realm="SIP Communications Service", version=4
    Content-Length: 0
    Via: SIP/2.0/TLS 10.2.12.45:64767;ms-received-port=64767;ms-received-cid=C540500
    From: "user1"<sip:user1@domain.com>;tag=5fcbac3926;epid=22cfb25e25
    Call-ID: 7c4298f932934c589036cd962d3c4339
    CSeq: 1 INVITE
    To: <sip:test3@domain.com>;tag=617297e8c8
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting(Microsoft Lync Server 2013 5.0.8308.872)

    09/06/2018|15:56:57.914 2EA8:1650 INFO  :: End of Data Received -10.2.18.111:5061 (To Local Address: 10.2.12.45:64767) 681 bytes

    --------------------------------------------

    09/06/2018|15:56:58.026 2EA8:1650 INFO  :: Data Received -10.2.18.111:5061 (To Local Address: 10.2.12.45:64767) 1021 bytes:
    09/06/2018|15:56:58.026 2EA8:1650 INFO  :: 
    SIP/2.0 404 Not Found
    Authentication-Info: TLS-DSK qop="auth", opaque="567E1715", srand="DD4906EE", snum="66", rspauth="2cd1d4d12ea479320124247295318b438bd401be", targetname="servername.domain.com", realm="SIP Communications Service", version=4
    Via: SIP/2.0/TLS 10.2.12.45:64767;ms-received-port=64767;ms-received-cid=C540500
    CONTENT-LENGTH: 0
    From: "User1"<sip:user1@domain.com>;tag=5fcbac3926;epid=22cfb25e25
    To: <sip:test3@domain.com>;tag=617297e8c8;epid=EDBAC5EC48
    CSeq: 1 INVITE
    Call-ID: 7c4298f932934c589036cd962d3c4339
    P-Asserted-Identity: <sip:+821032458xxx@domain.com;user=phone>
    Server: RTCC/5.0.0.0 MediationServer
    ms-trunking-peer: sonus01.domain.com;trunk=sonus01.domain.com;User-Agent="SONUS SBC1000 4.0.0v353 Sonus SBC"
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    ms-diagnostics: 13008;reason="Diagnostic headers removed for privacy.";source="SBA01.DOMAIN.COM";appName="InboundRouting"

    09/06/2018|15:56:58.026 2EA8:1650 INFO  :: End of Data Received -10.2.18.111:5061 (To Local Address: 10.2.12.45:64767) 1021 bytes

    -------------------------------------------

    According to the information you provided, I want to confirm with you about the questions below: Did this issue only occur on the specific client or specific user?

    Me: The issue is happening to all SBA user.


    In addition, you could try to check whether the Call is reaching to your gateway from mediation server and your gateway has accepted the call. You could contact your gateway vendor to check this.

    Me: I checked live monitoring screen in sonus gateway and the call is not touching the gateway. I don't see purple color touch in gateway. Any dial plan i need to add in Lync and sbc for call forwarding. 

    Unfortunately, they don't have vendor support and only hardware maintenance.   

    The below is the result when i run the cmd.

    PS C:\Users\username> Get-CsUser -Identity "sip:user1@domain.com " | Select-Object SamAccount, SipAddress,@{Name='AllowCallForwarding';Expression
    ={[String]::join(";",(Get-CsVoicePolicy -identity $_.voicepolicy.FriendlyName).
    AllowCallForwarding)}}

    SamAccount SipAddress                         AllowCallForwarding
    ---------- ----------                         -------------------
               sip:user1@domain.com True


    PS C:\Users\username> Get-CsUser -Identity "sip:test3@domain.com" | Select-Object SamAccount, SipAddress,@{Name='AllowCallForwarding';Express
    ion={[String]::join(";",(Get-CsVoicePolicy -identity $_.voicepolicy.FriendlyName
    ). AllowCallForwarding)}}

    SamAccount SipAddress                            AllowCallForwarding
    ---------- ----------                            -------------------
               sip:test3@domain.com True

    Once again, Thanks for help. 



    • Edited by Michelle_May Thursday, September 6, 2018 8:19 AM
    Thursday, September 6, 2018 8:18 AM
  • Hi Michelle_May,

    I checked the logs you provided, and I could not find the reason why this issue occurred from it. 
    The information about ms-diagnostics: 13008;reason="Diagnostic headers removed for privacy.";source="";appName="InboundRouting" and SIP/2.0 199 Early Dialog Terminated in the log did not show the reasons. You could find more details from the following link:
    https://lyncforbusiness.wordpress.com/2015/10/15/lync-diagnostic-codes/ 

    About this case, I suggest you could try to use ClsLogger to collect logs with the components S4 and SipStack from mediation server check about this issue.

    Best Regard,
    Evan

    Friday, September 7, 2018 8:57 AM
    Moderator
  • Hi Michelle_May,

    Is there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who have the similar issue.

    Best Regard,
    Evan
    • Marked as answer by Michelle_May Wednesday, September 12, 2018 4:35 AM
    Monday, September 10, 2018 7:55 AM
    Moderator
  • Hi Evan, 

    Let me try on that and update you again. Thanks.

    Monday, September 10, 2018 8:19 AM
  • Hi Evan, 

    it is working now after i changed the called transformation rules in SBC. 

    But the user is receiving anonymous caller in their mobile phone. Which setting should I take a look for that issue?

    Thank you. 

    Wednesday, September 12, 2018 5:46 AM
  • Hi Michelle_May,

    About the caller ID shows as Anonymous call, I found a similar case you could refer to:
    https://social.technet.microsoft.com/Forums/lync/en-US/45ab6495-fc3d-41fa-adb0-8b10c61f8cd4/caller-id-shows-anonymous-call?forum=ocsucintegration 

    Best Regard,
    Evan
    • Marked as answer by Michelle_May Monday, September 17, 2018 9:08 AM
    Thursday, September 13, 2018 8:00 AM
    Moderator