Re: [SR-Users] "Sleeping Giant - No Snore" Kam?

[Alex Balashov]

What you want there is the 'ctl' module and the 'kamcmd' utility that comes 
with Kamailio.

# kamcmd ls

Gets a list of available RPC commands from all loaded modules + core.

Beware that if you put the ctl socket in a nonstandard place, you'll need to 
specify the path via the '-s' option to kamcmd. 

-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] "Sleeping Giant - No Snore" Kam?

[KamDev Essa]

 Awesome note. 
How does one fire the RPC command. Whats the interface? Any docs on that?
KD
On Wednesday, May 9, 2018, 10:06:35 PM EDT, Alex Balashov 
 wrote:  
 
 There are a lot of options here.

For source IPs and subnets, the `permissions` module probably works
best:

https://kamailio.org/docs/modules/5.1.x/modules/permissions.html

While it can function in a mode where it bangs on your database for
every request, it also supports a caching mode (db_mode 1):

https://kamailio.org/docs/modules/5.1.x/modules/permissions.html#permissions.p.db_mode

In caching mode, it loads the ACL from the database once on startup and
keeps it in memory. If you have made alterations to the database table
and want to kick Kamailio to reload it, there are management/RPC commands for 
that[2]:

https://kamailio.org/docs/modules/5.1.x/modules/permissions.html#permissions.r.trustedReload
https://kamailio.org/docs/modules/5.1.x/modules/permissions.html#permissions.r.addressReload

Note that in a lot of scenarios, use of the permissions module isn't
truly necessary because some other module provides a de facto ACL. For
example, if you are using the dispatcher[1] module to front-end a group
of servers for round-robin type load balancing, making routing decisions
based on whether the origin is within the dispatcher server pool seems
only natural[2]:

  if(ds_is_from_list("1")) { 
      # Allow from own application server farm.
}

For filtering out nonlocal URI domains, the `domain` module presents a
natural fit. It works much as `permissions` does in terms of in-memory
caching and that:

https://kamailio.org/docs/modules/5.1.x/modules/domain.html

And if you should find that these modules' data model doesn't
schematically meet your needs, you can always seed your own `htable`
values from a DB-backed hash table:

https://kamailio.org/docs/modules/5.1.x/modules/htable.html#htable.p.db_url

Or fetch these values from somewhere else (e.g. HTTP API) and inject
them into an htable upon startup:

https://kamailio.org/docs/modules/5.1.x/modules/htable.html#idp49461924

Lots of options...

-- Alex

[1] https://kamailio.org/docs/modules/5.1.x/modules/dispatcher.html

[2] 
https://kamailio.org/docs/modules/5.1.x/modules/dispatcher.html#dispatcher.f.ds_is_from_list

On Wed, May 09, 2018 at 09:04:16PM +, KamDev Essa wrote:

>  easy. Not one of my domains or source IPs. Unless hackers is ex user they 
>would never know my list. 
> KD
>    On Wednesday, May 9, 2018, 4:53:21 PM EDT, Alex Balashov 
> wrote:  
>  
>  How would you define "foes" in a programmatic sense? :) That will dictate 
>the answer. 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity. 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>  

> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 Update : I piggy backed Freeswitch to Kamailio and have resolved the issue. No 
media touching us now. Pros and Cons for doing that I know. But we have it 
working.
Thanks for the dialog. 
KD
On Wednesday, May 9, 2018, 8:57:49 PM EDT, KamDev Essa 
 wrote:  
 
  Response from the carrier matches your description. Looks like their Inbound 
carrier is latching but the outbound carrier is not and yes they recommended 
handling the NAT on my end.
That said, whats my options here. Is the native rtpproxy scalable? or is it 
better to go with a Freeswitch farm to handle media proxying. We are looking @ 
holding in upwards of 10K UAs on one instance of Kamailio. So whats the best 
architecture or that ?
H 
On Wednesday, May 9, 2018, 5:53:55 PM EDT, Alex Balashov 
 wrote:  
 
 Re-read the piece of the article related to "RTP latching":

http://blog.csrpswitch.com/server-side-nat-traversal-with-kamailio-the-definitive-guide/

In order for RTP to reach a NAT'd endpoint, all other things being
equal, the other party has to do RTP latching. This is true of both
inbound and outbound calls. Failure to do it will result in one-way
audio where the NAT'd party can transmit but cannot receive. 

As far as identifying who is doing that latching, that's not clear from
your description. Some carrier media gateways do it, in which case you
can get away with not having an RTP relay in the middle. Most carrier
media gateways are designed for wholesale-ish peering and don't, as a
matter of policy, but some do. Or you could have some near-end solutions
at work of which you're not aware. 

It's also not clear whether you've definitively removed all rtpproxy
invocation from your Kamailio config, in both directions. But if you
haven't, I'd start there, and given your statement that you don't really
want to be in series to the RTP path, figure out what exactly doesn't
work. Then add rtpproxy as necessary. Beware the distinction between
inbound and outbound call flows.

-- Alex

On Wed, May 09, 2018 at 09:15:48PM +, KamDev Essa wrote:

>  Well then why does Inbound (from carrier to NATed UA) call work. Kam is 
>doing something clever there. Why not when sending the call out. 
> KD  
>    On Wednesday, May 9, 2018, 4:34:55 PM EDT, Alex Balashov 
> wrote:  
>  
>  Oh, the UAs are NAT'd? Yeah, you're going to need something clever in the 
>middle that can do the RTP latching, then. 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity.  

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] "Sleeping Giant - No Snore" Kam?

[Alex Balashov]

There are a lot of options here.

For source IPs and subnets, the `permissions` module probably works
best:

https://kamailio.org/docs/modules/5.1.x/modules/permissions.html

While it can function in a mode where it bangs on your database for
every request, it also supports a caching mode (db_mode 1):

https://kamailio.org/docs/modules/5.1.x/modules/permissions.html#permissions.p.db_mode

In caching mode, it loads the ACL from the database once on startup and
keeps it in memory. If you have made alterations to the database table
and want to kick Kamailio to reload it, there are management/RPC commands for 
that[2]:

https://kamailio.org/docs/modules/5.1.x/modules/permissions.html#permissions.r.trustedReload
https://kamailio.org/docs/modules/5.1.x/modules/permissions.html#permissions.r.addressReload

Note that in a lot of scenarios, use of the permissions module isn't
truly necessary because some other module provides a de facto ACL. For
example, if you are using the dispatcher[1] module to front-end a group
of servers for round-robin type load balancing, making routing decisions
based on whether the origin is within the dispatcher server pool seems
only natural[2]:

   if(ds_is_from_list("1")) { 
# Allow from own application server farm.
}

For filtering out nonlocal URI domains, the `domain` module presents a
natural fit. It works much as `permissions` does in terms of in-memory
caching and that:

https://kamailio.org/docs/modules/5.1.x/modules/domain.html

And if you should find that these modules' data model doesn't
schematically meet your needs, you can always seed your own `htable`
values from a DB-backed hash table:

https://kamailio.org/docs/modules/5.1.x/modules/htable.html#htable.p.db_url

Or fetch these values from somewhere else (e.g. HTTP API) and inject
them into an htable upon startup:

https://kamailio.org/docs/modules/5.1.x/modules/htable.html#idp49461924

Lots of options...

-- Alex

[1] https://kamailio.org/docs/modules/5.1.x/modules/dispatcher.html

[2] 
https://kamailio.org/docs/modules/5.1.x/modules/dispatcher.html#dispatcher.f.ds_is_from_list

On Wed, May 09, 2018 at 09:04:16PM +, KamDev Essa wrote:

>  easy. Not one of my domains or source IPs. Unless hackers is ex user they 
> would never know my list. 
> KD
> On Wednesday, May 9, 2018, 4:53:21 PM EDT, Alex Balashov 
>  wrote:  
>  
>  How would you define "foes" in a programmatic sense? :) That will dictate 
> the answer. 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity. 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>   

> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Build Kamailio with MariaDB failed.

[Ye, Charlie (NSB - CN/Qingdao)]

Hi all,

Thanks for your nice help!
I have built Kamailio successfully. I just created a new link to libmysqld.so 
in /usr/lib64.

Thanks and Best Regards,
Charlie

From: Sergey Safarov [mailto:s.safa...@gmail.com]
Sent: 2018年5月9日 21:41
To: mico...@gmail.com; Kamailio (SER) - Users Mailing List 

Cc: Ye, Charlie (NSB - CN/Qingdao) 
Subject: Re: [SR-Users] Build Kamailio with MariaDB failed.

Need to install mysql-devel
https://github.com/kamailio/kamailio/blob/master/pkg/kamailio/obs/kamailio.spec#L554

And then apply Daniel recommendations.

ср, 9 мая 2018 г. в 14:42, Daniel-Constantin Mierla 
>:

Hello,

can you go to src/modules/db_mysql and run:

make clean

make Q=0

and send the output here?

Cheers,
Daniel

On 09.05.18 10:46, Ye, Charlie (NSB - CN/Qingdao) wrote:
Hi Daniel,

Please find my answer as below:

The operating system: Red Hat Enterprise Linux Server release 7.4 (Maipo).

I didn’t modify the Makefile, only include db_mysql module when made cfg.




Thanks and Best Regards,
Charlie

From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: 2018年5月9日 16:27
To: Kamailio (SER) - Users Mailing List 
; Ye, Charlie 
(NSB - CN/Qingdao) 

Subject: Re: [SR-Users] Build Kamailio with MariaDB failed.


Hello,

what operating system are you using?

Have you done any changes to the Makefiles, or is just stock Kamailio?

Cheers,
Daniel

On 09.05.18 10:23, Ye, Charlie (NSB - CN/Qingdao) wrote:
Hi all,

Does everyone use MariaDB in Kamailio? When I built Kamailio with MariaDB, the 
below error happened. Would anyone give a help? Thanks in advance!

[root@clcmos /usr/local/src/kamailio-devel/kamailio]$ # make all
make -C src/ all
make[1]: Entering directory `/usr/local/src/kamailio-devel/kamailio/src'
make[3]: `libsrdb2.so.1.0' is up to date.
make[3]: `libsrdb1.so.1.0' is up to date.
LD (gcc) [M db_mysql.so]db_mysql.so
/usr/bin/ld: cannot find -lmariadb
collect2: error: ld returned 1 exit status
make[2]: *** [db_mysql.so] Error 1
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/local/src/kamailio-devel/kamailio/src'
make: *** [all] Error 2



Thanks and Best Regards,
Charlie




___

Kamailio (SER) - Users Mailing List

sr-users@lists.kamailio.org

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--

Daniel-Constantin Mierla

www.twitter.com/miconda -- 
www.linkedin.com/in/miconda

Kamailio World Conference - May 14-16, 2018 - 
www.kamailioworld.com



--

Daniel-Constantin Mierla

www.twitter.com/miconda -- 
www.linkedin.com/in/miconda

Kamailio World Conference - May 14-16, 2018 - 
www.kamailioworld.com
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 Response from the carrier matches your description. Looks like their Inbound 
carrier is latching but the outbound carrier is not and yes they recommended 
handling the NAT on my end.
That said, whats my options here. Is the native rtpproxy scalable? or is it 
better to go with a Freeswitch farm to handle media proxying. We are looking @ 
holding in upwards of 10K UAs on one instance of Kamailio. So whats the best 
architecture or that ?
H 
On Wednesday, May 9, 2018, 5:53:55 PM EDT, Alex Balashov 
 wrote:  
 
 Re-read the piece of the article related to "RTP latching":

http://blog.csrpswitch.com/server-side-nat-traversal-with-kamailio-the-definitive-guide/

In order for RTP to reach a NAT'd endpoint, all other things being
equal, the other party has to do RTP latching. This is true of both
inbound and outbound calls. Failure to do it will result in one-way
audio where the NAT'd party can transmit but cannot receive. 

As far as identifying who is doing that latching, that's not clear from
your description. Some carrier media gateways do it, in which case you
can get away with not having an RTP relay in the middle. Most carrier
media gateways are designed for wholesale-ish peering and don't, as a
matter of policy, but some do. Or you could have some near-end solutions
at work of which you're not aware. 

It's also not clear whether you've definitively removed all rtpproxy
invocation from your Kamailio config, in both directions. But if you
haven't, I'd start there, and given your statement that you don't really
want to be in series to the RTP path, figure out what exactly doesn't
work. Then add rtpproxy as necessary. Beware the distinction between
inbound and outbound call flows.

-- Alex

On Wed, May 09, 2018 at 09:15:48PM +, KamDev Essa wrote:

>  Well then why does Inbound (from carrier to NATed UA) call work. Kam is 
>doing something clever there. Why not when sending the call out. 
> KD  
>    On Wednesday, May 9, 2018, 4:34:55 PM EDT, Alex Balashov 
> wrote:  
>  
>  Oh, the UAs are NAT'd? Yeah, you're going to need something clever in the 
>middle that can do the RTP latching, then. 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity.  

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Auth module with shared "secret"

[Asgaroth]

Hi All,

Does anyone have any thoughts on how I can debug this further, I'm 
currently stumped as to what steps to take to see why these messages are 
failing authentication.


Any suggestions appreciated.

Thanks


On 03/05/18 11:02, Asgaroth wrote:

Hi All,

I am testing a scenario where we have 3 proxies and I'm trying to 
ensure that if a messages comes in to 1 proxy, which challenges the 
ua, is able to be auth'd successfully on one of the remaining 2 
proxies if, for some reason the ua decides to send the response to one 
of the remaining two proxies.


I am testing this using a seperate kamailio proxy which loadbalances 
messages across the 3 proxies that I am testing with. I have 1 ua 
(zoiper) which I tell to subscribe for mwi, the initial subscribe is 
sent to proxy 1, which sends a 407 back, the new subscribe with auth, 
from the ua, is sent to proxy 2, which deems the nonce as expired and 
rechallenges, this continues in a loop across the 3 proxies and never 
authenticates.


I think I'm missing something in my settings that I just cannot put my 
finger on, and/or, I'm mis-understanding the documentation and how 
these settings interact with each other.


My auth module settings are as follows:

#
# - auth params -
#
modparam("auth", "qop", "auth")
modparam("auth", "nonce_count", 1)
modparam("auth", "one_time_nonce", 1)
modparam("auth", "nid_pool_no", 4)
modparam("auth", "nc_array_size", 4194304)
modparam("auth", "otn_in_flight_no", 8388608)
modparam("auth", "auth_checks_no_dlg", 9)
modparam("auth", "auth_checks_in_dlg", 15)
modparam("auth", "auth_checks_register", 11)
modparam("auth", "secret", "secret_32_char_str")

I tried with one_time_nonce enabled and disabled but the result is the 
same, continous rechallenge.


The documentation mentions that if nonce_count and one_time_nonce are 
enable, and a ua sends a response with nonce and qop in the auth 
header then one_time_nonce will not be used, one_time nonce will be 
used as a fallback in the case the ua does not support qop.


My auth block in the routing logic looks like so:

route[AUTH_CHECK]{
    xlog("L_DBG", "route[AUTH_CHECK] : $rm : Performing authentication 
checks for '$var(creds_key)'");

    $var(challenge_flags) = 1;
    if ( ! pv_auth_check("$fd", 
"$sht(creds=>$var(creds_key)::Password)", "20", "1") ) {

    switch($retcode) {
    case -1:
    xlog("L_DBG", "route[AUTH_CHECK] : $rm : Generic error 
occurred, no reply sent out.");

    break;
    case -2:
    xlog("L_DBG", "route[AUTH_CHECK] : $rm : Invalid 
password supplied, re-challenging client and removing from hash table.");

    sht_rm_name_re("creds=>$var(creds_key)");
    break;
    case -4:
    xlog("L_DBG", "route[AUTH_CHECK] : $rm : Nonce has 
expired, re-challenging client.");

    $var(challenge_flags) = $var(challenge_flags) + 16;
    break;
    case -5:
    xlog("L_DBG", "route[AUTH_CHECK] : $rm : No 
credentials supplied, challenging client.");

    break;
    case -6:
    xlog("L_DBG", "route[AUTH_CHECK] : $rm : Nonce has 
already been used to auth a previous request, challenging client.");

    break;
    case -8:
    xlog("L_DBG", "route[AUTH_CHECK] : $rm : Auth user is 
different to From/To user, challenging client.");

    break;
    }
    xlog("L_INFO", "route[AUTH_CHECK] : $rm : auth_challenge will 
be called with '$fd' and '$var(challenge_flags)'");

    auth_challenge("$fd", "$var(challenge_flags)");
    exit;
    }
    consume_credentials();
}

When I look at the logs I always see the proxies seeing the nonce as 
expired:


oUBGp0n6HRWu_mvPPxJQqg..: INFO: 

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[Alex Balashov]

Re-read the piece of the article related to "RTP latching":

http://blog.csrpswitch.com/server-side-nat-traversal-with-kamailio-the-definitive-guide/

In order for RTP to reach a NAT'd endpoint, all other things being
equal, the other party has to do RTP latching. This is true of both
inbound and outbound calls. Failure to do it will result in one-way
audio where the NAT'd party can transmit but cannot receive. 

As far as identifying who is doing that latching, that's not clear from
your description. Some carrier media gateways do it, in which case you
can get away with not having an RTP relay in the middle. Most carrier
media gateways are designed for wholesale-ish peering and don't, as a
matter of policy, but some do. Or you could have some near-end solutions
at work of which you're not aware. 

It's also not clear whether you've definitively removed all rtpproxy
invocation from your Kamailio config, in both directions. But if you
haven't, I'd start there, and given your statement that you don't really
want to be in series to the RTP path, figure out what exactly doesn't
work. Then add rtpproxy as necessary. Beware the distinction between
inbound and outbound call flows.

-- Alex

On Wed, May 09, 2018 at 09:15:48PM +, KamDev Essa wrote:

>  Well then why does Inbound (from carrier to NATed UA) call work. Kam is 
> doing something clever there. Why not when sending the call out. 
> KD  
> On Wednesday, May 9, 2018, 4:34:55 PM EDT, Alex Balashov 
>  wrote:  
>  
>  Oh, the UAs are NAT'd? Yeah, you're going to need something clever in the 
> middle that can do the RTP latching, then. 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity.  

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 Well then why does Inbound (from carrier to NATed UA) call work. Kam is doing 
something clever there. Why not when sending the call out. 
KD  
On Wednesday, May 9, 2018, 4:34:55 PM EDT, Alex Balashov 
 wrote:  
 
 Oh, the UAs are NAT'd? Yeah, you're going to need something clever in the 
middle that can do the RTP latching, then. 

-- Alex

--
Sent via mobile, please forgive typos and brevity.  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Parse presece xml and put stats into asterisk database

[Aqs Younas]

Greetings list,

I need to put presence info of a device into asterisk database through
sqlops module.

Currently, i opt to use a lua script to parse xml body of PUBLISH packet
issued by pua_dialoginfo and insert trying/ringing stats into asterisk
database.

Is there any better way to accomplish this?

Best Regards,

Aqs Younas
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] "Sleeping Giant - No Snore" Kam?

[KamDev Essa]

 easy. Not one of my domains or source IPs. Unless hackers is ex user they 
would never know my list. 
KD
On Wednesday, May 9, 2018, 4:53:21 PM EDT, Alex Balashov 
 wrote:  
 
 How would you define "foes" in a programmatic sense? :) That will dictate the 
answer. 

-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] "Sleeping Giant - No Snore" Kam?

[Alex Balashov]

How would you define "foes" in a programmatic sense? :) That will dictate the 
answer. 

-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] "Sleeping Giant - No Snore" Kam?

[KamDev Essa]

We have noticed pesky SIP hackers already knocking on our POC servers. Kam is 
holding the fort by sending out the proverbial 401/407 (snore). I can SQLOPS to 
do a dip to check destination domain or Source IP and nix the snore for alien 
requests, but wanted to know if there was a native way to keep silent when we 
have a request from foes.
KD ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 Update. I just checked inbound calls using the "rtpproxy clean" cfg. 
Inbound calls from Carrier to UA work fine with bidirectional RTP. Its the 
outbound calls from UA to carrier that have a NAT issue.
I am so close :) 
KD
On Wednesday, May 9, 2018, 4:29:39 PM EDT, KamDev Essa 
 wrote:  
 
  That did not help. sip capture shows NATed SDP being sent to carrier. 
Obviously carrier will not be able to make head nor tails about it. And carrier 
SDP sent to UA is perfect as its not NATed. So UA ===> Carrier is fine. Carrier 
> UA is no RTP.  Does not look like Kam alone can do RTP relase between 
NATed UA and the outside network entity. 
I will try Freeswitch piggy back and then let Freeswitch bypass media. Logic in 
Freeswitch may do the trick.   \
KD 
On Wednesday, May 9, 2018, 3:30:26 PM EDT, Alex Balashov 
 wrote:  
 
 You'll want to not load the rtpproxy module, and lose any rtpproxy_*() calls 
in the actual script. 

On May 9, 2018 3:26:43 PM EDT, KamDev Essa  wrote:
>If I comment out the modparam("rtpproxy", "rtpproxy_sock",
>"udp:127.0.0.1:7722") as suggested, I do get RTP flowing just in one
>direction.  From the UA to kam and out to the carrier. I get nothing
>geting back to the end point. In other words 1 way RTP. Looks like its
>Kam RTPProxy or bust.
>KD
>On Wednesday, May 9, 2018, 2:38:08 PM EDT, Alex Balashov
> wrote:  
> 
>Correct. So remove all semblance of any RTP proxy and the resulting
>behaviour will be exactly what you expect. 
>
>On May 9, 2018 2:13:22 PM EDT, KamDev Essa 
>wrote:
>>I dont. I want the 2 end points to talk to each other because I am on
>>AWS with shaky bandwidth stats. It can handle signalingbut not RTP. 
>>However the cfg entry modparam("rtpproxy", "rtpproxy_sock",
>>"udp:127.0.0.1:7722") gives me to believe (not tcdumped RTP ports yet
>>to prove it ) that Kam anchors RTP @ port 7722. 
>>KD  
>>On Wednesday, May 9, 2018, 2:02:14 PM EDT, Alex Balashov
>> wrote:  
>> 
>>That depends. Start with a more basic question: why do you need RTP
>>relay in the middle at all? 
>>
>>On May 9, 2018 1:54:55 PM EDT, KamDev Essa 
>>wrote:
>>>So all calls that kamailio processes using the default cfg file
>anchor
>>>RTP on the kamailio server? Is it a best architecture to farm out RTP
>>>to Freeswitch? Or is the Kamailio RTP proxy a better gig?
>>>KD
>>>On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov
>>> wrote:  
>>> 
>>>Ironically, nothing. Kamailio doesn't touch the respective parties'
>>SDP
>>>unless you invoke an RTP relay (or something else like
>>>fix_nated_sdp()). 
>>>
>>>On May 9, 2018 1:03:19 PM EDT, KamDev Essa 
>>>wrote:
What cfg files changes do I need to make to get Kamailio to be a
signally only server, yet manipulate the SDP part of the INVITE
>>>message
to allow remote parties to send media to each other? In Freeswitch
terms "bypassmedia".
KD
>>>
>>>
>>>-- Alex
>>>
>>>--
>>>Sent via mobile, please forgive typos and brevity. 
>>>
>>>___
>>>Kamailio (SER) - Users Mailing List
>>>sr-users@lists.kamailio.org
>>>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>  
>>
>>
>>-- Alex
>>
>>--
>>Sent via mobile, please forgive typos and brevity.  
>
>
>-- Alex
>
>--
>Sent via mobile, please forgive typos and brevity.  


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[Alex Balashov]

Oh, the UAs are NAT'd? Yeah, you're going to need something clever in the 
middle that can do the RTP latching, then. 

-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 That did not help. sip capture shows NATed SDP being sent to carrier. 
Obviously carrier will not be able to make head nor tails about it. And carrier 
SDP sent to UA is perfect as its not NATed. So UA ===> Carrier is fine. Carrier 
> UA is no RTP.  Does not look like Kam alone can do RTP relase between 
NATed UA and the outside network entity. 
I will try Freeswitch piggy back and then let Freeswitch bypass media. Logic in 
Freeswitch may do the trick.   \
KD 
On Wednesday, May 9, 2018, 3:30:26 PM EDT, Alex Balashov 
 wrote:  
 
 You'll want to not load the rtpproxy module, and lose any rtpproxy_*() calls 
in the actual script. 

On May 9, 2018 3:26:43 PM EDT, KamDev Essa  wrote:
>If I comment out the modparam("rtpproxy", "rtpproxy_sock",
>"udp:127.0.0.1:7722") as suggested, I do get RTP flowing just in one
>direction.  From the UA to kam and out to the carrier. I get nothing
>geting back to the end point. In other words 1 way RTP. Looks like its
>Kam RTPProxy or bust.
>KD
>On Wednesday, May 9, 2018, 2:38:08 PM EDT, Alex Balashov
> wrote:  
> 
>Correct. So remove all semblance of any RTP proxy and the resulting
>behaviour will be exactly what you expect. 
>
>On May 9, 2018 2:13:22 PM EDT, KamDev Essa 
>wrote:
>>I dont. I want the 2 end points to talk to each other because I am on
>>AWS with shaky bandwidth stats. It can handle signalingbut not RTP. 
>>However the cfg entry modparam("rtpproxy", "rtpproxy_sock",
>>"udp:127.0.0.1:7722") gives me to believe (not tcdumped RTP ports yet
>>to prove it ) that Kam anchors RTP @ port 7722. 
>>KD  
>>On Wednesday, May 9, 2018, 2:02:14 PM EDT, Alex Balashov
>> wrote:  
>> 
>>That depends. Start with a more basic question: why do you need RTP
>>relay in the middle at all? 
>>
>>On May 9, 2018 1:54:55 PM EDT, KamDev Essa 
>>wrote:
>>>So all calls that kamailio processes using the default cfg file
>anchor
>>>RTP on the kamailio server? Is it a best architecture to farm out RTP
>>>to Freeswitch? Or is the Kamailio RTP proxy a better gig?
>>>KD
>>>On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov
>>> wrote:  
>>> 
>>>Ironically, nothing. Kamailio doesn't touch the respective parties'
>>SDP
>>>unless you invoke an RTP relay (or something else like
>>>fix_nated_sdp()). 
>>>
>>>On May 9, 2018 1:03:19 PM EDT, KamDev Essa 
>>>wrote:
What cfg files changes do I need to make to get Kamailio to be a
signally only server, yet manipulate the SDP part of the INVITE
>>>message
to allow remote parties to send media to each other? In Freeswitch
terms "bypassmedia".
KD
>>>
>>>
>>>-- Alex
>>>
>>>--
>>>Sent via mobile, please forgive typos and brevity. 
>>>
>>>___
>>>Kamailio (SER) - Users Mailing List
>>>sr-users@lists.kamailio.org
>>>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>  
>>
>>
>>-- Alex
>>
>>--
>>Sent via mobile, please forgive typos and brevity.  
>
>
>-- Alex
>
>--
>Sent via mobile, please forgive typos and brevity.  


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] P-CSCF error: pv_parse_spec2(): error searching pvar "uac_req"

[Henning Westerholt]

Am Mittwoch, 9. Mai 2018, 18:29:05 CEST schrieb John M:
> I upgraded Kamailio 4.4 to 5.2.0-dev5 and when I tried to start the
> service(p-cscf), I am getting below error. However I am able to start the
> service with 4.4 p-cscf example cfg. Also after upgrading I-CSCF and S-CSCF
> nodes are running without any issue.
> 
> Any help would be greatly appreciated!
> 
> [root@8bd3221bd31e kamailio]# kamailio -f
> [..]
>  0(2464) ERROR:  [core/pvapi.c:903]: pv_parse_spec2(): error
> searching pvar "uac_req"
>  0(2464) ERROR:  [core/pvapi.c:1107]: pv_parse_spec2(): wrong char
> [m/109] in [$uac_req(method)] at [9 (5)]
>  0(2464) CRITICAL:  [core/cfg.y:3489]: yyerror_at(): parse error in
> config file
> /usr/local/src/kamailio-5.1/kamailio/misc/examples/ims/pcscf/kamailio.cfg,
> line 831, column 3-18: Can't get from cache: $uac_req(method)
> ERROR: bad config file (1 errors)
> [..]

Hello,

it looks that you need to properly define the "uac_req" variable. Is this 
included in your 
configuration? This is not really related to the *CSCF functionality, it 
belongs to the uac 
module.

Best regards,

Henning
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 If I comment out the modparam("rtpproxy", "rtpproxy_sock", 
"udp:127.0.0.1:7722") as suggested, I do get RTP flowing just in one direction. 
 From the UA to kam and out to the carrier. I get nothing geting back to the 
end point. In other words 1 way RTP. Looks like its Kam RTPProxy or bust.
KD
On Wednesday, May 9, 2018, 2:38:08 PM EDT, Alex Balashov 
 wrote:  
 
 Correct. So remove all semblance of any RTP proxy and the resulting behaviour 
will be exactly what you expect. 

On May 9, 2018 2:13:22 PM EDT, KamDev Essa  wrote:
>I dont. I want the 2 end points to talk to each other because I am on
>AWS with shaky bandwidth stats. It can handle signalingbut not RTP. 
>However the cfg entry modparam("rtpproxy", "rtpproxy_sock",
>"udp:127.0.0.1:7722") gives me to believe (not tcdumped RTP ports yet
>to prove it ) that Kam anchors RTP @ port 7722. 
>KD  
>On Wednesday, May 9, 2018, 2:02:14 PM EDT, Alex Balashov
> wrote:  
> 
>That depends. Start with a more basic question: why do you need RTP
>relay in the middle at all? 
>
>On May 9, 2018 1:54:55 PM EDT, KamDev Essa 
>wrote:
>>So all calls that kamailio processes using the default cfg file anchor
>>RTP on the kamailio server? Is it a best architecture to farm out RTP
>>to Freeswitch? Or is the Kamailio RTP proxy a better gig?
>>KD
>>On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov
>> wrote:  
>> 
>>Ironically, nothing. Kamailio doesn't touch the respective parties'
>SDP
>>unless you invoke an RTP relay (or something else like
>>fix_nated_sdp()). 
>>
>>On May 9, 2018 1:03:19 PM EDT, KamDev Essa 
>>wrote:
>>>What cfg files changes do I need to make to get Kamailio to be a
>>>signally only server, yet manipulate the SDP part of the INVITE
>>message
>>>to allow remote parties to send media to each other? In Freeswitch
>>>terms "bypassmedia".
>>>KD
>>
>>
>>-- Alex
>>
>>--
>>Sent via mobile, please forgive typos and brevity. 
>>
>>___
>>Kamailio (SER) - Users Mailing List
>>sr-users@lists.kamailio.org
>>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>  
>
>
>-- Alex
>
>--
>Sent via mobile, please forgive typos and brevity.  


-- Alex

--
Sent via mobile, please forgive typos and brevity.  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[Alex Balashov]

Correct. So remove all semblance of any RTP proxy and the resulting behaviour 
will be exactly what you expect. 

On May 9, 2018 2:13:22 PM EDT, KamDev Essa  wrote:
>I dont. I want the 2 end points to talk to each other because I am on
>AWS with shaky bandwidth stats. It can handle signalingbut not RTP. 
>However the cfg entry modparam("rtpproxy", "rtpproxy_sock",
>"udp:127.0.0.1:7722") gives me to believe (not tcdumped RTP ports yet
>to prove it ) that Kam anchors RTP @ port 7722. 
>KD  
>On Wednesday, May 9, 2018, 2:02:14 PM EDT, Alex Balashov
> wrote:  
> 
>That depends. Start with a more basic question: why do you need RTP
>relay in the middle at all? 
>
>On May 9, 2018 1:54:55 PM EDT, KamDev Essa 
>wrote:
>>So all calls that kamailio processes using the default cfg file anchor
>>RTP on the kamailio server? Is it a best architecture to farm out RTP
>>to Freeswitch? Or is the Kamailio RTP proxy a better gig?
>>KD
>>On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov
>> wrote:  
>> 
>>Ironically, nothing. Kamailio doesn't touch the respective parties'
>SDP
>>unless you invoke an RTP relay (or something else like
>>fix_nated_sdp()). 
>>
>>On May 9, 2018 1:03:19 PM EDT, KamDev Essa 
>>wrote:
>>>What cfg files changes do I need to make to get Kamailio to be a
>>>signally only server, yet manipulate the SDP part of the INVITE
>>message
>>>to allow remote parties to send media to each other? In Freeswitch
>>>terms "bypassmedia".
>>>KD
>>
>>
>>-- Alex
>>
>>--
>>Sent via mobile, please forgive typos and brevity. 
>>
>>___
>>Kamailio (SER) - Users Mailing List
>>sr-users@lists.kamailio.org
>>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>  
>
>
>-- Alex
>
>--
>Sent via mobile, please forgive typos and brevity.  


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 I dont. I want the 2 end points to talk to each other because I am on AWS with 
shaky bandwidth stats. It can handle signalingbut not RTP. 
However the cfg entry modparam("rtpproxy", "rtpproxy_sock", 
"udp:127.0.0.1:7722") gives me to believe (not tcdumped RTP ports yet to prove 
it ) that Kam anchors RTP @ port 7722. 
KD  
On Wednesday, May 9, 2018, 2:02:14 PM EDT, Alex Balashov 
 wrote:  
 
 That depends. Start with a more basic question: why do you need RTP relay in 
the middle at all? 

On May 9, 2018 1:54:55 PM EDT, KamDev Essa  wrote:
>So all calls that kamailio processes using the default cfg file anchor
>RTP on the kamailio server? Is it a best architecture to farm out RTP
>to Freeswitch? Or is the Kamailio RTP proxy a better gig?
>KD
>On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov
> wrote:  
> 
>Ironically, nothing. Kamailio doesn't touch the respective parties' SDP
>unless you invoke an RTP relay (or something else like
>fix_nated_sdp()). 
>
>On May 9, 2018 1:03:19 PM EDT, KamDev Essa 
>wrote:
>>What cfg files changes do I need to make to get Kamailio to be a
>>signally only server, yet manipulate the SDP part of the INVITE
>message
>>to allow remote parties to send media to each other? In Freeswitch
>>terms "bypassmedia".
>>KD
>
>
>-- Alex
>
>--
>Sent via mobile, please forgive typos and brevity. 
>
>___
>Kamailio (SER) - Users Mailing List
>sr-users@lists.kamailio.org
>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>  


-- Alex

--
Sent via mobile, please forgive typos and brevity.  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[Alex Balashov]

That depends. Start with a more basic question: why do you need RTP relay in 
the middle at all? 

On May 9, 2018 1:54:55 PM EDT, KamDev Essa  wrote:
>So all calls that kamailio processes using the default cfg file anchor
>RTP on the kamailio server? Is it a best architecture to farm out RTP
>to Freeswitch? Or is the Kamailio RTP proxy a better gig?
>KD
>On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov
> wrote:  
> 
>Ironically, nothing. Kamailio doesn't touch the respective parties' SDP
>unless you invoke an RTP relay (or something else like
>fix_nated_sdp()). 
>
>On May 9, 2018 1:03:19 PM EDT, KamDev Essa 
>wrote:
>>What cfg files changes do I need to make to get Kamailio to be a
>>signally only server, yet manipulate the SDP part of the INVITE
>message
>>to allow remote parties to send media to each other? In Freeswitch
>>terms "bypassmedia".
>>KD
>
>
>-- Alex
>
>--
>Sent via mobile, please forgive typos and brevity. 
>
>___
>Kamailio (SER) - Users Mailing List
>sr-users@lists.kamailio.org
>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>  


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

 So all calls that kamailio processes using the default cfg file anchor RTP on 
the kamailio server? Is it a best architecture to farm out RTP to Freeswitch? 
Or is the Kamailio RTP proxy a better gig?
KD
On Wednesday, May 9, 2018, 1:38:04 PM EDT, Alex Balashov 
 wrote:  
 
 Ironically, nothing. Kamailio doesn't touch the respective parties' SDP unless 
you invoke an RTP relay (or something else like fix_nated_sdp()). 

On May 9, 2018 1:03:19 PM EDT, KamDev Essa  wrote:
>What cfg files changes do I need to make to get Kamailio to be a
>signally only server, yet manipulate the SDP part of the INVITE message
>to allow remote parties to send media to each other? In Freeswitch
>terms "bypassmedia".
>KD


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
  ___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Is Media Release (signaling only) possible in Kamailio?

[Alex Balashov]

Ironically, nothing. Kamailio doesn't touch the respective parties' SDP unless 
you invoke an RTP relay (or something else like fix_nated_sdp()). 

On May 9, 2018 1:03:19 PM EDT, KamDev Essa  wrote:
>What cfg files changes do I need to make to get Kamailio to be a
>signally only server, yet manipulate the SDP part of the INVITE message
>to allow remote parties to send media to each other? In Freeswitch
>terms "bypassmedia".
>KD


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Question about using Kamailio and Asterisk and flow of an "INVITE"

[Wilkins, Steve]

Hello All,

I am trying to resolve, in my mind, the flow of a WebRTC<=>WebRTC call using 
Kamailio and Asterisk.

Each WebRTC client is registered in Kamailio and when I call WebTRC Client1 
from WebRTC Client2 what I see is ->
The Invite is sent from Kamailio to Asterisk and then Asterisk is sending the 
Invite back to Kamailio.  Also depending on
The version of Asterisk, the INVITE will then get forwarded to the AOR that is 
registered in Kamailio for the called number.
Does this seem correct?  It seems like there is an extra hop in there.

The reason I am now very curious now is because everything works fine if using 
Kamailio 5.0 and Asterisk 14.6, but I switch to Asterisk 15.3
I get the extra hop and call is dropped after 30 seconds.

I would appreciate any thoughts on this.

Thank you in advance.



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Is Media Release (signaling only) possible in Kamailio?

[KamDev Essa]

What cfg files changes do I need to make to get Kamailio to be a signally only 
server, yet manipulate the SDP part of the INVITE message to allow remote 
parties to send media to each other? In Freeswitch terms "bypassmedia".
KD___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Understanding port changing

[Social Boh]

Hello list,

I'm looking for to understand a problem have with Kamailio.

The configuration is:

user (behind NAT) -> Kamilio (Public IP) -> user (behind NAT)

When I make a call from user A to user B (both registered) , User B 
receive the INVITE correctly but in the ringing SIP message change the 
port present on the Contact Header and same think on 200OK so when 
Kamailio try to send it ACK SIP message to this port fail because the 
Softphone listen on the port where has received the INVITE from Kamailio.


This happens with 3 different Softphone: BRIA, Xlite, Linphone on the 
same computer.


Thank you

Regards

--
---
I'm SoCIaL, MayBe


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] P-CSCF error: pv_parse_spec2(): error searching pvar "uac_req"

[John M]

Hello,

I upgraded Kamailio 4.4 to 5.2.0-dev5 and when I tried to start the
service(p-cscf), I am getting below error. However I am able to start the
service with 4.4 p-cscf example cfg. Also after upgrading I-CSCF and S-CSCF
nodes are running without any issue.

Any help would be greatly appreciated!

[root@8bd3221bd31e kamailio]# kamailio -f
/usr/local/src/kamailio-5.1/kamailio/misc/examples/ims/pcscf/kamailio.cfg
loading modules under config path: /usr/local/lib64/kamailio/modules/
 0(2464) ERROR:  [core/pvapi.c:903]: pv_parse_spec2(): error
searching pvar "uac_req"
 0(2464) ERROR:  [core/pvapi.c:1107]: pv_parse_spec2(): wrong char
[m/109] in [$uac_req(method)] at [9 (5)]
 0(2464) CRITICAL:  [core/cfg.y:3489]: yyerror_at(): parse error in
config file
/usr/local/src/kamailio-5.1/kamailio/misc/examples/ims/pcscf/kamailio.cfg,
line 831, column 3-18: Can't get from cache: $uac_req(method)
ERROR: bad config file (1 errors)
 0(2464) INFO:  [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API
not initialized

Regards,
Uts
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] WebRTC to SIP gateway

[Yuriy Gorlichenko]

Hi!
You can to hande it with add_contact_alias but im not sure it will rewrite
transport for you

also if you will store contact as it is on your backend it is a big chance
that it can be unusefull with your SIP service because conract uri is
encrypted and most of b2b servers like asterisk for example will can not
resolve this.

Only one I can suggest - is rewrite contact header with ip address of
webrtc2sip gateway you are building

May be some one else will can suggest some more usefull solutions for you.

On Wed, May 9, 2018, 16:11 Pan Christensen 
wrote:

> Hello!
>
>
>
> It’s been several years since I’ve used Kamailio. My current employer
> wants to implement WebRTC, which is currently not supported in our SIP
> backend, and asked if I could set up a Kamailio server as a gateway.
>
>
>
> I’ve been able to make calls in all directions between SIP and WebRTC
> clients registered locally on Kamailio. When I tried to connect the server
> to the SIP backend, I ran into an issue. I’m able to register SIP clients
> in the backend via the gateway and make calls everywhere. However, the
> WebRTC client fails to register. Here are the messages between the Kamailio
> gateway and the SIP backend:
>
>
>
>
>
> U 2018/05/09 10:12:58.316643 GATEWAY:15060 -> DOMAIN:5060
>
> REGISTER sip:DOMAIN SIP/2.0.
>
> Via: SIP/2.0/UDP
> GATEWAY:15060;branch=z9hG4bK4fc6.04d1730be5b78d595c69a3aa137987c1.0.
>
> Via: SIP/2.0/AUTO
> lr2l9s72ehhc.invalid;rport=61353;received=CLIENT;branch=z9hG4bK5927151.
>
> Max-Forwards: 68.
>
> To: .
>
> From: ;tag=9qhqhrnj3s.
>
> Call-ID: j5h7830ivr5dfc2mn5sov1.
>
> CSeq: 4 REGISTER.
>
> Contact:  ;transport=ws>;+sip.ice;reg-id=1;+sip.instance="";expires=600.
>
> Expires: 600.
>
> Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER,INFO.
>
> Supported: path,gruu,outbound.
>
> User-Agent: JsSIP 3.2.9.
>
> Content-Length: 0.
>
> Path: .
>
> .
>
>
>
>
>
> U 2018/05/09 10:12:58.368409 DOMAIN:5060 -> GATEWAY:15060
>
> SIP/2.0 400 Wrong transport. Provided transport either invalid or not
> supported..
>
> Via: SIP/2.0/UDP
> GATEWAY:15060;branch=z9hG4bK4fc6.04d1730be5b78d595c69a3aa137987c1.0.
>
> Via: SIP/2.0/AUTO
> lr2l9s72ehhc.invalid;rport=61353;received=CLIENT;branch=z9hG4bK5927151.
>
> To: ;tag=91334f57.
>
> From: ;tag=9qhqhrnj3s.
>
> Call-ID: j5h7830ivr5dfc2mn5sov1.
>
> CSeq: 4 REGISTER.
>
> Content-Length: 0.
>
>
>
>
>
> I believe that this error message is caused by ‘;transport=ws’ in the
> Contact header. I’m not allowed to modify this header.
>
>
>
> In the backend database, I found that some other clients have
> ‘;transport=UDP’ in their path headers, so I tried to add that. (Why can I
> not add parameters in path module without adding username?) I still got the
> same error.
>
>
>
> How do I best proceed?
>
>
>
> For your information: We have outsourced the development of the WebRTC
> client, so we are able to change it. We also have the option of paying the
> supplier of the backend for development there.
>
>
>
>
>
> With kind regards
> *Pan B. Christensen*
> Developer
>
> Phonect AS
> Brugata 19, PB 9156 Grønland, N-0133 Oslo, Norway
> E-mail: pan.christen...@phonect.no
> Mobile: +47 41 88 88 00
>
>
>  [image: cid:image007.png@01D3A0E8.376921D0] 
>
> [image: facebook_2]  [image:
> LinkedIn_logo_initials (1)]
> 
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Build Kamailio with MariaDB failed.

[Sergey Safarov]

Need to install mysql-devel
https://github.com/kamailio/kamailio/blob/master/pkg/kamailio/obs/kamailio.spec#L554

And then apply Daniel recommendations.

ср, 9 мая 2018 г. в 14:42, Daniel-Constantin Mierla :

> Hello,
>
> can you go to src/modules/db_mysql and run:
>
> make clean
>
> make Q=0
>
> and send the output here?
>
> Cheers,
> Daniel
>
> On 09.05.18 10:46, Ye, Charlie (NSB - CN/Qingdao) wrote:
>
> Hi Daniel,
>
>
>
> Please find my answer as below:
>
>
>
> The operating system: Red Hat Enterprise Linux Server release 7.4 (Maipo).
>
>
>
> I didn’t modify the Makefile, only include db_mysql module when made cfg.
>
>
>
>
>
>
>
>
>
> Thanks and Best Regards,
>
> Charlie
>
>
>
> *From:* Daniel-Constantin Mierla [mailto:mico...@gmail.com
> ]
> *Sent:* 2018年5月9日 16:27
> *To:* Kamailio (SER) - Users Mailing List 
> ; Ye, Charlie (NSB - CN/Qingdao)
>  
> *Subject:* Re: [SR-Users] Build Kamailio with MariaDB failed.
>
>
>
> Hello,
>
> what operating system are you using?
>
> Have you done any changes to the Makefiles, or is just stock Kamailio?
>
> Cheers,
> Daniel
>
>
>
> On 09.05.18 10:23, Ye, Charlie (NSB - CN/Qingdao) wrote:
>
> Hi all,
>
>
>
> Does everyone use MariaDB in Kamailio? When I built Kamailio with MariaDB,
> the below error happened. Would anyone give a help? Thanks in advance!
>
>
>
> *[root@clcmos /usr/local/src/kamailio-devel/kamailio]$ # make all*
>
> *make -C src/ all*
>
> *make[1]: Entering directory `/usr/local/src/kamailio-devel/kamailio/src'*
>
> *make[3]: `libsrdb2.so.1.0' is up to date.*
>
> *make[3]: `libsrdb1.so.1.0' is up to date.*
>
> *LD (gcc) [M db_mysql.so]db_mysql.so*
>
> */usr/bin/ld: cannot find -lmariadb*
>
> *collect2: error: ld returned 1 exit status*
>
> *make[2]: *** [db_mysql.so] Error 1*
>
> *make[1]: *** [modules] Error 1*
>
> *make[1]: Leaving directory `/usr/local/src/kamailio-devel/kamailio/src'*
>
> *make: *** [all] Error 2*
>
>
>
>
>
>
>
> Thanks and Best Regards,
>
> Charlie
>
>
>
>
>
>
> ___
>
> Kamailio (SER) - Users Mailing List
>
> sr-users@lists.kamailio.org
>
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> --
>
> Daniel-Constantin Mierla
>
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>
> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
>
>
> --
> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Use GStreamer instead of FreeSwitch or Asterisk?

[rainerpiper1402]

Hello,

i don't think that GStreamer can handle SIP or SDP information.

It is just a ...

" GStreamer can bridge to other multimedia frameworks in order to reuse 
existing components (e.g. codecs) and use platform input/output mechanisms:"


And to point at RTP ... some codes are missing like G722, G711u/a and so 
on.


... " container formats: asf, avi, 3gp/mp4/mov, flv, mpeg-ps/ts, 
mkv/webm, mxf, ogg"



Am 09.05.18 um 13:07 schrieb Chandramouli P:

Hello,

I am using Kamailio as registration server and FreeSwitch for 
signalling (RTP packet handling). Can I use GStreamer instead of 
Freeswitch or Asterisk?


Thank you.

Regards,
CM


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Use GStreamer instead of FreeSwitch or Asterisk?

[Chandramouli P]

Hello,

I am using Kamailio as registration server and FreeSwitch for signalling
(RTP packet handling). Can I use GStreamer instead of Freeswitch or
Asterisk?

Thank you.

Regards,
CM
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Build Kamailio with MariaDB failed.

[rainerpiper1402]

Hello Ye,

i run MariaDB cluster on different servers.

I installed Kamailio with normal MySQL first and after i redirected to 
the MariaDB cluster.


hope it helps :))

Regarts Rainer


Am 09.05.18 um 10:46 schrieb Ye, Charlie (NSB - CN/Qingdao):


Hi Daniel,

Please find my answer as below:

The operating system: Red Hat Enterprise Linux Server release 7.4 (Maipo).

I didn’t modify the Makefile, only include db_mysql module when made cfg.

Thanks and Best Regards,

Charlie

*From:*Daniel-Constantin Mierla [mailto:mico...@gmail.com]
*Sent:* 2018年5月9日16:27
*To:* Kamailio (SER) - Users Mailing List 
; Ye, Charlie (NSB - CN/Qingdao) 


*Subject:* Re: [SR-Users] Build Kamailio with MariaDB failed.

Hello,

what operating system are you using?

Have you done any changes to the Makefiles, or is just stock Kamailio?

Cheers,
Daniel

On 09.05.18 10:23, Ye, Charlie (NSB - CN/Qingdao) wrote:

Hi all,

Does everyone use MariaDB in Kamailio? When I built Kamailio with
MariaDB, the below error happened. Would anyone give a help?
Thanks in advance!

/[root@clcmos /usr/local/src/kamailio-devel/kamailio]$ # make all/

/make -C src/ all/

/make[1]: Entering directory
`/usr/local/src/kamailio-devel/kamailio/src'/

/make[3]: `libsrdb2.so.1.0' is up to date./

/make[3]: `libsrdb1.so.1.0' is up to date./

/LD (gcc) [M db_mysql.so]db_mysql.so/

//usr/bin/ld: cannot find -lmariadb/

/collect2: error: ld returned 1 exit status/

/make[2]: *** [db_mysql.so] Error 1/

/make[1]: *** [modules] Error 1/

/make[1]: Leaving directory
`/usr/local/src/kamailio-devel/kamailio/src'/

/make: *** [all] Error 2/

Thanks and Best Regards,

Charlie




___

Kamailio (SER) - Users Mailing List

sr-users@lists.kamailio.org 

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



--
Daniel-Constantin Mierla
www.twitter.com/miconda  -- 
www.linkedin.com/in/miconda 
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com 




___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Build Kamailio with MariaDB failed.

[Ye, Charlie (NSB - CN/Qingdao)]

Hi Daniel,

Please find my answer as below:

The operating system: Red Hat Enterprise Linux Server release 7.4 (Maipo).

I didn’t modify the Makefile, only include db_mysql module when made cfg.




Thanks and Best Regards,
Charlie

From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: 2018年5月9日 16:27
To: Kamailio (SER) - Users Mailing List ; Ye, 
Charlie (NSB - CN/Qingdao) 
Subject: Re: [SR-Users] Build Kamailio with MariaDB failed.


Hello,

what operating system are you using?

Have you done any changes to the Makefiles, or is just stock Kamailio?

Cheers,
Daniel

On 09.05.18 10:23, Ye, Charlie (NSB - CN/Qingdao) wrote:
Hi all,

Does everyone use MariaDB in Kamailio? When I built Kamailio with MariaDB, the 
below error happened. Would anyone give a help? Thanks in advance!

[root@clcmos /usr/local/src/kamailio-devel/kamailio]$ # make all
make -C src/ all
make[1]: Entering directory `/usr/local/src/kamailio-devel/kamailio/src'
make[3]: `libsrdb2.so.1.0' is up to date.
make[3]: `libsrdb1.so.1.0' is up to date.
LD (gcc) [M db_mysql.so]db_mysql.so
/usr/bin/ld: cannot find -lmariadb
collect2: error: ld returned 1 exit status
make[2]: *** [db_mysql.so] Error 1
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/local/src/kamailio-devel/kamailio/src'
make: *** [all] Error 2



Thanks and Best Regards,
Charlie





___

Kamailio (SER) - Users Mailing List

sr-users@lists.kamailio.org

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



--

Daniel-Constantin Mierla

www.twitter.com/miconda -- 
www.linkedin.com/in/miconda

Kamailio World Conference - May 14-16, 2018 - 
www.kamailioworld.com
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Build Kamailio with MariaDB failed.

[Daniel-Constantin Mierla]

Hello,

what operating system are you using?

Have you done any changes to the Makefiles, or is just stock Kamailio?

Cheers,
Daniel


On 09.05.18 10:23, Ye, Charlie (NSB - CN/Qingdao) wrote:
>
> Hi all,
>
>  
>
> Does everyone use MariaDB in Kamailio? When I built Kamailio with
> MariaDB, the below error happened. Would anyone give a help? Thanks in
> advance!
>
>  
>
> /[root@clcmos /usr/local/src/kamailio-devel/kamailio]$ # make all/
>
> /make -C src/ all/
>
> /make[1]: Entering directory `/usr/local/src/kamailio-devel/kamailio/src'/
>
> /make[3]: `libsrdb2.so.1.0' is up to date./
>
> /make[3]: `libsrdb1.so.1.0' is up to date./
>
> /LD (gcc) [M db_mysql.so]    db_mysql.so/
>
> //usr/bin/ld: cannot find -lmariadb/
>
> /collect2: error: ld returned 1 exit status/
>
> /make[2]: *** [db_mysql.so] Error 1/
>
> /make[1]: *** [modules] Error 1/
>
> /make[1]: Leaving directory `/usr/local/src/kamailio-devel/kamailio/src'/
>
> /make: *** [all] Error 2/
>
>  
>
>  
>
>   
>
> Thanks and Best Regards,
>
> Charlie
>
>  
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Build Kamailio with MariaDB failed.

[Ye, Charlie (NSB - CN/Qingdao)]

Hi all,

Does everyone use MariaDB in Kamailio? When I built Kamailio with MariaDB, the 
below error happened. Would anyone give a help? Thanks in advance!

[root@clcmos /usr/local/src/kamailio-devel/kamailio]$ # make all
make -C src/ all
make[1]: Entering directory `/usr/local/src/kamailio-devel/kamailio/src'
make[3]: `libsrdb2.so.1.0' is up to date.
make[3]: `libsrdb1.so.1.0' is up to date.
LD (gcc) [M db_mysql.so]db_mysql.so
/usr/bin/ld: cannot find -lmariadb
collect2: error: ld returned 1 exit status
make[2]: *** [db_mysql.so] Error 1
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/local/src/kamailio-devel/kamailio/src'
make: *** [all] Error 2



Thanks and Best Regards,
Charlie

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users