sr-users

sr-users@lists.kamailio.org

39 participants
37513 discussions

Re: [Serusers] set some flag that isn't reset after some call leg has finished
by rcarvalho＠iric.up.pt 10 Oct '06

10 Oct '06

I'm trying to set some flag when Ser receives a 302 replay meaning that a forwarding is going to happen, so that the next dialog that gets written in acc DB table can be related with that forwarded call for proper billing! To accomplish that, I think I should set a flag when I receive that 302 replay, and I test that flag in the next dialog to be able to write something else to acc table, so that that call can be billed correctly. The problem, as I mentioned is that every flag that I rise with setflag() gets always reset after that call leg finishes! I hope I made myself clear:| Thanks, Ricardo. Greger V. Teigre wrote: > You mean transaction? > What are you trying to do? > g-) > > > > Ricardo Carvalho wrote: >> How may I set some flag that isn't reset after some call leg has finished? >> Every flag that I rise with setflag() gets always reset after that call leg finishes!! >> >> Thanks in advance, >> Ricardo. >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >> >> >

1 0

[Serusers] Need suggestion about RTP Timeout
by Lokesh Kumar 10 Oct '06

10 Oct '06

Hello, I want to connect cisco AS5300 to ser, but there can be a potential big problem when a BYE or CANCEL has been dropped by Gateway from ser. This thing has already been mentioned in the getting started manual, but no way to get rid of this problem has been mentioned. Can any one suggest how to drop a call on gateway if there is no rtp stream or when a BYE or CANCEL from ser to gateway has been missed. Thanks Lokesh -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.407 / Virus Database: 268.13.1/469 - Release Date: 10/9/2006

4 3

[Serusers] cancel message and to tag
by Hye-Jeong Mok 10 Oct '06

10 Oct '06

Hi, Have a question about the CANCEL message and the to tag. Let say I have a UAC sending INVITE to SER. SER responds with 183 message with a to tag = 111. Then the UAC sends CANCEL with no tag, and SER responds with 200 message with the new to tag = 222, followed by 487 message with to tag 222. SER 0.9.0 that I'm using behaves this way. I believe in 3261, the to tag of the 200 message in response to the CANCEL that has no tag, it has to be the same as the to tag that is in the previous 1xx message. So in this case, SER that I'm using is doing something wrong? Any idea how to fix this? Thanks, HJ _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

3 2

[Serusers] set some flag that isn't reset after some call leg has finished
by Ricardo Carvalho 10 Oct '06

10 Oct '06

How may I set some flag that isn't reset after some call leg has finished? Every flag that I rise with setflag() gets always reset after that call leg finishes!! Thanks in advance, Ricardo.

2 1

[Serusers] store in DB some searched content present in messages
by Ricardo Carvalho 10 Oct '06

10 Oct '06

Is there a way to search and store in a regular expression basis, some content of some kind of messages in an avp and then store that content in some table of MySQL database? Thanks, Ricardo.

2 2

[Users] openser-ser-sems
by geovani ferronetti 10 Oct '06

10 Oct '06

Hi, I have a problem. I have a working openser server, but I want and a media server, so I decide to use sems. I put everything in this way: Openser <-------> Ser<--------->sems All things are working on the same server.Openser works on 5060 port, and ser on 6060 port. In openser.cfg I redirect to ser in this way: if (uri=~"sip:100@.*") { t_relay("localhost:6060"); exit; }; and in ser.cfg: if (uri=~"sip:100.*@") { if(!t_write_unix("/tmp/am_sock","conference")) { t_reply("500","error contacting sems"); }; break; }; When I dial 100 the logs of the ser contain: Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: SIP Request: Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: method: <INVITE> Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: uri: <sip:100@domain.com> Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: version: <SIP/2.0> Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: flags=1 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: Found param type 232, <branch> = <z9hG4bK2cec.f018b0b5.0>; state=16 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: end of header reached, state=5 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: Via found, flags=1 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: this is the first via Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: After parse_msg... Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: preparing to run routing scripts... Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: flags=128 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: Found param type 232, <branch> = <z9hG4bKOUUByO4Kp1q4sDNU>; state=16 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: end of header reached, state=5 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: Via found, flags=128 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: this is the second via Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG:maxfwd:is_maxfwd_present: value = 69 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DBG:maxfwd:process_maxfwd_header: value 69 decreased to 16 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: flags=8 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: add_param: tag=6mVbY0KQFDRYupVP Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: end of header reached, state=29 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: flags=256 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: end of header reached, state=9 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: get_hdr_field: <To> [29]; uri=[sip:100@domain.com] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: to body ["100" <sip:100@voip.cts.md> ] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: get_hdr_field: cseq <CSeq>: <1> <INVITE> Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: get_hdr_body : content_length=232 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: found end of header Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: find_first_route: No Route headers found Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: loose_route: There is no Route HF Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if host==us: 11==9 && [domain.com] == [127.0.0.1] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if port 6060 matches port 5060 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if host==us: 11==11 && [domain.com] == [X.X.X.X] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if port 6060 matches port 5060 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if host==us: 11==10 && [domain.com] == [172.17.6.2] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if port 6060 matches port 5060 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if host==us: 11==9 && [domain.com] == [127.0.0.1] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if port 6060 matches port 5060 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if host==us: 11==11 && [domain.com] == [X.X.X.X] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if port 6060 matches port 5060 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if host==us: 11==10 && [domain.com] == [172.17.6.2] Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: grep_sock_info - checking if port 6060 matches port 5060 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: check_self: host != me Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: t_newtran: msg id=3 , global msg id=2 , T onfiltered=0xffffffffffffffff Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: flags=-1 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: flags=60 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: t_lookup_request: start searching: hash=52930, isACK=0 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: RFC3261 transaction matching failed Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: t_lookup_request: no transaction found Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: SER: new INVITE Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: parse_headers: flags=-1 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: check_via_address(172.17.6.2, 172.17.6.2, 0) Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: WARNING:vqm_resize: resize(0) called Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: reply sent out. buf=0x5d8838: SIP/2.0 1..., shmem=0x2b9b012ee768: SIP/2.0 1 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: _reply_light: finished Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: mk_proxy: doing DNS lookup... Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: get_record: lookup(_sip._udp.domain.com, 33) failed Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: sip_resolvehost: no SRV record found for voip.cts.md, trying 'normal' lookup... Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: check_via_address(172.17.6.2, 172.17.6.2, 0) Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: add_to_tail_of_timer[4]: 0x2b9b012ec368 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG: add_to_tail_of_timer[0]: 0x2b9b012ec388 Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: SER: new transaction fwd'ed Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: DEBUG:destroy_avp_list: destroying list (nil) Oct 4 12:26:59 voip /usr/local/sbin/ser[31088]: receive_msg: cleaning up Please show me where is the problem, in openser or ser or sems? Thanks. Ion M. __________________________________________________ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it

2 1

[Serusers] anyone know about SIPP
by vijay tiwari 10 Oct '06

10 Oct '06

hi all anyone have idea to use SIPP and how to you this tool in brief thanks vijay --------------------------------- Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business.

1 0

[Users] Question about handling retransmission
by Michael Ulitskiy 10 Oct '06

10 Oct '06

Hello, I have a question about a good way to handle retransmissions. I see that t_check_trans() function is able to tell me if the request is a retransmission or not. So my question is: should I apply the whole request-processing logic to retransmissions or I can simply do something like the following: if (is_method("ACK|CANCEL")) { if (t_check_trans()) { t_relay(); } else { xlog(L_NOTICE,"$rm: No matching transaction. dropping"); exit; } } if (t_check_trans()) { xlog(L_NOTICE,"$rm: is a retransmission"); t_relay(); } I.e. in the above code I assume that t_relay() would be able to match the request to the transaction and absorb it like it does for ACKs and CANCELs without applying whatever modification was done to original request. Is it true? Thanks, Michael

2 2

[Users] [Devel] SST module changes
by Ron Winacott 10 Oct '06

10 Oct '06

Hello all, I just updated the SST module to be fully compliant with the RFC. Here is a list of the biggest changes: 1) The script function sstCheckMin() will now add the Min-SE: header and send the 422 reply if the Session-Expire: header in the INVITE is too small. (with the argument flag set to true) The old sstCheckMin() function would return true stating that the Min-SE: value was too small, but the RFC states the 422 reply can *not* be sent without stating your Min-SE: value. 2) The Min-SE: and the Session-Expires: headers will be updated to your min_se value if in the initial request if too small. 3) If the UAC does not request SST support, the SST module will request it on behave of the PROXY. 4) The PRACK issue with the dialog module has been worked around. PRACK will clobber the dialog expires lifetime value but the SST module will fix it. 5) If the UAS does not support SST, the SST module will request the UAC refresh on behave of the PROXY. 6) reINTITE and UPDATE are now supported as refreshers to an active timed session. 7) The introduction of the sst flag parameter. This is keeping with the idea that the module will not do anything to a message unless asked for by the script (openser.cfg) file. You now have to setflag(sst_flag) just like you have to setflag(dialog_flag) for the module to act on a message. 8) Code clean up and commenting of all functions and beefed up the user documentation. Hope you find this module usefull, ronw (karwin) -- Ron Winacott - SOMA Networks, Inc. --- Chaos, panic and disorder...my work here is done. _______________________________________________ Devel mailing list Devel(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/devel

1 0

[Users] set some flag that isn't reset after some call leg has finished
by Ricardo Carvalho 10 Oct '06

10 Oct '06

How may I set some flag that isn't reset after some call leg has finished? Every flag that I rise with setflag() gets always reset after that call leg finishes!! Thanks in advance, Ricardo.

2 1

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