sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

Kamailio Memory Settings
by Duarte Rocha 08 Mar '18

08 Mar '18

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

2 1

Failed auth
by Aidar Kamalov 08 Mar '18

08 Mar '18

Hello! I have kamailio 5.0.5 and some cisco spa 50x phones. Sometime phone can't register to kamailio. REGISTER packets with right nonce,reponse, etc gets to kamailio but it response 401 Unauthorized with code -3 (user not found). After some attempts(or time, phone send register every 1200 seconds) or after reboot phone it register succesfully Feb 13 11:20:02 sipchel /usr/sbin/kamailio[110432]: NOTICE: <script>: AUTH: REGISTER [a470211a-b7d8faa5(a)172.16.3.1] Feb 13 11:20:02 sipchel /usr/sbin/kamailio[110432]: NOTICE: <script>: AUTH: REGISTER FAILED (code: -5) fd=voip.xxxx.org, adu=<null>, aa=<null>, ar=<null>, au=<null>, ad=<null>, aU=<null>, Au=33855(a)voip.xxxx.org [ a470211a-b7d8faa5(a)172.16.3.1] Feb 13 11:20:02 sipchel /usr/sbin/kamailio[110433]: NOTICE: <script>: AUTH: REGISTER [a470211a-b7d8faa5(a)172.16.3.1] Feb 13 11:20:02 sipchel /usr/sbin/kamailio[110433]: NOTICE: <script>: AUTH: REGISTER FAILED (code: -3) fd=voip.xxxx.org, adu=sip:voip.xxxx.org, aa=MD5, ar=voip.xxxx.org, au=33855, ad=, aU=33855, Au=33855(a)voip.xxxx.org [ a470211a-b7d8faa5(a)172.16.3.1] Feb 13 11:20:02 sipchel /usr/sbin/kamailio[110431]: NOTICE: <script>: AUTH: REGISTER [a470211a-b7d8faa5(a)172.16.3.1] Feb 13 11:20:02 sipchel /usr/sbin/kamailio[110431]: NOTICE: <script>: AUTH: REGISTER FAILED (code: -3) fd=voip.xxxx.org, adu=sip:voip.xxxx.org, aa=MD5, ar=voip.xxxx.org, au=33855, ad=, aU=33855, Au=33855(a)voip.xxxx.org [ a470211a-b7d8faa5(a)172.16.3.1] -- Aydar A. Kamalov

2 1

Issue starting with kamctl
by Ruben Lezama 08 Mar '18

08 Mar '18

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

2 1

KeepAlive Module
by Social Boh 08 Mar '18

08 Mar '18

Hello, I'm using keepalive module with drouting module... the event route works fine: NOTICE: <script>: Gateway up: OPTIONS sip:1.2.3.4 NOTICE: <script>: Gateway up: OPTIONS sip:5.6.7.8 but kamcmd command not: *kamcmd keepalive.list* foobar 42 foobar 42 { text: foobar number: 42 } { list: { nn: 17 nn: 22 } } { uri: sip:1.2.3.4 owner: drouting last checked: Wed Feb 21 11:20:12 2018 *last up: Wed Dec 31 19:00:00 1969* *last down: Wed Feb 21 11:20:13 2018* } { uri: sip:5.6.7.8 owner: drouting last checked: Wed Feb 21 11:20:12 2018 *last up: Wed Dec 31 19:00:00 1969* *last down: Wed Feb 21 11:20:12 2018* Thank you Regards... -- --- I'm SoCIaL, MayBe

2 1

Strongswan on same Server in EC2 as kamailio 4.4
by Jonathan Hunter 08 Mar '18

08 Mar '18

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

2 1

Question about t_branch_timeout behavior.
by José Seabra 08 Mar '18

08 Mar '18

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

2 1

SIP header when 911 called
by Abdul Basit 08 Mar '18

08 Mar '18

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

2 1

Choosing a Testing and Validation Tool
by Duarte Rocha 08 Mar '18

08 Mar '18

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 :)

2 1

Disable non-existent user warning
by Stefan Rüetschli 08 Mar '18

08 Mar '18

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

3 4

Kamailio not send NOTIFY for the state of the subscription when using Event: dialog (BLF)
by Borislav Gergov 08 Mar '18

08 Mar '18

Hello, The initial NOTIFY that shows the server accepts our subscription is not sent: SUBSCRIBE sip:002@10.7.2.22;transport=TCP SIP/2.0. Via: SIP/2.0/TCP 10.2.4.38:63718 ;branch=z9hG4bK-524287-1---837a95d50bef81d4;rport. Max-Forwards: 70. Contact: <sip:444@10.2.4.38:63718;transport=TCP>. To: <sip:002@10.7.2.22;transport=TCP>. From: <sip:444@10.7.2.22;transport=TCP>;tag=810bbd39. Call-ID: 8fMhJ4GnMrkSu8qxez70aw... CSeq: 1 SUBSCRIBE. Expires: 120. Accept: application/dialog-info+xml. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. User-Agent: Z. Event: dialog. Allow-Events: presence, kpml, talk. Content-Length: 0. . SIP/2.0 202 OK. Via: SIP/2.0/TCP 10.2.4.38:63718 ;branch=z9hG4bK-524287-1---837a95d50bef81d4;rport=63718;received=10.2.4.38. To: <sip:002@10.7.2.22 ;transport=TCP>;tag=339c21513a585618341888f199c2a0f6-c10d. From: <sip:444@10.7.2.22;transport=TCP>;tag=810bbd39. Call-ID: 8fMhJ4GnMrkSu8qxez70aw... CSeq: 1 SUBSCRIBE. Expires: 120. Contact: <sip:10.7.2.22:5060;transport=tcp>. Server: kamailio (5.1.1 (x86_64/linux)). Content-Length: 0. . SIP/2.0 200 OK. Via: SIP/2.0/TCP 10.2.4.38:63718 ;branch=z9hG4bK-524287-1---5b9c08901116e843;rport=63718;received=10.2.4.38. To: <sip:444@10.7.2.22 ;transport=TCP>;tag=75017b5d51cabe3de4b519c896167ee7.88a9. From: <sip:444@10.7.2.22;transport=TCP>;tag=d831f844. Call-ID: p-vce2LWcasOPThxdFZP6A... CSeq: 3 REGISTER. Contact: <sip:444@10.2.4.38:63718 ;transport=TCP;rinstance=045d4a61cf8385dc>;expires=120. Server: kamailio (5.1.1 (x86_64/linux)). Content-Length: 0. . NOTIFY sip:444@10.2.4.38:63718;transport=TCP SIP/2.0. Via: SIP/2.0/TCP 10.7.2.22;branch=z9hG4bK94d5.046c6940000000000000000000000000.0. To: <sip:444@10.7.2.22>;tag=810bbd39. From: <sip:002@10.7.2.22>;tag=339c21513a585618341888f199c2a0f6-c10d. CSeq: 2 NOTIFY. Call-ID: 8fMhJ4GnMrkSu8qxez70aw... Content-Length: 0. User-Agent: kamailio (5.1.1 (x86_64/linux)). Max-Forwards: 70. Event: dialog. Contact: <sip:10.7.2.22:5060;transport=tcp>. Subscription-State: terminated;reason=timeout. . SIP/2.0 200 OK. Via: SIP/2.0/TCP 10.7.2.22;branch=z9hG4bK94d5.046c6940000000000000000000000000.0. Contact: <sip:444@10.2.4.38:63718;transport=TCP>. To: <sip:444@10.7.2.22>;tag=810bbd39. From: <sip:002@10.7.2.22>;tag=339c21513a585618341888f199c2a0f6-c10d. Call-ID: 8fMhJ4GnMrkSu8qxez70aw... CSeq: 2 NOTIFY. User-Agent: Z. Content-Length: 0.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users