Finally I've found a way how to disable this fcuking dumb, annoying, resource-intensive popup advertisement in Skype client completely*. This is specific to Windows client version 5+ (looks like Linux client is not affected yet).
( just edit your etc\hosts )
( just edit your etc\hosts )
Here is an informational RFC6271 with a list of formal requirements that can be used for session peering policy negotiation and monitoring.
See also Appendix A. ( Policy Parameters for Session Peering )
See also Appendix A. ( Policy Parameters for Session Peering )
RFC6230 allows SIP network components (e.g. SIP server or b2bua) to control different media applications (like RTP proxy, IVR, conference server) located on a separate server using SIP as a control protocol. ( Read more... )
In 5 months after the initial announce it becomes stable enough:
It's available in us-east-1 location only at the moment.
FreeBSD is now available on cc1.4xlarge instances.
cc1.4xlarge instances have 8 cores of 2.93 GHz Nehalem, 23 GB of RAM, two 840 GB ephemeral disks (plus as many EBS volumes as you want to create, of course), and 10 Gbps network connectivity.
I have absolutely no hesitation in saying that FreeBSD is production-ready on cluster compute instances.
It's available in us-east-1 location only at the moment.
Glad to know that there is a scientific ground for software versioning - http://semver.org/ - a set of rules to set a specific version number to your software product and avoid a dependency hell.
Why Use Semantic Versioning?
This is not a new or revolutionary idea. In fact, you probably do something close to this already. The problem is that "close" isn't good enough. Without compliance to some sort of formal specification, version numbers are essentially useless for dependency management. By giving a name and clear definition to the above ideas, it becomes easy to communicate your intentions to the users of your software. Once these intentions are clear, flexible (but not too flexible) dependency specifications can finally be made.
...
About
The Semantic Versioning specification is authored by Tom Preston-Werner, inventor of Gravatars and cofounder of GitHub.
This is not a new or revolutionary idea. In fact, you probably do something close to this already. The problem is that "close" isn't good enough. Without compliance to some sort of formal specification, version numbers are essentially useless for dependency management. By giving a name and clear definition to the above ideas, it becomes easy to communicate your intentions to the users of your software. Once these intentions are clear, flexible (but not too flexible) dependency specifications can finally be made.
...
About
The Semantic Versioning specification is authored by Tom Preston-Werner, inventor of Gravatars and cofounder of GitHub.
It's brilliant! MIT/BSD license will look like:
(source)
Take my code with you.
And do whatever you want.
But please don't blame me.
(source)
RFC6076 will be useful to compare metrics from different VoIP QoS/performance monitoring systems.
This document defines a set of metrics and their usage to evaluate
the performance of end-to-end Session Initiation Protocol (SIP) for
telephony services in both production and testing environments. The
purpose of this document is to combine a standard set of common
metrics, allowing interoperable performance measurements, easing the
comparison of industry implementations.
...
4.1. Registration Request Delay (RRD)
4.2. Ineffective Registration Attempts (IRAs)
4.3. Session Request Delay (SRD)
4.4. Session Disconnect Delay (SDD)
4.5. Session Duration Time (SDT)
4.6. Session Establishment Ratio (SER)
4.7. Session Establishment Effectiveness Ratio (SEER)
4.8. Ineffective Session Attempts (ISAs)
4.9. Session Completion Ratio (SCR)
Profile
![[info]](http://l-stat.livejournal.com/img/userinfo.gif?v=92.1)
technovodstvo- Artem Naluzhnyy
