17 Jul
2014
17 Jul
'14
3:53 p.m.
On 07/17/2014 03:20 PM, Alex Balashov wrote:
On 07/17/2014 03:19 PM, Conners, James wrote:
The question is very difficult to answer, for the reasons Alex explained....
The core of Kamailio is an RFC3261 SIP Server.
Adding or using different modules will to the list of RFCs... such as
with CPL module (RFC3880), invoking P-asserted-identity (RFC3325), using
DNS NAPTR (RFC2915), Websockets (RFC6455), etc.
The ultimate answer to this would depend on your intentions/usages of
the product in deployment.
The current stable version of Kamailio offers the following modules:
http://kamailio.org/docs/modules/stable/
You can also search the wiki (http://www.kamailio.org/wiki/start) for
specific RFC's that may be of interest.
Fred Posner
The Palner Group, Inc.
http://www.palner.com (web)
+1-503-914-0999 (direct)
+1-954-472-2896 (fax)
Asking what the "real" objective is
suggests there is a hidden reason
for my question. I can assure there is no hidden reason. We're simply
investigating the possible use of the Kamailio SIP server and would
like to know its capabilities and which RFCs it supports. Our current
SIP server supports a set of RFCs. So, it seems logical to ask what
RFCs an alternative SIP Server supports. The Kamailio website uses
the words "Among supported standards:" on its interoperability page.
Maybe the folks at Kamailio can provide you with their meaning of the
word "supported".
If you understand that SIP consists of a core RFC (3261) and hundreds of
additional features and extensions specified by other drafts and RFCs,
in varying stages of approval and de facto adoption, then you would be
able to appreciate that this is not a black-and-white, yes-or-no question.