locked
Outgoing calls disconnects using new SIP trunk RRS feed

  • Question

  • Hi,

    i have a lync 2010 setup. all calls (until now) are going through isdn lines. a few days ago i have configured a sip trunk to use. i have configured new dial plans and voice routes for this.

    the issue is that when i call an external number the call is not established. if i click redial usually the call is connected fine. incoming calls are working just fine

    Wednesday, October 1, 2014 7:24 PM

Answers

  • Hm, certified for Lync 2010 means nothing, because I have also some sip providers they configured the sip trunk wrong.

    Best way to find out what happened is to make a Wireshark trace and to see what is wrong for sim ring and forwarded calls. On your OCSLogger trace we can see the service for your number is not available.

    Have you check if  its need to change the trunk configuration like

    set-cstrunconfig -Identity yourtrunk -EnableSessionTimer $true -RTCPActiveCalls $false -RTCPCallsOnHold $false


    regards Holger Technical Specialist UC

    • Marked as answer by Eason Huang Monday, October 13, 2014 2:09 AM
    Sunday, October 12, 2014 8:22 AM

All replies

  • There are many potential causes. The best option here is to grab a trace of the Call from the Mediation server to determine whats going on. A trace from the Client will also prove useful. Share that with us and we can see how we may be able to assist.

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Lync Sorted blog

    Wednesday, October 1, 2014 8:32 PM
  • Hi,

    this could be anything. Have logging run on the mediation server for SIPSTACK and outbound calling, simulate the problem and see what's really going on when a call getting terminated 


    http://thamaraw.com

    Thursday, October 2, 2014 1:55 AM
  • i got this from the logging Tool:

    TL_ERROR(TF_PROTOCOL) [1]070C.083C::10/02/2014-09:53:35.314.000001a9 (MediationServer,GatewayCall.GatewayParticipateComplete:gatewaycall.cs(1740))(0000000002446616)$$START-MEDIATIONSERVER
    MediationCall: 3ff4fd37c1dc4083bc2a12218476c925
    CallId: 005e2a14-9630-4f2e-b9ad-9f22d8d67c5d
    From: sip:89898989@lynmedia-i001.hnint.lan;user=phone
    To: sip:+4541269061@hostnordic.supertel.dk;user=phone
    Direction: Outbound
    Start-Line: FailureResponseException: ResponseCode=503 ResponseText=Service unavailable
    Microsoft.Rtc.Signaling.FailureResponseException:A 503 (Service unavailable) 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.SignalingSession.EndParticipate(IAsyncResult result)
       at Microsoft.RTC.MediationServerCore.GatewayCall.GatewayParticipateComplete(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.SipInviteAsyncResult.ProcessFailureResponse(Object state)
       at Microsoft.Rtc.Signaling.QueueWorkItemState.ExecuteWrappedMethod(WaitCallback method, Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

    i get the 503 service unavailable... which i find strange. because first outbound call ALLWAYS fail and the second always succeds

    Thursday, October 2, 2014 10:02 AM
  • You might be hitting different switches on the telco side, if one fails then another works, I'd suggest calling your telephony provider and see if they can tell you why they're rejecting it.

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications

    Thursday, October 2, 2014 10:40 AM
  • Hi,

    just had a chat with out sip provider... the failing calls are rejecting the calls from 89898989@lynmedia-i001.hnint.lan. but why oh why is this number used when dialing out??? for some reason this is used on the first attempt for all outgoing calls.

    Thursday, October 2, 2014 11:07 AM
  • I was thinking that, but wasnt' sure if you were just masking your internal DID in the forum post intentially.  Check your trunk settings and the route itself for normalization rules or a caller ID mask to see if anything is in the way.  Does the number in the second call look correct? What type of gateway are you using to connect to ISDN?  Have you reviewed the configuration there?

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications

    Thursday, October 2, 2014 11:38 AM
  • Hi,

    the issue with the 89898998 number was a brainfart from my side... i configured that number on the voice route... and my sip supplyer were disconecting calls from that number because it was not "originating" from them.

    now my issue is that my workflow is failing with the same error... calls from outside are forwarded and disconected because they are not comming from a "known" number.

    Thursday, October 2, 2014 11:54 AM
  • Hi,

    From your description above, it seems that the issue of outbound call has solved. Now the same issue happens for incoming calls.

    Please double check the normalization rule on Lync Server Control Panel.

    Best Regards,

    Eason Huang


    Eason Huang
    TechNet Community Support

    Sunday, October 5, 2014 7:04 AM
  • if you use the ocslogger and filter Mediation server, Inbound Routing, you can see your incomming numbers.

    Looks like something with normalization isn´t correct configured.


    regards Holger Technical Specialist UC

    Sunday, October 5, 2014 8:33 AM
  • As Holger mentioned, run logging in Mediation server and check for thr inbound number and make sure that it properly get normalize in to the correct E.164 number. Else it will fail to establish the call with the end point 



    Monday, October 6, 2014 3:06 AM
  • Hello everyone...

    The issue is not resolved you. and the issue is not inbound calls. only sim call and forwarding. and it is because referred-by is not working.

    The lync 2010 cu from september is installed. i have updated the MediationServerSvc.exe.config file have been updated with the fqdn of the gateway. 

    i have tested with both referral enabled and disabled on the trunk config. same issue.

    The sip provider is lync 2010 certified

    Monday, October 6, 2014 2:10 PM
  • Hm, certified for Lync 2010 means nothing, because I have also some sip providers they configured the sip trunk wrong.

    Best way to find out what happened is to make a Wireshark trace and to see what is wrong for sim ring and forwarded calls. On your OCSLogger trace we can see the service for your number is not available.

    Have you check if  its need to change the trunk configuration like

    set-cstrunconfig -Identity yourtrunk -EnableSessionTimer $true -RTCPActiveCalls $false -RTCPCallsOnHold $false


    regards Holger Technical Specialist UC

    • Marked as answer by Eason Huang Monday, October 13, 2014 2:09 AM
    Sunday, October 12, 2014 8:22 AM