- sr-users - kamailio.org

DNSSRV to resolve to multiple Kamailio servers
by Derek Bolichowski 24 Feb '16

24 Feb '16

Hello, I'm trying to create a DNSSRV record that resolves to multiple Kamailio servers for my clients to authenticate against. Before using Kamailio, we had a DNSSRV record setup that resolved to our multiple Asterisk servers via their WAN Address. I've tried to do the same with Kamailio, but not having much luck. The DNSSRV record is setup as follows, as you can see from the output of a `dig` query: ;_sip._udp.kam.some-domain.com. IN SRV ;; ANSWER SECTION: _sip._udp.kam.some-domain.com. 14399 IN SRV 20 100 5060 kam1.some-domain.com. _sip._udp.kam.some-domain.com. 14399 IN SRV 10 100 5060 kam2.some-domain.com. I am not able to register any devices to this SRV record. However I /CAN/ register directly to kam1.some-domain.com and kam2.some-domain.com Registration attempts to the DNSSRV Record (kam.some-domain.com) do not even appear in /var/log/messages. We have the domain name for kam (SRV Record), kam1 and kam2 setup in kamailio.domain and kamailio.dispatcher. What am I missing here? Thank you for taking the time to read this! Derek Bolichowski

3 2

getting error on kamailio with homer configurations
by Achintha 24 Feb '16

24 Feb '16

hi , we configured homer with kamailio sip capture (server-A) then i try configured another kamailio with siptrace (server-B) mysql database configured with "homer_data" DB i try to call to the second kamailio server using sip phone but didn't get data on homer ui then I find an error on kamailio server configured with homer (server-B) as follows, 5(18128) ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table 'homer_data.sip_capture_call_20160223' doesn't exist (1146) 5(18128) ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query kindly help me to solve this -- Thanking you Achintha

2 2

Issue with Double Record Route
by Alberto Sagredo 24 Feb '16

24 Feb '16

Im fancing some issues due to kamailio behind nat and thought double record route could help me . But enabling that : modparam("rr", "enable_double_rr", 1) And later using record_route_advertised_address("X.X.X.X:5060"); is giving me this error: w_record_route_advertised_address(): Double attempt to record-route Off course, only a single Record Route is present.. What am i doing wrong? Using Kamailio 4.3.4

2 5

catching lost websocket ua
by Juha Heinanen 23 Feb '16

23 Feb '16

when a ua that has registered over tcp has lost its connection to sip proxy, t_relay() succeeds and branch failure route is executed: Feb 21 05:07:26 lohi /usr/bin/sip-proxy[20528]: INFO: ********** entering branch_route [CONTACT_BRANCH] Feb 21 05:07:26 lohi /usr/bin/sip-proxy[20528]: INFO: ********** activating t_on_branch_failure("contact)" Feb 21 05:07:26 lohi /usr/bin/sip-proxy[20528]: INFO: Routing INVITE <sip:jh-0x16737a0@192.98.102.10:44186;transport=tcp> to contact via <sip:192.98.102.10:51297;transport=tcp> Feb 21 05:07:26 lohi /usr/bin/sip-proxy[20528]: WARNING: tm [t_fwd.c:1543]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Feb 21 05:07:26 lohi /usr/bin/sip-proxy[20528]: INFO: ********* t_relay success Feb 21 05:07:31 lohi /usr/bin/sip-proxy[20480]: INFO: ********** entering tm:branch-failure:contact but when a ua that has registered over websocket over tcp has lost is connection to sip proxy, t_relay() fails and branch failure route is not executed: Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: INFO: ********** entering branch_route [CONTACT_BRANCH] Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: INFO: ********** activating t_on_branch_failure("contact)" Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: INFO: Routing INVITE <sip:an41pa6p@ggjdptrk9jm0.invalid;transport=ws> to contact via <sip:192.98.102.10:39057;transport=ws> Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: WARNING: <core> [msg_translator.c:2756]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: ERROR: <core> [msg_translator.c:1974]: build_req_buf_from_sip_req(): could not create Via header Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: ERROR: tm [t_fwd.c:462]: prepare_new_uac(): could not build request Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: ERROR: tm [t_fwd.c:1712]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Feb 21 05:08:26 lohi /usr/bin/sip-proxy[20523]: INFO: ********* t_relay failure in the latter case, is there some means to get access to the failing branch in order to be able to unregister it, delete its rtpengine session, etc? why can't kamailio behave the same way no matter if pure tcp connection or one using websocket protocol over tcp connection fails? -- juha

2 2

PUBLISH request receives 404 response, and loops on loopback interface
by Matthew Harrold 23 Feb '16

23 Feb '16

Hi all, I am new to Kamailio but have previous experience with Asterisk, Freeswitch and SIP. I am using a fairly default config file with some sections removed (E.G NAT) to simplify things, and some extra logging so I can see the way packets traverse the configuration. Config here - http://pastebin.com/raw/CCgT0C78 I have noticed that when a UAC sends a PUBLISH request, Kamailio immediately responds '404 Not Found' and more worryingly the logs and a packet capture running on the lo interface indicate it's sending the PUBLISH request to itself in a loop until it hits the Max-Forwards limit. Publish URI is PUBLISH sip:201@kamailio.marrold.co.uk;transport=UDP SIP/2.0 I have two questions, 1) Why is this request being sent a 404, when the UAC is in the USRLOC table? 2) Why is the request looping until Max Forwards is exhausted? Any help appreciated, Marrold

3 5

Re: [SR-Users] Kamailio Cluster
by Arsen Hovhanissian 23 Feb '16

23 Feb '16

Sorry forgot to specify (in-memory) not using the DB, I feel like using the DB for such a task would be such a drag on it

2 1

Installation issues
by Ed Todd 23 Feb '16

23 Feb '16

I tried installing the pre-compiled version of 4.3 under Debian and had all sorts of problems. I found there were 2 sets of paths involved in documentation/procedures plus a reference to a 3rd which caused a complete failure when the directory referred to was missing. I ran into more problems when I tried to access my server from outside my network (static IP). So I thought I’d bite the bullet and install from source. I get to the bit where I am creating the database and even more errors: a.. cannot connect to local mysql server b.. kamdbctl.mysql 112: unary operator expected In one part of the procedure it refers to db_mysql and another to mysql. Is there a simple installation guide around anywhere which will help me get around all these problems? All I want is a Debian with KAMAILIO running on it!

2 1

Re: [SR-Users] Kamailio Cluster
by Arsen Hovhanissian 23 Feb '16

23 Feb '16

Since this thread is open, I wanted to ask, is it possible to replicate dialog data over to multiple nodes as well?

1 0

avp's are not available on default onreply_route ?
by Uri Shacked 22 Feb '16

22 Feb '16

before route[relay] i set $avp(x)="test" on the managed onreply_route i can use $avp(x). on the default onreply_route it is not available. meaning <null>. is that how it suppose to work? it makes it difficult to block a certain 200ok, like i meant to, on the issue - "how to drop 200ok and survive?" thanks, uri

2 2

sip_trace vs uac_reg
by James Cloos 22 Feb '16

22 Feb '16

I've started adding sip_trace to my kamailios, and mostly have it working, but cannot figure out how to capture the outgoing calls from uac_reg. I had to add: reply_route { sip_trace(); } onsend_route { sip_trace(); } to capture those packets. What *_route {} does uac_reg target for its outgoing packets? I read uac_reg.[ch], and see that it uses the t_request method from tm's struct tm_binds. And that the methods are defined via a call to load_tm_api(), and that t_request defaults to the request() function in tm/uac.c. But I don't see from that which route chunk it uses. -JimC -- James Cloos <cloos(a)jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6

3 3

Upgrade 4.0 to 4.3
by Daniel W. Graham 22 Feb '16

22 Feb '16

I'm looking to upgrade a system from 4.0 to 4.3 I see the various upgrade docs https://www.kamailio.org/wiki/install/upgrade/4.0.x-to-4.1.0 https://www.kamailio.org/wiki/install/upgrade/4.1.x-to-4.2.0 https://www.kamailio.org/wiki/install/upgrade/4.2.x-to-4.3.0 If the updates are completed as shown in the docs, can I jump directly to 4.3? Anything to look out for? Thanks! -dan

3 4

Unable to use json module
by Sunil More 22 Feb '16

22 Feb '16

Hello All, I am getting the below error , when ever i try to use json.so module for kamailio. I have compiled and installed with json.so however this error occurs. 0(20153) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/local/kamailio//lib64/kamailio/modules/json.so>: /usr/local/kamailio//lib64/kamailio/modules/json.so: undefined symbol: is_error 0(20153) : <core> [cfg.y:3365]: yyerror_at(): parse error in config file /usr/local/kamailio/etc/kamailio/cc_kamailio/basic.cfg, line 69, column 12-20: failed to load module ERROR: bad config file (1 errors) The kamailio version I am using is : version: kamailio 4.4.0-pre0 (x86_64/linux) 4e7573 Please let me know, how can i proceed here. Thanking You, Sunil More Ph : 9503338275

2 3

db_cluster.so module and kamctlrc DBHOST= field
by Derek Bolichowski 22 Feb '16

22 Feb '16

Hi there, New user to Kamailio here. We currently have it up and running in a virtualized environment with 1 Kamailio sever, 1 Asterisk server and 1 MySQL server. I'm currently writing install scripts to make deploying new nodes/servers easy and to keep settings the same across the board. I've chosed to load the db_cluster.so module in kamailio.cfg, as we will have 2x MySQL servers in master-master replication which will contain the 'kamailio' and 'asterisk' tables. I've just hit a stumbling block - in `kamctlrc`, there is a field called `DBHOST=`. How can I reference my cluster here? In kamailio.cfg, I simply define DBURL as "cluster//<clustername>". What is the syntax for 'DBHOST=' in 'kamctlrc'? Can I reference the cluster? Can I have 2 separate DBHOST= lines? Looking for some guidance on this one. Thanks, Derek B.

2 2

Unable to start kamailio
by sgy 21 Feb '16

21 Feb '16

Hi, Today I download the source codes in version 4.3 by git, and compile and install it. I configure the kamctlrc and kamailio.cfg, but I can't start it, Please refer to following error. Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Table 'kamailio.version' doesn't exist (1146) Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: <core> [db.c:397]: db_table_version(): error in db_query Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: <core> [db.c:436]: db_check_table_version(): querying version for table location Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: usrloc [dlist.c:642]: register_udomain(): error during table version check. Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: registrar [reg_mod.c:561]: domain_fixup(): failed to register domain Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/etc/kamailio//kamailio.cfg:647 Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/etc/kamailio//kamailio.cfg:649 Feb 21 21:47:36 ubuntu /usr/local/sbin/kamailio[13672]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized -- Best Regards, Shengy

2 2

Re: [SR-Users] [SPAM]Re: Registration Failure - IMS
by Franz Edler 21 Feb '16

21 Feb '16

Hi Cristina, > But I have another problem related to registration process. After REGISTER- > 401 Unauthorized-REGISTER-200 OK, the IMS client sends the SUBSCRIBE > message (for the "reg" event package subscription) to the S-CSCF, the latter > replies with NOTIFY and the client correctly responds with 200 OK. In order to > be notified on any change of registration state for the client, also the P-CSCF > sends the SUBSCRIBE message to the S-CSCF, the S-CSCF sends a NOTIFY to > the proxy but, instead of replying with 200 OK, the P-CSCF replies with 404- > Not Here (like it doesn't recognize that the recipient of the NOTIFY in the > Req-URI is the P-CSCF itself). > > Have you ever seen similar issue? I have now spent some time to reproduce the issue. First of all: I had to adapt module reg_mod.c in ims_registrar_pcscf, because it containes a hardcoded P-CSCF address: str pcscf_uri = str_init("sip:pcscf.ims.smilecoms.com:4060"); which is only valid for smilecoms. Did you also change that? Then I got exactly the same problem. I found that the P-CSCF config causes in the part "# Check for Subsequent requests:" a reject " sl_send_reply("404","Not here");" I have doubts that this is correctly designed and have to dig deeper into the logic of the config-file. Fact is: the NOTIFY request does not contain a Route header and as it not an ACK it goes straight to the reject. Maybe any IMS expert can shed some light on this code as shown below: # Check for Subsequent requests: if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if ($route_uri =~ "sip:mo@.*") { setflag(FLT_MO); } if(!isdsturiset()) { handle_ruri_alias(); } # RTP-Relay, if necessary route(RTPPROXY); t_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 here"); } exit; BR Franz

1 0

Make SIP session between two kamailio servers
by Cockhootec Yahrabee 21 Feb '16

21 Feb '16

Hi everyone, I am curious if there is a way to make SIP session between two kamailio server instances eg. if there is way to use kamailio as an SIP client and SIP server at the same time. I am thinking about the following configuration: kamailio main server ----- kamailio server B ----- SIP client B1 | | | kamailio server A ----- SIP client A2 | | | SIP client A1 I want to be able to make SIP session between: SIP client A1 : SIP client A2 kamailio server A : kamailio server B SIP client A1 : SIP client B1 (this would be great) If there is currently no way to do this do you think that it would be possible to create the module which will support this kind of functionality? Thanks in advance for the replies

2 4

How long will be client online in kamailio server since client is forcely closed
by sgy 21 Feb '16

21 Feb '16

Hi All, If the client is forcely closed, the client will be shown as online state in kamailio when I run the command: "kamctl online". How long will be the client online since client is closed? Thank you. -- Best Regards, Shengy

2 2

Re: [SR-Users] [SPAM]Re: Registration Failure - IMS
by Franz Edler 20 Feb '16

20 Feb '16

Hello Cristina, > In the attach you can find the trace of the registration. I have checked your tracefile and confirm: that is a problem which needs further debugging. Up to now I did not activate "WITH_REGINFO" in my installation, therefore I cannot compare. If I find time (this weekend) I will do that and come back with the findings. BR Franz

1 0

rfc: kamailio.cfg polishing for v4.4
by Daniel-Constantin Mierla 20 Feb '16

20 Feb '16

Hello, wondering if people feel it is need to polish the current default kamailio.cfg, to prepare the version for next major release. It can be browsed online at: - https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg It is mainly about very common scenarios that are encountered out there and we should deal with by default. Have in mind that there are the basic and advanced versions of kamailio.cfg in the etc folder. Also, I am looking for tunings for core parameters and module parameters that make the config more suitable for common use case. Speaking of those extra config files, I think the kamailio-advanced.cfg and kamailio-basic.cfg should be deployed in shared doc folder, not being active configs upon default installation. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 3

BUG: qm_free: freeing already freed pointer
by Rene Montilva 19 Feb '16

19 Feb '16

Hi list i've got this bug report in kamailio 4.3 at syslog, then it frozen, i checked my config file looking for htable parameter, and i notice i have htable param without autexpire is this reason why kamailio crash? "/usr/sbin/kamailio[24113]: : <core> [mem/q_malloc.c:453]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7f673dead5d8), called from tm: h_table.c: free_cell(133), first free tm: h_table.c: free_cell(133) - aborting " -- Ing. Rene Montilva *FOSS Developer and VoIP Engineer.*

2 5

Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 19 Feb '16

19 Feb '16

Yes, there is a append_hf("Remote-Party-ID: below is the complete section: # Send to Asterisk route[TOASTERISK] { ds_mark_dst("P"); if(!ds_select_dst("1", "4")) { sl_send_reply("500", "Service Unavailable"); xlog("L_INFO","[$fU@$si:$sp]{$rm} No destinations available for $rd \n"); exit; } # Replace FROM header to Kamailio's address # http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_repla… uac_replace_from("","sip:$sel(cfg_get.kamailio.bind_external_domain):5060"); # rewrite Destinatin URI #$du= $au + "@10.1.4.22:5060"; # Add Remote-Party-ID to header append_hf("Remote-Party-ID: \"$au\" <sip:$au@ $sel(cfg_get.kamailio.bindip_external)>;party=calling;privacy=off;screen=no"); xlog("L_INFO","route[TOASTERISK]: [$fU@$si:$sp]{$rm} From Outside World to Asterisk Box $du\n"); rtpproxy_manage("cawei"); route(RELAY); exit; } Regards Subject: Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found Message-ID: <56B79AFD.8010505(a)gmail.com> Content-Type: text/plain; charset="windows-1252" Hello, do you have an action like: append_hf("Remote-Party-ID: ..."); in kamailio.cfg? Can you paste all that action here? Cheers, Daniel

2 2

Registration Failure
by Cristina Caridi 19 Feb '16

19 Feb '16

Hello, I'm a new starter of Kamailio (SER). I am using the version 4.4.0-dev6 in a Debian machine. I've configured all the IMS network elements, the FHoSS and also Boghe IMS/RCS client in a Windows machine. When an IMS user belonging to my network tries to register and IP SEC mechanism is enabled, the registration flow stops at 401 Unauthorized from S-CSCF -> I-CSCF -> P-CSCF -> client. The problem is that the HSS in MAA message does not send the SIP-Auth-Data-item that should be cointain the Confidentiality Key and the Integrity Key; so the client is not able to challenge the S-CSCF sending another REGISTER message. Do you have any suggestions about this? When IP SEC is disabled (by managing client options), the registration works well. Maybe is there any configuration at HSS level that i'm not considering? Thank you in advance for your help, Cristina

4 7

ACC Module
by Alberto Sagredo 19 Feb '16

19 Feb '16

I have a strange behaviour when configuring ACC module to put CDRs It must be as simple as this: modparam("acc", "cdr_enable", 1) But got this error: feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: acc [acc_mod.c:604]: mod_init(): failed to init cdr generation feb 19 09:26:14 kamailio /usr/local/sbin/kamailio[23712]: ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module acc (/usr/local/lib64/kamailio/modules/acc.so) I have read documentation and seems ok. Tables in databases are created and ALTER commands applied. IM getting actually ACC registers on acc table, but could not active cdrs for acc. What am i missing?

1 2

dispatcher flag
by alexandre.anconetti＠orange.com 19 Feb '16

19 Feb '16

Hi, I'm using the dispatcher module with Kamailio 4.3.4, the keep alive mechanism and the routing are OK, but I would like to get in my request_route the flag(s) (active, inactive, probing ...) that the dispatcher give to each destination. I know that in command line I can run kamcmd or kamctl to get : NRSETS: 1 RECORDS: { SET: { ID: 1 TARGETS: { DEST: { URI: sip: xxx.xxx.xxx.xxx:xxxx FLAGS: IP PRIORITY: 0 } DEST: { URI: sip:xxx.xxx.xxx.xxx:xxxx FLAGS: AP PRIORITY: 0 How can I get that in the request_route process ? Any suggestion would be appreciated ;) Best Regards, Alexandre. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 3

LCR Module issue
by Alberto Sagredo 18 Feb '16

18 Feb '16

Hi I have LCR working but not able to add more gateways? It seems only first one is accepted What could be wrong? I show you database data and kamcmd commands output. mysql> select * from lcr_rule_target; +----+--------+---------+-------+----------+--------+ | id | lcr_id | rule_id | gw_id | priority | weight | +----+--------+---------+-------+----------+--------+ | 1 | 1 | 1 | 1 | 1 | 1 | | 2 | 1 | 2 | 1 | 1 | 1 | | 3 | 2 | 2 | 2 | 1 | 1 | +----+--------+---------+-------+----------+--------+ 3 rows in set (0.00 sec) mysql> select * from lcr_rule; +----+--------+-----------+----------+-------------+---------+---------+ | id | lcr_id | prefix | from_uri | request_uri | stopper | enabled | +----+--------+-----------+----------+-------------+---------+---------+ | 1 | 1 | 6 | NULL | NULL | 1 | 1 | | 2 | 1 | DIDNUMBER | NULL | NULL | 1 | 1 | | 3 | 2 | DIDNUMBER | NULL | NULL | 1 | 1 | +----+--------+-----------+----------+-------------+---------+---------+ 3 rows in set (0.00 sec) mysql> select * from lcr_gw; +----+--------+----------------+--------------+----------+------+--------+------------+-----------+-------+--------+------+-------+---------+ | id | lcr_id | gw_name | ip_addr | hostname | port | params | uri_scheme | transport | strip | prefix | tag | flags | defunct | +----+--------+----------------+--------------+----------+------+--------+------------+-----------+-------+--------+------+-------+---------+ | 1 | 1 | Carrier_Prueba | 172.x.x.x | NULL | 5060 | NULL | 1 | 1 | 0 | NULL | NULL | 1 | NULL | | 5 | 2 | Proveedor_1 | 172.x.x.x | NULL | 5060 | NULL | 1 | 1 | 0 | NULL | NULL | 0 | NULL | +----+--------+----------------+--------------+----------+------+--------+------------+-----------+-------+--------+------+-------+---------+ 2 rows in set (0.00 sec) mysql> root@kamailio:~# kamcmd lcr.reload root@kamailio:~# kamcmd lcr.dump_rules { lcr_id: 1 rule_id: 2 prefix: DIDNUMBER from_uri: request_uri: stopper: 1 } { gw_index: 1 priority: 1 weight: 1 } { lcr_id: 1 rule_id: 1 prefix: 6 from_uri: request_uri: stopper: 1 } { gw_index: 1 priority: 1 weight: 1 } 9 1 root@kamailio:~# kamcmd lcr.dump_gws { lcr_id: 1 gw_id: 1 gw_index: 1 gw_name: Carrier_Prueba scheme: sip: ip_addr: 172.x.x.x hostname: port: 5060 params: transport: ;transport=udp strip: 0 prefix: tag: flags: 1 state: 0 defunct_until: 0

2 2

Questions
by francisco rodriguez 18 Feb '16

18 Feb '16

Hi; Today I'm trying to use my users and include unregistered, there is a problem, this was solved soon or do. I appreciate your attention and cooperation Francisco Rodriguez

2 1

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 17 Feb '16

17 Feb '16

Hi Franz, Thanks for your response. Even we observed in Wireshark traces, no username is included in REGISTER request. Any changes required? No, we are not using NATURAL in our platform. Observed there is no communication between PCSCF – ICSCF while registration and also attaching the tracefile(tcpdump) using command “tcpdump -i any -s 3000 -w /var/tmp/trace_OpenIMS.pcap not port 22 and not port 3306”. Please suggest me if I have missed anything. Regards, Sainath From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Tuesday, February 9, 2016 1:01 PM To: Sainath Ellendula (NEP) <sainath.ellendula(a)wipro.com> Cc: basitstar(a)hotmail.com; sr-users(a)lists.sip-router.org Subject: AW: RE: Re:[SR-Users] Kamailio IMS deployment The REGISTER request is OK. There is no username included in REGISTER request. Regarding the mismatch: do you use NATURAL on your platform? Next step should be a tracefile (tcpdump) and later a debug-log from the node which shows the problem. Von Samsung-Tablet gesendet -------- Ursprüngliche Nachricht -------- Von: sainath.ellendula(a)wipro.com<mailto:sainath.ellendula@wipro.com> Datum: 2016.02.09 08:05 (GMT+01:00) An: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at> Cc: basitstar(a)hotmail.com<mailto:basitstar@hotmail.com>, sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> Betreff: RE: Re:[SR-Users] Kamailio IMS deployment Hi Franz, Please find ping status and seems good. root@server:~# ping -c 1 hss.net1.test PING hss.net1.test (10.0.0.9) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.9): icmp_seq=1 ttl=64 time=0.017 ms --- hss.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# ping -c 1 pcscf.net1.test PING pcscf.net1.test (10.0.0.10) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.10): icmp_seq=1 ttl=64 time=0.020 ms --- pcscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.020/0.020/0.020/0.000 ms root@server:~# ping -c 1 icscf.net1.test PING icscf.net1.test (10.0.0.11) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.11): icmp_seq=1 ttl=64 time=0.018 ms --- icscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.018/0.018/0.018/0.000 ms root@server:~# ping -c 1 scscf.net1.test PING scscf.net1.test (10.0.0.12) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.12): icmp_seq=1 ttl=64 time=0.017 ms --- scscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# Seems Some progress happened: Tried register using Boghe IMS client and observed few errors: 0(1445) INFO: <script>: [REGISTER] from [sip:alice@net1.test] to [sip:alice@net1.test] 0(1445) ERROR: <script>: REGISTER (sip:alice@net1.test (10.0.0.8:55280) to sip:alice@net1.test, 2006cdca-0076-bacb-5010-bffa714b3cdb) 0(1445) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <7994> <REGISTER> 0(1445) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 0(1445) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 0(1445) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 0(1445) DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: <core> [select.c:412]: run_select(): Calling SELECT 0x7fb548dd2400 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=1 T start=0xffffffffffffffff 0(1445) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=65064, isACK=0 0(1445) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed 0(1445) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found 0(1445) DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil) 0(1445) DEBUG: sl [sl.c:280]: send_reply(): reply in stateless mode (sl) 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T start=(nil) 0(1445) DEBUG: tm [t_lookup.c:1086]: t_check_msg(): DEBUG: t_check_msg: T previously sought and not found 0(1445) DEBUG: ims_registrar_pcscf [save.c:273]: save_pending(): contact requesting to expire in 600000 seconds 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:155]: get_hash_slot(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:159]: get_hash_slot(): Returning hash slot: [167] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): Searching for contact in P-CSCF usrloc [sip:alice@10.0.0.8:55280;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:183]: get_aor_hash(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): Returning hash slot: [1662767783] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:483]: get_pcontact(): Comparing needle user@host:port [alice@10.0.0.8:55280] and contact_user@contact_host:port [alice@10.0.0.8:51219] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:494]: get_pcontact(): Searching for [sip:alice@10.0.0.8:55280;transport=udp] and comparing to [sip:alice@10.0.0.8:51219;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:553]: get_pcontact(): Port don't match: 51219 (contact) 51219 (received) != 55280! 0(1445) DEBUG: ims_registrar_pcscf [save.c:310]: save_pending(): Adding pending pcontact: <sip:alice@10.0.0.8:55280;transport=udp> 0(1445) DEBUG: ims_usrloc_pcscf [pcontact.c:132]: new_pcontact(): New contact [<sip:alice@10.0.0.8:55280;transport=udp>] with 0 associated IMPUs in state: [registration pending] 0(1445) DEBUG: ims_registrar_pcscf [save.c:314]: save_pending(): registering for UL callback 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param Please guide me for any more changes has to be done, As observed in Wireshark(Register request from 10.0.0.8(host)-PCSCF as REGISTER sip:net1.test SIP/2.0). I think the register request should sent as REGISTER sip:alice@net1.test SIP/2.0 Thanks in advance!! Regards, Sainath From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Tuesday, February 9, 2016 3:00 AM To: Sainath Ellendula (NEP) <sainath.ellendula(a)wipro.com<mailto:sainath.ellendula@wipro.com>> Cc: basitstar(a)hotmail.com<mailto:basitstar@hotmail.com>; sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> Subject: RE: Re:[SR-Users] Kamailio IMS deployment Sainath, what was the result for ping on - icsct.net1.test - scscf.net1.test - hss.net1.test to increase debug level you have to modify the corresponding cfg-file, e.g. kamailio-icscf.cfg in line 35: debug=2 Just increase to debug=3 and then start the process again. BR Franz The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

3 8

[TOPOH] Contact header for 302 Moved Temporarily
by SamyGo 17 Feb '16

17 Feb '16

Hi All, I've recently stumbled upon this little hitch while using kamailio with topoh module that the Contact header do not contains the User part for the 302 Moved temporarily packet. *My topology:* UserA<====\ ->Kamailio<===>FreeSwitch UserB<====/ The B party has set Call forwarding on their phone hence phone sends a 302 Moved Temporarily to Kamailio. Via: SIP/2.0/UDP TOPOH.KAMAILIO.IP:5060;branch=z9hG4bK0767.4e4e57deca89da5c5f5ae97228325f85.0 Via: SIP/2.0/UDP TOPOH.KAMAILIO.IP;branch=z9hG4bKsr-j4IPOlV7MGQKatycM.y7MGZLMGZwM.1LgRWIC9gIgx4fMGZAOBVAOBNfzuaVHRaYpB1LNSQLpx4uMx3Az6eL3RsBCxu-zRrUWSeOgjeBk.IVm4ds34aONc** From: "+4319714111" <sip:+4319714111@FREESWITCH.IP.HERE>;tag=yUr5UZ7eF794K To: <sip:502@USER.B.IP.HERE:5060>;tag=105223296 Call-ID: cd811276-4b4d-1234-66ae-005056867dbc CSeq: 87257355 INVITE Contact: <sip:06606017597@FREESWITCH.IP.HERE:5060> User-Agent: Yealink SIP-T46G 28.80.0.70 Diversion: <sip:502@USER.B.IP.HERE:5060>;reason=unconditional Content-Length: 0 This is modified in Kamailio TOPOH and sent to FreeSwitch as following SIP/2.0 302 Moved Temporarily Via: SIP/2.0/UDP 10.0.20.71;received=10.0.20.71;rport=5060;branch=z9hG4bKeBcy9HKK9cDKr From: "+4319714111" <sip:+4319714111@FREESWITCH.IP.HERE>;tag=yUr5UZ7eF794K To: <sip:502@USER.B.IP.HERE:5060>;tag=105223296 Call-ID: cd811276-4b4d-1234-66ae-005056867dbc CSeq: 87257355 INVITE Contact: <*sip:TOPOH.KAMAILIO.IP* ;line=sr-N6IAzBy6WBy6MxFwW.qwPSW5ohWINhaYNLu4g9W4OhWI3wKLgRsIpUg5kGs7g9P-W.y6My**> User-Agent: Yealink SIP-T46G 28.80.0.70 Diversion: <sip:502@USER.B.IP.HERE:5060>;reason=unconditional Content-Length: 0 Which results in a Call Originate from FreeSwitch with RURI as this: INVITE *sip:TOPOH.KAMAILIO.IP*;line=sr-N6IAzBy6WBy6MxFwW.qwPSW5ohWINhaYNLu4g9W4OhWI3wKLgRsIpUg5kGs7g9P-W.y6My** SIP/2.0 I am thinking that in TOPOH Module some patch is required to atleast retain the $rU for 3XX replies , not sure if this will break some RFC or Kamailio stability etc ! Thanks, Sammy.

3 4

siptrace module plain sip mode
by Grant Bagdasarian 17 Feb '16

17 Feb '16

Hello, The documentation of the siptrace module specifies duplication of sip messages to a capture server using the HEP protocol or plain SIP mode. Which params to I need to set (and with which values) in the siptrace and sipcapture to enable plain SIP mode? I tried several configurations but none of the worked. Seems like only HEP works. My test kamailio (sip capture node with sipcapture module) doesn't receive the duplicated SIP messages. Any ideas? Regards, Grant

2 2

Installatioin issues
by Ed Todd 17 Feb '16

17 Feb '16

I am installing KAMAILIO under DEBIAN. I have got it to work fine (TLS) until I upgraded my Comcast to business service to get static IP’s. Now it no longer works. I am using the Cisco DPC3941 modem/router and am tring to connect an IPhone on WIFI to the PC SIP server on the LAN. Here are the log entries: Feb 16 19:14:59 SIP-Server kamailio[2010]: NOTICE: <core> [main.c:738]: handle_sigs(): Thank you for flying kamailio!!! Feb 16 19:14:59 SIP-Server kamailio[2019]: INFO: <core> [main.c:849]: sig_usr(): signal 15 received Feb 16 20:01:25 SIP-Server kamailio: INFO: tls [tls_init.c:385]: init_tls_compression(): tls: init_tls: disabling compression... Feb 16 20:01:26 SIP-Server kamailio: INFO: <core> [tcp_main.c:4745]: init_tcp(): using epoll_lt as the io watch method (auto detected) Feb 16 20:01:26 SIP-Server kamailio[3876]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Feb 16 20:01:26 SIP-Server kamailio[3876]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Feb 16 20:01:26 SIP-Server kamailio[3876]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Feb 16 20:01:26 SIP-Server kamailio[3876]: ERROR: ctl [init_socks.c:126]: init_unix_sock(): ERROR: init_unix_sock: bind: No such file or directory [2] Feb 16 20:01:26 SIP-Server kamailio[3876]: ERROR: ctl [ctl.c:283]: mod_init(): ERROR: ctl: mod_init: init ctrl. sockets failed Feb 16 20:01:26 SIP-Server kamailio[3876]: ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module ctl (/usr/lib/x86_64-linux-gnu/kamailio/modules/ctl.so) I am informed that SIP-ALG is disabled. Any ideas?

2 1

Remove_hf_is not working
by aman jeff 17 Feb '16

17 Feb '16

Hi , I am working kamailio 4.4.0 ,i want to remove my Contact header completely.So I used remove_hf..but its now working ..Let me know the solution Am very thankful to you Regards Jefff

2 1

db_cluster.so module and kamctlrc DBHOST= field
by Hosted Services 16 Feb '16

16 Feb '16

Hi there, New user to Kamailio here. We currently have it up and running in a virtualized environment with 1 Kamailio sever, 1 Asterisk server and 1 MySQL server. I'm currently writing install scripts to make deploying new nodes/servers easy and to keep settings the same across the board. I've chosed to load the db_cluster.so module in kamailio.cfg, as we will have 2x MySQL servers in master-master replication which will contain the 'kamailio' and 'asterisk' tables. I've just hit a stumbling block - in `kamctlrc`, there is a field called `DBHOST=`. How can I reference my cluster here? In kamailio.cfg, I simply define DBURL as "cluster//<clustername>". What is the syntax for 'DBHOST=' in 'kamctlrc'? Can I reference the cluster? Can I have 2 separate DBHOST= lines? Looking for some guidance on this one. Thanks, Derek B.

2 1

Database Insert
by Daniel W. Graham 16 Feb '16

16 Feb '16

I see there is a new SQLops function sql_query_async that has been added in 4.2 (I believe?). Is there a good way to perform database insert using version 4.0? Using mysql Thanks! -dan

2 4

Need to validate a IP address with subnet mask
by Sunil More 16 Feb '16

16 Feb '16

Hi All, I want to validate a IP address in kamailio for requests coming from different IPs. I have browsed and found permissions module, however is there a way where i can directly compare a source IP address to an address stored in an avp and get a true or false value. something like this $si==192.168.2.0/24 Thanking You, Sunil More

3 7

Textops and Multipart Body - adding ISUP
by Sergey Basov 16 Feb '16

16 Feb '16

Hi All. I need to use SIP-I with my upstream to set A number as unknown. I was read about adding incapsulation ISUP using if(has_body("application/sdp")) { set_body_multipart(); msg_apply_changes() $var(acm) = "7e Od 04 55 75 69 20 4d 61 6b 65 43 61 6c 6c"; append_body_part("$var(acm)","application/isup;version=itu-t92+","signal; handling=optional"); msg_apply_changes() xlog("L_INFO", "ISUP Changes Applied Succesfully"); } It is converts body to multipart and inserts ISUP But it inserts is as text. Is there any possibility to insert basic ISUP message to update it after using sipt_destination($rU, 31, 4); and sipt_set_calling($fU, 4, 0, 3); Thank you. -- Best regards, Sergey Basov e-mail: sergey.v.basov(a)gmail.com

3 10

kamailio 4 with asterisk
by Sébastien Brice 15 Feb '16

15 Feb '16

this one (written by Daniel) http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb maybe a bit outdated but still consistent ? the thing i am really stuck with (and concerning real-time) is that none of my extensions (from asterisk CLI) are online: ns3325046*CLI> sip show peers Name/username Host Dyn Forcerport Comedia ACL Port Status Description Realtime 102/102 (Unspecified) D Auto (No) No 0 Unmonitored Cached RT 103/103 (Unspecified) D Auto (No) No 0 Unmonitored Cached RT 2 sip peers [Monitored: 0 online, 0 offline Unmonitored: 0 online, 2 offline] that drives asterisk crazy ! and logger reports: app_dial.c:2411 dial_exec_full: Unable to create channel of type 'SIP' (cause 20 - Subscriber absent) every time i place a call. The tutorial written by daniel mention a channel configuration pretty minimal: INSERT INTO sipusers (name, defaultuser, host, sippasswd, fromuser, fromdomain, mailbox) VALUES ('102', '102', 'dynamic', '102', '102', 'yoursip.com', '102'); and since there's no context associated to the 102 extension i cant figure out where that channel enter the dialplan ? [public] [LocalSet] [default] ???? and a dialplan exten => _1XX,1,Dial(SIP/${EXTEN}) exten => _1XX,n,Voicemail(${EXTEN},u) exten => _1XX,n,Hangup exten => _1XX,101,Voicemail(${EXTEN},b) exten => _1XX,102,Hangup i am sorry to bother you with issues more asterisk oriented than kamailio. By the way i took a good start with kamailio as it seems to work flawlessly on my system. thx you. On Mon, Feb 15, 2016 at 12:26:06PM +0100, Sébastien Brice wrote: > Hi Everyone, i like the way this tutorial explain asterisk and kamailio integration. Which tutorial? > the only thing i missed is asterisk behaviors'r regarding sip registration ? That was a part of a tutorial I once saw. In essence asterisk uses the kamailio database, UA registers on kamailio and is stored there, asterisk sees the same data (realtime). Sébastien BRICE VoIP, Support et Intégration

2 1

no pkg memory left
by Gholamreza Sabery 15 Feb '16

15 Feb '16

Hello. I am seeing the following error repeating again and again in the log file: /sbin/kamailio[14510]: ERROR: registrar [reply.c:199]: build_contact(): no pkg memory left I am using 64MB of SHM memory and 8MB of PKG memory. What is the reason for this error? How to solve it?

2 2

kamailio 4 with asterisk
by Sébastien Brice 15 Feb '16

15 Feb '16

Hi Everyone, i like the way this tutorial explain asterisk and kamailio integration. the only thing i missed is asterisk behaviors'r regarding sip registration ? I tryed to place a call between 102 and 103 extensions and experimenting an issue Asterisk tells me that the subscriber is absent and I'm sent directly to voicemail ! -- Executing [103@public:1] Dial("SIP/102-00000001", "SIP/103") in new stack [Feb 14 21:00:15] WARNING[19444][C-00000001]: app_dial.c:2411 dial_exec_full: Unable to create channel of type 'SIP' (cause 20 - Subscriber absent) ns3325046*CLI> sip show peers Name/username Host Dyn Forcerport Comedia ACL Port Status Description Realtime 102/102 (Unspecified) D Auto (No) No 0 Unmonitored Cached RT 103/103 (Unspecified) D Auto (No) No 0 Unmonitored Cached RT 2 sip peers [Monitored: 0 online, 0 offline Unmonitored: 0 online, 2 offline] apart that my sip.conf and extensions.conf are very minimal: [LocalSets] exten => _1XX,1,Dial(SIP/${EXTEN}) exten => _1XX,n,Voicemail(${EXTEN},u) exten => _1XX,n,Hangup exten => _1XX,102,Voicemail(${EXTEN},b) exten => _1XX,103,Hangup [general] context=LocalSets ; Default context for incoming calls. Defaults to 'default' rtcachefriends=yes ; Cache realtime friends by adding them to the internal list i did INSERT TO the users in mysql tables (sipusers, sipregs and voicemail) and registering extensions from UA works ok (i am using jitsi) Whats wrong with my setup ? thank you

2 1

kamctl add VS kamctl ul add under SIPML
by kssyrr 15 Feb '16

15 Feb '16

2 3

uac module configuration
by Andrew Tan 15 Feb '16

15 Feb '16

Hello, Submit a ticket in GitHub apologize about that I should have sent my question here. I would like some help in configuring the uac module to route to an gateway without specifically setting the URI-domain from the UAC. I would like to set change it in the Kamailio side. Currently I use uac_auth on failure route. All is working if I set the URI from on the client to xxx(a)gatewayaddress.com. But if I just dial just the number as is which translate to xxx(a)kamailioserver.com the invite doesnt go anywhere. My failure route is like so failure_route[MANAGE_FAILURE] { xlog("DEBUG: MANAGE FAILURE ROUTE: "); if ($T_reply_code == "407") # there's also 401 { $avp(arealm) = GATEWAY; $avp(auser) = USERNAME; $avp(apass) = PASSWORD; #$ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ":" + $sel(cfg_get.pstn.gw_port); #rewritehost("sip.ca.didlogic.net"); uac_auth(); rtpengine_offer("force trust-address replace-origin replace-session-connection ICE=remove RTP/AVP"); route(NATMANAGE); route(RELAY); exit; } } Thank you

2 1

LCR
by Alexey V. Panfilov 15 Feb '16

15 Feb '16

Hello, I'm using LCR module in my kamailio setup. I can access to the gw_uri_avp's value of matched gateway, but I'd like to get value of selected id of lcr_rule_target. Is there any way to get it? Thanks. P.S. Access to value of custom table's field (for example, named as 'flags') of cr_rule_target will be better. I'd like to store at this field the price of selected direction. -- Best regards, Alexey V. Panfilov

2 4

Kamailio 4 && Asterisk. Getting started
by Sébastien Brice 14 Feb '16

14 Feb '16

Hi everyone I did follow the tutorial Kamailio 4.0.x and asterisk written by Daniel-C and I need a hand :-) after a successful install (kamailio and asterisk on the same server), i did setup 2 sip extensions (102 and 103) and tryed to place a call between them and experimenting an issue Asterisk tells me that the subscriber is absent and I'm sent directly to voicemail ! -- Executing [103@public:1] Dial("SIP/101-00000001", "SIP/103") in new stack [Feb 14 21:00:15] WARNING[19444][C-00000001]: app_dial.c:2411 dial_exec_full: Unable to create channel of type 'SIP' (cause 20 - Subscriber absent) ns3325046*CLI> sip show peers Name/username Host Dyn Forcerport Comedia ACL Port Status Description Realtime 102/102 (Unspecified) D Auto (No) No 0 Unmonitored Cached RT 103/103 (Unspecified) D Auto (No) No 0 Unmonitored Cached RT 2 sip peers [Monitored: 0 online, 0 offline Unmonitored: 0 online, 2 offline] Actually none of my extensions are online and i am wondering if Kamailio forward register with asterisk ? transport between K and Asterisk seems ok (at least i did setup bindport in both sip.conf and kamailio.cfg) apart that my sip.conf and extensions.conf are very minimal: exten => _1XX,1,Dial(SIP/${EXTEN}) exten => _1XX,n,Voicemail(${EXTEN},u) exten => _1XX,n,Hangup exten => _1XX,102,Voicemail(${EXTEN},b) exten => _1XX,103,Hangup [general] context=LocalSets ; Default context for incoming calls. Defaults to 'default' rtcachefriends=yes ; Cache realtime friends by adding them to the internal list I am a bit new with Kamailio and I don't know if this behavior is normal since i have a sipregs mysql table that could do the job on purpose? Could someone point me to the right direction and enlight my knowing, thanks you thx you

1 0

Kamailio and freeswitch integration for SBC
by malik sherif 12 Feb '16

12 Feb '16

Hello, I was able to have successful call with kamailio and after integrating kamailio with freeswitch using the following link, the invite timeout and as a result the call failed.The status on kamailio show these info. Do I need to download outbound model? I am running kamailio ver 4.1.1 and freeswitch 1.4.18. kamailio[19153]: 0(19162) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob kamailio[19153]: 0(19162) INFO: rr [rr_mod.c:159]: mod_init(): outbound module not available http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc Thank you very much and your help is appreciated. Thanks Abdul <http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> [http://kb.asipto.com/_media/wiki:logo.png]<http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc [Asipto ...<http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> kb.asipto.com The scope of this tutorial is to show how you can use Kamailio (former OpenSER) and FreeSWITCH to build a complete SIP/VoIP platform for large number of subscribers.

4 45

BLF on different IPs/domains
by Phil Lavin 12 Feb '16

12 Feb '16

Hi all, A different BLF query to my other one so creating another thread. We've tried to have a BLF client SUBSCRIBE using a secondary IP on Kamailio. It is not sent a NOTIFY, but a client which has done a SUBSCRIBE using the primary IP is. If we route the problematic client such that it connects to the primary IP, it too is sent a NOTIFY. Looking at the query that is done on the database when a call is made to 441164969988 it is as follows: select `callid`,`to_tag`,`from_tag` from `active_watchers` where `presentity_uri`='sip:441164969988@185.28.212.118' AND `event`='dialog' Where 185.28.212.118 is the primary IP. In reality, it should be doing an additional query for anything considered `myself`. i.e. select `callid`,`to_tag`,`from_tag` from `active_watchers` where `presentity_uri`='sip:441164969988@10.20.11.118' AND `event`='dialog' I've been scouring the docs for a way to add additional IPs and/or domains for the purpose of querying active_watchers but I can't see anything relevant. What's the process here? Thanks Phil

2 3

kamailio xmpp gateway configuration issue
by kevin hifx 12 Feb '16

12 Feb '16

Dear friends, I am facing an issue, when trying to configure xmpp gateway between kamailio and ejabbred xmpp server. I have followed the steps mention in this web site: http://www.kamailio.org/docs/modules/4.1.x/modules/xmpp.html The kamailio service is running but in the log file it show that xmpp connection failed. "*Feb 5 11:32:33 sip-xmpp-server /usr/sbin/kamailio[646]: ERROR: xmpp [network.c:122]: net_connect(): connect() failed: Connection refused* " (Both kamailio and ejabbred installed on the same server in local network and have local DNS server) I have added following entries in the kamailio configuration file. I am only mentioning the xmpp section. " ####### Global Parameters ######### alias=sip-xmpp.kevin.org ####### Modules Section ######## #!ifdef WITH_MYSQL loadmodule "db_mysql.so" #!endif loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.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 "cfg_rpc.so" loadmodule "mi_rpc.so" loadmodule "acc.so" # XMPP loadmodule "xmpp.so" # ----------------- setting module-specific parameters --------------- modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo") modparam("rr", "enable_full_lr", 1) # XMPP modparam("xmpp", "domain_separator", "*") modparam("xmpp", "gateway_domain", "sip-xmpp.kevin.org") modparam("xmpp", "xmpp_domain", "xmpp-sip.kevin.org") modparam("xmpp", "xmpp_host", "xmpp.kevin.org") ###############XMPP # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; ### absorb retransmissions ### if (!t_newtran()) { sl_reply_error(); return; } if (method == "MESSAGE") { log("*** xmpp-handled MESSAGE message.\n"); if (xmpp_send_message()) { t_reply("200", "Accepted"); } else { t_reply("404", "Not found"); } return; } log("*** xmpp: unhandled message type\n"); t_reply("503", "Service unavailable"); return; ############### " could you please help me solve this issue. Thank you kevin

2 5

Only Cassandra, Possible?
by Barış Şekerciler 12 Feb '16

12 Feb '16

Hello, I want to use only Cassandra DB for Kamailio. Is this possible? If it yes, how can I do that? For example, if I replace the DBENGINE as DB_CASSANDRA can I use it like this? Thank you. Regards.

2 3

Kamailio TLS
by Kethzer Docteur 12 Feb '16

12 Feb '16

Im trying to enable Kamailio TLS but the configuration is not running at all when I cahnge it liike this as follow. Kamailio 3.3 ubuntu 12.04 LTS #!define WITH_TLS #!ifdef WITH_TLS enable_tls=yes #!endif #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") #!endif Please help -- Kethzer Docteur

4 3

Negative return codes from functions
by Phil Lavin 11 Feb '16

11 Feb '16

Hi all, Just a sanity check, really. Does Kamailio consider negative response codes to be false? For example, should the following log execute? if (!foo()) { # Returns -2 x_log("Foo is false"); } The reason for asking here is that I'm implementing flood protection using pike, based off the kamailio.cfg that ships with v4.3. The logic is thus: if (!pike_check_req()) { # Do blocking } However pike_check_req only returns -1 or -2 in the case of failure, never 0. The blocking code is, thus, never executed. Changing to explicitly check for != 1 works correctly. Am I missing something here or is the example kamailio.cfg incorrect? Cheers

2 3

Kamailio 4.2.6 crash
by Igor Potjevlesch 11 Feb '16

11 Feb '16

Hello, I have seen couple of crashes since yesterday. I copy/paste the last "bt full": Program terminated with signal 11, Segmentation fault. #0 0x0000000000619694 in fm_extract_free (qm=0x7fcdf8780000, frag=0x7fcdf8a62c78) at mem/f_malloc.c:206 206 *pf= (gdb) bt full #0 0x0000000000619694 in fm_extract_free (qm=0x7fcdf8780000, frag=0x7fcdf8a62c78) at mem/f_malloc.c:206 pf = 0x6576203b50555349 hash = 2097 #1 0x000000000061ad68 in fm_malloc (qm=0x7fcdf8780000, size=1104, file=0x7fce0f081a7b "tm: t_msgbuilder.c", func=0x7fce0f0860a0 "build_local_reparse", line=369) at mem/f_malloc.c:490 f = 0x7fcdf8780b08 frag = 0x7fcdf8a62c78 hash = 156 __FUNCTION__ = "fm_malloc" #2 0x00007fce0f011fa9 in _shm_malloc (size=1099, file=0x7fce0f081a7b "tm: t_msgbuilder.c", function=0x7fce0f0860a0 "build_local_reparse", line=369) at ../../mem/shm_mem.h:208 p = 0x6 #3 0x00007fce0f01920e in build_local_reparse (Trans=0x7fcdf8a5e2f0, branch=0, len=0x7fff00c32fbc, method=0x7fce0f087a25 "ACK", method_len=3, to=0x7fff00c32d90, reason=0x0) at t_msgbuilder.c:369 invite_buf = 0x7fcdf8a62868 "INVITE sip:<CALLED>@goren SIP/2.0\r\nRecord-Route: <sip:A.B.C5.60;lr;did=5b1.3112>\r\nCSeq: 1 INVITE\r\nCall-ID: 3da8-469-1111201513435-JANGO-1-A.B.C_leg2\r\nFrom: <sip:<CALLING>@<HOST_FROM>>;"... invite_buf_end = 0x7fcdf8a62c70 "" cancel_buf = 0x415440 "1\355I\211\321^H\211\342H\203\344\360PTI\307\300\300\363m" s = 0x7fcdf8a62868 "INVITE sip:<CALLED>@goren SIP/2.0\r\nRecord-Route: <sip:A.B.C5.60;lr;did=5b1.3112>\r\nCSeq: 1 INVITE\r\nCall-ID: 3da8-469-1111201513435-JANGO-1-A.B.C_leg2\r\nFrom: <sip:<CALLING>@<HOST_FROM>>;"... s1 = 0x0 d = 0x10703ab0 <Address 0x10703ab0 out of bounds> invite_len = 1032 hf_type = 2540 first_via = 0 to_len = 67 cancel_buf_len = 1099 reason_len = 0 code_len = 0 reas1 = 0x0 reas_last = 0x0 hdr = 0xa7294e __FUNCTION__ = "build_local_reparse" #4 0x00007fce0f02e58b in build_ack (rpl=0x7fce107038b8, trans=0x7fcdf8a5e2f0, branch=0, ret_len=0x7fff00c32fbc) at t_reply.c:439 to = {s = 0xa728f6 "To: <sip:+<CALLED>@A.B.C5.60:5060>;tag=3658827875-928685\r\nContent-Length: 0\r\n\r\n", len = 67} __FUNCTION__ = "build_ack" #5 0x00007fce0f03b3ca in reply_received (p_msg=0x7fce107038b8) at t_reply.c:2253 msg_status = 488 last_uac_status = 100 ack = 0x7fce10588010 "\001" ack_len = 0 branch = 0 reply_status = 274235864 onreply_route = 1 cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 10955086}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 10955086}}}} uac = 0x7fcdf8a5e458 t = 0x7fcdf8a5e2f0 lack_dst = {send_sock = 0x13a948, to = {s = {sa_family = 10306, sa_data = "\247\000\000\000\000\000(\r\030\000\000\000\000"}, sin = {sin_family = 10306, sin_port = 167, sin_addr = {s_addr = 0}, sin_zero = "(\r\030\000\000\000\000"}, sin6 = {sin6_family = 10306, sin6_port = 167, sin6_flowinfo = 0, sin6_addr = { __in6_u = {__u6_addr8 = "(\r\030\000\000\000\000\000\270|^\020\316\177\000", __u6_addr16 = {3368, 24, 0, 0, 31928, 4190, 32718, 0}, __u6_addr32 = {1576232, 0, 274627768, 32718}}}, sin6_scope_id = 93}}, id = 0, proto = -72 '\270', send_flags = {f = 106 'j', blst_imask = 94 '^'}} backup_user_from = 0x758a50 backup_user_to = 0x415440 backup_domain_from = 0x300c337e0 backup_domain_to = 0x0 backup_uri_from = 0x7fce10703ab0 backup_uri_to = 0x7fff00c330d0 backup_xavps = 0x628478 replies_locked = 0 branch_ret = 0 prev_branch = 275790040 blst_503_timeout = 32718 hf = 0x18e00c33060 onsend_params = {req = 0x7fff00c32f50, rpl = 0x47deb8, param = 0x0, code = 274623280, flags = 32718, branch = 0, t_rbuf = 0xa7294e, dst = 0xa727e1, send_buf = { s = 0x7fff00c33010 "\320\060", <incomplete sequence \303>, len = 6402299}} ctx = {rec_lev = 7715456, run_flags = 0, last_retcode = 7704068, jmp_env = {{__jmpbuf = {232, 140523014225936, 140523014226728, 140523014618240, 29, 0, 140523015781040, 4281408}, __mask_was_saved = 12793824, __saved_mask = {__val = {0, 140733206179856, 6439748, 140733206179616, 140523001001690, 140733206179584, 0, 67108864, 65537912, 1288288, 1570952, 1576232, 8, 94, 0, 1473240891392}}}}} __FUNCTION__ = "reply_received" #6 0x000000000048cc3a in do_forward_reply (msg=0x7fce107038b8, mode=0) at forward.c:783 new_buf = 0x0 dst = {send_sock = 0x0, to = {s = {sa_family = 0, sa_data = '\000' <repeats 13 times>}, sin = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = 0}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 0, sin6_port = 0, sin6_flowinfo = 0, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, id = 0, proto = 0 '\000', send_flags = {f = 0 '\000', blst_imask = 0 '\000'}} new_len = 1 r = 0 ip = {af = 12792240, len = 32767, u = {addrl = {6466393, 280}, addr32 = {6466393, 0, 280, 0}, addr16 = {43865, 98, 0, 0, 280, 0, 0, 0}, addr = "Y\253b\000\000\000\000\000\030\001\000\000\000\000\000"}} s = 0x410004 "" len = 0 __FUNCTION__ = "do_forward_reply" #7 0x000000000048e27d in forward_reply (msg=0x7fce107038b8) at forward.c:885 ---Type <return> to continue, or q <return> to quit--- No locals. #8 0x0000000000509c9c in receive_msg ( buf=0xa727c0 "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"..., len=398, rcv_info=0x7fff00c333b0) at receive.c:275 msg = 0x7fce107038b8 ctx = {rec_lev = 10237056, run_flags = 0, last_retcode = 0, jmp_env = {{__jmpbuf = {0, 0, 0, 272136986608, 1812476198913, 0, 272145363728, 272145384176}, __mask_was_saved = 0, __saved_mask = {__val = {140523014366192, 140733206180688, 1, 140522613671152, 272137013029, 50195, 1024, 4307759872, 140522613671152, 140733206180608, 6299381, 140733206180896, 140522613671152, 81, 6299509, 140733206180976}}}}} ret = 12792656 inb = { s = 0xa727c0 "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"..., len = 398} __FUNCTION__ = "receive_msg" #9 0x0000000000608f02 in udp_rcv_loop () at udp_server.c:521 len = 398 buf = "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"... tmp = 0x3f60c4067a <Address 0x3f60c4067a out of bounds> from = 0x7fce105e7920 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {151524537, 0}, addr32 = {151524537, 0, 0, 0}, addr16 = {5305, 2312, 0, 0, 0, 0, 0, 0}, addr = "\271\024\b\t", '\000' <repeats 11 times>}}, dst_ip = {af = 2, len = 4, u = {addrl = {1016190299, 0}, addr32 = {1016190299, 0, 0, 0}, addr16 = {54619, 15505, 0, 0, 0, 0, 0, 0}, addr = "[Õ<", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = { s = {sa_family = 2, sa_data = "\023Ä¹\024\b\t\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 151524537}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 151524537, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7fce105aa2b0, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #10 0x00000000004a6d9b in main_loop () at main.c:1629 i = 0 pid = 0 si = 0x7fce105aa2b0 si_desc = "udp receiver child=0 sock=A.B.C5.60:5060\000\177\000\000 5\303\000\377\177\000\000\003zN\000\000\000\000\000\016\b\000\000\377\177\00 0\000\260\204x\370\315\177\000\000\000\000\000\020\004\000\000\000\260\204x\ 370\315\177\000\000@TA\000\000\000\000\000\340\067\303\000\001\000\000\000p5 \303\000\377\177\000\000\246zN\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #11 0x00000000004acedf in main (argc=7, argv=0x7fff00c337e8) at main.c:2581 cfg_stream = 0xac7010 c = -1 r = 0 tmp = 0x7fff00c34f70 "" tmp_len = 32767 port = 12793534 proto = 0 options = 0x6ff8f8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 3913881212 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x40d11c p = 0xc2 <Address 0xc2 out of bounds> __FUNCTION__ = "main" Regards, Igor.

2 15

Reg: REGISTER request don't have username in request line
by sainath.ellendula＠wipro.com 11 Feb '16

11 Feb '16

Hi Team, Working on Kamailio setup with IMS components(P-CSCF, I-CSCF, S-CSCF). Assigned IP's: hss/server-10.0.0.9 P-CSCF-10.0.0.10 I-CSCF-10.0.0.11 S-CSCF-10.0.0.12 Here tried to send an REGISTER request from Boghe IMS client, the register request should go from P-CSCF to I-CSCF, here P-CSCF - I-CSCF communication is not happening but I could able ping. One more thing observed from logs here is REGISTER request don't have username (username is not there in request line), Execution log: 0(1338) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param Please find attachment of Zone file, SCSCF.xml, Diameter.xml, ICSCF.xml and tcpdump. Any changes/suggestions would be very helpful. Regards, Sainath The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 1

Terminate dialogs on [websocket:closed]
by mayamatakeshi 11 Feb '16

11 Feb '16

Hello, I am using module websocket and it works very well. However I would like to send BYE to the other end if event [websocket:closed] happens. >From the docs I can see websocket module itself doesn't provide for this. I was considering doing something like this: - use module htable to match $si:$sp to dialogs - use event_route[dialog:start] to insert dialog info to my htable under $si:$sp of Websocket side of the call - use event_route[dialog:end] to remove dialog info from htable - use event_route[websocket:closed] to iterate over entries in the htable under key $si:$sp and call dlg_get() and dlg_bye(). Obs: in the above, there is a risk of losing some dialogs as insertion in htable cannot be done atomically, but I am fine with it as it it not expected to happen as WebSocket users would only infrequently generate simultaneous calls. However before going with this, I would like to ask for other possible approaches. Regards, Takeshi

2 6

Route for BYE requests
by alexandre.anconetti＠orange.com 11 Feb '16

11 Feb '16

Hello, I would like some advice about a situation i have encountered recently. I'm using Kamailio 4.3.4 as a "proxy" : I have a media server, and to reach this server all the requests have to pass through my Kamailio server. The Kamailio server does not have to handle authentification or registration, all of that stuff is done on the media server. To do that I'm using the following route : route[REDIRECT] { if($rU == "" ) { $ru = ("sip:1.2.3.4:xxxx"); } else { $ru = ("sip:" + $rU + "@1.2.3.4:xxxx"); } } 1.2.3.4 is my media server's address. I have 2 users : an "internal" one registered on the media server, and an "external" one which is a random caller. It works fine for EXT -> Kamailio -> Media server requests but when I try to hang up with my internal user, the "BYE" request uses the following path : Internal user -> Media server -> Kamailio -> Media server instead of : Internal user -> Media server -> Kamailio -> External user. Obviously it is because of the REDIRECT route which send back the "BYE" request to the media server, when it should sends that request to the external user. So, how should I modify that route to do what I want ? Maybe should I create a second route ? Any answer will be appreciated :) Best regards, Alexandre _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

kamctl ul add...<path>
by kssyrr 10 Feb '16

10 Feb '16

1 0

RTCWeb Breaker question
by SamyGo 10 Feb '16

10 Feb '16

Hi All, reference to this link: https://www.kamailio.org/wiki/devel/rtcweb_breaker#scenarios I want to know if the module to communicate with RTCWeb Breaker is available or it was just a proposal and no more under consideration. I have webrtc clients registered to Kamailio but due to lack of (scalable/efficient) transcoding capabilities they can not make video calls to Video IP-Phones. I tried using webrtc2sip from doubango telecom and it actually enabled me to achieve the goal, the problem with that case is webrtc2sip is working with sipml5 client and there is not a big list of WebRTC clients that work with it. If I can achieve the referred rtc_web_breaker architecture then I believe a lot of webRTC clients will be able to integrate with my setup. Thanks, Regards, Sammy

2 4

Kamailio SST and Dialog module workings
by Jason Penton 10 Feb '16

10 Feb '16

Hi Kamailio users and Devs. I am interested to know if any of you are using SST module with DIALOG module and sharing the timeout avp between the two - expecting the call to be torn down if no in-dialog requests are processed. If you are using it, is it working as you expect? To me it seems that the timers in the dialog module will never be updated by any in-dialog requests. I just wanted to check before I start looking at fixing... perhaps I am missing something. Cheers Jason

2 2

Permission module about from_pattern
by Yasin CANER 10 Feb '16

10 Feb '16

2 3

regular expression for fromuser
by Yasin CANER 10 Feb '16

10 Feb '16

1 0

regular expression for from_pattern
by Yasin CANER 10 Feb '16

10 Feb '16

1 0

info: dialog_ng renamed to ims_dialog
by Daniel-Constantin Mierla 09 Feb '16

09 Feb '16

Hello, based on a previous discussion on mailing lists, I just renamed the dialog_ng to ims_dialog in order to reflect better its purpose nowadays (use together with the other ims modules) and avoid confusion that it is something that includes the features of dialog module and some new stuff. Functions and params are not renamed, being anyhow overlapping a lot with dialog module, but they are not intended to be used at the same time. Perhaps some examples still need to be updated (contributions are welcome here if you identify such places). If any other issue is discovered to the ims modules, write here to get it fixed. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

1 0

Re: [SR-Users] Kamailio IMS deployment
by Franz Edler 09 Feb '16

09 Feb '16

The REGISTER request is OK. There is no username included in REGISTER request.Regarding the mismatch: do you use NATURAL on your platform? Next step should be a tracefile (tcpdump) and later a debug-log from the node which shows the problem. Von Samsung-Tablet gesendet-------- Ursprüngliche Nachricht --------Von: sainath.ellendula(a)wipro.com Datum: 2016.02.09 08:05 (GMT+01:00) An: franz.edler(a)technikum-wien.at Cc: basitstar(a)hotmail.com, sr-users(a)lists.sip-router.org Betreff: RE: Re:[SR-Users] Kamailio IMS deployment Hi Franz, Please find ping status and seems good. root@server:~# ping -c 1 hss.net1.test PING hss.net1.test (10.0.0.9) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.9): icmp_seq=1 ttl=64 time=0.017 ms --- hss.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# ping -c 1 pcscf.net1.test PING pcscf.net1.test (10.0.0.10) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.10): icmp_seq=1 ttl=64 time=0.020 ms --- pcscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.020/0.020/0.020/0.000 ms root@server:~# ping -c 1 icscf.net1.test PING icscf.net1.test (10.0.0.11) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.11): icmp_seq=1 ttl=64 time=0.018 ms --- icscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.018/0.018/0.018/0.000 ms root@server:~# ping -c 1 scscf.net1.test PING scscf.net1.test (10.0.0.12) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.12): icmp_seq=1 ttl=64 time=0.017 ms --- scscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# Seems Some progress happened: Tried register using Boghe IMS client and observed few errors: 0(1445) INFO: <script>: [REGISTER] from [sip:alice@net1.test] to [sip:alice@net1.test] 0(1445) ERROR: <script>: REGISTER (sip:alice@net1.test (10.0.0.8:55280) to sip:alice@net1.test, 2006cdca-0076-bacb-5010-bffa714b3cdb) 0(1445) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <7994> <REGISTER> 0(1445) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 0(1445) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 0(1445) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 0(1445) DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: <core> [select.c:412]: run_select(): Calling SELECT 0x7fb548dd2400 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=1 T start=0xffffffffffffffff 0(1445) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=65064, isACK=0 0(1445) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed 0(1445) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found 0(1445) DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil) 0(1445) DEBUG: sl [sl.c:280]: send_reply(): reply in stateless mode (sl) 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T start=(nil) 0(1445) DEBUG: tm [t_lookup.c:1086]: t_check_msg(): DEBUG: t_check_msg: T previously sought and not found 0(1445) DEBUG: ims_registrar_pcscf [save.c:273]: save_pending(): contact requesting to expire in 600000 seconds 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:155]: get_hash_slot(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:159]: get_hash_slot(): Returning hash slot: [167] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): Searching for contact in P-CSCF usrloc [sip:alice@10.0.0.8:55280;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:183]: get_aor_hash(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): Returning hash slot: [1662767783] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:483]: get_pcontact(): Comparing needle user@host:port [alice@10.0.0.8:55280] and contact_user@contact_host:port [alice@10.0.0.8:51219] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:494]: get_pcontact(): Searching for [sip:alice@10.0.0.8:55280;transport=udp] and comparing to [sip:alice@10.0.0.8:51219;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:553]: get_pcontact(): Port don't match: 51219 (contact) 51219 (received) != 55280! 0(1445) DEBUG: ims_registrar_pcscf [save.c:310]: save_pending(): Adding pending pcontact: <sip:alice@10.0.0.8:55280;transport=udp> 0(1445) DEBUG: ims_usrloc_pcscf [pcontact.c:132]: new_pcontact(): New contact [<sip:alice@10.0.0.8:55280;transport=udp>] with 0 associated IMPUs in state: [registration pending] 0(1445) DEBUG: ims_registrar_pcscf [save.c:314]: save_pending(): registering for UL callback 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param Please guide me for any more changes has to be done, As observed in Wireshark(Register request from 10.0.0.8(host)-PCSCF as REGISTER sip:net1.test SIP/2.0). I think the register request should sent as REGISTER sip:alice@net1.test SIP/2.0 Thanks in advance!! Regards, Sainath From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Tuesday, February 9, 2016 3:00 AM To: Sainath Ellendula (NEP) <sainath.ellendula(a)wipro.com> Cc: basitstar(a)hotmail.com; sr-users(a)lists.sip-router.org Subject: RE: Re:[SR-Users] Kamailio IMS deployment Sainath, what was the result for ping on - icsct.net1.test - scscf.net1.test - hss.net1.test to increase debug level you have to modify the corresponding cfg-file, e.g. kamailio-icscf.cfg in line 35: debug=2 Just increase to debug=3 and then start the process again. BR Franz The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

1 0

GCC version in use
by Daniel-Constantin Mierla 09 Feb '16

09 Feb '16

Hello, looking a bit over our makefiles, I am thinking of simplifying some parts related to compiler optimizations, as I noticed some of them are for gcc 2.x. So I would like to see if people are still using old OSes and/or old GCC versions. In other words, if you use old or some dedicated systems and plan to deploy most recent Kamailio versions, reply here with the gcc version in use, particularly interested to see the use of gcc 2.x or 3.x. The idea is not to remove the support for it completely, but to simply and don't try to find all tunings for old versions, but go more with the default gcc options. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 7

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 09 Feb '16

09 Feb '16

Hi Franz, Thank you so much for your response. As suggested modified changes and don't observe connection refused error. After modification few more errors observed. Detailed errors as below. 10.0.0.9 /catalina-optional.jar:lib/catalina.jar:lib/c3p0-0.9.1.jar:lib/base64.jar:lib/asm.jar:lib/asm-attrs.jar:lib/antlr-2.7.6.jar::log4j.properties:.. 2016-02-01 12:09:28,371 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started. 2016-02-01 12:09:29,301 WARN org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9 2016-02-01 12:09:30,294 INFO de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation! 2016-02-01 12:09:31,251 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started ! 2016-02-01 12:09:34,813 WARN org.hibernate.impl.SessionFactoryObjectFactory - addInstance InitialContext did not implement EventContext 2016-02-01 12:09:34,847 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - <init> Bean style constructor called, don't forget to configure! 2016-02-01 12:09:34,851 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure FQDN: hss.net1.test 2016-02-01 12:09:34,852 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Realm: net1.test 2016-02-01 12:09:34,853 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Vendor_ID : 10415 2016-02-01 12:09:34,854 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Product Name: JavaDiameterPeer 2016-02-01 12:09:34,854 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure AcceptUnknwonPeers: true 2016-02-01 12:09:34,855 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure DropUnknownOnDisconnect: true 2016-02-01 12:09:34,864 INFO de.fhg.fokus.hss.main.HSSContainer - waitForExit Type "exit" to stop FHoSS! 2016-02-01 12:09:34,873 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer icscf.net1.test:3869 not responding to connection attempt 2016-02-01 12:09:34,876 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer scscf.net1.test:3870 not responding to connection attempt 10.0.0.10 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(1856) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(1856) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(1856) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(1856) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(1856) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1856) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1856) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing 0(1856) INFO: <script>: [REGISTER] from [sip:alice@net1.test] to [sip:alice@net1.test] 0(1856) ERROR: <script>: REGISTER (sip:alice@net1.test (10.0.0.8:55859) to sip:alice@net1.test, aaeacddd-376e-4a63-5745-2757d1b9a29d) 10.0.0.11 9(1870) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.11 port 3869 9(1870) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.11 port 3869 9(1870) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(1871) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(1871) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(1871) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 8(1869) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(1871) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10.0.0.12 9(1883) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.12 port 3870 9(1883) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.12 port 3870 9(1883) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 7(1881) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(1881) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(1884) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(1884) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(1884) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 8(1882) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(1884) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 Could you please guide me here. Any suggestions would be very helpful. Thanks in advance!! Regards, Sainath -----Original Message----- From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Saturday, January 30, 2016 1:27 PM To: Sainath Ellendula (WT01 - NEP) <sainath.ellendula(a)wipro.com>; basitstar(a)hotmail.com; sr-users(a)lists.sip-router.org Subject: RE: [SR-Users] Kamailio IMS deployment Hi, > As suggested, modified the changes in icscf.xml and scscf.xml files, PFA > modified files. > > Still getting few errors .... Now it seems to be clear to me where the problem might come from: I have restricted access to mysql server to address 10.0.0.9 only. You have to change the bind-address statement in /etc/mysql.cnf accordingly. See: http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_bi… Change the address to "*" or to 0.0.0.0. BR Franz _______________________________________________ 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 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 6

No contact info(0 bindings) in 200-register
by sgy 08 Feb '16

08 Feb '16

Hi Members, I notice an issue: the client register to kamailio server and could receive 200-register message, but no contact infomation(shows 0 bindings) returns in the message(200-register). I checked contact exist in register message and client shows register successfully. When I run command "kamctl online", the client is not online. Could you met with this issue? Expected to your help, thank you very much. Register: REGISTER sip:12.2.1.197 SIP/2.0 Via: SIP/2.0/UDP 12.2.1.180:5060;rport;branch=z9hG4bKPjWScZ6O7MbSbtauTPHcKpjzsHb5U6wxGP Route: <sip:12.2.1.197;lr> Max-Forwards: 70 From: "2016" <sip:2016@12.2.1.197>;tag=jqx1XzTgoS-XKh-S3LyrYmjrCBSqJZ48 To: "2016" <sip:2016@12.2.1.197> Call-ID: AiD6dDi6YOK4.ArBsMpse2MQEoh4dBmP CSeq: 12358 REGISTER User-Agent: A-client Contact: "2016" <sip:2016@12.2.1.180:5060;ob>;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000000020805>";reg-id=0 Supported: geolocation, gruu, path, outbound, answermode, tdialog, replaces, timer, precondition, norefersub Expires: 3600 Allow: INVITE, ACK, BYE, CANCEL, UPDATE, INFO, NOTIFY, REFER, MESSAGE, OPTIONS Authorization: Digest username="2016", realm="12.2.1.197", nonce="Vq8AMFau/wTtkI9/v58I86rqhbvPhSTW", uri="sip:12.2.1.197", response="aebb4a141197b2200bdfc5dce008d9ac" Content-Length: 0 200-Register: //No contact infomation rE/(a)SIP/2.0 200 OK Via: SIP/2.0/UDP 12.2.1.180:5060;rport=5060;branch=z9hG4bKPjpBm-dzHb.9vJY19Ccy9Yz8sx7jigkAM1;received=12.2.1.180 From: "2015" <sip:2015@12.2.1.197>;tag=tVTyij9jGH8wprKa2olsevAockWFs8k0 To: "2015" <sip:2015@12.2.1.197>;tag=090f6aa955fd574e08bca845127013d9.2885 Call-ID: fIQWmPXYtdkT94lzPscrMjzj3R5san9g CSeq: 58932 REGISTER Server: kamailio (4.2.0 (x86_64/linux)) Content-Length: 0 Best Regards, Shengy

2 9

Re: [SR-Users] Replace User Agent
by Daniel-Constantin Mierla 08 Feb '16

08 Feb '16

Hello, for changing the user-agent header you can use: remove_hf("User-Agent"); append_hf("User-Agent: abc\r\n"); Cheers, Daniel On 02/02/16 11:20, Steven Maddox wrote: > Hi, > > I've brought up this topic up before (here and on IRC) and I feel like > I'm getting closer but still a bit stuck. Since it takes a while to > explain the idea (and get past any confusion!) I've summarized it in a > diagram for easier understanding. > > At work my employers have decided to use this god awful hosted PBX > which is picky about which phones can register and checks their user > agent, the hosted PBX is marked on the diagram as the purple blob. > > > > The progress I've made since last time is getting Kamailio 4.2.4 on > that little white device, the *only* purpose of that device is to > change the user agent - nothing more... since it has lots of ports it > could have lots of "Unapproved" phones directly connected to it. > > Someone gave me a link to this as a starting point... > https://blog.voipxswitch.com/2015/03/27/kamailio-basic-sip-proxy-all-reques… > > However I'm not sure what portions of the default kamailio.cfg should > be kept to use this, additionally it doesn't include anything about > changing user agents. > > The normal configuration of an "Approved" phone is *like*... > > username="441234111999" > password="rAnD0Mp4s5" > auth_user="jsmith" > domain="company.co.uk" > registrar/proxy="uk.ic.56hnt.hlpcom.co.uk" > > In terms of the configuration of an "Unapproved" phone I can either... > > 1) Put in exactly the same as above (as though it isn't intending to > contact Kamailio)... but since the phone is directly connected to the > Kamailio device - perhaps Kamailio could watch SIP traffic coming in > on eth1 (even if it isn't addressed to it), alter the user agent and > pass it out through eth0 ? I'm not sure even Kamailio is capable of > this - but it'd be cool if possible. > > 2) Put in exactly the same as above however just change the > registrar/proxy to be the IP of the Kamailio device... Kamailio can > then keep all other configuration the same as it passes it through - > just change the user agent. > > Any thoughts? > > n.b. > 1) Yes changing the user agent definitely does allow you connect, it's > not just a guess - tested it with Asterisk. > 2) No I don't think the hosted PBX supports path extensions - I'd > rather not rely on it supporting undocumented stuff anyway. > > -- > Steven Maddox > > > _______________________________________________ > 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://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

1 0

Users in different domains and multiple domains
by Barış Şekerciler 08 Feb '16

08 Feb '16

Hello everyone! I'm wondering something about Kamailio. Here is the idea: Such and example, I want to give base system which depends on Kamailio to 3 companies in 1 server. So I have 1 Kamailio Server and 4 or 5 Freeswitch server. Thus, I have to set a domain for each company, so total is I need 3 domains. For example a, b, c are users. But they should in the different domains for know which is which. In a word, it should seems like this: a(a)subdomain.domain.com b(a)subdomain.domain.com c(a)subdomain.domain.com a(a)subdomain2.domain.com b(a)subdomain2.domain.com c(a)subdomain2.domain.com or a(a)subdomain.domain2.com b(a)subdomain.domain2.com c(a)subdomain.domain2.com etc... So where can I do this? Remember, Kamailio should in the 1 server and all of domains and users should in this server (I will use Postgres) For more details, you can write. Thank you. Regards.

2 5

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Below is the SIP record captured using NGREP: http://pastebin.com/hUqP56fw Regards

2 1

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Below is the SIP record captured using NGREP Regards U 2016/02/07 20:20:06.054910 90.X.X.68:25189 -> 10.1.4.23:5060 INVITE sip:0031651022945@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. . v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.056642 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.8324. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 INVITE. Proxy-Authenticate: Digest realm="voip.system.com", nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme". Content-Length: 0. . U 2016/02/07 20:20:06.059536 90.X.X.68:25189 -> 10.1.4.23:5060 ACK sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport. To: "003165656565"<sip:003165656565@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.8324. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 ACK. Content-Length: 0. . U 2016/02/07 20:20:06.061317 90.X.X.68:25189 -> 10.1.4.23:5060 INVITE sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. . v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.065526 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Content-Length: 0. . U 2016/02/07 20:20:06.065940 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 INVITE sip:003165656565@voip.system.com SIP/2.0. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>. From: <sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. Remote-Party-ID: "9005" <sip:9005@103.XXX.XXX.23 >;party=calling;privacy=off;screen=no. v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.090448 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.883489 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.883574 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:10.884941 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.885646 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:20.596774 90.X.X.68:25189 -> 10.1.4.23:5060 CANCEL sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 CANCEL. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="b739a517585b9bdcd997b3e3322c3bad",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:20.599102 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 500 cancel error. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com >;tag=79597765d0ff0775a3cc048295d6500c-3fc1. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 CANCEL. Content-Length: 0. . U 2016/02/07 20:20:23.407575 90.X.X.68:25189 -> 10.1.4.23:5060 REGISTER sip:voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-7176c672f55aba4c-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189;rinstance=5a52b9593b8bd582>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 7 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc1l1a3NGs8NrsUIZb+Kyau9v9Q9jUn",uri="sip:voip.system.com ",response="602901348ea359e385f99c5d4261ea5c",algorithm=MD5. Content-Length: 0. . U 2016/02/07 20:20:23.409286 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-7176c672f55aba4c-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.fab9. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 7 REGISTER. WWW-Authenticate: Digest realm="voip.system.com", nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa". Content-Length: 0. . U 2016/02/07 20:20:23.515175 90.X.X.68:25189 -> 10.1.4.23:5060 REGISTER sip:voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189;rinstance=5a52b9593b8bd582>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa",uri="sip:voip.system.com ",response="e7d27803d159526ee124e64e59bcc7d0",algorithm=MD5. Content-Length: 0. . U 2016/02/07 20:20:23.520290 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Contact: <sip:9005@90.X.X.68 :25189;rinstance=5a52b9593b8bd582>;expires=600;received="sip:90.X.X.68:25189". Content-Length: 0. . U 2016/02/07 20:20:23.520546 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Contact: <sip:9005@90.X.X.68 :25189;rinstance=5a52b9593b8bd582>;expires=600;received="sip:90.X.X.68:25189". WWW-Authenticate: Digest realm="voip.gpnsystem.com", nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa", qop="auth". Content-Length: 0. . U 2016/02/07 20:20:24.426155 90.X.X.68:25189 -> 10.1.4.23:5060 SUBSCRIBE sip:9005@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-3f31377b941acf34-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 1 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Event: message-summary. Content-Length: 0. . U 2016/02/07 20:20:24.428409 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-3f31377b941acf34-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 1 SUBSCRIBE. Proxy-Authenticate: Digest realm="voip.system.com", nonce="Vrc3tFa3NoiYOjmQMojfuh3ttECnmpZW". Content-Length: 0. . U 2016/02/07 20:20:24.534158 90.X.X.68:25189 -> 10.1.4.23:5060 SUBSCRIBE sip:9005@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-4b7b5d2b2726d57d-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 2 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3tFa3NoiYOjmQMojfuh3ttECnmpZW",uri="sip:9005@voip.system.com ",response="2d1f53e6973bf2eb878f679add8bebc8",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Event: message-summary. Content-Length: 0. . U 2016/02/07 20:20:24.537592 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 404 No voicemail service. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-4b7b5d2b2726d57d-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.2dea. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 2 SUBSCRIBE. Content-Length: 0. . U 2016/02/07 20:20:25.358979 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 OPTIONS sip:103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bK828d.ce4b9911000000000000000000000000.0. To: <sip:103.XXX.XXX.22:5060>. From: <sip:dispatcher@localhost>;tag=56254dc816783af7c55a1ac0231200e3-6d5c. CSeq: 10 OPTIONS. Call-ID: 4063eaf942a6e19e-12704(a)10.1.4.23. Max-Forwards: 70. Content-Length: 0. . U 2016/02/07 20:20:25.365672 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 404 Not Found. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bK828d.ce4b9911000000000000000000000000.0;received=103.XXX.XXX.23. From: <sip:dispatcher@localhost>;tag=56254dc816783af7c55a1ac0231200e3-6d5c. To: <sip:103.XXX.XXX.22:5060>;tag=as00a791b0. Call-ID: 4063eaf942a6e19e-12704(a)10.1.4.23. CSeq: 10 OPTIONS. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Accept: application/sdp. Content-Length: 0. . U 2016/02/07 20:20:26.250911 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:26.252410 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:26.362474 90.X.X.68:25189 -> 10.1.4.23:5060 ACK sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-8c04097075073c09-1---d8754z-;rport. Max-Forwards: 70. Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 ACK. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.362493 90.X.X.68:25189 -> 10.1.4.23:5060 BYE sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport. Max-Forwards: 70. Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri="sip:003165656565@103.XXX.XXX.22 :5060",response="e3f1d030387f1b10ab21c126b8e8d656",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.365975 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 ACK sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.9327d42091ecb853a5c80ed2dd347040.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-8c04097075073c09-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 ACK. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.367367 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 BYE sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKedff.e74ad188da31f15ff2ec2bcb57878ae2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri="sip:003165656565@103.XXX.XXX.22 :5060",response="e3f1d030387f1b10ab21c126b8e8d656",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.368319 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKedff.e74ad188da31f15ff2ec2bcb57878ae2.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Content-Length: 0. . U 2016/02/07 20:20:26.369422 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Content-Length: 0. . <CAEmfXJ4KeqaPD_7k9pgFJNK3Ny4OsQ5X36M+r=Y6LQ1eYwy0pg(a)mail.gmail.com>

1 0

Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Thanks a lot for the reply, It means a lot to as I am stuck on this issue. I'm not sure if attachment works here or not. I will paste the log in paste bin: http://pastebin.com/0w6a8iTB Regards <CAEmfXJ4KeqaPD_7k9pgFJNK3Ny4OsQ5X36M+r=Y6LQ1eYwy0pg(a)mail.gmail.com>

2 1

Extending the default 1800 seconds of session expiration
by kssyrr 06 Feb '16

06 Feb '16

2 2

why msg_apply_changes() from REQUEST_ROUTE only
by smititelu 05 Feb '16

05 Feb '16

Hello, I don't understand why msg_apply changes() can be called from REQUEST_ROUTE *only*. Can someone explain? Can this be extended to *FAILURE_ROUTES *also? Basically I need to call this from FAILURE_ROUTES in order to avoid double SDP for rtpengine offers. Searching in the mailing list I could see that there could be other means of handling this like keeping and reading the SDP from an avp(write/read_sdp_pv), but I find the above method pretty straightforward. Thanks, Stefan

3 4

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 05 Feb '16

05 Feb '16

Hi We are receiving error on CANCEL request from client that is supposed to be relayed to an Asterisk Server: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found Any help on this is much appreciated. below is the log: Regards Sid 0(6351) DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: 0(6351) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <CANCEL> 0(6351) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:0031XXXXXXXXX@voip03nl.voipsystem.com> 0(6351) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> 0(6351) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d8754z-ff05107e83283f5e-1---d8754z->; state=6 0(6351) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 0(6351) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 0(6351) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 0(6351) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 0(6351) DEBUG: <core> [receive.c:134]: receive_msg(): After parse_msg... 0(6351) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 0(6351) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [59]; uri=[sip:0031XXXXXXXXX@voip03nl.voipsystem.com] 0(6351) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body ["0031XXXXXXXXX"<sip:0031XXXXXXXXX@voip03nl.voipsystem.com> 0(6351) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <CANCEL> 0(6351) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 0(6351) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [receive.c:177]: receive_msg(): preparing to run routing scripts... {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=614 a=5 n=route {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=734 a=25 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: <script>: The IP is : 90.152.66.68 and uri {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=745 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=742 a=25 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: <script>: Match the 0/24 IP -- the message was sent from REGUS OFFICE! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=767 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 12==9 && [90.152.66.68] == [10.1.4.23] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:582]: grep_sock_info(): checking advertise if host==us: 12==22 && [90.152.66.68] == [voip03nl.voipsystem.com] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 12==9 && [90.152.66.68] == [10.1.4.23] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:582]: grep_sock_info(): checking advertise if host==us: 12==22 && [90.152.66.68] == [voip03nl.voipsystem.com] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [forward.c:412]: check_self(): host != me {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=761 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=766 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=761 a=24 n=pike_check_req {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [ip_tree.c:286]: mark_node(): search on branch 90 (top=0x7f24a45a4688) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [ip_tree.c:299]: mark_node(): only first 4 were matched! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [pike_funcs.c:93]: pike_check_req(): src IP [90.152.66.68],node=0x7f24a45a4d78; hits=[0,0],[0,1] node_flags=6 func_flags=0 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [timer.c:46]: remove_from_timer(): 0x7f24a45a4d88 from 0x7f24a4579500(0x7f24a45a4d88,0x7f24a45a4d88) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [timer.c:33]: append_to_timer(): 0x7f24a45a4d88 in 0x7f24a4579500(0x7f24a4579500,0x7f24a4579500) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=782 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=807 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=782 a=25 n=mf_process_maxfwd_header {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: maxfwd [mf_funcs.c:66]: is_maxfwd_present(): max_forwards header not found! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=807 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [REQINIT] (Method is CANCEL) r-uri ( sip:0031XXXXXXXXX@voip03nl.voipsystem.com) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=825 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=811 a=25 n=is_method {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=829 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=825 a=26 n=sanity_check {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=0d61d760 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=617 a=5 n=route {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1104 a=55 n=force_rport {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1149 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1118 a=25 n=nat_uac_test {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1143 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1119 a=25 n=is_method {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1125 a=25 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: <script>: [NATDETECT]: method is CANCEL{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_r oute=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1142 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1132 a=24 n=is_first_hop {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: siputils [sipops.c:159]: w_is_first_hop(): no 2nd via found - first hop {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1138 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [NATDETECT]: (is_first_hop() is true) set_contact_alias() Adds an “;alias=ip~port~transport” parameter to the contact URI{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1139 a=24 n=set_contact_alias {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1146 a=39 n=setflag {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1151 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [NATDETECT]: NATDETECT is done{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1152 a=2 n=return {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=620 a=5 n=route {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=842 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=837 a=24 n=has_totag {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: siputils [checks.c:97]: has_totag(): no totag {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=838 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [WITHINDLG]: Has_totag() is false; Return 1;{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=839 a=2 n=return {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=632 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=625 a=25 n=is_method {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=629 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=627 a=24 n=t_check_trans {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:701]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: searching on hash entry 38426 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:409]: matching_3261(): DEBUG: RFC3261 transaction matched, tid=-d8754z-ff05107e83283f5e-1---d8754z- {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:798]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: canceled transaction found (0x7f24a45a4fa8)! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:801]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT completed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [tm.c:1043]: w_t_lookup_cancel(): lookup_original: t_lookupOriginalT returned: 0x7f24a45a4fa8 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=628 a=24 n=t_relay {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:1312]: t_newtran(): DEBUG: t_newtran: msg id=12 , global msg id=11 , T on entrance=0xffffffffffffffff {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=38426, isACK=0 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_hooks.c:358]: run_reqin_callbacks_internal(): DBG: trans=0x7f24a45a9098, callback type 1, id 0 entered {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [md5utils.c:67]: MD5StringArray(): MD5 calculated: a4351b7a4b00df7d36f1c82b3d87c603 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:701]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: searching on hash entry 38426 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:409]: matching_3261(): DEBUG: RFC3261 transaction matched, tid=-d8754z-ff05107e83283f5e-1---d8754z- {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:798]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: canceled transaction found (0x7f24a45a4fa8)! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:801]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT completed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_msgbuilder.c:494]: build_local_reparse(): ERROR: build_local_reparse: cannot build CANCEL request {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_cancel.c:310]: cancel_branch(): ERROR: attempt to build a CANCEL failed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_fwd.c:1388]: e2e_cancel(): ERROR: cancel error {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [mem/shm_mem.c:101]: _shm_resize(): WARNING:vqm_resize: resize(0) called {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_reply.c:1591]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_reply.c:647]: _reply_light(): DEBUG: reply sent out. buf=0x7f24aee459c8: SIP/2.0 500 cancel e..., shmem=0x7f24a45ab880: SIP/2.0 500 cancel e {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_reply.c:657]: _reply_light(): DEBUG: _reply_light: finished {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_funcs.c:362]: t_relay_to(): SER: new transaction fwd'ed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=629 a=2 n=exit {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [xavp.c:446]: xavp_destroy_list(): destroying xavp list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [receive.c:278]: receive_msg(): cleaning up

2 1

Kamailio strange behaviour
by Gholamreza Sabery 05 Feb '16

05 Feb '16

I am using Kamailio 4.1.x with NAT enabled. When I want to REGISTER using my desktop client which is Linphone everything is find with any username. But on Android some users can REGISTER and someusers can not. I captured SIP packets and the only difference between packets on Android devices and packets on Desktop client is that on my desktop "received" and "rport" are not added by Kamailio in response messages. Any idea on what is happening here?

2 3

Extending the default 1800 seconds expiration of presence
by kssyrr 04 Feb '16

04 Feb '16

1 0

Sip routing
by David Bakker 04 Feb '16

04 Feb '16

I want to be able to route sip invites from my on prem skype to either an on prem jabber server or out to office 365. It depends on who the recipient is. I am sure Kamailio can do this but I am absolutely at a loss on where to start. I have tried a few different configs but I basically have to break our office communication to test. I am looking for some guidance on what to do. Thanks in advance!

2 1

Kamailio v4.4 - development frozen
by Daniel-Constantin Mierla 04 Feb '16

04 Feb '16

Hello, development (master) branch of Kamailio enters now in pre-release phase for version 4.4.0. Therefore, no new feature should be pushed to master until we create a dedicated branch for 4.4 (expected to be in about 4 weeks or so). If in doubt to push or not a commit to master, push it first on a personal branch (or attach to an email) and discuss it on sr-dev. The new modules can be a bit more dynamic if there is need to get them to the right shape (e.g., like decision to rename functions, parameters or adjust database structure). We hope to get many people involved in testing, to reach a stable state before releasing 4.4.0. If you want to get involved and need assistance, don't hesitate to write to mailing lists. Based on my quick review, there were no major changes to old core components, meaning we should have preserved quite a good level of stability overall. Help with updating the wiki page for migration from 4.3 to 4.4 as well as what is new in 4.4 is very appreciated. I will post updates about them very soon. Many thanks to everyone involved in development of 4.4 and the early testers that played with master branch so far. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 18-20, 2016 Berlin, Germany - http://www.kamailioworld.com

1 0

Kamailio Cluster
by Gholamreza Sabery 03 Feb '16

03 Feb '16

I am trying to create a cluster of Kamailio servers. I want users that are registered on one server to be able to contact and call users on other servers. How can I implement this in Kamailio? PS: My servers are in a private network and I do not have DNS.

10 21

rtpengine port allocation & recycling
by Alex Balashov 03 Feb '16

03 Feb '16

Hello, I have a high-volume installation with 100% RTP relay using rtpengine. We run rtpengine with a high and low port range of 8000 - 65000. Generally the peak concurrent channel count is around 2000-4000 ports, so in theory, so we should have enough ports for all calls currently in process. In practice, however, we get a nearly constant stream of these errors from Kamailio: Feb 2 15:52:58 sip /usr/local/sbin/kamailio[16438]: ERROR: rtpengine [rtpengine.c:1541]: rtpp_function_call(): proxy replied with error: Error rewriting SDP When I trace this back to rtpengine logs on the server, I see: --- Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Received command 'offer' from 215.111.222.101:54100 Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Creating new call Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Failed to get 2 consecutive UDP ports for relay Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Error allocating media ports Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Protocol error in packet from 215.111.222.101:54100: Error rewriting SDP [d3:sdp285:v=0#015#012o=- 1631132006999214513 4263823554000404972 IN IP4 45.201.202.203#015#012s=VOS2009#015#012c=IN IP4 45.201.202.203#015#012t=0 0#015#012m=audio 29034 RTP/AVP 18 8 0 101#015#012a=rtpmap:18 G729/8000#015#012a=fmtp:18 annexb=no#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-15#015#0123:ICE6:remove7:replacel6:origin18:session-connectione7:call-id31:FSRIGZPJGXZWPNO.52364.90737680613:received-froml3:IP415:215.111.222 ... Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] ... 5.125e8:from-tag32:709abb985b675e1497597a5bd44ca2d67:command5:offere] --- This is despite nearly no rtpengine engagement: [root@csrprtpus1 log]# cat /proc/rtpengine/0/status Refcount: 1 Control PID: 14709 Targets: 0 Buckets: 0 As far as I can see, the cause is that rtpengine is not deallocating ports: --- [root@rtphost log]# lsof -n | grep -i rtp rtpengine 14710 root *542u IPv6 1082109949 0t0 UDP *:39910 rtpengine 14710 root *543u IPv6 1082109950 0t0 UDP *:39911 rtpengine 14710 root *544u IPv6 1082218768 0t0 UDP *:41469 rtpengine 14710 root *545u IPv6 1082058934 0t0 UDP *:46424 rtpengine 14710 root *546u IPv6 1082366799 0t0 UDP *:22915 rtpengine 14710 root *547u IPv6 1082288397 0t0 UDP *:57245 rtpengine 14710 root *548u IPv6 1082428020 0t0 UDP *:24311 rtpengine 14710 root *549u IPv6 1082366800 0t0 UDP *:23266 rtpengine 14710 root *550u IPv6 1082798144 0t0 UDP *:22743 rtpengine 14710 root *551u IPv6 1082605782 0t0 UDP *:47845 rtpengine 14710 root *552u IPv6 1082062515 0t0 UDP *:52766 rtpengine 14710 root *553u IPv6 1082648709 0t0 UDP *:58266 rtpengine 14710 root *554u IPv6 1082122218 0t0 UDP *:54359 ... --- There are _lots_ of these: [root@rtphost log]# lsof -n | grep -i rtpengine | grep 'UDP \*:' | wc -l 56964 So, I suppose most of these just aren't being freed up. These are short-duration calls, and the vast majority of them are CANCEL'd at various stages of completion. My approach to invocation of rtpengine in the config is: 1) rtpengine_offer() in branch_route[] on outbound call: set_rtpengine_set("1"); rtpengine_offer("replace-origin replace-session-connection ICE=remove"); add_rr_param(";proxy_media=yes"); setflag(PROXY_MEDIA); This can happen multiple times, as many branches may be attempted before a gateway is found to take the call. 2) Symmetrical rtpengine_answer() in onreply_route: if(isflagset(PROXY_MEDIA) && has_body("application/sdp") && $var(origin_b2bua) == 0) { set_rtpengine_set("1"); rtpengine_answer("replace-origin replace-session-connection ICE=remove"); } 3) rtpengine_delete() in event of CANCEL: if(is_method("CANCEL")) { # Kill RTP stream if this call was using rtpengine. set_rtpengine_set("1"); rtpengine_delete(); # Implicitly forward the CANCEL and drop out of script # if the corresponding INVITE transaction exists. if(!t_relay_cancel()) { # If we are still here, the INVITE transaction # was found but an error occurred. sl_send_reply("500", "Internal Server Error"); exit; } # If we are still here, this is also bad because it means # the corresponding INVITE transaction no longer exists. xlog("L_INFO", 'action=R-MAIN-REQUEST | ret=CANCEL_NO_TRANS_MATCH'); exit; 4) rtpengine_delete() in case of BYE: if(has_totag()) { if(loose_route()) { if(is_method("BYE")) { if(check_route_param("proxy_media=yes")) { set_rtpengine_set("1"); rtpengine_delete(); } } else if(is_method("INVITE")) { # update rtpengine_offer() etc. } ... } else { ... } } Any obvious problem here? Thanks! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 5

Freezing the development for next major version 4.4
by Daniel-Constantin Mierla 03 Feb '16

03 Feb '16

Hello, as a follow up to previous discussions on the mailing list, I would like to propose Wednesday, Feb 3, 2016 as the day to freeze the development for next major release. It will allow the people going at Fosdem to chat and do last minute tunings before freezing. Other suggestions or comments are welcome! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 6

Compile error with CNXCC on Debian 7 Wheezy
by Dirk Teurlings - SIGNET B.V. 03 Feb '16

03 Feb '16

Hi, While compiling Kamailio 4.3.4 from package sources for Debian 7 Wheezy (kamailio repository) I'm running into a problem. I've forked the CNXCC module which I was trying to keep up to date with upstream changes. But before I could do that, there is a dependency of redis added. Unfortunately, installing redis devel libs and libevent doesn't provide the correct version of redis. Also, I noticed on Debian 8 Jessie, it does compile correctly. How could Kamailio be compiled for Wheezy with these sources? I'm missing something obvious I feel. Attached is the compile log, this is with a completely unaltered sources. root@devhost:/usr/src/kamailio-4.3.4+wheezy# make -C modules/cnxcc make: Entering directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc' CC (gcc) [L libkmi.so.1.0] attr.o CC (gcc) [L libkmi.so.1.0] fmt.o CC (gcc) [L libkmi.so.1.0] mi.o CC (gcc) [L libkmi.so.1.0] tree.o LD (gcc) [L libkmi.so.1.0] libkmi.so.1.0 CC (gcc) [L libsrdb1.so.1.0] db.o CC (gcc) [L libsrdb1.so.1.0] db_id.o CC (gcc) [L libsrdb1.so.1.0] db_pool.o CC (gcc) [L libsrdb1.so.1.0] db_query.o CC (gcc) [L libsrdb1.so.1.0] db_res.o CC (gcc) [L libsrdb1.so.1.0] db_row.o CC (gcc) [L libsrdb1.so.1.0] db_ut.o CC (gcc) [L libsrdb1.so.1.0] db_val.o LD (gcc) [L libsrdb1.so.1.0] libsrdb1.so.1.0 CC (gcc) [L libkcore.so.1.0] cmpapi.o CC (gcc) [L libkcore.so.1.0] faked_msg.o CC (gcc) [L libkcore.so.1.0] kstats_wrapper.o CC (gcc) [L libkcore.so.1.0] parse_privacy.o CC (gcc) [L libkcore.so.1.0] parse_sst.o CC (gcc) [L libkcore.so.1.0] regexp.o CC (gcc) [L libkcore.so.1.0] statistics.o CC (gcc) [L libkcore.so.1.0] strcommon.o LD (gcc) [L libkcore.so.1.0] libkcore.so.1.0 LD (gcc) [M cnxcc.so] cnxcc.so cnxcc_mod.o: In function `redisLibeventReadEvent': /usr/include/hiredis/adapters/libevent.h:10: multiple definition of `redisLibeventReadEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined here cnxcc_mod.o: In function `redisLibeventWriteEvent': /usr/include/hiredis/adapters/libevent.h:16: multiple definition of `redisLibeventWriteEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined here cnxcc_mod.o: In function `redisLibeventAddRead': /usr/include/hiredis/adapters/libevent.h:22: multiple definition of `redisLibeventAddRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined here cnxcc_mod.o: In function `redisLibeventDelRead': /usr/include/hiredis/adapters/libevent.h:27: multiple definition of `redisLibeventDelRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined here cnxcc_mod.o: In function `redisLibeventAddWrite': /usr/include/hiredis/adapters/libevent.h:32: multiple definition of `redisLibeventAddWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined here cnxcc_mod.o: In function `redisLibeventDelWrite': /usr/include/hiredis/adapters/libevent.h:37: multiple definition of `redisLibeventDelWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined here cnxcc_mod.o: In function `redisLibeventCleanup': /usr/include/hiredis/adapters/libevent.h:42: multiple definition of `redisLibeventCleanup' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined here cnxcc_mod.o: In function `redisLibeventAttach': /usr/include/hiredis/adapters/libevent.h:49: multiple definition of `redisLibeventAttach' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined here cnxcc_redis.o: In function `redisLibeventReadEvent': /usr/include/hiredis/adapters/libevent.h:10: multiple definition of `redisLibeventReadEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined here cnxcc_redis.o: In function `redisLibeventWriteEvent': /usr/include/hiredis/adapters/libevent.h:16: multiple definition of `redisLibeventWriteEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined here cnxcc_redis.o: In function `redisLibeventAddRead': /usr/include/hiredis/adapters/libevent.h:22: multiple definition of `redisLibeventAddRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined here cnxcc_redis.o: In function `redisLibeventDelRead': /usr/include/hiredis/adapters/libevent.h:27: multiple definition of `redisLibeventDelRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined here cnxcc_redis.o: In function `redisLibeventAddWrite': /usr/include/hiredis/adapters/libevent.h:32: multiple definition of `redisLibeventAddWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined here cnxcc_redis.o: In function `redisLibeventDelWrite': /usr/include/hiredis/adapters/libevent.h:37: multiple definition of `redisLibeventDelWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined here cnxcc_redis.o: In function `redisLibeventCleanup': /usr/include/hiredis/adapters/libevent.h:42: multiple definition of `redisLibeventCleanup' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined here cnxcc_redis.o: In function `redisLibeventAttach': /usr/include/hiredis/adapters/libevent.h:49: multiple definition of `redisLibeventAttach' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined here collect2: error: ld returned 1 exit status make: *** [cnxcc.so] Error 1 make: Leaving directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc' Cheers, Dirk

3 3

Possible accidental merge to master.
by Cody Herzog 03 Feb '16

03 Feb '16

Hello. I feel like a total idiot. I was inspecting the various GitHub branches for Kamailio using a GitHub visual client, and I think I managed to accidentally merge a branch back into master. The branch I was inspecting was 'lazedo/presence_improvements'. I was inspecting diffs and branches, and was amazed that I was able to screw up so badly with one single click, but I guess that's the danger of a visual git client. Anyway, before trying to do anything more, I figured I'd asked for advice, because I don't want to screw up further. Hopefully there's a simple way to revert the accidental merge, but I first wanted to confirm that I actually did make that mistake, and that it's visible to others. Thanks.

2 2

issue with INVITE frame size
by Rene Montilva 03 Feb '16

03 Feb '16

Hi list I have problem with invite packet in some wifi networks because the invite packet is less than 1000bytes(frame size) and the access point not redirect to softphone, this scenario happen with incoming calls to my DID, the packets come from the provider to kamailio with a size more than 1000 and when kamailio redirect to softphone sometimes is less than 1000. how i could solve this issue?. thanks for any help.

3 7

Kamailio/How to send all requests ?
by alexandre.anconetti＠orange.com 02 Feb '16

02 Feb '16

Hello ! I'm using Kamailio for 2 months, and I have a problem with the routing logic. My aim is to use 2 Kamailio servers (in a cluster, so I have a primary and a backup server with a Virtual IP that can switch between the 2 servers) working with 2 medias servers (same as above, a primary and a backup). The Kamailio servers are here to handle failover, so all the requests go through them, and then are sent to the active media server. My question is : Which module(s) should I load to transmit all the requests (including registers) to my media server, through the Kamailio server ? Any particular parameters ? Then, what will be in the "request_route" ? I'm using Kamailio 4.3.4. Best regards, Alexandre _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 2

SIP register - memory size
by José Seabra 02 Feb '16

02 Feb '16

Hello there, Can anyone tell me what is the exactly memory size that kamailio use for one sip register saved on memory? How much memory i need allocate to kamailio in order to support 50.000 subscribers. Best Regards

2 4

Kamailio Social Event at Fosdem 2016
by Daniel-Constantin Mierla 02 Feb '16

02 Feb '16

Hello, only few days left, so we need to nail the location down for Kamailio dinner at Fosdem. One suggestion in walking distance is: - http://restaurant-italien-picotin-bruxelles.be/en I understood that it was used in the past also for Fosdem Speaker's Dinner, so it might be busy and we can't get the seats. So new suggestions are more than welcome in order to have some backups to try! If there is no strong preference for something else by end of today, tomorrow we should attempt to do the reservation at this place. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

5 9

Asterisk+Kamailio
by Вячеслав Завалко 02 Feb '16

02 Feb '16

The adjustment was carried out by a manual that http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb But the sharing screen is not working softphone on a given configuration. What can be done?

2 1

kamailio + asterisk
by Вячеслав Завалко 02 Feb '16

02 Feb '16

Is it possible to do a demonstration screen caller using Kamailio + Asterisk?

2 1

Kamailio 4.3 and Freeswitch 1.0 Stable Latest
by Barış Şekerciler 02 Feb '16

02 Feb '16

Hello everyone. I'm a student and I'm working on project which about SIP communication and PBXs with IP phones. So, my first test results were OK with JITSI. But I think I need Freeswitch for working with IP phones. In a word, I need configure an integration Kamailio and Freeswitch. First, I setup Debian 8.3 Jessie and installed Kamailio on this my local server, after that I installed another Debian 8.3 Jessie (from same image) as my second server and it was going to run Freeswitch on itself. Then I tried to send my communication requests to my Freeswitch server. I made some tests, my Jitsi accounts which are set in Kamailio server were done. I've read Kamailio 3.2 and Freeswitch integration from the Kamailio wiki and I applied exactly the same thing but I did not work. When I tried to reach another IP phone from my IP phone (I registered them) phone always say "NOT FOUND". I'm sure I did my configuration properly. So, how can I figure it out these things? How can I understand, does Kamailio routes to Freeswitch to my phones? Best regards. Thanks.

2 1

Critical issue: Kamailio throwing db errors
by Sharon Nathaniel 02 Feb '16

02 Feb '16

Hi, I am not sure, if its a kamailio issue or something else, but our Kamailio 4.2 server crashes everyday. Throwing out these logs: http://pastebin.com/z1MWdk7q. We have to restart the server to get this fixed. Please help us understand what is causing the issue. Thanks and Regards, Sharon Nathaniel The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to it by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken based on it, is strictly prohibited and may be unlawful.

2 1

Kamailio v4.3 and Freeswitch Stable Latest
by Barış Şekerciler 02 Feb '16

02 Feb '16

Hello everyone. I'm a student and I'm working on project which about SIP communication and PBXs with IP phones. So, my first test results were OK with JITSI. But I think I need Freeswitch for working with IP phones. In a word, I need configure an integration Kamailio and Freeswitch. First, I setup Debian 8.3 Jessie and installed Kamailio on this my local server, after that I installed another Debian 8.3 Jessie (from same image) as my second server and it was going to run Freeswitch on itself. Then I tried to send my communication requests to my Freeswitch server. I made some tests, my Jitsi accounts which are set in Kamailio server were done. I've read Kamailio 3.2 and Freeswitch integration from the Kamailio wiki and I applied exactly the same thing but I did not work. When I tried to reach another IP phone from my IP phone (I registered them) phone always say "NOT FOUND". I'm sure I did my configuration properly. So, how can I figure it out these things? How can I understand, does Kamailio routes to Freeswitch to my phones? Best regards. Thanks.

4 27

Force transport from TLS to UDP when using dispatcher
by mayamatakeshi 01 Feb '16

01 Feb '16

Hello, I have this scenario: - subscriber registers using TLS - call arrives from PSTN gateway (in UDP) to subscriber - I relay the INVITE to subscriber but it doesn't answer the call - the subscriber has callforward enabled - we send the call to PSTN callforward destination using carrierroute In the above, after calling cr_route I use this: $du = "sip:" + $rd + ":" + $rp + ";transport=udp"; to force the call to PSTN gateway to go out as UDP because after trying to call the subscriber, the transport changes and stays as TLS. However, if instead of callforward the user has voicemail enabled, we use dispatcher to send the call to a cluster of media servers. So, after calling ds_select_dst() I call $du = "sip:" + $dd + ":" + $dp + ";transport=udp"; but this is unable to force the call to go as UDP but it still goes as in TLS In both cases I see this in the log files: /usr/local/src/git/kamailio-4.3/kamailio[19277]: WARNING: <core> [forward.c:231]: get_send_socket2(): protocol/port mismatch (forced tls:XXX.XXX.XXX.XXX:5061, to udp:YYY.YYY.YYY.YYY:5060) But it only works for carrierroute, not for dispatcher. I am not sure if this is a bug in dispatcher. But anyway, is there any other way I could try to force transport=UDP? Regards, Takeshi

1 1

checking source domain
by Yuriy Gorlichenko 01 Feb '16

01 Feb '16

I need to understand where from packets received. Now I use something like If $si == "1.2.3.4" { xlog("L_INFO","bla bla bla"); } But I need to check source server not only by IP and PORT, but at Domain too For example if (some_pseudovariable=="pbx.server.com"){ xlog("L_INFO","bla bla bla"); } I can use $fu for example because for some packets it includes domain name of kamailio (i think details not important but this situations can be) Does kamailio have some mechanisms to do that? I searched it at cookbook but not found anything. Thank you

2 1

RTPPROXY issue and sip to sip calling
by Ahmed Rehan 31 Jan '16

31 Jan '16

Dear All I m trying to setup kamailio and asterisk in load balancing with a2billing . Currently all of my VMs, one Kamailio and two asterisks are on same subnet . I have started the RTPproxy like below ./rtpproxy -s udp:127.0.0.1:7722 -l X.X.X.153 -m 10000 -M 50000 -u root root -F -d INFO LOG_LOCAL0 My question is if all the VMs are on same subnet with same gateway what should be written in the private IP X.X.X.153/<private - ip> Secondly i m authenticating and registering the SIP on kamailio using the A2B DB . all the dialplan for a2b is being run on asterisk . Now if i want to call SIP peer to Peer like in case of followme case , How should i route the calls in Kamailio ? will it be using usr loc module? if so any help will be appreciated -- Regards Ahmed Rehan

2 1

Core Dump during shutdown on SPARC64
by Spencer Thomason 31 Jan '16

31 Jan '16

Hello, I’m trying to get Kamailio running on Solaris 11 SPARC64 and I’m receiving a bus error on shutdown. If needed, we can make SPARC hardware available for testing. Thanks, Spencer Core was generated by `/opt/kamailio/sbin/kamailio -f /opt/kamailio/etc/kamailio/kamailio.cfg -P /syst'. Program terminated with signal 10, Bus error. #0 0x00000001003e73f0 in cfg_destory_groups (block=0xffffffff76e5ded4 "") at cfg/cfg_struct.c:299 299 old_string = *(char **)(block + group->var_offset + mapping[i].offset); (gdb) bt full #0 0x00000001003e73f0 in cfg_destory_groups (block=0xffffffff76e5ded4 "") at cfg/cfg_struct.c:299 group = 0x100745e20 def = <optimized out> i = 14 group2 = <optimized out> mapping = 0x100745a78 old_string = <optimized out> #1 cfg_destroy () at cfg/cfg_struct.c:391 __FUNCTION__ = "cfg_destroy" #2 0x0000000100163fc4 in cleanup (show_status=show_status@entry=1) at main.c:540 memlog = <optimized out> __FUNCTION__ = "cleanup" #3 0x00000001001650d4 in shutdown_children (show_status=show_status@entry=1, sig=15) at main.c:665 No locals. #4 0x0000000100165c0c in handle_sigs () at main.c:695 chld = <optimized out> chld_status = 0 memlog = <optimized out> __FUNCTION__ = "handle_sigs" #5 0x000000010016e678 in main_loop () at main.c:1722 i = <optimized out> pid = <optimized out> si = <optimized out> si_desc = "udp receiver child=15 sock=104.222.31.55:9000\000\005\066\377\377\377\377v\345\322\370\000\000\000\000\000\020\000\063\377\377\377\377\177\377\360q\000\000\000\001\000B\277 \000\000\000\001\000^:P\000\000\000\001\000\002\356(\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" nrprocs = <optimized out> woneinit = <optimized out> __FUNCTION__ = "main_loop" #6 0x000000010042cafc in main (argc=<optimized out>, argv=<optimized out>) at main.c:2597 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0xffffffff7ffffd57 "" tmp_len = 0 port = 0 proto = 0 options = 0x100036918 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:" ret = -1 seed = 4139658536 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> p = <optimized out> st = {st_dev = 2478196129807, st_ino = 405001306, st_mode = 16832, st_nlink = 2, st_uid = 0, st_gid = 0, st_rdev = 18446744073709551615, st_size = 117, st_atim = {tv_sec = 1452739293, tv_nsec = 444332080}, st_mtim = { tv_sec = 1452739411, tv_nsec = 727071262}, st_ctim = {tv_sec = 1452739411, tv_nsec = 727071262}, st_blksize = 8192, st_blocks = 16, st_fstype = "tmpfs\000\000\000\000\000\000\000\000\000\000"} __FUNCTION__ = “main" # this file is autogenerated by make cfg MAIN_NAME= kamailio CFG_NAME= kamailio SCR_NAME= sip-router FLAVOUR= kamailio INSTALL_FLAVOUR= kamailio SRC_NAME= sip-router RELEASE= 4.4.0-dev8 OS= solaris ARCH= sparc64 C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.4.0-dev8"' -DARCH='"sparc64"' -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"gcc 4.8.2"' -D__CPU_sparc64 -D__OS_solaris -DSER_VER=4004000 -DCFG_DIR='"/opt/kamailio/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DSPARC64_MODE -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -DHAVE_DEVPOLL -DHAVE_SELECT -DHAVE_FILIO_H DEFS_RM= PROFILE= CC= gcc LD= gcc MKDEP= gcc -MM -MG MKTAGS= ctags LDFLAGS= -m64 -O2 C_INCLUDES= CC_MKDEP_OPTS= -MMD -MP MOD_LDFLAGS= -G -m64 -O2 LIB_LDFLAGS= -G -m64 -O2 UTILS_LDFLAGS= -m64 -O2 LIB_SONAME= -Wl,-h, LD_RPATH= -Wl,-R, LIB_SUFFIX= .so LIB_PREFIX= lib LIBS= -ldl -lresolv -L/usr/local/lib -lxnet -lsocket -lnsl -lrt LEX= flex YACC= bison YACC_FLAGS= -d -b cfg PREFIX= /opt/kamailio LOCALBASE= /usr/local TAR= gtar INSTALL= ginstall INSTALL_CFG= ginstall -m 644 INSTALL_BIN= ginstall -m 755 INSTALL_MODULES= ginstall -m 755 INSTALL_DOC= ginstall -m 644 INSTALL_MAN= ginstall -m 644 INSTALL_LIB= ginstall -m 755 INSTALL_TOUCH= touch INSTALL_SHARE= ginstall -m 644 Q= 1 CC_EXTRA_OPTS= -O2 -m64 CPU= ultrasparc CFLAGS_RM= CFLAGS= -g -funroll-loops -mtune=native -mcpu=native -fno-strict-overflow -ftree-vectorize -Wall -mno-faster-structs MOD_CFLAGS= -fPIC -DPIC $(CFLAGS) LIB_CFLAGS= -fPIC -DPIC $(CFLAGS) UTILS_CFLAGS= $(CFLAGS) BASEDIR= $(DESTDIR) basedir= $(BASEDIR) DESTDIR= LIBDIR= lib64 RUNBASEDIR= $(DESTDIR) runbasedir= $(RUNBASEDIR) PREFIX= /opt/kamailio prefix= $(PREFIX) cfg_prefix= $(basedir)$(prefix) cfg_dir= etc/$(MAIN_NAME)/ bin_prefix= $(basedir)$(prefix) bin_dir= sbin/ modules_prefix= $(basedir)$(prefix) modules_dir= $(LIBDIR)/$(MAIN_NAME)/ doc_prefix= $(basedir)$(prefix) doc_dir= doc/$(MAIN_NAME)/ man_prefix= $(basedir)$(prefix) man_dir= man/ ut_prefix= $(basedir)$(prefix) ut_dir= share_prefix= $(basedir)$(prefix) share_dir= share/$(MAIN_NAME)/ lib_prefix= $(basedir)$(prefix) lib_dir= $(LIBDIR)/$(MAIN_NAME)/ data_prefix= $(basedir)$(prefix) data_dir= $(MAIN_NAME)/ cfg_target= $(prefix)/$(cfg_dir) lib_target= $(prefix)/$(lib_dir) data_target= $(prefix)/$(data_dir) run_prefix= $(runbasedir) run_dir= var/run/$(MAIN_NAME)/ run_target= $(run_prefix)/$(run_dir) override makefile_defs:=1 C_DEFS:=$(filter-out $(DEFS_RM) $(extra_defs),$(C_DEFS)) $(extra_defs) CFLAGS:=$(filter-out $(CFLAGS_RM) $(CC_EXTRA_OPTS), $(CFLAGS)) $(CC_EXTRA_OPTS)

2 5

P-CSCF
by Fred Schulz 30 Jan '16

30 Jan '16

Hi all, we’re just playing around with an IMS setup bases on kamailio. Therefore the kamailio is used as P-,I- and S-CSCF. We where able to register two clients through all components. As we wan to start a call session, the P-CSCF answers with „403 - Forbidden. You must register with an S-CSCF“… I found this snippet in kamailio.cfg: if (!pcscf_is_registered("location")) { send_reply("403","Forbidden - You must register first with a S-CSCF“); break; } Can one tell me what exactly the kamailio is checking there? As I figured out it is looking in database location table. The table contains the registered users registered towards the IMS. Another „problem“ we faced with is the rtpproxy. As the ngcp-mediaproxy-ng is no longer available and replaced with rtpproxy we’re trying to use it. But kamailio said that the proxy isn’t answering the way expected. ERROR: rtpengine [rtpengine.c:1622]: rtpp_test(): proxy responded with invalid response Any advise would be nice. Thank you Fred

2 2

Re: [SR-Users] P-CSCF
by Aaron Hamstra 30 Jan '16

30 Jan '16

Fred, I think you would need to use rtpengine instead of rtpproxy. https://github.com/sipwise/rtpengine -Aaron From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Fred Schulz Sent: Thursday, January 28, 2016 1:24 PM To: sr-users(a)lists.sip-router.org Subject: [SR-Users] P-CSCF Hi all, we’re just playing around with an IMS setup bases on kamailio. Therefore the kamailio is used as P-,I- and S-CSCF. We where able to register two clients through all components. As we wan to start a call session, the P-CSCF answers with „403 - Forbidden. You must register with an S-CSCF“… I found this snippet in kamailio.cfg: if (!pcscf_is_registered("location")) { send_reply("403","Forbidden - You must register first with a S-CSCF“); break; } Can one tell me what exactly the kamailio is checking there? As I figured out it is looking in database location table. The table contains the registered users registered towards the IMS. Another „problem“ we faced with is the rtpproxy. As the ngcp-mediaproxy-ng is no longer available and replaced with rtpproxy we’re trying to use it. But kamailio said that the proxy isn’t answering the way expected. ERROR: rtpengine [rtpengine.c:1622]: rtpp_test(): proxy responded with invalid response Any advise would be nice. Thank you Fred

2 1

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 30 Jan '16

30 Jan '16

Hi Basit, Thanks for response. I have tried the below commands to grant all privileges. The commands results OK. Still I was facing the same issue which is mentioned in trailing mail. Could anyone guide me here to proceed further. Any suggestions/solutions would be very helpful. Regards, Sainath ---------- Forwarded message ---------- From: "Abdul Basit" <basitstar(a)hotmail.com<mailto:basitstar@hotmail.com>> Date: Jan 27, 2016 7:37 PM Subject: Re: [SR-Users] Kamailio IMS deployment To: "Kamailio SER - Users Mailing List" <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>, "franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>" <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> Cc: use the following command and try again.. GRANT ALL PRIVILEGES ON *.* TO '<user>'@'<hostname>' IDENTIFIED BY '<password>'; GRANT ALL PRIVILEGES ON *.* TO '<user>'@'%' IDENTIFIED BY '<password>'; FLUSH PRIVILEGES; regards, AB ________________________________ From: sainath.ellendula(a)wipro.com<mailto:sainath.ellendula@wipro.com> To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at> Date: Wed, 27 Jan 2016 06:21:52 +0000 CC: sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz, Thanks for the response. As suggested followed below commands to check the GRANTs on database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; The output result is same as mentioned below. Could you please guide me here to proceed further. Regards, Sainath ---------- Forwarded message ---------- From: "Franz Edler" <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> Date: Jan 27, 2016 1:07 AM Subject: RE: [SR-Users] Kamailio IMS deployment To: "Kranti Kumar" <krantikumara(a)gmail.com<mailto:krantikumara@gmail.com>>, "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: "Ramya Y" <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Obviously the access of HSS to the database did not succeed. You should check if access permissions to the database is enabled for HSS. Check the GRANTs on the database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; quit; The result should be: +-------------------------------------------------------------------------------------------------------------------+ | Grants for hss(a)server.net1.test<mailto:hss@server.net1.test> | +-------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'hss'@'server.net1.test' IDENTIFIED BY PASSWORD '*AC83FCF24B79020EF2C51D780CDFA559F25CC9BE' | | GRANT SELECT, INSERT, UPDATE, DELETE ON `hss_db`.* TO 'hss'@'server.net1.test' | +-------------------------------------------------------------------------------------------------------------------+ BR Franz From: Kranti Kumar [mailto:krantikumara@gmail.com<mailto:krantikumara@gmail.com>] Sent: Sunday, January 24, 2016 10:55 AM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: Ramya Y <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Subject: Re: [SR-Users] Kamailio IMS deployment Thanks a lot Franz. Observed few issues even after changes done in /etc/bind. Please find the below Errors in each interfaces and also find the attachment of /var/log/syslog(not shared full logs) Could you please help me here to proceed further. HSS – Configured IP : 10.0.0.9 root@server:~# ./hss.sh – Configured IP : 10.0.0.9 Building Classpath Classpath is lib/xml-apis.jar:lib/xercesImpl.jar:lib/xerces-2.4.0.jar:lib/xalan-2.4.0.jar:lib/tomcat-util.jar:lib/tomcat-http.jar:lib/tomcat-coyote.jar:lib/struts.jar:lib/servlets-default.jar:lib/servlet-api.jar:lib/naming-resources.jar:lib/naming-factory.jar:lib/mysql-connector-java-3.1.12-bin.jar:lib/mx4j-3.0.1.jar:lib/log4j.jar:lib/junit.jar:lib/junitee.jar:lib/jta.jar:lib/jsp-api.jar:lib/jmx.jar:lib/jdp.jar:lib/jasper-runtime.jar:lib/jasper-compiler-jdt.jar:lib/jasper-compiler.jar:lib/hibernate3.jar:lib/FHoSS.jar:lib/ehcache-1.1.jar:lib/dom4j-1.6.1.jar:lib/commons-validator.jar:lib/commons-modeler.jar:lib/commons-logging.jar:lib/commons-logging-1.0.4.jar:lib/commons-lang.jar:lib/commons-fileupload.jar:lib/commons-el.jar:lib/commons-digester.jar:lib/commons-collections-3.1.jar:lib/commons-beanutils.jar:lib/cglib-2.1.3.jar:lib/catalina-optional.jar:lib/catalina.jar:lib/c3p0-0.9.1.jar:lib/base64.jar:lib/asm.jar:lib/asm-attrs.jar:lib/antlr-2.7.6.jar::log4j.properties:.. 2016-01-21 14:07:07,876 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started. 2016-01-21 14:07:12,462 WARN org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9 2016-01-21 14:07:16,578 INFO de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation! 2016-01-21 14:07:17,966 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started ! 2016-01-21 14:08:21,200 WARN com.mchange.v2.resourcepool.BasicResourcePool - run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1670988b<mailto:com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1670988b> -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (60). Last acquisition attempt exception: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: java.net.ConnectException: Connection refused STACKTRACE: java.net.SocketException: java.net.ConnectException: Connection refused PCSCF – Configured IP : 10.0.0.10 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2352) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(2352) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2352) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2352) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(2352) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2352) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2352) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing ^C^C 0(2352) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 1(2373) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 2(2374) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2352) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ICSCF – Configured IP : 10.0.0.11 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-icscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2353) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: icscf.net1.test [10.0.0.11]:5060 Aliases: *: icscf.net1.test:* WARNING: no fork mode 0(2353) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2353) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2353) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2353) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2353) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2353) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 10(2370) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 6(2366) INFO: cdp [worker.c:331]: worker_process(): [3] Worker process started... 7(2367) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2367) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2368) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2368) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 9(2369) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2369) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3869 9(2369) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3869 9(2369) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 8(2368) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2370) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 8(2368) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [14] returned 0 > ... dropping 8(2368) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer ^C10(2370) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2353) ALERT: <core> [main.c:725]: handle_sigs(): child process 2361 exited normally, status=0 0(2353) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2353) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 2(2362) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2353) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... 0(2353) INFO: cdp [diameter_peer.c:428]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... 0(2353) INFO: cdp [diameter_peer.c:435]: diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child [2370] to terminate... 0(2353) INFO: cdp [diameter_peer.c:447]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated. Cleaning up. 0(2353) INFO: cdp [worker.c:140]: worker_destroy(): Unlocking workers waiting on empty queue... 0(2353) INFO: cdp [worker.c:143]: worker_destroy(): Unlocking workers waiting on full queue... 0(2353) CRITICAL: cdp [diameter_peer.c:487]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test 0(2353) INFO: cdp [mod.c:244]: cdp_exit(): ... CDiameterPeer child stoped 0(2353) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized SCSCF – Configured IP : 10.0.0.12 root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-scscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2371) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: scscf.net1.test [10.0.0.12]:6060 Aliases: *: scscf.net1.test:* WARNING: no fork mode 0(2371) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2371) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2371) INFO: ims_usrloc_scscf [hslot.c:69]: ul_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [hslot_sp.c:67]: subs_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [contact_hslot.c:67]: init_contacts_locks(): locks array size 512 0(2371) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2371) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2371) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2371) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 3(2381) INFO: cdp [worker.c:331]: worker_process(): [0] Worker process started... 4(2382) INFO: cdp [worker.c:331]: worker_process(): [1] Worker process started... 5(2383) INFO: cdp [worker.c:331]: worker_process(): [2] Worker process started... 7(2390) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2390) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2392) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2392) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 8(2392) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 9(2393) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2393) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3870 9(2393) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3870 9(2393) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 10(2394) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2394) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 8(2392) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [15] returned 0 > ... dropping 8(2392) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused ^C11(2398) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 9(2393) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2371) ALERT: <core> [main.c:725]: handle_sigs(): child process 2381 exited normally, status=0 0(2371) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2371) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 10(2394) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2371) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... On Fri, Jan 22, 2016 at 2:16 AM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Hi, you can see the first error is a database error: ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) This error I expected because you have to adapt the access permissions to the database. Just check the GRANT statements in my log-file and try to understand what they do. Then adapt it accordingly. BR Franz From: Ramya Y [mailto:y.ramya146@gmail.com<mailto:y.ramya146@gmail.com>] Sent: Wednesday, January 20, 2016 2:19 PM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz we have tried with different interfaces(eth0(10.0.0.9),eth1(10.0.0.10),eth2(10.0.0.11),eth3(10.0.0.12) for P/I/S ,but facing below error. root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(1630) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(1630) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(1630) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(1630) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(1630) ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) 0(1630) ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool 0(1630) ERROR: ims_usrloc_pcscf [usrloc_db.c:79]: init_db(): unable to connect to the database 0(1630) ERROR: ims_usrloc_pcscf [ul_mod.c:203]: mod_init(): Error initializing db connection 0(1630) ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module ims_usrloc_pcscf (/usr/local/lib64/kamailio/modules/ims_usrloc_pcscf.so) ERROR: error while initializing modules 0(1630) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialize could you please help me how to proceed further, steps followed: =========== 1)Modified at - /etc/network/interfaces: created eth1,eth2,eth3 for P/I/S-CSCF. Interfaces are up. 2)Added Bind address at /etc/mysql/my.cnf bind-address 10.0.0.9 bind-address 10.0.0.10 bind-address 10.0.0.11 bind-address 10.0.0.12 3)Modified at /etc/bind/net1.test.zone $ORIGIN net1.test. $TTL 1W @ 1D IN SOA serverkde. root.net1.test ( 2010081401 ; Serial YYYYMMDDXX 3H ; refresh 15M ; retry 1W ; expiry 1D ) ; minimum 1D IN NS server server 1D IN A 10.0.0.9 hss 1D IN CNAME server as1 1D IN CNAME server as2 1D IN CNAME server xcap 1D IN CNAME server server1 1D IN A 10.0.0.10 pcscf 1D IN CNAME server1 server2 1D IN A 10.0.0.11 icscf 1D IN CNAME server2 server3 1D IN A 10.0.0.12 scscf 1D IN CNAME server3 4)Modified at /etc/bind/0.0.10.zone $TTL 86400 @ IN SOA server. root.net2.test ( 2010081401 ; Serial YYYYMMDDXX 28800 ; Refresh 14400 ; Retry 3600000 ; Expire 86400 ) ; Minimum IN NS server.net1.test. IN NS server1.net1.test. IN NS server2.net1.test. IN NS server3.net1.test. 10 IN PTR notebook.net1.test. 9 IN PTR server.net1.test. 7 IN PTR server.net2.test. 5)Modified at /etc/resolve.conf domain net1.test search net1.test nameserver server.net1.test nameserver server1.net1.test nameserver server2.net1.test nameserver server3.net1.test 6)Modified at /etc/hosts 127.0.0.1 localhost 10.0.0.9 server.net1.test server 10.0.0.10 server1.net1.test server1 10.0.0.11 server2.net1.test server2 10.0.0.12 server3.net1.test server3 10.0.0.9 net1.test 10.0.0.10 pcscf.net1.test 10.0.0.11 icscf.net1.test 10.0.0.12 scscf.net1.test Thanks, Ramyasri. On Sun, Jan 17, 2016 at 5:33 PM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Fine. This exactly was my intention. BR Franz > -----Original Message----- > From: sr-users [mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>] On Behalf Of > Vasiliy Ganchev > Sent: Monday, January 11, 2016 9:08 AM > To: sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> > Subject: Re: [SR-Users] Kamailio IMS deployment > > Hi Franz! > > Thanks for sharing! Great job, end excellent materials to get started with > students (beside my main work I also teach students in Odessa National > Academy of Telecommunication). > I was looking for some "light" way how to start with real deployment of IMS, > not pure theory, and this is just the kind I wanted! > > Will try your deploy in education process this year. (will share the results in > the end) > > Cheers! > > > > -- > View this message in context: http://sip- > router.1086192.n5.nabble.com/Kamailio-IMS-deployment-<http://router.1086192.n5.nabble.com/Kamailio-IMS-deployment-> > tp143593p144517.html > Sent from the Users mailing list archive at Nabble.com. > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr- > users(a)lists.sip-router.org<mailto:users@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<mailto:sr-users@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<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> _______________________________________________ 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 _______________________________________________ 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 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 3

Re: [SR-Users] [sr-dev] Fosdem 2016
by Daniel-Constantin Mierla 29 Jan '16

29 Jan '16

Hello, ok, let's see how many we are going to be and then decide how to do it (if we are not a large group, we can just go in the city center and walk around for a place). Cheers, Daniel On 06/01/16 02:30, Alexandr Dubovikov wrote: > Hello Daniel, > > I will be there, plus Lorenzo and Torsen. Make a small event on > Saturday will be very cool, but not at Beer Mania :-) > > Wbr, > Alexandr > > On 05.01.2016 20:06, Daniel-Constantin Mierla wrote: >> Hello, >> >> anyone going to Fosdem? >> >> If no unexpected weather conditions messing the transport system, I am >> going to be there. It would be good to know who else we can meet there. >> >> If there are enough people interested, we can try organizing a social >> event (dinner/drinks) on Saturday evening. Last year we did it together >> with Jitsi team, but they are not coming this year. Perhaps there are >> other folks around the RTC dev room we can ask. >> >> On the other hand, it is harder to find a place if it is a large group, >> even harder to put all together if there are different >> groups/coordinators. Also, it is not easy to discuss withing a large >> group, as typically for a dinner we were seated to tables. Therefore >> organizing for a smaller group just for Kamailio friends could be a good >> alternative. Let's see first the number of participant and the level of >> interest for various options. >> >> This being an announcement, was crossposted to few mailing lists, but as >> most of the people are on sr-users, I think it would be good to reply >> and follow up on this discussion only there. >> >> Cheers, >> Daniel >> > > > _______________________________________________ > sr-dev mailing list > sr-dev(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

5 6

Memory issue?
by Igor Potjevlesch 29 Jan '16

29 Jan '16

Hello, I got several errors this morning on a Kamailio instance. The first occurred without a complete crash of Kamailio but 4 coredumps have been created: BFD: Warning: /core.3818 is truncated: expected core file size >= 342618112, found: 61579264. [New Thread 3818] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3821 is truncated: expected core file size >= 343044096, found: 21229568. [New Thread 3821] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3822 is truncated: expected core file size >= 342675456, found: 120066048. [New Thread 3822] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3839 is truncated: expected core file size >= 342401024, found: 2691072. [New Thread 3839] Cannot access memory at address 0x3d6f021168 Cannot access memory at address 0x3d6f021168 Cannot access memory at address 0x3d6f021168 It seems that Kamailio auto recovered without fully crashed during this issue. But the Kamailio FIFO was deleted and kamctl didn't worked anymore. I had to properly restart. I have seen in the logs: Jan 21 10:21:11 /usr/local/sbin/kamailio[3843]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3839]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3839]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3843]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3831]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3831]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3841]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3821]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3821]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:12 /usr/local/sbin/kamailio[3828]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3843]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3818]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3818]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. [.] Jan 21 10:21:13 kernel: kamailio[3818]: segfault at 40 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] Jan 21 10:21:13 kernel: kamailio[3822]: segfault at 20 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] Jan 21 10:21:14 kernel: kamailio[3821]: segfault at 0 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] [.] Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3828 exited by a signal 11 Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:787]: handle_sigs(): core was not generated Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3825 exited by a signal 11 Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:787]: handle_sigs(): core was not generated Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Jan 21 10:21:14 /usr/local/sbin/kamailio[3832]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Jan 21 10:21:14 /usr/local/sbin/kamailio[3841]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Jan 21 10:21:14 /usr/local/sbin/kamailio[3876]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received 1 hour later a new crash but here Kamailio has completely restarted with two coredump showing the same error than previous one. And 2 coredumps readable: Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 256 -M 64'. Program terminated with signal 11, Segmentation fault. #0 0x00007f13a1550af2 in dtrie_insert (root=0x7f138d7ffb38, number=0x22ba6c0 "003716716", numberlen=9, data=0x2, branches=10) at dtrie.c:141 141 if (node->child[digit] == NULL) { Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 256 -M 64'. Program terminated with signal 11, Segmentation fault. #0 0x00007f13a1550af2 in dtrie_insert (root=0x7f138d7ff998, number=0x22b57a8 "0035587482", numberlen=10, data=0x2, branches=10) at dtrie.c:141 141 if (node->child[digit] == NULL) { Kamailio is 4.2.6 on this instance. Regards, Igor.

3 4

RTP Statistics
by Gholamreza Sabery 29 Jan '16

29 Jan '16

Hello everyone. I want to store RTCP Statistics for a RTP session. Currently I am using $rtpstat pseudo-variable which is exported by RTPProxy module. The value of this variable does not show actual number of packets sent and received; and only contains ttl, npkts_ina, npkts_ino, nrelayed and ndropped. I want actual number of packets sent from and actual number of packets received by a client. How can I obtain this information?

2 3

Presence: Notify on publication status refresh
by Aleš Šturm 28 Jan '16

28 Jan '16

Hi all, I am using Kamailio 4.3 as Presence server and I have a question regarding NOTIFY messages sent after publication status refresh. When PUA sends refreshing PUBLISH request (before expiration) Kamailio sends NOTIFY request. Large number of watchers per one presentity causes large traffic. RFC3265 states: NOTIFY messages are sent to inform subscribers of changes in state to which the subscriber has a subscription. But when publication is only refreshed (publication expiration is extended) the publish state is not changed (PUBLISH without XML body). >From RFC5839: The SIP PUBLISH [RFC3903] method uses a similar mechanism, where a refresh of a publication is done by reference to its assigned entity-tag, instead of retransmitting the event state each time the publication expiration is extended. Is it possible to configure Kamailio that wouldn't send NOTIFY request to watchers when publication status refresh (PUBLISH without XML Body) occur? Can anyone help? Thanks in advance, Ales

3 5

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