Lync 2013 Edge Server - Lync Server Audio/Video Edge Don´t respond

Hello, We have a Lync 2013 Infraestructure. (With Windows 2008 R2)
3 front ends servers (pool) and 1 edge server.
We have an issue with the edge server.  Often we lost the Presence , IM and Audio/Video with external/federated contacts
We can´t chat or do any calls.
When we try to restart the service "Lync Server Audio/Video Edge" in the Edge, it never stop...
We try to kill the process MediaRelaySvc.exe without success.
The only way is to restart the server.
The server is up to date with the lastest hotfixes.
There are not events in APP/SYSTEM/LYNC logs in the event viewer.
Any idea ?
Thanks in advance!

Hi,
Please also check if there is any error message on FE Server.
Please make sure the CMS replication is update to the latest status on Edge Server.
Please make sure there is no other antivirus software in Edge Server as Anthony said above.
Please also double check the Edge certificate/DNS is setting suitable.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Similar Messages

  • Lync 2013 Deployment Requirements - One Server?

    I have an organization that has an offsite Exchange Server 2010, and Windows Server 2008 R2 Domain Controller (for the Exchange Server).
    I am trying to figure out what we need for hardware and Windows Server software to implement Lync 2013.  I understand that Lync 2013 cannot be put on the same server as the Exchange Server.  Can Lync 2013 be put on one Windows server?
    Michael

    Depends. Without knowing a lot about your environment (i.e users, HA requirements) ideally you'd have two. One as a Lync Standard Edition server (which can support up to 5000 users for Front End Services and Back-End database - but won't have HA) and one
    as an Lync Edge server (for outside connectivity - also won't have HA)
    Standard Edition will use SQL express as its database and automatically install it on the single server.
    As for operating system Windows 2008 R2 or above.
    As for hardware you can use this as a guide: http://technet.microsoft.com/en-us/library/gg398835.aspx and use the Lync Capacity planning tool http://www.microsoft.com/en-us/download/details.aspx?id=36828
    How many users do you have? (for example the first link has 32GB as recommended memory for a Front End, but if you don't have many users you can use less than that - and the Cap Planner will reflect that)
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
    www.lynced.com.au | Twitter
    @imlynced

  • Lync 2013-Office Web Access Server-IPAD

    I have configured a Office Web App server onto a Windows Server 2012.  I was able to upload a PowerPoint from a Lync 2013 client both internally and externally.  When I test external access to that PowerPoint from an IPAD using the 2013 clinet,
    I am not able to see the PowerPoint.  If I VPN into the network from the IPAD it works.  There seems to be a problem with my AAR but, like I said my Lync 2013 client works fine though AAR.  I can browse to the external url http:\\externalurl\hosting\discovery
    and I can see the XML page.  I have confirmed that I can ping the internal name on the AAR.
    I am using the following pattern us/|^hosting/|^m/|^o/|^oh/|^op/|^p/|^we/|^wv/|^x/).*) in my AAR
    Any help would be appreciated.

    Are you able to access the PowerPoint externally using the desktop Lync client?
    If not, check that you are able to access your Web Conferencing ports on your Edge infrastructure. (usually TCP 443 on the webconf.domain.com (or whatever you called it) on the Edge server or TCP 444 if you have only a single IP on your Edge)
    The test you've done, shows that you are able to connect to your Office WAC. But if you can't connect to webconf service, this can cause this type of issue - and it's not obvious.
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
    www.lynced.com.au | Twitter
    @imlynced

  • Forefront 2010 dening outlook 2013 and lync 2013 access to ther server

    we have currently, forefront TMG 2010, exchange server 2010 and lync 2010, running on our network and every working fine but recently i upgraded client MS Office 2010 to MS Office 2013 and suddenly forefront TMG 2010 started denying lync 2013 and outlook
    2013 access to the server.
    Please can somebody tell me how to resolve this problem.

    Hi,
    Thank you for your post here.
    Do you mean that you have published exchange server 2010 and lync 2010 via TMG?
    How dou you judge that TMG  blocks your traffic?
    Please check if there is any error information via TMG live logging.
    You can try to delete publish rule and reconfigure it.
    Best Regards
    Quan Gu

  • Lync 2013 Web Scheduler SMTP Server for invitations - non-exchange env

    We cannot get the Lync 2013 Web Scheduler to send email invites to anyone even after configuring the SMTP server for both the external and internal sites on our one and only front-end (we did the super simple same box install for testing
    purposes).  Yes we have done an IISReset;)  Has the SMTP server configuration process for the now built-in Lync 2013 Web Scheduler changed since the add-on Lync 2010 Web Scheduler?
    BTW, unless we haven't search for the right phrase(s), it seems there is ZERO documentation about configuring this for 2013 - only for 2010.
    HELP!!!

    Hi,
    You can refer to this blog Lync web scheduler without Exchange:
    http://blog.lyncfreak.com/2011/11/02/lync-web-scheduler-without-exchange/
    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.
    Kent Huang
    TechNet Community Support

  • On-Prem Lync 2013 moving to Lync Online (Office 365)

    We have an office of about 130 users, all of whom use either Lync 2010 or Lync 2013 client to connect to Lync Server 2013 (on-prem). We have recently signed up for Office 365's E3 plan which includes Lync Online, which we plan on using in favor of on-prem
    Lync Server. Our internal domain name is the same as the domain we're using be using for Office 365 (i.e. "initech.com"). Externally, I can connect to Lync Online (O365) just fine - however, from my Office's LAN, the external autodiscover records
    can't be resolved.
    If I want to cut all Lync users over to Lync Online and stop using Lync Server on-prem, what do I have to do? Any internal DNS records I have to add to make sure autodiscover resolves to Office 365?
    I have the following External DNS records set up successfully - should internal DNS mirror any of these?
    CNAME records
    Host name
    Points to address or value
    TTL
    msoid
    clientconfig.microsoftonline-p.net
    3600
    sip
    sipdir.online.lync.com
    3600
    lyncdiscover
    webdir.online.lync.com
    3600
    SRV records
    Service
    Protocol
    Port
    Weight
    Priority
    Name
    Target
    TTL
    _sip
    _tls
    443
    1
    100
    sipdir.online.lync.com
    3600
    _sipfederationtls
    _tcp
    5061
    1
    100
    sipfed.online.lync.com
    3600
    Thanks!

    Hi cllpd23,
    Based on my knowledge, in a hybrid environment, the External DNS records should not be changed to use the Lync Online records.
    You should recover your External DNS records settings and only add the SRV record
     “_sipfederationtls._tcp.domain.com 5061  sip.domain.com”.
    In internal DNS server, you should add the SRV records “_sipfederationtls._tcp.domain.com 5061 sip.domain.com” and ”_sip._tls.domain.com 443 sip.domain.com”,
    and also should point to the on-premises Access Proxy.
    The related articles for your reference.
    http://technet.microsoft.com/en-us/library/jj205403.aspx
    http://technet.microsoft.com/en-us/library/gg412787.aspx
    http://support.microsoft.com/kb/2757450
    Best regards,
    Eric

  • Lync 2013 migration from Lync 2010

    Hi All,
    I have a problem after I've successfully migrated our Lync environment from Lync 2010 (what was migrated from OCS 2008 R2) to Lync 2013.
    When I would like to delete the old Lync 2010 Front End server from the topology I cannot do that, because there are some TrustedApplicationPool registered to that. And I cannot delete this unused TrustedApplicationPools, because I got the following error:
    "Remove-CsTrustedApplicationPool : Cannot remove legacy trusted application pool. Use the legacy tools to remove the pool, then run Merge-CsTopology."
    I've tried that many ways, I've tried the merging etc. but it was unsuccessful. Has anybody any idea, step-by-step or something what can helpful to me?
    Many thanks,
    Tamás Dobos

    Hi,
    Did you check this step by step migration lync 2010 to 2013
    http://www.oiboran.com/?p=1073
    To remove Trusted application pools
    Get-CSTrustedApplicationPool
    Remove-CSTrustedApplicationPool -Identity nameofthepool 
    Removing Lync 2010
    http://terenceluk.blogspot.nl/2012/12/removing-lync-server-2010-standard.html
    Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

  • Lync 2013 client can't connect externally to edge server

    So I have my edge server set up in the DMZ. 3 ips bound to an interface for external connectivity.
    sip.domain.org (A record)
    webconf.domain.org (A record)
    av.domain.org (A record)
    _sip.tls.domain.org:443 pointing to the same IP as sip.domain.org
    External Lync Clients should be using this srv record to auto-connect, correct?
    I have purchased a thawte ssl cert and bound it correctly to the external interface.  Internal interface is a PKI internal CA cert. Sometimes when doing a testconnectivity from MS, it comes up stating " The certificate couldn't be validated because
    SSL negotiation wasn't successful", when other times I run the test and it states that it validates the cert correctly, analyzing the cert - no problems found, etc, all looks good and then fails at "couldn't sign in Error Unknown (0x80131500) 
    Error type: TLSFailureException.
    Not sure where to start looking or why it shows the cert is good sometimes and others not.
    Also when I launch the Lync Server Admin Console, Under Topology,  my edge server is showing Replication with a red X.  Don't know what to look for either.

    Hi jackl2001,
    By default, no policies are configured to support external user access, including remote user access, federated user access, even if you have already enabled external user access
    support for your organization. To control the use of external user access, you must configure one or more policies, specifying the type of external user access supported for each policy.
    Click on the link below for more details.
    Managing federation and external access to Lync Server 2013
    http://technet.microsoft.com/en-us/library/gg520966.aspx
    Best regards,
    Eric

  • Lync 2013 client Microphone auto Gain and video aspect ratio settings

    I can't disable the auto microphone gain which seems to be regulated by the Lync client.
    When having a meeting with video for instance, the microphone of the listening partner (side b) will keep on increasing the microphone gain, until it is on its maximum, because the listening partner is listening and does not make any noise.
    When someone on the other side of the room on side b is having a conversation with someone else, the mic gain keeps increasing till side a can follow that conversation, the mic is very sensitive.
    This can not be, there is no way to disable the gain in the Lync client, I've tried to disable the right of a program to take exclusive right of the device, without succes.
    Why did Microsoft didn't think about this, we need an advanced settings menu where things can be shaped.
    Not only the microphone gain is a problem, also the way the video is presented, there is no way to set an aspect ratio, if i'm having a 16:9 screen the video is chopped at the bottem and top of the video of the sending partner, so i'm unable to see the whole
    room of the sending side, which is there cause the cam can provide me a nice overview of the side when viewing the local cam at that side, but not with Lync.
    We are in an evaluation of Lync, but really getting annoyed by these short comings, in my opinion some basic settings which should be in lync from start. We can not sell these short comings to our employees.
    Maybe i'm looking in the wrong direction, if so, please tell me.

    Hi,
    Sorry for any inconvenience caused. You can try to set
    allowing high-definition video, with a resolution of 1280 x 720 and aspect ratio 16:9. For details about HD Video in Lync:
    http://blog.schertz.name/2011/10/hd-video-in-lync/
    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.
    Kent Huang
    TechNet Community Support

  • Audio/Video presets don't match

    When I capture video, I get this message:
    The audio sample rate of one or more of your captured media files does not match the sample rate on your source tape. The may cause the video and audio of the media files to be out of sync. Make sure the audio sample rate on your capture preset matches the sample rate of your tape.
    I've tried to find a way to access changing the kHz and bit rate (currently 12 on my Canon XL1S) but without luck.
    Any advice would be greatly appreciated.

    For existing tapes that were recorded in 12-bit audio, your options would be:
    1) in FCE select the DV-NTSC 32KHz Easy Setup and recapture the tape to a new sequence using this Easy Setup (32KHz = 12 bit audio) or
    2) dub your tape to another camcorder via ANALOG connection and then capture the new tape in FCE. Of course, make sure that the second camera is set up to record 16-bit audio when you dub <grin>
    For the future, you really should change your camera's setup to 16-bit audio. On the Canon camcorders, this is normally in the camera setup menus under 'audio' or a/v.
    Try Camera menu > VCR setup > Audio mode > 16 bit. The XL1S manual is available online at the Canon Product Support website. You should select 16-bit audio and keep it that way for all future filming.

  • Lync 2013 Mobility Client - Video Call Issue (Everything Else works).

    Hey Technet’ies,
    I have been struggling for a couple of weeks now to resolve one of the final issues with a Migration/Upgrade Project on Lync Server 2013.
    I have nearly every Lync Client Scenario working well except the Mobility Client (outside of the domain) which cannot successfully complete a Video
    Call to a Windows Desktop Client (inside the domain) – the toast pops up, but when we click accept - it just times out after 15 seconds
    K
    The strange thing is every other Video Call scenario works;
    Mobility Client (Outside Domain)
    àWindows Desktop Client (Inside Domain)
    = Unsuccessful
    Mobility Client (Inside Domain)
    à Windows Desktop Client (Inside Domain) = Successful
    Mobility Client (Inside Domain)
    à Windows Desktop Client (Outside Domain) = Successful
    Mobility Client (Outside Domain)
    à Windows Desktop Client (Outside Domain) = Successful
    Mobility Client (Inside Domain)
    à Mac Desktop Client (Inside Domain) = Successful
    Mobility Client (Inside Domain)
    à Mac Desktop Client (Outside Domain) = Successful
    Mobility Client (Outside Domain)
    à Mac Desktop Client (Outside Domain) = Successful
    Mobility Client (Outside Domain)
    à Mac Desktop Client (Inside Domain) = Successful
    Mobility Client (All Scenarios)
    à Mobility Client (All Scenarios) = Successful
    Our setup is pretty standard;
    All OS servers are Win Server 2012 R2
    Lync 2013 Standard FE Server
    Lync 2013 Edge Server
    Reverse Proxy IIS AAR (Also Win Server 20012 R2)
    Lync 2013 Desktop Clients, Lync 2011 Mac Clients, IOS and Android Mobility Clients – all latest versions.
    External NAT (via Cisco Routers ACL’s)
    Internal Windows Firewall Currently off on all Servers
    All Certs / DNS Configured as per Technet Recommendation
    I have reviewed / analysed a number of log/trace files – looking for some/any information on the problem;
    Mobility Client (cmlogX.log)
    Windows Desktop Client (*.etl) / Microsoft Message Analyzer
    Lync 2013 Server (CSController)
    With all my looking I could not make out an error except a timeout (15 seconds) on the Mobility Client log (which I currently can’t find).
    Clearly we are missing something and I have gone up and down our implementation a number of times, the only semi-unknown is our old 2010 Pool / Central Management Server (which is currently pretty much redundant but the majority of users still on).
    I would really appreciate any feedback anyone can provide or any insight anyone may have on this challenge.
    Thanks in advance, Alex.
    Alex

    Hi Andrew,
    Thanks for the quick contact!!
    Sorry - typo in my post, I have now corrected it;
    Mobility
    Client (Outside Domain) àWindows
    Desktop Client (Inside Domain) = Unsuccessful
    So I completely missed that blog post of yours (out of the 100's I have read) and you are the first person to clearly say (in simple terms) to point the lyncweb.contso.com to the public IP address on my internal DNS, I have just made that change and see
    if it will correct the issue - will wait for replication. 
    Also I am running IIS / AAR as Reverse Proxy (not ISA) and had the Internal DNS Host A of lyncweb.contso.com and lyncdiscover.contso.com point back to my Reverse Proxy Internal NIC (i.e. 10.1.1.32) as the External NIC is isolated on in the Perimeter Network,
    is this correct?
    So it now goes like this
    *Inside Domain*
    lyncdiscover.contson.com --> 10.1.1.32 (Reverse Proxy Internal Nic) --> 10.1.1.26 (Front End Server)
    lyncweb.contson.com --> 201.183.0.1 (Reverse Proxy External Nic - Public IP) --> 10.1.2.16 (Reverse Proxy External Nic) --> 10.1.1.26 (Front End Server)
    Does this make any sense, I know ISA and IIS/AAR are pretty much interchangeable.
    Thanks again Andrew and look forward to any feedback,
    Alex.
    Alex

  • Lync 2013 - We didn't find an audio device

    Hi,
    I have done all troubleshooting but while opening Lync 2013, it's showing no audio device is available.
    Both speakers and mic are working fine in laptop.

    Hi Rahul Mallaiya,
    This is a very common problem, and there're so many reasons can cause this problem.
    There are several common situations:
    1. Compatible problem
    Try to use the qualified device for Lync.
    2. Drivers related problem
    Try to update the drivers of your device(include BIOS)
    3. Software related problem
    Maybe some similar software as Lync installed on your device, you could try to uninstall the software.
    4. other
     related problems
    USB hub related problem, you could refer to the following thread.
    https://social.technet.microsoft.com/Forums/lync/en-US/30ec9d70-2cca-40be-b9dc-be7763e3530a/lync-2013-client-no-audio-device-detected
    Also please take your Lync client up to date.
    Hope it 
    can be helpful.
    Best regards,
    Eric

  • Lync 2013 external to internal IM is slow or messages do not arrive

    Hi,
    I'm building a Lync 2013 setup on Windows Server 2012. Internal Lync 2013 standard server with Lync 2013 edge server in a DMZ. No federation.
    Internally al users are able to chat, audio/video and conferance.
    My problem is that external users are able to sign in and start a chat with an internal user but it looks like communication is only working in one way.
    Example:
    User 1 is external;
    User 2 is internal;
    User 1 starts IM with user 2 and says "hi"
    User 2 receives the IM and accepts and is seeing the "Hi" messages from user 1.
    User 2 reply's with "Hi" back and that messages does not arrive at user 2. Some time's not at all, some times after a minute or 2.
    When user 1 is receiving the reply user 2 still see's the rotating dot's that the message is beeing send. and after a while user 2 receives:  "This message may not have been sent to User1
    because there was no response from the server."
    The situation seems to occures only from internally to externally and also with both users externally. I cannot see any error's in the event logs of the Internal or Edge server. De debugging tools is showing me error's like:
    Text: Message or one of its headers caused SIP transaction processing error
    Result-Code: 0xc3e93f5b SIPPROXY_E_TRANSACTION_TIMEOUT
    Text: Message was discarded by the application
    Result-Code: 0xc3e93ec6 SIP_E_AUTH_CANNOT_CHALLENGE
    Audio/video requests are also arriving at the other user but are unable to establish a connection.
    I can't really figure out what is going wrong. Certificates are correct, i think firewall rules are in place otherwise i have no communication at all i'm guessing. Routes also seem ok.
    Some help would be great
    Regards
    Pascal

    Hi,
    The internal user Lynctest is sending a message to pslijkerman who is connected externally.
    User pslijkerman receives the messages but the lynctest user keeps seeing rotating dots (processing message or something) after 1 minute or so the following messages is displayed in the Lync Im screen for user lynctest.
    ======
    This message may not have been sent to Pascal Slijkerman because there was no response from the server.
    ======
    This is some logging from the internal lync server.
    ===========
    TL_INFO(TF_PROTOCOL) [0]226C.2528::04/09/2013-07:53:17.056.0013034f (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2420.idx(196))[2737352855] $$begin_record
    Trace-Correlation-Id: 2737352855
    Instance-Id: 1304
    Direction: incoming
    Peer: srv-domain34.domain.nl:49510
    Message-Type: request
    BYE sip:[email protected];opaque=user:epid:L30jBQ2CP1G71x2KsIF2cAAA;gruu SIP/2.0
    Start-Line: BYE sip:[email protected];opaque=user:epid:L30jBQ2CP1G71x2KsIF2cAAA;gruu SIP/2.0
    From: "" <sip:[email protected]>;epid=36889192ba;tag=c84477430c
    To: "lynctest"<sip:[email protected]>;tag=ffbc4dc4e5;epid=b58bd39e10
    Call-ID:  f295aa80628b4c7e8e0896ed216ec5b2
    CSeq: 1 BYE
    Via:  SIP/2.0/TLS 172.xx.xx.1:49510;branch=z9hG4bK49BC5E54.654FC7DF7B8FBC80;branched=FALSE
    Via:  SIP/2.0/TLS 192.xx.xx.164:49524;received=84.xx.xx.204;ms-received-port=49524;ms-received-cid=E00
    Route:  <sip:SRV-domain34.domain.nl:5061;transport=tls;opaque=state:T:F;lr>;tag=BDBD058532075001772DF63E1A794C59
    Max-Forwards:  69
    Content-Length:  0
    Ms-client-diagnostics:  52112;reason="Callee did not receive an ACK for the 200 OK"
    $$end_record
    TL_INFO(TF_DIAG) [0]226C.2528::04/09/2013-07:53:17.087.00130d06 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:1207.idx(778))[2737352855] $$begin_record
    Severity: information
    Text: Routed a request that came from a server trusted for routing
    SIP-Start-Line: BYE sip:10.xx.xx.30:52211;transport=tls;ms-opaque=07531f0291;ms-received-cid=11400;grid SIP/2.0
    SIP-Call-ID: f295aa80628b4c7e8e0896ed216ec5b2
    SIP-CSeq: 1 BYE
    Peer: 10.xx.xx.30:52211
    Data: destination="[email protected]"
    $$end_record
    TL_INFO(TF_PROTOCOL) [0]226C.2528::04/09/2013-07:53:17.087.00130d62 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2420.idx(196))[2737352855] $$begin_record
    Trace-Correlation-Id: 2737352855
    Instance-Id: 1304
    Direction: outgoing
    Peer: 10.xx.xx.30:52211
    Message-Type: request
    BYE sip:10.xx.xx.30:52211;transport=tls;ms-opaque=07531f0291;ms-received-cid=11400;grid SIP/2.0
    Start-Line: BYE sip:10.xx.xx.30:52211;transport=tls;ms-opaque=07531f0291;ms-received-cid=11400;grid SIP/2.0
    From: "" <sip:[email protected]>;epid=36889192ba;tag=c84477430c
    To: "lynctest"<sip:[email protected]>;tag=ffbc4dc4e5;epid=b58bd39e10
    Call-ID: f295aa80628b4c7e8e0896ed216ec5b2
    CSeq: 1 BYE
    Via: SIP/2.0/TLS 10.xx.xx.37:5061;branch=z9hG4bK445B1BFE.41682B6C1B09AC7D;branched=FALSE;ms-internal-info="bajkITWtf7W6iXpPN4ntXDe2Uuk9SpjNhAw17jrz6DmT9sK2hB10T2EQAA"
    Via: SIP/2.0/TLS 172.xx.xx.1:49510;branch=z9hG4bK49BC5E54.654FC7DF7B8FBC80;branched=FALSE;ms-received-port=49510;ms-received-cid=13800
    Via: SIP/2.0/TLS 192.xx.xx.164:49524;received=84.xx.xx.204;ms-received-port=49524;ms-received-cid=E00
    Max-Forwards: 68
    Content-Length: 0
    Ms-client-diagnostics: 52112;reason="Callee did not receive an ACK for the 200 OK"
    $$end_record
    TL_INFO(TF_PROTOCOL) [0]226C.2528::04/09/2013-07:53:17.087.00130f28 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2420.idx(196))[2737352855] $$begin_record
    Trace-Correlation-Id: 2737352855
    Instance-Id: 1306
    Direction: incoming
    Peer: 10.xx.xx.30:52211
    Message-Type: response
    SIP/2.0 481 Call Leg/Transaction Does Not Exist
    Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist
    From: "" <sip:[email protected]>;epid=36889192ba;tag=c84477430c
    To: "lynctest"<sip:[email protected]>;tag=ffbc4dc4e5;epid=b58bd39e10
    Call-ID:  f295aa80628b4c7e8e0896ed216ec5b2
    CSeq: 1 BYE
    Via:  SIP/2.0/TLS 10.xx.xx.37:5061;branch=z9hG4bK445B1BFE.41682B6C1B09AC7D;branched=FALSE;ms-internal-info="bajkITWtf7W6iXpPN4ntXDe2Uuk9SpjNhAw17jrz6DmT9sK2hB10T2EQAA"
    Via:  SIP/2.0/TLS 172.xx.xx.1:49510;branch=z9hG4bK49BC5E54.654FC7DF7B8FBC80;branched=FALSE;ms-received-port=49510;ms-received-cid=13800
    Via:  SIP/2.0/TLS 192.xx.xx.164:49524;received=84.xx.xx.204;ms-received-port=49524;ms-received-cid=E00
    Content-Length:  0
    Ms-client-diagnostics:  52085;reason="Dialog does not exist"
    $$end_record
    TL_INFO(TF_DIAG) [0]226C.2528::04/09/2013-07:53:17.087.0013142e (SIPStack,SIPAdminLog::WriteDiagnosticEvent:1207.idx(778))[2737352855] $$begin_record
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist
    SIP-Call-ID: f295aa80628b4c7e8e0896ed216ec5b2
    SIP-CSeq: 1 BYE
    Peer: srv-domain34.domain.nl:49510
    $$end_record
    TL_INFO(TF_PROTOCOL) [0]226C.2528::04/09/2013-07:53:17.087.00131486 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:2420.idx(196))[2737352855] $$begin_record
    Trace-Correlation-Id: 2737352855
    Instance-Id: 1306
    Direction: outgoing
    Peer: srv-domain34.domain.nl:49510
    Message-Type: response
    SIP/2.0 481 Call Leg/Transaction Does Not Exist
    Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist
    From: "" <sip:[email protected]>;epid=36889192ba;tag=c84477430c
    To: "lynctest"<sip:[email protected]>;tag=ffbc4dc4e5;epid=b58bd39e10
    Call-ID: f295aa80628b4c7e8e0896ed216ec5b2
    CSeq: 1 BYE
    Via: SIP/2.0/TLS 172.xx.xx.1:49510;branch=z9hG4bK49BC5E54.654FC7DF7B8FBC80;branched=FALSE;ms-received-port=49510;ms-received-cid=13800
    Via: SIP/2.0/TLS 192.xx.xx.164:49524;received=84.xx.xx.204;ms-received-port=49524;ms-received-cid=E00
    Content-Length: 0
    Ms-client-diagnostics: 52085;reason="Dialog does not exist"
    $$end_record
    ============
    Thanks
    Regards
    Pascal

  • Mac Lync 2011 and Lync 2013 - Autodiscovery not working

    We're currently setting up a Lync 2013 topology including Front End Pool and Edge Server.  I've been told that the Lync 2011 client should work with lyncdiscover and lyncdiscoverinternal as it does for IOS and Windows.
    However looking at the logs being generated by the Lync 2011 client this doesn't seem to be the case.  I'm seeing
    sipinternal, sip, sipexternal when Lync 2011 is set to AutoConfigure.  I do not have any of these configured.
    If I manually specify lyncdiscover and lyncdiscoverinternal the logs show it's starting to find the Front End Servers, but still errors.
    What am I doing wrong?

    Hi,
    Please add the following SRV records in internal DNS Server:
    _sipinternaltls._tcp.sipdomain.com
     _sipinternal._tcp.sipdomain.com
     _sip._tls.sipdmain.com
    Then flush the DNS cache on the local Mac computer, then test the issue again.
    Best Regards,
    Eason Huang
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Eason Huang
    TechNet Community Support

  • Lync 2013 Web App : Web Ticket error

    Hi,
    I have a Lync 2013 std installed on server 2008 r2, with edge , TMG and Wac server.
    When i try to join a meeting with Lync Web App i get the error
    There was an error contacting the web ticket service. Service Error !
    I have tried several explorer ( chrome ,firefox, IE ), to restart FE, checking certificates, logs, IIS, TMG rules.
    I cannot fixed this.
    Is anynone has an idea ?
    Thanks

    Hi Joe,
    Would you please tell us more details about this issue?
    Have you tried all steps in the above links? Does this happenf or all client machines? Please try to reset IE to test the issue.
    If the issue persists, please check event log and try to enabling logging tool for further troubleshooting.
    http://blog.schertz.name/2011/06/using-the-lync-logging-tool/
    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.
    Kent Huang
    TechNet Community Support

Maybe you are looking for