Hi, please help me out with these questions:
Is it possible to configure kamailio to use different certificates, one per peer? Do we just add them to the same "calist.pem" file?
Is is possible to configure kamailio to accept a certificate from another device? I mean instead of Kamailio creating the certificate/key and give it to customer/provider. If that is the case, do we also add it to the "calist.pem" file as well?
If all the above is true, what happens when the certificates have different expiration dates?
thank you very much
Which variables I can use in
event_route[sl:local-response] route to xlog
proto:ip:port to which the response will be
sent?
event_route[sl:local-response] {
xlog("L_INFO","Local response to
*$??*\n$mb\n");
}
Hi,
Following this issue, and the issue "BYE dialog timeout bad syntax" from
Julia.
I have 2 kamailio servers. srv1 creates a dlg_timeout BYE and sends it to
srv2 that forwards the BYE to the next sip server (some other server...).
I can definitely see that the BYE that is being forward is malformed. The
TO header info is not complete (the port section for example).
When a "normal" bye is received from srv1 (not dlg_timeout) all works fine.
One thing that i do in this scenario, on srv2 i use uac_replace() on the TO
header. So, it is OK that the final destination is different (i do
translations).
I attached the BYE from both servers.
Any ideas?
Thanks,
Uri
You probably meant the To and From headers, I'm guessing. Yeah, as long as
there is no display name component, URIs in headers like that don't have to
go in <>s. The way Kamailio sends it is grammatically valid, per RFC 3261.
The user agents are at fault for not understanding it correctly. Alex
Balashov <abalashov at
evaristesys.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
wrote: >*"BYE headers"? Which headers? *>* *>*Uri Shacked <ushacked at
gmail.com <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
wrote: *>* *>>*Hi, *>>* *>>*I think there is a bug with the BYE that is
sent to the caller and *>>*callee *>>*when dialog timeout happends. *>>* *>>
*The BYE headers are sent with no "<" or ">". *>>*So, some sip singaling
points decline the BYE. *>>* *>>*BR, *>>*Uri *>>* *>>*
*>>*------------------------------------------------------------------------
*>>* *>>*_______________________________________________ *>>*SIP Express
Router (SER) and Kamailio (OpenSER) - sr-users mailing *>*list *>>*sr-users
at lists.sip-router.org<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
*>>*http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users *>* *>*--
*>*Sent from my mobile, and thus lacking in the refinement one might *>*expect
from a fully-fledged keyboard. *>* *>*Alex Balashov - Principal *>*Evariste
Systems LLC *>*235 E Ponce de Leon Ave *>*Suite 106 *>*Decatur, GA
30030 *>*United
States *>*Tel: +1-678-954-0670 *>*Web: http://www.evaristesys.com/,
http://www.alexbalashov.com/ *>*
*>*_______________________________________________
*>*SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list *
>*sr-users at lists.sip-router.org<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
*>*http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users * -- Sent
from my Nexus 10, with all the figments of autocorrect that might imply.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave
Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web:
http://www.evaristesys.com/, http://www.alexbalashov.com/ --------------
next part -------------- An HTML attachment was scrubbed... URL: <
http://lists.sip-router.org/pipermail/sr-users/attachments/20130422/0c75272…>
Hello,
there were old and recent discussions about the representation of time
in accounting records. At this moment the acc module stores the unix
timestamp as datetime value.
In some countries is required to store more accuracy, beyond the
seconds. Also, the datetime gives some troubles with converting back to
unix timestamp, specifically with time zones and daylight saving times.
I want to open a discussion that is visible for all users and devs,
being something affecting probably everyone, input from anyone that is
interested being relevant to select the right approach.
Here are some suggestions presented so far.
1) store seconds.miliseconds as double - there is a patch (which
probably needs some tunings itself) on tracker. The precision is shifted
from seconds to milliseconds. Internally computed from microseconds from
timeval structure. The other modules might need updates (iirc dbtext has
only 2 decimals precisions for double, while miliseconds will require at
least three -- could be the case for flatstore or other modules).
Advantage is the computing of duration directly by subtraction of two
values.
2) store seconds and microseconds as two separate values. Should be no
issues with existing modules. Even more accuracy than above, no issues
with other modules, but will require to use two columns (thus four
values to compute the duration)
Any other suggestions?
Personally, at this moment, I will go with 2), but that might not meet
everyone's needs. So a solution can be to make it configurable, as a
bitmask of what time representation to store.
Say, there will be a new parameter timestamp_mode for acc module:
- bit one set - store seconds timestamp as for now (default)
- bit two set - store seconds and microseconds in separate integer columns
- bit three set - store seconds.miliseconds as double value in one column
I could add the parameter and tune acc for bit one and two. For bit
three a deeper review is needed for other modules, probably the
developer that submitted to the tracker can do it.
More suggestions? Pro or cons opinions?
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24016, 2013
* http://asipto.com/u/katu *
Dear Sir,
I am using kamailio 1.5.0, having installed and configured as given on the
kamailio site
<http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-1.5.x-from-svn>
on my PC having Centos operating system. I have configured the config files
kamailio.cfg, kamctlrc accordingly as given on site.
when I start the kamailio using kamctl start command. it gives the error
message like
*[root@localhost ~]# kamctl start
database engine 'MYSQL' loaded
Control engine 'FIFO' loaded
INFO: Starting Kamailio :
ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start
failed
*please* *help me out to solve this problem and suggest me where I am
wrong. * *I have configured kamalio so many times it gives me the same kind
of error message.
*
*
-
With Regards,
Dinesh Kumar Gautam
Noida,
+919911838275
Hi,
With TCP, there is no way Server can establish a TCP connection through
client's Firewall/NAT.
So, when Client connection is disconnected from the server due to Network
issues, the Registration should be removed.
I tried to handle this with a Event Route in tcp_read.c. However, There is
not an easy way to find the Registration with TCP socket info (IP and Port
of the Client).
Could anyone suggest a solution?
Thanks
Krish Kura
Hello,
I've been trying to make the Presence thing work with kamailio
4.0.1 and SipML5 browser client .I have loaded only the modules which are
already in the Kamailio.cfg file
loadmodule "presence.so"
loadmodule "presence_xml.so"
Is it necessary to load other modules as well?At the same time I request
you to suggest which Sip client I should use in order to make presence work.
Rupayan Dutta
Hi,
After few crashes of the Kamailio during prcessing of the messages,
Kamailio fails to start
I see rtimer is failing. Here is the log
0(20082) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (0): sqlops
0(20082) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (0):
app_lua
0(20082) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (0): rtimer
0(20082) ERROR: rtimer [rtimer_mod.c:162]: failed to start timer routine
as process
0(20082) ERROR: <core> [sr_module.c:896]: init_mod_child(): Error while
initializing module rtimer (/usr/local/lib64/imckamailio/modules/rtimer.so)
0(20082) ERROR: <core> [main.c:1716]: ERROR: main: error in init_child
6(20091) INFO: <core> [main.c:854]: INFO: signal 15 received
What can I do to fix this issue?
Thanks
Krish
Hi everyone,
I'm using Kamailio 3.2.1 with a quite big config file. After adding some
new config lines I did a syntax check of the configuration file with
"kamailio -c -f <file>" and got the following error output:
loading modules under
/opt/kamailio/lib/kamailio/modules_k/:/opt/kamailio/lib/kamailio/modules/
0(28755) : <core> [cfg.lex:1426]: ERROR:lex:addstr: memory allocation
error
0(28755) : <core> [cfg.lex:1428]: ERROR:lex:addstr: try to increase
pkg size with -M parameter
increasing the pkg memory (-M) or shared memory (-m) has no effect.
I played around with the size of the configuration file with xlog lines
and the cause really seems to be the size of the config file.
Restart of Kamailio is possible without problems, it is only the syntax
check that leads to the memory error output
Is there any possibility to increase the memory for the syntax check?
Regards
Fred
While I have seen other posts I have not found anything that describes my scenario.
Kamailio sets in front of a group of asterisk servers which are used in a round robin dispatch group. All asterisk servers share a common database in which voicemail boxes are defined and messages are stored.
I'm looking for a way to make message waiting work in this example. I have tried creating a view with basic peer information for asterisk to use for message notification, however asterisk does not 'see' these peers until a call is made to the specific user and the peer info is retrieved from the database, which can delay notifications severely rendering them useless. I also want to avoid sending a copy of the registrations to asterisk servers, as the purpose of the distributed system is to eliminate the large number of sip registrations asterisk needs to manage.
I have also seen a couple of script methods that look at the voicemail directory structure for file changes and trigger an application like sipsak to generate the notifications and let kamailio relay them. From what I see, the consensus is not to go this route. In my case the script would need to look at the database level, and maybe some sort of database trigger could be used.
What are others doing / what do others recommend as the best way to handle message waiting with a situation where kamailio sets in front of a voicemail server?
Any input is appreciated.
Dan-
