Hello,
Kamailio SIP Server v3.1.5 stable release is out.
This is a maintenance release of latest stable branch, 3.1, that
includes fixes since release of v3.1.4. There is no change to database
schema or configuration language structure. Deployments running previous
v3.1.x versions are strongly recommended to be upgraded to v3.1.5.
For more details about version 3.1.5, visit:
http://www.kamailio.org/w/2011/09/kamailio-v3-1-5-released/
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hello
Im facing a big problem after upgrading from version 3.1.2 to 3.1.4.
The kamailio process keeps on terminating every now and then, this is what i
was able to retrieve from my logs.
Sep 14 12:52:31 SipProxy1 kernel: [71448.062089] __ratelimit: 15 callbacks
suppressed
Sep 14 12:52:31 SipProxy1 kernel: [71448.062096] kamailio[13963]: segfault
at 14 ip 0816452a sp bfedc940 error 4 in kamailio[8048000+1d9000]
Sep 14 12:52:31 SipProxy1 /usr/local/sbin/kamailio[13991]: : <core>
[pass_fd.c:293]: ERROR: receive_fd: EOF on 49
Sep 14 12:52:31 SipProxy1 /usr/local/sbin/kamailio[13907]: ALERT: <core>
[main.c:741]: child process 13963 exited by a signal 11
Sep 14 12:52:31 SipProxy1 /usr/local/sbin/kamailio[13907]: ALERT: <core>
[main.c:744]: core was generated
Sep 14 12:52:31 SipProxy1 /usr/local/sbin/kamailio[13907]: INFO: <core>
[main.c:756]: INFO: terminating due to SIGCHLD
Does anyone have an idea why this is happening?
Your help is much appreciated!
Regards
Phillip
Hi,
path module calls register_rrcb when "use_received" is set to 1 to
extract the "received=" param and set its content as dst-uri if present.
Now I've noticed that when e.g. a message has a pre-loaded route like
"Route: <sip:mydomain.com;lr>", then kamailio (at least 3.1.3) spits the
following error message:
/usr/sbin/kamailio[23953]: ERROR: <core> [parser/parse_param.c:481]:
parse_params(): Invalid character, ; expected
/usr/sbin/kamailio[23953]: ERROR: path [path.c:213]: failed to parse
route parametes
I was trying to reproduce this but without much success, it sometimes
happens and sometimes not, but I can't yet put the finger on the reason.
Any ideas?
Andreas
Hello,
it's being quite some time since we released 3.1.4, so I am thinking of
packaging soon v3.1.5 out of stable branch 3.1. My plan is to release it
Wednesday, September 14, 2011. Any other opinions?
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hi,
I am using the XCAP server of kamailio for contact list and presence
rules. It seems it only support to update the whole xcap doc of the
user but not the partial update. Can anyone tell me if the kamailio's
xcap server support the partial update of a user's doc? for example,
to remove a contact from the contact list or add a contact to the
contact list without PUT or DELETE the whole xcap document of this
user? If yes, what's the syntax of the HTTP request?
Thank you very much in advanced
Best Regards,
Laura
Hello Guys,
Is there any chance to modify at running time (in a register event) the max_contacts parameter?
I am running OpenSER version 1.4 .
Regards,
Rafael Rincon
rrincon(a)ipcomnetwork.com
+13054772902 x 111
Hello,
The documentation of carrierroute says "If flags and mask are not zero, and
no match to the message flags is possible, no routing will be done." Then is
there any route entry which can act as default gw (like an always-match
entry)?
For example this 'carrierroute' table:
+---------+--------+-------------+-------+------+------+
| carrier | domain | scan_prefix | flags | mask |
+---------+--------+-------------+-------+------+------+
1 | 1 | 1 | 156 | 500 | 0 |
2 | 1 | 1 | | 0 | 0 |
3 | 1 | 2 | | 0 | 0 |
+---------+--------+-------------+-------+------+-
Here if ruri is 156xx, and there is no flag set, then the cr module does not
find a match because of the non-zero value in the flag column (entry 1).
But I want to route this call via carrier1 domain1 and scan_prefix
empty-value entry (entry 2).
How can I set a default route entry here? Is possible with cr? Now I only
find it possible via a pstn.def_gw_ip variable.
Thank you,
Claudio