FMS edge server tmp files issue
I have a few edge servers connecting to an origin server and over time the FMS's tmp directory in the edge server is filled with .proxy files like
MTA0MDAxMDE2Ng=.proxy
MTA0MDAxMjg1MQ=.proxy
MTA0MDU2MzAyOA=.proxy
MTA0MDYzNDU2MA=.proxy
MTA0MTE4MjgyNw=.proxy
MTA0MTM3OTcwNg=.proxy
MTA0MTM4NjIzNQ=.proxy
MTA0MTMzNzE2Nw=.proxy
MTA0MTYxNjUyNQ=.proxy
Over time this becomes millions of files, which then considerably slows down the system and the performance of FMS. I have to restart FMS and delete all the files in the tmp directory regularly and this makes my cluster very difficult to manage.
Can anyone help me on how to remove all these files automatically? Or if there is any config that I am missing which might cause this issue?
hey one541_,
i believe for you to be gettiing .proxy files you must be having disk caching enabled. These are created to handle process mutex. These files get removed as soon as fms shuts down. If these are not getting deleted maybe you are not shutting the edge server (in the edge origin configuration) down properly or you are not shutting down at all.
Similar Messages
-
Lync Edge Server 2013 Certificate Issue seems unresolvable
I've implemented a single internal Standard Edition Front End server with a single consolidated Edge server and Reverse Proxy server/appliance located in a perimeter network.
On the internal IP of the Edge server I use a certificate form a internal CA ( which is trusted by the edge server), the "internal" certificate issued by the internal Ca is used only between the edge server and the frontend server. An external certificate
with cn sip.ipabo.nl and alt.subj sip.ipabo.nl and webconf.ipabo.nl. from Globalsign is used on the external IP’s . Services have their own ip adresses and are natted by a router. Ive tested that all ports can be reached from the internet. But still no connection
possible from external clients. The ms. connectivity analyser says: "The The certificate couldn't be validated because SSL negotiation wasn't successful". Connections from mobile clients through reverse proxy are no problem also internal clients
have no issue ( they both don’t use the edge but proxy ). So i assume there's someting wrong with the certificate implementation on the Edge server, however ive tested it with the RUCT from Curtis Johnstone, and the certificate seems to be OK. Also in the
Lync Server Deployment Wizard the certificates seem to be OK. In the computers personal certificate store the are only the two necessary certificates ( internal and external) also intermediate certificates are installed. Routing ( default gateway on external
interface ) is working fine. So I think I'm out of options, any ideas?
Tnx,
GuidoPlease check the DNS records for sip.ipabo.nl and webconf.ipabo.nl are created on external DNS server.
Please check you can telnet Lync Edge Access service FQDN on 443 port.
Check the automatic configuration for remote access is configured correctly or you can try to sign in manually.
Follow the steps in blog blow to test your Edge Server:
http://blogs.technet.com/b/nexthop/archive/2011/12/07/useful-tips-for-testing-your-lync-edge-server.aspx
Lisa Zheng
TechNet Community Support -
Hi,
after a storage failure, some files seemed to be damaged on exchange 2010 edge server
it said it could not connect to DC and i realized that is because ADAM service stopped
I tried to start it but encountered a weird error (0xc000000) some thing like that
so i found that adamntds.dit is corrupted
I issued this :
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Adam>eseutil /p adamntds.dit
it said integrity check ok but after that again ADAM does not start and says
this service started and the stopped ... (the famous message we all know)
1- now is there any way to fix it?
2- is it reasonable to use the other edge server database file on this one (we have two edge servers) or it is non-sense
3- according to this
http://social.technet.microsoft.com/Forums/exchange/en-US/93ed667c-5a37-404c-9471-d2525621a371/adam-service-wont-start-on-edge-transport?forum=exchange2010
and the advice of Ed my dear friend on Technet, itmay be better to reinstall it
but it does not even let me to uninstall it and says :
Summary: 2 item(s). 1 succeeded, 1 failed.
Elapsed time: 00:02:58
Configuring Prerequisites
Completed
Elapsed Time: 00:00:41
Edge Transport Role Prerequisites
Failed
Error:
The Active Directory Application Mode (ADAM) service must be started before Setup can continue.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
so somebody please tell MS guys if i could start it why should i uninstall it :P
and i do not want to use manual methods to do the removal if possible
and much better if i can fix it without even uninstall exchange
thanks to allHi,
I would like to verify if you have a backup of ADAM directory.
If yes, please put it on the server and try to start the ADAM service.
If no, I recommend you recover the ADAM directory as the following steps:
1. Use esentutl /g.
2. If Integrity check is successful, use this cmdlet: esentutl /d.
3. Use esentutl /r edb.
4. If above steps fail, use esentutl /p adamntds.dit. Then delete all files in the directory except for the adamntds.dit. (Note: Before you delete the files, please take a backup for them.)
5. Try starting ADAM service.
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
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
JamesLync 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. -
Issue in Synchronizing with Exchange 2010 Hub and Edge server
Dear Sir,
We have an issue with the installation of Exchange edge server 2010 SP1.
We installed exchange edge server on DMZ but unable to do the subscription between edge server and hub server. Tried to check from the edge server whether the ports (50389 & 50636) are listening. Both are listening without any issues. After the
edge subscription is done and when pass the command start -edgesynchronization we are getting the below error:
Unable to contact the edgesync service.
+catogary :ReadError: (:) [start-edgesynchronization], Endpoint not registered exception
+Fullyqualifiederrorid : FE1A5BE2, Microsoft.Exchange.Management.Edgesync.SyncNowTask
Please help me in rosolving the issue with regards to Edge Server.
Thank & Regards
Suraj SreekumarHi Suraj,
Try to Re subscribe the HUB & EDGE serve, Create XML file on the EDGE server, Removed the Edge subscription from the HUB server and Restart the Transport & ADAM service
Then Ran Start & Test-EdgeSynchronization cmdlet on the Exchange Management Shell on Hub, again Restart the Transport server on the HUB & ADAM service on the EDGE .
White Paper: Edge Subscription and Synchronization
http://technet.microsoft.com/en-us/library/bb310755(EXCHG.80).aspx#EdgeSyncsynchronization
Anil -
Hi i am getting an error like this while installing Live Cycle Server " The file merge_modules\lc11_common_iam_zip does not exist This file is required sucessfullly run the Live Cycle Installer.Can any one help me on resolving this issue it would be of great help..thanks .
I think in your situation it would be worth trying the things listed under the event. It does have to do with FRS and it's easy to do. I've used it to fix journal errors after a server unexpectedly restarts and sysvol stops replicating. I
could see where it could fix your issue, and if it doesn't, you're out 5 minutes. :)
The listed registry key does not exist
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
-
Bi server + space management + logfile / cache file /tmp file
hi all,
i would like to know what are the files i can remove from linux server ( i mean to say "log file", cache file or tmp file) becuase it is getting generated on daily basis and increase our server space.
we are using oracle 11.1.1.6.0 on linux 32bit
please advice.hi ,
refer this :
Re: Need help -To Restrict Huge temp file, which grows around 3 GB in OBIEE 11g -
Forgive me if this question sounds rather "entry level", I have never worked with Lync and this project was handed to me by my boss, who hasn't worked with Lync either.
I have been reading various posts and forum messages until I went cross eyed about setting up Lync 2013 Edge server correctly. I am still running into some questions and issues with the Access, Web, and A/V services starting. Here is my main
question, and below is my setup.
Question:
Is there a need for both an external and internal nic card IF all three external IP's for the external services are programmed at the firewall and router to go directly to 1 internal IP address?
Setup:
Currently I have 1 FE-Standard server that also acts as the Mediation Server, and 1 Edge Server both of which are virtual and running Server 2012. Originally I did have 2 network cards setup, as all other documentation suggested, 1 external and 1 internal.
However my boss, who setup the DNS/Firewall entries stated to remove the External Card since the external address that was setup for the 3 services was routed to 1 internal address. The Access Services, Web Services, and A/V services are all running on three
separate ports with their own unique FQDN- 443, 444, and 445. The cert that was deployed is a wild card cert from GoDaddy, this has been used by other servers that point inside and outside without issues.
Issues and Errors Messages:
I have run into a few different issues and error messages from the Event Viewer:
System
Provider
[ Name]
LS Protocol Stack
EventID
14352
[ Qualifiers]
50153
Level
2
Task
1001
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2885
Channel
Lync Server
Computer
edgesvr01
Security
EventData
0xC3E93C0A
SIP_E_STACK_TRANSPORT_FAILED
System
Provider
[ Name]
LS Server
EventID
12303
[ Qualifiers]
50152
Level
2
Task
1000
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2884
Channel
Lync Server
Computer
edgesvr01
Security
EventData
80072741
The requested address is not valid in its context.
System
Provider
[ Name]
LS Protocol Stack
EventID
14336
[ Qualifiers]
50153
Level
2
Task
1001
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2013-09-09T15:44:51.000000000Z
EventRecordID
2883
Channel
Lync Server
Computer
edgesvr01
Security
EventData
TLS
external IP address that is now used now
5061
Please help, I am at a loss as to where to go from here.Thanks for the quick responses.
I have re-enabled the external NIC. All services are running now. When I ran the Remote Connectivity tester this was the outcome.
Testing remote connectivity for user: username@domain... to the Microsoft Lync server.
Specified remote connectivity test(s) to Microsoft Lync server failed. See details below for specific failure reasons.
Test Steps
Attempting to resolve the host name lync.metisconnect.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: xxx.xxx.xxx.xxx (external address)
Testing TCP port 443 on host: host fqdn to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server host fqdn on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=*.ourdomain.com, OU=Domain Control Validated, Issuer: SERIALNUMBER=######, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona,
C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
The host name that was found, lync.metisconnect.com, is a wildcard certificate match for common name *.ourdomain.com.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=*.ourdomain.com, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 7/31/2013 4:02:03 PM, NotAfter = 7/31/2014 4:02:03 PM
Testing remote connectivity for user username@domain to the Microsoft Lync server.
Specified remote connectivity test(s) to Microsoft Lync server failed. See details below for specific failure reasons.
Tell me more about this issue and how to resolve it
Additional Details
Couldn't sign in. Error: Error Message: Operation failed because the network connection was not available..
Error Type: ConnectionFailureException.
External calls from a 3g/4g data connection are not connecting when using the Lync call feature to an internal users Lync Client. Outcome is: Connecting Call and No Audio. Then call ends. -
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
DanielI 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 Edge Server Certificate Issue
I've implemented a single internal Standard Edition
Front End server with a single consolidated Edge server and Reverse Proxy server/appliance located in a perimeter network.
On the internal IP of the Edge server I use a certificate form a internal CA ( which is trusted by the edge server), the "internal" certificate issued by the internal Ca is used only between the edge server and the frontend server. An external certificate
with cn sip.ipabo.nl and alt.subj sip.ipabo.nl and webconf.ipabo.nl. from Globalsign is used on the external IP’s . Services have their own ip adresses and are natted by a router. Ive tested that all ports can be reached from the internet. But still no connection
possible from external clients. The ms. connectivity analyser says: "The The certificate couldn't be validated because SSL negotiation wasn't successful". Connections from mobile clients through reverse proxy are no problem also internal clients
have no issue ( they both don’t use the edge but proxy ). So i assume there's someting wrong with the certificate implementation on the Edge server, however ive tested it with the RUCT from Curtis Johnstone, and the certificate seems to be OK. Also in the
Lync Server Deployment Wizard the certificates seem to be OK. In the computers personal certificate store the are only the two necessary certificates ( internal and external) also intermediate certificates are installed. Routing ( default gateway on external
interface ) is working fine. So I think I'm out of options, any ideas?
Tnx,
GuidoOk I found It:
It was a simple setting in the Control panel, or in the management shell:
In Set-Accessedgeconfiguration
AllowOutsideUsers was set to False. this should be true.
I found it by Using OCSlogging on the Edgeserver, looking at SIP.
So I don't understand how all the certificate and server unavailable warnings make any sense.
The next issue will be exchange integration :)
Thanks for your help everybody -
LYNC 2010 Edge server deployment issues
I've been able to install LYNC and have the meet and dialin function working properly internal/external. I'm attempting to test setting up external access to the client with an edge server. All seems to install properly etc with no errors being thrown my
way. But in the services i have a few that will not start with the below errors. Can anyone point me to a deployment scenario with an edge server how-to?
Any help would be greatly appreciated.
The Lync Server Access Edge service terminated with service-specific error %%-1008124918.
The Lync Server Web Conferencing Edge service terminated with the following error:
The requested address is not valid in its context.Hi every body, I am trying to do a
proof of concept before we buy the public Certificate for my Edge server but I have this error..
I have the same error as you guys (1008124918 )
Here is my setup
Active directory with a CA on it. ( I used this CA for my Front-End, and for both Internal/External Edge Certificate )
FrontEnd ;
-In the domain
-192.168.16.55 255.255.255.0
==
Edge:
Inside NIC : 192.168.16.57 255.255.255.0, no gateway
Outside NIC (dmz ) : 192.168.18.80 255.255.255.0 . Gateway 192.168.18.0
The edge is not in the domain.
==
My Public IP : 69.70.xx.xx
=====================
In the wizzard for the edge-pool
I choose:
-Single computer pool
I check :
- Use a single FQDN & IP
-Enable federation ( port 5061 )
-The external IP address of this edge pool is translated by Nat
external fqdn : sip.OurCie.com / 5061 Port
Internal IP : 192.168.16.57
External IP ( for sip access, web conf, A/V Edge services ) : 192.168.18.80
Public IP used by nat : 69.70.xx.xx
=====================
So when I start the service I have this error code : Windows could not start the Lync Server Access Edge....code : 1008124918
in the eventvwr here is ther error that I have :
Transport TLS has failed to start on local ip : 69.70.xx.xx at port 5061
cause: config error, low system ressources or another proram is using this port
can also happen if the ip address has become invalid
Any idea ? -
Exception to audit tmp files deleted in Win2008 Server
I need to prevent the event viewer record deleted tmp files when I use the audit fileserver 2008, because the log file is too large .
Hi,
We could not exclude tmp files from being logged in the security audits. Since the file system doesn't have a special "type" for temporary files, we also cannot fileter tmp files in security audit logs.
For more detailed information, please refer to the article below:
Advanced XML filtering in the Windows Event Viewer
http://blogs.technet.com/b/askds/archive/2011/09/26/advanced-xml-filtering-in-the-windows-event-viewer.aspx
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Word 2008 for Mac and NFS mounted home directories "Save File" issues
Greetings everyone,
(Long time lurker, first time poster here)
I admin a small network (under 20 workstaitons) with a centralized NFS server, with user home directories mounted via NFS upon login. Users are authenticated via LDAP. This is all working fine, there is no problem here. The problem lies when my users use Microsoft Word 2008 for Mac. When they attempt to save a file to thier Desktop (or Documents or any folder under thier home dir) they are met with the following message:
(dialog box popup)
"Word cannot save or create this file. The disk maybe be full or write-protected. Try one or more of the following: * Free more memory. * Make sure the disk you want to save the file on is not full, write-protected or damaged. (document-name.ext)"
This happens regardless of file format (Doc, Docx, Txt) and regardless of saved location under the network mounted dir. I've noticed that when saving Word creates a .tmp file in the target directory, which only further confuses me to the underlying cause of the issue.
When users logon to a local machine account and attempt the save, there is no issue.
I have found many posts in other commuity forums, including this one, indicating that the issue is a .TempoaryItems folder in the root of the mounted directory. This folder already exists and is populated with entries such as "folder.2112" (where 2112 is the uid of the LDAP user). I find other posts indicating that this is an issue with Word:2008 and OSX10.8, with finger pointing in either direction, but no real solution.
I have installed all Office for Mac updates from Microsoft (latest version 12.3.6).
I have verified permissions of the user's home dir.
I have also ensured that this issue effects ONLY Microsoft Office 2008 for Mac apps, LibreOffice and other applications have no issue.
Does *ANYONE* have a solution or workaround for this issue? While we're trying to phase Microsoft products out, getting users to ditch Word and Excel is difficult without removing them from systems completely. So any pointers or help would be greatly appreciated.
Thanks.
~kI can't tell you how to fix bugs in an obsolete version of Office, but a possible workaround is to use mobile home directories under OS X Server. The home directories are hosted locally and synced with the server.
-
Hi all,
Maybe this topic has been asked and answered before. But I
have not found relevant information on this issue. So there it is:
I found out that when the FMS service is running, it creates
a lot of temporily files in the
c:\windows\tempdirectory (the files are created in the name
of
mx_???.tmp where the ??? is hexadecimal value). I wonder is
there any way to configure this including changing the directory
and as well as set the number of tmp files where it can create.
Furthermore, there may be a bug whereby after the service is
manually stopped, the temporily fies are still being created by the
services.exe where i believe is caused by a unsucessfully
termination of thread(s). Please verify this.
Any help would be appreciated.
LaiHmm... I've never seen that one before. Are you 100% sure
it's FMS writing those files? I looked into a number of my FMS
servers (windows) after reading your post, and couldn't find any
files like the ones you described. The only temp file I'm finding
has to do with the Macromedia licensing service, but that's only
one file on each machine (in the windows/temp dir). -
I need help to setup FMS edge can stream video from a FMS-core (or from other FMS-edge). configuration diagram:
FMLE ==> FMS-core ==> FMS-edge ==> users.
on FMS-edge i have a application on
C:\AMS\applications\myapp
if i did not change anything in Vhost.xml file (path: C:\AMS\conf\_defaultRoot_\_defaultVHost_\Vhost.xml). The myapp application is ok, but can not see the video stream rtmp://FMS-edge/live/livestream.
if i change Vhost file:
<Proxy>
<Mode>remote</Mode>
<RouteTable protocol="">
<RouteEntry>FMS-edge:1935;FMS-core:1935</RouteEntry>
Then video stream is ok but application don't.
In this case, setup FMS-edge hybird mode. 1 Vhost setup as local mode to serve myapp application, and 1 Vhost setup as remote mode to serve streamming video from FMS-core, right?
Tonyhey one541_,
i believe for you to be gettiing .proxy files you must be having disk caching enabled. These are created to handle process mutex. These files get removed as soon as fms shuts down. If these are not getting deleted maybe you are not shutting the edge server (in the edge origin configuration) down properly or you are not shutting down at all.
Maybe you are looking for
-
Is it possible to Schedule File Adapter to pick the files ?
Hi , I am planning to pick the files at particular time daily.. say 11AM. Is it possible to schedule the Communication channel to pick the file daily at 11AM ? Kindly suggest. Thanks Deepthi
-
SELECT EXPERT formula howto?
<p>Hi All! I write a program under VS 2005 C# and Crystal Report. So I have a problem with the formula (and with the sql expression formula). My problem is this:</p><p> How can I do create a group with the selection expert? My task is the next: </p><
-
Removing font shadow on pie charts in Numbers '09
Help!! how do I remove the font shadow on my pie charts? It seems to be a standard feature but my reports are all blurred, how can I make the pie chart labels have a nice crisp font? Thanks.
-
Do I need two separate licenses to be able to use Flash Builder on Mac and Windows?
Does my Creative Cloud subscription allow me to install Flash Builder on both Mac and Windows machines?
-
What's different between statfulacl and detailedacl
i just confused that what's different between stateful ACL and Detailed ACL in Hyper-V 2012R2, i know stateful ACL will create return traffic automatically for example: Add-VMNetworkAdapterExtendedAcl –VMName "ApplicationServer" –Action "Allow" –Dire