- sr-users - kamailio.org

Stress Testing
by Jack Stevens 17 Aug '16

17 Aug '16

Hi Guys, I have been stress testing my Kamailio box but I am unable to get it upto 2000 concurrent calls it starts to fall over at 1300 have you got any ideas on how I can increase the performance of kamilio btw I am also using rtpengine Kind Regards -- CONFIDENTIAL EMAIL FROM NETCALL TELECOM LIMITED This email, and any attachments, is intended only for the above addressee. It may contain private and/or confidential information. If you have received this email in error you are on notice of its status, please immediately notify the sender by return email then delete this message and any attachments. If you are not the addressee, except to notify the sender, you must not use, disclose, copy or distribute this email and/or its attachments. Netcall Telecom accepts no responsibility for any changes made to this message after it has been sent by the original author. Opinions or views expressed in this email may be those of the individual sender and not Netcall Telecom. Nothing in this email shall bind Netcall Telecom in any contract or obligation Netcall Telecom Ltd Registered in England 2831215. Registered Office : 3rd Floor, Hamilton House, 111 Marlowes, Hemel Hempstead, Herts, HP1 1BB

5 7

Kamailio SIP 500
by Rodrigo Moreira 17 Aug '16

17 Aug '16

Hello, You can help me to due with the error: SIP 500 - Server error on UAR select next S-CSCF. What am I doing wrong? Thanks. Regards. -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

3 3

t_set_fr() different behavior whether transport is udp or tcp
by Daniel Tryba 16 Aug '16

16 Aug '16

I'm seeing a different behavior of t_set_fr depending on transports. Scenario is that a endpoint has a failover defined in the registrat after 10s (t_set_fr(10000) and handling the locally generated 408 to the failover destination). This works fine when the request and response where delivered over UDP. When the Path is TCP the failover happends after 30s (even when using a different time t_set_fr(20000) so it is not a factor 3 or something like that). Setup: OK, 10s: Orig->UDP->loadbalancer->UDP->registrar->UDP->loadbalancer->TCP->Term Fail, 30s: Orig->UDP->loadbalancer->TCP->registrar->TCP->loadbalancer->TCP->Term Loadbalancer and registrar are kamailio machines (4.3.6). Communication between lb and registrar is based on dispatcher and path modules. 1 sip:registrar:5060;transport=udp 8 0 or via tcp: 1 sip:registrar:5060;transport=tcp 8 0 In the location database of the registrar the difference between the cases is: socket: udp:registrar:5060 or via tcp tcp:registrar:5060 path: <sip:lb@loadbalancer;lr;received=sip:1.2.3.4:5067%3Btransport%3Dtcp> or via tcp <sip:lb@loadbalancer;transport=tcp;lr;received=sip:1.2.3.4:5067%3Btransport%3Dtcp> Looking at debug(=3) nothing happens between the initial INVITE and the local 408 as far as I can see.

2 2

302 - stop sending once ACKed
by jaflong jaflong 16 Aug '16

16 Aug '16

I have kamailio as a redirect server. It responds with 302 to invites. The problem I am having is it continues to send the 302 multiple times. How can i get it to stop sending once it gets the first ACK

2 1

Is ACK required in a re-invite?
by Jay Li 15 Aug '16

15 Aug '16

Dear All, I just have a basic SIP question on re-invite. I wonder if "ACK" is required in a re-invite scenario, like re-invite -> 200 OK -> ACK. What I've seen is for some reason, my PSTN doesn't send a "ACK" back to me after my 200 OK response to their re-invite. I don't know if not sending an ACK in a re-invite is an allowed behavior. Thanks. Regards,Jay

2 3

kamailio TLS mod_register failed
by wanmon wanmon 15 Aug '16

15 Aug '16

4 14

Via in locally generated PUBLISH (using different presence server address)
by Asgaroth 15 Aug '16

15 Aug '16

Hi All, I have a configuration where we run a multi-homed proxy/loadbalancer and a seperate internal presence server. We then use pua/pua-dialoginfo on the proxies to publish dialog state to the internal presence server. The proxies listen on udp:external_ip:5062 and udp:internal_ip1:5060. The presence server listens on udp:internal_ip2:5060 on a seperate server. The problem I am coming accross is that when kamailio generates a PUBLISH message for some dialogs it creates the via header with address external:ip:5062, however the pua module is configured to send to the presence server address on internal_ip2:5060. I have a route which forces the sending socket ($fs) to be udp:internal_ip1:5060. What happens then is that the presence server tries to send the 200 reply to the PUBLISH message back to internal_ip1:5062 (when it should be internal_ip1:5060), I'm thinking this is because the Via header has host as external_ip:5062. Is it possible, from event-route[tm:local-request] to rewrite the via header so that it reflects internal_ip1:5060 instead of external_ip:5062? I did try the following snippet from event-route[tm:local-request], but I got module parse errors on the Via header: if (is_method("PUBLISH")) { subst_hf("Via", "/ 1\.2\.3\.[0-9]+:5062;/ $sel(cfg_get.socket.internal_ip);/", "f"); } [7370]: ERROR: <core> [parser/parse_via.c:2607]: parse_via(): ERROR:parse_via on <1> state 5 (default) [7370]: ERROR: <core> [parser/parse_via.c:2708]: parse_via(): ERROR: parse_via on: <SIP/2.0/UDP external_ip:5062;branch=z9hG4bK96eb.0f014ae4000000000000000000000000.0#015#012 internal_ip1; [7370]: ERROR: <core> [parser/parse_via.c:2712]: parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP external_ip:5062;branch=z9hG4bK96eb.0f014ae4000000000000000000000000.0#015#012 > [7370]: ERROR: <core> [parser/msg_parser.c:125]: get_hdr_field(): ERROR: get_hdr_field: bad via [7370]: INFO: <core> [parser/msg_parser.c:338]: parse_headers(): ERROR: bad header field [Via: SIP/2.0/UDP 1] [7370]: ERROR: <core> [parser/msg_parser.c:690]: parse_msg(): ERROR: parse_msg: message=<PUBLISH sip:user@domain;transport=UDP SIP/2.0#015#012Via: SIP/2.0/UDP external_ip:5062;branch=z9hG4bK96eb.0f014ae4000000000000000000000000.0#015#012 internal_ip1;To: <sip:user@domain;transport=UDP>#015#012From: <sip:user@domain;transport=UDP>;tag=3e8fdaca277026bf3e6d75c5e5313096-f162#015#012CSeq: 10 PUBLISH#015#012Call-ID: 5634294b786134b3-7370@external_ip#015#012Content-Length: 692#015#012User-Agent: kamailio (bfievklb04)#015#012Max-Forwards: 70#015#012Event: dialog#015#012Expires: 10901#015#012Content-Type: application/dialog-info+xml#015#012#015#012<?xml version="1.0"?>#012<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:user@domain;transport=UDP">#012 <dialog id="mvqXXaAr24DHdfsffYKZeA.." call-id="mvqXXaAr24DHdfsffYKZeA.." direction="initiator">#012 <state>Trying</state>#012 <remote>#012 <identity>sip:1234567@domain;transport=UDP</identity>#012 <target uri="sip:1234567@domain;transport=UDP"/>#012 </remote>#012 <local>#012 <identity>sip:user@domain;transport=UDP</identity>#012 <target uri="sip:user@domain;transport=UDP"/>#012 </local>#012 </dialog>#012</dialog-info>#012> [7370]: ERROR: <core> [msg_translator.c:3057]: build_sip_msg_from_buf(): parsing failed [7370]: ERROR: tm [uac.c:163]: uac_refresh_hdr_shortcuts(): failed to parse msg buffer [7370]: ERROR: tm [uac.c:487]: t_uac_prepare(): failed to refresh header shortcuts [7370]: ERROR: pua [send_publish.c:700]: send_publish(): in t_request tm module function [7370]: ERROR: pua_dialoginfo [dialog_publish.c:358]: dialog_publish(): while sending publish To me, it looks like the replace section of the subst_hf sub expression is being appended to the end of the via header instead of replacing the address section found. I have sanitized the above output to not show internal details, but if you need it, I can send it on to you privately. Am I going about this issue in the correct way, and, if so, where am I going wrong with the subst_hf snippet above? Kamailio version is 4.3.6. Any pointers/tips/trciks are greatly appreciated. Thanks

2 5

Installation question on ubuntu xenial / undefined symbol: EVP_sha1
by Christian Lox 15 Aug '16

15 Aug '16

Hi. I am trying to install kamailio 4.4.2 on ubuntu xenial, for use with kazoo. Using source and compiling just went fine, but /usr/local/sbin/kamailio -c throws ERROR: <core> [sr_module.c:582]: load_module(): could not open module </usr/local/lib64/kamailio/modules/outbound.so>: /usr/local/lib64/kamailio/modules/outbound.so: undefined symbol: EVP_sha1 any hint appreciated! Thanks, Christian

2 1

Re: [SR-Users] undefined symbol: EVP_sha1 when using outbound module
by Christian Lox 15 Aug '16

15 Aug '16

Hi. Same problem here; undefined symbol : EVP_sha1 in outbound.so pkg-config was available when compiled from source. Tried installing several dev packages and so on but always the same error. How do i link it against libssl/libcrypto? Thanks, Christian

2 2

access header variables in failure route
by jaflong jaflong 13 Aug '16

13 Aug '16

On an 302 message caught in failure_route Is it possible to get to access $hdr(xxx) of the 302. When I do this $hdr(xxx) it is null.

2 1

Struggling at 1000 Concurrent Calls
by Jack Stevens 12 Aug '16

12 Aug '16

Hi Guys, I have built an SBC using kamailio with the dispatcher module and rtpengine and when I run a sip test I find it struggles to go past 1000 calls at 20cps would really like some help on how to resolve this. As I am very new to this I am stuggeling to work out where to start from. I have found when running this sort of load the debian box drops pings any ideas Kind Regards -- CONFIDENTIAL EMAIL FROM NETCALL TELECOM LIMITED This email, and any attachments, is intended only for the above addressee. It may contain private and/or confidential information. If you have received this email in error you are on notice of its status, please immediately notify the sender by return email then delete this message and any attachments. If you are not the addressee, except to notify the sender, you must not use, disclose, copy or distribute this email and/or its attachments. Netcall Telecom accepts no responsibility for any changes made to this message after it has been sent by the original author. Opinions or views expressed in this email may be those of the individual sender and not Netcall Telecom. Nothing in this email shall bind Netcall Telecom in any contract or obligation Netcall Telecom Ltd Registered in England 2831215. Registered Office : 3rd Floor, Hamilton House, 111 Marlowes, Hemel Hempstead, Herts, HP1 1BB

3 3

CDP Error S-CSCF Kamailio
by Rodrigo Moreira 12 Aug '16

12 Aug '16

Hello Carsten Bock, I got to advance in the event REGISTER, but now face the following problem: When I type the command: */etc/init.d/kamailio restart* Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [diameter_peer.c:428]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [diameter_peer.c:447]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated....aning up. Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [worker.c:140]: worker_destroy(): Unlocking workers waiting on empty queue... Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [worker.c:143]: worker_destroy(): Unlocking workers waiting on full queue... Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: CRITICAL: cdp [diameter_peer.c:487]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [mod.c:244]: cdp_exit(): ... CDiameterPeer child stoped Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Aug 10 20:40:52 scscf systemd[1]: kamailio.service: control process exited, code=exited status=255 Aug 10 20:40:52 scscf systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Aug 10 20:40:52 scscf systemd[1]: Unit kamailio.service entered failed state. I can not start the Kamailio, I used the examples codes available in the repository (GIT). You suggest something I may be doing wrong? Can you help me? I attached my config files. Thank you very much. Regards. -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

4 4

Kamailio 4.4 Dispatcher on Debian 8 with MongoDB
by Jonathan Hunter 12 Aug '16

12 Aug '16

Hi Guys, I am integrating kamailio with MongoDB, and it works well with subscriber/location tables. However when using the dispatcher module I am getting the following error even though the IP Im trying to get to is routeable; /usr/local/kamailio-4.4/sbin/kamailio[2998]: ERROR: dispatcher [dispatch.c:1403]: ds_get_index(): destination set [1] not foundAug 11 17:01:47 ip-172-31-43-8 /usr/local/kamailio-4.4/sbin/kamailio[2998]: ERROR: dispatcher [dispatch.c:1832]: ds_select_dst_limit(): destination set [1] not found I created the table as below; db.getCollection("version").insert({table_name: "dispatcher", table_version: NumberInt(4) }) And the entry Im routing to is; db.dispatcher.find().pretty(){ "_id" : ObjectId("57acadc81e7e803fa565bce3"), "setid" : "1", "destination" : "sip:1.1.1.1:5080;transport=tcp", "flags" : "0", "priority" : "100", "attrs" : "name=labfS", "description" : "FreeSWITCH1"} Is there something I am missing ? Has anyone else got it working with Mongo? Thanks Jon

2 1

Kamailio CDP Error - SCSCF
by Rodrigo Moreira 12 Aug '16

12 Aug '16

Hello, I can not make the S-CSCF module work, is giving CDP error. CRITICAL: cdp [diameter_peer.c: 485]: diameter_peer_destroy (): destroy_diameter_peer (): Bye Bye from C Diameter Peer test I am using the examples available in the repository still occur errors that prevent Kamailio to boot. Can someone help me? Someone has the kamailio.cfg, scscf.cfg and scscf.xml files to share? Regards. -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

1 0

Process redirected message
by jaflong jaflong 11 Aug '16

11 Aug '16

kamailio A relays to kamailio B kamailio B send 300 redirect back to kamailio A In this setup how do I catch the redirect response back from kamailio B What conditions should I do to catch and further process the redirect message Regards

2 2

Re: [SR-Users] kamailio starts looping invites(some) back to itself.
by SamyGo 10 Aug '16

10 Aug '16

Hi Aqs, How about putting a loop protection of some sort additionally like $si != myself. Is there any chance the API http call is getting skipped to relay w/o getting any reply back and hence looping back to itself ? Regards, Sammy On Jul 22, 2016 14:17, "Aqs Younas" <aqsyounas(a)gmail.com> wrote: Hi, I am using http_async_client and dispatcher modules of Kamailio. Here is scenario! http_async_client makes calls to an API to get groupid upon which dispatcher sends calls. I am using SIPp to generate calls with 100 cps. I see some calls being failed with an error cause, 483 Too Many Hops. Taking the trace shows Kamailio routing some calls to itself. I think this is not a configuration issue since all calls are same(follow same logic) and some calls get failed. Any pointer is much appreciated. Best Regards. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

5 13

Problem receiving large payloads from JSONRPC-S
by Alex Balashov 10 Aug '16

10 Aug '16

Hi, I'm requesting 'dlg.list' from JSONRPC-S via XHTTP on a rather busy server, i.e. event_route[xhttp:request] { xlog("L_INFO", 'action=ER-XHTTP-REQUEST | ret=LOG_HTTP_REQ | data={"method": "$rm", "path": "$hu", "source": "$si:$sp"}'); # Digest challenge omitted. if($hu =~ "^/rpc") { xlog("L_INFO", 'action=ER-XHTTP-REQUEST | ret=JSON_RPC_REQUEST | data={"path": "$hu"}'); jsonrpc_dispatch(); } else { xhttp_reply("404", "Not Found", "text/html", ""); } } # curl --digest -v \ -X POST -H 'Content-Type: application/json' \ -H 'Call-ID: abc12' \ -d '{"jsonrpc": "2.0", "method": "dlg.list", "id": "0deadb33f"}' \ 'http://sipus_adm:raSheinmet4@10.0.62.74:5060/csrp_rpc/' and finding that when there's more than a hundred or so dialogs in play, Kamailio abruptly closes the connection in the middle of returning the output: ----- "tag": "AF5DA9B4-6D5", "contact": "sip:14045551212@xxx.xxx.xxx.xxx:5060", "cseq": "0", "route_set": "", "socket": "udp:xxx.xxx.xxx.xxx:5060" }, * transfer closed with 151674 bytes remaining to read * Closing connection #0 curl: (18) transfer closed with 151674 bytes remaining to read "profiles": ["total",[root@proxy kamailio]# ------ I can't seem to figure out what parameters regulate this. I'm using the following TCP settings: tcp_async=yes tcp_connect_timeout=5 tcp_crlf_ping=no tcp_keepalive=yes tcp_keepidle=30 tcp_linger2=10 tcp_max_connections=4096 tcp_send_timeout=3 tcp_accept_no_cl=yes tcp_wq_blk_size=65535 tcp_wq_max=20971520 But this doesn't seem to have had any effect. Any help appreciated! Thanks, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 6

Duplicate ACC records in db when using db_cluster
by Jan Hazenberg 09 Aug '16

09 Aug '16

Hi, I have a issue with the db_cluster module. All works fine but when i enable ACC records to the database i get duplicate entry's in the acc table. I have 2 nodes enabled: # ----- db_cluster params ----- modparam("db_cluster", "connection", "con1=>mysql://kamailio:password@10.1.1.1/kamailio") modparam("db_cluster", "connection", "con2=>mysql://kamailio:password@10.1.1.2/kamailio") modparam("db_cluster", "cluster", "cls1=>con1=9s8p;con2=9s8p") When i remove one node from the pool the acc records look fine. Could this be a bug? Or should i bypass the db_cluster for accounting? I'm running kamailio 4.4.2. Thanks, Jan Hazenberg

3 5

When Not Found
by Nahum Nir 09 Aug '16

09 Aug '16

Hi List, When sending an invite and the calle not found or responding with an ACK I want my script do some costume work. When can I do it (using regular script)? Thanks, Nir

3 2

Kamailio Regiser
by Rodrigo Moreira 09 Aug '16

09 Aug '16

Hello everyone, I am deploying an IMS core, however I can not register the user (Bob). The entities are all working PCSCF, ICSCF SCSCF and HSS, I suppose. However after utiliizar Wireshark is returned the following error: 604 Does not exist anywhere - HSS User Unknow 400 Bad Request - P-visited-Network-ID header missing. What am I doing wrong? I ask for help, the great community. Or methods to better understand what is causing the problem. Is it DNS? Regards. -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

2 1

open websocket connction from kamailio
by Uri Shacked 08 Aug '16

08 Aug '16

Hi, Is it possible to open a websocket connection from kamailio to another websocket server. not something based on sip, just a websocket to send to the websocket server messages from cfg file. (like http_query) ?? Uri

1 0

Feature Request CarrierRoute To and Contact header Strip
by Yasin CANER 08 Aug '16

08 Aug '16

2 1

app_python access to message body content
by Anthony Joseph Messina 08 Aug '16

08 Aug '16

I'm trying to play around a bit with app_python using the examples in the source. I'd like to access the content of the body of the SIP message, but can't figure out how to do that. I can get headers, method, etc. How does one access body content with app_python? Thanks. -A -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

3 4

TCP message parsing & connection close issue
by Alex Balashov 08 Aug '16

08 Aug '16

Hello, I've got an odd issue where: 1. TCP client makes call out through Kamailio. 2. Call is answered, TCP client sends e2e ACK. 3. Parser chokes on ACK, closes TCP connection (SYN+FIN). 4. Subsequent messages from the client, immediately following the ACK (about 240 ms later), come through because the client is halfway around the world - about 250 ms away - and is not yet aware the connection has been closed. Otherwise, it would presumably try to re-establish the connection before sending anything. Anyway, messages from the parser concerning the ACK are: --- Aug 4 21:55:57 sip-proxy /usr/local/kamailio/sbin/kamailio[14680]: INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP Aug 4 21:55:57 sip-proxy /usr/local/kamailio/sbin/kamailio[14680]: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) Aug 4 21:55:57 sip-proxy /usr/local/kamailio/sbin/kamailio[14680]: ERROR: <core> [parser/msg_parser.c:690]: parse_msg(): ERROR: parse_msg: message=<0#015#012a=rtcp:4007 IN IP4 1.1.1.1:1071#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:96 telephone-event/8000#015#012a=fmtp:96 0-16#015#012ACK sip:*98*0b3ff883-a89d-4317-b758-8979682f5357@10.0.2.53:5060;transport=udp SIP/2.0#015#012Via: SIP/2.0/TCP 1.1.1.1:61979;branch=z9hG4bKPjc15bf9fdded940cab7f859634b9f036e;alias#015#012Max-Forwards: 70#015#012From: sip:4b57be8d-267d-48c4-aa82-0f3a269d74cb@sip.evaristesys.com;tag=dd1d7fd0344d47b7b22c4017091df17a#015#012To: sip:*98*0b3ff883-a89d-4317-b758-8979682f5357@sip.evaristesys.com;tag=2rZDKcBFmU65S#015#012Call-ID: 5ba5a84451074159aaaa931eb1f98fe5#015#012CSeq: 3071 ACK#015#012Route: <sip:2.2.2.2;transport=tcp;lr;r2=on;ftag=dd1d7fd0344d47b7b22c4017091df17a;rtp_set_id=1>#015#012Route: <sip:10.0.2.119;lr;r2=on;ftag=dd1d7fd0344d47b7b22c4017091df17a;rtp_set_id=1>#015#012Content-Length: 0#015#012#015#012> Aug 4 21:55:57 sip-proxy /usr/local/kamailio/sbin/kamailio[14680]: ERROR: <core> [receive.c:173]: receive_msg(): core parsing of SIP message failed (1.1.1.1:61979/2) --- That doesn't look like a clean message buffer to me. The message should start here: ACK sip:*98*0b3ff883-a89d-4317-b758-8979682f5357@10.0.2.53:5060;transport=udp SIP/2.0#015#012Via: SIP/2.0/TCP ... But instead it's got these SDP attributes prepended: 0#015#012a=rtcp:4007 IN IP4 1.1.1.1:1071#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:96 telephone-event/8000#015#012a=fmtp:96 0-16#015#012 These SDP attribute appear to have fallen off the back of the SDP offer in the initial INVITE: v=0 o=- 3679365582 3679365582 IN IP4 10.0.0.200 s=pjmedia t=0 0 m=audio 4006 RTP/AVP 0 8 96 c=IN IP4 1.1.1.1 The relationship between the 4006 RTP port and the 4007 RTCP port suggests that these two things belong together. This is on kamailio 4.4.0 (x86_64/linux) d4f23c. Any help would be greatly appreciated! The issue is consistently reproducible and this happens every time. Cheers, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 6

Synonyms User Name
by Nahum Nir 07 Aug '16

07 Aug '16

Hello List, I wonder if there is a way to define synonyms. For example, I there is a person by the name of John Smith with extention 5555 I would like to have a user john_smith that will also be available if some INVITE 5555. Thanks, Nahum

2 3

Prepaid system using dialog and sqlops
by Infinicalls Infinicalls 06 Aug '16

06 Aug '16

Hi, I am still struggling to get a prepaid system for my service. After installing SIREMIS, I am able to get the CDRs updated. But even after adding the cron settings, the call duration doesn't get updated. And also in http://lists.sip-router.org/pipermail/sr-users/2012-January/071517.html it has been mentioned that "If it is the case of 1 call per user at a time, then practically can be done from kamailio config only. When call starts, compute the max duration for that call based on caller/destination (e.g., call a stored procedure via sqlops) and set the dialog timeout to that duration. When call ends (BYE in main route or timeout route) update the credit accordingly." Can somebody let me know if my understanding is correct. 1) Add a field called "credits" in the database. And topup that field. 2) First compute max permitted duration for that user by multiplying the cost for number prefix (say +91) and pulse. 3) And finally add this value to timeout of dialog. modparam("dialog", "default_timeout", 100000) $dlg_ctx(timeout_bye) = 1; Will this work? Any help would be appreciated. regards Ganesh Kumar

3 4

segfault when using sipt modifications
by david 05 Aug '16

05 Aug '16

hello all i'm trying to add a ISUP multipart in a regular call using the textops module, and despite seeing one previous issue int he mail list, i'm finding some issue here i'm using this commands msg_apply_changes(); set_body_multipart(,"2123894789_1257887457"); msg_apply_changes(); append_body_part("\x01\x12\x49\x00\x0a\x03\x02\x0a\x08\x84\x90\x33 \x41\x72\x17\x00\x06\x0a\x08\x04\x13\x93\x70\x21\x73\x23\x10\x08\x01\x00 \x00","application/isup;version=itu-t92+","signal;handling=optional"); msg_apply_changes(); sipt_destination($rU, 31, 4); sipt_set_calling($fU, 4, 0, 3); msg_apply_changes(); before the record_route command, and when using sipt_destination($rU, 31, 4); i'm getting asegfault here you have the logs could you please give me any clue about something i'm missing or doing wrong? thanks alot and regards david 5(24552) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): SIP Request: 5(24552) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): method: <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): uri: <sip:34666988297@79.170.71.132:5060> 5(24552) DEBUG: <core> [parser/msg_parser.c:614]: parse_msg(): version: <SIP/2.0> 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK7ma5t4FKS0SKa>; state=16 5(24552) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 5(24552) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 5(24552) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 5(24552) DEBUG: <core> [receive.c:178]: receive_msg(): After parse_msg... 5(24552) DEBUG: <core> [receive.c:221]: receive_msg(): preparing to run routing scripts... 5(24552) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 65 5(24552) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 5(24552) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [49]; uri=[sip:34666988297@79.170.71.132:5060;user=phone] 5(24552) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:34666988297@79.170.71.132:5060;user=phone> ] 5(24552) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <94568362> <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=104 5(24552) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 5(24552) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=5jBBFae4D90rg 5(24552) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 5(24552) DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 5(24552) DEBUG: siputils [checks.c:97]: has_totag(): no totag 5(24552) DEBUG: <core> [socket_info.c:564]: grep_sock_info(): checking if host==us: 13==13 && [79.170.71.132] == [79.170.71.132] 5(24552) DEBUG: <core> [socket_info.c:567]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 5(24552) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=1 global id=0 T start=0xffffffffffffffff 5(24552) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=46859, isACK=0 5(24552) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed 5(24552) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found 5(24552) DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=1 global id=1 T end=(nil) 5(24552) DEBUG: tm [t_lookup.c:1312]: t_newtran(): DEBUG: t_newtran: msg id=1 , global msg id=1 , T on entrance=(nil) 5(24552) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=46859, isACK=0 5(24552) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed 5(24552) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found 5(24552) DEBUG: tm [t_hooks.c:358]: run_reqin_callbacks_internal(): DBG: trans=0x7fb3fb0c64e0, callback type 1, id 0 entered 5(24552) DEBUG: <core> [md5utils.c:67]: MD5StringArray(): MD5 calculated: 5ea9736b3bdcf90a4c3043a5a492b31f 5(24552) DEBUG: <core> [select.c:412]: run_select(): Calling SELECT 0x7fb404252ef8 5(24552) INFO: Theseus-Test Call 69672589-67f5-4edd-8844-f6ad2ee5b208 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: Call-ID = 69672589-67f5-4edd-8844-f6ad2ee5b208 5(24552) DEBUG: app_lua [app_lua_api.c:643]: app_lua_run(): reload deactivated 5(24552) DEBUG: app_lua [app_lua_api.c:644]: app_lua_run(): executing Lua function: [[allow_src_uri]] 5(24552) DEBUG: app_lua [app_lua_api.c:645]: app_lua_run(): lua top index is: 4 5(24552) DEBUG: app_lua [app_lua_sr.c:979]: lua_sr_pv_get(): pv get: $avp(s:call_obj) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:call_obj)] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:979]: lua_sr_pv_get(): pv get: $ci 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$ci] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $var(authorized) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$var(authorized)] found in cache 5(24552) INFO: Theseus-Test Call 69672589-67f5-4edd-8844-f6ad2ee5b208 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: Method INVITE from 79.170.64.130:5080 authorized 5(24552) INFO: Theseus-Test Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: Object 58825 assigned to Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208 5(24552) INFO: Theseus-Test Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: The call has been sent to RG 106406 5(24552) DEBUG: app_lua [app_lua_api.c:643]: app_lua_run(): reload deactivated 5(24552) DEBUG: app_lua [app_lua_api.c:644]: app_lua_run(): executing Lua function: [[get_rg_info]] 5(24552) DEBUG: app_lua [app_lua_api.c:645]: app_lua_run(): lua top index is: 4 5(24552) DEBUG: app_lua [app_lua_sr.c:979]: lua_sr_pv_get(): pv get: $ci 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$ci] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:979]: lua_sr_pv_get(): pv get: $avp(s:call_obj) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:call_obj)] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:979]: lua_sr_pv_get(): pv get: $shv(flag_list) 5(24552) DEBUG: <core> [pvapi.c:293]: pv_cache_add(): pvar [$shv(flag_list)] added in cache 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG 106406 attributes: 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 description = PBX--NOC-TEST 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 admin_status = 1 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 cir_direction = 2 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 ani_posttranslation = 0 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 ani_posttranslation_table = 0 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 posttranslation = 1 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 posttranslation_table = 106384 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 pound = 2 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 gw_port = 5060 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: RG OUT 106406 custom_flags = None 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:description) 5(24552) DEBUG: <core> [usr_avp.c:882]: parse_avp_ident(): Parsing 's:description' 5(24552) DEBUG: <core> [pvapi.c:293]: pv_cache_add(): pvar [$avp(s:description)] added in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:admin_status) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:admin_status)] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:cir_direction) 5(24552) DEBUG: <core> [usr_avp.c:882]: parse_avp_ident(): Parsing 's:cir_direction' 5(24552) DEBUG: <core> [pvapi.c:293]: pv_cache_add(): pvar [$avp(s:cir_direction)] added in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:ani_posttranslation_table) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:ani_posttranslation_table)] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:posttranslation_table) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:posttranslation_table)] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:pound) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:pound)] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:gw_ip) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:gw_ip)] found in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:1101]: lua_sr_pv_sets(): pv set: $avp(s:gw_port) 5(24552) DEBUG: <core> [pvapi.c:321]: pv_cache_lookup(): pvar [$avp(s:gw_port)] found in cache 5(24552) INFO: app_lua [app_lua_sr.c:96]: lua_sr_log(): Call 58825 / Call-ID 69672589-67f5-4edd-8844-f6ad2ee5b208: Custom flags = None 5(24552) DEBUG: app_lua [app_lua_sr.c:979]: lua_sr_pv_get(): pv get: $shv(custom_flag_list) 5(24552) DEBUG: <core> [pvapi.c:293]: pv_cache_add(): pvar [$shv(custom_flag_list)] added in cache 5(24552) DEBUG: app_lua [app_lua_sr.c:979]: lua_sr_pv_get(): pv get: $shv(custom_flag_list_branch) 5(24552) DEBUG: <core> [pvapi.c:293]: pv_cache_add(): pvar [$shv(custom_flag_list_branch)] added in cache 5(24552) DEBUG: textopsx [textopsx.c:231]: msg_apply_changes_f(): SIP message content updated - reparsing 5(24552) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): SIP Request: 5(24552) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): method: <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): uri: <sip:34666988297@79.170.71.132:5060> 5(24552) DEBUG: <core> [parser/msg_parser.c:614]: parse_msg(): version: <SIP/2.0> 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK7ma5t4FKS0SKa>; state=16 5(24552) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 5(24552) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 5(24552) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 5(24552) DEBUG: textops [textops.c:1577]: set_multibody_helper(): delimiter<21>:[2123894789_1257887457] 5(24552) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 5(24552) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [49]; uri=[sip:34666988297@79.170.71.132:5060;user=phone] 5(24552) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:34666988297@79.170.71.132:5060;user=phone> ] 5(24552) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <94568362> <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=104 5(24552) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 5(24552) DEBUG: textops [textops.c:1486]: generate_boundary(): adding final CRLF+CRLF 5(24552) DEBUG: textops [textops.c:1714]: set_multibody_helper(): content-type<48>:[multipart/mixed;boundary="2123894789_1257887457"] 5(24552) DEBUG: textops [textops.c:1768]: set_multibody_helper(): set flag FL_BODY_MULTIPART 5(24552) INFO: <core> [msg_translator.c:1692]: get_boundary(): Content-Type hdr has no params <application/sdp> 5(24552) WARNING: <core> [msg_translator.c:1958]: build_req_buf_from_sip_req(): check_boundaries error 5(24552) DEBUG: <core> [msg_translator.c:422]: clen_builder(): content-length: 189 (189) 5(24552) DEBUG: textopsx [textopsx.c:231]: msg_apply_changes_f(): SIP message content updated - reparsing 5(24552) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): SIP Request: 5(24552) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): method: <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): uri: <sip:34666988297@79.170.71.132:5060> 5(24552) DEBUG: <core> [parser/msg_parser.c:614]: parse_msg(): version: <SIP/2.0> 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK7ma5t4FKS0SKa>; state=16 5(24552) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 5(24552) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 5(24552) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 5(24552) ERROR: <core> [lvalue.c:345]: lval_pvar_assign(): non existing right pvar 5(24552) ERROR: <core> [lvalue.c:405]: lval_assign(): assignment failed at pos: (390,18-390,44) 5(24552) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 5(24552) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [49]; uri=[sip:34666988297@79.170.71.132:5060;user=phone] 5(24552) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:34666988297@79.170.71.132:5060;user=phone> ] 5(24552) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <94568362> <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=189 5(24552) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 5(24552) DEBUG: textops [textops.c:1486]: generate_boundary(): adding final CRLF+CRLF 5(24552) DEBUG: <core> [msg_translator.c:1719]: get_boundary(): boundary is <--2123894789_1257887457> 5(24552) DEBUG: <core> [msg_translator.c:1839]: check_boundaries(): last bondary without -- at the end 5(24552) DEBUG: <core> [msg_translator.c:1639]: replace_body(): old size body[189] actual[319] 5(24552) DEBUG: <core> [msg_translator.c:422]: clen_builder(): content-length: 319 (319) 5(24552) DEBUG: textopsx [textopsx.c:231]: msg_apply_changes_f(): SIP message content updated - reparsing 5(24552) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): SIP Request: 5(24552) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): method: <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): uri: <sip:34666988297@79.170.71.132:5060> 5(24552) DEBUG: <core> [parser/msg_parser.c:614]: parse_msg(): version: <SIP/2.0> 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 5(24552) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK7ma5t4FKS0SKa>; state=16 5(24552) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 5(24552) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 5(24552) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 5(24552) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 5(24552) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [49]; uri=[sip:34666988297@79.170.71.132:5060;user=phone] 5(24552) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:34666988297@79.170.71.132:5060;user=phone> ] 5(24552) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <94568362> <INVITE> 5(24552) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=319 5(24552) DEBUG: <core> [parser/parse_body.c:87]: get_boundary_param(): boundary is "2123894789_1257887457" 5(24552) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 5(24552) DEBUG: <core> [parser/parse_body.c:87]: get_boundary_param(): boundary is "2123894789_1257887457" 5(24552) CRITICAL: <core> [data_lump.c:297]: del_lump(): offset + len exceeds message size (1176 + 51 > 1201) 35(24582) CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 17 35(24582) DEBUG: <core> [tcp_main.c:3448]: handle_ser_child(): dead child 5, pid 24552 (shutting down?) 35(24582) DEBUG: <core> [io_wait.h:598]: io_watch_del(): DBG: io_watch_del (0xa2ae40, 17, -1, 0x0) fd_no=39 called 0(24547) ALERT: <core> [main.c:739]: handle_sigs(): child process 24552 exited by a signal 6 0(24547) ALERT: <core> [main.c:742]: handle_sigs(): core was not generated 0(24547) INFO: <core> [main.c:754]: handle_sigs(): terminating due to SIGCHLD 0(24547) DEBUG: <core> [main.c:756]: handle_sigs(): terminating due to SIGCHLD 34(24581) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 33(24580) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 32(24579) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 31(24578) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 30(24577) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 29(24576) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 28(24575) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 27(24574) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 26(24573) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 25(24572) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 24(24571) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 23(24570) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 22(24569) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 21(24568) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 20(24567) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 19(24566) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 18(24565) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 17(24564) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 16(24563) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 15(24562) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 14(24561) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 13(24560) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 12(24559) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 11(24558) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 10(24557) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 9(24556) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 8(24555) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 7(24554) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 6(24553) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 4(24551) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 3(24550) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 2(24549) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 1(24548) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 35(24582) INFO: <core> [main.c:809]: sig_usr(): signal 15 received 0(24547) DEBUG: rtpengine [rtpengine.c:2014]: mod_destroy(): rtpengine_hash_table_destroy() success! 0(24547) DEBUG: db_text [dbtext.c:110]: destroy(): destroy ... 0(24547) DEBUG: tm [t_funcs.c:86]: tm_shutdown(): DEBUG: tm_shutdown : start 0(24547) DEBUG: tm [t_funcs.c:89]: tm_shutdown(): DEBUG: tm_shutdown : emptying hash table 0(24547) DEBUG: tm [h_table.c:127]: free_cell_helper(): freeing transaction 0x7fb3fb0c64e0 from h_table.c:449 0(24547) DEBUG: tm [t_funcs.c:91]: tm_shutdown(): DEBUG: tm_shutdown : removing semaphores 0(24547) DEBUG: tm [t_funcs.c:93]: tm_shutdown(): DEBUG: tm_shutdown : destroying tmcb lists 0(24547) DEBUG: tm [t_funcs.c:96]: tm_shutdown(): DEBUG: tm_shutdown : done 0(24547) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 0(24547) DEBUG: <core> [mem/shm.c:174]: shm_core_lock_destroy(): destroying the shared memory lock 0(24547) DEBUG: <core> [mem/shm.c:266]: shm_destroy_manager(): destroying memory manager: f_malloc 0(24547) DEBUG: <core> [mem/pkg.c:89]: pkg_destroy_manager(): destroying memory manager: f_malloc

3 13

e2e ACK. Kamailio. Cantact. Route.
by pavel＠eremina.net 05 Aug '16

05 Aug '16

Hello, I have this scheme: SIP Carrier (external IP 22.203) < > (local ip 1.21) mikrotik < > (local ip 1.21) Kamailio - (local ip 1.15) Asterisk. Carrier does not know what is Route header. that is why Carrier send ACK directly to 1.15 and fail. I change Contact at Kamailio to 1.21 then ACK is coming to Kamailio. But i think it's wrong way... How can i get ACK from CArrier to Kamalio and route it in right way? Thanks

1 0

e2e ACK
by Pavel Eremin 05 Aug '16

05 Aug '16

Hello, I have this scheme: SIP Carrier (external IP 22.203) < > (local ip 1.21) mikrotik < > (local ip 1.21) Kamailio - (local ip 1.15) Asterisk. Carrier does not know what is Route header. that is why Carrier send ACK directly to 1.15 and fail. I change Contact at Kamailio to 1.21 then ACK is coming to Kamailio. But i think it's wrong way... How can i get ACK from CArrier to Kamalio and route it in right way? Thanks

1 0

Re: [SR-Users] Textops and Multipart Body - adding ISUP segfaults Kamailio
by david 05 Aug '16

05 Aug '16

Hello all i'm having the same error on kam 4.4 when doing set_body_multipart(); msg_apply_changes(); i see in the logs 5(17797) DEBUG: textops [textops.c:1577]: set_multibody_helper(): delimiter<17>:[unique-boundary-1] 5(17797) DEBUG: textops [textops.c:1486]: generate_boundary(): adding final CRLF+CRLF 5(17797) DEBUG: textops [textops.c:1714]: set_multibody_helper(): content-type<44>:[multipart/mixed;boundary="unique-boundary-1"] 5(17797) DEBUG: textops [textops.c:1768]: set_multibody_helper(): set flag FL_BODY_MULTIPART 5(17797) INFO: <core> [msg_translator.c:1692]: get_boundary(): Content-Type hdr has no params <application/sdp> 5(17797) WARNING: <core> [msg_translator.c:1958]: build_req_buf_from_sip_req(): check_boundaries error 5(17797) DEBUG: <core> [msg_translator.c:422]: clen_builder(): content-length: 191 (191) the original INVITE is like .... Content-Type: application/sdp. Content-Disposition: session. Content-Length: 104. P-Asserted-Identity: "10707334" <sip:10707334@3.3.3.3>. . v=0. o=user1 53655765 23536 IN IP4 79.170.68.171. s=-. c=IN IP4 2.2.2.2. t=0 0. m=audio 6001 RTP/AVP 8. .... do you have any idea why these messages appear thanks a lot and regards david

2 1

Re: [SR-Users] Kamailio on multiple interface
by Daniel-Constantin Mierla 05 Aug '16

05 Aug '16

Hello, if you know the ip address associated with the network interfaces, you can use keyword dst_ip to check which of the ip addresses was used to receive the packet (or use $Ri instead of dst_ip). Cheers, Daniel On 05/08/16 08:41, Marino Mileti wrote: > > Hi guys, > > > > I've my Kamailio box that works great J > > > > Now I would like to enable wifi on the board (in AP mode) in order to > allow mobile devices to connect and receive and place calls. > > Is it possible? Is it possible to configure Kama like a "gateway" > between two network cards? > > > > I've find a guide regarding gateway between IPv4 and IPV6 but i can't > use "af" to discriminate message between eth0 or wlan0. Is there a > command to detect if a message is received from a specific interface card? > > > > Any help or any cfg example is very appreciate J > > > > /Marino Maria Mileti/// > > /marino.mileti(a)alice.it <mailto:marino.mileti@alice.it>/ > > / / > > /cid:006a01cb6b0e$67eecdae$_CDOSYS2.0//Reduce your energy consumption > and keep polar bears on ice!/ > > > > > > ------------------------------------------------------------------------ > Avast logo > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > > Questa e-mail è stata controllata per individuare virus con Avast > antivirus. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Kamailio on multiple interface
by Marino Mileti 05 Aug '16

05 Aug '16

Hi guys, I've my Kamailio box that works great J Now I would like to enable wifi on the board (in AP mode) in order to allow mobile devices to connect and receive and place calls. Is it possible? Is it possible to configure Kama like a "gateway" between two network cards? I've find a guide regarding gateway between IPv4 and IPV6 but i can't use "af" to discriminate message between eth0 or wlan0. Is there a command to detect if a message is received from a specific interface card? Any help or any cfg example is very appreciate J Marino Maria Mileti <mailto:marino.mileti@alice.it> marino.mileti(a)alice.it cid:006a01cb6b0e$67eecdae$_CDOSYS2.0Reduce your energy consumption and keep polar bears on ice! --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus

1 0

Kamailio RTP Engine
by Jack Stevens 05 Aug '16

05 Aug '16

Hi Guys, Looking for some help on configuring RTP Engine with Dispatcher on my Kamailio Box Please see this paste for the kamailio configuration = http://pastebin.com/yZzSEJmK When I run a call the dispatcher does it job perfectly but the rtpengine is not been used does anyone know why -- CONFIDENTIAL EMAIL FROM NETCALL TELECOM LIMITED This email, and any attachments, is intended only for the above addressee. It may contain private and/or confidential information. If you have received this email in error you are on notice of its status, please immediately notify the sender by return email then delete this message and any attachments. If you are not the addressee, except to notify the sender, you must not use, disclose, copy or distribute this email and/or its attachments. Netcall Telecom accepts no responsibility for any changes made to this message after it has been sent by the original author. Opinions or views expressed in this email may be those of the individual sender and not Netcall Telecom. Nothing in this email shall bind Netcall Telecom in any contract or obligation Netcall Telecom Ltd Registered in England 2831215. Registered Office : 3rd Floor, Hamilton House, 111 Marlowes, Hemel Hempstead, Herts, HP1 1BB

2 1

Kamailio 4.4 wont start on CentOS 7 using script
by Fabian Borot 04 Aug '16

04 Aug '16

Hello I installed/compiled version 4.4 on CentOS 7. When I start the server like this: "./kamctl start" it works but when I try to use the script: "/etc/init.d/kamailio" it fails [root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio start Starting kamailio (via systemctl): Job for kamailio.service failed because the control process exited with error code. See "systemctl status kamailio.service" and "journalctl -xe" for details. [FAILED] [root@ar-mia-proxy-01 sbin]# when running the "status" I see this: [root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio status â kamailio.service - LSB: Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Thu 2016-08-04 15:25:59 GMT; 14s ago Docs: man:systemd-sysv-generator(8) Process: 5556 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Starting LSB: Kamailio (OpenSER) - the Open Source SIP Server... Aug 04 15:25:59 ar-mia-proxy-01.dom.com kamailio[5556]: Starting kamailio: Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service: control process exited, code=exited status=1 Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Failed to start LSB: Kamailio (OpenSER) - the Open Source SIP Server. Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Unit kamailio.service entered failed state. Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service failed. [root@ar-mia-proxy-01 sbin]# I welcome all ideas, thank you in advance

3 4

Kamailio and RTPProxy in-front of freeswitch
by Achintha 04 Aug '16

04 Aug '16

hi all, i have configured kamailio and RTPProxy on one ubuntu server then freeswitch on another server. all servers installed on digital ocean. i was tried to build following setup, SIP_Call------> kamailio+RTPPROXY-------> freeswitch put following configurations on kamailio. modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722") modparam("rtpproxy", "rtpproxy_retr", 2) modparam("rtpproxy", "ice_candidate_priority_avp", "$avp(ice_priority)") mhomed=1 route[FROM_TRUNK] #force_send_socket("pu.bl.ic.ip "); rtpproxy_manage("","pu.bl.ic.ip "); $du="sip:ip.of.free.switch:5080"; route(RELAY); call was connected but rtp is not going through the kamailio server like folows, SIP FLOOR SIP_Call------> kamailio-------> freeswitch SIP_Call<------ kamailio<------- freeswitch RTP FLOOR SIP_Call ------> freeswitch SIP_Call <------ freeswitch please help me to configure kamailio and RTPProxy to manage RTP -- thanking you.. Achintha

1 0

Re: [SR-Users] Path & Loose Route
by Luke Milbourne 04 Aug '16

04 Aug '16

Hi Daniel, Thanks again for your reply again. I remembered about the debug setting and done it yesterday, not at my pc right now but I remember one of the log lines was saying "the topmost route header is me". Still trying to understand it, but will get a copy of the log lines for you, if you wouldn't mind taking a look. Thanks again, Luke On 4 Aug 2016 06:57, "Daniel-Constantin Mierla" <miconda(a)gmail.com> wrote: Hello, set debug=3 in kamailio.cfg and look at log messages in syslog. If you find it too verbose, use dispatcher module and set debug level only for core and rr modules to 3. Cheers, Daniel On 03/08/16 13:22, Luke Milbourne wrote: Hi Daniel, I've added some more logging and can see loose_route() is returning -1 - route calculation has been unsuccessful. Is there a way of finding out why this is the case? Kind regards, Luke On 2 August 2016 at 09:49, Luke Milbourne <luke.milbourne(a)gmail.com> wrote: > I added the below xlog lines into my script: > > xlog("L_NOTICE", "Before loose_route: $si -> $ru - $du\n"); > xlog("L_NOTICE", "Before record_route: $si -> $ru - $du\n"); > xlog("L_NOTICE", "After both: $si -> $ru - $du\n"); > > Which generated the below output in syslog: > > Aug 2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: <script>: Before > loose_route: 10.10.0.25 -> sip:201@192.168.1.114:5062 - <null> > Aug 2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: <script>: Before > record_route: 10.10.0.25 -> sip:201@192.168.1.114:5062 - <null> > Aug 2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: <script>: After > both: 10.10.0.25 -> sip:201@192.168.1.114:5062 - <null> > > Seems that the destination URI is never set, the Route header is below: > > Route: <sip:201@10.10.2.5:5072>;lr;received=sip:[PUBLIC_IP]:45126 > > The use_received modparam for path is also set to 1. > > Any idea's/suggestions are greatly appreciated :) > > Kind regards, > Luke > > On 2 August 2016 at 09:40, Luke Milbourne <luke.milbourne(a)gmail.com> > wrote: > >> Morning Gents, >> >> Firstly, thanks for taking the time to reply :) >> >> Kamailio is doing the NAT detection and simply acting as a passthrough to >> FreeSWITCH (which handles all SIP registrations etc). >> >> Will setup the log lines shortly and share the results. >> >> kamailio -V outputs; >> >> version: kamailio 4.3.4 (x86_64/linux) 83e842 >> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, >> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, >> DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, >> USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES >> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, >> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB >> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. >> id: 83e842 >> compiled on 18:22:39 Jan 26 2016 with gcc 4.9.2 >> >> Kind regards, >> Luke - Chicane Support >> >> On 2 August 2016 at 07:52, Daniel-Constantin Mierla <miconda(a)gmail.com> >> wrote: >> >>> Hello, >>> >>> yes, loose_route() should be used there. Can you add a log message and >>> print $ru and $du before and after loose_route() in config and then send >>> the result to this mailing list? >>> >>> Btw, what version of Kamailio are you using? >>> >>> Cheers, >>> Daniel >>> >>> On 01/08/16 14:46, Luke Milbourne wrote: >>> >>> Is it correct to use loose_route() along side the path module? >>> >>> On 1 August 2016 at 13:33, Luke Milbourne <luke.milbourne(a)gmail.com> >>> wrote: >>> >>>> Hi Daniel, >>>> >>>> Yep, I've got the below in my kamailio.cfg >>>> >>>> modparam("path", "use_received", 1) >>>> >>>> Kind regards, >>>> Luke >>>> >>>> On 1 August 2016 at 13:25, Daniel-Constantin Mierla <miconda(a)gmail.com> >>>> wrote: >>>> >>>>> Hello, >>>>> >>>>> On 01/08/16 14:14, Luke Milbourne wrote: >>>>> >>>>> Hi all, >>>>> >>>>> Currently trying to use Kamailio as a passthrough to some FreeSWITCH >>>>> boxes. >>>>> >>>>> When receiving an invite from FreeSWITCH which contains a Route header >>>>> including received information, example below; >>>>> >>>>> Route: <sip:201@10.10.2.5:5072>;lr;received=sip:[PUBLIC_IP]:45126 >>>>> >>>>> When using loose_route() Kamailio still send the invite to the rfc1918 >>>>> address instead of the received IP:PORT in the Route header. >>>>> >>>>> Am I misunderstanding how this should work? >>>>> >>>>> >>>>> if you use path module, have you enabled the option to use the >>>>> received parameter? >>>>> >>>>> >>>>> https://www.kamailio.org/docs/modules/stable/modules/path.html#idp38033932 >>>>> >>>>> Cheers, >>>>> Daniel >>>>> >>>>> -- >>>>> Daniel-Constantin Mierlahttp://www.asipto.com - http://www.kamailio.orghttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda >>>>> >>>>> >>>>> _______________________________________________ >>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>>>> sr-users(a)lists.sip-router.org >>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>>>> >>>>> >>>> >>>> >>>> -- >>>> Luke Milbourne >>>> >>>> Tel: 07857154817 >>>> Google Talk/Email: luke.milbourne(a)gmail.com >>>> >>> >>> >>> >>> -- >>> Luke Milbourne >>> >>> Tel: 07857154817 >>> Google Talk/Email: luke.milbourne(a)gmail.com >>> >>> >>> _______________________________________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >>> -- >>> Daniel-Constantin Mierlahttp://www.asipto.com - http://www.kamailio.orghttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda >>> >>> >>> _______________________________________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>> sr-users(a)lists.sip-router.org >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >> >> >> -- >> Luke Milbourne >> >> Tel: 07857154817 >> Google Talk/Email: luke.milbourne(a)gmail.com >> > > > > -- > Luke Milbourne > > Tel: 07857154817 > Google Talk/Email: luke.milbourne(a)gmail.com > -- Luke Milbourne Tel: 07857154817 Google Talk/Email: luke.milbourne(a)gmail.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierlahttp://www.asipto.com - http://www.kamailio.orghttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 1

Kamailio on Mac
by Carlos Ruiz Díaz 04 Aug '16

04 Aug '16

Hi all, I'm switching my development environment from Linux to Mac. Is there any tutorial on how to setup Kamailio on this OS? It may be an Unix flavor, but it's still quite different from Linux :). Thanks, -- Carlos http://caruizdiaz.com http://ngvoice.com +52 55 3048 3303

6 9

Kamailio + rtpengine + freeswitch
by Kotb, Amir 04 Aug '16

04 Aug '16

[03:50] <meamo> I have a small query, can anybody assist please? [03:51] <meamo> I am running kamailio + rtpengine on a google compute cloud instance [03:51] <meamo> have setup them to work with devices behind nat, and everything works [03:52] <meamo> no i have added freeswitch. but I don't know how to configure rtpengine to work with both [03:52] <meamo> when I use #!define with_nat and #!define with_freeswitch, I get no voice in the calls. When I remove, #!define with_freeswitch, everything works normally Best regards, Amir -- Amir KOTB, Msc., Bsc. Postgraduate Researcher Department of Electrical Engineering & Electronics, The University of Liverpool, Brownlow Hill, Liverpool L69 3GJ, UK Mobile: +44-(0) 7428844234 Email: A.Kotb(a)liverpool.ac.uk Skype: A.kotb1 Web: Http://uk.linkedin.com/in/AOKotb Please consider the environment before printing this email

2 1

Path & Loose Route
by Luke Milbourne 04 Aug '16

04 Aug '16

Hi all, Currently trying to use Kamailio as a passthrough to some FreeSWITCH boxes. When receiving an invite from FreeSWITCH which contains a Route header including received information, example below; Route: <sip:201@10.10.2.5:5072>;lr;received=sip:[PUBLIC_IP]:45126 When using loose_route() Kamailio still send the invite to the rfc1918 address instead of the received IP:PORT in the Route header. Am I misunderstanding how this should work? -- Luke Milbourne <luke.milbourne(a)gmail.com> Tel: 07857154817 Google Talk/Email: luke.milbourne(a)gmail.com

3 10

Help with dispatcher ping: Kamailo 4.1
by Andy Chen 03 Aug '16

03 Aug '16

Hi, I'm currently running Kamailio 4.1 and was wondering if there is a way to control ds_ping_interval on a dispatcher setid. Thanks. -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen(a)thinkingphones.com

1 0

Fail to register at trunk through UAC
by Yuriy Gorlichenko 03 Aug '16

03 Aug '16

Hi. All trunks works fine ony one not works Kamailio sends REGISTER with proxy auth provider answers with 407 Kamailio not send any REGISTER Just answers in log uac_reg_tm_callback(): authentication failed for <trunkname> At attachement kamialio debug 3 log and sip log

2 6

SSL Certificate (Second Try)
by JCOT 02 Aug '16

02 Aug '16

I'm not sure where to send this information so I hope it's okay to share it with the mailing list, as well as the whois registrants: I went to register for a new account at https://serweb.iptel.org/user/reg. Firefox told me that the SSL certificate was bad. Specifically: -- serweb.iptel.org uses an invalid security certificate. The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure. The certificate expired on 10/22/2014 12:39 AM. The current time is 08/01/2016 09:55 PM. -- Thank you.

2 1

SSL Certificate
by JCOT 02 Aug '16

02 Aug '16

I'm not sure where to send this information so I hope it's okay to share it here: I went to register for a new account at https://serweb.iptel.org/user/reg. Firefox told me that the SSL certificate was bad. Specifically:

1 0

A: Upgrading kamailio.org os
by Daniel-Constantin Mierla 02 Aug '16

02 Aug '16

Hello, a short note to announce that the os on kamailio.org server will be upgraded in the near future, likely next week, exact date still to be decided. Hopefully there will be only very short downtime intervals. Main affected services: website (including the wiki) and mailing lists. I will send a notification once the procedure starts, but I wanted to allow enough time for this information to propagate properly within the community. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

12 24

Saving and extracting contact header
by Nahum Nir 01 Aug '16

01 Aug '16

Hello, I am quite a newbe in Kamailio scripts and further to my effort to implement push notification, I am adding to the contact header device ID. I have two problems: 1. When the register of the callee expires Kamailio frees the record so the information on the calle is not available. 2. Even when the callee is registered I do not how to access the contact field. Tried reg_fetch_contacts(...,"callee") and there is a lot of info but not the contact header. Thanks and regards, Nir

2 7

CDP -Could not open module error
by Andrew Okri 01 Aug '16

01 Aug '16

Hi All, I have just installed KamailioIMS 4.4.2 on a Ubuntu 16.04 vm and configured it according to the kamailio tutorial. When l attempt to start the icscf or scscf kamailio, it fails to start due to its inability to open the CDP module referring to the log_db_config function in particular.I have looked at the archive to see if anyone else have encountered this problem, but could not find anything. The log_db_config function takes a config object as a parameter, hence l have inspected the CDiameterPeer config file carefully and it seems both xml and diameter compliant. I am at loss where else to look. Please would anyone be kind enough to assist with getting a scscf and icscf started please. Regards Andrew

2 1

Kamailio static comilation
by Pratik V Patel 01 Aug '16

01 Aug '16

Hello all, I want to compile kamailio open source statically. I want to remove dependency for dynamic shared libraries. can anyone help me to get out of it? I have tried by chang in Makefiles but it does not work. What the meaning of "static_modules" during compilation. It is still generating dynamic shared libraries. Please do needful. -- Thanks And Regards, Pratik V. Patel Ext: 558

2 1

cnxcc-web error
by Infinicalls Infinicalls 01 Aug '16

01 Aug '16

Hi, I am really struggling to get the cnxcc-web installed. the /var/log/apache2/error.log says [Mon Aug 01 02:52:00.177725 2016] [:error] [pid 17534] [client 115.241.40.163:1851] PHP Deprecated: ServiceManagerAwareInterface is deprecated and will be removed in version 3.0, along with the ServiceManagerAwareInitializer. Please update your class ZfcUser\\Authentication\\Adapter\\Db to remove the implementation, and start injecting your dependencies via factory instead. in /usr/local/cnxcc/cnxcc-web/vendor/zendframework/zend-mvc/src/Service/ServiceManagerConfig.php on line 129, referer: http://xxxxxxxx.com/user/login I am getting the login screen and it freezes there. Can somebody guide me how to go about? Or is there a simple php (without Zend framework) interface available for cnxcc? thanks Ganesh Kumar

2 1

manage rtp with or without RTP Proxy
by Achintha 01 Aug '16

01 Aug '16

hi I have configured kamailio and freeswitch on two Ubuntu servers as follows. Sip_TRUNK------> kamailio-------> freeswitch i wan to manage rtp through the kamailio server, first i want to know, 1. can i do it without RTP Proxy ? anyway i tried it with RTP Proxy as follows, I installed rtpproxy on kamailio server and start it using “rtpproxy –F -l pu.bl.ic.ip -s udp:localhost :7722 -u root” it was working Then I put modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722") modparam("rtpproxy", "rtpproxy_retr", 2) modparam("rtpproxy", "ice_candidate_priority_avp", "$avp(ice_priority)") mhomed=0 route[FROM_TRUNK] force_send_socket("pu.bl.ic.ip "); rtpproxy_manage("","pu.bl.ic.ip "); $du="sip:ip.of.free.switch:5080"; route(RELAY); then call is received to user and disconnected on freeswitch console get some errors [ERR] switch_core_media.c:7179 AUDIO RTP REPORTS ERROR: [Remote Address Error!] [ERR] mod_sofia.c:2290 CODEC NEGOTIATION ERROR. SDP: v=0 o=- 3679035755 3679035755 IN IP4 pu.bl.ic.ippu.bl.ic.ip s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 4167841678 RTP/AVP 123 8 0 101 c=IN IP4 pu.bl.ic.ippu.bl.ic.ip b=TIAS:64000 a=rtpmap:123 opus/48000/2 a=fmtp:123 maxplaybackrate=16000;sprop-maxcapturerate=16000;maxaveragebitrate=16000;useinbandfec=1 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtcp:4167941679 a=nortpproxy:yes a=nortpproxy:yes please advice me thank you

2 1

function to check if string is an ipv4 address
by Juha Heinanen 29 Jul '16

29 Jul '16

I did not find in textops or utils modules a function to check if a string is an ipv4 address. Does it exist somewhere else? -- Juha

2 2

RTPEngine Kamailio crashed because someone tried to do something
by Andrew Tan 29 Jul '16

29 Jul '16

I'm getting below every 2-3 weeks someone tried to connect through the CLi of RTPengine and crashed Rtpengine. Anyone knows what to make out of this ? Thanks Andrew 82440 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: INFO: <script>: HTTP Request Received 182441 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 16) 182442 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 404 Not Found#015#012Sia: SIP/2.0/TCP 89.163.135.117:63413#015#012Server: kamailio (4.3.3 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012> 182443 Jul 28 16:24:21 sipr rtpengine[1224]: New cli connection from 89.163.135.117:63587 182444 Jul 28 16:24:21 sipr rtpengine[1224]: Got CLI command: 182445 Jul 28 16:24:21 sipr rtpengine[1224]: New cli connection from 89.163.135.117:63838 182446 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13028]: WARNING: <script>: HTTP request received on 5080 182447 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182448 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182449 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182450 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182451 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182452 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182453 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13028]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182454 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13028]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182455 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13020]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182456 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182457 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13021]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182458 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13021]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading

2 1

Kamailio LB: how to get Asterisk to do the RTP
by Tickling Contest 28 Jul '16

28 Jul '16

With the help of members from this mailing list (many thanks!), I finally got Asterisk fronted by Kamailio for LB and REGISTERs and I am able to make a call using the setup that looks like this: [Kamailio 4.4.2]<->[Asterisk 13.7.2] Kamailio manages REGISTERs, but also forwarding them to Asterisk. I am able to make a call, but I get only one way audio or no audio depending on which client made the call (SipDroid->Zoiper I hear one way audio on Zoiper, but no audio if the call is made the other way). I noticed that Kamailio forced direct media between the endpoints in this situation, but my application really needs Asterisk to handle it. How do I do this? Should I start by forwarding INVITEs to Asterisk? How do I do that? Any help is appreciated. Thanks!

5 5

undefined symbol: EVP_sha1 when using outbound module
by Francisco Burgos 28 Jul '16

28 Jul '16

Hi, I am trying to use kamailio as an edge proxy to forward requests and media to an sbc. when compiling the cfg file included on the examples. i get: undefined symbol: EVP_sha1 I believe this problem is being caused by the outbound module and after some research i managed to read that it is caused by the linking between the gcc libcrypto. I would like some help since this project requires urgency. Thanks in advance.

2 5

TM: t_relay([host, port]) DNS Queries
by Louis-Olivier Roof 27 Jul '16

27 Jul '16

Dear Kamailio users, Ref: http://kamailio.org/docs/modules/4.2.x/modules/tm.html#tm.f.t_relay Using t_relay([host, port]) to relay messages to a specific host does not seem to generate DNS queries to the said host after Kamailio has initially processed the configuration file. It resolves the host once at startup then continues using the same IP after. Is that expected behavior? Anyone has had this issue before and found a way to work around it? Note that for this specific application, messages need to be relayed to a specified host (different from current R-URI) and this host needs to be resolved by DNS during normal operation, not only at startup. Thanks! Louis-Olivier

2 4

Checking for 200ok Response to a REGISTER request kamailio-Asterisk
by Jonathan Hunter 27 Jul '16

27 Jul '16

Hi Guys, So currently on our network we have a kamailio server which users register against, we then replicate the register messages to 2 Asterisk boxes sat behind it so that all entities are aware of the registration state of the users. REGISTER--->KAMAILIO---->ASTERISK A ---->ASTERISK B With a REGISTER---200OK exchange between Kamailio and Asterisk. We have an issue where at some points the Asterisk servers when under load dont respond with a 200 ok(something being investigated) to the register messages sent to kamailio, so I am just working on some logic for the register message to be resent using the t_replicate and t_set_fr functions. This works well should both Asterisk servers not respond, however, as I am using replicate and it is parallel forking, if say Asterisk A answers first and is available with a 200ok then that in turn cancels the register message branch being sent to Asterisk B(which I know is fine), however there could be a scenario where Asterisk B doesnt respond, and we wont know about it to try and resend the Register message, as the branch is cancelled. Hope that makes sense? I am looking at checking that both the Asterisk servers have responded and sent a 200ok, which I can grab in an onreply route but Im just wondering if someone has done something similar or has any suggestions as it is tricky to achieve currently. I have also thought about stateless working but I really need kamailio to keep retransmitting the register until it gets a response. Many thanks Jon

2 4

Segfault in dialog.so with 4.4.2 stable
by Dirk Teurlings - Signet B.V. 26 Jul '16

26 Jul '16

Hi, Running Kamailio on Debian from the Kamailio repository with 4.4.2 stable (unpatched). Getting some random segfaults with it now, here's the relevant backtrace from the generated core. Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.'. Program terminated with signal 11, Segmentation fault. #0 run_dlg_callbacks (type=type@entry=64, dlg=dlg@entry=0x7fceb400e2f0, req=req@entry=0x7fced4f093c8, rpl=rpl@entry=0x0, dir=<optimized out>, dlg_data=dlg_data@entry=0x0) at dlg_cb.c:253 253 if ( (cb->types)&type ) { (gdb) bt #0 run_dlg_callbacks (type=type@entry=64, dlg=dlg@entry=0x7fceb400e2f0, req=req@entry=0x7fced4f093c8, rpl=rpl@entry=0x0, dir=<optimized out>, dlg_data=dlg_data@entry=0x0) at dlg_cb.c:253 #1 0x00007fcead3648f9 in dlg_terminated (dir=<optimized out>, dlg=0x7fceb400e2f0, req=0x7fced4f093c8) at dlg_handlers.c:368 #2 dlg_onroute (req=0x7fced4f093c8, route_params=<optimized out>, param=<optimized out>) at dlg_handlers.c:1354 #3 0x00007fceb10ab0e2 in run_rr_callbacks (req=req@entry=0x7fced4f093c8, rr_param=rr_param@entry=0x7fceb12b77a0) at rr_cb.c:96 #4 0x00007fceb10952c5 in after_loose (_m=0x7fced4f093c8, preloaded=0) at loose.c:919 #5 0x000000000042b618 in do_action (h=h@entry=0x7ffeb0b3ed80, a=a@entry=0x7fced4cb4338, msg=msg@entry=0x7fced4f093c8) at action.c:1060 #6 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b3ed80, a=0x7fced4cb4338, msg=0x7fced4f093c8) at action.c:1549 #7 0x0000000000437544 in run_actions_safe (h=h@entry=0x7ffeb0b402b0, a=<optimized out>, msg=<optimized out>) at action.c:1614 #8 0x000000000053b2e8 in rval_get_int (h=0x7ffeb0b402b0, msg=<optimized out>, i=0x7ffeb0b3f1e0, rv=rv@entry=0x7fced4cb4d58, cache=cache@entry=0x0) at rvalue.c:912 #9 0x000000000054261c in rval_expr_eval_int (h=h@entry=0x7ffeb0b402b0, msg=msg@entry=0x7fced4f093c8, res=res@entry=0x7ffeb0b3f1e0, rve=rve@entry=0x7fced4cb4d50) at rvalue.c:1910 #10 0x000000000042bc91 in do_action (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4cb8f88, msg=msg@entry=0x7fced4f093c8) at action.c:1030 #11 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b402b0, a=0x7fced4cb8f88, msg=msg@entry=0x7fced4f093c8) at action.c:1549 #12 0x000000000042bcf2 in do_action (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4cb91e8, msg=msg@entry=0x7fced4f093c8) at action.c:1049 #13 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b402b0, a=0x7fced4cb3f48, msg=msg@entry=0x7fced4f093c8) at action.c:1549 #14 0x000000000042bde0 in do_action (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4ac3d70, msg=msg@entry=0x7fced4f093c8) at action.c:678 #15 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4ac1698, msg=msg@entry=0x7fced4f093c8) at action.c:1549 #16 0x00000000004375d0 in run_top_route (a=0x7fced4ac1698, msg=msg@entry=0x7fced4f093c8, c=c@entry=0x0) at action.c:1635 #17 0x0000000000504386 in receive_msg (buf=<optimized out>, len=<optimized out>, rcv_info=<optimized out>) at receive.c:240 #18 0x00000000005f5bd4 in udp_rcv_loop () at udp_server.c:495 #19 0x00000000004b2625 in main_loop () at main.c:1600 #20 0x0000000000427e2b in main (argc=<optimized out>, argv=<optimized out>) at main.c:2616 And from syslog the relevant messages before this dump: Jul 15 08:55:03 server /usr/sbin/kamailio[16470]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param 'd4c.26d1' [3149:7522] Jul 15 08:56:01 server /usr/sbin/kamailio[16481]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param 'fc.99f1' [207:8089] Jul 15 08:56:27 server /usr/sbin/kamailio[16470]: CRITICAL: dialog [dlg_timer.c:200]: update_dlg_timer(): Trying to update a bogus dlg tl=0x7fceb3f7d920 tl->next=(nil) tl->prev=(nil) Jul 15 08:56:27 server /usr/sbin/kamailio[16470]: ERROR: dialog [dlg_handlers.c:1377]: dlg_onroute(): failed to update dialog lifetime Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Duplicate entry '9584-3854-435' for key 'hash_index' (1062) Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query [INSERT INTO `dialog_extra` (`h_i] Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: auth [api.c:119]: auth_check_hdr_md5(): auth:pre_auth: Credentials are not filled properly Jul 15 08:57:01 server /usr/sbin/kamailio[16483]: ERROR: auth [api.c:119]: auth_check_hdr_md5(): auth:pre_auth: Credentials are not filled properly Jul 15 08:57:54 server /usr/sbin/kamailio[16506]: NOTICE: dialog [dlg_hash.c:245]: dlg_clean_run(): dialog in delete state is too old (0x7fceb3f64470 ref 4) Jul 15 08:57:54 server /usr/sbin/kamailio[16473]: WARNING: dialog [dlg_handlers.c:1348]: dlg_onroute(): inconsitent dlg timer data on dlg 0x7fceb3f64470 [1182:5803] with clid '09ad128753e2535d24bde58e3d7eda04@192.168.10.232:5060' and tags 'as1b497b34' '5788890C-EC6F55F-3E86ED0C' Jul 15 08:57:54 server /usr/sbin/kamailio[16469]: ERROR: dialog [dlg_handlers.c:334]: dlg_terminated_confirmed(): failed to get dialog from params! Jul 15 08:58:49 server /usr/sbin/kamailio[16467]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param '6d2.2581' [726:6226] Jul 15 08:59:24 server /usr/sbin/kamailio[16506]: NOTICE: dialog [dlg_hash.c:245]: dlg_clean_run(): dialog in delete state is too old (0x7fceb400e2f0 ref 4) Jul 15 08:59:25 server /usr/sbin/kamailio[16464]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param '3e4.b5c1' [1251:7259] Jul 15 08:59:25 server /usr/sbin/kamailio[16465]: WARNING: dialog [dlg_handlers.c:1348]: dlg_onroute(): inconsitent dlg timer data on dlg 0x7fceb400e2f0 [1251:7259] with clid '87791a#015#012Call-ID: 25750e286a5654361ef9405d72edbc' and tags '' 'as148f41b1' Jul 15 08:59:25 server kernel: [203670.830521] kamailio[16465] general protection ip:7fcead34b3a5 sp:7ffeb0b3e220 error:0 in dialog.so[7fcead330000+88000] Jul 15 08:59:26 server /usr/sbin/kamailio[16511]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 33 Jul 15 08:59:26 server /usr/sbin/kamailio[16458]: ALERT: <core> [main.c:739]: handle_sigs(): child process 16465 exited by a signal 11 Jul 15 08:59:26 server /usr/sbin/kamailio[16458]: ALERT: <core> [main.c:742]: handle_sigs(): core was generated Jul 15 08:59:26 server /usr/sbin/kamailio[16458]: INFO: <core> [main.c:754]: handle_sigs(): terminating due to SIGCHLD Any insight would be appreciated! Cheers, Dirk

2 12

CANCEL message within transaction not being relayed
by Ali Soltani 26 Jul '16

26 Jul '16

Hi, We tested the following on Kamailio 3.x and 4.x and observed the same behavior. INVITE and CANCEL are sent to Kamailo from the same source within the same transaction. (branch value in the first via header are the same in both INVITE and CANCEL message. Also FROM and TO header are same as well). However, Kamailio does not relay CANCEL message. UAC keep sending CANCEL till timeout. Apparently, t_check_trans() returns false. Can anyone help me on this issue on why Kamailio does not relay CANCEL message? Thanks, AS INVITE received by Kamailio INVITE sip:1111111@10.10.10.10:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 20.20.20.20:5060;branch=z9hG4bKkjhg4n100gagvkoup741.1 Max-Forwards: 69 From: <sip:2222222@20.20.20.20>;tag=SDl9eu701-1c1026774897 To: <sip:1111111@10.10.10.10;user=phone> Call-ID: SDl9eu701-36d75c874d3f463f6c83c5c94cc98b77-8q7ug02 CSeq: 1 INVITE Contact: <sip:2222222@20.20.20.20:5060;transport=udp> Supported: em,timer,replaces,path,resource-priority,sdp-anat Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: CS-CustomerName/v.6.60A.274 Content-Type: application/sdp Content-Length: 237 P-Asserted-Identity: tel:2222222 P-Asserted-Identity: sip:2222222@192.168.0.1 after 70 msec CANCEL received by Kamailio in the same transaction CANCEL sip:1111111@10.10.10.10:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 20.20.20.20:5060;branch=z9hG4bKkjhg4n100gagvkoup741.1 CSeq: 1 CANCEL Max-Forwards: 69 From: <sip:2222222@20.20.20.20>;tag=SDl9eu701-1c1026774897 To: <sip:1111111@10.10.10.10.;user=phone> Call-ID: SDl9eu701-36d75c874d3f463f6c83c5c94cc98b77-8q7ug02 Content-Length: 0 Reason: Q.850 ;cause=16

2 1

music on hold configuration
by Gaurav Bmotra 25 Jul '16

25 Jul '16

hi i m a new user of kamailio i have sertup kamailio SIP to SIP call going well but now i m tring to impliment Music On Hold i m this http://www.kamailio.org/docs/modules/devel/modules/mohqueue.html#table.parms but unable to impliment plz help me Hare i attache my kamailio config file -- *Regards:* Gaurav Bmotra Smith Infotech E-46, phase 8 , Indus Area S.A.S Nagar Mohali 160071

3 18

Kamailio+tls not working with Ubuntu 16.04
by Yuriy Gorlichenko 25 Jul '16

25 Jul '16

Just asking about any progress of this staff THere is a bug descried at the ubuntu bug tracker https://bugs.launchpad.net/ubuntu/+source/kamailio/+bug/1591992 There is bug that i wrote at the kamailio bug tracker https://github.com/kamailio/kamailio/issues/714 Closed it because It is not trouble of kamailio itself. I suppose something wrong at the ubuntu enviroment Any ideas or may be someone resolves it?

2 3

Re: [SR-Users] Tsilo Tiimers
by Federico Cabiddu 25 Jul '16

25 Jul '16

Hi, looks like in your script, in the SENDPUSH route, you set the luaret var to 0 then you check if it's value is != 1, in which case you reply 501, Unknown Destination. Since you never change the var value you are always hitting this case. Regards, Federico On 24 Jul 2016 14:25, "Nahum Nir" <hello.shalom.hi(a)gmail.com> wrote: > Hello Fredrico, > > Please see the attached cfg. I tried to add the fragments you published > and to add a suspension at SENDPUSH but I am getting Desitnation Unknow. > > Thank you so much, > Nir > > On Thu, Jul 21, 2016 at 10:03 PM, Federico Cabiddu < > federico.cabiddu(a)gmail.com> wrote: > >> Hi Nir, >> all you should do upon receiving B's REGISTER, after saving the contact >> (by calling save function) is either resume the transaction, perform a >> lookup and relay or call ts_append (if you already relayed the INVITE). If >> you get "unavailable" (I guess that this means that you are receiving a >> 404) probably the user is not being found in the location. Check if you are >> doing these steps in your config and if it doesn't work try to send the >> relevant part of the config and the kamailio's logs. I'm currently away and >> almost without network but I'll try to have a look as soon as possible. >> >> Regards, >> >> Federico >> >> On 21 Jul 2016 16:09, "Nahum Nir" <hello.shalom.hi(a)gmail.com> wrote: >> >> Thanks, >> >> I was able to suspend the transaction and wait for the register but the >> client that sends the INVITE get unavailable right after the other side >> joins. >> Here is my debug flow: >> Client A sends the INVITES. >> >> Use case 1: Client B register one time. Then I turn off the WiFi in >> client B so it will not recieve the push notification. Client A sends the >> INVITE, server sends the PUSH and Client A is waiting for 5 seconds. >> >> Use case 3: Same as before but now client B get the push. This time >> client A that sends the INVITE gets from the server unavailable as soon as >> client B register. >> >> I did as you suggested and suspend the trunsaction before sending the >> push. Probably a second suspend is needed when client B sends the REGISTER? >> >> Thanks and regards, >> Nir >> >> On Wed, Jul 20, 2016 at 4:06 PM, Federico Cabiddu < >> federico.cabiddu(a)gmail.com> wrote: >> >>> Hi, >>> to set the timeout for a specific transaction you can use tm module >>> function t_set_fr ( >>> http://www.kamailio.org/docs/modules/devel/modules/tm.html#tm.f.t_set_fr >>> ). >>> For example you could call it before suspending the transaction setting >>> a short timeout and then call it again in the reply route when receiving >>> the first provisional response from the client. >>> >>> Regards, >>> >>> Federico >>> On 20 Jul 2016 2:50 pm, "Nahum Nir" <hello.shalom.hi(a)gmail.com> wrote: >>> >>>> Hello, >>>> >>>> How can I chage the timer waiting for the client to send the register. >>>> i.e. how much time to wait for the push? >>>> >>>> Thanks, >>>> Nir >>>> >>>> >>>> _______________________________________________ >>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>>> sr-users(a)lists.sip-router.org >>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>>> >>>> >>> _______________________________________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>> sr-users(a)lists.sip-router.org >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >> >> >

1 0

How to forward REGISTERs to Asterisk in kamailio with dispatcher module with several Asterisk PBXs?
by Tickling Contest 24 Jul '16

24 Jul '16

Hello, When using Kamailio with the dispatcher module for Asterisk load balancing, I am offloading REGISTERs to Kamailio (works fine), but would like to forward the REGISTERs to Asterisk so that outgoing calls from Asterisk will be possible. I know this is not strictly necessary (e.g., just use Kamailio to forward everything), but I have a lot of application logic behind my Asterisk boxes (using ARI) and so I don't want that to break. Thereby, I do need this information in Asterisk as soon as possible from Kamailio. Let's say I have three boxes Asterisk_1, Asterisk_2 and Asterisk_3 in the dispatcher module like so: 1 sip:192.168.1.201:5060;transport=tcp 1 sip:192.168.1.202:5060;transport=tcp 1 sip:192.168.1.203:5060;transport=tcp My system has endpoints as numerical extensions, from 101 to 110. When a new endpoint registers with kamailio (and authenticates), I would like to send the REGISTER to Asterisk. But I have the following questions: (a) Which Asterisk? I could send it to a round-robinned Asterisk (say, Asterisk_2), but that Asterisk may not be the one responsible for handling calls outbound for the endpoint that just registered. Even if I use "hash over auth username" instead of round-robin (In http://www.kamailio.org/docs/modules/4.0.x/modules/dispatcher.html#idp16940…, choose 5 for "alg", for example) that wont solve this problem as an outbound request may come from another Asterisk box which won't have the requisite registration information. Should I forward REGISTERs to all Asterisk boxes? Maybe I won't have to deal with this issue as I use realtime and so the REGISTER information, sent to one Asterisk box, is available to all Asterisk boxes after the write to the realtime DB. Is my understanding correct? (b) How do I do this in kamailio.cfg? With some examples on the Internet for WITH_ASTERISK directive, I see that you do route[REGFWD] { if(!is_method("REGISTER")) { return; } $var(rip) = $sel(cfg_get.asterisk.bindip); $uac_req(method)="REGISTER"; $uac_req(ruri)="sip:" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport) + ";transport=tcp"; $uac_req(furi)="sip:" + $au + "@" + $var(rip); $uac_req(turi)="sip:" + $au + "@" + $var(rip); $uac_req(hdrs)="Contact: <sip:" + $au + "@" + $sel(cfg_get.kamailio.bindip) + ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n"; if($sel(contact.expires) != $null) $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n"; else $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n"; uac_req_send(); } What is the equivalent for when you are using the dispatcher module and the kamailio.bindip and asterisk.bindip etc. are not set in the configuration, but instead should be procured from elsewhere? Any help is appreciated.

3 9

SIP Outbound / t_next_contacts()
by Colin Morelli 24 Jul '16

24 Jul '16

Hey all, I've got two layers of Kamailio proxies running. One set of edge proxies that are parking outbound connections and doing load balancing to a set of registrar/proxies. This is working well with one exception: I can't seem to get t_load_contacts/t_next_contacts working correctly for handling multiple outbound connections. It *appears* to work (though I haven't extensively tested) whenever there's more than one registration binding for an AOR. However, when there's only one, I get: 8(27) DEBUG: tm [t_serial.c:191]: t_load_contacts(): nr_branches is 0 8(27) DEBUG: tm [t_serial.c:194]: t_load_contacts(): nothing to do - only one contact! 8(27) DEBUG: tm [t_serial.c:455]: t_next_contacts(): no contacts in contacts_avp - we are done! 8(27) ERROR: <script>: t_next_contacts() failed I tried omitting the call to t_next_contacts(), thinking it should possibly only be used in failure_route. But when I do that (while leaving t_load_contacts), I get: 5(24) ERROR: tm [t_fwd.c:1730]: t_forward_nonack(): ERROR: t_forward_nonack: no branches for forwarding 5(24) WARNING: <core> [receive.c:258]: receive_msg(): error while trying script The relevant part of the config is: if (!lookup("location")) { $var(rc) = $rc; switch ($var(rc)) { case -1: xlog("L_INFO", "$ci|log|lookup of contacts for $ru returned no results\r\n"); send_reply("404", "Not Found"); exit; case -3: xlog("L_INFO", "$ci|log|lookup of contacts for $ru failed with code $var(rc)\r\n"); send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } if (!t_load_contacts() || !t_next_contacts()) { xlog("L_ERR", "t_load_contacts() failed\n"); sl_reply_error(); t_release(); exit; } Am I missing something else here? Note: it works fine if I remove t_load_contacts/t_next_contacts, but then I don't get proper handling of multiple sip.instance bindings/differing q values. Best, Colin

2 4

business case
by anfecora 24 Jul '16

24 Jul '16

I apologize since this is a technical mail list and this question may not belong here but i need to fill a business requirement and need more information of big companies using kamailio, i am searching over the internet but if anyone can provide me with names of real carriers using kamailio will be very useful. Thanks again for any help in this case.

2 1

Dispatcher list not loading from dispatcher.list, but loading from DB
by Tickling Contest 23 Jul '16

23 Jul '16

Hello, I have a Kamailio 4.0.4 configured with the cfg file shown in https://gist.github.com/ticklingcontest/f96aa4d08b08dc4643056d73da24f0a5 The modparam for dispatcher sets the dispatcher file to be in /var/run/kamailio/dispatcher.list. However, I recently discovered that $ kamctl dispatcher show picks up the information from the kamailio DB instead of the dispatcher.list. What's going on? Any insight is appreciated. Thanks!

1 0

kamailio starts looping invites(some) back to itself.
by Aqs Younas 22 Jul '16

22 Jul '16

Hi, I am using http_async_client and dispatcher modules of Kamailio. Here is scenario! http_async_client makes calls to an API to get groupid upon which dispatcher sends calls. I am using SIPp to generate calls with 100 cps. I see some calls being failed with an error cause, 483 Too Many Hops. Taking the trace shows Kamailio routing some calls to itself. I think this is not a configuration issue since all calls are same(follow same logic) and some calls get failed. Any pointer is much appreciated. Best Regards.

1 0

sip options not relaying
by gerry kernan 22 Jul '16

22 Jul '16

Hi I have a kamailio proxy in front of asterisk ver 13 servers. I'm using path support to route to the relevant asterisk server depending on the domain in the sip header. The incoming registers & invites from sip endpoints get routed to the correct asterisk server , but when asterisk is sending sip options to the end points my kamailio config is not routing the option on to the endpoint . Kamailio debug shows error below ERROR: <script>: 192.168.200.131 OPTIONS sip:1333@192.168.200.112:5062 -- domain "192.168.200.112" is not found in domain table 192.168.200.131 Am I correct in thinking that this SIP option should be getting routed via my on-reply route. the sip option looks like it is failing here at the start of my config if (src_ip != BACKEND_NET4) { xlog("L_NOTICE", "FROM CLIENT IP: $si $rm $ru $td \n"); # SIP request packet client->backend if( !loose_route() ) { if (!lookup_domain("$td", "dattr_")) { xlog("L_NOTOCE" , "Domain lookup, $rm "); xlog("L_ERR", "$si $rm $ru -- domain \"$td\" is not " + "found in domain table $si\n"); drop(); } Sample of SIP option captured on the kamailio server OPTIONS sip:1333@192.168.200.112:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.200.131:5060;branch=z9hG4bK4f910445 Max-Forwards: 70 Route: <sip:192.168.200.148;lr;received=sip:87.198.223.83:16070> From: "Unknown" <sip:Unknown@192.168.200.131>;tag=as54cfb9df To: <sip:1333@192.168.200.112:5062> Contact: <sip:Unknown@192.168.200.131:5060> Call-ID: 257dea110f5255275aa38d9c45e0e235@192.168.200.131:5060 CSeq: 102 OPTIONS User-Agent: FPBX-2.11.0(13.10.0) Date: Fri, 22 Jul 2016 15:31:13 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer, path Content-Length: 0 OPTIONS sip:1333@192.168.200.112:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.200.131:5060;branch=z9hG4bK20611e3b Max-Forwards: 70 Route: <sip:192.168.200.148;lr;received=sip:87.198.223.83:16070> From: "Unknown" <sip:Unknown@192.168.200.131>;tag=as1b6a0faf To: <sip:1333@192.168.200.112:5062> Contact: <sip:Unknown@192.168.200.131:5060> Call-ID: 7f8ed5ea7a147f2b61269df862af7fae@192.168.200.131:5060 CSeq: 102 OPTIONS User-Agent: FPBX-2.11.0(13.10.0) Date: Fri, 22 Jul 2016 15:31:27 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer, path Content-Length: 0 Gerry Kernan Infinity IT | 17 The Mall | Beacon Court | Sandyford | Dublin D18 E3C8 | Ireland Tel: +353 - (0)1 - 293 0090 | E-Mail: <mailto:gerry.kernan@infinityit.ie> gerry.kernan(a)infinityit.ie Managed IT Services Infinity IT - <http://www.infinityit.ie/> www.infinityit.ie IP Telephony Asterisk Consulting - <http://www.asteriskconsulting.com> www.asteriskconsulting.com Contact Centre Total Interact - <http://www.totalinteract.com> www.totalinteract.com

1 1

Kamailio + Asterisk MWI Issues
by TEG AMJG 21 Jul '16

21 Jul '16

Dear list I am quite new to Kamailio and i know that probably this thread has been answered quite few times. But i have few questions I was able to configure Kamailio + Asterisk MWI with Kamailio handling the registration of users. The problem is that i am quite sure that is not the right way. What i did was just putting "subscribemwi=no" on every user declared on Asterisk and he will send NOTIFY's when a voicemail has been received for a particular user to Kamailio and Kamailio will just forward them to the endpoints (because he knows the location of the users). I know about the modules presence presence_xml and presence_mwi of Kamailio which will handle the subscription of users and send NOTIFY's but it is useless since I am not verifying any NOTIFY that comes from Asterisk, just forwarding. Now, some others solution are just a bunch of scripts that, for me, it doesnt make much sense since is the same idea like how i did it just more hacky and unnecesary, i guess?. This solution can be found here: http://saevolgo.blogspot.com/2012/07/asterisk-behind-kamailio-voicemail-mwi… There is another solution that i found in few threads here which i dont understand really well, is to send PUBLISH messages from Asterisk to Kamailio so Kamailio sends NOTIFY's with the event and content about the amount of voice messages in a particular mailbox. Some say that you need to create the message PUBLISH and send it with sipsak or another solution in Asterisk. For what i see in SIP documentation, the last solution seems a bit less of a hack lets say, more resilient. With all said, i have a few questions Is it the solution I made really a bad idea?. I havent take a lot of time understanding SUBSCRIBE/NOTIFY messages, just the basics, i dont know if there are some security issues i should think about in this particular flow. Should i check the status of the authorization of the subscription in Kamailio before forwarding the mesage (if there is a way, how)? or it really doesnt make sense at all? because after all, my endpoints receives the NOTIFY and "you have a new voicemail" message appears. Now, about the last solution, is there any guide of someone that has done that in a clean way?, may someone guide me how to construct the PUBLISH message and when should i send it?, should i create a cron or something?, this PUBLISH message needs to be send for every user?. may someone guide me (if this is considered a cleaner way of doing it) how to make this? Many of the answers in other threads about this are not enough to understand the idea as a whole, at least for me. Thank you very much in advance Alejandro -- - Saludos a todos

1 0

Kamailio stops accepting calls for few seconds after 80 CPS.
by Aqs Younas 21 Jul '16

21 Jul '16

Greeting list. I am doing the load test of Kamailio with SIPp using most basic script(kamailio.cfg) with logging level set to minimum to dispatch requests to SIPp UAS. This is my dispatcher code snippet. $avp(quality) = "1"; ds_select_dst("$avp(quality)", "4"); route(RELAY); At 70 CPS calls work fine. But if I increase CPS to 80, Kamailio stops accepting calls for few seconds and comes to life after being idle for some time. 100 CPS for sip proxy is not hot cake. Also, I see in http://www.kamailio.org/docs/openser-performance-tests/ tests were made with -l27 and -m7000 which looks wronged to me. ./sipp -sf uac_inv.xml <http://www.kamailio.org/docs/openser-performance-tests/data/uac_inv.xml> -rsa 192.168.2.102:5060 192.168.2.102:5070 -m 200000 -r 7000 -d 1 -l 27 There must be something wrong in my configuration since this cps is very low. kamailio -version version: kamailio 4.4.1 (x86_64/linux) 90be8b flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 90be8b SHM_MEMORY=768 PKG_MEMORY=64 Any suggestion is much appreciated. Best Regards,

2 2

Issue with ftag parameter in Record-Route header
by Valentin Christoph 21 Jul '16

21 Jul '16

Hi community, I'm using an MGCF that creates From tags like **%%!!MYOFFICE++00!!%%**A0F1F1BA Now the special characters "%%" are allowed in tags (i.e. "token" according to RFC 3261), token = 1*(alphanum / "-" / "." / "!" / "%" / "*" / "_" / "+" / "`" / "'" / "~" ) but they are NOT allowed in URI parameters according to RFC 3261 uri-parameter = transport-param / user-param / method-param / ttl-param / maddr-param / lr-param / other-param other-param = pname [ "=" pvalue ] pname = 1*paramchar pvalue = 1*paramchar paramchar = param-unreserved / unreserved / escaped param-unreserved = "[" / "]" / "/" / ":" / "&" / "+" / "$" unreserved = alphanum / mark mark = "-" / "_" / "." / "!" / "~" / "*" / "'" / "(" / ")" escaped = "%" HEXDIG HEXDIG which makes the MGCF ignore the whole RR header and sending subsequent requests directly to the peer SIP UA, instead of sending it to the CSCF. Hence it's not OK to just copy the From tag into the ftag parameter, imho. We did a workaround in the MGCF, now sending **~~!!MYOFFICE++00!!~~**A0F1F1BA, but strictly spoken the kamailio S-CSCF is not compliant to RFC 3261. What's your opinion? Is there an configuration option to make it compliant? All the best Christoph The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 0

Tsilo Tiimers
by Nahum Nir 21 Jul '16

21 Jul '16

Hello, How can I chage the timer waiting for the client to send the register. i.e. how much time to wait for the push? Thanks, Nir

2 2

Trouble with Asterisk behind Kamailio
by Tickling Contest 21 Jul '16

21 Jul '16

Hello, I am following the instructions in http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb to configure my Kamailio and Asterisk (using PJSIP realtime with MySQL). I am able to get Kamailio register the clients (tested with Zoiper softphone), but having trouble getting any further to load balance a couple of Asterisk servers. Here is a range of issues I have: (a) The Kamailio server keeps sending UDP SIP messages to the Asterisk server and it is not clear where to control what protocol to use to send SIP messages Asterisk server(s). (b) I followed the instructions for the dispatcher module in the wiki, but it is not clear why I should use the #!define WITH_ASTERISK directive to enumerate the bind IPs and ports (how does this reconcile with the list of Asterisk servers in the dispatcher.list file?): !ifdef WITH_ASTERISK asterisk.bindip = "192.168.1.102" desc "Asterisk IP Address" asterisk.bindport = "5060" desc "Asterisk Port" kamailio.bindip = "192.168.1.101" desc "Kamailio IP Address" kamailio.bindport = "5060" desc "Kamailio Port" Also, where do I specify the protocol to use when sending to the Asterisk servers? Is it auto detected? If so, why is Kamailio not detecting that the Asterisk servers are only listening on TCP? Any help is appreciated. My entire /etc/kamailio/kamailio.cfg file is in here: https://gist.github.com/ticklingcontest/c7437dbc2d8e838834ee4d852753f254. I am using Kamailio 4.0.4 with Asterisk 13.7.2 using TCP for PJSIP. Thanks!

3 3

Kamailio Crashes when dispatcher failover is being applied
by TEG AMJG 21 Jul '16

21 Jul '16

Dear list Im quite new to Kamailio and i found something while trying to see the failover behaviour in Kamailio. I have a kamailio v4.3.5 load balancing two Asterisk boxes. This happens just when i stop one of the asterisk and make a call that is being load balanced to the same asterisk box that i stopped before, when trying to go to failure_route and dispatch it to the other box then Kamailio just crashes. I have debug=4 in the config file and it really doesnt say much about the error. This is the relative logging i could found: *Jul 18 16:30:13 kam2 /usr/sbin/kamailio[69548]: INFO: <script>: UBICAR: Forwarding non-registrar requests to AsteriskJul 18 16:30:13 kam2 /usr/sbin/kamailio[69548]: INFO: <script>: UBICAR: Dispatching to Asterisk Box sip:10.0.1.201:5060 <http://10.0.1.201:5060>Jul 18 16:30:13 kam2 /usr/sbin/kamailio[69550]: INFO: <script>: UBICAR: requestm=INVITE reply=<null> SIP packet comes from the Asterisk Box duid=PBX2;my=pbx2;maxload=10000 callid=4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060 <http://4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060>Jul 18 16:30:13 kam2 /usr/sbin/kamailio[69550]: INFO: <script>: UBICAR: requestm=INVITE reply=<null> SIP packet comes from the Asterisk Box duid=PBX2;my=pbx2;maxload=10000 callid=4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060 <http://4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060>Jul 18 16:30:18 kam2 /usr/sbin/kamailio[69547]: INFO: <script>: UBICAR: setting call load requesturi=<null> callid=896175650(a)192.168.14.76 <896175650(a)192.168.14.76>Jul 18 16:30:20 kam2 /usr/sbin/kamailio[69550]: INFO: <script>: UBICAR: delete call load requesturi=sip:10005@10.0.1.201:5060 <http://sip:10005@10.0.1.201:5060> callid=896175650(a)192.168.14.76 <896175650(a)192.168.14.76>Jul 18 16:30:38 kam2 /usr/sbin/kamailio[69548]: INFO: <script>: UBICAR: Forwarding non-registrar requests to AsteriskJul 18 16:30:38 kam2 /usr/sbin/kamailio[69548]: INFO: <script>: UBICAR: Dispatching to Asterisk Box sip:10.0.1.201:5060 <http://10.0.1.201:5060>Jul 18 16:30:42 kam2 /usr/sbin/kamailio[69559]: ALERT: <script>: UBICAR: Asterisk sip:10.0.1.201:5060 <http://10.0.1.201:5060> failed to answer, selecting other one!Jul 18 16:30:42 kam2 /usr/sbin/kamailio[69559]: INFO: <script>: UBICAR: Dispatching to Asterisk Box sip:10.0.1.200:5060 <http://10.0.1.200:5060>Jul 18 16:30:43 kam2 /usr/sbin/kamailio[69546]: ALERT: <core> [main.c:728]: handle_sigs(): child process 69559 exited by a signal 11Jul 18 16:30:43 kam2 /usr/sbin/kamailio[69546]: ALERT: <core> [main.c:731]: handle_sigs(): core was generatedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69546]: INFO: <core> [main.c:743]: handle_sigs(): terminating due to SIGCHLDJul 18 16:30:43 kam2 /usr/sbin/kamailio[69563]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69562]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69561]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69558]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69557]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69556]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69555]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69554]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69553]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69552]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69551]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69548]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69547]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69549]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69550]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69560]: INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69546]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized* My configuration when applying load balancing and failover is detailed here: *# Send to Asteriskroute[TOASTERISK] {#!ifdef WITH_LOADBALANCE xlog("L_INFO","UBICAR: Forwarding non-registrar requests to Asterisk \n"); if(!ds_select_dst("0", "10")) { sl_send_reply("500", "Service Unavailable"); xlog("L_ERROR","UBICAR: No destinations available for $rd \n"); exit; } xlog("L_INFO","UBICAR: Dispatching to Asterisk Box $du\n"); t_set_fr(0,4000); t_on_failure("MANAGE_FAILURE"); route(RELAY); exit;#!endif* *# manage failure routing casesfailure_route[MANAGE_FAILURE] { #xlog("L_ALERT","UBICAR: failure requestm=$rm requesturi=$ru callid=$ci\n"); if (t_is_canceled()) { exit; }#!ifdef WITH_LOADBALANCE xlog("L_ALERT","UBICAR: Asterisk $du failed to answer, selecting other one!"); # next DST - only for 500 reply or local timeout (set by t_set_fr()) if (t_check_status("500") || t_branch_timeout() || !t_branch_replied()) { #we mark the destination Inactive and Probing ds_mark_dst("ip"); #select the new destination if(ds_next_dst()) { t_set_fr(0,4000); t_on_failure("MANAGE_FAILURE"); xlog("L_INFO","UBICAR: Dispatching to Asterisk Box $du\n"); route(RELAY); exit; }else{ #last available node failed to reply, no other destinations available send_reply("404", "No destination"); exit; }#!endif }}* It may be a bug in that Kamailio version because i used Kamailio v4.2 before and i didnt have that inconvenient, still i had to upgrade to v4.3 because i needed the default_socket modparam that wasnt implemented in Kamailio v4.2 Any hint about this issue would be appreciate it Best Regards Alejandro

2 1

Managing concurrent ports
by Grant Bagdasarian 21 Jul '16

21 Jul '16

Hello, Are there any recommended modules for managing concurrent ports for different endpoints/customers/accounts/etc? I believe the dialog and dialog_ng modules do exactly this, but how is the performance of these modules under high loads? What is the release time of the ports? Are there perhaps other modules? Regards, Grant

3 6

Kamailio + rtpproxy + SRTP
by Konstantin M. 20 Jul '16

20 Jul '16

I have some problem with SSL+rtpproxy, kamailio successfully decodes SIP, rtpproxy decodes SRTP frames, all is going to freeswitch unencrypted. FS transfers the call back, the call is going unencrypted though kamailio, kamailio encodes to SSL, but rtpproxy DOESN'T encodes RTP frames to SRTP. Hence, endpoint SIP equipment rejects the call with 488 Not Acceptable Here Scenario 1. Endpoint device -> SRTP -> kamailio -> RTP -> freeswitch 2. Freeswitch calls back 3. freeswitch -> RTP -> kamailio -> PROBLEM (SIP[TLS] + RTP (but not SRTP)) -> Endpoint device 4. Endpoint device -> 488 Not Acceptable Here -> Kamailio Could somebody point me what's wrong here? Thanks!

2 1

WEBRTC Confusion (2)
by Zaka 20 Jul '16

20 Jul '16

Dear List: I am still stuck. Still unable to get Kamailio to listen on WEBRTC port* (in this case 8000)* Please advise if it has something to do with disabling TLS/MSRP? Please see the log & related config file in line here: *Log:* 0(5724) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !MY_WS_PORT!8000!g *and the result of config file check:* root@callcntr:/usr/local/etc/kamailio# kamailio -eE -ddd -cf /usr/local/etc/kamailio/websocket.cfg 0(5902) INFO: <core> [main.c:1911]: main(): private (per process) memory: 8388608 bytes 0(5902) DEBUG: <core> [mem/f_malloc.c:323]: fm_malloc_init(): fm_malloc_init: F_OPTIMIZE=16384, /ROUNDTO=2048 0(5902) DEBUG: <core> [mem/f_malloc.c:325]: fm_malloc_init(): fm_malloc_init: F_HASH_SIZE=2099, fm_block size=33912 0(5902) DEBUG: <core> [mem/f_malloc.c:327]: fm_malloc_init(): fm_malloc_init(0x7f9ca6e1f010, 8388608), start=0x7f9ca6e1f010 0(5902) DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xac2700)[0] to 0 0(5902) DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xac2680)[0] to 0 0(5902) DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xac26c0)[0] to 0 0(5902) DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xac2720)[0] to 0 0(5902) DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xac26a0)[0] to 0 0(5902) DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xac26e0)[0] to 0 0(5902) DEBUG: <core> [pvapi.c:1976]: pv_init_buffer(): PV print buffer initialized to [10][8192] 0(5902) DEBUG: <core> [main.c:2097]: main(): read 286773155 from /dev/urandom 0(5902) DEBUG: <core> [main.c:2103]: main(): seeding PRNG with 1755363211 0(5902) DEBUG: <core> [main.c:2107]: main(): test random numbers 726213135 321707966 991183401 0(5902) DEBUG: <core> [re.c:313]: subst_parser(): ok, se is 0x7f9ca6e3fc48 0(5902) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !DBURL!mysql://kamailio:kamailiorw@localhost/kamailio!g 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: DBURL 0(5902) DEBUG: <core> [cfg.lex:1776]: pp_define_set(): ### setting define ID [DBURL] value [mysql://kamailio:kamailiorw@localhost/kamailio] 0(5902) DEBUG: <core> [ppcfg.c:160]: pp_substdef_add(): ### added substdef: [DBURL]=[mysql://kamailio:kamailiorw@localhost/kamailio] (0) 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:313]: subst_parser(): ok, se is 0x7f9ca6e3ffe8 0(5902) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !MY_IP_ADDR!192.168.1.16!g 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: MY_IP_ADDR 0(5902) DEBUG: <core> [cfg.lex:1776]: pp_define_set(): ### setting define ID [MY_IP_ADDR] value [192.168.1.16] 0(5902) DEBUG: <core> [ppcfg.c:160]: pp_substdef_add(): ### added substdef: [MY_IP_ADDR]=[192.168.1.16] (0) 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:313]: subst_parser(): ok, se is 0x7f9ca6e40320 0(5902) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !MY_DOMAIN!callcntr.com.al!g 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: MY_DOMAIN 0(5902) DEBUG: <core> [cfg.lex:1776]: pp_define_set(): ### setting define ID [MY_DOMAIN] value [callcntr.com.al] 0(5902) DEBUG: <core> [ppcfg.c:160]: pp_substdef_add(): ### added substdef: [MY_DOMAIN]=[callcntr.com.al] (0) 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:313]: subst_parser(): ok, se is 0x7f9ca6e40658 0(5902) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !MY_WS_PORT!8000!g 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: MY_WS_PORT 0(5902) DEBUG: <core> [cfg.lex:1776]: pp_define_set(): ### setting define ID [MY_WS_PORT] value [8000] 0(5902) DEBUG: <core> [ppcfg.c:160]: pp_substdef_add(): ### added substdef: [MY_WS_PORT]=[8000] (0) 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:313]: subst_parser(): ok, se is 0x7f9ca6e40988 0(5902) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !MY_WSS_PORT!443!g 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: MY_WSS_PORT 0(5902) DEBUG: <core> [cfg.lex:1776]: pp_define_set(): ### setting define ID [MY_WSS_PORT] value [443] 0(5902) DEBUG: <core> [ppcfg.c:160]: pp_substdef_add(): ### added substdef: [MY_WSS_PORT]=[443] (0) 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:313]: subst_parser(): ok, se is 0x7f9ca6e40cb8 0(5902) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !MY_MSRP_PORT!9000!g 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: MY_MSRP_PORT 0(5902) DEBUG: <core> [cfg.lex:1776]: pp_define_set(): ### setting define ID [MY_MSRP_PORT] value [9000] 0(5902) DEBUG: <core> [ppcfg.c:160]: pp_substdef_add(): ### added substdef: [MY_MSRP_PORT]=[9000] (0) 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=0 0(5902) DEBUG: <core> [re.c:455]: subst_run(): matched (16, 10): [MY_IP_ADDR] 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [ppcfg.c:192]: pp_subst_run(): preprocess subst applied [#1] to [!MY_WS_ADDR!tcp:MY_IP_ADDR:MY_WS_PORT!g] - returning new string [!MY_WS_ADDR!tcp:192.168.1.16:MY_WS_PORT!g] 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=0 0(5902) DEBUG: <core> [re.c:455]: subst_run(): matched (29, 10): [MY_WS_PORT] 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [ppcfg.c:192]: pp_subst_run(): preprocess subst applied [#2] to [!MY_WS_ADDR!tcp:192.168.1.16:MY_WS_PORT!g] - returning new string [!MY_WS_ADDR!tcp:192.168.1.16:8000!g] 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:436]: subst_run(): running. r=1 0(5902) DEBUG: <core> [re.c:505]: subst_str(): no match 0(5902) DEBUG: <core> [re.c:313]: subst_parser(): ok, se is 0x7f9ca6e41118 0(5902) INFO: <core> [ppcfg.c:82]: pp_subst_add(): ### added subst expression: !MY_WS_ADDR!tcp:192.168.1.16:8000!g 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: MY_WS_ADDR 0(5902) DEBUG: <core> [cfg.lex:1776]: pp_define_set(): ### setting define ID [MY_WS_ADDR] value [tcp:192.168.1.16:8000] 0(5902) DEBUG: <core> [ppcfg.c:160]: pp_substdef_add(): ### added substdef: [MY_WS_ADDR]=[tcp:192.168.1.16:8000] (0) 0(5902) DEBUG: <core> [cfg.lex:1690]: pp_define(): defining id: WITH_WEBSOCKETS 0(5902) DEBUG: <core> [cfg.lex:1795]: pp_define_get(): ### returning define ID [MY_IP_ADDR] value [192.168.1.16] 0(5902) DEBUG: <core> [cfg.lex:1795]: pp_define_get(): ### returning define ID [MY_IP_ADDR] value [192.168.1.16] loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(5902) DEBUG: <core> [ppcfg.c:223]: pp_ifdef_level_check(): same number of pairing preprocessor directives #!IF[N]DEF - #!ENDIF 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): routing table 0: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_WARN" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e443b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "403" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:347]: print_action(): route( 0(5902) DEBUG: <core> [route_struct.c:452]: print_action(): "REQINIT" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:421]: print_action(): force_rport( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<0> 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e50ff0> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_ERR" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e443b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "400" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:347]: print_action(): route( 0(5902) DEBUG: <core> [route_struct.c:452]: print_action(): "WITHINDLG" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e42f78> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e43950> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:347]: print_action(): route( 0(5902) DEBUG: <core> [route_struct.c:452]: print_action(): "AUTH" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4c350> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:543]: print_action(): , type<22> 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e44968> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:347]: print_action(): route( 0(5902) DEBUG: <core> [route_struct.c:452]: print_action(): "REGISTRAR" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e443b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "484" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:347]: print_action(): route( 0(5902) DEBUG: <core> [route_struct.c:452]: print_action(): "LOCATION" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:347]: print_action(): route( 0(5902) DEBUG: <core> [route_struct.c:452]: print_action(): "RELAY" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): routing table 1: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e44460> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): routing table 2: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e443b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "483" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d7d0> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "Malformed SIP message from $si:$sp " 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4cdb0> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): routing table 3: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_ERR" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e443b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "400" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:347]: print_action(): route( 0(5902) DEBUG: <core> [route_struct.c:452]: print_action(): "RELAY" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e42f78> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e443b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "404" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): routing table 4: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e44460> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): routing table 5: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e42a70> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e44428> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "404" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:442]: print_action(): assign( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<21> 0(5902) DEBUG: <core> [route_struct.c:517]: print_action(): , type<22> 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e42a70> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:448]: print_action(): UNKNOWN( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:517]: print_action(): , type<24> 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): routing table 6: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4e8b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "$fd" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4e810> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e443b8> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "403" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): onreply routing table 0: 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_WARN" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 0 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 9 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e50e68> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 0 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): event routing table 1: 0(5902) DEBUG: <core> [route_struct.c:448]: print_action(): UNKNOWN( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<0> 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:448]: print_action(): UNKNOWN( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<0> 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_WARN" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e50660> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 4 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "403" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_DBG" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_WARN" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e50660> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 4 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "403" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:401]: print_action(): if ( 0(5902) DEBUG: <core> [route_struct.c:483]: print_action(): type<22> 0(5902) DEBUG: <core> [route_struct.c:485]: print_action(): ) { 0(5902) DEBUG: <core> [route_struct.c:338]: print_action(): drop( 0(5902) DEBUG: <core> [route_struct.c:455]: print_action(): 1 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 1 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:519]: print_action(): } else { 0(5902) DEBUG: <core> [route_struct.c:545]: print_action(): }; 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e50660> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 4 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "404" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:2132]: print_rl(): event routing table 2: 0(5902) DEBUG: <core> [route_struct.c:418]: print_action(): external_module_call( 0(5902) DEBUG: <core> [route_struct.c:467]: print_action(): f_ptr<0x7f9ca6e4d808> 0(5902) DEBUG: <core> [route_struct.c:493]: print_action(): , 2 0(5902) DEBUG: <core> [route_struct.c:524]: print_action(): , "L_INFO" 0(5902) DEBUG: <core> [route_struct.c:546]: print_action(): ); 0(5902) DEBUG: <core> [route.c:2134]: print_rl(): 0(5902) DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xac26e0)[core:receive-parse-error] to 3 0(5902) INFO: <core> [sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 192.168.1.16:5060 tcp: 192.168.1.16:5060 Aliases: tcp: callcntr:5060 udp: callcntr:5060 config file ok, exiting... root@callcntr:/usr/local/etc/kamailio# *Config File:* #!KAMAILIO # # Simple/sample kamailio.cfg for running a proxy/registrar with TLS and # WebSockets support. #!substdef "!DBURL!mysql://kamailio:kamailiorw@localhost/kamailio!g" #!substdef "!MY_IP_ADDR!192.168.1.16!g" #!substdef "!MY_DOMAIN!callcntr.com.al!g" #!substdef "!MY_WS_PORT!8000!g" #!substdef "!MY_WSS_PORT!443!g" #!substdef "!MY_MSRP_PORT!9000!g" #!substdef "!MY_WS_ADDR!tcp:MY_IP_ADDR:MY_WS_PORT!g" ##!substdef "!MY_WSS_ADDR!tls:MY_IP_ADDR:MY_WSS_PORT!g" ##!substdef "!MY_MSRP_ADDR!tls:MY_IP_ADDR:MY_MSRP_PORT!g" ##!substdef "!MSRP_MIN_EXPIRES!1800!g" ##!substdef "!MSRP_MAX_EXPIRES!3600!g" ##!define LOCAL_TEST_RUN ##!define WITH_TLS #!define WITH_WEBSOCKETS ##!define WITH_MSRP ####### Global Parameters ######### fork=yes children=4 #!ifdef WITH_TLS enable_tls=1 #!endif listen=MY_IP_ADDR #!ifdef WITH_WEBSOCKETS listen=MY_IP_ADDR #!ifdef WITH_TLS #listen=MY_WSS_ADDR #!endif #!endif #!ifdef WITH_MSRP listen=MY_MSRP_ADDR #!endif tcp_connection_lifetime=3604 tcp_accept_no_cl=yes tcp_rd_buf_size=16384 #!ifdef LOCAL_TEST_RUN debug=2 mpath="modules" #!else debug=0 mpath="/usr/local/lib64/kamailio/modules/" #!endif loadmodule "db_mysql.so" loadmodule "tm.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "auth.so" loadmodule "auth_db.so" loadmodule "kex.so" loadmodule "mi_rpc.so" loadmodule "corex.so" #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_MSRP loadmodule "msrp.so" loadmodule "htable.so" loadmodule "cfgutils.so" #!endif #!ifdef WITH_WEBSOCKETS loadmodule "xhttp.so" loadmodule "websocket.so" loadmodule "nathelper.so" #!endif #!ifdef WITH_WEBSOCKETS # ----- nathelper params ----- modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") # Note: leaving NAT pings turned off here as nathelper is _only_ being used for # WebSocket connections. NAT pings are not needed as WebSockets have # their own keep-alives. #!endif ####### Routing Logic ######## # Main SIP request routing logic # - processing of any incoming SIP request starts with this route # - note: this is the same as route { ... } request_route { * if (($Rp == MY_WS_PORT)) { * *#### I deleted/ modified this logical expression ####* xlog("L_WARN", "SIP request received on $Rp\n"); sl_send_reply("403", "Forbidden"); exit; } # per request initial checks route(REQINIT); #!ifdef WITH_WEBSOCKETS if (nat_uac_test(64)) { # Do NAT traversal stuff for requests from a WebSocket # connection - even if it is not behind a NAT! # This won't be needed in the future if Kamailio and the # WebSocket client support Outbound and Path. force_rport(); if (is_method("REGISTER")) { fix_nated_register(); } else { if (!add_contact_alias()) { xlog("L_ERR", "Error aliasing contact <$ct>\n"); sl_send_reply("400", "Bad Request"); exit; } } } #!endif # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { t_relay(); } exit; } t_check_trans(); # authentication route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE")) { record_route(); } # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484", "Address Incomplete"); exit; } # user location service route(LOCATION); route(RELAY); } route[RELAY] { if (!t_relay()) { sl_reply_error(); } exit; } # Per SIP request initial checks route[REQINIT] { if (!mf_process_maxfwd_header("10")) { sl_send_reply("483", "Too Many Hops"); exit; } if (!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } if (uri == myself && is_method("OPTIONS") && !(uri=~"sip:.*[@]+.*")) { options_reply(); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { #!ifdef WITH_WEBSOCKETS if ($du == "") { if (!handle_ruri_alias()) { xlog("L_ERR", "Bad alias <$ru>\n"); sl_send_reply("400", "Bad Request"); exit; } } #!endif route(RELAY); } else { if ( is_method("ACK") ) { if ( t_check_trans() ) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server t_relay(); exit; } else { # ACK without matching transaction... # ignore and discard exit; } } sl_send_reply("404", "Not Found"); } exit; } } # Handle SIP registrations route[REGISTRAR] { if (is_method("REGISTER")) { if (!save("location")) { sl_reply_error(); } exit; } } # USER location service route[LOCATION] { if (!is_subscriber("$ru", "subscriber", "1")) { t_newtran(); send_reply("404", "Not Found"); exit; } if (!lookup("location")) { $var(rc) = $rc; t_newtran(); switch ($var(rc)) { case -1: send_reply("480", "Temporarily Unavailable"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; case -3: send_reply("500", "Server Internal Error"); exit; } } } # Authentication route route[AUTH] { if (is_method("REGISTER") || from_uri==myself) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); exit; } # user authenticated - remove auth header if(!is_method("REGISTER")) { consume_credentials(); } } # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here if (from_uri!=myself && uri!=myself) { sl_send_reply("403", "Forbidden"); exit; } } #!ifdef WITH_WEBSOCKETS onreply_route { if ((($Rp == MY_WS_PORT) && !(proto == WS)) || $Rp == MY_MSRP_PORT) { xlog("L_WARN", "SIP response received on $Rp\n"); drop; } if (nat_uac_test(64)) { # Do NAT traversal stuff for replies to a WebSocket connection # - even if it is not behind a NAT! # This won't be needed in the future if Kamailio and the # WebSocket client support Outbound and Path. add_contact_alias(); } } event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); if ($Rp != MY_WS_PORT #!ifdef WITH_TLS && $Rp != MY_WSS_PORT #!endif ) { xlog("L_WARN", "HTTP request received on $Rp\n"); xhttp_reply("403", "Forbidden", "", ""); exit; } xlog("L_DBG", "HTTP Request Received\n"); if ($hdr(Upgrade)=~"websocket" && $hdr(Connection)=~"Upgrade" && $rm=~"GET") { # Validate Host - make sure the client is using the correct # alias for WebSockets if ($hdr(Host) == $null || !is_myself("sip:" + $hdr(Host))) { xlog("L_WARN", "Bad host $hdr(Host)\n"); xhttp_reply("403", "Forbidden", "", ""); exit; } # Optional... validate Origin - make sure the client is from an # authorised website. For example, # # if ($hdr(Origin) != "http://communicator.MY_DOMAIN" # && $hdr(Origin) != "https://communicator.MY_DOMAIN") { # xlog("L_WARN", "Unauthorised client $hdr(Origin)\n"); # xhttp_reply("403", "Forbidden", "", ""); # exit; # } # Optional... perform HTTP authentication # ws_handle_handshake() exits (no further configuration file # processing of the request) when complete. if (ws_handle_handshake()) { # Optional... cache some information about the # successful connection exit; } } xhttp_reply("404", "Not Found", "", ""); } event_route[websocket:closed] { xlog("L_INFO", "WebSocket connection from $si:$sp has closed\n"); } #!endif #!ifdef WITH_MSRP event_route[msrp:frame-in] { msrp_reply_flags("1"); if ((($Rp == MY_WS_PORT || $Rp == MY_WSS_PORT) && !(proto == WS || proto == WSS)) && $Rp != MY_MSRP_PORT) { xlog("L_WARN", "MSRP request received on $Rp\n"); msrp_reply("403", "Action-not-allowed"); exit; } if (msrp_is_reply()) { msrp_relay(); } else if($msrp(method)=="AUTH") { if($msrp(nexthops)>0) { msrp_relay(); exit; } if (!www_authenticate("MY_DOMAIN", "subscriber", "$msrp(method)")) { if (auth_get_www_authenticate("MY_DOMAIN", "1", "$var(wauth)")) { msrp_reply("401", "Unauthorized", "$var(wauth)"); } else { msrp_reply("500", "Server Error"); } exit; } if ($hdr(Expires) != $null) { $var(expires) = (int) $hdr(Expires); if ($var(expires) < MSRP_MIN_EXPIRES) { msrp_reply("423", "Interval Out-of-Bounds", "Min-Expires: MSRP_MIN_EXPIRES\r\n"); exit; } else if ($var(expires) > MSRP_MAX_EXPIRES) { msrp_reply("423", "Interval Out-of-Bounds", "Max-Expires: MSRP_MAX_EXPIRES\r\n"); exit; } } else { $var(expires) = MSRP_MAX_EXPIRES; } $var(cnt) = $var(cnt) + 1; pv_printf("$var(sessid)", "s.$(pp).$(var(cnt)).$(RANDOM)"); $sht(msrp=>$var(sessid)::srcaddr) = $msrp(srcaddr); $sht(msrp=>$var(sessid)::srcsock) = $msrp(srcsock); $shtex(msrp=>$var(sessid)) = $var(expires) + 5; # - Use-Path: the MSRP address for server + session id $var(hdrs) = "Use-Path: msrps://MY_IP_ADDR:MY_MSRP_PORT/" + $var(sessid) + ";tcp\r\n" + "Expires: " + $var(expires) + "\r\n"; msrp_reply("200", "OK", "$var(hdrs)"); } else if ($msrp(method)=="SEND" || $msrp(method)=="REPORT") { if ($msrp(nexthops)>1) { if ($msrp(method)!="REPORT") { msrp_reply("200", "OK"); } msrp_relay(); exit; } $var(sessid) = $msrp(sessid); if ($sht(msrp=>$var(sessid)::srcaddr) == $null) { # one more hop, but we don't have address in htable msrp_reply("481", "Session-does-not-exist"); exit; } else if ($msrp(method)!="REPORT") { msrp_reply("200", "OK"); } msrp_relay_flags("1"); msrp_set_dst("$sht(msrp=>$var(sessid)::srcaddr)", "$sht(msrp=>$var(sessid)::srcsock)"); msrp_relay(); } else { msrp_reply("501", "Request-method-not-understood"); } } #!endif Thanks a million! Zaka One accurate measurement is worth more than a thousand expert opinions!

2 4

reading siptrace trace_on current value in script
by ananda agrawal 20 Jul '16

20 Jul '16

Hi, Is it possible to check wether the trace_on for siptrace module is on or off from within the config script, e.g inside routing logic, thannks in advance -Anand

1 0

Crocodile-msrp
by Marcelo Pignataro 19 Jul '16

19 Jul '16

Hi, I don't really know if I'm writing to the right list, sorry if I don't. Has someone been using crocodile-msrp library? I need to develop a webchat app with Kamailio together and I found Crocodile, but I see it hasn't documentation neither guides to developers. I also realize it hasn't active community, last commit done to crocodile-msrp library by its developers was 2013. I need some information to know if I should use it or not. Thank you and best regards, Marcelo

1 0

Push Notifications
by Nahum Nir 18 Jul '16

18 Jul '16

Hello, Found the presentation about asynch push. Is there an example cfg file? Thanks, Nir

3 6

Custom header on reply is removed on t_relay
by David Wilson 18 Jul '16

18 Jul '16

Hello All, We have a Kamailio proxy (P1) and a custom client (A). Calls are working reliably with A communicating directly with P1. When A sends INVITE to P1, in some cases, we insert a custom header ‘X-Routing’ in the reply. Now, testing with a new, additional proxy (P2) between these two: A -> P2 -> P1 A sends INVITE via P2 to P1, P1 replies include X-Routing header field (confirmed by logging message buffer received from P1 by P2). However, the reply relayed from P2 to A does not contain the custom header. P2’s reply_route block only contains logging code and I’ve checked for calls to remove_hf. I can’t find documentation or code to explain why the header is omitted. Is there a module config parameter that I can set to preserve custom headers? Any suggestions welcome! Regards, Dave Wilson.

2 1

Rx Interface connected, get error code: SIP/2.0 403 Forbidden - You must register first with a S-CSCF
by Kristian Martens 18 Jul '16

18 Jul '16

Hi, I have installed Kamailio version 4.4.1. Everything works just fine. If I connect a PCRF via Rx to the P-CSCF, the registration still runs through as expected but the subsequent SUBSCRIBE is rejected with "403 Forbidden - You must register first with a S-CSCF" error cause or is simply ignored (see attached wireshark traces). And, if I disconnect Rx and restart the P-CSCF, the "forbidden" problem still persists. (But I can work around this by cleaning up the P-CSCF database.) Any suggestions how I could get Rx working? Thanks, Kristian

3 7

kamailio-dbg package
by Laura García Pérez 18 Jul '16

18 Jul '16

Is it possible to install kamailio-dbg in CentOS? Thanks, Laura García Pérez www.logslie.com <http://www.logslie.com/> +34680923532 +12602069698

2 2

Conditionally calling TOPOS
by Nathan Ward 18 Jul '16

18 Jul '16

Hi, I think it make sense to put this topic in a seperate message, though this is very much the same scenario mentioned here: http://lists.sip-router.org/pipermail/sr-users/2016-July/093864.html I would like the ability initiate topology hiding only for certain messages - i.e. on inbound calls, I would like my Kamailio ‘SBC' to retain the routing information for inbound requests, but strip it for outgoing requests - so that I can see the full path a call has taken to reach and then traverse my network all the way to an egress SBC but then this is all stripped before forwarding the call to a 3rd party (i.e. customer, or carrier). I note that this isn’t possible at present, but I’d like to take a stab at the code, perhaps designating ‘trusted’ IPs for which topology hiding doesn’t take place. Before I embark on this, is this something that would be considered useful, or is there a good reason to have full topology hiding that I’m missing? -- Nathan Ward

2 1

TOPOS - REGISTER
by Nathan Ward 18 Jul '16

18 Jul '16

Hi all, I’m doing some testing using Kamailio to do some lightweight SBC type functions. We have considered OpenSIPs as well as it has built in b2bua bits, but having chosen Kamailio for other parts of our network it makes sense to stick with one piece of software I think. Luckily, we only need (want) topology hiding, and don’t need other b2bua things. I have a server in the middle of our network sending registrations out to a 3rd party network for a number of lines, using Kamailio+uacreg. This works great. It sends these registrations through an SBC, also running Kamailio. I do this by setting the proxy column of the uacreg table to the SBC’s inside address. On the SBC, I rewrite the Contact header, so calls come in to the SBC. I am running topos on the SBC, and would like to be able to do topology hiding for the outgoing REGISTER. I note that there is code in tps_skip_msg to specifically avoid topology hiding for REGISTER and PUBLISH messages. Is there a SIP reason for this, or is this just a part of the code that hasn’t been finished yet or wasn’t needed by the author, so it’s been excluded? I note that topoh is the same, with a th_skip_msg function that has I think identical code, so no doubt the same reasoning is applied there. This is a very minor issue, but I’d like to understand the reasoning, and contribute code if the reason is code rather than SIP. -- Nathan Ward

2 1

RTPProxy Issues
by TEG AMJG 18 Jul '16

18 Jul '16

Dear list I am quite new to Kamailio and i have been able to solve some NAT Traversal issues with symmetric SIP+RTP putting kamailio+rtpproxy behind NAT, i am also load balancing some asterisk boxes for transcoding and some other services like voicemail. Also i am using SIPp for load testing Now the question is that, while everything is working great with NAT (even when i am using SIPp for testing with low load) when i am about to test it with more than 150 calls or something i am starting to get the following error: *kamailio[34549]: ERROR: rtpproxy [rtpproxy.c:2735]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy* I have been trying to look at some SIP packets when the error starts and i am not seeing anything out of the normal (while being quite difficult to debug when having so many concurrent calls at SIP level) My configuration doesnt have anything new, the only thing is that, because Kamailio is behind NAT i used some ideas from some other users and debates from this same mailing list: *# RTPProxy control* *route[NATMANAGE] {* *#!ifdef WITH_NAT* * if(is_request()) {* * if(has_totag()) {* * if(check_route_param("nat=yes")) {* * setbflag(FLB_NATB);* * }* * }* * }* * if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB)))* * return;* * if(!route(FROMASTERISK)){* * force_send_socket(10.0.1.207);* * rtpproxy_manage("rw","10.0.1.206");* * }else{* * force_send_socket(10.0.1.206);* * rtpproxy_manage("rw","10.0.5.203");* * }* * if (is_request()) {* * if (!has_totag()) {* * add_rr_param(";nat=yes");* * }* * }* * if (is_reply()) {* * if(isbflagset(FLB_NATB)) {* * fix_nated_contact();* * }* *#!endif* * return;* *}* This solution is based of someone's idea from this mailing list: http://lists.sip-router.org/pipermail/sr-users/2013-January/076254.html As you can see in my configuration, my "public network" is really private network so i tweak the NATDETECT route to not include RFC1918 networks as part of the detection *# Caller NAT detection route* *route[NATDETECT] {* *#!ifdef WITH_NAT* *if (nat_uac_test("1")) {* * if (nat_uac_test("18")) {* * force_rport();* * if (is_method("REGISTER")) {* * fix_nated_register();* * } else {* * fix_nated_contact();* * }* * setflag(FLT_NATS);* * return;* * }* * }* *#!endif* * return;* *}* Also i would like to know how may i use RTPProxy logs?, i tried to configure it like this: /etc/rsyslog.conf *# Kamailio logging* *local0.* -/var/log/kamailio.log* *#RTPProxy logging* *local3.* /var/log/rtpproxy.log* /etc/sysconfig/rtpproxy *OPTIONS="-l 10.0.1.206 -A 10.0.5.203 -s udp:127.0.0.1:7722 <http://127.0.0.1:7722> -r /var/lib/rtpproxy/sessions -d DBUG:LOG_LOCAL3 -m 35000 -M 55000 -F"* I cannot see anyhing in the logs Thank you very much Alejandro

3 3

Questions
by francisco rodriguez 15 Jul '16

15 Jul '16

Hello ; I have the sip account with you, but to put it to work in a team asks me some data. you can tell me what they are. my account is sip: masterlaradio(a)iptel.org I request the following information IP SERVER :? SERVER USER? USERNAME? STUN DOMAIN? DNS SERVER? thanks for your attention and collaboration Francisco Rodriguez Enviado desde Correo<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10

1 0

Websocket Path Issues
by Colin Morelli 15 Jul '16

15 Jul '16

Hey all, I'm using Kamailio as an outbound edge proxy for websocket connections. When my registrar calls out to Kamailio to forward to a websocket connection that has since been killed, rather than just entering the failure branch, it throws a few errors: 5(24) WARNING: <core> [msg_translator.c:2760]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found 5(24) ERROR: <core> [msg_translator.c:1978]: build_req_buf_from_sip_req(): could not create Via header 5(24) ERROR: tm [t_fwd.c:476]: prepare_new_uac(): could not build request 5(24) ERROR: tm [t_fwd.c:1737]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches 5(24) ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: No error (2/SL) Ultimately this means the proxy gets a 500 rather than a 430 flow failed, and the registration sits around in the proxy when it should be removed. Am I missing something obvious to get this behavior? Best, Colin

2 2

Re: [SR-Users] Determining if request is from a local domain
by Shane Harrison 15 Jul '16

15 Jul '16

Hi all, Solved! As is often the case, after working all morning on the problem, after posting I discovered my error. I noticed that I hadn't included in my post the "alias=" command. It was indeed in my script but I had used aws-rcsstg.voip.systems instead of aws-rcsstg.vvoip.systems ! I don't know how many times I have stared at that but I guess you often see what you want to see...... Apologies for wasting your time. Kind regards Shane > -----Original Message----- > From: Shane Harrison > Sent: Wednesday, 13 July 2016 2:48 p.m. > To: 'sr-users(a)lists.sip-router.org' > Subject: Determining if request is from a local domain > > Hi all, > > From previous posts my understanding is that RURI's are matched against > reverse DNS lookup of listen addresses and aliases set via the "alias=" > parameter in the config file (assuming the domain module isn't being used). > However I am having difficulty in getting this to work. From looking at the > code and the log file, it appears to me as if the alias isn't making it into the list > of hosts that is checked against for some reason. > > Kamailio proxy is behind a loadbalancer (Kamailio dispatcher) and proxy is > trying to relay the request because it doesn't recognise it as a local domain. > Any thoughts on where my error is would be appreciated. > > Relevant CFG file section - note that > RCS_LB_PUBLIC_IP:RCS_LB_PUBLIC_PORT is 52.64.xxx.221 :5061 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~~~~~~~~~~ > auto_aliases=yes > > # aliases and listening settings for sipproxy alias="aws-rcsstg.voip.systems" > listen=tcp:10.4.1.62:5060 advertise > RCS_LB_PUBLIC_IP:RCS_LB_PUBLIC_PORT > > > My request is a REGISTER as follows: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > received message > REGISTER call-id b2ed2fdd(a)192.168.148.30 received from 10.4.1.62 raw msg > REGISTER sip:aws-rcsstg.vvoip.systems;transport=tls SIP/2.0 > Via: SIP/2.0/TCP > 52.64.xxx.221:5060;branch=z9hG4bKa691.5fd57c2a783d3a5d7f6f80fcd0c815d > 6.0;i=d91 > Via: SIP/2.0/TLS > 192.168.148.30:5061;received=203.171.46.54;rport=64515;branch=z9hG4bK68 > b886fd00518;keep > From: <sip:+6421608919@aws- > rcsstg.vvoip.systems;transport=tls>;tag=4af7e7d8 > To: <sip:+6421608919@aws-rcsstg.vvoip.systems;transport=tls> > Call-ID: b2ed2fdd(a)192.168.148.30 > CSeq: 1995005270 REGISTER > Max-Forwards: 69 > Contact: > <sip:+6421608919@203.171.46.54:64515;transport=tls>;expires=240;+sip.inst > ance="<urn:uuid:23624e3d-c98e-3b76-9acb-5499202e2f8d>";reg- > id=1;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp- > application.ims.iari.rcs.sm";+g.oma.sip-im;+g.3gpp.iari-ref="urn%3Aurn- > 7%3A3gpp-application.ims.iari.gsma-is";+g.3gpp.cs-voice;+g.3gpp.iari- > ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.iari- > ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.sp";+g.3gpp.icsi- > ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video > User-Agent: FlowTalk-WindowsCommunicator_5.x > P-Access-Network-Info: IEEE-802.3 > Allow: > INVITE,ACK,BYE,CANCEL,REFER,NOTIFY,OPTIONS,PRACK,UPDATE,INFO,MESS > AGE,SUBSCRIBE,PUBLISH > Allow-Events: refer, presence > Supported: 100rel, replaces, timer, gruu, join, histinfo, path > Date: Wed, 13 Jul 2016 00:27:39 GMT > Content-Length: 0 > Path: > <sip:52.64.xxx.221:5060;transport=tcp;lr;received=sip:203.171.46.54:64515%3 > Btransport%3Dtls> > > > Relevant section of the log where if( !uri == me ) is tested: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Jul 13 03:18:06 aws-rcsstg-sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: > ERROR: *** cfgtrace:request_route=[SIPOUT] > c=[//etc/kamailio/kamailio.cfg] l=1052 a=16 n=if Jul 13 03:18:06 aws-rcsstg- > sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> > [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: > 24==9 && [aws-rcsstg.vvoip.systems] == [10.4.1.62] Jul 13 03:18:06 aws- > rcsstg-sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> > [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 > (advertise 5061) matches port 5061 Jul 13 03:18:06 aws-rcsstg-sip-proxy-i- > b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> [socket_info.c:603]: > grep_sock_info(): grep_sock_info - checking advertise if host==us: 24==13 > && [aws-rcsstg.vvoip.systems] == [52.64.xxx.221] Jul 13 03:18:06 aws-rcsstg- > sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> > [forward.c:448]: check_self(): check_self: host != me > > > Kind regards > > Shane Harrison > Senior Software Engineer > > Imagination Technologies NZ Limited > Level 2 > 1 Market Grove > Lower Hutt, 5010 > New Zealand > > PO Box 30-449 > Lower Hutt, 5040 > New Zealand > > Phone: +64 4 890-3681 ext 3361 >

2 1

Re: [SR-Users] kamcmd & route[REMOTE_TEST]
by Daniel-Constantin Mierla 15 Jul '16

15 Jul '16

Hello, On 14/07/16 11:02, Marino Mileti wrote: > > Hi guys, > > > > I've two question regarding rpc command. > > > > Is it possible to "execute" a specific route (for example my > route[REMOTE_TEST]) using a rpc command by kamcmd? > > > > If not exist some other tricks to do this? > you can send a xmlrpc, jsonrpc or just http request to kamailio and it will result is executing a route or event_route inside kamailio.cfg, from where you can execute other sub-routes. See xmlrpc, jsonrpc-s or xhttp modules. Obviously, you can send a sip message with tools like sipsak or sipp from command line and handle it inside request_route to execute what route block you want. Sometimes it may just suit executing a route block periodically -- for that see rtimer module. Cheers, Daniel > > > Another question...regarding uac module... > > When Kamailio starts the UAC module makes a REGISTER according to > database...and periodically refresh this registration. Is it possible > to "force" a refresh with rpc command by kamcmd? > > > > Many thanks! > > > > /Marino Maria Mileti/// > > /marino.mileti(a)alice.it <mailto:marino.mileti@alice.it>/ > > / / > > /cid:006a01cb6b0e$67eecdae$_CDOSYS2.0//Reduce your energy consumption > and keep polar bears on ice!/ > > > > > > ------------------------------------------------------------------------ > Avast logo > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > > Questa e-mail è stata controllata per individuare virus con Avast > antivirus. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Re: [SR-Users] kamcmd & route[REMOTE_TEST]
by SamyGo 14 Jul '16

14 Jul '16

Hi Marino, How do you mean execute a route !? like enable a route for all calls onwards after the RPC command execution ? or for a specific call engage that route ? If this is to enable/disable a particular route for ALL calls based on a RPC command I'd make use of some DB or memcache variable to trigger this route i.e if(redis_cmd("srvN", "GET toggle_route", "r")){ $avp(signal) = $redis(r=>value); if($avp(signal) =~ 'true') { route(REMOTE_TEST); } } I used Redis, you can see if any RPC command can let you modify value of an AVP directly. For your second question check RPC commands uac.reg_refresh <http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.r.uac.reg_r…> . Regards, Sammy On Thu, Jul 14, 2016 at 5:02 AM, Marino Mileti <marino.mileti(a)alice.it> wrote: > Hi guys, > > > > I've two question regarding rpc command. > > > > Is it possible to "execute" a specific route (for example my > route[REMOTE_TEST]) using a rpc command by kamcmd? > > > > If not exist some other tricks to do this? > > > > Another question...regarding uac module... > > When Kamailio starts the UAC module makes a REGISTER according to > database...and periodically refresh this registration. Is it possible to > "force" a refresh with rpc command by kamcmd? > > > > Many thanks! > > > > *Marino Maria Mileti* > > *marino.mileti(a)alice.it <marino.mileti(a)alice.it>* > > > > *[image: cid:006a01cb6b0e$67eecdae$_CDOSYS2.0]**Reduce your energy > consumption and keep polar bears on ice!* > > > > > ------------------------------ > [image: Avast logo] > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > Questa e-mail è stata controllata per individuare virus con Avast > antivirus. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > >

1 0

kamcmd & route[REMOTE_TEST]
by Marino Mileti 14 Jul '16

14 Jul '16

Hi guys, I've two question regarding rpc command. Is it possible to "execute" a specific route (for example my route[REMOTE_TEST]) using a rpc command by kamcmd? If not exist some other tricks to do this? Another question...regarding uac module... When Kamailio starts the UAC module makes a REGISTER according to database...and periodically refresh this registration. Is it possible to "force" a refresh with rpc command by kamcmd? Many thanks! Marino Maria Mileti <mailto:marino.mileti@alice.it> marino.mileti(a)alice.it cid:006a01cb6b0e$67eecdae$_CDOSYS2.0Reduce your energy consumption and keep polar bears on ice! --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus

1 0

Modules How To ?
by Eng Hooda 14 Jul '16

14 Jul '16

Hello All, I just started using kamailio last month , using basic configuration I got from online tutorials I got it to work. Now I need to add functionality like offline messages delivery , searching lead me to msilo module , unfortunately I could not find a detailed tutorial of how to enable it and troubleshoot it's operation. All what I managed to find was the official technical documentation. https://www.kamailio.org/docs/modules/stable/modules/msilo.html It provides a list of parameters which has a default value , with no indication if the declaration of any of them is mandatory if the default values are kept intact. also there is a route code which I do not know if it was mandatory to copy to kamailio.cfg . Not to mention that the configuration file example contains lines that is already similar to what I already have , so which to keep and which to replace ? That was a case to apply to , but general answers (with msilo as an example) that apply to all modules is what I need just to avoid having to ask again if I needed to enable another module. Or may be there is something out there that I need to read first. system details : {(OS:Debian8 i386),(Kamailio4.4 with mySQL , UDP only)} Thank you all in advance. Best Regards, Eng Hooda

2 2

is_direction / $fti / $tti not working possible
by Nathan Angelacos 13 Jul '16

13 Jul '16

I'm missing something obvious here, throwing this out to get a couple extra sets of eyeballs on it. I can't get rr modules is_direction() or the $fti / $tti pv's to work in 4.3.x or 4.4.x Relevant parts of the config: loadmodule "rr.so" modparam ("rr", "enable_full_lr", 1) modparam ("rr", "append_fromtag", 1) ... route { xlog ("L_INFO", "$rm: $fu -> $ru"); record_route (); if (has_totag ()) { xlog ("L_INFO", "Before Loose route: fti: $fti tti: $tti ci: $ci"); if (loose_route ()) { if (is_direction ("downstream")) { xlog ("L_INFO", "in-dialog $rm request from caller to callee"); } else { xlog ("L_INFO", "in-dialog $rm request from callee to caller"); } xlog ("L_INFO", "After Loose route: fti: $fti tti: $tti ci: $ci"); } } if (! t_relay ()) { sl_reply_error (); } } ---- Bob and Alice are hard phones, with kamailio + dbaliases in the middle. Alice calls Bob, then Bob (the callee) sends the BYE ---- Syslog: 01. INVITE: sip:alice@kamailio.org -> sip:bob@kamailio.org:5060 02. Alias lookup returned <sip:bob@biloxi.com> , sending on 03. ACK: sip:alice@kamailio.org -> sip:bob@biloxi.com 04. Before Loose route: fti: 707601862 tti: 45686ADF-10AAEB28 ci: 8744171(a)atlanta.com 05. in-dialog ACK request from caller to callee 06. After Loose route: fti: 707601862 tti: 45686ADF-10AAEB28 ci: 8744171(a)atlanta.com 07. BYE: sip:bob@kamailio.org -> sip:alice@atlanta.com:5066 08. Before Loose route: fti: 45686ADF-10AAEB28 tti: 707601862 ci: 8744171(a)atlanta.com 09. in-dialog BYE request from caller to callee 10. After Loose route: fti: 45686ADF-10AAEB28 tti: 707601862 ci: 8744171(a)atlanta.com Using the above config, is_direction always returns "caller", even when bob is sending the message. Looking at a packet capture: 01. Kamailio Sent: Record-Route: <sip:kamailio.org;lr=on;ftag=707601862> <on the 200 ok from Bob> Kamailio Received: Record-Route: <sip:kamailio.org;lr=on;ftag=707601862> Kamailio Sent: Record-Route: <sip:kamailio.org;lr=on;ftag=707601862> 07. Kamailio Received: Route: <sip:kamailio.org;lr=on;ftag=707601862> Kamailio Sent: Record-Route: <sip:kamailio.org;lr=on;ftag=45686ADF-10AAEB28> I expect $fti to be wrong before the loose_route (line 08); but lines 09 and 10 are wrong. I'm obviously missing something trivial here. Any ideas what I should check next? Thanks!

2 2

Kamailio Enviroment
by Rodrigo Moreira 13 Jul '16

13 Jul '16

Hi, Right, to basic configuration of the P-I-S-CSCF services just I call the CFGS appropriate example (directory) for each entity to achieve basic funcionality. What exactly dispacher? How to config it? Regards. -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

2 1

Kamailio know which Interface Packet would route out
by SamyGo 13 Jul '16

13 Jul '16

Hi, Question: Is there a function in kamailio to get the interface/listen IP kamailio would use to route a packet out for a domain / ip ? Example: $avp(interface_ip) = find_interface_for_request("192.168.12.123"); And it gives me the Kamailio's Listen address that would be used for sending call out to this IP/Domain ! I've a weird situation where a multi-homed kamailio with about 7 different interfaces needs to send call out, I've so many RTProxy instances to engage but I can't decide which instance to engage since I do not know which Interface the Packet would route out from. Regards, Sammy

2 2

Re: [SR-Users] shm_malloc
by Daniel-Constantin Mierla 13 Jul '16

13 Jul '16

Hello, Can you be more explicit about what do you expect? Daniel On 13/07/16 07:27, Prakash wrote: > > Hello Daniel, > > > > Many thanks for the response. > > Could you please provide me the behind scenes of shm_malloc()?. > > It will be very helpful for me to segregate without any flaws. > > > > > > Thanks, > > Prakash > > > > *From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On > Behalf Of *Daniel-Constantin Mierla > *Sent:* Tuesday, July 12, 2016 6:34 PM > *To:* Kamailio (SER) - Users Mailing List > *Subject:* Re: [SR-Users] shm_malloc > > > > Hello, > > I don't expect to be very hard to extract the shm management code from > kamailio. It is inside the subfolder mem/ . > > Then, there should be some dependecies that you need to get out from > the core, coming in my mind is locking (mutexes). Maybe atomic > operations (not remembering by heart if some counters are kept for > memory management) and few other bits. > > It should work without crash, you just need to get it initialized as > kamailio does it in it's main function. > > Cheers, > Daniel > > On 12/07/16 13:57, Prakash wrote: > > Hello, > > > > Is it possible to take out shared memory code from kamailio? > > if so ,Will it work without any crash? > > > > > _______________________________________________ > > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > > sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> > > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > Daniel-Constantin Mierla > http://www.asipto.com - http://www.kamailio.org > http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda -- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

2 1

access to tls X509v3 Subject Alternative Name
by Juha Heinanen 13 Jul '16

13 Jul '16

Is there some means to get access to local and peer ssl certificate X509v3 Subject Alternative Name value? For example, if there is this in certificate: Subject: CN=foo.bar.com X509v3 Subject Alternative Name: DNS:foo.bar.com, DNS:foo.car.com, DNS:car.com $tls_my_san_hostname produces only foo.bar.com. -- Juha

2 5

Re: [SR-Users] shm_malloc
by Daniel-Constantin Mierla 13 Jul '16

13 Jul '16

Hello, I don't expect to be very hard to extract the shm management code from kamailio. It is inside the subfolder mem/ . Then, there should be some dependecies that you need to get out from the core, coming in my mind is locking (mutexes). Maybe atomic operations (not remembering by heart if some counters are kept for memory management) and few other bits. It should work without crash, you just need to get it initialized as kamailio does it in it's main function. Cheers, Daniel On 12/07/16 13:57, Prakash wrote: > > Hello, > > > > Is it possible to take out shared memory code from kamailio? > > if so ,Will it work without any crash? > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

2 1

Determining if request is from a local domain
by Shane Harrison 13 Jul '16

13 Jul '16

Hi all, >From previous posts my understanding is that RURI's are matched against reverse DNS lookup of listen addresses and aliases set via the "alias=" parameter in the config file (assuming the domain module isn't being used). However I am having difficulty in getting this to work. From looking at the code and the log file, it appears to me as if the alias isn't making it into the list of hosts that is checked against for some reason. Kamailio proxy is behind a loadbalancer (Kamailio dispatcher) and proxy is trying to relay the request because it doesn't recognise it as a local domain. Any thoughts on where my error is would be appreciated. Relevant CFG file section - note that RCS_LB_PUBLIC_IP:RCS_LB_PUBLIC_PORT is 52.64.xxx.221 :5061 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ auto_aliases=yes # aliases and listening settings for sipproxy alias="aws-rcsstg.voip.systems" listen=tcp:10.4.1.62:5060 advertise RCS_LB_PUBLIC_IP:RCS_LB_PUBLIC_PORT My request is a REGISTER as follows: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ received message REGISTER call-id b2ed2fdd(a)192.168.148.30 received from 10.4.1.62 raw msg REGISTER sip:aws-rcsstg.vvoip.systems;transport=tls SIP/2.0 Via: SIP/2.0/TCP 52.64.xxx.221:5060;branch=z9hG4bKa691.5fd57c2a783d3a5d7f6f80fcd0c815d6.0;i=d91 Via: SIP/2.0/TLS 192.168.148.30:5061;received=203.171.46.54;rport=64515;branch=z9hG4bK68b886fd00518;keep From: <sip:+6421608919@aws-rcsstg.vvoip.systems;transport=tls>;tag=4af7e7d8 To: <sip:+6421608919@aws-rcsstg.vvoip.systems;transport=tls> Call-ID: b2ed2fdd(a)192.168.148.30 CSeq: 1995005270 REGISTER Max-Forwards: 69 Contact: <sip:+6421608919@203.171.46.54:64515;transport=tls>;expires=240;+sip.instance="<urn:uuid:23624e3d-c98e-3b76-9acb-5499202e2f8d>";reg-id=1;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.sm";+g.oma.sip-im;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-is";+g.3gpp.cs-voice;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.sp";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video User-Agent: FlowTalk-WindowsCommunicator_5.x P-Access-Network-Info: IEEE-802.3 Allow: INVITE,ACK,BYE,CANCEL,REFER,NOTIFY,OPTIONS,PRACK,UPDATE,INFO,MESSAGE,SUBSCRIBE,PUBLISH Allow-Events: refer, presence Supported: 100rel, replaces, timer, gruu, join, histinfo, path Date: Wed, 13 Jul 2016 00:27:39 GMT Content-Length: 0 Path: <sip:52.64.xxx.221:5060;transport=tcp;lr;received=sip:203.171.46.54:64515%3Btransport%3Dtls> Relevant section of the log where if( !uri == me ) is tested: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jul 13 03:18:06 aws-rcsstg-sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: ERROR: *** cfgtrace:request_route=[SIPOUT] c=[//etc/kamailio/kamailio.cfg] l=1052 a=16 n=if Jul 13 03:18:06 aws-rcsstg-sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 24==9 && [aws-rcsstg.vvoip.systems] == [10.4.1.62] Jul 13 03:18:06 aws-rcsstg-sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 5061) matches port 5061 Jul 13 03:18:06 aws-rcsstg-sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> [socket_info.c:603]: grep_sock_info(): grep_sock_info - checking advertise if host==us: 24==13 && [aws-rcsstg.vvoip.systems] == [52.64.xxx.221] Jul 13 03:18:06 aws-rcsstg-sip-proxy-i-b879b469 /usr/sbin/kamailio[9367]: DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me Kind regards Shane Harrison Senior Software Engineer Imagination Technologies NZ Limited Level 2 1 Market Grove Lower Hutt, 5010 New Zealand PO Box 30-449 Lower Hutt, 5040 New Zealand Phone: +64 4 890-3681 ext 3361

1 0

Detect 200 OK for ReINVITE
by Grant Bagdasarian 12 Jul '16

12 Jul '16

Hi, Is it possible in Kamailio, or SIP in general, to detect if a 200 OK is for a ReINVITE? Regards, Grant

4 5

Video conferencing with Kamailio
by Jay Li 12 Jul '16

12 Jul '16

Dear All, I'm curious if anybody has set up an infrastructure for video conferencing utilizing Kamailio as a proxy (like NAT support and so so). I found a kind of old tutorial "Run you own Skype-like service in less than one hour" kamailio:skype-like-service-in-less-than-one-hour [Asipto - SIP and VoIP Knowledge Base Site] written in 2013 on Kamailio 3.1. I wonder if this feature has been further developed in later releases. I know Kamailio is more often used as a SIP proxy, but somehow I got the impression that Kamailio supports WebRTC, so I wonder if it's possible to implement a many to many video conferencing infrastructure using Kamailio. If the answer is yes, how's the performance or the bottleneck I should pay more attention to (maybe bandwidth for video traffic, especially with NAT? ) Anyway I'm a newbie to both Kamailio and video conference, so any suggestion/discussion is appreciated. Thanks. Regards,Jay

2 3

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