sr-users August 2008

sr-users@lists.kamailio.org

144 participants
202 discussions

Re: [Serusers] call forward no answer (solved)
by caio 25 Aug '08

25 Aug '08

append_branch() is missed at ser examples... On Fri, Aug 15, 2008 at 4:22 PM, caio <elcaio(a)gmail.com> wrote: > Hi all, > I can't make call forwarding on no answer works on my ser-0.9.7 installation. > Here you can see a snippet of log, where the call falls on > failure_route and then to route_1 where t_relay is called. > > Log at: http://rafb.net/p/xwTmn195.html > > The call is from sip:579951 to sip:579915(who has enabled the feature > fwdnoanswer to sip:579916. > But I do not know why the INVITE after the append_branch() is still to > R-URI: sip:579915@.... > > After the relay then the call terminates with: > > Aug 15 16:13:25 [/usr/sbin/ser] SIP Reply (status):_ > Aug 15 16:13:25 [/usr/sbin/ser] version: <SIP/2.0>_ > Aug 15 16:13:25 [/usr/sbin/ser] status: <487>_ > Aug 15 16:13:25 [/usr/sbin/ser] reason: <Request Terminated>_ > > I follow the example of ser guide.., but do not work.. > I would appreciate any comment.. > > Regards, > > -- > caiogf > -- caio

1 0

[Serusers] ser + media server
by caio 25 Aug '08

25 Aug '08

Hi all, What do you recommend for media server application to integrate wih ser-0.9.x? SEM or Asterisk? Specifically i'm talking about running services such as IVR, conference and voicemail.. Thanks your suggestions.. -- caio

1 0

[Kamailio-Users] crashing problem
by Jonathan K. Creasy 25 Aug '08

25 Aug '08

We're using Carrier route with about 53,000 routes stored in a mysql databse. We're getting this crash in production that we never had in the lab. The bt is below. Does anyone have any suggestions? nline static void free_to_params(struct to_body* tb) { struct to_param *tp=tb->param_lst; struct to_param *foo; while (tp){ foo = tp->next; <-- **** Line 75 ***** pkg_free(tp); tp=foo; } } -Jonathan #0 free_to (tb=0x817cf10) at parser/parse_to.c:75 #1 0x080daf70 in clean_hdr_field (hf=0x8a8ee18) at parser/hf.c:182 #2 0x080db05b in free_hdr_field_lst (hf=0x8a905b8) at parser/hf.c:209 #3 0x080db12d in free_sip_msg (msg=0x8193030) at parser/msg_parser.c:660 #4 0x08094695 in receive_msg ( buf=0x8168220 "SIP/2.0 183 Session Progress\r\nf: \"16512552900\"<sip:16512552900@206.80.65.90>;tag=as781b438d\r\nt: <sip:+16513401989@lefty.netlogic.net>;tag=c7ad5f5020080822192510\r\ni: 396fb801653abd6f605a12153e0e3e72@20"..., len=1271, rcv_info=0xbf82f844) at receive.c:206 #5 0x080d3e0d in udp_rcv_loop () at udp_server.c:438 #6 0x0806c8f5 in main (argc=3, argv=0xbf82fa34) at main.c:834 (gdb) backtrace full #0 free_to (tb=0x817cf10) at parser/parse_to.c:75 No locals. #1 0x080daf70 in clean_hdr_field (hf=0x8a8ee18) at parser/hf.c:182 __FUNCTION__ = "clean_hdr_field" #2 0x080db05b in free_hdr_field_lst (hf=0x8a905b8) at parser/hf.c:209 No locals. #3 0x080db12d in free_sip_msg (msg=0x8193030) at parser/msg_parser.c:660 No locals. #4 0x08094695 in receive_msg ( buf=0x8168220 "SIP/2.0 183 Session Progress\r\nf: \"16512552900\"<sip:16512552900@206.80.65.90>;tag=as781b438d\r\nt: <sip:+16513401989@lefty.netlogic.net>;tag=c7ad5f5020080822192510\r\ni: 396fb801653abd6f605a12153e0e3e72@20"..., len=1271, rcv_info=0xbf82f844) at receive.c:206 msg = (struct sip_msg *) 0x8193030 __FUNCTION__ = "receive_msg" #5 0x080d3e0d in udp_rcv_loop () at udp_server.c:438 len = 1271 buf = "SIP/2.0 183 Session Progress\r\nf: \"16512552900\"<sip:16512552900@206.80.65.90>;tag=as781b438d\r\nt: <sip:+16513401989@lefty.netlogic.net>;tag=c7ad5f5020080822192510\r\ni: 396fb801653abd6f605a12153e0e3e72@20"... tmp = <value optimized out> from = (union sockaddr_union *) 0x8a91318 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {2850040017, 135426432, 3213031528, 3085483479}, addr32 = {2850040017, 135426432, 3213031528, 3085483479}, addr16 = {10449, 43488, 29056, 2066, 63592, 49026, 48599, 47080}, addr = "Ñ(à©\200q\022\bhø\202¿×½è·"}}, dst_ip = {af = 2, len = 4, u = {addrl = {509300942, 0, 0, 0}, addr32 = {509300942, 0, 0, 0}, addr16 = {20686, 7771, 0, 0, 0, 0, 0, 0}, addr = "ÎP[\036", '\0' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto = 1, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023ÄÑ(à©\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 2850040017}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 2850040017, sin6_addr = {in6_u = {u6_addr8 = '\0' <repeats 15 times>, u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x818dd90} __FUNCTION__ = "udp_rcv_loop" #6 0x0806c8f5 in main (argc=3, argv=0xbf82fa34) at main.c:834 cfg_log_stderr = 0 cfg_stream = (FILE *) 0xa179008 c = <value optimized out> r = <value optimized out> tmp = 0x8148b9c "ÿÿÿÿ" tmp_len = <value optimized out> port = <value optimized out> proto = <value optimized out> ret = <value optimized out> seed = 639236262 rfd = 4 __FUNCTION__ = "main"

4 9

Re: [Kamailio-Users] Google reference to openser users and devel Archives
by H Quintana 25 Aug '08

25 Aug '08

Hi, My temporary solution was to edit the etc/hosts file in my windows xp machine. The path is: C:\WINDOWS\system32\drivers\etc\hosts And I added the lines: 193.22.119.66 www.openser.org 193.22.119.66 openser.org to point to the Kamailio servers. Hope this helps, Humberto > Subject: Re: [Kamailio-Users] Google reference to openser > users and > devel Archives > To: users(a)lists.kamailio.org > Message-ID: > <200808251326.44077.henning.westerholt(a)1und1.de> > Content-Type: text/plain; charset="utf-8" > > On Friday 15 August 2008, Rafael Risco Gonzales-Vigil > wrote: > > This is for openser/kamailio and opensips list > administrators: > > google still has references to > http://www.openser.org/pipermail/users/ and > > http://www.openser.org/pipermail/devel/ for openser > related searchings and > > those urls does not contains old files anymore so its > dificult search > > information for learning and troubleshooting about > openser/kamailio or > > opensips... I hope someone can solve this issue for > the benefit of all > > current and future community users. > > Hi Rafael, > > we don't have access to the openser.org domain, so > there is nothing what we > can do here, sorry. All access of web and mail services to > openser.org will > go to opensips infrastructure. > > If you encounter such old links with openser.org, you can > simply > change "openser.org" to "kamailio.org", > then you'll be able to access the > content, apart from using the google archives, as Alex > pointed out. > > Cheers, > > Henning >

2 1

[Kamailio-Users] failure route configuration
by Jonathan K. Creasy 25 Aug '08

25 Aug '08

I have this block in my configuration: <excerpt from failure_route[1]> if(!cr_rewrite_uri("1", "call_id")){ t_reply("403", "$fU@$fd Not allowed"); } else { # In case of failure, re-route the request prefix("+"); t_on_failure("2"); if (is_method("INVITE")) t_on_reply("1"); # Relay the request to the gateway t_relay(); } The output in my log file: Aug 18 18:41:29 lab02b /usr/local/sbin/openser[5622]: INFO: carrierroute:carrier_rewrite_msg: uri 8909 was rewritten to sip: 8909@gateway_one Aug 18 18:41:29 lab02b /usr/local/sbin/openser[5626]: INFO: Failure Route Started Aug 18 18:41:29 lab02b /usr/local/sbin/openser[5626]: INFO: carrierroute:carrier_rewrite_msg: uri 8909 was rewritten to sip: 8909@gateway_two Aug 18 18:41:29 lab02b /usr/local/sbin/openser[5626]: ERROR: tm:t_forward_nonack: no branch for forwarding Aug 18 18:41:29 lab02b /usr/local/sbin/openser[5626]: ERROR: tm:w_t_relay: t_forward_nonack failed What am I missing that I need to do prior to calling t_relay()? -Jonathan

6 11

[Kamailio-Users] Google reference to openser users and devel Archives
by Rafael Risco Gonzales-Vigil 25 Aug '08

25 Aug '08

This is for openser/kamailio and opensips list administrators: google still has references to http://www.openser.org/pipermail/users/ and http://www.openser.org/pipermail/devel/ for openser related searchings and those urls does not contains old files anymore so its dificult search information for learning and troubleshooting about openser/kamailio or opensips... I hope someone can solve this issue for the benefit of all current and future community users. rafael Lima - Peru

3 2

[Kamailio-Users] need help on starting opensips v1.4.1
by Do Nguyen Ha 25 Aug '08

25 Aug '08

hi opensips debian:/etc/opensips# /etc/init.d/opensips start Starting opensips: opensipsListening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 192.168.1.254 [192.168.1.254]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 192.168.1.254 [192.168.1.254]:5060 Aliases: tcp: debian:5060 tcp: localhost:5060 udp: debian:5060 udp: localhost:5060 . debian:/etc/opensips# /etc/init.d/opensips status Status of opensips: opensips is not running. could anyone tell me the tips for this Thanks Ha`

2 1

[Kamailio-Users] Why does Kamailio reply 408 when 'fr_inv_timer' expires?
by Iñaki Baz Castillo 25 Aug '08

25 Aug '08

Hi, when 'fr_inv_timer' expires Kamailio CANCELs the pending branches and reply "408 Request Timeout" to the UAC. Well, I wonder if 408 is appropiate. I think "480 User Unavailable" or "487 Cancelled" would be better: I received those replies in other maillist: "408 indicates transaction timeout. You have sent request to next hop and it has not responded back. If the gateway has not responded at all (Including 100 trying), 408 is appropriate. 480 is more of application usage meaning that the user is not available and would be appropriate if the gateway has at least send one provisional response i.e. 100, 180, 183..." "408 is used consistently to mean IP-level timeout in sending a request from one element to another. It is also defined to be returned by a UA when the time specified in "Expires" has been reached. (In theory, two different error codes should be defined for these two situations, but that has not been done.) However, in a ring-no-answer situation, it is more common for an upstream proxy to send a CANCEL to the UA/gateway, in which case the UA/gateway provides a 487 response to the INVITE." This last point suggest that Kamailio could do the following: - If the proxy has received provisional responses from callee's then not send a 408 upstream since when the proxy sends CANCEL to UAS's it will receive some 487 and would return a 487 upstream. - If the proxy hasn't received provisional responses then this is a clear "408 Request timeout". So a possibility is that Kamailio just reply a 408 in real timeouts and reply 487 when 'fr_inv_timer' expires (or just reply nothing since UAS's will generate the 487). Opinions? -- Iñaki Baz Castillo <ibc(a)aliax.net>

3 2

[Kamailio-Users] Where have the OLD Module Docs gone?
by Douglas Garstang 25 Aug '08

25 Aug '08

The module documentation for versions 1.2, 1.3 etc used to be available on the web site. Where has it gone? When you clicked on the documentation link, you used to be able to choose the version of OpenSER(Kam...OpenSIPS whatever) that you wanted. Now, your taken immediately to what appears to be the documentation for the LATEST version. Doug.

7 7

[Kamailio-Users] presence fail
by Ricky Gutierrez 25 Aug '08

25 Aug '08

Hi, lists I have some problems with the simple presence in kamailio 1.4, I add to my kamailio.cfg the following line and when restarting the it shows me errors in this it lines Aug 24 19:31:41 [21946] ERROR:core:set_mod_param_regex: parameter <force_active> not found in module <presence> Aug 24 19:31:41 [21946] CRITICAL:core:yyerror: parse error in config file, line 50, column 19-20: Can't set module parameter Aug 24 19:31:41 [21946] ERROR:core:main: bad config file (1 errors) Aug 24 19:31:41 [21946] NOTICE:presence:destroy: destroy module ... I remove of the Makefile the modul presence kamailio.cfg loadmodule "presence.so" modparam("presence|auth_db|uri_db|usrloc", "db_url", "mysql://openser:openserrw@localhost/openser") modparam("presence", "force_active", 1) modparam("presence", "max_expires", 3600) modparam("presence", "server_address", "sip:192.168.10.1:5060") where the error can be? regards rickygm

2 1

← Newer
1
2
3
4
5
6
7
8
...
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 August 2008