sr-users May 2008

sr-users@lists.kamailio.org

121 participants
203 discussions

Start a nNew thread

[OpenSER-Users] [Fwd: Re: facing problem]
by Amit Vijayvargiya 22 May '08

22 May '08

1 0

Re: [Serusers] ser/sems question
by Stefan Sayer 22 May '08

22 May '08

o Steven C. Blair [05/22/08 13:52]: > Thanks Stefan. Is the README for sems-1.0.0 correct? I'm questioning step #4. If I am running this version of SEMS on a Linux box without a proxy server, our proxy resides elsewhere, do I need to perform step #4? no, that is optional, and you only need to do that if you want SER as frontend to SEMS. That's why it says 'Optional' in in http://ftp.iptel.org/pub/sems/doc/current/Readme.html Stefan > > Thanks,Steve > >> -----Original Message----- >> From: Stefan Sayer [mailto:stefan.sayer@iptego.com] >> Sent: Wednesday, May 21, 2008 4:45 PM >> To: Steven C. Blair >> Cc: serusers(a)iptel.org >> Subject: Re: [Serusers] ser/sems question >> >> Hello, >> >> o Steven C. Blair [05/20/08 20:13]: >>> I've been away from SEMS for a few years. II hear the new version of >>> SEMS makes an excellent conference server. Does anyone happen to know >> if >>> I can install SEMS on a standalone Linux machine and interface it, >> via >>> SIP, to a SER 0.9.7-pre3 proxy server? >> yes, you can use it now with any SIP proxy thanks to its own SIP stack. ... -- Stefan Sayer VoIP Services stefan.sayer(a)iptego.com www.iptego.com iptego GmbH Am Borsigturm 40 13507 Berlin Germany Amtsgericht Charlottenburg, HRB 101010 Geschaeftsfuehrer: Alexander Hoffmann

1 0

[OpenSER-Users] Problem PUA_USRLOC, Presence acc. REGISTER/INVITE
by Schumann Sebastian 22 May '08

22 May '08

Dear all I have a problem, which I thought I can solve with PUA_USRLOC. I have a OpenSER SIP Proxy and want him to create presence information about the messages that pass him. Some examples: - REGISTER: Publish as online/available - REGISTER+Expires=0: Publish as offline - INVITE/200 OK: Publish as busy - BYE: Publish as available again. PUA_USRLOC seems to me can handle only simple on/offline according registration state, that is saved on the server. As I have only a proxy server and messages just pass by, this solution seems not the best. What would you recommend me to solve the problem? Change the module, add a module? As I don't have that much of experience in that area I was thinking about using perl module and trigger some perl functions that parse the messages that pass the proxy and make perl send the PUBLISHes to the presence server. Maybe some of you have other ideas or suggestions about that.... I would be happy if you share them with me. Best regards Sebastian

3 3

[OpenSER-Users] Does somebody use $(rU{s.unescape.user}) to be RFC3261 compliant?
by Iñaki Baz Castillo 22 May '08

22 May '08

Hi, to be RFC3261 compliant a SIP proxy should accept hex encoded username in any URI, this is: sip:alice@domain == sip:%61l%69ce@domain For allowing this we must use, explicitely, the transformation $(rU{s.unescape.user}). Do OpenSer administrators allow this hex encoding? -- Iñaki Baz Castillo ibc(a)in.ilimit.es

2 3

[OpenSER-Users] Small documentation mistake pua_usrloc
by Schumann Sebastian 22 May '08

22 May '08

Dear all I noticed a small mistake in the documentation: I had some errors in config file using the pua_usrloc modparam parameters with copy & paste. The problem were the semicolons ; behind the modparam definitions. As I had the error some time ago already I easily figured that out. Although, it might be good to remove them from the doc for other users in the future to not have the same problem as well. Best regards Sebastian

3 3

[Serusers] Creating SIP trunk from OpenSER to Cisco CallManager
by G. Ross 22 May '08

22 May '08

Hi, I've been tasked with getting an OpenSER system to talk to a Cisco CallManager system.I've tried searching the docs, the mailing lists and google, but all my searches end up with references to the "trunk" in the source code repository. Can someone point me somewhere which could help me in this task ? Thanks, GTG

2 1

[OpenSER-Users] facing problem
by Amit Vijayvargiya 22 May '08

22 May '08

Hi, I am facing a problem when user is online more then one machines, openser not able to send request to all machines. Thanks in advance Amit

3 3

[Serusers] ser/sems question
by Steven C. Blair 21 May '08

21 May '08

I've been away from SEMS for a few years. II hear the new version of SEMS makes an excellent conference server. Does anyone happen to know if I can install SEMS on a standalone Linux machine and interface it, via SIP, to a SER 0.9.7-pre3 proxy server? Thanks,steve Senior Network Engineer, Information Systems and Computing Networking and Telecommunications , Suite 221A /6228 University of Pennsylvania Voice:215-573-8396 FAX:215-898-9348

2 1

[OpenSER-Users] v1.3.2 , presence hash table error
by Jeremy George 21 May '08

21 May '08

Hello All, BLA was working nicely for me with v1.3.0 and Polycom 3.0.0 phones. I downloaded 1.3.2 and I'm now getting this error on the presence server. I tried adding the hash table modparams explicitly, but with got the same error message. modparam("presence", "subs_htable_size", 11) modparam("presence", "pres_htable_size", 11) Thoughts? And thanks. May 20 11:44:35 [12319] ERROR:presence:get_stored_info: record not found in hash_table May 20 11:44:35 [12319] ERROR:presence:handle_subscribe: getting stored info - Jeremy

2 1

[OpenSER-Users] Unable to do transformation on expires param if display name present
by Robert Dyck 21 May '08

21 May '08

I am currently using 1.3.2 but this problem exists in older versions as well. My config script includes a transformation on the expires parameter in a Contact header. I have found that a Linksys SPA3000 will include the display name in the Contact header and that there is white space between the display name and the URI. The function parse_param_name in parse_param.c will stop parsing when it encounters the white space. As a workaround I commented the line in parse_param_name that checks for white space. This works for me but I do not know if there are side effects. This form of Contact is not common but it appears to be legal according to RFC 3261. 20.10 Contact A Contact header field value provides a URI whose meaning depends on the type of request or response it is in. A Contact header field value can contain a display name, a URI with URI parameters, and header parameters. This document defines the Contact parameters "q" and "expires". These parameters are only used when the Contact is present in a REGISTER request or response, or in a 3xx response. Additional parameters may be defined in other specifications. When the header field value contains a display name, the URI including all URI parameters is enclosed in "<" and ">". If no "<" and ">" are present, all parameters after the URI are header parameters, not URI parameters. The display name can be tokens, or a quoted string, if a larger character set is desired. Even if the "display-name" is empty, the "name-addr" form MUST be used if the "addr-spec" contains a comma, semicolon, or question mark. There may or may not be LWS between the display-name and the "<". Here is an excerpt from my script -- if ((is_present_hf("Expires") && $(hdr(Expires) {s.int}) == 0)\ ||($(ct{param.value,expires}) == '0')) { log(1, "looks like deregistration\n"); I added some debug messages to illustrate the problem -- May 19 22:16:32 [14447] DBG:core:parse_param_name: string passed to parse_param_name is RJD <sip:17476316719@192.168.1.4:5061>;expires=3600 May 19 22:16:32 [14447] DBG:core:parse_param_name: next char is R May 19 22:16:32 [14447] DBG:core:parse_param_name: next char is J May 19 22:16:32 [14447] DBG:core:parse_param_name: next char is D May 19 22:16:32 [14447] DBG:core:parse_param_name: next char is May 19 22:16:32 [14447] ERROR:core:parse_params: invalid character, ; expected May 19 22:16:32 [14447] DBG:core:run_transformations: return val is -1 May 19 22:16:32 [14447] CRITICAL:core:comp_scriptvar: cannot get left var value May 19 22:16:32 [14447] WARNING:core:do_action: error in expression

2 4

← Newer
1
...
8
9
10
11
12
13
14
...
21
Older →

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 May 2008