Hello,
soon I am going to travel to Singapore for FOSSASIA 2018 conference
(March 22-25 - https://2018.fossasia.org/), giving a talk about Kamailio.
Given that it is rather rare I travel to south-east Asia, I wonder if
there are other people from Kamailio community attending FOSASSIA or
happen to be in the city during the event. Maybe we can plan something
like a small group meetup to greet, have a drink or so and chat about
the project and real time communications.
Write me if you can join such a meetup. It would be great to meet some
kamailians around there!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
Hey.
I have some questions about memory settings.
I can see the default values with "kamailio -I" and change the current
values with "kamailio -M 12 -m 128". How do i see the active settings and
how do i change the default value?
I want to setup a proxy capable to handle 150CPS, 6k active calls, with
Dispatcher, Database, Number Normalizations and other operations. What are
good settings for CPU, RAM Memory, PKG_SIZE and SHM_SIZE?
Thanks for the help,
Best Regards,
Duarte Rocha
Hi,
I am having issues to start Kamailio using kamctl.
root@kamailio2:/etc/systemd/system# kamctl restart
INFO: Stopping Kamailio :
ERROR: No PID file found (/var/run/kamailio.pid)! Kamailio probably not
running
INFO: check with 'ps axw | /bin/egrep kamailio'
Using #Kamailio starts works. I can register peers and make calls between
them. But I cannot update configuration.
root@kamailio2:/var/log# kamailio
Listening on
udp: 127.0.0.1:5060
udp: 192.168.1.100:5060
tcp: 127.0.0.1:5060
tcp: 192.168.1.100:5060
Aliases:
tcp: kamailio2:5060
tcp: localhost:5060
udp: kamailio2:5060
udp: localhost:5060
I would appreciate any help provided.
Attached the syslog output
Ruben
Hi Guys,
I have an issue with sending a BYE message back down a strongswan VPN tunnel on a server in the Amazon EC2 environment.
To get the configuration working correctly I have the Public IP address bound to a loopback virtual interface, and I also have kamailio listening to it.
Calls establish without issue, but when the called party send a BYE, I cant seem to force the SIP message down the correct interface.
Due to client confidentiality I need to be careful what information I send but does anyone have a similar configuration set up, and working, I am just looking for reasons as to why force_socket and mhomed=1 doesnt appear to force the BYE message via the Public Interface but the private IP address on the server as its a NAT'd environment.
So essentially call establishes;
CLIENT---------(VIA IPSEC)-INVITE----->(UDP)KAMAILIO PUBLIC IP-------->(UDP)KAMAILIO PRIVATE IP(TCP)------------------------->CLIENT B
| | | |
|<---------(VIA IPSEC)-100 TRYING----|<----------100 TRYING---------------|<----------100 TRYING----------------------------|
| | | |
|<---------(VIA IPSEC)-180 RINGING---|<----------180 RINGING--------------|<----------180 RINGING---------------------------|
| | | |
|<---------(VIA IPSEC)-200OK --------|<----------200OK -------------------|<----------200OK --------------------------------|
| | | |
|----------(VIA IPSEC)-ACk---------> |-----------ACk--------------------->|-----------ACk---------------------------------->|
How can I ensure the BYE is forced out via the PUBLIC IP?
So I do this;
CLIENT---------(VIA IPSEC)-INVITE----->(UDP)KAMAILIO PUBLIC IP-------->(UDP)KAMAILIO PRIVATE IP(TCP)------------------------->CLIENT B
|<---------BYE (VIA IPSEC)----------------------|<----------BYE ----------------------------|<----------BYE -------------------|
As it appears to be going from Private IP and not being pushed down the IPSEC tunnel
CLIENT---------(VIA IPSEC)-INVITE----->KAMAILIO PUBLIC IP-------->KAMAILIO PRIVATE IP------------------------->CLIENT B
|<---------BYE ----------------------<----------BYE ----------------------------|<----------BYE -------------------|
on the BYE I have tried;
force_send_socket(KAMAILIO PUBLIC IP);
However doesnt appear to work, is this an issue for ip routing on the server to push the BYE correctly down the IPSEC tunnel? or is it configuration related?
Any comments welcome if people have had this issue before.
Many thanks
Jon
Hi there,
I have some situations where Kamailio receives replies (100 and then 180)
from the other end and after 2 seconds (timer defined on function
t_set_fr(0,2000)) after receive the last reply(180) the INVITE transaction
enters on the failure route with variable $T_reply_code=408.
What can be wrong here to kamailio generates a 408 internally after receive
1xx replies?
Best Regards
José Seabra
Hi Team,
Does kamailio has compatibility with E911, i.e. through location in SIP
header when 911 called?
Is there any reference document?
--
regards,
abdul basit
Hey
I need to create several testing and validation processes for the deploy of
an SBC and i would like to know your opinion on the best tools to use.
I need to create an automated group of testing scenarios and validation of
the packets sanity and SIP compliance. I also would like to validate the
packets according to some parameters of mine (ex. All numbers in E164, etc).
I'm looking at Star Trinity's SIP Tester right now but i'm not sure it can
fulfill all my needs. I've also looked into SIPp and considered creating a
Kamailio to do the validation, but i'm not sure it's worth the work if i
can find a tool prepared to do this.
Cheers :)
Hello sr-users!
I'm using Kamailio 5.1.2.
If I execute the command "serctl acl grant 1234 mygrant" I get a warning
which I have to accept with "Y":
Non-existent user '1234'. Still proceeding? [Y|N]
Is it possible to deactivate this warning? I know why this warning is
there (it's not a user, it's an alias), so I think I know what I'm doing ;-)
Regards
Stefan
