Hello,
Im running kamailio 4.2.3 and I'm trying to build a system where I could
have the following features: SIP proxy, RTP proxy, Presence & XCAP
service for IM messaging.
I have a problem with the Presence service with users that are located
behind nat. When Kamailio sends presence info to a watcher with sip
NOTIFY message, the destaination ip for the pacage seems to be an
un-routable (=private) ip, and so the watcher never receives the NOTIFY
message making the watchers sip client unaware of the other users presence.
Any suggestions how to make Kamailio handle the watchers behind nat so
that the NOTIFY messages will get delivered succesfully?
I tried the scenario with a client with public ip and the presence works
fine.
my kamailio.cfg:
http://tny.cz/7d85773c
-- Olli
Dear All
I have a sip user agent. Today it works fine with Kamailio using tcp as
tranasport. Now I am planning to support websocket in my sip ua.
My question is does Kamailio support websocket transport. If so how can I
configure it or while building kamailio do I need to make some flags on. I
am using latest Kamailio 4.2.3 (version: kamailio 4.2.3 (x86_64/linux)).
Thanks
Austin
Hi All,
1. What are resource requirements for running Kamailio server with TLS module active for 1000 registered users (concurrent calls) when running on VPS? In other words, what amount of RAM and processor power required?
2. What is the maximum number of Kamailio TLS users/concurrent calls can be made for the below default values?
# Amount of shared and private memory to allocate
# for the running Kamailio server (in Mb)
SHM_MEMORY=64
PKG_MEMORY=8
Thanks.
Hi,
We are currently deploying an entire architecture composed of load
balancers, proxies and media relays. All the components except the media
relays are Kamailio instances. The media relays are RTP proxy instances.
We are trying to determine the hardware requirements for the different
servers.
We will start with an architecture composed of:
. 2 load balancers (one kept as backup to ensure availability)
. 2 proxies (load is balanced over the 2 using the DISPATCHER
module)
. 2 media relays
We are trying to determine the recommended hardware for the different
components taking into account we will need to serve around 400000 users.
How many registrations per second can Kamailio support?
How many concurrent calls can Kamailio support?
What is the recommended number of children processes?
What is the recommended size for PKG memory?
What is the recommended size for SHM memory?
Thanks for your help,
Mickael
Hello,
Does Kamailio still support authentication using the auth_diameter module?
There is a note on the modules page stating the module is now obsolete.
"NOTE: diameter support was developed for DISC (DIameter Server Client project at http://developer.berlios.de/projects/disc/). This project seems to be no longer maintained and DIAMETER specifications were updated in the meantime. Thus, the module is obsolete and needs rework to be usable with opendiameter or other DIAMETER servers."
Is the page referring to this module or the DISC?
Are there perhaps any other ways to do authentication with Kamailio using diameter?
Hello,
I discovered an issue related to the handling of "timestamp" and/or "Marker
bit" with rtpproxy (I use the latest Extension 20081224).
The call-flow is the following: one UA places a call to A and put this call
on hold. Then, the same UA call another number B. Individual streams are ok.
When the UA tries to transfer A with B, the RTPProxy receive a RTP packet
with a huge timestamp and the Marker bit set to "True".
Just after this RTP packet, RTPProxy stop forward the RTP packets from A to
B. B to C is still working.
Anyone have an idea?
Regards,
Igor.
Hi,
I'm trying to add PUSH support to my system using Kamailio.
When a call is received and the callee has no active registration, a PUSH is
sent to the callee endpoint. In order to send this PUSH, my proxy sends an
HTTP requests to another server that will send the PUSH.
So, my route block is as follows:
route[PUSH] {
#Send PUSH notification using a custom module I wrote
#Suspend transaction execution.
t_on_failure("MANAGE_FAILURE");
if(!t_suspend()) {
send_reply("503", "Service Unavailable");
exit;
}
$sht(push=>join::$rU) = "" + $T(id_index) + ":" + $T(id_label);
exit;
}
I would like to execute this route block asynchronously (i.e. in a separate
process).
I tried using the async_task_route command, and I can see the route block is
execute in a separate process, however some stuffs are broken (e.g.
transaction timeout, failure route). So, I thought it may be related to the
fact asynchronous execution is implemented using t_suspend/t_continue and in
this case, t_suspend/t_continue would be called twice.
The important point is to make the interaction with the PUSH server
asynchronous.
Any idea?
Thanks,
Mickael
Hi,
When receiving an INVITE, I arm a failure route and set the fr_timer to 30
seconds. After the fr_timer expires, I need to do some operations however I
see the failure route is not executed.
I guess it is related to the fact the INVITE has not been forwarded?
If yes, how can I execute code when a transaction times out after calling
t_suspend?
Thanks,
Mickael
