Re: [SR-Users] Fwd: kemi lua routing block as route in standart cfg

Hello, where is that TBD note? It needs to be adjusted, probably it is a leftover from first days of this feature. The failure_route, branch_route and onreply_route can be now natively in the embedded language, see the Lua script example I provide with the link in my previous email. If you are

[SR-Users] Kamailio inserting Quote " mark in SIP header

Hi All, We are seeing that Kamailio's nat_helper_module function of add_rcv_param(), inserts " (quote) mark to some of the SIP headers (as below in the contact header in sip 200 OK response) Contact: ;expires=172 We got few SIP

Re: [SR-Users] Kamailio example configuration: auth section incomplete?

Hi George, Kamailio is very flexible application and don't be afraid to change default config file. ;) So if default config file do not fit you, just update accordingly. With kind regards, Jurijs On Wed, Aug 2, 2017 at 10:17 PM, George Diamantopoulos wrote: > Sorry, I

Re: [SR-Users] Kamailio example configuration: auth section incomplete?

Sorry, I replied before I could read your second post. Ah, I can see now where this is going, although it's completely unfit for the use of kamailio I'm investigating. Thanks! On 2 August 2017 at 22:11, Jurijs Ivolga wrote: > Hi George, > > I misread your email, sorry.

Re: [SR-Users] Kamailio example configuration: auth section incomplete?

Hey, Thanks for the reply! Actually it's the entire logic that baffles me. It is not uncommon for a UAC (say at 192.168.1.1) to send out an INVITE which is formed like this: * R-URI: kamailio's URI * From: username@192.168.1.1 * To: irrelevant What I'm saying is that this SIP message will fail

Re: [SR-Users] Kamailio example configuration: auth section incomplete?

Hi George, I misread your email, sorry. In your case scenario is when somebody from outside tries to call user registered in kamailio, by default it is allowed. We do not need to challenge such request, because it is user from outside, not our subscriber and by default kamailio allows such calls

Re: [SR-Users] Issue with ims_isc module? (distinct PSI)

Hi Daniel and Carsten, Thanks for this honest explanation of the problem. After vacation, this is the first time I scan the SR-USERS e-mails and hence am a little bit late with my response. Well, we can do more investigation. However, we have found a way to send unregistered terminating

Re: [SR-Users] Kamailio example configuration: auth section incomplete?

Hi George, If you are asking about this part: if (from_uri!=myself && uri!=myself) { sl_send_reply("403","Not relaying"); exit; } Then this mean that we do not want to deal with sip requests which not send to us or not by us. So any request which is not related to us we will

[SR-Users] SIP Proxy/Redirect

Hi All, Hoping for some help as a beginner. I need to configure a sip proxy server so that it redirects all processes to a freeswitch server on another network. SIP UACs are on an isolated network and have only a connection to the sip proxy. All I need the proxy to do is pass on all requests to

[SR-Users] Fwd: kemi lua routing block as route in standart cfg

thx. I just thought that it's possibe to concatenate both engines together. So this is my last question regardng kemi: Main goal why i still not use kemi at the my projects is a: TBD: the options for specific event_route blocks. Meanwhile, should work using hybrid configuration with

Re: [SR-Users] kemi lua routing block as route in standart cfg

Hello, if you want to do routing in lua via kemi, the kamailio.cfg has only the passive part (global parameters, loading modules and modparams) and the active part (routing blocks) is a separate file written in the desired scripting language (e.g., lua). See examples: -

Re: [SR-Users] Reverse DNS lookups inside Kamailio

Hello, On 01.08.17 17:06, Sebastian Damm wrote: > Hi, > > for a project I need the option to do a reverse lookup of an IP > address and use the value from it in a variable. > > As far as I could see the ipops module only allows SRV and A record > lookups. Is there anything I missed? > > And if

Re: [SR-Users] kemi lua routing block as route in standart cfg

Hi, no I wanna include lua routes part at existing kamailio.cfg file Just wanna rewrite some route with lua code using kemi because lua more flexible for my needs, but want to call this route at the cfg file. like kamailio.cfg ... route { [MY_SUPER_ROUTE_IN_LUA] } ... Where

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

Hello, On 02.08.17 12:02, Yu Boot wrote: > 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

Re: [SR-Users] kemi lua routing block as route in standart cfg

Hello, On 02.08.17 12:02, Yuriy Gorlichenko wrote: > Hello. I found how to implement lua routimg logic with > cfgengine but didn't found how to include cimple route in lua at the > cfg file > > Presume i have routing logic and want to include > my_super_custom_route written with Kemo on lua.

[SR-Users] kemi lua routing block as route in standart cfg

Hello. I found how to implement lua routimg logic with cfgengine but didn't found how to include cimple route in lua at the cfg file Presume i have routing logic and want to include my_super_custom_route written with Kemo on lua. How i need to set up my config for it work with both engines?

[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 (detected with