[SR-Users] implementing call-quota with dialog module

2012-10-08 Thread Aft nix
Hi,

I'm trying to implement a "callquota" based on destination domains.

The idea is following:

every destation domain has a limit of, say 50 calls.

As the sip clients are registered with the "destination domains", i've extracted
the domain using "$fd" because it results as same value as destination domain.

Problem is, i wanted to have separate quota for each domains. But it seems,
that the quota is  reached "as total" not as per domain basis.

Another thing is, the number of calls reported by it is also unusually
large than
actual calls.

This is implemenated as bellow:


#!ifdef WITH_CALL_LIMIT
 modparam("dialog","enable_stats",1)
 modparam("dialog","dlg_flag", DLG_FLAG)
 modparam("dialog","hash_size", 4096)
 modparam("dialog", "profiles_with_value","callquota")
 modparam("dialog", "default_timeout", 300)
 modparam("dialog", "dlg_match_mode", 2)
 modparam("dialog", "detect_spirals", 1)
 modparam("dialog", "db_mode", 0)
 #!endif

 #!ifdef WITH_CALL_LIMIT
  if (is_method("INVITE")) {
  dlg_manage();
  $var(100) = 0;
  get_profile_size("callquota", "$fd", "$var(100)");
  if ($var(100) >= 50 ) {
  xdbg("DEBUG: Simultaneous calls limit reached");
  sl_send_reply("503","Simultaneous calls
limit reached");
  exit;
  }

  set_dlg_profile("callquota","$fd");
  if (get_profile_size("callquota","$fd", "$var(100)")) {
  xdbg("DEBUG: there are $var(100) total calls
for $fd");
  }
  }
  #!endif

Thanks in advance.
-- 
-aft

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] how to use fix_nated_sdp("2") with multiple media types

2012-10-08 Thread MARINA SERRANO MONTES
Hi,

I have a doubt about how to use "fix_nated_sdp("2")" function when we have an 
scenario with multiple media types (audio and video) and the param "c" in sdp 
for each media type has a different IP.
We are using a SCOPIA 400 MCU to multi-party in a call, and it will set up 
different IP to send RTP depend on media type.

I have tested this function, but it rewrites always all the "c" parameter with 
the same value.

Is there any option to use the function or to rewrite "c" value for each media 
type independently?

Many thanks.

Br,
Marina



Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace 
situado m?s abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] how to use fix_nated_sdp("2") with multiple media types

2012-10-08 Thread Vicente Hernando

Hello Marina,

there is a bug in sdp parser about c IPs which are not correctly reset 
for non existent c values in streams.


I have still not uploaded it to master branch, sorry.

May be it is related to your issue, in this link you have the attached 
patch.


http://lists.sip-router.org/pipermail/sr-dev/2012-September/016440.html


Kind regards,
Vicente.

On 10/08/2012 01:18 PM, MARINA SERRANO MONTES wrote:

Hi,

I have a doubt about how to use "fix_nated_sdp("2")" function when we 
have an scenario with multiple media types (audio and video) and the 
param "c" in sdp for each media type has a different IP.
We are using a SCOPIA 400 MCU to multi-party in a call, and it will 
set up different IP to send RTP depend on media type.


I have tested this function, but it rewrites always all the "c" 
parameter with the same value.


Is there any option to use the function or to rewrite "c" value for 
each media type independently?


Many thanks.

Br,
Marina



Este mensaje se dirige exclusivamente a su destinatario. Puede 
consultar nuestra política de envío y recepción de correo electrónico 
en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send 
and receive email on the basis of the terms set out at:

http://www.tid.es/ES/PAGINAS/disclaimer.aspx


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
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@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] how to use fix_nated_sdp("2") with multiple media types

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

I understood that Marina is looking for the option of being able to use 
different IP addresses for updating various c= lines in SDP.


fix_nated_sdp(...) can work only with one IP address given as second 
parameter (or taken for source address of the packet).


Perhaps fix_nated_sdp(...) can be easily extended to support a list of 
ip addresses in the second parameter. For now the solution is to use 
rtpproxy to rewrite all the IP addresses in c= lines with the IP address 
of the rtpproxy. RTPProxy will then dispatch RTP to the right IP address 
assigned for each media stream.


Regarding the patch sent by Vicente, I just replied on sr-dev mailing list.

Cheers,
Daniel

On 10/8/12 3:25 PM, Vicente Hernando wrote:

Hello Marina,

there is a bug in sdp parser about c IPs which are not correctly reset 
for non existent c values in streams.


I have still not uploaded it to master branch, sorry.

May be it is related to your issue, in this link you have the attached 
patch.


http://lists.sip-router.org/pipermail/sr-dev/2012-September/016440.html


Kind regards,
Vicente.

On 10/08/2012 01:18 PM, MARINA SERRANO MONTES wrote:

Hi,

I have a doubt about how to use "fix_nated_sdp("2")" function when we 
have an scenario with multiple media types (audio and video) and the 
param "c" in sdp for each media type has a different IP.
We are using a SCOPIA 400 MCU to multi-party in a call, and it will 
set up different IP to send RTP depend on media type.


I have tested this function, but it rewrites always all the "c" 
parameter with the same value.


Is there any option to use the function or to rewrite "c" value for 
each media type independently?


Many thanks.

Br,
Marina



Este mensaje se dirige exclusivamente a su destinatario. Puede 
consultar nuestra política de envío y recepción de correo electrónico 
en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send 
and receive email on the basis of the terms set out at:

http://www.tid.es/ES/PAGINAS/disclaimer.aspx


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
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@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] implementing call-quota with dialog module

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

what version are you using? at some point it was an issue adding a call 
in a profile after creating its associated dialog.


Also, it might be better to check the quota before creating the dialog, 
because if the limit is reached, then you will just reject the call, so 
you avoid quite some internal operations -- but it is not really 
something crucial.


Cheers,
Daniel

On 10/8/12 11:40 AM, Aft nix wrote:

Hi,

I'm trying to implement a "callquota" based on destination domains.

The idea is following:

every destation domain has a limit of, say 50 calls.

As the sip clients are registered with the "destination domains", i've extracted
the domain using "$fd" because it results as same value as destination domain.

Problem is, i wanted to have separate quota for each domains. But it seems,
that the quota is  reached "as total" not as per domain basis.

Another thing is, the number of calls reported by it is also unusually
large than
actual calls.

This is implemenated as bellow:


#!ifdef WITH_CALL_LIMIT
  modparam("dialog","enable_stats",1)
  modparam("dialog","dlg_flag", DLG_FLAG)
  modparam("dialog","hash_size", 4096)
  modparam("dialog", "profiles_with_value","callquota")
  modparam("dialog", "default_timeout", 300)
  modparam("dialog", "dlg_match_mode", 2)
  modparam("dialog", "detect_spirals", 1)
  modparam("dialog", "db_mode", 0)
  #!endif

  #!ifdef WITH_CALL_LIMIT
   if (is_method("INVITE")) {
   dlg_manage();
   $var(100) = 0;
   get_profile_size("callquota", "$fd", "$var(100)");
   if ($var(100) >= 50 ) {
   xdbg("DEBUG: Simultaneous calls limit reached");
   sl_send_reply("503","Simultaneous calls
limit reached");
   exit;
   }

   set_dlg_profile("callquota","$fd");
   if (get_profile_size("callquota","$fd", "$var(100)")) {
   xdbg("DEBUG: there are $var(100) total calls
for $fd");
   }
   }
   #!endif

Thanks in advance.


--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] pseudovariable values written from app_lua sometimes appear incorrect

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

can you test with latest version in 3.3.x series (from git branch or at 
least the packages for 3.3.1) -- there were many fixes since 3.3.0 was 
released -- just to be sure we don't hunt fixed issues.


I will analyze properly the details you sent in the near future.

Cheers,
Daniel

On 10/5/12 7:54 PM, elact...@jamailca.com wrote:

On 2012-09-27 11:05, elact...@jamailca.com wrote:

On 2012-09-27 10:19, Daniel-Constantin Mierla wrote:

Hello,

On 9/26/12 9:47 PM, elact...@jamailca.com wrote:

Hi,

I am using app_lua to frequently store some data in htable and avp 
entries, using sr.pv.sets. When I read the values using sr.pv.get 
immediately after writing them, they seem correct. However, when I 
read them later from Lua, I have noticed that sometimes the value 
is incorrect or nil. Am I doing something wrong?


The following code uses rtimer to duplicate the problem on startup, 
printing the errors to syslog.


Tested on version: kamailio 3.3.1 (i386/linux) 2d0f6f

###
# kamailio.cfg
###
loadmodule"pv.so"
loadmodule"xlog.so"
loadmodule"htable.so"
loadmodule"rtimer.so"
loadmodule"app_lua"

modparam("htable", "htable", "status=>size=14;autoexpire=0;")

modparam("rtimer", "timer", "name=ta;interval=10;mode=1")
modparam("rtimer", "exec", "timer=ta;route=LUA_TEST")

# the following path may need to change depending on filesystem setup
modparam("app_lua", "load", "/etc/kamailio/kamailio.lua")

route
{
route(LUA_TEST);
}

route[LUA_TEST] {

$var(lua_test_key) = $(pp{s.toupper}) + "::";
lua_runstring("htable_test([[status=>$var(lua_test_key)]])");
lua_runstring("avp_test([[status=>$var(lua_test_key)]])");

}


-- kamailio.lua

-- Test of sr.pv operations in Lua

function htable_test (namekey)
local pvar_prefix = "$sht("..namekey
pvar_test(pvar_prefix)
end

function avp_test ( name )
local pvar_prefix = "$avp("..name
pvar_test(pvar_prefix)
end


function pvar_test ( pvar_prefix )

for value = 1, 10050 do
local pvar = pvar_prefix..value..")"
--sr.log("info", "Lua attempting to set '"..pvar.."' to 
value '"..value.."'")

sr.pv.sets(pvar, value)
end

for value = 1, 10050 do
-- now we check what was stored
local pvar = pvar_prefix..value..")"
local checkvar = sr.pv.get(pvar)
if ( tostring(checkvar) ~= tostring(value) ) then
sr.err(string.format("CHECK: Lua checking pvar '%s' and 
got value '%s' which is NOT '%s'",

tostring(pvar),
tostring(checkvar),
tostring(value)
))
end

end
end
-- end of kamailio.lua


can you provide the log messages?


Sorry, I should have included them with the initial posting. I have
attached an example of the first seven executions of rtimer after a
fresh startup. Each startup of kamailio results in slightly different
error values, but the pattern seems similar.

Please let me know if it would be good to send more logs or anything 
else.




Note that avps are destroyed after
execution of the rtimer route - avps are attached to
message/transaction. Hash table values should stay no matter where are
set.


Thanks for the reminder. I think in this case the test is valid,
though, since the avp values are written and read within a single
rtimer route.



Cheers,
Daniel


Thanks for the help!

-Andrew



I have now duplicated this on the following systems:

Alpine Linux (2.4.5) - kamailio-3.3.0-r0@edge
Ubuntu (12.04.1) - kamailio-3.3.0+precise1
Ubuntu (12.04.1) - kamailio-3.3.0+wheezy1


Only certain pseudovariables are affected:

sr.pv.sets("$sht(name=>key)") fails
sr.pv.sets("$avp(name)") fails
sr.pv.sets("$xavp(name)") fails
sr.pv.sets("$shv(name)") works
sr.pv.sets("$var(name)") works

Do you need any more information to track this problem?


Thanks,

-Andrew



--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] implementing call-quota with dialog module

2012-10-08 Thread Aft nix
On Mon, Oct 8, 2012 at 8:09 PM, Daniel-Constantin Mierla
 wrote:
> Hello,
>
> what version are you using? at some point it was an issue adding a call in a
> profile after creating its associated dialog.
>

i'm using 3.2 branch of the git repository.

> Also, it might be better to check the quota before creating the dialog,
> because if the limit is reached, then you will just reject the call, so you
> avoid quite some internal operations -- but it is not really something
> crucial.

I'm under the impression that my idea behind this implementation is
somewhat flawed.

The idea was to  count calls per "domain".  If the the idea is
reflected in my approach then
i will head for minor tweaking. But if my implementation is just plain
wrong, then i will have to
do it manually, like using sqlops and do the dialog accounting myself.

cheers.

>
> Cheers,
> Daniel
>
>
> On 10/8/12 11:40 AM, Aft nix wrote:
>>
>> Hi,
>>
>> I'm trying to implement a "callquota" based on destination domains.
>>
>> The idea is following:
>>
>> every destation domain has a limit of, say 50 calls.
>>
>> As the sip clients are registered with the "destination domains", i've
>> extracted
>> the domain using "$fd" because it results as same value as destination
>> domain.
>>
>> Problem is, i wanted to have separate quota for each domains. But it
>> seems,
>> that the quota is  reached "as total" not as per domain basis.
>>
>> Another thing is, the number of calls reported by it is also unusually
>> large than
>> actual calls.
>>
>> This is implemenated as bellow:
>>
>>
>> #!ifdef WITH_CALL_LIMIT
>>   modparam("dialog","enable_stats",1)
>>   modparam("dialog","dlg_flag", DLG_FLAG)
>>   modparam("dialog","hash_size", 4096)
>>   modparam("dialog", "profiles_with_value","callquota")
>>   modparam("dialog", "default_timeout", 300)
>>   modparam("dialog", "dlg_match_mode", 2)
>>   modparam("dialog", "detect_spirals", 1)
>>   modparam("dialog", "db_mode", 0)
>>   #!endif
>>
>>   #!ifdef WITH_CALL_LIMIT
>>if (is_method("INVITE")) {
>>dlg_manage();
>>$var(100) = 0;
>>get_profile_size("callquota", "$fd", "$var(100)");
>>if ($var(100) >= 50 ) {
>>xdbg("DEBUG: Simultaneous calls limit
>> reached");
>>sl_send_reply("503","Simultaneous calls
>> limit reached");
>>exit;
>>}
>>
>>set_dlg_profile("callquota","$fd");
>>if (get_profile_size("callquota","$fd", "$var(100)")) {
>>xdbg("DEBUG: there are $var(100) total calls
>> for $fd");
>>}
>>}
>>#!endif
>>
>> Thanks in advance.
>
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
> Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
> Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 -
> http://asipto.com/u/katu
>



-- 
-aft

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] TLS support in Kamailio

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

On 10/5/12 1:29 PM, Kamal Palei wrote:

Hi Daniel
Thanks a lot for kind response.
For this requirement, I need -
1. When a message is received at Kamailio proxy, that message either 
will be sent to client side or to main proxy side.
2. If it is supposed to send to client side, then it should send in 
plain UDP. Also note that, when the message is received from clients 
it should be received in plain udp by Kamailio proxy.
3. If Kamailio proxy is supposed to send the message to main proxy 
side, then it should send using TLS. Also note that, any message that 
comes from main proxy, Kamailio should receive in TLS only.
As I understand, the three optioned mentioned below in your mail, I 
can use either of one.


yes, any is good.

Do I need to take any additional precaution so that TLS stuff will 
work fine (actually will be working on TLS first time).


TLS is quite transparent to the configuration file, working 
automatically -- in you case you need to force the transport by 
yourself, because it is not specified in R-URI. Request within dialog 
will be routed using Route headers, so there is nothing to do for them.


Cheers,
Daniel


Thanks
Kamal
NECS, Bangalore

On Fri, Oct 5, 2012 at 1:56 PM, Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:


Hello,

yes, it is possible. There are couple options:

- rewrite r-uri ($ru) to contain the transport=tls and then t_relay()
- set dst uri ($du) to the uri point to main proxy address having
the transport=tls parameter and then t_relay()
- use t_relay_to("tls:mainproxyip:port")

Cheers,
Daniel


On 10/4/12 12:21 PM, Kamal Palei wrote:

Hi List
I have a specific requiremnt where I want Kamailio proxy need to
work as a intermideiate proxy .
The endpoints will talk to Kamailio using UDP as transport and
Kamailio should interact with main proxy using TLS.
Is this scenario possible with Kamailio ?
If so, can you give me some pointer how can I acheive it.
Thanks
Kamal
Net clooud systems
Bangalore


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org  
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


-- 
Daniel-Constantin Mierla -http://www.asipto.com  

http://twitter.com/#!/miconda    
-http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 
-http://asipto.com/u/katu




--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] moving all to kamailio namespace

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

some bits were left with the old project name OpenSER, not to disturb 
too much at that time and see where everything goes.


Other voices expressed same idea in the past, now everything is stable 
and development goes smooth, so it is good to make a decision because 
openser is too way back and new comers could be confused.


In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that 
much as most of them have database provided by module parameter)
- default database access usernames and passwords, respectively openser, 
openserro and openserrw should become kamailio, kamailioro and kamailiorw
- perl module API is packed as OpenSER - this could affect some people 
using it, but a search and replace should do it

- snmpstats mibs - probably it is going to have some impact as well

Eventually we can start doing it gradually, one or two per release, but 
is probably better to do all at once, so people will do one upgrade with 
next major release.


Another thing is sercmd, it is in conflict for packaging as both ser and 
kamailio install it. It means that one cannot install both kamailio and 
ser at same time from packages. One option is to install it as kamcmd.


Because these changes affect users and devels, I sent the message to 
both mailing lists. Opinions?


Cheers,
Daniel

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] moving all to kamailio namespace

2012-10-08 Thread Cenk İlker İzanlı
Hello,

I think it is better to do all changes at once.

Thx.



2012/10/8 Daniel-Constantin Mierla 

> Hello,
>
> some bits were left with the old project name OpenSER, not to disturb too
> much at that time and see where everything goes.
>
> Other voices expressed same idea in the past, now everything is stable and
> development goes smooth, so it is good to make a decision because openser
> is too way back and new comers could be confused.
>
> In my list is renaming from openser to kamailio next attributes:
> - default database name (exiting configs should not be impacted that much
> as most of them have database provided by module parameter)
> - default database access usernames and passwords, respectively openser,
> openserro and openserrw should become kamailio, kamailioro and kamailiorw
> - perl module API is packed as OpenSER - this could affect some people
> using it, but a search and replace should do it
> - snmpstats mibs - probably it is going to have some impact as well
>
> Eventually we can start doing it gradually, one or two per release, but is
> probably better to do all at once, so people will do one upgrade with next
> major release.
>
> Another thing is sercmd, it is in conflict for packaging as both ser and
> kamailio install it. It means that one cannot install both kamailio and ser
> at same time from packages. One option is to install it as kamcmd.
>
> Because these changes affect users and devels, I sent the message to both
> mailing lists. Opinions?
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - 
> http://www.linkedin.com/in/**miconda
> Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -
> http://asipto.com/u/kat
> Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 -
> http://asipto.com/u/katu
>
>
> __**_
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> 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@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] [sr-dev] moving all to kamailio namespace

2012-10-08 Thread Juha Heinanen
Daniel-Constantin Mierla writes:

> In my list is renaming from openser to kamailio next attributes:
> - default database name (exiting configs should not be impacted that 
> much as most of them have database provided by module parameter)

i once tried to change database name from ser to something newer, but
i was not able to find from mysql docs a db rename command.

-- juha

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] [sr-dev] moving all to kamailio namespace

2012-10-08 Thread Carlos Ruiz Díaz
HI Daniel,

I consider myself a "new comer" and having both kamailio and ser
interacting with each other is indeed confusing.

For me, the change is welcome and I'm in favor of doing all the effort at
once.

Regards.

Carlos

On Mon, Oct 8, 2012 at 11:33 AM, Daniel-Constantin Mierla  wrote:

> Hello,
>
> some bits were left with the old project name OpenSER, not to disturb too
> much at that time and see where everything goes.
>
> Other voices expressed same idea in the past, now everything is stable and
> development goes smooth, so it is good to make a decision because openser
> is too way back and new comers could be confused.
>
> In my list is renaming from openser to kamailio next attributes:
> - default database name (exiting configs should not be impacted that much
> as most of them have database provided by module parameter)
> - default database access usernames and passwords, respectively openser,
> openserro and openserrw should become kamailio, kamailioro and kamailiorw
> - perl module API is packed as OpenSER - this could affect some people
> using it, but a search and replace should do it
> - snmpstats mibs - probably it is going to have some impact as well
>
> Eventually we can start doing it gradually, one or two per release, but is
> probably better to do all at once, so people will do one upgrade with next
> major release.
>
> Another thing is sercmd, it is in conflict for packaging as both ser and
> kamailio install it. It means that one cannot install both kamailio and ser
> at same time from packages. One option is to install it as kamcmd.
>
> Because these changes affect users and devels, I sent the message to both
> mailing lists. Opinions?
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - 
> http://www.linkedin.com/in/**miconda
> Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -
> http://asipto.com/u/kat
> Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 -
> http://asipto.com/u/katu
>
>
> __**_
> sr-dev mailing list
> sr-...@lists.sip-router.org
> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**dev
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] MSRP Config

2012-10-08 Thread Ed Brady
Hi,

I am working on an MSRP project with Kamailio. I have Kamailio installed
and configured for SIP with several test accounts created, but am unable to
send MSRP messages so far. I am using Blink as a test client, though the
final intentions of the project will be to use iDoubs and IMSDroid for
client connections. We are having these developed to our needs right now
though, so I must use another client to begin testing.

I have been unable to find good documentation on the initial configuration
of MSRP in Kamailio. I have seen the module documentation, but am unclear
how to utilize the information there to configure Kamailio properly. Is
there any documentation on getting started with a basic MSRP relay setup so
that two clients can chat and send files? I am not new to SIP, but this is
my first project with MSRP.


Thanks,
Ed
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] pseudovariable values written from app_lua sometimes appear incorrect

2012-10-08 Thread elactrum

On 2012-10-08 09:15, Daniel-Constantin Mierla wrote:

Hello,

can you test with latest version in 3.3.x series (from git branch or
at least the packages for 3.3.1) -- there were many fixes since 3.3.0
was released -- just to be sure we don't hunt fixed issues.



Tested and duplicated the same behavior on the following nightly 
builds:


Ubuntu (12.04.1) kamailio, kamailio-lua-modules i386 
3.3.1+git20121008+precise1
Ubuntu (12.04.1) kamailio, kamailio-lua-modules i386 
3.3.1+git20121008+wheezy1



I will analyze properly the details you sent in the near future.



Thanks. I am looking forward to it.

-Andrew


Cheers,
Daniel

On 10/5/12 7:54 PM, elact...@jamailca.com wrote:

On 2012-09-27 11:05, elact...@jamailca.com wrote:

On 2012-09-27 10:19, Daniel-Constantin Mierla wrote:

Hello,

On 9/26/12 9:47 PM, elact...@jamailca.com wrote:

Hi,

I am using app_lua to frequently store some data in htable and 
avp entries, using sr.pv.sets. When I read the values using 
sr.pv.get immediately after writing them, they seem correct. 
However, when I read them later from Lua, I have noticed that 
sometimes the value is incorrect or nil. Am I doing something 
wrong?


The following code uses rtimer to duplicate the problem on 
startup, printing the errors to syslog.


Tested on version: kamailio 3.3.1 (i386/linux) 2d0f6f

###
# kamailio.cfg
###
loadmodule"pv.so"
loadmodule"xlog.so"
loadmodule"htable.so"
loadmodule"rtimer.so"
loadmodule"app_lua"

modparam("htable", "htable", "status=>size=14;autoexpire=0;")

modparam("rtimer", "timer", "name=ta;interval=10;mode=1")
modparam("rtimer", "exec", "timer=ta;route=LUA_TEST")

# the following path may need to change depending on filesystem 
setup

modparam("app_lua", "load", "/etc/kamailio/kamailio.lua")

route
{
route(LUA_TEST);
}

route[LUA_TEST] {

$var(lua_test_key) = $(pp{s.toupper}) + "::";
lua_runstring("htable_test([[status=>$var(lua_test_key)]])");
lua_runstring("avp_test([[status=>$var(lua_test_key)]])");

}


-- kamailio.lua

-- Test of sr.pv operations in Lua

function htable_test (namekey)
local pvar_prefix = "$sht("..namekey
pvar_test(pvar_prefix)
end

function avp_test ( name )
local pvar_prefix = "$avp("..name
pvar_test(pvar_prefix)
end


function pvar_test ( pvar_prefix )

for value = 1, 10050 do
local pvar = pvar_prefix..value..")"
--sr.log("info", "Lua attempting to set '"..pvar.."' to 
value '"..value.."'")

sr.pv.sets(pvar, value)
end

for value = 1, 10050 do
-- now we check what was stored
local pvar = pvar_prefix..value..")"
local checkvar = sr.pv.get(pvar)
if ( tostring(checkvar) ~= tostring(value) ) then
sr.err(string.format("CHECK: Lua checking pvar '%s' 
and got value '%s' which is NOT '%s'",

tostring(pvar),
tostring(checkvar),
tostring(value)
))
end

end
end
-- end of kamailio.lua


can you provide the log messages?


Sorry, I should have included them with the initial posting. I have
attached an example of the first seven executions of rtimer after a
fresh startup. Each startup of kamailio results in slightly 
different

error values, but the pattern seems similar.

Please let me know if it would be good to send more logs or 
anything else.




Note that avps are destroyed after
execution of the rtimer route - avps are attached to
message/transaction. Hash table values should stay no matter where 
are

set.


Thanks for the reminder. I think in this case the test is valid,
though, since the avp values are written and read within a single
rtimer route.



Cheers,
Daniel


Thanks for the help!

-Andrew



I have now duplicated this on the following systems:

Alpine Linux (2.4.5) - kamailio-3.3.0-r0@edge
Ubuntu (12.04.1) - kamailio-3.3.0+precise1
Ubuntu (12.04.1) - kamailio-3.3.0+wheezy1


Only certain pseudovariables are affected:

sr.pv.sets("$sht(name=>key)") fails
sr.pv.sets("$avp(name)") fails
sr.pv.sets("$xavp(name)") fails
sr.pv.sets("$shv(name)") works
sr.pv.sets("$var(name)") works

Do you need any more information to track this problem?


Thanks,

-Andrew




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] how to use fix_nated_sdp("2") with multiple media types

2012-10-08 Thread MARINA SERRANO MONTES
Hi Daniel,

I have tested using "rtpproxy_manage("", public IP), but in this case, it 
replaces all the c= lines with this public IP, included c=lines in media 
descriptions and then, the rtp traffic is not routing to the right IP in MCU.

Have I to set up any value/param….to route rtp traffic through rtpproxy in sip 
server and then it will dispatch RTP packets to MCU?

Thanks.

Br,
Marina

From: Daniel-Constantin Mierla mailto:mico...@gmail.com>>
Reply-To: "mico...@gmail.com" 
mailto:mico...@gmail.com>>
Date: lunes 8 de octubre de 2012 16:04
To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users 
Mailing List" 
mailto:sr-users@lists.sip-router.org>>
Cc: Vicente Hernando 
mailto:vherna...@systemonenoc.com>>, Marina Serrano 
Montes mailto:mari...@tid.es>>
Subject: Re: [SR-Users] how to use fix_nated_sdp("2") with multiple media types

Hello,

I understood that Marina is looking for the option of being able to use 
different IP addresses for updating various c= lines in SDP.

fix_nated_sdp(...) can work only with one IP address given as second parameter 
(or taken for source address of the packet).

Perhaps fix_nated_sdp(...) can be easily extended to support a list of ip 
addresses in the second parameter. For now the solution is to use rtpproxy to 
rewrite all the IP addresses in c= lines with the IP address of the rtpproxy. 
RTPProxy will then dispatch RTP to the right IP address assigned for each media 
stream.

Regarding the patch sent by Vicente, I just replied on sr-dev mailing list.

Cheers,
Daniel

On 10/8/12 3:25 PM, Vicente Hernando wrote:
Hello Marina,

there is a bug in sdp parser about c IPs which are not correctly reset for non 
existent c values in streams.

I have still not uploaded it to master branch, sorry.

May be it is related to your issue, in this link you have the attached patch.

http://lists.sip-router.org/pipermail/sr-dev/2012-September/016440.html


Kind regards,
Vicente.

On 10/08/2012 01:18 PM, MARINA SERRANO MONTES wrote:
Hi,

I have a doubt about how to use "fix_nated_sdp("2")" function when we have an 
scenario with multiple media types (audio and video) and the param "c" in sdp 
for each media type has a different IP.
We are using a SCOPIA 400 MCU to multi-party in a call, and it will set up 
different IP to send RTP depend on media type.

I have tested this function, but it rewrites always all the "c" parameter with 
the same value.

Is there any option to use the function or to rewrite "c" value for each media 
type independently?

Many thanks.

Br,
Marina



Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra política de envío y recepción de correo electrónico en el enlace 
situado más abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - 
http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu



Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra política de envío y recepción de correo electrónico en el enlace 
situado más abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] update_subs_rlsdb: NO MATCH

2012-10-08 Thread Sangeeta Shah
I have Kamailio 3.3 with Presence, RLS and integrated XCAP.

I see this information message in the log file:

Oct  8 14:34:05 RCS-Presence /usr/local/sbin/kamailio[4530]: INFO: rls
[rls_db.c:779]: update_subs_rlsdb: NO MATCH

Anyone know why the application is calling that method if it doesn't
exist in rls_db.c.

I still haven't been able to get presence with rls and integrated xcap
working so not sure if this is an issue or no. Currently for both
presence and RLS i am using "DB-Only" mode.

Any help is appreciated. It seems like when client A adds client B as
a contact, the kamalio server is not sending out an auth request to
client B. Even though it's registered for presence.winfo events.



Thanks,
Sangeeta

-- 
Sangeeta Shah

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] Errors issued by Kamailio

2012-10-08 Thread Sangeeta Shah
Hi,
   I am seeing the following errors in syslog:

Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence_xml [notify_body.c:635]: while extracting tuple node
Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence_xml [notify_body.c:75]: while constructing offline body
Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence [presentity.c:1220]: preparing body
Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence [publish.c:171]: Marking presentity
Oct  8 16:21:55 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO:
presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via
sip:8475551004@10.50.0.93:60562;transport=udp on behalf of
sip:8475551004@10.50.251.12 for event message-summary
Oct  8 16:21:55 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO:
presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via
sip:8475551004@10.50.0.93:60562;transport=udp on behalf of
sip:8475551004@10.50.251.12 for event presence.winfo
Oct  8 16:21:57 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO:
presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via
sip:8475551004@10.50.0.93:60562;transport=udp on behalf of
sip:8475551004@10.50.251.12 for event presence


I am using Kamailio 3.3 with Presence and RLS with integrated XCAP.

The only significant change i made today is update the presence and
RLS config to DB ONLY mode.

Thanks,
Sangeeta

-- 
Sangeeta Shah

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] [sr-dev] moving all to kamailio namespace

2012-10-08 Thread Daniel-Constantin Mierla


On 10/8/12 4:41 PM, Juha Heinanen wrote:

Daniel-Constantin Mierla writes:


In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that
much as most of them have database provided by module parameter)

i once tried to change database name from ser to something newer, but
i was not able to find from mysql docs a db rename command.

this one:
- http://dev.mysql.com/doc/refman/5.1/en/rename-database.html

But the old name can be kept in existing installation -- it is a matter 
of db_url parameter value and setting in kamctlrc.


Cheers,
Daniel

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] [sr-dev] moving all to kamailio namespace

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

I am aware of such confusion, but there are people using the two 
database schema, so completely unifying them is quite complex process.


But, speaking of available documentation, community maintenance and new 
comers, probably it makes sense to make kamailio default flavour, 
because ser requires more technical involvement -- I haven't seen new 
comers looking at installing ser flavour, which is default one now.


Cheers,
Daniel

On 10/8/12 4:48 PM, Carlos Ruiz Díaz wrote:

HI Daniel,

I consider myself a "new comer" and having both kamailio and ser 
interacting with each other is indeed confusing.


For me, the change is welcome and I'm in favor of doing all the effort 
at once.


Regards.

Carlos

On Mon, Oct 8, 2012 at 11:33 AM, Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:


Hello,

some bits were left with the old project name OpenSER, not to
disturb too much at that time and see where everything goes.

Other voices expressed same idea in the past, now everything is
stable and development goes smooth, so it is good to make a
decision because openser is too way back and new comers could be
confused.

In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted
that much as most of them have database provided by module parameter)
- default database access usernames and passwords, respectively
openser, openserro and openserrw should become kamailio,
kamailioro and kamailiorw
- perl module API is packed as OpenSER - this could affect some
people using it, but a search and replace should do it
- snmpstats mibs - probably it is going to have some impact as well

Eventually we can start doing it gradually, one or two per
release, but is probably better to do all at once, so people will
do one upgrade with next major release.

Another thing is sercmd, it is in conflict for packaging as both
ser and kamailio install it. It means that one cannot install both
kamailio and ser at same time from packages. One option is to
install it as kamcmd.

Because these changes affect users and devels, I sent the message
to both mailing lists. Opinions?

Cheers,
Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com

http://twitter.com/#!/miconda  -
http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -
http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 -
http://asipto.com/u/katu


___
sr-dev mailing list
sr-...@lists.sip-router.org 
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev




--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] MSRP Config

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

On 10/8/12 5:26 PM, Ed Brady wrote:

Hi,

I am working on an MSRP project with Kamailio. I have Kamailio 
installed and configured for SIP with several test accounts created, 
but am unable to send MSRP messages so far. I am using Blink as a test 
client, though the final intentions of the project will be to use 
iDoubs and IMSDroid for client connections. We are having these 
developed to our needs right now though, so I must use another client 
to begin testing.


I have been unable to find good documentation on the initial 
configuration of MSRP in Kamailio. I have seen the module 
documentation, but am unclear how to utilize the information there to 
configure Kamailio properly. Is there any documentation on getting 
started with a basic MSRP relay setup so that two clients can chat and 
send files? I am not new to SIP, but this is my first project with MSRP.


at the time I developed the module were no good clients supporting msrp, 
so I did testing mainly with forged network tools. But I am happy to 
assist as much as possible provided my availability and fix eventual issues.


The readme of the module provides and example for a stand alone msrp 
relay. If you want to put it inside a more complex kamailio 
configuration that handles sip as well, then be sure you load msrp 
module as well as all the other modules from the readme's config and set 
the module parameters.


Then copy the event_route[msrp:frame-in] block in your config. MSRP 
packets have to be sent to port 5060 (or 5061 for tls), or you can 
configure kamailio to listen on an additional port where you send the 
msrp packets.


If something is not working, send the log messages (debug=3 in your 
config) and the ngrep trace if you use plain tcp.


Cheers,
Daniel

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] how to use fix_nated_sdp("2") with multiple media types

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

you should not set the second parameter of rtpproxy_manage(...), let it 
be the one returned by rtpproxy.


And yes, all the occurrences of IP addresses in c= lines will be 
replaced by the rtpproxy ip, but providing different ports for each 
media stream.


Practically the rtp streams are going from end device to rtpproxy and 
then based on port will be delivered to different IPs of the MCU. Also, 
the MCU will send from different IPs to RTPProxy on different ports and 
from there to the end device.


Cheers,
Daniel

On 10/8/12 6:05 PM, MARINA SERRANO MONTES wrote:

Hi Daniel,

I have tested using "rtpproxy_manage("", public IP), but in this case, 
it replaces all the c= lines with this public IP, included c=lines in 
media descriptions and then, the rtp traffic is not routing to the 
right IP in MCU.


Have I to set up any value/param….to route rtp traffic through 
rtpproxy in sip server and then it will dispatch RTP packets to MCU?


Thanks.

Br,
Marina

From: Daniel-Constantin Mierla >
Reply-To: "mico...@gmail.com " 
mailto:mico...@gmail.com>>

Date: lunes 8 de octubre de 2012 16:04
To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - 
Users Mailing List" >
Cc: Vicente Hernando >, Marina Serrano Montes 
mailto:mari...@tid.es>>
Subject: Re: [SR-Users] how to use fix_nated_sdp("2") with multiple 
media types


Hello,

I understood that Marina is looking for the option of being able to 
use different IP addresses for updating various c= lines in SDP.


fix_nated_sdp(...) can work only with one IP address given as second 
parameter (or taken for source address of the packet).


Perhaps fix_nated_sdp(...) can be easily extended to support a list of 
ip addresses in the second parameter. For now the solution is to use 
rtpproxy to rewrite all the IP addresses in c= lines with the IP 
address of the rtpproxy. RTPProxy will then dispatch RTP to the right 
IP address assigned for each media stream.


Regarding the patch sent by Vicente, I just replied on sr-dev mailing 
list.


Cheers,
Daniel

On 10/8/12 3:25 PM, Vicente Hernando wrote:

Hello Marina,

there is a bug in sdp parser about c IPs which are not correctly 
reset for non existent c values in streams.


I have still not uploaded it to master branch, sorry.

May be it is related to your issue, in this link you have the 
attached patch.


http://lists.sip-router.org/pipermail/sr-dev/2012-September/016440.html


Kind regards,
Vicente.

On 10/08/2012 01:18 PM, MARINA SERRANO MONTES wrote:

Hi,

I have a doubt about how to use "fix_nated_sdp("2")" function when 
we have an scenario with multiple media types (audio and video) and 
the param "c" in sdp for each media type has a different IP.
We are using a SCOPIA 400 MCU to multi-party in a call, and it will 
set up different IP to send RTP depend on media type.


I have tested this function, but it rewrites always all the "c" 
parameter with the same value.


Is there any option to use the function or to rewrite "c" value for 
each media type independently?


Many thanks.

Br,
Marina



Este mensaje se dirige exclusivamente a su destinatario. Puede 
consultar nuestra política de envío y recepción de correo 
electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send 
and receive email on the basis of the terms set out at:

http://www.tid.es/ES/PAGINAS/disclaimer.aspx


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla -http://www.asipto.comhttp://twitter.com/#!/miconda  
-http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 
-http://asipto.com/u/katu



Este mensaje se dirige exclusivamente a su destinatario. Puede 
consultar nuestra política de envío y recepción de correo electrónico 
en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send 
and receive email on the basis of the terms set out at:

http://www.tid.es/ES/PAGINAS/disclaimer.aspx


--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/kat

Re: [SR-Users] update_subs_rlsdb: NO MATCH

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

you should set debug=3 in your config file and watch the logs messages 
to get more details about what happens there.


I don't have any sip application that supports rls, so I'm not able to 
test, but classic SIMPLE presence should work fine.


Regards,
Daniel

On 10/8/12 9:32 PM, Sangeeta Shah wrote:

I have Kamailio 3.3 with Presence, RLS and integrated XCAP.

I see this information message in the log file:

Oct  8 14:34:05 RCS-Presence /usr/local/sbin/kamailio[4530]: INFO: rls
[rls_db.c:779]: update_subs_rlsdb: NO MATCH

Anyone know why the application is calling that method if it doesn't
exist in rls_db.c.

I still haven't been able to get presence with rls and integrated xcap
working so not sure if this is an issue or no. Currently for both
presence and RLS i am using "DB-Only" mode.

Any help is appreciated. It seems like when client A adds client B as
a contact, the kamalio server is not sending out an auth request to
client B. Even though it's registered for presence.winfo events.



Thanks,
Sangeeta



--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] Errors issued by Kamailio

2012-10-08 Thread Daniel-Constantin Mierla

Hello,

the error messages seem to be due to a broken XML document in a NOTIFY 
-- they are printed because of errors reported by libxml2 parser. Can 
you get a sip trace for such requests that throw these error messages in 
the log?


Cheers,
Daniel

On 10/8/12 11:17 PM, Sangeeta Shah wrote:

Hi,
I am seeing the following errors in syslog:

Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence_xml [notify_body.c:635]: while extracting tuple node
Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence_xml [notify_body.c:75]: while constructing offline body
Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence [presentity.c:1220]: preparing body
Oct  8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR:
presence [publish.c:171]: Marking presentity
Oct  8 16:21:55 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO:
presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via
sip:8475551004@10.50.0.93:60562;transport=udp on behalf of
sip:8475551004@10.50.251.12 for event message-summary
Oct  8 16:21:55 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO:
presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via
sip:8475551004@10.50.0.93:60562;transport=udp on behalf of
sip:8475551004@10.50.251.12 for event presence.winfo
Oct  8 16:21:57 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO:
presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via
sip:8475551004@10.50.0.93:60562;transport=udp on behalf of
sip:8475551004@10.50.251.12 for event presence


I am using Kamailio 3.3 with Presence and RLS with integrated XCAP.

The only significant change i made today is update the presence and
RLS config to DB ONLY mode.

Thanks,
Sangeeta



--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - 
http://asipto.com/u/katu


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] moving all to kamailio namespace

2012-10-08 Thread Olle E. Johansson

8 okt 2012 kl. 16:33 skrev Daniel-Constantin Mierla :

> Hello,
> 
> some bits were left with the old project name OpenSER, not to disturb too 
> much at that time and see where everything goes.
> 
> Other voices expressed same idea in the past, now everything is stable and 
> development goes smooth, so it is good to make a decision because openser is 
> too way back and new comers could be confused.
> 
> In my list is renaming from openser to kamailio next attributes:
> - default database name (exiting configs should not be impacted that much as 
> most of them have database provided by module parameter)
> - default database access usernames and passwords, respectively openser, 
> openserro and openserrw should become kamailio, kamailioro and kamailiorw
> - perl module API is packed as OpenSER - this could affect some people using 
> it, but a search and replace should do it
> - snmpstats mibs - probably it is going to have some impact as well
> 
Good timing, good idea.

I think we should clean up everything at the same time - including all 
documentation. 

Time to restart with GIT I think ;-)

/O
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users