Hello,
Which module do I need to have Kamailio send REGISTER messages to our carrier?
Is it the UAC module or REGISTRAR module?
It just needs to register with our carrier in order to receive inbound calls.
Regards,
Grant
Hi guys,
I have a local proxy running on private ip 192.168.3.97 and advertising the wan ip of my box (THEPUBLICIPOFMYBOX)
this local Kamailio is a stateful proxy that TM REGISTERS and INVITES to a Kamailio registrar(PUBLICIPKAMAILIOREGISTRAR)
(please have a look at the kamailio.cfg attached to this email.)
I want to force the signalling and sessions through this local proxy (some kind of outbound proxy)
I have jitsi and xlite behind (ip 192.168.3.39 and 192.168.3.16) that tries to call themselves.
user agents keep retransmitting 200 OK because they never get the ACK following the 200 OK pickup.
If i remove the advertise THEPUBLICIPOFMYBOX of the kamailio.cfg the three handshake is working ok and the call is no longer dropped after a few second!
i have a true bidirectionnal session and that's working ok.
The bad thing is RTP flows straight through router (thanks to rtpproxy i guess) but i want incoming and outgoing RTP traffic to go on central local node 192.168.3.97
How can i achieve that?
thanks.
PS: i am not using path header because i am not skilled enough and kamailio is really hard horse to train
Hi!
The attachment contains a log trace of kamailio 3.3.2. There is some
errors in the log and I wonder if it is normal operation?
The errors appeared in the middle of DHCP lease renewal and I wonder if
the configuration (of dhclient/kamailio) could be improved to prevent
such errors? Or to make sure kamailio retries udp_send sufficiently many
times. The kamailio operated normally before renewal procedure began and
after the procedure finished.
Joonas Harjumäki
Hi,
I am using centos 7.
By default on centos 7, the var/run file system is tmpfs.
So, when kamailio runs with user and group other than root, it can not
create the fifo file.
I set the kamailio service and config files to work on
usr/local/var/run/kamailio.
Now, how do i set the kamctl to work with the fifo on
/usr/local/var/run/kamailio ?
Uri
Hi!
I'd like to restrict max call duration.
Currently we have something that partially works:
dialog.default_timeout. But, as described in "How it works" section
http://www.kamailio.org/docs/modules/devel/modules/dialog.html#idp2029360
"The dialog timeout is reset each time a sequential request is
processed."
So this option works for us when the useragents don't send sequential
UPDATEs or reINVITEs.
I am not sure if it is adequate to ask for this feature in dialog
module. I am aware of possibility to terminate any call by management
command, and of cnxcc module which has call duration control. I would
love to find something that simple - a single option for max call
duration, without external mechanism (cronjob etc.) or full-blown
billing.
Any suggestions are very welcome. Thanks in advance.
Please reply to all recipients, I am not subscribed to this maillist.
