Hello,
the RPMs for Kamailio v4.2.0 were generated for Centos (5, 6, 7), Fedora
(18, 19, 20), OpenSuse (12.3, 13.1, 13.2) and RedHat (5, 6, 7). Packages
are made with OpenSuse build service, but as different build project --
see the details at:
- http://www.kamailio.org/wiki/packages/rpms
The change was made to have a build project for each release series from
now on, making easier to manage and mirror. Given this, the mirror at
rpm.kamailio.org has been updated as well. If you used it for 4.1.x or
older releases, you have to upgrade the repo path, see:
- http://rpm.kamailio.org
And again a call for people using RPMs: join the efforts in packaging
and managing there repos, we have the infrastructure now, but we are
short in time/human resources. If you want to keep the packages up to
date, come on board and help a bit.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
How can I specify weight for socket? can I get an example?
How to set weight for each socket below? thanks.
http://kamailio.org/docs/modules/stable/modules/rtpproxy.html
Sockets can be weighted by adding '=#' to a socket where # is an integer. A socket with a weight of 2 will be chosen twice as often as one with a weight of 1.
# multiple sets of multiple rtproxies
modparam("rtpproxy", "rtpproxy_sock",
"1 == udp:localhost:12221 udp:localhost:12222")
modparam("rtpproxy", "rtpproxy_sock",
"2 == udp:localhost:12225")
Hello everyone. I'm having a problem with registrations and Path and hope
that someone can help.
I have a Kamailio instance which is both a WebSocket proxy and a registrar
which has the following behaviour:
* A REGISTER with a Path header already on it gets recorded in the location
table.
* I use add_path() on all incoming REGISTERs, and a REGISTER relayed to
another registrar reaches that registrar with a Path header added
appropriately.
Unfortunately, save("location") ignores the path added by add_path(). I'd
prefer to keep the proxy and registrar co-located for the short term. Does
anyone know if/how I might be able to have the Path header properly stored
in the case that it was added by add_path()?
Regards,
Ben Langfeld
Dear All
I have setup a Kamailio proxy for testing IMS call flows.
I have configured as per help provided.
On registration, I get 483 response from server. When I searched it in
google and help, it was suggested to set the alias name properly. I set the
alias name properly.
Still I get 483 from Kamailio (used as IMS server)
Can somebody help me with what are the possible reasons for this.
Thanks
kamal
Hi,
we are filtering some method names from the Allow header with kamailio
4.1: depending in the configuration:
if (hf_value_exists("Allow", "INFO"))
{
xlog("L_INFO", "Remove INFO from Allow\n");
exclude_hf_value("Allow", "INFO");
}
if (hf_value_exists("Allow", "REFER")) {
xlog("L_INFO", "Remove REFER from Allow\n");
exclude_hf_value("Allow", "REFER");
}
There is a problem in case multiple rewrites are done on the same header
so the resulting message is going to be broken:
Input:
Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY,
PRACK, INFO, REFER
OUTPUT:
Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY,
PRACK,
The trailing comma is not allowed. So we have to use
msg_apply_changes(). But kamailio is quite restrictive on where you can
call msg_apply_changes():
1. it must be done before record_route()* and
2. it is not allowed in the branch route. As for me it's valid use case
when you need to do some header manipulations only for some of the
branches, isn't?
*(1) is further aggravated by the fact that the record_route() for
loose-routed requests is usually called quite early in the processing
pipeline. Imagine kamailio.cfg would look like:
request_route {
# per request initial checks
route(REQINIT);
# NAT detection
route(NATDETECT);
# CANCEL processing
if (is_method("CANCEL"))
{
if (t_check_trans()) {
route(RELAY);
}
exit;
}
# ---> filter Allow
route(FILTER_ALLOW_METHODS);
# handle requests within SIP dialogs
route(WITHINDLG);
I don't like the idea of changing the message before loose-routing.
Taking (1) and (2) into account, would it be possible to
a) fix exclude_hf_value to allow to filter multiple values in a single
pass and
b) allow msg_apply_changes() in branch route without any ill effects on
the record-route headers?
Please share your ideas.
Thanks,
Andrew
We configure use XCAP in version: kamailio 4.1.6 (x86_64/linux)
Error in SIP Client (Jitsi)
Resource cannot be read
http://192.x.x.x.x:5060/xcap-root/xca-caps/global/index For Null
Please Help me , for solve it's solution
//Gafar
Hello,
short note to say that packaging of v4.2.0 will start after 14:00
(Berlin time) -- anyone willing to do changes to branch 4.2 should send
a short notice on sr-dev and wait for confirmation to avoid conflicts.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda