Re: [SR-Users] auth by IP

I mean auth, not registration. Anyway this works as I've wanted:   if(!allow_source_address() && $au==$null)     {     sl_send_reply("403","Go away!");     exit;     } 19.04.2019 12:19, Daniel Tryba пишет: This code is in no way related to registrations.

Re: [SR-Users] auth by IP

Added this before final "return", it still allow to call from any IP without registration. :( 19.04.2019 11:22, Daniel Tryba пишет: if(!allow_source_address() || $au==$null) { sl_send_reply("403","Go away!"); } ___ Kamailio (SER) - Users

[SR-Users] auth by IP

Following code snippet from default kamailio.cfg never gives 403 if you smart enough to set "fromdomain" parameter on Asterisk to Kamailio's IP. How to fix it? I want password-based registration (which is OK now) and permit calls via Kamailio only from permitted IPs.     # if caller is

Re: [SR-Users] Kamailio and CDR

m 07.04.2019 um 12:42 schrieb Henning Westerholt <mailto:h...@skalatan.de>>: Hello, some starting points: - use dlg_manage() or set a dialog flag in the cfg to start dialog tracking - setup the dialog event routes (section 11 in README) and put your logging logic there Best

Re: [SR-Users] Kamailio and CDR

How to make something on dialog event? Just can't figure it out after reading module docs :( 06.04.2019 2:09, David Villasmil пишет: You can always export the cdr table periodically. Take a look at siremis. And when the trigger fires every 5 minutes to create the cdrs, just export them.

Re: [SR-Users] Kamailio and CDR

Anyone? I can't believe that nobody of Kami users don't have these problems with CDR. 03.04.2019 16:03, Yu Boot пишет: You didn't catch my idea. Here's what Kami writes to syslog:  NOTICE: acc [acc_cdr.c:352]: log_write_cdr(): start_time=1554295999.014; end_time=1554296092.164; duration

Re: [SR-Users] Kamailio and CDR

You can also look at acc_json, you can construct a way to push the acc records to your own backend where you can do whatever suits better for your needs. Cheers, Daniel On 03.04.19 14:31, Yu Boot wrote: Thanks for a reply I need CDR easily "greppable", so it must be in regular text

Re: [SR-Users] Kamailio and CDR

ifferent than using dialog+acc? Cheers, Daniel On 03.04.19 13:27, Yu Boot wrote: Is there any other way to retrieve CDRs from Kami other than dialog/acc modules and writing CDRs to syslog only? Thanks. ___ Kamailio (SER) - Users Mailing List sr-

[SR-Users] Kamailio and CDR

Is there any other way to retrieve CDRs from Kami other than dialog/acc modules and writing CDRs to syslog only? Thanks. ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org

[SR-Users] Kami, rtpproxy, T38 fax - anyone?

Yet again, fighting against strange fax behavior on Kamailio. When call is routed from device behind Kami and uplink is plain old Mediant2000 gateway to E1, T.38 always correctly established via reinvite and fax works perfectly. When call is routed to anything else including local Asterisk or

Re: [SR-Users] Questions

other working solutions like Yate or FreeSwitch. 26.10.2018 9:32, YAS0 CANER пишет: Hello Yu, it isnt related but  i couldnt install rtpengine on Centos(6.X or 7.X) because when start rtpengine or restart system , network interfaces are disappeared. In addition , i think rtpproxy doesnt

[SR-Users] Questions

Hello. Have a following auestions on Kami 4.4.7. Centos 6.9 1. Dialog modules stores entire dialog data in SQL. When I do "kamctl restart", dialog data is still on SQL, but dialog module ignores it and start new dialog. I've expeced previous dialog will be catched up and contonue and finally

Re: [SR-Users] Kamailio as SBC

I can help you with cfg, if you 're ready to implement standalone softswitch on your Kamailio :) 22.10.2018 17:21, Ellad Yatsko пишет: May you help?.. :-) Kind regards, Ellad 22.10.2018 17:12, Alex Balashov пишет: I did not say that my article represents a complete answer to every part of

Re: [SR-Users] rtpproxy or rtpengine with Kamailio and Asterisk

I've tested Kamailio+rtpproxy as a simple softswitch in many configurations including (something)<->Kamailio<->Asterisk. With single interface mode of rtpproxy, it works perfectly. Send your kamailio.cfg, sip.conf and describe your network topology with Kamailio and Asterisk machines. Maybe

Re: [SR-Users] Rtpengine?

Hello. It's not enough to install rtpproxy/rtpengine and start it. You need to call rtpengine functions from kamailio.cfg for every SIP packet with SDP so media will be routed "thru Kamailio". To make it easier, I recommend to begin with rtpproxy, not rtpengine. Default kamailio.cfg

Re: [SR-Users] Module RTPPROXY param Timeout_Socket not Working

Hello. AFAIK rtpproxy timeout socket requires very special version of rtpproxy itself and a patch. Personally, I've gived up to make this feature work. Now I use dialog-based keepalives to detect and tear down dead sessions. 23.07.2018 9:42, Hamid Hashmi пишет: waiting for suggestions.

Re: [SR-Users] SIP re-invite Packets

ReInvites like all in-dialog requests are processed in has_totag()/loose_route part. Default kamailio.cfg has almost identical part for this purpose. Main idea is that an initial request (non in-dialog) hasn't To tag already. It appears only when your request "hits" remote side (called or

[SR-Users] Keep dialog info on Kamailio restart?

Hello. I want that all dialog- and acc- related stuff were saved on kamailio restart and then on Kamailio startup was loaded from SQL tables. dialog settings: modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 1) modparam("dialog", "dlg_flag", 4) modparam("dialog",

Re: [SR-Users] Convert 183+SDP and 180+SDP into a single reply w/SDP

Daniel-Constantin Mierla mico...@gmail.com : >That's indeed much simpler if works. > >Cheers, >Daniel > >On 16.07.18 09:34, Yu Boot wrote: > Thanks for advice. > > I simplify my task a bit by just pass only first 183/180 answer and > then drop everythin

Re: [SR-Users] Convert 183+SDP and 180+SDP into a single reply w/SDP

Thanks for advice. I simplify my task a bit by just pass only first 183/180 answer and then drop everything else. Seems to work properly. 16.07.2018 10:30, Daniel-Constantin Mierla пишет: Hello, if you define an onreply_route[x] to be executed for that invite transaction, you can

[SR-Users] Convert 183+SDP and 180+SDP into a single reply w/SDP

Hello. My uplink usually gives ringback as both 183 Progress with SDP and 180 Ringing also with (different) SDP. One of my clients can't handle that behavior and it just don't plays ringback at all. Is it possible to relay only last provisional response with SDP and drop anything else 183? Any

[SR-Users] Auth and default kami config

Hello. Have a question on auth and default kamailio.cfg. Default behavior of kamailio on auth is: Auth initial requests, delete auth headers before forwarding to next hop. In-dialog requests are forwarded "as-is" so all auth related info is propagated to uplinks or just another Kami users. How

[SR-Users] Add custom parameter to From field

Hello. My carrier requires something like this in From field: From: How to add this parameter after "5060"? ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org

Re: [SR-Users] Kami as NAT traversal + FS as media

ks for advice. 04.01.2018 12:42, Daniel-Constantin Mierla пишет: Hello, On 25.12.17 10:16, Yu Boot wrote: Hello. I want to implement the following scheme: Kami takes inbound call, replces SPD for correct NAT trversal and forward that call to FS. Kami should NOT be in RTP stream. Is it pos

Re: [SR-Users] Best way to do routing against a list of gateways

Hello. Try carrierroute module. Use it with failure_route to iterate thru different gateways from database. 29.11.2017 14:29, voipspace voipspace пишет: Hi I want to build the following scenerio There should be some sort of database table to hold a list of gateway entries with fields ip,

Re: [SR-Users] Set timeout before 180/183 reply arrived

Thanks! 27.10.2017 9:53, Alex Balashov пишет: On Fri, Oct 27, 2017 at 09:44:55AM +0300, Yu Boot wrote: Have a problem with some uplinks. They sometimes respond "100 Trying" on initial INVITE and... that's all. A caller waits for about 30 seconds and cancel a call deciding there's

Re: [SR-Users] Siremis - version from git don't work

For now I can only parse text output with Ruby script. My PHP is too bad to integrate this into Siremis :( 18.09.2017 10:23, Daniel-Constantin Mierla пишет: Great! Have you sorted out xmlrpc or jsonrpc? ___ Kamailio (SER) - Users Mailing List

Re: [SR-Users] Siremis - version from git don't work

Thanks you, now it works 15.09.2017 17:49, Daniel-Constantin Mierla пишет: You need xml rpc extension for php. You may also consider using jsonrpc instead of xmlrpc. ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org

Re: [SR-Users] Siremis - version from git don't work

Thanks, now it is installed and working. But I can't use XMLRPC https://pastebin.com/uDxXeW52 15.09.2017 16:04, Daniel-Constantin Mierla пишет: If you do not have a lot of data that needs to be recreated afterwards (like a lot of admin users), then the simplest way is to delete (make a backup

Re: [SR-Users] Siremis - version from git don't work

Thanks you for an answer. Do I need to delete "siremis" db from mysql to install it? 15.09.2017 15:45, Daniel-Constantin Mierla пишет: Hello, you need to do a fresh installation when using git master branch, including a reset of menu. ___

[SR-Users] Siremis - version from git don't work

Downloaded new Siremis version via "git clone" and replaced /var/www/ content by new files. Now any menu entry gives the following error: https://pastebin.com/hV8ngRVx If if copy old Siremis files back, everything works fine. ___ Kamailio (SER) -

Re: [SR-Users] dialog keep-alive don't work

Timer works OK, now Kami sends BYE to both ends when one peer goes offline. Nice. But that dropped calls don't appear in CDR at all. How to fix it? 11.09.2017 11:26, Daniel-Constantin Mierla пишет: you also need to set the KA property for src or dst:   -

Re: [SR-Users] dialog keep-alive don't work

Thanks you so much :) 11.09.2017 11:26, Daniel-Constantin Mierla пишет: you also need to set the KA property for src or dst:   - https://www.kamailio.org/docs/modules/stable/modules/dialog.html#dialog.f.dlg_set_property ___ Kamailio (SER) -

Re: [SR-Users] Map Technique(Key value pair) in kamailio

You should use this in kamailio.cfg, not in bash :) 11.09.2017 10:09, Logeshwaran G пишет: [root@zeodialer kamailio]# $sht(htable=>91) ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org

Re: [SR-Users] Map Technique(Key value pair) in kamailio

Hello. You can do it easily with dialplan module or any other way to lookup in DB such as sqlops. 11.09.2017 9:26, Logeshwaran G пишет: Key = 91, Value = India Key = 92, Value = Srilanka How to store Key Value Pairs into kamailio and how to Retrieve? If I pass 91 it should Retrieve

[SR-Users] dialog keep-alive don't work

Hello. I'm using following dialog module settings: modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 1) modparam("dialog", "dlg_flag", 4) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "profiles_with_value", "limithash ; caller") modparam("dialog", "ka_timer", 10)

Re: [SR-Users] need some help about acc module

Hello. Take your accounting code for INVITE and copy and modify it like this:     if (is_method("OPTIONS")) {     setflag(FLT_ACC); # do accounting     } 08.09.2017 8:30, Vidja Prashant пишет: Hello, I have some feature required changes in acc module. In acc module we

Re: [SR-Users] Carrierroute, uac_*, failure_route.

Finally I've found dirty hack for that:     remove_hf("From");     insert_hf("From: sip:$fU@my_ip;tag=$fti\r\n"); instead of uac_replace_from()? and similiar for To. So weird that such a simple option requires such hacks and can't be done using standard tools (or I've

Re: [SR-Users] Carrierroute, uac_*, failure_route.

A trick to jump out of first failure route after first call attempt works, and now Kami permits to use uac* functions. But they don't work. From/To remains unchanged on second call. 01.09.2017 8:59, ycaner пишет: hello, i route it another request route, for example. In addition, i remember

[SR-Users] Carrierroute, uac_*, failure_route.

Hello. Have a following task. Select carrier by carrierroute module from db, try to route (dial, relay, bridge - you name it) call there and if call is failed/rejected due to any reason, go to failure_route(?), perform carrierroute lookup again for  another carrier and route call there. Main

Re: [SR-Users] Query in Dialplan module

subst_exp: ^222([0-9]­+)$  And if you call dialplan before lcr, remove 222 from lcr table entries. -- Отправлено из myMail для Android среда, 23 августа 2017г., 12:56 +03:00 от Logeshwaran G logeshwara...@gmail.com : >Hi, > >I have one query in Dialplan module, my scenario is If I call

Re: [SR-Users] rtpproxy rtp timeout

rtpproxy sources... Maybe some patch is required for that option? 22.08.2017 8:02, Maxim Sobolev пишет: Hi. 2.1 is the version we recommend using. -Max On Aug 21, 2017 1:22 PM, <y...@yu-boot.ru <mailto:y...@yu-boot.ru>> wrote: Hello. What version of rtpproxy app s

[SR-Users] Save original $fU, $rU

Have a problem with Asterisk. When callee behind Asterisk hangs up first, it sends back BYE with swapped From and To fields, which affects Kami CDRs rendering them useless. I've tried to save original From/To to AVPs on initial INVITE but they are empty when CDR is written. How to solve this?

[SR-Users] dp_translate_cr_route, R-URI

Hello. #cut off prefix "9"     dp_translate("1"); ... #searching in db by called number without prefix...  if(!cr_route("default", "default", "$rU", "$rU", "call_id")){ ... and failing. Is it normal behavior that cr_route "sees" original $rU even after dp_translate manipulations?

Re: [SR-Users] Siremis - can't add carrier without prefix/suffix

Oh, thanks you so much, it's exactly what I've wanted. 22.08.2017 9:25, Daniel-Constantin Mierla пишет: Try with latest master, I changed corresponding Required flags for those fields to N (no). Not being that familiar with carrierrroute module, should other fields need something similar, you

Re: [SR-Users] rtpproxy: One direction rtp not being relayed

Use sngrep to see SIP packets internals, look for c= and o= fields in SDP and for reINVITE events. And post your kamailio.cfg to pastebin.com please. -- Отправлено из myMail для Android вторник, 22 августа 2017г., 14:53 +03:00 от Jon Bonilla (Manwe) ma...@aholab.ehu.es : >Hi all > >After a

Re: [SR-Users] rtpproxy rtp timeout

Thanks for an answer. Where to get it? Google knows only about 2.0 :( -- Отправлено из myMail для Android вторник, 22 августа 2017г., 08:02 +03:00 от Maxim Sobolev sobo...@sippysoft.com : >Hi. 2.1 is the version we recommend using.  > >-Max > >On Aug 21, 2017 1:22 PM, &l

Re: [SR-Users] allow inbound calls from any ip

You need to remove any IP checks in cfg. AFAIR they are in AUTH and PSTN sections if you use default Kami config. -- Отправлено из myMail для Android понедельник, 21 августа 2017г., 12:35 +03:00 от Logeshwaran G logeshwara...@gmail.com : >Hi, > >I need to allow the inbound calls from any ip i

Re: [SR-Users] Siremis - can't add carrier without prefix/suffix

Here is it: http://imgur.com/SrK1UO1 21.08.2017 8:27, Daniel-Constantin Mierla пишет: Hello, the link to screenshot does not show any image. Have you remove it? Cheers, Daniel On 20.08.17 16:00, Yu Boot wrote: Hello Suddenly revealed that I can't add carriers without rewrite_prefix

[SR-Users] Siremis - can't add carrier without prefix/suffix

Hello Suddenly revealed that I can't add carriers without rewrite_prefix/rewrite_suffix via Siremis. But I don't need these fields! And kamctl adds these rules fine. What's a problem? Screenshot with error http://tinypic.com/r/68v493/9 ___

[SR-Users] syslog CDR time format

Hello. Can't get 'date-time' format timestamps in syslog CDRs, while SQL CDRs are OK. According to acc module documentation: modparam("acc", "cdr_enable", 1) modparam("acc", "time_format", "%Y-%m-%d %H:%M:%S") modparam("acc", "time_mode", 3) modparam("acc", "cdr_facility", "LOG_DAEMON")

Re: [SR-Users] Siremis Install: Unable to write in the session save path (CentOS 6)

use following command: chcon -t httpd_sys_content_t /var/www/html -R or just disable SELinux globally 16.08.2017 0:34, Trent пишет: Full error: Unable to write in the session save path [/var/www/html/siremis/session]Unable to write in the session save path

[SR-Users] [Solved] Re: Reinvite, rewrite reply SDP?

("rtpproxy", "nortpproxy_str", "") Pretty dumb solution, but for now it finally works. Sorry for annoying :) 14.08.2017 12:55, Yu Boot пишет: Finally I find a root of a problem with my T.38 reinvites. A->(NAT)->Kami->PSTN When NATted caller does reinvite, and

[SR-Users] Reinvite, rewrite reply SDP?

Finally I find a root of a problem with my T.38 reinvites. A->(NAT)->Kami->PSTN When NATted caller does reinvite, and remote side answers with 200 OK+SDP, Kami (why?) doesn't rewrite SDP for its own IP (so NATted caller can receive RTP) and leaves remote's IP as media address, so of course

[SR-Users] Carrierroute, fallback, reinvites

Hello. Trying to implement fallback route for carrierroute and got sick to make reinvites working correctly. Until fallback route triggers, everything is OK. Anyone has working config for that purposes (NAT traversal, reinvites, carrierroute ), please? And abstract question - is it generally a

Re: [SR-Users] [ *SPAM* 2.2 ] Re: "kamctl restart" fails

# grep PID /etc/kamailio/kamctlrc ## PID file path - default is: /var/run/kamailio.pid PID_FILE=/var/run/kamailio.pid I've stopped Kami entirely, deleted that .pid. Now: # kamctl restart INFO: Stopping Kamailio : INFO: stopped INFO: Starting Kamailio : 3069 pts/0S+ 0:00 /bin/egrep

[SR-Users] [ *SPAM* 3.0 ] Re: [ *SPAM* 2.2 ] Re: carrierroute and failure route

Can you provide 100% working Kami config with correct NAT traversal and REINVITE please? -- Отправлено из myMail для Android понедельник, 07 августа 2017г., 13:08 +03:00 от Sebastian Damm d...@sipgate.de : >Hi, > >On Sat, Aug 5, 2017 at 7:00 PM, Yu Boot < y...@yu-boot.ru > w

[SR-Users] "kamctl restart" fails

# kamctl restart INFO: Stopping Kamailio : INFO: stopped INFO: Starting Kamailio : 2292 pts/0S+ 0:00 /bin/egrep kamailio -rw-r--r--. 1 kamailio kamailio 5 Aug 8 11:15 /var/run/kamailio.pid INFO: PID file exists (/var/run/kamailio.pid)! Kamailio already running? "service kamailio

Re: [SR-Users] carrierroute and failure route

#here we go fix_nated_contact(); set_contact_alias(); } setflag(FLT_NATS); } #!endif return; } 04.08.2017 16:27, Yu Boot пишет: Played some time with sngrep and wire

Re: [SR-Users] [ *SPAM* 5.1 ] Re: carrierroute and failure route

and t_relay to actually send created message, isn't it? 04.08.2017 13:26, Sebastian Damm пишет: Hi, On Thu, Aug 3, 2017 at 3:45 PM, Yu Boot <y...@yu-boot.ru> wrote: I use this in WITHINDLG to handle reINVITEs else if ( is_method("INVITE") ) { record_r

Re: [SR-Users] [ *SPAM* 5.1 ] Re: carrierroute and failure route

I use this in WITHINDLG to handle reINVITEs else if ( is_method("INVITE") ) { record_route(); or T.38 fax behind NAT doesn't work at all. 03.08.2017 15:14, Sebastian Damm пишет: Hi, On Thu, Aug 3, 2017 at 12:48 PM, Yu Boot <y...@yu-boot.ru> wr

[SR-Users] T.38 fax, rtpproxy, re-invite

Hello. I'm using almost default kamailio.cfg with nathelper, rtpproxy, PSTN dialing and other default features. I have following scheme: FXS gateway -> (NAT) -> Kamailio -> FreeSwitch Voice calls work perfectly, no one-direction sound and so on. But with fax machine there was a problem. In

[SR-Users] [ *SPAM* 2.0 ] Re: Kamailio CDR "best practices"

31.07.2017 17:35, Daniel-Constantin Mierla пишет: On 31.07.17 13:18, Yu Boot wrote: How to make Kamailio write "normal" CDRs? Can you provide more details about what you consider a 'normal' CDR? It is hard to guess what you expect here. Like Asterisk/FS/Yate one :) sourceIP

[SR-Users] Kamailio CDR "best practices"

How to make Kamailio write "normal" CDRs? acc cdr module writes start time and end time in unixtime format, that is very uncomfortable. Fnd stcond question - how to make Kamailio to write CDR in ordinary text file? ___ Kamailio (SER) - Users