sr-users

sr-users@lists.kamailio.org

25 participants
37536 discussions

RE: [Serusers] global contact list
by Barta János 03 Apr '07

03 Apr '07

Hello! Thanks for your answer. I'm using the standard config file (http://ftp.iptel.org/pub/ser/presence/cfg/full-no-failover.cfg), with a little modification, because I'm using radius authentication, accounting and media proxy. loadmodule "/opt/lib/ser/modules/acc_radius.so" loadmodule "/opt/lib/ser/modules/mediaproxy.so" loadmodule "/opt/lib/ser/modules/auth_radius.so" modparam("acc_radius","radius_config","/etc/radiusclient-ng/radiusclient.conf") modparam("acc_radius", "log_flag", 1) modparam("acc_radius", "log_missed_flag", 2) modparam("rls", "db_url", "mysql://yyyyyyy:xxxxxx@10.22.1.222/ser_pa") modparam("domain|uri_db|auth_db|usrloc|msilo", "db_url", "mysql://yyyyyyy:xxxxxx@10.22.1.222/ser_pa") if ((method=="INVITE") or (method=="BYE") or (method=="CANCEL")) { setflag(1); } if (!radius_www_authorize("test.intra")) { www_challenge("test.intra", "0"); break; }; handle_rls_subscription("1"); route[1] { if (method=="INVITE") { t_on_reply("1"); t_on_failure("1"); use_media_proxy(); } else if (method=="BYE|CANCEL") { end_media_session(); } # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; } onreply_route[1] { if (status=~"(183)|2[0-9][0-9]") { use_media_proxy(); }; if (status=~"[3-6]0[0-9]") { end_media_session(); break; } } failure_route[1] { # forwarding failed -- check if the request was a MESSAGE if (!method=="MESSAGE") { break; }; log(1, "MSILO: MESSAGE forward failed - storing it\n"); # we have changed the R-URI with the contact address, ignore it now if (m_store("0", "")) { t_reply("202", "Accepted"); } else { log(1, "MSILO: offline message NOT stored\n"); t_reply("503", "Service Unavailable"); }; end_media_session(); } ----------------- I made a capture with Ethereal, and I can see that eyeBeam sent the "Supported: eventlist" field. I inserted the lists of both type: Global-list: Message Header Via: SIP/2.0/UDP 10.22.2.134:9510;branch=z9hG4bK-d87543-dd118615e6316f41-1--d87543- Max-Forwards: 70 Contact: <sip:12345@10.22.2.134:9510> To: <sip:bartaj-list@test.intra> SIP to address: sip:bartaj-list@test.intra From: "12345"<sip:12345@test.intra>;tag=0a48df34 SIP Display info: "12345" SIP from address: sip:12345@test.intra SIP tag: 0a48df34 Call-ID: ee79a62abd227204@S2FhbGlhLXhwLndlc3RlbC53ZXN0ZWw5MDAuaHU. CSeq: 1 SUBSCRIBE Expires: 60 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Supported: eventlist User-Agent: CounterPath eyeBeam Event: presence Content-Length: 0 User-list: Message Header Via: SIP/2.0/UDP 10.22.2.134:9510;branch=z9hG4bK-d87543-6300f275d049656e-1--d87543- Max-Forwards: 70 Contact: <sip:12345@10.22.2.134:9510> To: <sip:12345@test.intra> SIP to address: sip:12345@test.intra From: "12345"<sip:12345@test.intra>;tag=cb3e2c5c SIP Display info: "12345" SIP from address: sip:12345@test.intra SIP tag: cb3e2c5c Call-ID: a46e4b35e4754144@S2FhbGlhLXhwLndlc3RlbC53ZXN0ZWw5MDAuaHU. CSeq: 1 SUBSCRIBE Expires: 3600 Accept: message/external-body Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Supported: eventlist User-Agent: CounterPath eyeBeam Event: sip-profile;profile-type=application;app-id=resource-lists Content-Length: 0 The second case is working, but the first one is not. Is this maybe an EyeBeam problem? Which version of EyeBeam works fine (or which other client can I test it with)? And I have another question. What can I do with those clients, that does not support the presence information (can I do something anyway?). For example: I have a "Cisco Call Manager Express" box, and some Cisco IP Phones, that reach other PC clients through the SER. The Cisco makes the registration (and reregistration) with the phone's identifiers too into the SER (but the presence information is not handled by the Cisco), and therefore if a PC client would like to add the Cisco phone into his buddy list, the presence won't be working. ...Record(0x405cc588)... domain: 'location' aor : '101$' ~~~Contact(0x405cc5c8)~~~ domain : 'location' aor : '101$' Contact : 'sip:101$@10.22.2.233:5060' Expires : Expired q : Call-ID : '9C5717E5-D7D211DB-804EA958-71810899' CSeq : 4103 User-Agent: 'Cisco-SIPGateway/IOS-12.x' received : '' State : CS_SYNC Flags : 0 next : (nil) prev : (nil) ~~~/Contact~~~~ .../Record... ...Record(0x405cc698)... domain: 'location' aor : '100$' ~~~Contact(0x405cc6d8)~~~ domain : 'location' aor : '100$' Contact : 'sip:100$@10.22.2.233:5060' Expires : Expired q : Call-ID : '9C5717E5-D7D211DB-804DA958-71810899' CSeq : 1364 User-Agent: 'Cisco-SIPGateway/IOS-12.x' received : '' State : CS_SYNC Flags : 0 next : (nil) prev : (nil) ~~~/Contact~~~~ .../Record... Is it possible, that the SER (in these cases) simulates a presence client (if the user registration is active, then the user is online, anyway offline)? Thanks, Jani -----Original Message----- From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] Sent: Wednesday, March 28, 2007 3:46 PM To: Barta János Cc: serusers(a)iptel.org Subject: Re: [Serusers] global contact list Hi, please can you send here your config file? By the way, in some EyeBeam versions was not possible to use "Subscribe to contact list" feature because in such cases EyeBeam didn't send header "Supported: eventlist". Vaclav On Tue, Mar 27, 2007 at 08:54:15AM +0200, Barta János wrote: > Hello! > > I have a little problem with the (global) contact list subscription > of the presence, please help me. > I installed the presence server (0.10.99-dev35-pa-4.1), and it works > without any problems. > But I can not use the "Subscribe to contact list" of the eyeBeam. (The > user subscribe list works fine.) I typed the next content into this > field (of the eyeBeam): > > sip:bartaj-list@test.intra > > > and my config file contains: > > sip:/var/xcap-root/rls-services/global# cat ./index <?xml > version="1.0" encoding="UTF-8"?> <rls-services> > > <service uri="sip:bartaj-list@test.intra"> > <list name="Human resources"> > <entry uri="sip:test1@test.intra"> > > <display-name>bartaj</display-name> > </entry> > <entry uri="sip:test2@test.intra"> > > <display-name>12345</display-name> > </entry> > </list> > <packages> > <package>presence</package> > </packages> > </service> > > </rls-services> > > But I can see only the user subscribe list, and can't see the global > one. > Why? > Can anybody help me? > Thx, > Jani > _____________________________________________________________________________________________________ Jean Michel Jarre: Téo és Téa, az új, ünnepi album 1990 Forintért, kizárólag a T-Online Zeneáruházban! http://zenearuhaz.t-online.hu/index.php?m=info&albumid=30593&sp=1&sty=21

2 1

[Users] [resolv] radius problem in 1.2
by Bodin Bruno 03 Apr '07

03 Apr '07

Hello, During few days I've a problem with openser 1.2 and radius authentication but I just solve it ! This is a little note about my method. *Please, you're welcome to check and comment it for a better solution.* *Issue* : Radius authentication fail for openser 1.2 but not for 1.1.1 version with the same config. *Description* : freeradius server sucess (Sending Access-Accept in log) but it's not good in openser log. *Search method* : analyse of differences between 1.1.1 and 1.2 version >lsof | grep radius | grep -v radiusd /_openser 1.1.1_/ : openser 6226 root mem REG 8,2 50984 1333396 /usr/lib64/libradiusclient-ng.so.2.0.0 openser 6226 root mem REG 8,2 71642 30076344 /opt/openser-1.1.1/lib64/openser/modules/auth_radius.so openser 6226 root mem REG 8,2 41637 30076357 /opt/openser-1.1.1/lib64/openser/modules/group_radius.so openser 6226 root mem REG 8,2 43683 30076346 /opt/openser-1.1.1/lib64/openser/modules/avp_radius.so openser 6226 root mem REG 8,2 38171 30389824 /opt/openser-1.1.1/lib64/openser/modules/uri_radius.so _/openser1.2 :/_ openser 6299 root mem REG 8,2 50952 1333316 /usr/lib64/libfreeradius-client.so.2.0.0 openser 6299 root mem REG 8,2 76493 30356347 /opt/openser-1.2/lib64/openser/modules/auth_radius.so openser 6299 root mem REG 8,2 41769 30356361 /opt/openser-1.2/lib64/openser/modules/group_radius.so openser 6299 root mem REG 8,2 44923 30356349 /opt/openser-1.2/lib64/openser/modules/avp_radius.so openser 6299 root mem REG 8,2 39411 30076331 /opt/openser-1.2/lib64/openser/modules/uri_radius.so *openser 1.2.0 use libfreeradius-client.so.2.0.0 openser 1.1.1 use libradiusclient-ng.so.2.0.0 * * my solve method :* >cd /usr/lib64/ >mv libfreeradius-client.so.2.0.0 libfreeradius-client.so.2.0.0.old >ln -s libradiusclient-ng.so.2.0.0 libfreeradius-client.so.2.0.0

2 1

[Users] DLG: BYE not detected because of route reccord
by Michel Bensoussan 03 Apr '07

03 Apr '07

Hello The dialog module checks SIP messages only if the OpenSER in on record-route header in function dlg_onroute(). When the callee in registered on another SIP Server and the callee sends BYE, the OpenSER is not on record-route header. In this case, the dialog module doesn't detect end of call. Is there a way to callback the dlg_onroute() function not only in case of record-route? The configuration is as following: - Tel 101 registered to 192.168.13.8 (siproxd) (URI: 101(a)192.168.13.8) (IP: 192.168.13.101) - Tel 155 registered to 192.168.13.86 (OpenSER) (URI: 155(a)192.168.13.86) (IP: 192.168.13.155) - 155 is the caller and 101 is the callee. Attached, message capture (ethereal) when the callee (101) terminate the call. Thanks. Regards, Michel.

2 5

[Users] BUG in TM
by Sam Lee 03 Apr '07

03 Apr '07

Hey guys, I'm getting BUG:tm:run_failure_handlers: stack level is 1!! in my syslog. It is generating when i place a call out to PSTN. Any ideas ? Sam

2 5

Re: [Users] Module UAC to authentication and redirect calls
by Bogdan-Andrei Iancu 03 Apr '07

03 Apr '07

See the "credential" module parameter: http://www.openser.org/docs/modules/1.2.x/uac.html#AEN106 regards, bogdan Thiago Maluf wrote: > what`s parameters I will use to do this authentication? > > 2007/3/2, Bogdan-Andrei Iancu < bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>>: > > Hi, > > try something like: > > failure_route[1] { > xlog("-----------$T_reply_code ---------\n"); > if (t_check_status("401|407")) { > log(1,"doing auth\n"); > if (uac_auth()) { > append_branch(); > t_relay(); > } > } > } > > regards, > bogdan > > Thiago Maluf wrote: > > Hi List, > > I need config one module UAC to do authentication and redirect my > > calls to other Voip Provider. > > Somebody already did it? If can tell me what functions you used. > > Thanks in advanced! > > Thiago Maluf. > > > > ---------------------------------------------------------------- > > THIAGO MALUF RESENDE > > Consultor Voip e Programador WEB (Voip Developer and Web Developer) > > e-mail: malufrj(a)gmail.com <mailto:malufrj@gmail.com> <mailto: > malufrj(a)gmail.com <mailto:malufrj@gmail.com>> > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org <mailto:Users@openser.org> > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > -- > ---------------------------------------------------------------- > THIAGO MALUF RESENDE > Consultor Voip e Programador WEB (Voip Developer and Web Developer) > Tel: +55 21 86042100 > e-mail: malufrj(a)gmail.com <mailto:malufrj@gmail.com>

1 0

Re: [Users] 3xx requests and t_relay
by Bogdan-Andrei Iancu 03 Apr '07

03 Apr '07

Hi Shane, please post the network trace from the the server and the full debug log of openser (use debug=9). regards, bogdan Shane Burrell wrote: > I used that as an example. On the sip side I see the 302 come back and the > openser ack it. Then I never see the new call go out. The user gets a busy > or not avaible message from the switch. In openser I have some logging and > it seems to start a new route after the ACK but bombs somewhere. > > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Wednesday, February 28, 2007 12:54 PM > To: Shane Burrell; users openser.org > Subject: Re: [Users] 3xx requests and t_relay > > Hi Shane, > > have you followed this ex: > http://www.openser.org/docs/modules/1.2.x/uac_redirect.html#AEN251 > > can you be more specific about the errors you see? > > regards, > bogdan > > Shane Burrell wrote: > >> I am calling the t_relay after getting the contacts. However internally I >> see in openser it makes it back to the route and then dies in loose route. >> I assumed there was something I need to check to allow the new call to be >> processed. >> >> -----Original Message----- >> From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] >> Sent: Wednesday, February 28, 2007 12:26 PM >> To: Shane Burrell >> Cc: users(a)openser.org >> Subject: Re: [Users] 3xx requests and t_relay >> >> Hi, >> >> let me see if I get it right...you get a 3xx reply and try to generate >> INVITE to the new contacts? if so, take a look at the uac_redirect module. >> >> regards, >> bogdan >> >> Shane Burrell wrote: >> >> >>> I have this working to the point it tries to relay the call but I see >>> that internally openser is not making the new call. I assume t_relay >>> calls a new route but how to I make sure that all relays get >>> forwarded. Some of my logic else where seems to be killing the >>> rerouted call and I need any 302 routed calls to be accepted and routed. >>> >>> >>> >>> TIA, >>> >>> >>> >>> Shane >>> >>> >>> *************************************************************** >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)openser.org >>> http://openser.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >> >> > > >

1 0

[Users] TCP lifetime
by Klaus Darilion 03 Apr '07

03 Apr '07

Hi! I thought setting the tcp_connection_lifetime to 0 should keep them open endlessly, but in my case the proxy closes the TCP connection ~10 seconds after the last SIP message. What am I doing wrong? regards klaus -- Klaus Darilion nic.at

2 7

[Users] NEW FEATURE: IP blacklists
by Bogdan-Andrei Iancu 03 Apr '07

03 Apr '07

Hi everybody, OpenSER 1.2.0 has new feature - IP Blacklist support. This is a low level filtering engine for the outgoing requests; low level, because the filtering is done based on IP, protocol, port, etc. Its primary purposes will be to prevent sending requests to critical IPs (like GWs) due DNS or to avoid sending to destinations that are known to be unavailable (temporary or permanent). Because of flexibility concerns, the filtering rules can be groups inside multiple lists. A rule: - matches based on IP/mask, proto, port and text pattern criteria - can be reversed applied A list: - can be read-only - it does not change during execution - have timeout per elements - elements expires after a configured timeout. How to use: =========== currently there are 2 ways of using the blacklists: 1) statically defining list in the configuration file and selecting which ones should be used for each request. You can define blacklists as follow: # filter out requests going to ips of my gws dst_blacklist = gw:{( tcp , 192.168.2.100 , 5060 , "" ),( any , 192.168.2.101 , 0 , "" )} # block requests going to "evil" networks dst_blacklist = net_filter:{ ( any , 192.168.1.100/255.255.255.0 , 0 , "" )} # block message requests with nasty words dst_blacklist = msg_filter:{ ( any , 192.168.20.0/255.255.255.0 , 0 , "MESSAGE*ugly_word" )} # block requests not going to a specific subnet dst_blacklist = net_filter2:{ !( any , 192.168.30.0/255.255.255.0 , 0 , "" )} a rule is defined by: protocol : TCP, UDP, TLS or "any" for anything port : number or 0 for any ip/mask test patter - is a filename like matching (see "man 3 fnmatch") applied on the outgoing request buffer (first_line+hdrs+body) From routing script, you can use the use_blacklist("name") function to select what blacklist to be applied for the current request. More than one list can be selected. If the destination address matches on of the selected rules, the send will fail. 2) via DNS The DNS resolver, when configured with failover, can automatically store in a temporary blacklist the failed destinations. This will prevent (for a limited period of time) openser to send requests to destination known as failed. So, the blacklist can be used as a memory for the DNS resolver. To use it, you have to enabled it - the rest is done automatically. disable_dns_blacklist = no By default is enabled. The temporary blacklist created by DNS resolver is named "dns" and it is by default selected for usage (no need use the use_blacklist() function. The rules from this list have a life time of 4 minutes - you can change it at compile time, from blacklists.h . To give you an internal snapshot, a new MI function - "list_blacklists" - was added to print all existent blacklists and their rules. Any suggestions/reports are welcome! regards, bogdan

2 5

re: [Users] SIPp and registration
by yanlin 03 Apr '07

03 Apr '07

Hi, Scott Yagel, you could find some clues in the file scenario.cpp of sipp project. there were some embeded scenario scripts in sipp, stored in char* default_scenario[], you can sent a register sip message by doing this: " <send retrans=\"500\">\n" " <![CDATA[\n" "\n" " REGISTER sip:CA.cym.com SIP/2.0\n" " Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]\n" " From: ua1 <sip:ua1@nnl.cym:[local_port]>;tag=[pid]SIPpTag07[call_number]\n" " To: ua1 <sip:ua1@nnl.cym:[local_port]>\n" " Call-ID: [call_id]\n" " CSeq: 1 REGISTER\n" " Contact: sip:ua1@[local_ip]:[local_port]\n" " Content-Length: 0\n" " Expires: 300\n" "\n" " ]]>\n" " </send>\n" regards. Yan Lin

2 1

[Users] What does this mean?
by nick 03 Apr '07

03 Apr '07

pre_auth(): Credentials with given realm not found After looking around google it seems to be based on the fact that the first sip: value doesn't contain the userid (if I understand correctly...) I can't figure out exactly why the RURI is coming in this fashion.. Should I be changing something in the clients, or my config?? These worked on an older config, now with this section, they just don't get accepted. I've tried it with and without sipserver.mobilia.it in the realm. I've also tried it with the server generating ha1 and static ha1 (from the ha1 and ha1b fields in the db), no difference. I have use domain 1 in registrar and auth_db, and strip "sipserver." sl_send_reply("100", "Trying"); if(!www_authorize("", "subscriber")) { xlog("L_INFO", "Register authentication failed - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); www_challenge("", "1"); exit; } Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: New request - M=REGISTER RURI=sip:mobilia.it F=sip:rice@mobilia.it T=sip:rice@mobilia.it IP=x.x.x.105 ID=fmq-17240(a)x.x.x.105 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=100 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: get_hdr_field: cseq <CSeq>: <100> <REGISTER> Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: DEBUG:maxfwd:is_maxfwd_present: value = 70 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=200 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: DEBUG: get_hdr_body : content_length=0 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: found end of header Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: find_first_route: No Route headers found Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: loose_route: There is no Route HF Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=ffffffffffffffff Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: check_via_address(x.x.x.105, x.x.x.105, 0) Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=4000 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: pre_auth(): Credentials with given realm not found Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: Register authentication failed - M=REGISTER RURI=sip:mobilia.it F=sip:rice@mobilia.it T=sip:rice@mobilia.it IP=x.x.x.105 ID=fmq-17240(a)x.x.x.105 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: build_auth_hf(): 'WWW-Authenticate: Digest realm="mobilia.it", nonce="460b9118a6a044d8837a01f924be2a9a3b7e0271", qop="auth"^M '

4 5

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