locked
Inbound Calls from Cell with Blocked Caller ID not Working RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Nortel CS1000, Audiocodes Mediant 1000, Lync 2010 CU2, f5 load balancer (for Edge, Mediation, Front End, and Director pools)

    We have an instance where someone outside has a cell phone with a blocked caller ID that cannot call any number in Lync yet we can call out to that phone fine and they can call into any non-Lync phone.  They get a number is not in service message when trying to call any Lync number.

    Below is what we see in the log on the Mediation server.  1234 represents the internal extension being called.  LyncVoice is the IP group name in the Mediant 1000 for Lync.  192.168.10.2 represents the IP address of the gateway.  In our topology we do have the gateways entered using their DNS names, not IP addresses but that has not been a problem for any other calls (I've seen that mentioned in other posts).

     

    TL_INFO(TF_COMPONENT) [9]0BE8.0ED4::08/09/2011-20:05:29.512.00000799 (MediationServer,GatewayListener.GatewaySessionReceivedEventHandler:gatewaylistener.cs(566))(00000000005D06D4)$$START-MEDIATIONSERVER
    MediationCall: 7e5d28a0-5540-49f5-90eb-29ae8367268c
    CallId: 132728793798201115529@192.168.10.2
    From: sip:anonymous@anonymous.invalid
    To: sip:1234@LyncVoice;user=phone
    Direction: Inbound
    Start-Line: Received new Gateway incoming session with requestUri: sip:1234@LyncVoice;user=phone
    $$END-MEDIATIONSERVER
    TL_INFO(TF_COMPONENT) [9]0BE8.0ED4::08/09/2011-20:05:29.514.0000079f (MediationServer,GatewayListener.GatewaySessionReceivedEventHandler:gatewaylistener.cs(568))[1][0]->[4417893]$$START-MEDIATIONSERVER
    MediationCall: 7e5d28a0-5540-49f5-90eb-29ae8367268c
    CallId: 132728793798201115529@192.168.10.2
    From: sip:anonymous@anonymous.invalid
    To: sip:1234@LyncVoice;user=phone
    Direction: Inbound
    Start-Line: Mapping GatewayListener to incoming session
    $$END-MEDIATIONSERVER
    TL_INFO(TF_COMPONENT) [9]0BE8.0ED4::08/09/2011-20:05:29.517.000007a2 (MediationServer,SessionCommon.SendInboundErrorCerReport:sessioncommon.cs(1301))$$START-MEDIATIONSERVER
    MediationCall: c7ffddf4-a9ff-425b-ac9c-28c77560cae2
    CallId: 132728793798201115529@192.168.10.2
    From: sip:anonymous@anonymous.invalid
    To: sip:1234@LyncVoice;user=phone
    Direction: Inbound
    Start-Line: There was an inbound call error, sending a CER
    $$END-MEDIATIONSERVER
    TL_INFO(TF_COMPONENT) [9]0BE8.0ED4::08/09/2011-20:05:29.517.000007a3 (MediationServer,SessionCommon.ApplyOutgoingRequestURIRules:sessioncommon.cs(1179))$$START-MEDIATIONSERVER
    MediationCall: c7ffddf4-a9ff-425b-ac9c-28c77560cae2
    CallId: 132728793798201115529@192.168.10.2
    From: sip:anonymous@anonymous.invalid
    To: sip:1234@LyncVoice;user=phone
    Direction: Inbound
    Start-Line: Valid phone number for inbound call.
    $$END-MEDIATIONSERVER
    TL_ERROR(TF_COMPONENT) [9]0BE8.0994::08/09/2011-20:05:29.550.0000089c (MediationServer,SendCerResultHandler.OnMsDiagnosticsReporterFailure:sessioncommon.cs(2049))(00000000026CAEF8)$$START-MEDIATIONSERVER
    MediationCall: c7ffddf4-a9ff-425b-ac9c-28c77560cae2
    CallId: 132728793798201115529@192.168.10.2
    From: sip:anonymous@anonymous.invalid
    To: sip:1234@LyncVoice;user=phone
    Direction: Inbound
    Start-Line: Send CER Report Failed. Exception: ResponseCode=404 ResponseText=Not Found
    DiagnosticInformation=ErrorCode=1003,Source=accessedge.company.com,Reason=User does not exist
    Microsoft.Rtc.Signaling.DiagnosticHeader
    Microsoft.Rtc.Signaling.FailureResponseException:A 404 (Not Found) response was received from the network and the operation failed. See the exception details for more information.
       at Microsoft.Rtc.Signaling.SipAsyncResult2`1.ThrowIfFailed()
       at Microsoft.Rtc.Signaling.SipAsyncResultBase2.EndAsyncOperation[TResult](Object owner, IAsyncResult result)
       at Microsoft.Rtc.Signaling.RealTimeEndpoint.EndSendMessage(IAsyncResult result)
       at Microsoft.Rtc.Internal.MsDiagnosticsReporterBase.SendMessageCallback(IAsyncResult ar)
    Detected at System.Environment.get_StackTrace()
       at Microsoft.Rtc.Signaling.FailureResponseException..ctor(String message, Exception innerException, SipResponseData responseData)
       at Microsoft.Rtc.Signaling.RealTimeException.GetWrappedRealTimeException(String message, SipResponseData responseData, Exception exceptionToWrap)
       at Microsoft.Rtc.Signaling.SipTransactionAsyncResult`1.ProcessFailureResponse(SipResponse response)
       at Microsoft.Rtc.Signaling.SipMessageAsyncResult.ProcessFailureResponse(SipResponse response)
       at Microsoft.Rtc.Signaling.SipTransactionAsyncResult`1.Transaction_ResponseReceived(Object sender, ResponseReceivedEventArgs e)
       at Microsoft.Rtc.Internal.Sip.OutgoingNonInviteTransaction.OnResponseReceived(EventArgs e)
       at Microsoft.Rtc.Internal.Sip.SingleThreadedDispatcherQueue.DispatcherCallback(Object queue)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
    $$END-MEDIATIONSERVER
    TL_INFO(TF_COMPONENT) [9]0BE8.0994::08/09/2011-20:05:29.550.0000089d (MediationServer,SendCerResultHandler.OnMsDiagnosticsReporterFailure:sessioncommon.cs(2061))(00000000026CAEF8)$$START-MEDIATIONSERVER
    MediationCall: c7ffddf4-a9ff-425b-ac9c-28c77560cae2
    CallId: 132728793798201115529@192.168.10.2
    From: sip:anonymous@anonymous.invalid
    To: sip:1234@LyncVoice;user=phone
    Direction: Inbound
    Start-Line: Response Code of 404 received. MS will retry CER with MS Gruu in the From header.
    $$END-MEDIATIONSERVER
    TL_INFO(TF_COMPONENT) [9]0BE8.0ED4::08/09/2011-20:05:29.555.00000940 (MediationServer,SendCerResultHandler.OnMsDiagnosticsReporterSuccess:sessioncommon.cs(2080))(00000000026CAEF8)$$START-MEDIATIONSERVER
    MediationCall: c7ffddf4-a9ff-425b-ac9c-28c77560cae2
    CallId: 132728793798201115529@192.168.10.2
    From: sip:anonymous@anonymous.invalid
    To: sip:1234@LyncVoice;user=phone
    Direction: Inbound
    Start-Line: Send CER Report Succeeded.
    $$END-MEDIATIONSERVER


    I also have logs from the gateway that I will try to consolidate and post.  Those might be more helpful.  Of course what we are trying to determine is where the call is being dropped and why.

    Thank you.



    Wednesday, August 10, 2011 2:06 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    When a call comes in from the PSTN with just anonymous for the FROM line

    29d:10h:35m:33s INVITE sip:+19528926910@10.10.10.1;user=phone SIP/2.0
    Via: SIP/2.0/TCP 10.0.1.3:5068;branch=z9hG4bKac1354670853;alias
    Max-Forwards: 70
    From: "anonymous" ;tag=1c1354636487

    Lync rejects the call and the caller hears a fast busy.  To resolve the issue you need to replace the anonymous From line with a valid number.  I chose to have 9525551212 as the valid number for blocked calls.  In order to replace the number you will need to modify the Source Number Tel->IP Manipulation Table on the gateway (Protocol Configuration – Manipulation Tables – Source Number Tel->IP).  The Source Prefix that you will be modifying comes from the phone number that you have assigned to your Trunk Groups (Configuration – Protocol Configuration – Trunk Group – Trunk Group). In my case the numbers are 1100, 1200, 1300 & 1400.  You need to make sure that you include all the numbers that can be used.  In my case each one is a PRI so that means that the numbers are 1100-1122 ect. 

    In the manipulation table (Source Number Tel->IP) you need to create a rule for each set of numbers.  Destination Prefix will be an asterisk (*) since you want this to affect all incoming numbers.  Source Prefix are the numbers that you want it to change.  In my case I put in 11[00-22] for the first rule, 12[00-22] for the second and so on.  This will only affect the numbers 1100-1122 ect.  Leave both Stripped digits columns set to 0 and change the “Prefix to Add” to the number that you want displayed on the Lync client for blocked calls.  I chose +19525551212.  Leave “Suffix to Add” blank, “Number of Digits to Leave” to 0 and set “Presentation to Allowed.  Make sure that you save the changes.


    in addition you will need to change one INI file setting.  Go to the IP address of the gateway /AdminPage (Example: http://10.10.10.1/AdminPage).  On the left Click on “ini Parameters”.  In the Parameter Name field put in     USESOURCENUMBERASDISPLAYNAME and click on the Apply New Value button.  In the output window you should see that the current value is 0.  You will want to change this to 1 by putting a 1 in the Enter Value box and clicking on the Apply New Value button. 


    Burn the configuration to the gateway and you will be able to receive blocked calls from the PSTN to Lync DIDs.

     

    Hope this helps.

    • Proposed as answer by jyoungjr Tuesday, August 16, 2011 5:30 PM
    • Marked as answer by Sharon.Shen Friday, August 19, 2011 1:16 AM
    Thursday, August 11, 2011 9:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    FYI

    If you don't need to present a number another option is to set the ANONYMOUSMODE value in the INI file to 1.  This will let the call through but in Lync you will see it as "Anonymous Caller".  So it is depends on how you want to see that presented.

    They really should handle anonymous calls better in Lync though...

    • Marked as answer by MacGeever Friday, August 19, 2011 11:35 PM
    Friday, August 19, 2011 11:32 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I was quite curious about this one so I tried calling from a blocked cell number to a Lync DID and got the same results.  I am going to see if I can track this down as well.  Very interesting.
    Wednesday, August 10, 2011 4:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Wow, that is interesting.  Thanks for giving it a try.

    After reviewing the logs further it does appear Lync (Mediation) is rejecting the call (see the message captured from the gateway below).  After this the call is disconnected.

    Note: 192.168.20.4 represents the VIP of our Mediation server pool on the f5.  All other values match what I pointed out in the log above.

     

    15:05:29.926 : 192.168.10.2 : Local 0   :NOTICE  : (      lgr_flow)(12306353  )  ---- Incoming SIP Message from 192.168.20.4:5067 to SIPInterface #0 ---- [Time: 15:05:29]
    15:05:29.926 : 192.168.10.2 : Local 0   :NOTICE  : SIP/2.0 488 Not Acceptable Here
                                                  FROM: "anonymous"<sip:anonymous@anonymous.invalid>;tag=1c1327289756
                                                  TO: <sip:1234@LyncVoice;user=phone>;epid=76CA76B31B;tag=75d4d788f6
                                                  CSEQ: 1 INVITE
                                                  CALL-ID: 132728793798201115529@192.168.10.2
                                                  VIA: SIP/2.0/TCP 192.168.10.2;branch=z9hG4bKac1327308899;alias
                                                  CONTENT-LENGTH: 0
                                                  SERVER: RTCC/4.0.0.0 MediationServer
                                                   [Time: 15:05:29]

     

    Thanks again.


    Wednesday, August 10, 2011 5:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The call is being rejected in Lync because the FROM: "anonymous" line is not correct.  I am looking at how to modify the gateway (I run audiocodes as well) to resolve the issue.  I should be able to take any call that is blocked and add in a number so it will work.  I will let you know once I have it figured out.
    Wednesday, August 10, 2011 5:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I was looking at the possibility of using a manipulation as well but am not nearly as versed at that in AudioCodes as I am at using transformations in Lync.  I will be curious to see your solution but will educate myself on using those as well.

    The trouble I see is there really isn't anything wrong with the source number but I'm not sure how to manipulate that part of the SIP message to correct the "anonymous" FROM value.

    Thanks again.



    Wednesday, August 10, 2011 5:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I find it odd that Lync would not accept anonymous@anonymous.invalid.  Isn't that the standard way (or at least one way) to represent a number in SIP that is blocking the caller ID?  Can anyone verify or clarify that?

    Thanks.


    Thursday, August 11, 2011 7:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    When a call comes in from the PSTN with just anonymous for the FROM line

    29d:10h:35m:33s INVITE sip:+19528926910@10.10.10.1;user=phone SIP/2.0
    Via: SIP/2.0/TCP 10.0.1.3:5068;branch=z9hG4bKac1354670853;alias
    Max-Forwards: 70
    From: "anonymous" ;tag=1c1354636487

    Lync rejects the call and the caller hears a fast busy.  To resolve the issue you need to replace the anonymous From line with a valid number.  I chose to have 9525551212 as the valid number for blocked calls.  In order to replace the number you will need to modify the Source Number Tel->IP Manipulation Table on the gateway (Protocol Configuration – Manipulation Tables – Source Number Tel->IP).  The Source Prefix that you will be modifying comes from the phone number that you have assigned to your Trunk Groups (Configuration – Protocol Configuration – Trunk Group – Trunk Group). In my case the numbers are 1100, 1200, 1300 & 1400.  You need to make sure that you include all the numbers that can be used.  In my case each one is a PRI so that means that the numbers are 1100-1122 ect. 

    In the manipulation table (Source Number Tel->IP) you need to create a rule for each set of numbers.  Destination Prefix will be an asterisk (*) since you want this to affect all incoming numbers.  Source Prefix are the numbers that you want it to change.  In my case I put in 11[00-22] for the first rule, 12[00-22] for the second and so on.  This will only affect the numbers 1100-1122 ect.  Leave both Stripped digits columns set to 0 and change the “Prefix to Add” to the number that you want displayed on the Lync client for blocked calls.  I chose +19525551212.  Leave “Suffix to Add” blank, “Number of Digits to Leave” to 0 and set “Presentation to Allowed.  Make sure that you save the changes.


    in addition you will need to change one INI file setting.  Go to the IP address of the gateway /AdminPage (Example: http://10.10.10.1/AdminPage).  On the left Click on “ini Parameters”.  In the Parameter Name field put in     USESOURCENUMBERASDISPLAYNAME and click on the Apply New Value button.  In the output window you should see that the current value is 0.  You will want to change this to 1 by putting a 1 in the Enter Value box and clicking on the Apply New Value button. 


    Burn the configuration to the gateway and you will be able to receive blocked calls from the PSTN to Lync DIDs.

     

    Hope this helps.

    • Proposed as answer by jyoungjr Tuesday, August 16, 2011 5:30 PM
    • Marked as answer by Sharon.Shen Friday, August 19, 2011 1:16 AM
    Thursday, August 11, 2011 9:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,MacGeever,

    I think you can configure a special SIP URI for unkown Caller ID,calls received with hidden caller ID from the PSTN will be shown as coming from this number on the Lync client.

    Here is an arrticle about this configuration on Avaya,hope this method can give you some hints.

     http://jasonmlee.net/archives/431

    Regards,

    Sharon

    Monday, August 15, 2011 6:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    FYI

    If you don't need to present a number another option is to set the ANONYMOUSMODE value in the INI file to 1.  This will let the call through but in Lync you will see it as "Anonymous Caller".  So it is depends on how you want to see that presented.

    They really should handle anonymous calls better in Lync though...

    • Marked as answer by MacGeever Friday, August 19, 2011 11:35 PM
    Friday, August 19, 2011 11:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    For the benefit of anyone encountering this issue you can also implement the solution jyoungjr proposed but put "anonymous" in as the Prefix to Add instead of a phone number and it will work.  All calls will appear as "Anonymous Caller".  Thanks.
    Tuesday, August 23, 2011 3:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We have a very similar configuration and have found a resolution without modifying the source number.  The resolution was to add the vip of the f5 load-balancer to the Lync topology as a pstn gateway.

    The reason being is that when you receive a normal call you see sip:+telephonenumber@gatewayip.  So Lync knows exactly who it is talking to by the gateway ip address being found in the sip info.  In this instance the blocked calls come in as sip:anonymous@anonymous.invalid so Lync looks to the sending ip address to see who it needs to respond back to.  The last ip it sees is the f5 vip.  After running some sip tracing on the lync server we were able to catch an error stating something like the following "The gateway peer is not in the topology."  It assumed the gateway peer was the f5 vip, so to trick lync, we just put that vip in as a valid pstn gateway and everything started working just fine.

    It worked out for us, hopefully this helps someone.

    • Proposed as answer by mjbsn Thursday, September 15, 2011 6:10 PM
    Thursday, September 15, 2011 6:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I read this article and was having the exact issue where anonymous callers would fail as an incoming call and i recevied the gateway peer not found error I was using an Audiocodes 1000 also as voice gateway after trying every manipulation setting possible i still couldn't resolve the issue, so i figured maybe its not the gateway at all

    What puzzled me the most was i have an LYNC enterprise pool as well 6 Branch Servers where this was not occurring at these sites I then remembered recently that i had changed the IP's of this Lync Server and Audiocodes gateway to suit a QOS setup i was implementing for this site, it then occurred to me that maybe some old settings where causing this gateway peer not found error (I had not republished my topology after these changes as there was no other errors present)

     

    Republished my Topology and restarted Lync Server and all was resolved and Anonymous calls now work perfectly Hope this helps other people and saves them the time i spent on this problem

    • Edited by maz124ss Thursday, November 10, 2011 11:11 AM
    • Proposed as answer by maz124ss Thursday, November 10, 2011 11:12 AM
    Thursday, November 10, 2011 11:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having this same issue but I am not sure how to access the AdminPage to change the .ini settings. When you refer to gateway are you referring to the Lync FE server? - Robert

    Robert Hefner

    Friday, September 1, 2017 8:49 PM