sr-users

sr-users@lists.kamailio.org

13 participants
37464 discussions

Re: [OpenSER-Users] dialog matching criteria
by Jayesh Nambiar 01 Apr '08

01 Apr '08

Hi Bogdan, Thanks for your reply. I tried of acheiving the same as follows: Enabled DB support for dialog module. If the called number is 123456, I first query the dialog table to retreive the count on to_uri and compare it with a certain limit value. If the count is equal to or greater than the limit value, just reply as 403, Forbidden. I am about to finish this today and will let you know the results. I just wanted an expert advice on if the logic is ok and efficient. Also there is a column in the dialog table which is caller_route_set and callee_route_set, can someone please tell me from where these values are retreived from as it stays blank while checking the dlg_list. Also is it possible to insert some custom value in this column to implement any further logic. Thanks, w/regards, Jayesh ----- Original Message ---- From: Bogdan-Andrei Iancu <bogdan(a)voice-system.ro> To: Jayesh Nambiar <voip_freak(a)yahoo.co.in> Cc: users(a)lists.openser.org Sent: Monday, 31 March, 2008 5:34:05 PM Subject: Re: [OpenSER-Users] dialog matching criteria Hi Jayesh, Such support is not available, but it is on the roadmap for 1.4. Regards, Bogdan Jayesh Nambiar wrote: > Hi All, > Is there a way in dialog module that I can keep count of active > dialogs based on certain parameters like ruri, to_uri etc. > For example, if i need to do a check of active dialogs on a called > number which is 123456 and take certain actions if the number of > active dialogs to called number 123456 is greater than or equal to > certain integer value. > > Is the above requirement a possibility in openser? > Any help regarding this will be highly appreciated. > > Thanks in advance. > > w/regards, > Jayesh > > ------------------------------------------------------------------------ > Get the freedom to save as many mails as you wish. Click here to know > how. > <http://in.rd.yahoo.com/tagline_mail_5/*http://help.yahoo.com/l/in/yahoo/mai…> > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users(a)lists.openser.org > http://lists.openser.org/cgi-bin/mailman/listinfo/users > Forgot the famous last words? Access your message archive online at http://in.messenger.yahoo.com/webmessengerpromo.php

1 0

[OpenSER-Users] Effect of use_domain in registrar module
by Chahn Kim 31 Mar '08

31 Mar '08

Hi, all Currently we are running Openser 1.1 registering ATAs just with user name only. This works fine however it generates minor problem with our Python based monitoring script. The script was written under assumption of non blank domain list. resulting only showing those sessions where the user location table has domain field manually inserted. Before we switch to use_domain parameter to 1, We'd like to know any implicit effect of doing it, as well as some questions answered. Q. 1) Does this setting takes "SIP_DOMAIN" env parameter of server itself or the client ATA must send it to Openser in "REGISTER"? Q. 2) Once use_domain in registrar is set to 1, would there be any impacts on existing ATA entries in location table with blank domain? Q. 3) Are there any other parameter that are required to be changed along with use_domain in registrar module? Any comments will be appreciated. John Chahn Kim email: johnk(a)koreanet.us

2 1

[Serusers] Effect of use_domain in registrar module
by Chahn Kim 31 Mar '08

31 Mar '08

1 0

[OpenSER-Users] Res: OpenSER and radiusclient-ng [Unknown Attribute]
by Flavio Goncalves 31 Mar '08

31 Mar '08

Kyle, Check your radius dictionaries and the order of the includes. You are probably not including OpenSER (SIP) attributes. Regards, Flavio E. Goncalves ----- Mensagem original ---- De: Krom <kyle.romulas(a)gmail.com> Para: users(a)lists.openser.org Enviadas: Segunda-feira, 31 de Março de 2008 16:07:00 Assunto: [OpenSER-Users] OpenSER and radiusclient-ng [Unknown Attribute] Parallel posting this to both CDRTool users and OpenSER users, so apologies to members of both. I have installed the latest version of CDRTool and running it with OpenSER 1.1.1 for the time being. When looking at the tcpdump of the records leaving the OpenSER server via radiusclient-ng I am viewing a few 'Unknown Attribute' statements. Ex: Accounting Status Attribute (40), length: 6, Value: Start Service Type Attribute (6), length: 6, Value: #15 Unknown Attribute (102), length: 6, Value: Unknown Attribute (101), length: 6, Value: Username Attribute (1), length: 26, Value: +15552221111(a)x.x.x.x Calling Station Attribute (31), length: 24, Value: sip:+15552221111@x.x.x.x Called Station Attribute (30), length: 32, Value: sip:+15553334444@x.x.x.x Unknown Attribute (107), length: 35, Value: Accounting Session ID Attribute (44), length: 14, Value: 0d487415(a)mysipserver.com Unknown Attribute (104), length: 10, Value: Unknown Attribute (105), length: 7, Value: Unknown Attribute (103), length: 6, Value: Unknown Attribute (214), length: 15, Value: Unknown Attribute (215), length: 6, Value: Unknown Attribute (216), length: 32, Value: Event Timestamp Attribute (55), length: 6, Value: Thu Mar 27 11:01:23 2008 NAS IP Address Attribute (4), length: 6, Value: x.x.x.x NAS Port Attribute (5), length: 6, Value: 5060 Accounting Delay Attribute (41), length: 6, Value: 00 secs I have looked into the dictionary.ser and each of the Attributes are defined and the dictionary file that is defined in radiusclient.conf has the $INCLUDE dictionary.ser statement. Any hints, ideas or links would be appreciated. -- -- Krom kyle.romulas(a)gmail.com -----Anexo incorporado----- _______________________________________________ Users mailing list Users(a)lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users

2 1

[OpenSER-Users] OpenSER and radiusclient-ng [Unknown Attribute]
by Krom 31 Mar '08

31 Mar '08

Parallel posting this to both CDRTool users and OpenSER users, so apologies to members of both. I have installed the latest version of CDRTool and running it with OpenSER 1.1.1 for the time being. When looking at the tcpdump of the records leaving the OpenSER server via radiusclient-ng I am viewing a few 'Unknown Attribute' statements. Ex: Accounting Status Attribute (40), length: 6, Value: Start Service Type Attribute (6), length: 6, Value: #15 Unknown Attribute (102), length: 6, Value: Unknown Attribute (101), length: 6, Value: Username Attribute (1), length: 26, Value: +15552221111(a)x.x.x.x Calling Station Attribute (31), length: 24, Value: sip:+15552221111@x.x.x.x Called Station Attribute (30), length: 32, Value: sip:+15553334444@x.x.x.x Unknown Attribute (107), length: 35, Value: Accounting Session ID Attribute (44), length: 14, Value: 0d487415(a)mysipserver.com Unknown Attribute (104), length: 10, Value: Unknown Attribute (105), length: 7, Value: Unknown Attribute (103), length: 6, Value: Unknown Attribute (214), length: 15, Value: Unknown Attribute (215), length: 6, Value: Unknown Attribute (216), length: 32, Value: Event Timestamp Attribute (55), length: 6, Value: Thu Mar 27 11:01:23 2008 NAS IP Address Attribute (4), length: 6, Value: x.x.x.x NAS Port Attribute (5), length: 6, Value: 5060 Accounting Delay Attribute (41), length: 6, Value: 00 secs I have looked into the dictionary.ser and each of the Attributes are defined and the dictionary file that is defined in radiusclient.conf has the $INCLUDE dictionary.ser statement. Any hints, ideas or links would be appreciated. -- -- Krom kyle.romulas(a)gmail.com

1 0

[OpenSER-Users] compile Openser 1.3.1 with module carrierroute
by Samael - 31 Mar '08

31 Mar '08

Hi, I tried to compile Openser 1.3.1 with module carrierroute on CentOS 5 in a 64 bits architecture. I compiled the confuse library and when I tried to compile Openser 1.3.1 with carrierroute module show me this error # make prefix=/ include_modules="mysql snmpstats carrierroute" modules ... /usr/bin/ld: /usr/local/lib/libconfuse.a(confuse.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libconfuse.a: could not read symbols: Bad value collect2: ld devolviÃ³ el estado de salida 1 make[1]: *** [carrierroute.so] Error 1 make[1]: se sale del directorio `/fuentes/openser/openser-1.3.1-tls /modules/carrierroute' make: *** [modules] Error 2 Can you help me? . If you need more information ask me . Best regards

2 1

[OpenSER-Users] unable to find dialog for BYE
by Jayesh Nambiar 31 Mar '08

31 Mar '08

Hi All, I have recently upgraded to openser 1.3.1 and I am trying to explore the Dialog module. I want to maintain the dialog for specific set of calls, so I have defined a route and I have written setflag(4) in that route so that all calls getting into that route will have the dialogs maintained. Flag 4 is defined for dialog module. Now when the call initiator hangs up; the dialog starts and ends properly but when the called party hangs up, I get this message in the syslog: " unable to find dialog for BYE" Can someone please guide me on how to interpret this WARNING and what measures should be taken to avoid the same. Thanks in advance w/regards, Jayesh Save all your chat conversations. Find them online at http://in.messenger.yahoo.com/webmessengerpromo.php

3 2

[OpenSER-Users] [FEATURE REQ] allow does_uri_exist() to test against other variables besides $ru
by Mike Fedyk 31 Mar '08

31 Mar '08

Hi, Is there a better way to test if a call is from a registered user without authentication than the code below? If not, then let me request that does_uri_exist() take an argument specifying the variable to test against. Mike if (src_ip != 'x.x.x.28' && !lookup("location")) { if (registered("location")) { xlog("L_NOTICE", "cs<$cs> si<$si:$sp> ci<$ci> route3: matched registered()\n"); } if (!registered("location")) { xlog("L_NOTICE", "cs<$cs> si<$si:$sp> ci<$ci> route3: matched !registered()\n"); } ### send DIDs to asterisk directly because it doesn't handle unauthenticated calls via a proxy properly #change request uri to from uri so that does_uri_exist() can test against it $var(orig_ru) = $ru; $ru = $fu; if (does_uri_exist()) { xlog("L_NOTICE", "cs<$cs> si<$si:$sp> ci<$ci> route3: matched does_uri_exist()\n"); } if (!does_uri_exist()) { xlog("L_NOTICE", "cs<$cs> si<$si:$sp> ci<$ci> route3: matched !does_uri_exist()\n"); } #10 digit DID and is not from one of our users if ($var(orig_ru) =~ "^sip:[0-9]{10}" && !does_uri_exist()) { xlog("L_NOTICE", "cs<$cs> si<$si:$sp> ci<$ci> route3: 302 redirect to asterisk\n"); $var(dstredir) = "sip:" + $tU + "@x.x.x.28"; $ru=$var(dstredir); sl_send_reply("302", "Moved Temporarily"); exit; #route(1); }; #END DIDs to asterisk and change request uri back $ru = $var(orig_ru); }

2 1

[OpenSER-Users] dialog matching criteria
by Jayesh Nambiar 31 Mar '08

31 Mar '08

Hi All, Is there a way in dialog module that I can keep count of active dialogs based on certain parameters like ruri, to_uri etc. For example, if i need to do a check of active dialogs on a called number which is 123456 and take certain actions if the number of active dialogs to called number 123456 is greater than or equal to certain integer value. Is the above requirement a possibility in openser? Any help regarding this will be highly appreciated. Thanks in advance. w/regards, Jayesh Chat on a cool, new interface. No download required. Go to http://in.messenger.yahoo.com/webmessengerpromo.php

2 1

[OpenSER-Users] nat_uac_test("31") not enough to detect with some consumer voip passthrough routers
by Mike Fedyk 31 Mar '08

31 Mar '08

Hi, Some of our customers have been connecting behind NAT routers that mangle the sip headers but don't keep the ports open. I've added checks on the source port to catch this case. Has anyone done something similar or better? It'd be nice if this could be added as a flag to nat_uac_test() if it is a common test and there isn't already a better way. Here is the code I've used to handle my registers. I need to do more testing once I can get some of these routers in my lab to see how this affects call processing, not just registering. Mike if (!search("^Contact:\ +\*") && nat_uac_test("7")) { xlog("L_INFO", "M=$rm RURI=$ru F=$fu IP=$si:$sp CS=$cs route2: matched nat_uac_test7\n"); xlog("L_NOTICE", "M=$rm RURI=$ru F=$fu IP=$si:$sp CS=$cs route2: setbflag(6)\n"); setbflag(6); xlog("L_NOTICE", "M=$rm RURI=$ru F=$fu IP=$si:$sp CS=$cs route2: fix_natted_register()\n"); fix_nated_register(); #xlog("L_INFO", "M=$rm RURI=$ru F=$fu IP=$si:$sp CS=$cs route2: force_rport()\n"); #force_rport(); }; #Some NAT devices modify SIP headers to but do not keep the port mappings open, also some UAs detect report the #public IP address. In both cases we need nat ping. Exceptions for default ports. These ports if used as #source ports can be assumed to be at the very least port forwarded. if (!isbflagset(6) && $sp != '5060' && $sp != '5061') { xlog("L_NOTICE", "M=$rm RURI=$ru F=$fu IP=$si:$sp CS=$cs route2: matched !isbflagset(6) && ($sp != '5060' && $sp != '5061')\n"); setbflag(6); };

4 3

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