Check current calls via edge server

Is there a way to check what calls are currently happening via a Lync 2013 edge server.  What I mean here is we need to take down the director pool for some maintenance and this is the next hop from the edge hence before we do this would be good to
see if there is active communications going on of any kind of modality (video, voice etc)
Thanks
DE

Hi, 
You can use Get-CsWindowsService.
It will list you all services and activity level/sessions as below:
Status     Name            ActivityLevel
Running  REPLICA
Running  RTCSRV                Incoming Requests per Second=0,Messages In Server=0,Incoming ..
Running  RTCDATAPROXY    Server Connections Currently Active=40
Running  RTCMRAUTH         Current Requests=0
Running  RTCMEDIARELAY   Active Sessions=45
You can put edge server on drain as:
Stop-CsWindowsService -Graceful
It will not drop active session and also will not accept any new user on your edge server. Once all active sessions are completed, you can start your maintenance.

Similar Messages

  • Adobe Connect prevents external users from connecting via Edge Server

    Errors thrown in the logs:
    Bad network data; terminating connection : bad chunk version 24 on input stream 07726718
    Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: Unknown, IP: 110.141.64.253, App: , Protocol: rtmp) : 18
    Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: Unknown, IP: 110.141.64.253, App: , Protocol: rtmp) : 03
    Any advice would be greatly appreciated!
    Regards
    Ole Kristensen

    Hi,
    Please check all the services are started on Lync Edge server.
    Please double check the ports for both Edge server internal and external interface with the help of the link below:
    http://technet.microsoft.com/en-us/library/gg425891.aspx
    You can test your remote connectivity with the help of the link below:
    https://testconnectivity.microsoft.com/
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Check the time of edge server stop working

    We have exchange 2010 in our environment. There is an edge role installed in a server. The server was hanged and mail service stopped working. But unfortunately we dont monitor these time.
    How can we see the last time the edge server working i.e from when it stopped receiving mail from outside domain.
    and what is the reason for server hanged?
    NB: The whole time internal domain mail send/receive was ok.
    Setu Bandhan Saha

    Hi
    In your event viewer it should give you some indication of when the server stopped responding. It can be due to updates, running out of resources, potential hardware failures.
    If possible can u plz tell me where in event viewer(system,security....)
    Setu Bandhan Saha

  • Exchange 2007 edge server with ironport

    I currently have a frontend exch 2003 and backend exch 2003 server with ironport. my mx record is the ironport which then forwards into the backend server. The frontend server was only used for owa and using outlook with https connection to exchange.
    With 2007 it has more functionality and the front end server is now called an edge server. Should I have mx go there then to ironport or vice versa? I'm thinking ironport to edge server to hub transport server. Is that correct? will it work?
    anyone have exchange 2007 edge server with ironport? what are you doing?

    well that wouldve been nice to know a little earlier. anyway I have ironport successfully sending mail to the edge server who sends it on to the hub transport server. right now the client access server is on the same as the hub but can be easily moved later. this is for very few people so its not like I need to off load anything as its a powerful dual core server. anyway now with the edge server I can test how effective it is versus the ironport. I'll let everyone know when you can ditch the ironport for msft's edge server. (Don't hold your breath).

  • Forced to restart Edge Server for new Users

    Our current architecture is fairly simple and has a Front-End, Edge, and Office Web Apps Server. When we add a user, we are unable to sign-in with that new user until we restart the Edge Server.
    We have tried to run "Update-CsUserDatabase" from front-end as well as "Invoke-CSManagementStoreReplication" to force replication.  We see when we run "Get-CsManagementStoreReplicationStatus" that all is up to date and
    is showing "True" and "True".
    We are also able to see the accounts when running Cs-GetUser on both servers.  However, we are unable to login with the new users we added until after we reboot the Edge Server.
    We have checked logs on the Edge server and we don't see any errrors.  On the Front-End server, the only error we see is in regards to Source "LS Data MCU" Event ID 41029.
    It just seems strange that the Replication Store appears updated but people can't login until after reboot of edge server.
    If anyone has any information about this, please respond.
    NH

    Hi,
    Did the issue happen if the Lync users login external the corporation or even happen when the Lync users login internal the corporation?
    Please double check WAC configuration (including Server FQDN spelling, certificate and so on).
    More details:
    http://lyncuc.blogspot.com/2014/06/ls-data-mcu-event-id-41029.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,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Outbound Calls stop working when Lync Edge server is offline

    All,
    We have had an issue inside our environment after one of our virtual hosts died and took out our sole Edge server, basically users could not dial out and were getting the error "Network is busy" on the client. Internal dialling worked perfectly to our Lync
    users but the users could not dial out via our Cisco CME server.
    Our configuration is a Lync Enterprise Pool with 2 servers, DB cluster and a single Lync edge server, the mediation servers are installed on our enterprise pool servers as a single server and the CME is looking at the mediation servers directly and has nothing
    pointing at the edge server.
    This issue affected internal users (as the external users were all kicked out due to the server being down), the strange thing was that you got errors in snooper about the server being unavailable when you dialled out, no idea why it did this. Even stranger
    was that the call itself was sent to the CME as a debug SIP showed traffic being attempted between the user and the number which confused me even more as my mobile actually rang for a single ring as well.
    Has anybody got any ideas as to why the Edge server would do this to internal users?
    Thanks
    James

    Lync checks the bandwith policy against the Edge server. As the Edge is not responding Lync is unable to check the policy and the call fails.
    For the time being you may want to remove the Edge from the topology, then Lync checks against the Front End server.
    I hope you do understand, that this is not a great solution, but a drastic workaround suggestion to a hidden product defect! In hidden product defect I mean Microsoft Lync document team is cynically silent and trying to cover the tracks of this product defect.
    What I would consider as a straight and honest retroactive action for the Lync document team, to add a big warning section to a) single server edge deployment page + b) the Call Admission Control caveats page on Technet:
    "Warning: PRODUCT DEFECT / PRODUCT LIMITATION comes here
    If you associate an edge server or pool to a FE pool, and enable Call Admission Control, your single / pool edge will become SINGLE POINT OF FAILURE for your entire enterprise telephony when doing outbound call attempts!
    So if outbound calls is important in your company (hell, of course it is!) then deploy at least 2x Edge servers in the same pool before enable CAC!"
    But I think that warning message is way too much to ask for, thatswhy is this 2,5 years old topic still open.

  • How can i check the office web app server(wac client) is calling custom WOPI host?

    I am getting an error when I testing my wopi host(which is the same as
    example) with Office Web app server "Sorry, there was a problem and we can't open this document.  If this happens again, try opening the document in Microsoft Word."
    1-how can find the log files of this error?
    2-how can i check the office web app server(wac client) is calling my WOPI host?
    I am not sure about cumunication between owa to wopi host. I actually dont know how to implement checkfile and getfile functions to wopi host for waiting for call back from owa client.
    Note:I am sure that office web app server is configured true. Because i test it with sharepoint 2013 and editing and viewing is working well.

    Hi,
    According to your post, my understanding is that
    CheckFileInfo is how the WOPI application gets information about the file and the permissions a user has on the file. It should have a URL that looks like this:
    HTTP://server/<...>/wopi*/files/<id>?access_token=<token>
    While CheckFileInfo provides information about a file, GetFile returns the file itself. It should have a URL that looks like this:
    HTTP://server/<...>/wopi*/files/<id>/contents?access_token=<token>
    There is a great article for your reference.
    http://blogs.msdn.com/b/officedevdocs/archive/2013/03/20/introducing-wopi.aspx
    You can also refer to the following article which is about building an Office Web Apps(OWA) WOPI Host.
    http://blogs.msdn.com/b/scicoria/archive/2013/07/22/building-an-office-web-apps-owa-wopi-host.aspx
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • How to check current input/output rate on router subintenterface via SNMP?

    How to check current input/output rate on router (2821, etc..) subintenterface via SNMP, like cacti monitoring system.
    I cant find OID to make this with snmpwalk.
    Or there is no way to check current load by this way? Only polling?
    P.S. Ethernet subinterface, of course.
    With great respect, S.A.

    Hi,
    Try to use:
    1.3.6.1.4.1.9.2.2.1.1.6 - InBitRate
    1.3.6.1.4.1.9.2.2.1.1.8 - OutBitRate
    1.3.6.1.4.1.9.2.2.1.1.28 - ifDescription

  • Hi All can anyone help me, I have a Iphone 4s and I'm currently recieving nuisance calls via a blocked number is there anyway I can stop my phone accepting blocked numbers? Cheers

    Hi all I'm Currently recieving Nuisance Calls via a Blocked number is there anyway I can stop my Iphone accepting Blocked Numbers? Thanks

    There is a way! I'm very happy to share this and hope it helps those who find themselves plagued, as I was.
    I have been getting nuisance calls for months from some muppet, who hides his phone number before he calls at 3am. I need to keep my phone on, in case any of my immediate family have an emergency. I'm sure many have the same problem, just turning off the phone is not an option. I have been to two or three shops to ask the experts and none could offer me a solution. I was on the verge of tring to jailbreak my phone or even get rid of it to get an andriod one...That's how bad things had become.
    Anyway, this is my solution, which I found by trawling through page after page on the internet, for ages and trying various other solutions first. I have an iPhone 4S and the operating system is 6.1.3 and I am in the UK, on Orange, or EE as we should now call it. I cannot promise it will help everyone, but it works for me.
    Go to Settings, Do Not Disturb and switch this on. Underneath here, go to Notifications, then Do Not Disturb again. Then Scheduled and set the times you want the restrictions to start and end. For example, I use 7pm to 8am, so that I know I won't get nuisance calls during this period, but whatever times work for you. Underneath, it says Allow calls from and you can select your favourites. If you haven't saved any of your contacts as Favourites, do so, it's very easy. Just go to contacts, open one and underneath the number there is a button to Add to favourites. Repeat for all close friends and family you want to be able to reach you at any time. All your favourites should be allowed to call. I think you can have 50 numbers in the favourites. But any unknown caller should be simply sent to voicemail.
    Apple have had some previous issues with the Do Not Disturb feature and to be honest this didnt work 100% of the time for me. If you find the same, don't give up. I suggest you do as I did at this point and use an app called Call Bliss, which seems to have cracked it. (I have NO connection to them and it's no skin off my nose if you use this app or not). There may be other apps that do the same, or even better for all I know. You have a free one day trial then it's £3 if you want to continue to use it. For me, £3 to solve the problem was money very well spent. If you need this app, download it, then do as suggested above to the point where it says Allow calls from and this time you select Bliss Exceptions. Follow the instructions in the app.
    There are two modes, I use suppress mode, which allows all calls to get through except those from unknown callers and those specified by you. I believe the other mode blocks all calls, except those you specify. Please note, the app only works when the iPhone is locked. Your lock might come on after the phone is not used for 5 minutes or so, or you can lock the phone by single clicking the on/off button (not holding it down).
    I hope this helps anyone as much as it has done me.

  • Sending emails via edge transport server fails

    Hello,
    I am using Exchange 2013 edge server in my DMZ to send emails, but it refuses to send messages to Internet. Once I create a Internet send connector on my CAS server, mails are easily sent to the Internet. My edge subscription and sync happened successfully.
    As edge server did not send any emails to the Internet, I checked the message queue on my CAS servers and I noticed that my messages are in the message queue on my CAS server. Could you please help me sort out my issue? Thanks a lot.
    Regards,
    Pooriya
    Pooriya Aghaalitari

    Hi 
    Can you tell us the last error that you can see in the message queue.
    Just run get-edgesynchronization and see the results
    What happens if you telnet to edge server fqdn from the cas server on port 25 ?
    If nothing helps i would recommend you to remove and recreate the edge subscription file  and see the results.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Different behaviour with 2 PC's when calling VIT via VI server

    Hello,
    I know there are a lot of posts about VI server and VIT on this forum, but i think my problem is not common.
    I use Labview 6.1 on Windows XP Pro. Pentium 2.6GHz 512Mo.
    My application load many instances of a template VI (vit) via VI server. All goes perfect in the development environment.
    When I generate a redistributable exe via app Builder, the application seems not to load the different instance of the vit, but without Error (I have put an error handler when loading the vit).
    The vit is included in a llb (the same as the main vi). I generate a single executable file (without external llb), i which i see the vit when opened.
    The paths are OK for the 2 environment (debug and runtime),
    vit is loaded in the app builder, and the VI Server Datasocket too. The Front Panel of the instance is opened before executing as explained in some posts.
    The most interesting (crazy?) in this story, is that my application is correctly running (a little bit slower, it's true ... )) on an old PC (Pentium II 300MHz with 128Mo) !!!
    Is there any relationship with the machine speed ?
    If somebody has an explanation ... or a solution (my client has bought a modern PC !)
    Thanks a lot.
    -Michael- (my english is so poor ...)

    Hi MickAltrel
    When I was confronted to this kind of behavior, it was due to loops that where not timed... I know it makes it very basic, but did you check that such problems are not present ?
    Doc-Doc
    Doc-Doc
    http://www.machinevision.ch
    http://visionindustrielle.ch
    Please take time to rate this answer

  • Unable to establish AV call with Lync server 2013 from internal to external remote users

    Hi,
    Instant messaging is working fine
    When trying to video call from the internal Lan to an remote external user Video call connects for 10 seconds and then drops.
    This also happens between federated sites when we initiate the call
    Internal to internal video call works
    External to external video works
    Please see logs below, can anyone advise on this issue or point me in the direction
    The logs show trying to make a video call from user on the same domain, one user on the internal network and the other user is external
    08/08/2014|11:25:44.523 4024:4344 INFO  :: End of Sending Packet - 192.168.10.4:5061 (From Local Address: 192.168.11.77:62287) 1082 bytes
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPCompression::CompressSendBuffer after compression, BytesLeft = 1082, BytesProcessed = 1082, cbDataCompressed = 465, psCompressedData = 16A01FD8
    08/08/2014|11:25:44.523 4024:4344 TRACE :: - encrypted buffer length: 533 bytes.  First 8 bytes:
    08/08/2014|11:25:44.523 4024:4344 TRACE ::  17 03 03 02 10 D0 D8 3D  :.....ÐØ=
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPTransportLayerSecurity::Send after encryption, BytesLeft = 465, BytesProcessed = 465, cbEncryptedBufSize = 533, spEncryptedBuff = 0C2B13C8
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPAsyncSocket::Send this 07B3B000, sending pbSendBuf 0C2B13C8, dwSendBufSize = 533
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPAsyncSocket::SendHelper - [0x07B3B000]
    08/08/2014|11:25:44.523 4024:4344 TRACE :: CAsyncSocketWin32::Send this 0C47D5A0, pbSendBuf 0C2B13C8, dwSendBufSize = 533, dwBytesSent = 533
    08/08/2014|11:25:44.523 4024:4344 INFO  :: REGISTER_CONTEXT(c554a20) SetAndNotify Recv(2) at State (1)
    08/08/2014|11:25:44.523 4024:4344 INFO  :: REGISTER_CONTEXT:State (1) => (2)
    08/08/2014|11:25:44.523 4024:4344 INFO  :: UCCP:NegotiatedAuthProt0x8
    08/08/2014|11:25:44.523 4024:4344 INFO  :: Function: CUccPlatform::GetMetricsDataPoints
    08/08/2014|11:25:44.523 4024:4344 ERROR :: Failure condition: 'm_spMediaManage == NULL'
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 543 (first 8):
    08/08/2014|11:25:44.594 4024:4344 TRACE ::  17 03 03 00 E0 C4 48 8E  :....àÄHŽ
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.594 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
    08/08/2014|11:25:44.594 4024:4344 INFO  :: SIP/2.0 200 OK
    Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="CEA1D9C7", snum="34", rspauth="040401ffffffffff000000000000000008fa065605ec8ffed4978ee2", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=e56751f845;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=EB010080
    Call-ID: aa4c7843a0c14678a03acc30a615c81b
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Content-Length: 0
    08/08/2014|11:25:44.594 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.594 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 314 (first 8):
    08/08/2014|11:25:44.594 4024:4344 TRACE ::  17 03 03 00 B0 42 E2 01  :....°Bâ.
    08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.595 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
    08/08/2014|11:25:44.595 4024:4344 INFO  :: SIP/2.0 200 OK
    Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="A79E32E6", snum="35", rspauth="040401ffffffffff0000000000000000435392b30686e91dd20b3120", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=457d67e5ba;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=3D631C5A
    Call-ID: 7666f05a981c4eb28c8bd44d497382a2
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Content-Length: 0
    08/08/2014|11:25:44.595 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 133 (first 8):
    08/08/2014|11:25:44.595 4024:4344 TRACE ::  17 03 03 00 80 46 FC D6  :....€FüÖ
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.595 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
    08/08/2014|11:25:44.595 4024:4344 INFO  :: SIP/2.0 200 OK
    Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="8FB2392C", snum="36", rspauth="040401ffffffffff00000000000000005c89df75c789bd815f2c87c7", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=b87f3eb341;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=447B0080
    Call-ID: 78fff0c6673c4c209914ba91221e7a71
    CSeq: 3 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Content-Length: 0
    08/08/2014|11:25:44.595 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.596 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCE28] dtor
    08/08/2014|11:25:44.597 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCEC8] dtor
    08/08/2014|11:25:44.597 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCC48] dtor
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E850
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E300
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E300
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 07B818F0
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E740
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E6B8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47EAF8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [contactCard] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C51B0C8
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 WARN  :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E960
    08/08/2014|11:25:44.597 4024:4344 INFO  :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCCE8] dtor
    08/08/2014|11:25:44.597 4024:4344 INFO  :: ~Out trxn corr-id (18680A38)
    08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><CEA1D9C7><34><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><aa4c7843a0c14678a03acc30a615c81b><2><SUBSCRIBE><sip:*****@*******.com><e56751f845><sip:*****@*******.com><EB010080><><><0><200>-length-238.
    signature:040401ffffffffff000000000000000008fa065605ec8ffed4978ee2
    08/08/2014|11:25:44.601 4024:4344 INFO  :: Trxn corr-id (184AD1C8), SIP msg corr-id (b7eb295)
    08/08/2014|11:25:44.601 4024:4344 INFO  :: ~Out trxn corr-id (184AD1C8)
    08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><A79E32E6><35><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><7666f05a981c4eb28c8bd44d497382a2><2><SUBSCRIBE><sip:*****@*******.com><457d67e5ba><sip:*****@*******.com><3D631C5A><><><0><200>-length-238.
    signature:040401ffffffffff0000000000000000435392b30686e91dd20b3120
    08/08/2014|11:25:44.601 4024:4344 INFO  :: Trxn corr-id (184AD2E0), SIP msg corr-id (e46ab49b)
    08/08/2014|11:25:44.601 4024:4344 INFO  :: ~Out trxn corr-id (184AD2E0)
    08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><8FB2392C><36><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><78fff0c6673c4c209914ba91221e7a71><3><SUBSCRIBE><sip:*****@*******.com><b87f3eb341><sip:*****@*******.com><447B0080><><><0><200>-length-238.
    signature:040401ffffffffff00000000000000005c89df75c789bd815f2c87c7
    08/08/2014|11:25:44.601 4024:4344 INFO  :: Trxn corr-id (186E42C8), SIP msg corr-id (b03cc2c3)
    08/08/2014|11:25:44.601 4024:4344 INFO  :: ~Out trxn corr-id (186E42C8)
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 373 (first 8):
    08/08/2014|11:25:44.757 4024:4344 TRACE ::  17 03 03 01 70 6D 6F B0  :....pmo°
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.757 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 959 bytes:
    08/08/2014|11:25:44.757 4024:4344 INFO  :: SIP/2.0 200 OK
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="FBA1D2E0", snum="37", rspauth="040401ffffffffff00000000000000009dbeae96bc6990dd02bfb9bd", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    From: "Administrator"<sip:*****@*******.com>;tag=50091c6b22;epid=6969679f0b
    To: <sip:*****@*******.com>;tag=AC6EA9B1891BDC84CB8DED81E89D55FF
    Call-ID: 6f1ec22d6c96481093ebcdd126f5b255
    CSeq: 3 REGISTER
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Expires: 0
    Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft-roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft-provisioning-v2
    Supported: adhoclist
    Server: RTC/5.0
    Supported: msrtc-event-categories
    Supported: ms-keepalive-deregister
    Supported: ms-userservices-state-notification
    Content-Length: 0
    08/08/2014|11:25:44.757 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 959 bytes
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.758 4024:4344 TRACE :: verified buffer: <Kerberos><FBA1D2E0><37><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><6f1ec22d6c96481093ebcdd126f5b255><3><REGISTER><sip:*****@*******.com><50091c6b22><sip:*****@*******.com><AC6EA9B1891BDC84CB8DED81E89D55FF><><><0><200>-length-261.
    signature:040401ffffffffff00000000000000009dbeae96bc6990dd02bfb9bd
    08/08/2014|11:25:44.758 4024:4344 INFO  :: Trxn corr-id (0C2E3618), SIP msg corr-id (67f10dc5)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: REGISTER_CONTEXT(c554a20) SetAndNotify Recv(3) at State (2)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: REGISTER_CONTEXT:State (2) => (3)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: SIP_REGISTER:State (3) => (0)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: UCCP:NegotiatedAuthProt0x8
    08/08/2014|11:25:44.758 4024:4344 TRACE :: CUccServerEndpoint::UpdateEndpointState - Update state from 3 to 4. Status 0. Status text (null).
    08/08/2014|11:25:44.758 4024:4344 INFO  :: CUccDnsResolverManager::Stop MR-INFO - [05026010] DNS resolver manager stopped
    08/08/2014|11:25:44.758 4024:4344 TRACE :: OUTGOING_REGISTER_TRANSACTION::ProcessSuccessfulResponse received 200 UnRegistration SUCCEEDED
    08/08/2014|11:25:44.758 4024:4344 INFO  :: ~Out trxn corr-id (0C2E3618)
    08/08/2014|11:25:44.758 4024:4344 INFO  :: CUccPlatform::WriteStreamToLog:
    08/08/2014|11:25:44.758 4024:4344 INFO  :: <?xml version="1.0" encoding="UTF-8"?>
    <root>
      <Login>
        <Info><![CDATA[Executing wws method with windows auth auth, asyncContext=16C3E478,
     context: WebRequest context@ :415272512
      MethodType:10
      ExecutionComplete? :1
      Callback@ :07AB55A4
      AsyncHResult:3d0000
      TargetUri:https://owa.lon.*******.com/EWS/Exchange.asmx
    .]]></Info>
        <Info><![CDATA[Logon success state 1 reported by user id=EWS (adjusted=EWS) on CManagedCredential[DEFAULT this=01B6C988]]]></Info>
        <ExecuteWithWindowsOrNoAuthInternal>
          <SequenceID>1.1.1</SequenceID>
          <hr>0x0</hr>
        </ExecuteWithWindowsOrNoAuthInternal>
        <SequenceID>1.1</SequenceID>
        <hr>0x0</hr>
      </Login>
    </root>
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 1125 (first 8):
    08/08/2014|11:25:44.974 4024:4344 TRACE ::  17 03 03 04 60 1A 0C FC  :....`..ü
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:44.974 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1891 bytes:
    08/08/2014|11:25:44.974 4024:4344 INFO  :: SIP/2.0 200 OK
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="4C70707C", snum="38", rspauth="040401ffffffffff000000000000000023304d3690145c9d580a26a5", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    Contact: <sip:LyncSG.dymonasia.com:5061;transport=tls>
    From: <sip:*****@*******.com>;tag=4c49873a8c;epid=6969679f0b
    To: <sip:[email protected]>;tag=925E0080
    Call-ID: 612b2be69bbe45479e2676a9c89605a3
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Record-Route: <sip:sip.dymonasia.com:5061;transport=tls;lr;ms-key-info=AAEAAQy-Hptx2bBz4bLPASfi0Q8AhsIHwfOZFhikS5I3lhvpZ6FVtoDW4nKeyfA65H-h1EPauf6Bo4PDT0Nc93YHKHPl5ZBwmxjvyetg5BZQ7yraK2EZvGpZ_bkQJlXyIw3lVlxFe-h2PmfG6lfKBZ8To-piAjW4LQLcr3Z7cic1p_GtAFi1lXOOdlcXxfUKQ_vqQjvpuZIrI7xCmomXlvM9o7Ue8lXbq3TndzkR-ghwnju0QJjj5GrUJ3Ia82bfodQYntaJaJG2bf5oUMAVJkX5_84vNcFhZRTRilUI-lC1wyChOjjWVV56ndqCVY7oiitF5HHDpfVg58-SSzRiHKhFZJKvyZtcorcM5WHuJwYNw7sdxzc2vB6hqN4vTdRjlpb1jhG35BsQ2usDMPfc8EZYGY-S5SW6C_NUgrh3Fb-_f0qcnXV92JDu55rbTy-Apz4GJk8Ivrt-PNr99CbhUoyRg_8301OIivRJAExy_xMjyIJBWkoJp7IVQjvhLL_bQWAFQn0HhJTpf13NpT-if54k7l5KbgL6K0vkcMnc8WVkgm5a_c2Dewp_RG-7jIbr5xxZXuJAxK9indqeCXnfjbIk6mhEAZI7SJmlK9_SJt0H94HutoIVwHYLarDclsdKrR7Xb-5nDPkFE4U4LjWRLf-7ff7MJJbzhbaXTE6o_t4nFFQ8kWxiRWBN2kMLChKY;ms-route-sig=bdBGMrXXhjLMmcJ4Ej8ReFZ_nqkUoCWKhFB19tji2ro5-_BAzrBqDJlQAA>
    Record-Route: <sip:pmdlonedg01.int.*******.com:5061;transport=tls;lr>
    Expires: 0
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=DirectPartner;ms-ep-fqdn=pmdlonedg01.int.*******.com;ms-source-verified-user=verified;ms-source-network=federation
    Record-Route: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls;opaque=state:F:Ci.R13cb00;lr;ms-route-sig=bc4_1nrdDL4-KX7KrdReLOthlr4n7DTIcsDrkM0bP4gGNYk0BjUtG1CwAA>
    08/08/2014|11:25:44.974 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1891 bytes
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:44.974 4024:4344 TRACE :: verified buffer: <Kerberos><4C70707C><38><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><612b2be69bbe45479e2676a9c89605a3><2><SUBSCRIBE><sip:*****@*******.com><4c49873a8c><sip:[email protected]><925E0080><><><0><200>-length-233.
    signature:040401ffffffffff000000000000000023304d3690145c9d580a26a5
    08/08/2014|11:25:44.974 4024:4344 INFO  :: Trxn corr-id (184AD3F8), SIP msg corr-id (e3f780cb)
    08/08/2014|11:25:44.974 4024:4344 INFO  :: ~Out trxn corr-id (184AD3F8)
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 277 (first 8):
    08/08/2014|11:25:45.288 4024:4344 TRACE ::  17 03 03 01 10 3B 87 16  :.....;‡.
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
    08/08/2014|11:25:45.288 4024:4344 INFO  :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1888 bytes:
    08/08/2014|11:25:45.288 4024:4344 INFO  :: SIP/2.0 200 OK
    Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="59667E0A", snum="39", rspauth="040401ffffffffff00000000000000002641ec9a3a4c088b301bcf5e", targetname="sip/PMDLONLYC01.int.*******.com",
    realm="SIP Communications Service", version=4
    Contact: <sip:LyncSG.dymonasia.com:5061;transport=tls>
    From: <sip:*****@*******.com>;tag=04814352f9;epid=6969679f0b
    To: <sip:[email protected]>;tag=3F0E0080
    Call-ID: 8115c934d1fd446eb7d034c4fc773ec0
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
    Record-Route: <sip:sip.dymonasia.com:5061;transport=tls;lr;ms-key-info=AAEAAQy-Hptx2bBz4bLPASfi0Q8AhsIHwfOZFhikS5I3lhvpZ6FVtoDW4nKeyfA65H-h1EPauf6Bo4PDT0Nc93YHKHPl5ZBwmxjvyetg5BZQ7yraK2EZvGpZ_bkQJlXyIw3lVlxFe-h2PmfG6lfKBZ8To-piAjW4LQLcr3Z7cic1p_GtAFi1lXOOdlcXxfUKQ_vqQjvpuZIrI7xCmomXlvM9o7Ue8lXbq3TndzkR-ghwnju0QJjj5GrUJ3Ia82bfodQYntaJaJG2bf5oUMAVJkX5_84vNcFhZRTRilUI-lC1wyChOjjWVV56ndqCVY7oiitF5HHDpfVg58-SSzRiHKhFZJKvyZtcorcM5WHuJwYNw7sdxzc2vB6hqN4vTdRjlpb1jhG35BsQ2usDMPfc8EZYGY-S5SW6C_NUgrh3Fb-_f0qcnXV92JDu55rbTy-Apz4GJk8Ivrt-PNr99CbhUoyRg_8301OIivRJAExy_xMjyIJBWkoJp7IVQjvhLL_bQWAFQn0HhJTpf13NpT-if54k7l5KbgL6K0vkcMnc8WVkgm5a_c2Dewp_RG-7jIbr5xxZXuJAxK9indqeCXnfjbIk6mhEAZI7SJmlK9_SJt0H94HutoIVwHYLarDclsdKrR7Xb-5nDPkFE4U4LjWRLf-7ff7MJJbzhbaXTE6o_t4nFFQ8kWxiRWBN2kMLChKY;ms-route-sig=bd5A_eMqoaHs_fuYP-5aSBoYbANCe_p5RWv6n6yajgyfxebrRuBqDJlQAA>
    Record-Route: <sip:pmdlonedg01.int.*******.com:5061;transport=tls;lr>
    Expires: 0
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=DirectPartner;ms-ep-fqdn=pmdlonedg01.int.*******.com;ms-source-verified-user=verified;ms-source-network=federation
    Record-Route: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls;opaque=state:F:Ci.R13cb00;lr;ms-route-sig=bcFuhIALmH85OaoJh25uPG5Y8-bgabM97QpJ5ypCK7x_cYXXQWUtG1CwAA>
    08/08/2014|11:25:45.288 4024:4344 INFO  :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1888 bytes
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
    08/08/2014|11:25:45.288 4024:4344 TRACE :: verified buffer: <Kerberos><59667E0A><39><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><8115c934d1fd446eb7d034c4fc773ec0><2><SUBSCRIBE><sip:*****@*******.com><04814352f9><sip:[email protected]><3F0E0080><><><0><200>-length-230.
    signature:040401ffffffffff00000000000000002641ec9a3a4c088b301bcf5e
    08/08/2014|11:25:45.289 4024:4344 INFO  :: Trxn corr-id (184AD510), SIP msg corr-id (42a27507)
    08/08/2014|11:25:45.289 4024:4344 INFO  :: ~Out trxn corr-id (184AD510)
    08/08/2014|11:25:49.397 4024:4344 TRACE :: MULTIPARTY_SESSION::RemoveFromLinkedList[17060C50] removed from linked list

    As with the original issue, your problem is likely with the Edge server. The first thing I would do is check all of your ports and DNS settings.
    Remember that Edge may use somewhat unique ports for AV if you, or the federation target, used a single IP address. If you haven't, see if you have that unique port open on the firewall. If you used a single IP address, ensure that the federation target
    has the correct port open also.

  • Can you use a self signed certificate on an external Edge Server interface?

    Hi,
    I have a small lab deployment for evaluation purposes. The Lync FE server works great for internal users. I have now added an Edge server. For the internal interface, I have a self signed certificate from our internal CA. (no problem there) For the external
    interface, I have a self signed certificate from our own external CA. I have installed the cert on the client machine of the external user and installed it for trusted operation. I have used the RUCT and digicert tools to prove that the external self signed
    cert is valid (root and intermediate have been checked for validity).
    At first, when logging in from the Lync 2013 client on the external users machine, I would get an error from Lync about the cert being untrusted. I have now fixed that error by adding it as trusted. At this point, there are no errors or warnings in the Event
    Viewer (in the application or system logs) However, I receive the following error from the Lync client, "Were having trouble connecting to the server... blah, blah".
    Here is my question. Does the Microsoft Lync 2013 client and/or the "testconnectivity.microsoft.com" tool specifically prevent or forbid the use of self signed certificates on the external interface of an Edge server? They seem too.
    I can tell if the certificate is my problem or something else. Any ideas on how to trouble shoot this?
    Thx

    Drago,
    Thanks for all your help. I got it working.
    My problem with the Lync client error, "Were having trouble connecting to the server... blah, blah", was NOT a certificate error. It was a problem with my Lync Server Topology. (My sip default domain needed to match my user login domain.)
    Let me update everyone about self-signed certificates:
    YES, you can self-sign a certificate on your external edge server. It is a pain, but possible.
    I have a self signed certificate from our own external CA. I have installed the cert on the client machine of the external user for trusted operation. I have used the RUCT and digicert tools to prove that the external self signed cert is valid (root and
    intermediate have been checked for validity).
    Here are my notes:
    Create/enable your own external Certificate Authority (CA) running on a server with internet access. 
    On the Lync Edge Server, run the "Lync Server 2013 - Development Wizard".
    Click "Install or Update Lync Server System". (Lync will automatically determine its deployment state)
    You should have already completed: Step1 and Step 2.
    Run or Run Again "Step 3: Request, Install or Assign Certificates".
    Install the "Edge internal" certificate.
    Click "Request" button to run the "Certificate Request" wizard.
    You use can "Send the request immediately to an online certificate authority" option to connect to your internal CA, and create the certificate.
    Once the certificate has been created, use "Import Certificate" to import it.
    Once imported, on the Edge Server, go to: (Control Panel -> Administrative Tools -> Internet Information Services (ISS) Manager -> Server Certificates -> Complete Certificate Request...
    In the Lync deployment wizard - Certificate Wizard, "Assign the newly imported "edge internal" certificate.
    Install the "Edge External" certificate (public Internet).
    Click the "Request" button to run the "Certificate Request" wizard.
    Press "next"
    Select "Prepare the request now, but send it later (offline certificate request).
    Supply the "Certificate Request File" name and location. (You will need the file later. It should have the file extension ".req").
    Click next on the "Specify Alternate Certificate Template". (which means you are using the default options)
    Give it a Friendly Name. Bit Length = 2048. I selected "Mark the certificate's private key as exportable" option.
    Fill in the organization info.
    Fill in the Geographical Information.
    The wizard should automatically fill-in the "Subject name:" and "subject alternative name:' fields.
    Select your "Configured SIP domains"
    "Configure Additional Subject Alternative Names" if you want. Otherwise, next.
    Verify the "certificate Request Summary". Click next.
    Run the wizard script to "Complete". The wizard will create a file containing the certificate request with the file extension ".req". (Let's assume the file name is "myCert.req")
     Move your myCert.req file to your external CA. Have your CA issue the cert (based on myCert.req) and export the new cert to a file. I save it as a P7B certificate. (Let's call it "ExternalCert.p7b")
    In the Lync Deployment wizard - Certificate Wizard, click on "Import Certificate" for ExternalCert.p7b.
    Once imported, on the Edge Server, go to: (Control Panel -> Administrative Tools -> Internet Information Services (ISS) Manager -> Server Certificates -> Complete Certificate Request... (assign it a friendly name. Let's say "EXTERNAL-EDGE")
    For the "External Edge certificate (public Internet), click "Assign".
    The "Certificate Assignment" wizard will run.
    Click next.
    From the list, select your cert "EXTERNAL-EDGE".
    Finish the wizard to "complete".
    You are finished on the server.
    Move the "ExternalCert.p7b" file to the machine running the lync client. Install the cert via the "Certificate Import Wizard".
    When installing it to a particular Certificate Store, select the "Place all certificates in the following store" option.
    Browse
    Select "Trusted Root Certification Authorities"
    Finish the wizard.

  • Edge server messages issue

    Hi everyone, 
    After spending hours of googling and configuring Im going to try this forum out. 
    My Lync 2013 standard configuration consists of one Front End and one Edge server. Internally on our network or for users connecting via VPN everything works fine and well. For users logging in externally things aren't working that well. 
    Issue 1
    Users can sign in. They look signed in to themselves and to others online. They can send messages to other users but they messages sent to them aren't received. One of the messages I can find while using the debug tool is: 
    Text: Routing error occurred; check Result-Code field for more information
    Result-Code: 0xc3e93f30 SIPPROXY_E_INVALID_EDGE_PROXY_HEADER
    Issue 2
    Some users who sign in externally appear as offline to themselves but are seen as online. When they try to change their status to Online nothing happens. 
    Can someone give me some hints on what I shall do next to troubleshoot this. 
    BR
    Daniel

    I guess I am to much of a rookie when it comes to this, however here is the log from the client sending. Not sure what this tells me: 
    <categories xmlns="http://schemas.microsoft.com/2006/09/sip/categories" uri="sip:[email protected]"><category xmlns="http://schemas.microsoft.com/2006/09/sip/categories" name="calendarData"
    instance="2468366808" publishTime="2014-09-16T16:21:09.560">
    <calendarData xmlns="http://schemas.microsoft.com/2006/09/sip/calendarData" mailboxID="Daniel. @ourdomain.com"><freeBusy startTime="2014-09-14T22:00:00Z" granularity="PT15M" encodingVersion="2">BQAAAAAAAAAAAAAAAAAgQAAAAIAkSZIkSQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgQBIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgQBIAAJIEAJIEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgQAAAAAAAAAAgAQAAAAAAAAAAAAAAAA==</freeBusy></calendarData>
    </category>
    <category xmlns="http://schemas.microsoft.com/2006/09/sip/categories" name="calendarData" instance="0" publishTime="2014-09-16T16:21:09.560">
    <calendarData xmlns="http://schemas.microsoft.com/2006/09/sip/calendarData" mailboxID="Daniel. @ourdomain.com"><WorkingHours xmlns="http://schemas.microsoft.com/exchange/services/2006/types"><TimeZone><Bias>-60</Bias><StandardTime><Bias>0</Bias><Time>03:00:00</Time><DayOrder>5</DayOrder><Month>10</Month><DayOfWeek>Sunday</DayOfWeek></StandardTime><DaylightTime><Bias>-60</Bias><Time>02:00:00</Time><DayOrder>5</DayOrder><Month>3</Month><DayOfWeek>Sunday</DayOfWeek></DaylightTime></TimeZone><WorkingPeriodArray><WorkingPeriod><DayOfWeek>Monday
    Tuesday Wednesday Thursday Friday</DayOfWeek><StartTimeInMinutes>480</StartTimeInMinutes><EndTimeInMinutes>1020</EndTimeInMinutes></WorkingPeriod></WorkingPeriodArray></WorkingHours></calendarData>
    </category>
    <category xmlns="http://schemas.microsoft.com/2006/09/sip/categories" name="calendarData" instance="1394624984" publishTime="2014-09-16T16:21:09.560">
    <calendarData xmlns="http://schemas.microsoft.com/2006/09/sip/calendarData" mailboxID="Daniel. @ourdomain.com"><freeBusy startTime="2014-09-14T22:00:00Z" granularity="PT15M" encodingVersion="2">AAAAAAAAAAAAggAAoKqqqgAAAAAAAAAAAAAAAAAAAAAAggoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAggoAqgCqAAAAAAAAAAAAAAAAAAAAAAAAggAAAAAACgAAAAAAAAAA</freeBusy></calendarData>
    </category>
    </categories>
    09/16/2014|18:21:09.583 2AF0:2B1C INFO  :: End of Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 2882 bytes
    09/16/2014|18:21:09.583 2AF0:2B1C TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x12B8E258]
    09/16/2014|18:21:09.583 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12B8E258]
    09/16/2014|18:21:09.583 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BC4198]
    09/16/2014|18:21:09.583 2AF0:2B1C TRACE :: verified buffer: <TLS-DSK><F048213C><169><SIP Communications Service><lync-01-vm.ourdomain.com><b592d284b76c4f7f80b26e12da2d5991><28><BENOTIFY><sip:[email protected]><F16D0080><sip:[email protected]><9f2907c059><><><>-length-193.
    signature:96980e61ea9cc654648c28a9134cba52cbcc48cc
    09/16/2014|18:21:09.583 2AF0:2B1C TRACE :: AddTag 132B7C88-<sip:[email protected]>;tag=F16D0080, local=sip:[email protected]
    09/16/2014|18:21:09.583 2AF0:2B1C INFO  :: In trxn corr-id (1448CDA0)
    09/16/2014|18:21:09.583 2AF0:2B1C INFO  :: Trxn corr-id (1448CDA0), SIP msg corr-id (463eaa79)
    09/16/2014|18:21:09.583 2AF0:2B1C INFO  :: ~In trxn corr-id (1448CDA0)
    09/16/2014|18:21:09.583 2AF0:2B1C INFO  :: Created Async workitem 145EAA20, txn timeout 5000, time sensitive 1, txn (15541090)
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccNotificationDispatcher::RegisterForUpdates - [0x0CFB4408]
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccLogicalSubscription::ProcessCategoryDataCollection - Presentity object found for [sip:[email protected]], this 0D2A74B0
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccGenericCategoryInstance::FireModifiedEvent - [0x140F1000] - calendarData
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccNotificationDispatcher::RegisterForUpdates - [0x0CFB4408]
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccGenericCategoryInstance::FireModifiedEvent - [0x143D8688] - calendarData
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccGenericCategoryInstance::FireModifiedEvent - [0x12D97F88] - calendarData
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccLogicalSubscription::ProcessCategoryDataCollection - Presentity object found for [sip:[email protected]], this 0D2A77D0
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccGenericCategoryInstance::FireModifiedEvent - [0x140EFE48] - calendarData
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccNotificationDispatcher::RegisterForUpdates - [0x0CFB4408]
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccGenericCategoryInstance::FireModifiedEvent - [0x143D8328] - calendarData
    09/16/2014|18:21:09.584 2AF0:2B1C TRACE :: CUccGenericCategoryInstance::FireModifiedEvent - [0x140EF788] - calendarData
    09/16/2014|18:21:09.584 2AF0:2B1C INFO  :: deleting Async workitem 145EAA20
    09/16/2014|18:21:18.007 2AF0:2B1C TRACE :: CUccContainerContext::FindContainerMember [0D285DF0] - FindContainerMember '' suceeded. hr = 0x0
    09/16/2014|18:21:18.007 2AF0:2B1C TRACE :: CUccContainerMember::IsInContainer - Member 12D91E08 ('null uri') is not in container 32000
    09/16/2014|18:21:18.007 2AF0:2B1C TRACE :: CUccContainerMember::IsInContainer - Member 12D91E08 ('null uri') is not in container 400
    09/16/2014|18:21:18.007 2AF0:2B1C TRACE :: CUccContainerMember::IsInContainer - Member 12D91E08 ('null uri') is not in container 300
    09/16/2014|18:21:18.007 2AF0:2B1C TRACE :: CUccContainerMember::IsInContainer - Member 12D91E08 ('null uri') is not in container 200
    09/16/2014|18:21:18.007 2AF0:2B1C TRACE :: CUccContainerMember::IsInContainer - Member 12D91E08 ('null uri') is not in container 100
    09/16/2014|18:21:18.203 2AF0:2B1C TRACE :: TEL_URL::Convert - [0x130C1A60]
    09/16/2014|18:21:18.203 2AF0:2B1C TRACE :: TEL_URL::Convert - [0x130C1A60]
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: New mpss created: 12FF1D50, stack=0AB840B0, 18
    09/16/2014|18:21:21.459 2AF0:2B1C INFO  :: MSP.SetMultipartySsnRole[12FF1D50] 0->1
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::SetConnectParams[12FF1D50] n=(null), [email protected]
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: CUccSession::InternalAddParticipant - Adding participant sip:[email protected]
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::AddParty - Enter participant: sip:[email protected], this=sip:[email protected], RM=(null)
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::AddParty SessionState 0, m_fAddedFirstParty 0, participant: sip:[email protected], this 12FF1D50
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: new InviteWorkitem for sip:[email protected], 12EE7AA8, mpss=12FF1D50
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: New SipCall:142CD008, dialog=142CD060, first=1, typ=2, mpss=12FF1D50, redir=00000000
    09/16/2014|18:21:21.459 2AF0:2B1C INFO  :: There is no Service-Route to copy
    09/16/2014|18:21:21.459 2AF0:2B1C INFO  :: call.SetRemote[142CD008] sip:[email protected]:(null);(null),0,0
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: PV[130C7740]-Add(142CD008,0)
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: LogMSP-130C76E8 AddMIM(12EE7AA8), state=0
    09/16/2014|18:21:21.459 2AF0:2B1C TRACE :: SIP_CALL::SetLocalAndRemoteForConnect - enter LocalDisplayName:  
    09/16/2014|18:21:21.459 2AF0:2B1C INFO  :: SIP_CALL::SetLocalAndRemoteForConnect - Call.Invite[142CD008]0:sip:[email protected]==>sip:[email protected]:, RM=(null)
    09/16/2014|18:21:21.460 2AF0:2B1C INFO  :: SIP_MSG_PROCESSOR::OnRequestConnectionConnectComplete - Enter this: 142CD060, callid=76aecefde32f48c5805ce1b5fdabc302, ErrorCode: 0x0
    09/16/2014|18:21:21.460 2AF0:2B1C TRACE :: IMSESSION::SetRequestURIRemoteAndRequestDestination[142CD008] - call set RequestURI to : sip:[email protected]
    09/16/2014|18:21:21.460 2AF0:2B1C INFO  :: Outgoing 142CD060-<sip:[email protected]>, local=sip:[email protected]
    09/16/2014|18:21:21.460 2AF0:2B1C INFO  :: call.SetRemote[142CD008] sip:[email protected]:(null);(null)
    09/16/2014|18:21:21.460 2AF0:2B1C TRACE :: SIP_CALL::CreateOutgoingInviteTransaction[142CD008], first=1, headers=0, cookie=0
    09/16/2014|18:21:21.464 2AF0:2B1C INFO  :: Out trxn corr-id (12BF1B20)
    09/16/2014|18:21:21.464 2AF0:2B1C TRACE :: call.SetState[142CD008]  SIP_CALL_STATE_IDLE-->SIP_CALL_STATE_CONNECTING for sip:[email protected], stack=0AB840B0
    09/16/2014|18:21:21.464 2AF0:2B1C TRACE :: SIP_CALL::NotifyCallStateChange[142CD008] : CallState : 3 StatusCode: 0, s=3
    09/16/2014|18:21:21.464 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::NotifyCallChange[12FF1D50]- call-leg:142CD008, Callstate:3 StatusCode:0 SessionState:0
    09/16/2014|18:21:21.464 2AF0:2B1C INFO  :: CUccMultipartySession::NotifyPartyChange[12EFA574] - for participant [sip:[email protected]]
    09/16/2014|18:21:21.464 2AF0:2B1C TRACE :: PV[130C7740]-Update(142CD008,0->3)
    09/16/2014|18:21:21.464 2AF0:2B1C TRACE :: [130C7730]msp.updateCall(142CD008):0->3
    09/16/2014|18:21:21.464 2AF0:2B1C TRACE :: MSP.UpdateState[130C7730]-State 0->3, call(0->3)
    09/16/2014|18:21:21.464 2AF0:2B1C INFO  :: MSP.SetState[12FF1D50] SIP_CALL_STATE_IDLE->SIP_CALL_STATE_CONNECTING, local=sip:[email protected]
    09/16/2014|18:21:21.464 2AF0:2B1C INFO  :: CUccSessionParticipant::InternalSetState [016FE04C] - state: 0x1->0x2
    09/16/2014|18:21:21.464 2AF0:2B1C INFO  :: Trxn corr-id (12BF1B20), SIP msg corr-id (fa8f2075)
    09/16/2014|18:21:21.465 2AF0:2B1C INFO  :: Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 2288 bytes:
    09/16/2014|18:21:21.465 2AF0:2B1C INFO  :: INVITE sip:[email protected] SIP/2.0
    Via: SIP/2.0/TLS xxx.31.20.13:50616
    Max-Forwards: 70
    From: <sip:[email protected]>;tag=5c84c0c81d;epid=b934ea0eac
    To: <sip:[email protected]>
    Call-ID: 76aecefde32f48c5805ce1b5fdabc302
    CSeq: 1 INVITE
    Contact: <sip:[email protected];opaque=user:epid:pgJmFnrHnVGiFDHAR8HwBAAA;gruu>
    User-Agent: UCCAPI/15.0.4649.1000 OC/15.0.4649.1000 (Microsoft Lync)
    Supported: ms-dialog-route-set-update
    Supported: ms-embedded-first-message
    Supported: ms-delayed-accept
    Supported: ms-renders-isf
    Supported: ms-renders-gif
    Supported: ms-renders-mime-alternative
    Ms-Conversation-ID: Ac/Ryj6NBHiQrlr+S9mg4j0SgIRpnA==
    Supported: timer
    Supported: histinfo
    Supported: ms-safe-transfer
    Supported: ms-sender
    Supported: ms-early-media
    Roster-Manager: sip:[email protected]
    EndPoints: <sip:[email protected]>, <sip:[email protected]>
    Supported: com.microsoft.rtc-multiparty
    ms-keep-alive: UAC;hop-hop=yes
    Allow: INVITE, BYE, ACK, CANCEL, INFO, MESSAGE, UPDATE, REFER, NOTIFY, BENOTIFY
    ms-subnet: 172.31.20.0
    Supported: ms-conf-invite
    Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="49D66A12", targetname="lync-01-vm.ourdomain.com", crand="8b1102eb", cnum="137", response="8820736f469fd0b22ce7ad42aba49243a2de44e6"
    Content-Type: application/sdp
    Content-Length: 244
    v=0
    o=- 0 0 IN IP4 xxx.31.20.13
    s=session
    c=IN IP4 xxx.31.20.13
    t=0 0
    m=message 5060 sip null
    a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite 
    09/16/2014|18:21:21.465 2AF0:2B1C INFO  :: End of Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 2288 bytes
    09/16/2014|18:21:21.465 2AF0:2B1C TRACE :: CSIPCompression::CompressSendBuffer after compression, BytesLeft = 2288, BytesProcessed = 2288, cbDataCompressed = 1247, psCompressedData = 12BF7B40 
    09/16/2014|18:21:21.465 2AF0:2B1C TRACE :: - encrypted buffer length: 1301 bytes.  First 8 bytes:
    09/16/2014|18:21:21.465 2AF0:2B1C TRACE :: 17 03 03 05 10 5A 53 9A  :.....ZSš
    09/16/2014|18:21:21.465 2AF0:2B1C TRACE :: CSIPTransportLayerSecurity::Send after encryption, BytesLeft = 1247, BytesProcessed = 1247, cbEncryptedBufSize = 1301, spEncryptedBuff = 0D102060 
    09/16/2014|18:21:21.465 2AF0:2B1C TRACE :: CSIPAsyncSocket::Send this 12BD6C28, sending pbSendBuf 0D102060, dwSendBufSize = 1301
    09/16/2014|18:21:21.465 2AF0:2B1C TRACE :: CSIPAsyncSocket::SendHelper - [0x12BD6C28]
    09/16/2014|18:21:21.465 2AF0:2B1C TRACE :: CAsyncSocketWin32::Send this 0D237310, pbSendBuf 0D102060, dwSendBufSize = 1301, dwBytesSent = 1301
    09/16/2014|18:21:21.537 2AF0:2B1C TRACE :: TEL_URL::Convert - [0x130C1A60]
    09/16/2014|18:21:21.537 2AF0:2B1C TRACE :: TEL_URL::Convert - [0x130C1A60]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BD6C30]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: SECURE_SOCKET: decrypting buffer size: 634 (first 8):
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: 17 03 03 01 40 DF 5C 07  :....@ß\.
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0D2A5CF8]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0AC7CC58]
    09/16/2014|18:21:21.538 2AF0:2B1C INFO  :: Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 564 bytes:
    09/16/2014|18:21:21.538 2AF0:2B1C INFO  :: SIP/2.0 100 Trying
    Authentication-Info: TLS-DSK qop="auth", opaque="49D66A12", srand="D0154E53", snum="170", rspauth="eb5c42d470524d43c038a78f56c89f6dc4b18f61", targetname="lync-01-vm.ourdomain.com", realm="SIP
    Communications Service", version=4
    From: "sendingClient"<sip:[email protected]>;tag=5c84c0c81d;epid=b934ea0eac
    To: <sip:[email protected]>
    Call-ID: 76aecefde32f48c5805ce1b5fdabc302
    CSeq: 1 INVITE
    Via: SIP/2.0/TLS xxx.31.20.13:50616;ms-received-port=50616;ms-received-cid=3100
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting
    Content-Length: 0
    09/16/2014|18:21:21.538 2AF0:2B1C INFO  :: End of Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 564 bytes
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x12B8E258]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12B8E258]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BC4198]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: SECURE_SOCKET: decrypting buffer size: 309 (first 8):
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: 17 03 03 01 30 36 5B C9  :....06[É
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0D2A5CF8]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0AC7CC58]
    09/16/2014|18:21:21.538 2AF0:2B1C INFO  :: Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 696 bytes:
    09/16/2014|18:21:21.538 2AF0:2B1C INFO  :: SIP/2.0 101 Progress Report
    Authentication-Info: TLS-DSK qop="auth", opaque="49D66A12", srand="1395D21A", snum="171", rspauth="5c0866000831ed9bb4e30c71072cc3a4306cf8a2", targetname="lync-01-vm.ourdomain.com", realm="SIP
    Communications Service", version=4
    Content-Length: 0
    Via: SIP/2.0/TLS xxx.31.20.13:50616;ms-received-port=50616;ms-received-cid=3100
    From: "sendingClient"<sip:[email protected]>;tag=5c84c0c81d;epid=b934ea0eac
    To: <sip:[email protected]>
    Call-ID: 76aecefde32f48c5805ce1b5fdabc302
    CSeq: 1 INVITE
    ms-diagnostics: 13004;reason="Request was proxied to one or more registered endpoints";source="LYNC-01-VM.ourdomain.com";Count="1";appName="InboundRouting"
    Server: InboundRouting/5.0.0.0
    09/16/2014|18:21:21.538 2AF0:2B1C INFO  :: End of Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 696 bytes
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x12B8E258]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12B8E258]
    09/16/2014|18:21:21.538 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BC4198]
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: verified buffer: <TLS-DSK><D0154E53><170><SIP Communications Service><lync-01-vm.ourdomain.com><76aecefde32f48c5805ce1b5fdabc302><1><INVITE><sip:[email protected]><5c84c0c81d><sip:[email protected]><><><><><100>-length-189.
    signature:eb5c42d470524d43c038a78f56c89f6dc4b18f61
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: Trxn corr-id (12BF1B20), SIP msg corr-id (fa8f2075)
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: call.SetState[142CD008]  SIP_CALL_STATE_CONNECTING-->SIP_CALL_STATE_ALERTING for sip:[email protected], stack=0AB840B0
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: SIP_CALL::NotifyCallStateChange[142CD008] : CallState : 5 StatusCode: ef0064, s=5
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::NotifyCallChange[12FF1D50]- call-leg:142CD008, Callstate:5 StatusCode:ef0064 SessionState:3
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: CUccMultipartySession::NotifyPartyChange[12EFA574] - for participant [sip:[email protected]]
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: CUccSessionParticipant::InternalSetState [016FD98C] - state: 0x1->0x2
    09/16/2014|18:21:21.542 2AF0:2B1C ERROR :: SIP_MESSAGE::GetHeader: HRESULT API failed: 80ee0005 = hr. GetHeader
    09/16/2014|18:21:21.542 2AF0:2B1C WARN  :: header not present
    09/16/2014|18:21:21.542 2AF0:2B1C ERROR :: SIP_MESSAGE::GetHeader: HRESULT API failed: 80ee0005 = hr. GetHeader
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: PV[130C7740]-Update(142CD008,3->5)
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: [130C7730]msp.updateCall(142CD008):3->5
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: MSP.UpdateState[130C7730]-State 3->5, call(3->5)
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: MSP.SetState[12FF1D50] SIP_CALL_STATE_CONNECTING->SIP_CALL_STATE_ALERTING, local=sip:[email protected]
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: CUccSessionParticipant::InternalSetState [016FE04C] - state: 0x2->0x2
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: verified buffer: <TLS-DSK><1395D21A><171><SIP Communications Service><lync-01-vm.ourdomain.com><76aecefde32f48c5805ce1b5fdabc302><1><INVITE><sip:[email protected]><5c84c0c81d><sip:[email protected]><><><><><101>-length-189.
    signature:5c0866000831ed9bb4e30c71072cc3a4306cf8a2
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: Trxn corr-id (12BF1B20), SIP msg corr-id (fa8f2075)
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: call.SetState[142CD008]  SIP_CALL_STATE_ALERTING-->SIP_CALL_STATE_ALERTING for sip:[email protected], stack=0AB840B0
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: SIP_CALL::NotifyCallStateChange[142CD008] : CallState : 5 StatusCode: ef0065, s=5
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::NotifyCallChange[12FF1D50]- call-leg:142CD008, Callstate:5 StatusCode:ef0065 SessionState:5
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: CUccMultipartySession::NotifyPartyChange[12EFA574] - for participant [sip:[email protected]]
    09/16/2014|18:21:21.542 2AF0:2B1C ERROR :: SIP_MESSAGE::GetHeader: HRESULT API failed: 80ee0005 = hr. GetHeader
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: PV[130C7740]-Update(142CD008,5->5)
    09/16/2014|18:21:21.542 2AF0:2B1C TRACE :: [130C7730]msp.updateCall(142CD008):5->5
    09/16/2014|18:21:21.542 2AF0:2B1C INFO  :: CUccSessionParticipant::InternalSetState [016FE04C] - state: 0x2->0x2
    09/16/2014|18:21:33.699 2AF0:2B1C INFO  :: ~In trxn corr-id (1319D440)
    09/16/2014|18:22:51.527 2AF0:2B1C INFO  :: CSIPWhiteSpaceKeepAlive::OnTimerExpire 12BC4198
    09/16/2014|18:22:51.527 2AF0:2B1C INFO  :: Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 16 bytes:
    09/16/2014|18:22:51.527 2AF0:2B1C INFO  :: ==== WHITESPACE SENT ====
    09/16/2014|18:22:51.527 2AF0:2B1C TRACE :: CSIPCompression::CompressSendBuffer after compression, BytesLeft = 16, BytesProcessed = 16, cbDataCompressed = 11, psCompressedData = 1459B1B8 
    09/16/2014|18:22:51.527 2AF0:2B1C TRACE :: - encrypted buffer length: 69 bytes.  First 8 bytes:
    09/16/2014|18:22:51.527 2AF0:2B1C TRACE :: 17 03 03 00 40 95 61 8D  :....@•a
    09/16/2014|18:22:51.527 2AF0:2B1C TRACE :: CSIPTransportLayerSecurity::Send after encryption, BytesLeft = 11, BytesProcessed = 11, cbEncryptedBufSize = 69, spEncryptedBuff = 14031058 
    09/16/2014|18:22:51.527 2AF0:2B1C TRACE :: CSIPAsyncSocket::Send this 12BD6C28, sending pbSendBuf 14031058, dwSendBufSize = 69
    09/16/2014|18:22:51.527 2AF0:2B1C TRACE :: CSIPAsyncSocket::SendHelper - [0x12BD6C28]
    09/16/2014|18:22:51.527 2AF0:2B1C TRACE :: CAsyncSocketWin32::Send this 0D237310, pbSendBuf 14031058, dwSendBufSize = 69, dwBytesSent = 69
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BD6C30]
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: SECURE_SOCKET: decrypting buffer size: 885 (first 8):
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: 17 03 03 03 70 B4 21 CC  :....p´!Ì
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0D2A5CF8]
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0AC7CC58]
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 1259 bytes:
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: UPDATE sip:xxx.31.20.13:50616;transport=tls;ms-opaque=c22a6edbb9;ms-received-cid=3100;grid SIP/2.0
    Record-Route: <sip:lync-01-vm.ourdomain.com:5061;transport=tls;opaque=state:T:F:Ci.R3100;lr;ms-route-sig=aaurJ8x4E_rVQ1kQKv3Xx8jUDb7SQoWX13Nqvow5odbKg5AigD1H2BRgAA>;tag=BD3F60C9FDE56A9F9EFC3FBF063C88B3
    Via: SIP/2.0/TLS xxx.31.20.13:5061;branch=z9hG4bKA3F8C278.03280239C018B5A3;branched=FALSE;ms-internal-info="abLT5zP8f8TNfBnWARBvEvat313QGOkIcu9HMiwukC2Xs5AigDr2UUrQAA"
    Authentication-Info: TLS-DSK qop="auth", opaque="49D66A12", srand="60EA270A", snum="172", rspauth="bd101536f5f16100099f10dd6e7dec1e4795d129", targetname="lync-01-vm.ourdomain.com", realm="SIP
    Communications Service", version=4
    Max-Forwards: 69
    Via: SIP/2.0/TLS xxx.9.164.40:50623;branch=z9hG4bK5ebad57d;ms-received-port=50623;ms-received-cid=3300
    FROM: <sip:[email protected]>;epid=74AF521DBE;tag=f6947d76d
    TO: <sip:[email protected]>;epid=b934ea0eac;tag=27fd721b0d
    CSEQ: 45 UPDATE
    CALL-ID: 903004e75f584fac8a9447ae694882ba
    CONTACT: <sip:[email protected];gruu;opaque=srvr:PersistentChat:ODmUIdRivFWZkXE_Oo8DvQAA>
    CONTENT-LENGTH: 0
    SUPPORTED: timer
    SUPPORTED: gruu-10
    USER-AGENT: RTCC/5.0.0.0 PCS/5.0.8308.420
    Session-Expires: 300
    Min-SE: 90
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: End of Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 1259 bytes
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x12B8E258]
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12B8E258]
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BC4198]
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: verified buffer: <TLS-DSK><60EA270A><172><SIP Communications Service><lync-01-vm.ourdomain.com><903004e75f584fac8a9447ae694882ba><45><UPDATE><sip:[email protected]><f6947d76d><sip:[email protected]><27fd721b0d><><><>-length-216.
    signature:bd101536f5f16100099f10dd6e7dec1e4795d129
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: In trxn corr-id (13240828)
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: Trxn corr-id (13240828), SIP msg corr-id (bab7de23)
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: SIP_CALL::StopSessionExpiresTimer disable session timer
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: Remote 12D54B60-<sip:[email protected]>;epid=74AF521DBE;tag=f6947d76d, local=sip:[email protected]
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: Trxn corr-id (13240828), SIP msg corr-id (bab7de23)
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 1075 bytes:
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: SIP/2.0 200 OK
    Via: SIP/2.0/TLS xxx.31.20.13:5061;branch=z9hG4bKA3F8C278.03280239C018B5A3;branched=FALSE;ms-internal-info="abLT5zP8f8TNfBnWARBvEvat313QGOkIcu9HMiwukC2Xs5AigDr2UUrQAA"
    Via: SIP/2.0/TLS xxx.9.164.40:50623;branch=z9hG4bK5ebad57d;ms-received-port=50623;ms-received-cid=3300
    From: <sip:[email protected]>;epid=74AF521DBE;tag=f6947d76d
    To: <sip:[email protected]>;epid=b934ea0eac;tag=27fd721b0d
    Call-ID: 903004e75f584fac8a9447ae694882ba
    CSeq: 45 UPDATE
    Record-Route: <sip:lync-01-vm.ourdomain.com:5061;transport=tls;opaque=state:T:F:Ci.R3100;lr;ms-route-sig=aaurJ8x4E_rVQ1kQKv3Xx8jUDb7SQoWX13Nqvow5odbKg5AigD1H2BRgAA>;tag=BD3F60C9FDE56A9F9EFC3FBF063C88B3
    Contact: <sip:[email protected];opaque=user:epid:pgJmFnrHnVGiFDHAR8HwBAAA;gruu>
    User-Agent: UCCAPI/15.0.4649.1000 OC/15.0.4649.1000 (Microsoft Lync)
    Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="49D66A12", targetname="lync-01-vm.ourdomain.com", crand="2f386c2e", cnum="138", response="3ca86915e9db9afa4a79b484261b41139866de2a"
    Content-Length: 0
    09/16/2014|18:24:03.242 2AF0:2B1C INFO  :: End of Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 1075 bytes
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPCompression::CompressSendBuffer after compression, BytesLeft = 1075, BytesProcessed = 1075, cbDataCompressed = 357, psCompressedData = 12CE8FF8 
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: - encrypted buffer length: 421 bytes.  First 8 bytes:
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: 17 03 03 01 A0 D3 1E 07  :.... Ó..
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPTransportLayerSecurity::Send after encryption, BytesLeft = 357, BytesProcessed = 357, cbEncryptedBufSize = 421, spEncryptedBuff = 12C374F0 
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPAsyncSocket::Send this 12BD6C28, sending pbSendBuf 12C374F0, dwSendBufSize = 421
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CSIPAsyncSocket::SendHelper - [0x12BD6C28]
    09/16/2014|18:24:03.242 2AF0:2B1C TRACE :: CAsyncSocketWin32::Send this 0D237310, pbSendBuf 12C374F0, dwSendBufSize = 421, dwBytesSent = 421
    09/16/2014|18:24:03.243 2AF0:2B1C INFO  :: CUccSessionParticipant::InternalSetState [12D9B2E4] - state: 0x3->0x3
    09/16/2014|18:24:06.542 2AF0:2B1C ERROR :: OUTGOING_INVITE_TRANSACTION::OnTimerExpire Received 1xx but didn't receive final response terminating Call
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: Out trxn corr-id (1325D9B0)
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: Trxn corr-id (1325D9B0), SIP msg corr-id (fa8f2075)
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 735 bytes:
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: CANCEL sip:[email protected] SIP/2.0
    Via: SIP/2.0/TLS xxx.31.20.13:50616
    Max-Forwards: 70
    From: <sip:[email protected]>;tag=5c84c0c81d;epid=b934ea0eac
    To: <sip:[email protected]>
    Call-ID: 76aecefde32f48c5805ce1b5fdabc302
    CSeq: 1 CANCEL
    User-Agent: UCCAPI/15.0.4649.1000 OC/15.0.4649.1000 (Microsoft Lync)
    Supported: ms-dialog-route-set-update
    Ms-client-diagnostics: 52089;reason="Caller failed to establish the session: remote party not responded in time or local message processing failed"
    Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="49D66A12", targetname="lync-01-vm.ourdomain.com", crand="2863ad49", cnum="139", response="ff7f5a26f1c820112bd781dfa8c72c51488bcd1b"
    Content-Length: 0
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: End of Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 735 bytes
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: CSIPCompression::CompressSendBuffer after compression, BytesLeft = 735, BytesProcessed = 735, cbDataCompressed = 217, psCompressedData = 01721150 
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: - encrypted buffer length: 277 bytes.  First 8 bytes:
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: 17 03 03 01 10 B3 87 0A  :.....³‡.
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: CSIPTransportLayerSecurity::Send after encryption, BytesLeft = 217, BytesProcessed = 217, cbEncryptedBufSize = 277, spEncryptedBuff = 1463AA70 
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: CSIPAsyncSocket::Send this 12BD6C28, sending pbSendBuf 1463AA70, dwSendBufSize = 277
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: CSIPAsyncSocket::SendHelper - [0x12BD6C28]
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: CAsyncSocketWin32::Send this 0D237310, pbSendBuf 1463AA70, dwSendBufSize = 277, dwBytesSent = 277
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: call.SetState[142CD008]  SIP_CALL_STATE_ALERTING-->SIP_CALL_STATE_DISCONNECTED for sip:[email protected], stack=0AB840B0
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: SIP_CALL::NotifyCallStateChange[142CD008] : CallState : 2 StatusCode: 80ee000c, s=2
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE ::  displayName [(null)] 
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::NotifyCallChange[12FF1D50]- call-leg:142CD008, Callstate:2 StatusCode:80ee000c SessionState:5
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: CUccMultipartySession::NotifyPartyChange[12EFA574] - for participant [sip:[email protected]]
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: this type of session should not retry
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: this type of session should not retry
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: CUccSessionParticipant::InternalSetState [016FD98C] - state: 0x2->0x5
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: CUccSession::InternalRemoveParticipant - Removing participant sip:[email protected]
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: PV[130C7740]-Update(142CD008,5->2)
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: [130C7730]msp.updateCall(142CD008):5->2
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: PV[130C7740]-Remove(142CD008)
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: MSP.UpdateState[130C7730]-State 5->2, call(5->2)
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: MSP.SetState[12FF1D50] SIP_CALL_STATE_ALERTING->SIP_CALL_STATE_DISCONNECTED, local=sip:[email protected]
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: CUccSessionParticipant::InternalSetState [016FE04C] - state: 0x2->0x5
    09/16/2014|18:24:06.542 2AF0:2B1C TRACE :: CUccSession::InternalRemoveParticipant - Removing participant sip:[email protected]
    09/16/2014|18:24:06.542 2AF0:2B1C INFO  :: ~Out trxn corr-id (12BF1B20)
    09/16/2014|18:24:06.627 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BD6C30]
    09/16/2014|18:24:06.627 2AF0:2B1C TRACE :: SECURE_SOCKET: decrypting buffer size: 378 (first 8):
    09/16/2014|18:24:06.627 2AF0:2B1C TRACE :: 17 03 03 00 B0 22 E0 1A  :....°"à.
    09/16/2014|18:24:06.627 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0D2A5CF8]
    09/16/2014|18:24:06.627 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0AC7CC58]
    09/16/2014|18:24:06.628 2AF0:2B1C INFO  :: Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 597 bytes:
    09/16/2014|18:24:06.628 2AF0:2B1C INFO  :: SIP/2.0 200 OK
    Authentication-Info: TLS-DSK qop="auth", opaque="49D66A12", srand="60D4B258", snum="173", rspauth="2e9ef3e734a1d66e61387519490b0225a83fceb2", targetname="lync-01-vm.ourdomain.com", realm="SIP
    Communications Service", version=4
    From: "sendingClient"<sip:[email protected]>;tag=5c84c0c81d;epid=b934ea0eac
    To: <sip:[email protected]>;tag=BD3F60C9FDE56A9F9EFC3FBF063C88B3
    Call-ID: 76aecefde32f48c5805ce1b5fdabc302
    CSeq: 1 CANCEL
    Via: SIP/2.0/TLS xxx.31.20.13:50616;ms-received-port=50616;ms-received-cid=3100
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting
    Content-Length: 0
    09/16/2014|18:24:06.628 2AF0:2B1C INFO  :: End of Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 597 bytes
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x12B8E258]
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12B8E258]
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BC4198]
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: SECURE_SOCKET: decrypting buffer size: 197 (first 8):
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: 17 03 03 00 C0 EA CC BA  :....Àê̺
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0D2A5CF8]
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0AC7CC58]
    09/16/2014|18:24:06.628 2AF0:2B1C INFO  :: Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 760 bytes:
    09/16/2014|18:24:06.628 2AF0:2B1C INFO  :: SIP/2.0 487 Request terminated
    Authentication-Info: TLS-DSK qop="auth", opaque="49D66A12", srand="2FFC2CF9", snum="174", rspauth="abb0d4b958f75381c0550b2d98a1618baa48a63a", targetname="lync-01-vm.ourdomain.com", realm="SIP
    Communications Service", version=4
    From: "sendingClient"<sip:[email protected]>;tag=5c84c0c81d;epid=b934ea0eac
    To: <sip:[email protected]>;tag=BD3F60C9FDE56A9F9EFC3FBF063C88B3
    Call-ID: 76aecefde32f48c5805ce1b5fdabc302
    CSeq: 1 INVITE
    Via: SIP/2.0/TLS xxx.31.20.13:50616;ms-received-port=50616;ms-received-cid=3100
    ms-diagnostics: 5002;reason="Request was cancelled";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting";source="lync-01-vm.ourdomain.com"
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting
    Content-Length: 0
    09/16/2014|18:24:06.628 2AF0:2B1C INFO  :: End of Data Received -xxx.31.20.13:5061 (To Local Address: xxx.31.20.13:50616) 760 bytes
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x12B8E258]
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12B8E258]
    09/16/2014|18:24:06.628 2AF0:2B1C TRACE :: CSIPTransportLayerNotify::OnRecv - [0x12BC4198]
    09/16/2014|18:24:06.630 2AF0:2B1C TRACE :: verified buffer: <TLS-DSK><60D4B258><173><SIP Communications Service><lync-01-vm.ourdomain.com><76aecefde32f48c5805ce1b5fdabc302><1><CANCEL><sip:[email protected]><5c84c0c81d><sip:[email protected]><BD3F60C9FDE56A9F9EFC3FBF063C88B3><><><><200>-length-221.
    signature:2e9ef3e734a1d66e61387519490b0225a83fceb2
    09/16/2014|18:24:06.630 2AF0:2B1C INFO  :: Trxn corr-id (1325D9B0), SIP msg corr-id (fa8f2075)
    09/16/2014|18:24:06.630 2AF0:2B1C INFO  :: ~Out trxn corr-id (1325D9B0)
    09/16/2014|18:24:10.549 2AF0:2B1C TRACE :: MULTIPARTY_SESSION::RemoveFromLinkedList[12FF1D50] removed from linked list
    09/16/2014|18:24:35.245 2AF0:2B1C INFO  :: ~In trxn corr-id (13240828)
    09/16/2014|18:24:42.799 2AF0:2B1C INFO  :: Out trxn corr-id (1325D380)
    09/16/2014|18:24:42.799 2AF0:2B1C INFO  :: Trxn corr-id (1325D380), SIP msg corr-id (bab7dd55)
    09/16/2014|18:24:42.799 2AF0:2B1C INFO  :: Sending Packet - xxx.31.20.13:5061 (From Local Address: xxx.31.20.13:50616) 945 bytes:
    09/16/2014|18:24:42.799 2AF0:2B1C INFO  :: INFO sip:[email protected];gruu;opaque=srvr:PersistentChat:ODmUIdRivFWZkXE_Oo8DvQAA SIP/2.0
    Via: SIP/2.0/TLS xxx.31.20.13:50616
    Max-Forwards: 70
    From: <sip:[email protected]>;tag=27fd721b0d;epid=b934ea0eac
    To: <sip:[email protected]>;epid=74AF521DBE;tag=f6947d76d
    Call-ID: 903004e75f584fac8a9447ae694882ba
    CSeq: 21 INFO
    Route: <sip:lync-01-vm.ourdomain.com:5061;transport=tls;opaque=state:T:F:Ci.R3100;lr;ms-route-sig=aaurJ8x4E_rVQ1kQKv3Xx8jUDb7SQoWX13Nqvow5odbKg5AigD1H2BRgAA>;tag=BD3F60C9FDE56A9F9EFC3FBF063C88B3
    User-Agent: UCCAPI/15.0.4649.1000 OC/15.0.4649.1000 (Microsoft Lync)
    Supported: ms-dialog-route-set-update
    Supported: timer
    Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="49D66A12", targetname="lync-01-vm.ourdomain.com", crand="62509871", cnum="140", response="8b9b03b3adfc8fe9ff1c4540572262094cd8f654"
    Content-Type: text/plain
    Content-Length: 1

  • Lync A/V not working via Edge except for Federation

    I have an interesting problem.
    Internal users can do audio/video/screen sharing just fine from the internal network.
    I can do A/V and screen sharing with my federated contacts just fine from my internal network.
    When I use Lync on an external network (from home, public wifi, or even 4G), I can see presence, IM back and forth with no issues, but I can not do Audio/Video or screen sharing. I can do the whiteboard/Q&A/etc. It connects the call but I don't see or
    hear the other internal participant, and then it disconnects after exactly 10 seconds.
    The 2013 Lync Mobile app has the same issue - I can IM, but cant use audio or video.
    Does anyone know where I should start? I currently have a mixed topology with Lync 2010 and 2013 front-end servers, and a Single consolidated 2010 Edge server, with 3 external IP's addresses NAT'd to 3 public addresses. I remember that this used to work,
    but since it is not a heavily used feature, I don't know when it stopped working. It may have stopped when I installed the 2013 FE servers but i'm not positive.

     You can verify my earlier statement by looking at your ICE candidate list when your AV fails... 
     Look in snooper at the log, and search for 'candidate'... you should see a list of at least 6 entries similar to this:
    a=candidate:1 1 UDP 2140706431 192.168.1.101 39052 typ host
    a=candidate:1 2 UDP 2140705918 192.168.1.101 39053 typ host
    a=candidate:2 1 TCP-PASS 6656159 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
    a=candidate:2 2 TCP-PASS 6656158 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
    a=candidate:3 1 UDP 16648713 x.x.x.x 55824 typ relay raddr 192.168.1.101 rport 39050
    a=candidate:3 2 UDP 16648712 x.x.x.x 52421 typ relay raddr 192.168.1.101 rport 39051
    a=candidate:4 1 TCP-ACT 7086863 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
    a=candidate:4 2 TCP-ACT 7086350 x.x.x.x 56276 typ relay raddr 192.168.1.101 rport 39041
    a=candidate:5 1 TCP-ACT 1664797951 y.y.y.y 39041 typ srflx raddr 192.168.1.101 rport 39041
    a=candidate:5 2 TCP-ACT 1664797438 y.y.y.y 39041 typ srflx raddr 192.168.1.101 rport 39041
     missing typ relay or typ srflx raddr means you're not successfully talking to your edge, and getting ports allocated, which is my suspicion. The best troubleshooting step from there is a network capture to verify whether you are getting responses
    to your TURN requests. I can't comment on the connectivity test website, as I haven't used it, but I have spent a lot of time troubleshooting edge issues in multiple environments... 
    Jon McClary
    Using the lync logging tool, which components should I log to get this output?

Maybe you are looking for