March 2016 - sr-users - kamailio.org

KAMAILIO Installation Problem
by Ed Todd 05 Mar '16

05 Mar '16

I have a local area network with: · A Windows PC with a VOIP application · A Linux PC with KAMailIO There is also a remote Windows PC with the same VOIP application. There is also an IPhone VOIP application that communicates with the Windows PC application. All communications use the same KAMailIO system. The IPhone application communicates with the PC on the local network. It times out trying to communicate. I have tried a URL and a static IP address for SIP_DOMAIN, neither succeeds. Here are some extracts from the log (ignore timestamp gap, several calls were attempted). I think the problem is that the reply to the PC is being sent to 192.168.1.12 instead of 92.13.147.87. Mar 4 00:28:51 SIS-Server kamailio[18136]: DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 92.13.147.87 Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:354]: tls_accept(): TLS accept successful Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:361]: tls_accept(): tls_accept: new connection from 92.13.147.87:49302 using TLSv1/SSLv3 AES256-SHA 256 Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:364]: tls_accept(): tls_accept: local socket: 96.81.57.12:5061 Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: auth [api.c:86]: pre_auth(): auth:pre_auth: Credentials with realm '96.81.57.12' not found Mar 4 00:28:55 SIS-Server kamailio[18130]: DEBUG: registrar [reply.c:374]: build_contact(): created Contact HF: Contact: <sip:hvs_uk_pc@192.168.1.12:49302;transport=TLS;line=b3d07204a26e36e>;expires=120 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060Mar 4 00:37:12 SIS-Server kamailio[18136]: ERROR: <core> [tcp_main.c:4159]: handle_tcpconn_ev(): connect 192.168.1.12:49302 failed Changes to KAMCTLRC are: SIP_DOMAIN=ed-todd-randd.com DBENGINE=MYSQL DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="kamailiorw" Changes to KAMAILIO.CFG are: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_TLS Plus I set debug=4 for logging. Whatsmyip.org shows the right IP address (static) and hostname www.ed-todd-randd.com So, any clues?

2 1

Installation problem: timeouts
by Ed Todd 05 Mar '16

05 Mar '16

I have a local area network with: · A Windows PC with a VOIP application · A Linux PC with KAMailIO There is also a remote Windows PC with the same VOIP application. There is also an IPhone VOIP application that communicates with the Windows PC application. All communications use the same KAMailIO system. The IPhone application communicates with the PC on the local network. It times out trying to communicate. The application works fine with either PC on another server (sip.antisip.com) I have tried a URL and a static IP address for SIP_DOMAIN, neither succeeds. Here are some extracts from the log (ignore timestamp gap, several calls were attempted). I think the problem is that the reply to the PC is being sent to 192.168.1.12 instead of 92.13.147.87. Mar 4 00:28:51 SIS-Server kamailio[18136]: DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 92.13.147.87 Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:354]: tls_accept(): TLS accept successful Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:361]: tls_accept(): tls_accept: new connection from 92.13.147.87:49302 using TLSv1/SSLv3 AES256-SHA 256 Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:364]: tls_accept(): tls_accept: local socket: 96.81.57.12:5061 Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: auth [api.c:86]: pre_auth(): auth:pre_auth: Credentials with realm '96.81.57.12' not found Mar 4 00:28:55 SIS-Server kamailio[18130]: DEBUG: registrar [reply.c:374]: build_contact(): created Contact HF: Contact: <sip:hvs_uk_pc@192.168.1.12:49302;transport=TLS;line=b3d07204a26e36e>;expires=120 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12] Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060Mar 4 00:37:12 SIS-Server kamailio[18136]: ERROR: <core> [tcp_main.c:4159]: handle_tcpconn_ev(): connect 192.168.1.12:49302 failed Changes to KAMCTLRC are: SIP_DOMAIN=ed-todd-randd.com DBENGINE=MYSQL DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="kamailiorw" Changes to KAMAILIO.CFG are: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_TLS Plus I set debug=4 for logging. Whatsmyip.org shows the right IP address (static) and hostname www.ed-todd-randd.com So, any clues?

1 0

DMQ question
by Alex Balashov 04 Mar '16

04 Mar '16

Hi, If I understand the DMQ documentation correctly, when a SIP request is distributed to other Kamailio instances via dmq_t_replicate(), it is not merely sent as a payload in a novel way, but actually "rehydrated" by the receiver into a mock request on the other end and processed as through it were a "real" message that came into the request_route[] in the natural way. Is this an accurate assumption? -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 9

options_reply() - ruri contains username
by Alex Balashov 04 Mar '16

04 Mar '16

Hello, This may have been discussed before, but when options_reply() from the siputils module is used to respond to OPTIONS requests and those OPTIONS requests come in with an RURI containing a user part, the following error is emitted to the logs: LM_ERR("ruri contains username\n"); No reply for the OPTIONS ping is given in this scenario. OPTIONS pings against a username are very common, and I can find no justification for this check in my interpretation of RFC 3261 scripture. According to Section 11.1 ("Construction of an OPTIONS request"): An OPTIONS request is constructed using the standard rules for a SIP request as discussed in Section 8.1.1. Moreover, the example request line given in that very section is: OPTIONS sip:carol@chicago.com SIP/2.0 Might it perhaps be agreeable to remove this constraint? Or is there some rationale for its presence that I have simply failed to grasp? Thanks! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

Reg: Facing issue in Registration of SIP Client
by sainath.ellendula＠wipro.com 04 Mar '16

04 Mar '16

Hi Franz, On Successful completion of Registration of IMS client. Now, I was trying to REGISTER SIP Client, But REGISTER request failing with 403 forbidden- User unknown. Please find attachment of X-lite configuration and Tcpdump from #422. Could you please suggest me any changes has to be done. Thanks in advance!! Regards, Sainath The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

3 9

Hello I am having problems pointing to a custom dispatcher table
by Humberto Rodriguez 03 Mar '16

03 Mar '16

Hello I am having problems pointing to a custom dispatcher table, when I use "dispatcher" as table, the kamailio service start running normal, but when I try to use for example "my_dispatcher" table the error shown bellow appears. I do not want to rebuilt the database, *my purpose is to have multiples dispatcher tables on the same server*, "dispatcher, my_dispatcher", "my_dispatcher_1", for example. The connection to the custom database is OK Thanks in advance for your help. ---------------------------------------------------------------------------------------- /var/log/messages Mar 3 14:03:00 kama-balance4 /usr/local/kamailio/sbin/kamailio[19153]: ERROR: dispatcher [dispatch.c:676]: init_ds_db(): invalid table version (found 0 , required 1, 2, 3 or 4)#012(use kamdbctl reinit) Mar 3 14:03:00 kama-balance4 /usr/local/kamailio/sbin/kamailio[19153]: ERROR: dispatcher [dispatcher.c:335]: mod_init(): could not initiate a connect to the database Mar 3 14:03:00 kama-balance4 /usr/local/kamailio/sbin/kamailio[19153]: ERROR: <core> [sr_module.c:970]: init_mod(): init_mod(): Error while initializing module dispatcher (/usr/local/kamailio/lib64/kamailio/modules/dispatcher.so)

2 1

mariadb and sql_query_async: the db driver module doesn't support async query
by Daniel Tryba 03 Mar '16

03 Mar '16

So trying to push some inserts/updates to the background I added: async_workers=1 and replaced sql_xquery("ca", "$var(query)", "ra"); sql_result_free("ra"); with sql_query_async("ca", "$var(query)"); where: $var(query)="insert into CDR.callogs (accountcode,number) values ('"+$var(accountcode)+"',substring('"+$rU+"',1,4))"; Only to find out that the queries aren't inserted and the log contains: /usr/sbin/kamailio[24754]: ERROR: sqlops [sql_api.c:429]: sql_do_query_async(): the db driver module doesn't support async query The table is an InnoDB some insert delayed should give these kind of errors, but isn't the point of sql_query_async that it does the plain normal insert in a background task? Test machine: kamailio 4.2.5

1 1

Kamailio 5.0 - db_cluster module sql_query_async support
by Daniel Tryba 03 Mar '16

03 Mar '16

If the backends for a dbcluster supports sql_query_async, sql_query_async should be available. At this moment (only tested with 4.3.x) async isn't supported.

1 0

Kamailio v4.3.5 Released
by Daniel-Constantin Mierla 03 Mar '16

03 Mar '16

Hello, Kamailio SIP Server v4.3.5 stable release is out. This is a maintenance release of the latest stable branch, 4.3, that includes fixes since release of v4.3.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.3.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.3.5. For more details about version 4.3.5 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2016/03/kamailio-v4-3-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Kamailio 5.0 - HTTP loading of config files
by Tim Chubb 03 Mar '16

03 Mar '16

As a suggestion for 5.0 being able to load config files from a URL, with any includes being taken relative to the URL would be a really handy feature. It would allow a central source for config files in a cluster and make it a much simpler process to push out changes to routing to all nodes.

6 11