sr-users

sr-users@lists.kamailio.org

42 participants
37549 discussions

[Users] uac_replace_from and avp
by CSB 03 May '07

03 May '07

In OpenSER 1.1 I use uac_replace_from to rewrite the from details. I want the rewritten from to be based on an avp value but I don't think that is possible. Am I right? If so, is it possible in 1.2? On a related point, is anyone working on fixing the CSEQ issue with the uac module or is there a plan for this? I know it's been on the todo list for a while. Regards Cameron

3 3

Res: [Users] LCR module (1.2.0)
by Bruno Machado 03 May '07

03 May '07

Hi Heinanen When I was using the version 1.1.0, I needed to set a preferred route to my voip 123. This way, it was necessary to insert this underscores after 0. They match any single character (like dot in regular expressions). I used it because the prefix needs to match the longest user part. prefix-------------------from_uri-------grp_id--------priority 0123456------------------------%------------ 1 ---------------1 0________-------------sip:123@.*----------- 2 ---------------0 If I call to number 01234560000 with voip 777, the GW 1 will be selected. Instead, when I use voip 123, the GW 2 is returned. This way, all the calls originated by voip 123 having a size of user part equal 7 or greater, will match with the second line. It does not happens with I have these lines (without the underscores): prefix-------------------from_uri-------grp_id--------priority 0123456------------------------%------------ 1 ---------------1 0-----------------------sip:123@.*----------- 2 ---------------0 In this case, GW 1 will be always selected to any voip. It works in version 1.1.0, but I need to set this behavior in 1.2.0. I know that from_uri in this version is a regular expression. So, I added a '^' in the beginning. prefix-------------------from_uri-------grp_id--------priority 0123456-------------------------------------- 1 ---------------1 0________------------^sip:123@.*--------- 2 ---------------0 The version 1.2.0 always use the LCR in memory. I looked for the query used by 1.1.0 in lcr_mod.h but I didn't find it. So, I don't know if the underscores is necessary because it is used by the MySQL. In my test, just the GW 1 was selected when I called using voip 123. Using other words: I want to route all the calls originated by voip 123 through GW 2 (when beginning with a 0) and the others to GW 1. Thanks for your help, Heinanen. Bruno ----- Mensagem original ---- De: Juha Heinanen <jh(a)tutpro.com> Para: Bruno Machado <bsmufu(a)yahoo.com.br> Cc: users(a)openser.org Enviadas: Quinta-feira, 3 de Maio de 2007 12:36:33 Assunto: [Users] LCR module (1.2.0) Bruno Machado writes: > prefix----------from_uri-------grp_id--------priority > 0123456------------------------------ 1 ---------------1 > 0________------^sip:123.*--------- 2 ---------------0 > > Ok. The LCR documentation tells that the column 'from_uri' must be a > regular expression in this version. The route selected is the first > line. I'd like to route the voip number 123 through GW 2, but it > doesn't happens. i don't understand based on the above, how your lcr table looks like and which uri you are trying to call. what are the underscores after 0? prefix is just a prefix, nothing else. -- juha __________________________________________________ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/

2 1

[Users] ACC : log_fmt equivalent in 1.2 ?
by Will Quan 03 May '07

03 May '07

In version 1.1.0 it was possible to specify the log_fmt for the ACC records that go into the syslog. modparam("acc", "log_fmt", "miocfsur");It appears this has been removed in 1.2, so I was wondering if there is a new way to achieve the same result. That is, produce ACC records with the same syslog format as my 1.3 version.Thanks,Will

2 1

[Users] Rejecting SUBSCRIBE/NOTIFY messages
by Andreas Sikkema 03 May '07

03 May '07

Hi, I've been googling for a while and I haven't been able to find out how to do the following: I would like to reject all SUBSCRIBE and NOTIFY messages received by my OpenSER server. How do I do properly? if (method=="SUBSCRIBE") { }; if (method=="NOTIFY") { }; I couldn't find any examples and Google also didn't find anything that pointed me in the right direction. Thanks! -- Andreas Sikkema

4 5

Res: [Users] LCR module (1.2.0)
by Bruno Machado 03 May '07

03 May '07

Other thing: the 1.2.0 is using the priority in contrary? prefix----------from_uri-------grp_id--------priority 0123456------------------------------ 1 ---------------1 0123456----------------------------- 2 ---------------0 When I called to 01234560000, GW 1 was selected. In version 1.1.0, the GW 2 will be selected because it has the minor number. Bruno ----- Mensagem original ---- De: Juha Heinanen <jh(a)tutpro.com> Para: Bruno Machado <bsmufu(a)yahoo.com.br> Cc: users(a)openser.org Enviadas: Quinta-feira, 3 de Maio de 2007 12:36:33 Assunto: [Users] LCR module (1.2.0) Bruno Machado writes: > prefix----------from_uri-------grp_id--------priority > 0123456------------------------------ 1 ---------------1 > 0________------^sip:123.*--------- 2 ---------------0 > > Ok. The LCR documentation tells that the column 'from_uri' must be a > regular expression in this version. The route selected is the first > line. I'd like to route the voip number 123 through GW 2, but it > doesn't happens. i don't understand based on the above, how your lcr table looks like and which uri you are trying to call. what are the underscores after 0? prefix is just a prefix, nothing else. -- juha __________________________________________________ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/

1 0

[Users] LCR module (1.2.0)
by Bruno Machado 03 May '07

03 May '07

Hi I'm in trouble with the new version 1.2.0. Before migration to 1.2.0, the LCR table was working without problems. The table has these lines now: prefix----------from_uri-------grp_id--------priority 0123456------------------------------ 1 ---------------1 0________------^sip:123.*--------- 2 ---------------0 Ok. The LCR documentation tells that the column 'from_uri' must be a regular expression in this version. The route selected is the first line. I'd like to route the voip number 123 through GW 2, but it doesn't happens. I already reloaded the table, restarted the proxy... all this things. Certainly, I'm doing something wrong. What I should do? Thanks in advance. Bruno Machado __________________________________________________ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/

2 1

[Users] Increase or Decrease openser debug value without restarting openser
by mailinglist-openser-users 03 May '07

03 May '07

Hi, openser 1.2.0. In the "openser.cfg", there is the "debug" variable which increase or decrease the verbosity of openser and its modules as well as the xlog I would like to know if it is possible to change the debug value without having to restart openser in order to be able to troubleshoot a problem without having to restart openser. Regards, Jerome -- Jerome

2 1

[Users] mediaproxy errors
by Helge Waastad 03 May '07

03 May '07

Hi, I'm running mediaproxy 1.8.2 and have started to se: error: uncaptured python exception, closing channel <rtphandler.CommandHandler connected <ip-address>:42224 at 0x2a99dff518> (socket.error:(9, 'Bad file descriptor') [/usr/lib64/python2.3/asyncore.py|readwrite|88] [/usr/lib64/python2.3/asyncore.py|handle_write_event|397] [/etc/mediaproxy/modules/rtphandler.py|handle_write|453] [/usr/lib64/python2.3/asyncore.py|send|337]) does anyone knw what this means? br hw -- Helge Waastad Senior developer Smartnet / Datametrix Et selskap i Ignis gruppen Martin Lingesvei 25 1367 Snarøya Postboks 494 1327 Lysaker Telefon: +47 67830017 Mobil: +47 48095461 Support: +47 67830045 - support(a)smartnet.no www.smartnet.no

2 2

[Serusers] record_route..........TCP ??
by KUMAR 03 May '07

03 May '07

Hi all, I am using SER-0.9.6 and the problem i'm having is this. When using the following ser.cfg, it works well when the transport UDP is used. But when transport TCP is used, then it only results in one way IM, only from the UA from which the INVITE is being sent. Moreover, when record_route is used instead of record_route_preset, then even that one way IM doesn't work. But it works well with UDP. Can anyone please point me as to where the problem might be?? Thank you in advance. kumar

2 2

Re: [Serusers] help with error
by Klaus Darilion 03 May '07

03 May '07

A client REGISTERs and REGISTERs and REGISTERs and somehow ser does not detect that this is always the same client and creates a new entry in the location table. This may happen e.g. with buggy NATs which changes the port for every REGISTER or with buggy clients. Thus, limit the number of max entries in location table: http://www.openser.org/docs/modules/0.9.x/registrar.html#AEN167 and set desc_time_order to 1 http://www.openser.org/docs/modules/0.9.x/registrar.html#AEN167 although this is openser I think these parameters also exists in ser. There is no need to change MAX_BRANCHES. Fix the problem by limiting the entries in the location table. regards klaus Steve Blair wrote: > > Klaus: > > It seems the only way to increase the limit is to change MAX_BRANCHES > then re-compile SER. I do not think that approach is best. Can you think > of any other reason why this error would be generated? > > Thanks,Steve > > Klaus Darilion wrote: >> I guess there are more then "max-branches" entries in location table >> (for this user). >> >> regards >> klaus >> >> Steve Blair wrote: >>> >>> I'm getting the following error on a ser-0.9.7 system and I cannot >>> figure out why. I see the message originates in dset.c but the cause >>> of the error is unclear. Any thoughts? >>> >>> Thanks,Steve >>> >>> ERROR: append_branch: max nr of branches exceeded >>> lookup(): Error while appending a branch >>> _______________________________________________ >>> Serusers mailing list >>> Serusers(a)lists.iptel.org >>> http://lists.iptel.org/mailman/listinfo/serusers >>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users