sr-users July 2007

sr-users@lists.kamailio.org

163 participants
262 discussions

[OpenSER-Users] SIP Trunking in openser
by Rizwan Hisham 04 Jul '07

04 Jul '07

Hi all, i tried to throw all my INVITE messages to an external IP address by using the rewritehost function. but calls from my openser dont passthru. i need to implement a sip trunk and throw my calls thru sip trunk to an external ip. how should i do this? I am a new user, so whatever your answer is, plz try to elaborate a little more. thanx -- Best Regards Rizwan Hisham Software Engineer AXVOICE Inc. www.axvoice.com

1 0

[OpenSER-Users] Why so many branches of openser?
by Rizwan Hisham 04 Jul '07

04 Jul '07

Hi all, I am a new user or openser. It is difficult for me to decide which release should i install on my computer as i have no knowledge of why there are so many branches of openser production. for startup, i have installed openser version 0.9.5. but i need to know whats the difference between 0.9.x 1.0.x 1.1.x and 1.2.x? -- Best Regards Rizwan Hisham Software Engineer AXVOICE Inc. www.axvoice.com

2 1

Re: [OpenSER-Users] help with using avp...
by Daniel-Constantin Mierla 04 Jul '07

04 Jul '07

On 07/04/07 09:26, liran tal wrote: > > Thank you very much Daniel. > I was mislead that such variables are not available on 1.1.1 and that > I have to > upgrade to 2.x to use it. It is on 1.1 as well, the link provided is for release 1.1.x. You have to use avpops functions in 1.1 to deal with them. Cheers, Daniel > > Thanks alot, it works just fine. > Liran. > > On 7/2/07, *Daniel-Constantin Mierla* <daniel(a)voice-system.ro > <mailto:daniel@voice-system.ro>> wrote: > > Hello, > > that's a standalone pseudo-variable you can use directlu: $au > http://www.openser.org/dokuwiki/doku.php/pseudovariables:1.1.x#auth_username > <http://www.openser.org/dokuwiki/doku.php/pseudovariables:1.1.x#auth_username> > > You do not need to play with such complex regexp subst. > > Daniel > > On 07/01/07 10:33, liran tal wrote: > > Hey everyone, > > > > I'm using OpenSER 1.1.1 SVN version. > > I'd like to save the Authorization Digest Username as it appears in > > header into a variable (avp) so > > that later I can use it to set an accounting attribute in the > radius. > > > > From the SIP Packet the information is given like this: > > Authorization: Digest username="dsdsds", realm=" 1.2.3.4 > <http://1.2.3.4> > > <http://1.2.3.4>", algorithm=MD5, uri="sip: 1.2.3.4 > <http://1.2.3.4> <http://1.2.3.4>", > > nonce="xxx" > > Where I would like to grab the username part "dsdsds". > > > > From the docs I could only conclude that doing it would be something > > like this: > > avp_write("$hdr[Authorization]","s:12"); > > avp_subst("$avp(s:12)", "/.*username=(.*),/\1/"); > > > > > > > > I'm not even sure about that piece of code, if someone can help... > > > > > > Thanks, > > Lir. > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org <mailto:Users@openser.org> > > http://openser.org/cgi-bin/mailman/listinfo/users > > > >

1 0

[Serusers] Number is Simultaneous calls
by Jai Rangi 04 Jul '07

04 Jul '07

Hello, Is there a module that can control number of simultaneous calls in ser. Fro example we want to allow max of 10 simultaneous calls for user A and 20 simultaneous calls for user B. How can I do that. Thank you, -Jai

2 1

Re: [OpenSER-Users] The Via Header of CANCEL Message
by fancy 04 Jul '07

04 Jul '07

Hi Bogdan: I did not use forward(), but I load sl module. And I did use sl_send_reply() to reply 483 and 513 message and sl_reply_error(). The attached file is my openser config file. I use this config file to run openser. The under RFC3665 section 3.8 condition, I got two Via headers as I mentioned before. So, according to my config file, Openser is a stateless proxy server under RFC3665 section 3.8's condition? Thank you. Best Regards, Fangyu Ling ----- Original Message ----- From: "Bogdan-Andrei Iancu" <bogdan(a)voice-system.ro> To: <fancy(a)cht.com.tw> Cc: <klaus.mailinglists(a)pernau.at>; <users(a)openser.org> Sent: Wednesday, July 04, 2007 2:53 PM Subject: Re: [OpenSER-Users] The Via Header of CANCEL Message > Hi Fangyu , > > My opinion is that the RFC3665 does not cover the stateless part. > > OpenSER can be both a stateless ans stateful proxy, it is just a matter > of configuration (what functions are you using). You can get pure > stateless or stateful cfg, or a mixed one, depending of you. > > If you use the TM function for relaying and replying you will get a pure > stateful proxy. For stateless functions, see the forward() or sl module. > > regards, > bogdan > > fancy wrote: >> Hi Bogdan: >> >> RFC3665 didn't mention any stateful or stateless >> within all the document. >> So I think it is just not covering it. >> >> By the way, is openser a stateless proxy server? >> I think it is a stateful proxy server! >> Can I config it to be a pure stateless or stateful proxy server? >> >> Thank you. >> >> Best Regards, >> Fangyu Ling >> >> >> >>> Klaus, >>> >>> CANCEL is hop-by-hop only in stateful processing and in this case, yes, >>> it has only on VIA. But if you have stateless processing, CANCEL is >>> end-2-end and it will have multiple VIAs... >>> >>> Does 3665 obsoletes stateless SIP or it is just not covering it??? >>> >>> regards, >>> bogdan >>> >>> Klaus Darilion wrote: >>> >>>> Looks like it is defined clearly and openser is not 100% standard conform. >>>> >>>> regards >>>> klaus >>>> >>>> fancy wrote: >>>> >>>> >>>>> Hi Klaus: >>>>> RFC 3665 page 54 line 4: >>>>> >> Sorry it's RFC 3261 page 54 line 4: >> >>>>> A CANCEL constructed by a >>>>> client MUST have only a single Via header field value matching the >>>>> top Via value in the request being cancelled. >>>>> >>>>> and RFC 3665 at page 53: >>>>> >> Sorry it's RFC 3261 at page 53: >> >>>>> CANCEL is referred to as a "hop-by-hop" request, since it is >>>>> responded to at each stateful proxy hop. >>>>> >>>>> and RFC 3665 at page 21: >>>>> >> Sorry it's RFC 3261 at page 21: >> >>>>> Client: A client is any network element that sends SIP requests >>>>> and receives SIP responses. Clients may or may not interact >>>>> directly with a human user. User agent clients and proxies are >>>>> clients. >>>>> >>>>> So, for my opinion, the role of proxy in this case of RFC 3665 section 3.8 is a client when it sends CANCEL message to Bob. >>>>> >>>>> If I misunderstand any RFC meanings, please correct me. >>>>> Thank you very much. >>>>> >>>>> Best Regards, >>>>> Fangyu Ling >>>>> >>>>> >>>>> >>>>> >>>>>> fancy wrote: >>>>>> >>>>>> >>>>>>> According to RFC 3665 section 3.8 and RFC 3261 section 9, >>>>>>> there is only one via header in CANCEL message >>>>>>> (message F11, F13 at page 72 of RFC 3665). >>>>>>> >>>>>>> >>>>>> Hi! >>>>>> >>>>>> I could find it in RFC 3665, but not in 3261. Where exactly in RFC 3261 >>>>>> is mentioned that the CANCEL has only 1 Via header? >>>>>> >>>>>> Further, the example has only one Via header - but I could not find any >>>>>> definition if this is a MUST or not. >>>>>> >>>>>> >>>>>> >>>>>>> How can I remove the 2nd via header?

1 0

Re: [OpenSER-Users] The Via Header of CANCEL Message
by fancy 04 Jul '07

04 Jul '07

Hi Bogdan: RFC3665 didn't mention any stateful or stateless within all the document. So I think it is just not covering it. By the way, is openser a stateless proxy server? I think it is a stateful proxy server! Can I config it to be a pure stateless or stateful proxy server? Thank you. Best Regards, Fangyu Ling > Klaus, > > CANCEL is hop-by-hop only in stateful processing and in this case, yes, > it has only on VIA. But if you have stateless processing, CANCEL is > end-2-end and it will have multiple VIAs... > > Does 3665 obsoletes stateless SIP or it is just not covering it??? > > regards, > bogdan > > Klaus Darilion wrote: >> Looks like it is defined clearly and openser is not 100% standard conform. >> >> regards >> klaus >> >> fancy wrote: >> >>> Hi Klaus: >>> RFC 3665 page 54 line 4: Sorry it's RFC 3261 page 54 line 4: >>> A CANCEL constructed by a >>> client MUST have only a single Via header field value matching the >>> top Via value in the request being cancelled. >>> >>> and RFC 3665 at page 53: Sorry it's RFC 3261 at page 53: >>> CANCEL is referred to as a "hop-by-hop" request, since it is >>> responded to at each stateful proxy hop. >>> >>> and RFC 3665 at page 21: Sorry it's RFC 3261 at page 21: >>> Client: A client is any network element that sends SIP requests >>> and receives SIP responses. Clients may or may not interact >>> directly with a human user. User agent clients and proxies are >>> clients. >>> >>> So, for my opinion, the role of proxy in this case of RFC 3665 section 3.8 is a client when it sends CANCEL message to Bob. >>> >>> If I misunderstand any RFC meanings, please correct me. >>> Thank you very much. >>> >>> Best Regards, >>> Fangyu Ling >>> >>> >>> >>>> fancy wrote: >>>> >>>>> According to RFC 3665 section 3.8 and RFC 3261 section 9, >>>>> there is only one via header in CANCEL message >>>>> (message F11, F13 at page 72 of RFC 3665). >>>>> >>>> Hi! >>>> >>>> I could find it in RFC 3665, but not in 3261. Where exactly in RFC 3261 >>>> is mentioned that the CANCEL has only 1 Via header? >>>> >>>> Further, the example has only one Via header - but I could not find any >>>> definition if this is a MUST or not. >>>> >>>> >>>>> How can I remove the 2nd via header? >>>>> >>>> You would have to modify tm module and change the code which generates >>>> the CANCEL message. >>>> >>>> regards >>>> klaus >>>>

2 1

Re: [Serusers] How SER communicate to other SIP server
by roayu 04 Jul '07

04 Jul '07

Hi, Olaf! >From what I understand about forward() is that it will forward the request to the given destination statelessly. Whereas for t_relay(), it will relay a message to the destination stated in current URI statefully. How do I get the URI to point to the other SIP server by using t_relay() as I couldn't assign any IP address for t_relay(). I managed to assign an IP address by using forward(). I tried to use both. Unfortunately, I still failed to forward the message to the another SIP server to establish the call. Is there any functions I need to use before using either those 2 functions? FYI, I will only call them when it starts to INVITE. Thanks! Best regards, :) Roa Yu -----Original Message----- From: Olaf Bergmann [mailto:Olaf.Bergmann@freenet-ag.de] Sent: Tuesday, July 03, 2007 8:14 PM To: roayu Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] How SER communicate to other SIP server roayu wrote: > In that case, since it's not recommended to change the TO header, is there > any other ways I can make the SER to route to another SIP server without > using rewritehostport()? Yes, several. First of all, rewritehostport() does no forwarding, it just changes the domain part of the request URI (not To). Use forward() or t_relay() depending on your particular needs. Regards, Olaf

2 1

[OpenSER-Users] openser 1.2.1 core dumps on 302 redirect
by Brandon Price 03 Jul '07

03 Jul '07

With debug=99 I get ... 0(31783) DEBUG:t_check_status: checked status is <302> 0(31783) +15183024234 has a forward 0(31783) DEBUG:uac_redirect:get_redirect: resume branch=0 0(31783) DEBUG:uac_redirect:get_redirect: checking branch=0 (added=0) 0(31783) DEBUG:uac_redirect:get_redirect: branch=0 is a redirect (added=0) 0(31783) parse_headers: flags=7 0(31783) Found param type 232, <branch> = <z9hG4bK68c33491>; state=16 0(31783) end of header reached, state=5 0(31783) parse_headers: Via found, flags=7 0(31783) parse_headers: this is the second via 0(31783) DEBUG: get_hdr_body : content_length=0 0(31783) found end of header 0(31783) DEBUG:uac_redirect:sort_contacts: <sip: 13143212222(a)eastern.testdomain.net> q=10 0(31783) DEBUG:uac_redirect:shmcontact2dset: adding contact <sip: 13143212222(a)eastern.testdomain.net> 0(31783) ******* setting for branch 0 flags 0 0(31783) parse_headers: flags=78 Segmentation fault (core dumped) // Where is this core dump being written? related openser.cfg snippet: if(t_check_status("302")){ xlog("$tU has a forward"); get_redirects("*", "redirected"); xlog("forwarding to $tU"); t_relay("5.6.7.8"); exit; }; Any help is as always, greatly appreciated.

2 1

[OpenSER-Users] OpenSER on Xorcom TS-1
by TCB 03 Jul '07

03 Jul '07

Anyone running openser on Xorcom TS-1 with asterisk as b2bua ? -- TC

1 0

[OpenSER-Users] opeser-SVN + Freeradius 1.1.6 problem
by ram 03 Jul '07

03 Jul '07

Hi iam following the below document http://www.openser.org/docs/openser-radius-1.0.x.html iam able to compile both openser and freeradius and radius-ng after configuration files edited. 7. Testing RADIUS server radiusd -X Starting - reading configuration files ... reread_config: reading radiusd.conf Config: including file: /usr/local/etc/raddb/proxy.conf Config: including file: /usr/local/etc/raddb/clients.conf Config: including file: /usr/local/etc/raddb/snmp.conf Config: including file: /usr/local/etc/raddb/sql.conf main: prefix = "/usr/local" main: localstatedir = "/usr/local/var" main: logdir = "/usr/local/var/log/radius" main: libdir = "/usr/local/lib" main: radacctdir = "/usr/local/var/log/radius/radacct" main: hostname_lookups = no main: max_request_time = 30 main: cleanup_delay = 5 main: max_requests = 1024 main: delete_blocked_requests = 0 main: port = 0 main: allow_core_dumps = no main: log_stripped_names = no main: log_file = "/usr/local/var/log/radius/radius.log" main: log_auth = no main: log_auth_badpass = no main: log_auth_goodpass = no main: pidfile = "/usr/local/var/run/radiusd/radiusd.pid" main: user = "(null)" main: group = "(null)" main: usercollide = no main: lower_user = "no" main: lower_pass = "no" main: nospace_user = "no" main: nospace_pass = "no" main: checkrad = "/usr/local/sbin/checkrad" main: proxy_requests = yes proxy: retry_delay = 5 proxy: retry_count = 3 proxy: synchronous = no proxy: default_fallback = yes proxy: dead_time = 120 proxy: post_proxy_authorize = no proxy: wake_all_if_all_dead = no security: max_attributes = 200 security: reject_delay = 1 security: status_server = no main: debug_level = 0 read_config_files: reading dictionary Errors reading dictionary: dict_init: No ATTRIBUTE "Service-Type" defined for VALUE "SIP-Callee-AVPs" Errors reading radiusd.conf any suggestions ram

2 2

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 July 2007