locked
New IP crashs connection between Lync 2013 on prem and Exchange Online UM RRS feed

  • Question

  • Hello,

    we're running Lync 2013 on prem, our mailboxes are hosted by Exchange online with UM enabled. It was working perfectly.

    Last week we had to change our external IP addresses due to a new leased line. All DNS settings were changed.

    Since we're using the new addresses no one is able to reach their voicemail for some reason. The error shown in the frond-end server log is:

    Event-ID 44009:

    Attempts to route to servers in an Exchange UM Dialplan failed

    No server in the dialplan [Hosted__exap.um.outlook.com__ourdomain.onmicrosoft.com] accepted the call with id [de27eb82-eb55-42b7-b17d-248f5c94f0fa].
    Cause: Dialplan is not configured properly.
    Resolution:
    Check the configuration of the dialplan on Exchange UM Servers.

    Unfortunately I'm unable to find any setting within the dial-plan that reflects an ip address, can anybody help which settings needs to be changed where?

    Regards

    Andreas

    Monday, August 13, 2018 3:07 PM

Answers

  • Hi,

    the issue has been resolved yesterday, it was related to a wrong firewallrule in re to port 3478.

    Thanks for all your inputs

    Andreas

    Wednesday, August 29, 2018 7:05 AM

All replies

  • Hey Hi ! 

    It is quite tough to comment anything unless we analyse the Server logs. The best way to analyse this issue or to fix the issue is to verify the configuration from the scratch. The below blog shows the steps for end-to-end integration Lync / Skype for Business with Exchange Online Unified messaging.

    Note : You may skip the Exchange on-premise part in this blog.

    https://blogs.technet.microsoft.com/nagshettykadwadi/2017/10/18/integrate-skype-for-business-server-with-exchange-online-unified-messaging-in-hybrid-scenario/

    Another Excellent Blog:

    https://blogs.technet.microsoft.com/nexthop/2016/03/29/integrate-on-premise-lync-or-skype-for-business-with-office-365-unified-messaging-um/

    Best Regards, Neeranjan


    Monday, August 13, 2018 7:23 PM
  • Hi Andreas,

    Firstly,you changed the external IP in the edge server,please notice if you have changed IP for following A records and SRV record the in the external DNS.


    And the _sipfederationtls._tcp.domain.com srv record should be moved to th exteranl DNS.There is a similar case.

    https://social.technet.microsoft.com/Forums/office/en-US/a5f30a23-333b-4bc6-b09f-a10e713ed116/event-id-44009-lync-server-2013-onprem-and-exchange-online-um-integration?forum=lyncvoice

    please refer to the following link.check the general settings step by step.

    http://troubleshootinglync.blogspot.com/2013/08/troubleshooting-lync-on-prem-um-in-cloud.html

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.



    Tuesday, August 14, 2018 3:13 AM
  • Hi ,

     

    Do you have some updates? If the reply help to you ,please mark the reply as answer.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, August 14, 2018 10:00 AM
  • Thanks for all your input. Unfortunately everything seems to be ok, so it's still not working.

    I did some digging and found this, obviosly there's something wrong:

    TL_INFO(TF_PROTOCOL) [2]14E4.6C48::08/14/2018-13:50:02.271.00016e5f (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1857863294] $$begin_record
    Trace-Correlation-Id: 1857863294
    Instance-Id: F980F4
    Direction: incoming
    Peer: 172.16.9.13:59522
    Message-Type: request
    Start-Line: BYE sip:uminternal.um.prod.outlook.com:5066;transport=Tls;ms-fe=AM6PR0502MB3943.eurprd05.prod.outlook.com SIP/2.0
    From: <sip:user@domain.de>;tag=8a0888bbf1;epid=945a864ddd
    To: <sip:user@domain.de;opaque=app:voicemail>;tag=3bc55227ab;epid=6D7C114DC7
    Call-ID: 83927580da8d4e40adb0c6c242191b6a
    CSeq: 2 BYE
    Via: SIP/2.0/TLS 172.16.9.13:59522
    Route: <sip:pool.domain.de:5061;transport=tls;ms-fe=fe-server.domain.de;opaque=state:F:Ci.R4fd1400;lr;ms-route-sig=gsQZRdWzBe73OxWY7b0-Fyh5LllcL3MCqaOrWyZTcgzTJM1YPljyb7twAA>
    Route: <sip:edge-server:5061;transport=tls;opaque=state:Si;lr>
    Route: <sip:exap.um.outlook.com:5061;transport=tls;epid=6D7C114DC7;lr;ms-key-info=AAEAAeNULexPbo_9wjPUAU17A4EG2kFH401nvuT5lGs0RFAPNejqHgSwlErj7DmjcQntrQTUgMW-gGIEWiU2CZLC1ZodmfL3KPY9H6p8R4enB9vnx4oqsedMqUXlD55qTBfCvHcpiNm4Jqy_cUbo2FNQZui4VKydYSIz3zrwSnOyo4qo7WpCcb-CXZaXHcnm9vk6XScUrY32ABvxHPZuZ-eOKxg5a-wpWF-2x4Egrgoy7wbDjfCgIoN4sE9r2DAE8PbqCHd3s1RSVA8DXH_wRGLbsVx0RicV0-SK7pkt_NQyaRa3q6JDEHS8xQ2MnTrVzAwcZ74qIO3WxSODYYL3oFSv_wzqRKwos4YTMzntIVp-Jvi7ppMT0ZqtV0sgeg1ktlDapslOQNAp0nWwZ1L18z29BU54cSv70s3ieNLpeJsdRLH0HfJwpbG8X9G_eDqYuExw546y1BQ1uQFYbnjmFmo4kdfA_ekvjtJkNNzqYIWd_0AirxX2G5iTlMFdMyG4mlHy7TlFJKLzkESmkmIxhOKw3tcS5Enc39GFvKCdadgHNy_OpVuPj3tGwSJJhKjINAfBFREWOeqI7Ge-Dg5XEohHiHgk-nNkCVQhNgZA9D6TPB8BZFE2uiNt3-uv-8ZQrkojnCAnfT-dsz_SLRGEzp70Ddiy7UUDijEzG1ofqOR86SevzBgd27W4VXst86qR;ms-route-sig=fcVTE0aCCQqYiKJYJL2UAYpB6ddTv1Pz0NIJIl3yeciKroCdZS2mCQJgAA>
    Max-Forwards: 70
    Content-Length: 0
    ms-client-diagnostics: 22; reason="Call failed to establish due to a media connectivity failure when both endpoints are internal";UserType="Callee";MediaType="audio";MediaChanBlob="NetworkErr=no error,ErrTime=0,RTPSeq=0,SeqDelta=0,RTPTime=0,RTCPTime=0,TransptRecvErr=0x0,RecvErrTime=0,TransptSendErr=0x0,SendErrTime=0,InterfacesStall=0x0,InterfacesConnCheck=0x0,MediaTimeout=0,RtcpByeSent=0,RtcpByeRcvd=0,BlobVer=1";BaseAddress="172.172.172.172:20018";LocalSite="172.172.172.172:20029";RemoteSite="10.21.15.254:25198";MediaEpBlob="ICEWarn=0x40003a0,ICEWarnEx=0x0,LocalMR=80.80.155.155:57690,RemoteMR=52.112.131.77:52952,PortRange=20000:20039,LocalMRTCPPort=54446,RemoteMRTCPPort=52952,LocalLocation=2,RemoteLocation=2,FederationType=0,StunVer=1,CsntRqOut=0,CsntRqIn=0,CsntRspOut=0,CsntRspIn=0,Interfaces=0x2,BaseInterface=0x2,IceRole=1,RtpRtcpMux=0,AllocationTimeInMs=225,FirstHopRTTInMs=2,TransportBytesSent=11816,TransportPktsSent=364,IceConnCheckStatus=5,PrelimConnChecksSucceeded=0,IceInitTS=3743243388971,ContactSrvMs=165,AllocFinMs=225,FinalAnsRcvMs=1232,ConnChksStartTimeMs=1234,ReinviteSntMs=12616,NetworkID=domain.de,BlobGenTime=3743243401816,MediaDllVersion=6.0.8968.450,BlobVer=1";MediaMgrBlob="MrDnsE=av.domain.de,MrResE=0,MrErrE=11001,MrBgnE=37432433889576816,MrEndE=37432433889583088,MrDnsI=edge-server,MrResI=1,MrErrI=0,MrBgnI=37432433889547864,MrEndI=37432433889555128,MrDnsCacheReadAttempt=0,BlobVer=1"
    $$end_record

    I don't have a clue why it thinks it is local, this ist our external ip-address nad remote is MS-Cloud: LocalMR=80.80.155.155:57690,RemoteMR=52.112.131.77:52952

    Tuesday, August 14, 2018 2:55 PM
  • Hi,

    This ICEWarn=0x40003a0 error is usually related to network configuration issue on Edge sever.

    Please review the NIC IP configuration of the Edge server in the topology.

    Also please review the route configuration on the Edge server.

    Refer to: https://ucsorted.com/2014/01/12/media-connectivity-failure-when-both-endpoints-are-internal/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, August 16, 2018 10:05 AM
  • Hello,

    I'm pretty sure my Network config is quite nice:

    C:\Users\Administrator>ipconfig

    Windows IP Configuration


    Ethernet adapter External:

       Connection-specific DNS Suffix  . : domain.de
       Link-local IPv6 Address . . . . . : 
       IPv4 Address. . . . . . . . . . . : 10.10.10.30
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 10.10.10.31
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 10.10.10.32
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.10.10.2

    Ethernet adapter Internal:

       Connection-specific DNS Suffix  . : domain.de
       Link-local IPv6 Address . . . . . : 
       IPv4 Address. . . . . . . . . . . : 172.16.1.104
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :

    The persistent routes also look fine to me, the 192 is our VPN, 172.16 the internal Network, 10.10.10.x DMZ all networks hosted by TMG:

    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
        192.168.102.0    255.255.255.0      172.16.1.98       1
           172.16.0.0      255.255.0.0      172.16.1.98       1
              0.0.0.0          0.0.0.0       10.10.10.2 

    Monday, August 20, 2018 12:34 PM
  • Hi,

    Have you resolved you issue?

    I noticed you only changed the external IP address, what I can think is it may be related to network route issue.

    Please review your route configuration about your new IP.

    In addition, what is the subnet of your client network? I notice it has “172.172.172.172” address in the logs, you could try to add static route with the whole private addresses on the Edge server.

    netsh interface ipv4 add route 10.0.0.0/8 "Internal" 172.16.1.98

    netsh interface ipv4 add route 172.16.0.0/12 "Internal" 172.16.1.98

    netsh interface ipv4 add route 192.168.0.0/16 "Internal" 172.16.1.98

    Regards,

    Shaw

    Tuesday, August 28, 2018 8:38 AM
  • Hi,

    the issue has been resolved yesterday, it was related to a wrong firewallrule in re to port 3478.

    Thanks for all your inputs

    Andreas

    Wednesday, August 29, 2018 7:05 AM
  • Thanks for your sharing.

    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, August 29, 2018 8:06 AM