sr-users

sr-users@lists.kamailio.org

20 participants
37471 discussions

Re: [Kamailio-Users] Trying to deliver a call across multiple peers with t_relay
by Tyler Brauer 28 Nov '08

28 Nov '08

Thank you Klaus for the suggestions. I've implemented the configuration below. When the first t_relay fails, Kamailio generates the 408 Request Timeout and doesn't attempt to try an INVITE to the second address. This what the syslog says: Nov 28 06:11:13 server kamailio[1315]: Attempting Carrier 1 Nov 28 06:11:28 server kamailio[1323]: Attempting Carrier 2 Nov 28 06:11:28 server kamailio[1323]: ERROR:tm:t_forward_nonack: no branch for forwarding Nov 28 06:11:28 server kamailio[1323]: ERROR:tm:w_t_relay: t_forward_nonack failed Nov 28 06:11:28 server kamailio[1317]: Attempting Carrier 1 And here's the watered-down version of my configuration. # - - - - - - - - - - - - - - - - - - - - route[0] { if($si=='10.10.10.10') { # Allowed Host route(1); } else { sl_send_reply("603", "Decline"); exit; } } # - - - - - - - - - - - - - - - - - - - - route[1] { if(msg:len > 2048) { sl_send_reply("513", "Message Too Big"); exit; } if (!mf_process_maxfwd_header("10")) { sl_send_reply("483", "Too Many Hops"); exit; } if (method==OPTIONS) { if ((uri==myself) && (! uri=~"sip:.*[@]+.*")) { options_reply(); exit; } } if (!method=="REGISTER") { record_route(); } if (loose_route()) { append_hf("P-hint: rr-enforced\r\n"); } if (is_method("CANCEL")) { if (t_check_trans()) { t_relay(); } exit; } route(2); } # - - - - - - - - - - - - - - - - - - - - route[2] { xlog("L_INFO", "Attempting Carrier 1"); t_on_failure("3"); t_relay("udp:1.1.1.1:5090","0x2"); exit; } # - - - - - - - - - - - - - - - - - - - - failure_route[3] { xlog("L_INFO", "Attempting Carrier 2"); t_on_failure("4"); t_relay("udp:2.2.2.2:5060"); exit; } # - - - - - - - - - - - - - - - - - - - - failure_route[4] { # I would like to know how to redirect the # original call destined to extension "100" # to 2015551234, but the originating server # will get nervous if the username@ part # of its SIP request is changed. How could } # - - - - - - - - - - - - - - - - - - - - Any further suggestions would be appreciated. Thanks!

2 1

[Kamailio-Users] Does enum_query support wildcard and non-terminal NAPTR record ?
by jerome boileau 28 Nov '08

28 Nov '08

Hi, I'm testing an ENUM DNS server (BIND9) with Openser 1.2.0. It seems that Openser Enum module doesn't support wildcard and non terminal NAPTR record. Enum module is working well when the NAPTR record is defined in the ENUM DNS with complete phone number and ‘u’ flag. Here is an example of the NAPTR record: 1.2.3.4.5.6.7.8.9.3.3.enum1.net IN NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:+33987654321@example.com!". When I declared a wildcard in the ENUM DNS (ie: *.enum1.net IN NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:+33987654321@example.com!".), enum_query function didn't find the NAPTR record. The following message is returned in the log, enum_query(): No NAPTR record found for 1.2.3.4.5.6.7.8.9.3.3.enum1.net. Should resolver (ie resolve.c source file) or enum module be modified to handle wildcard or is it just a parameter to set ? In case of wildcard CNAME record instead of NAPTR, openser behave in the same way, the CNAME record was not found. I also tried to use a non-terminal NAPTR to forward the ENUM DNS query towards another domain. Here is the NAPTR record declared in the ENUM DNS: 1.2.3.4.5.6.7.8.9.3.3.enum1.net IN NAPTR 10 100 "" "" "!^.*([0-9]{11})$!\\1.enum2.net!". By using sip_match function, the enum_query (ie do_query) function discards the NAPTR record without ‘u’ flag. I removed the check on the flag (comment sip_match function) so the NAPTR record is not discarded. But instead of looking for the terminal NATR record, enum_query function overwrites the Request URI with the non-terminal NAPTR record. Is the handling of non terminal NAPTR fixed in a new version of enum module ? If not, is it planned ? Thanks in advance for your help. Best regards, Jérôme -- View this message in context: http://www.nabble.com/Does-enum_query-support-wildcard-and-non-terminal-NAP… Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.

3 3

[Kamailio-Users] simultaneus calls limitations
by BERGANZ François 28 Nov '08

28 Nov '08

Hello all, How can I contrôle « simultaneus calls limitation I could try to add in the database the number off simultaneous calls per user and when I check invite+1 cancel-1 bye-1 busy-1 BUT I have to insert in the database for each calls the call-id to know which user to do +1 or -1 Have you another idea? Thank you Cordialement, BERGANZ François P Pensez à l'Environnement, n'imprimez ce mail que si nécessaire.

2 1

[Kamailio-Users] How to add Retry-After header in 503 response
by Alex Hermann 28 Nov '08

28 Nov '08

Hello, is there a way to add a Retry-After header to a 503 response i'm sending out using t_reply? Use case: t_relay creates an internal 408 on timeout. From failure-route, i want to pass it upstream as 503 with retry-after header. Changing the reply to 503 using t_reply works, but how to add the header? The reply obviously doens't pass through any reply_route. -- Greetings, Alex Hermann

3 4

[Kamailio-Users] Trying to deliver a call across multiple peers with t_relay
by Tyler Brauer 28 Nov '08

28 Nov '08

Good morning/afternoon/evening! I'm trying to accomplish two things. * First, I'd like to try sending a call from our B2BUA through Kamailio to one of our SIP peers, but in the event that the peer is unreachable, try the same call across an alternate peer. I'm currently trying something in our routing block like this. if(!t_relay("udp:1.1.1.1:5060","0x2")) { if(!t_relay("udp:2.2.2.2:5060")) { xlog("L_INFO", "Could not complete"); } } I've also been trying to put together something similar using t_on_failure(#) and a failure_route[#] block to say "if the first t_relay fails, try this instead". In both instances, when fr_timer elapses because the first peer hasn't responded to an INVITE, I can't stop Kamailio from throwing a "SIP/2.0 408 Request Timeout" back to the B2BUA. I have tried setting the flag on t_relay to keep quiet in the event of a forward failure, and instead use something like sl_send_reply("181", "Call Is Being Forwarded") to say to the agent "hold on, we're still trying". I can't seem to find the syntax to make any of that work. The 408 still keeps getting delivered (in spite of the flag on t_relay) to our server, which causes it to stop trying to deliver the call through Kamailio. * The second thing I'd like is that if the first two peers are unavailable, the request is rewritten to go across a third peer as a PSTN call. (eg: a call tries to reach 101(a)1.1.1.1 fails, then 101(a)2.2.2.2 fails, so then 2015551234(a)3.3.3.3 is tried). This requires rewriting the username field of the request URI, but I'm not sure how to do that without confusing the originating server. Could anyone help with the config syntax to resolve either of those two problems? Thank you very much!

3 2

[Kamailio-Users] important: pseudo-variables moved from core to pv module
by Elena-Ramona Modroiu 27 Nov '08

27 Nov '08

Hi, all pseudo-variables exported by core in the past are now in PV module. Therefore if you use any of them in your config you have to load the PV module. This is valid with devel version (trunk). This change was discussed some time ago on devel mailing list, the core is slimmer now. Soon transformations will be moved as well, making possible to export new transformations from modules. The core will include only the API to export PV and transformations, plus the engine to use them in config file. Regards, Ramona

3 2

[Serusers] Registering port instead of contact field port
by Daniel Serrano 27 Nov '08

27 Nov '08

Dear all, I am using SER as IM server and I found that the SER use the contact field to storage the user's location in the memory for future requests. I noted this using the command "serctl alias show" and checking some traces. Since I'm using a NAT scenario I'd like to use the UDP port that my SER server receives during the registration instead of the contact field port to reach the users after their registration. Is there any way to do this? Thanks in advanced. * Daniel Serrano D.** *

2 1

[Kamailio-Users] WARNING dbrow2info: non-local socket
by ALAEDDINE abbech 27 Nov '08

27 Nov '08

Hi, maybe this has been discussed before and maybe I'm not too good in reading mailinglists, but anyhow. If you have two OpenSER proxies storing to the same location table. I see in my logs: WARNING:usrloc:dbrow2info: non-local socket @of other server:5060 ...ignoring, I have a probleme with my DB when i register some UA. This is crucial? If this is not crucial, might this message be supressed in some way? Thanks,

2 3

Re: [Kamailio-Users] method value of the CSeq field
by Alex Balashov 27 Nov '08

27 Nov '08

Iñaki Baz Castillo wrote: > El Miércoles, 26 de Noviembre de 2008, Alex Balashov escribió: >> Iñaki Baz Castillo wrote: >>> El Miércoles, 26 de Noviembre de 2008, Alex Balashov escribió: >>>> You can parse it yourself using textops from $hdr(CSeq). >>> Not needed at all, just read $rm variable (works for requests and >>> responses). >> I didn't say it was needed, just that it could be done. ;) $rm is >> definitely best. > > I agree with you, parsing $hdr(CSeq) is cooler XD > In about the same measure that #include <stdio.h> #include <stdlib.h> int main(void) { FILE *fp = fopen("/dev/stdout", "w"); fprintf(fp, "Hello World!\n"); fclose(fp); return EXIT_SUCCESS; } is cooler than 10 PRINT "HELLO WORLD" 20 END :) -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599

2 1

[Kamailio-Users] http_query function
by jh＠tutpro.com 27 Nov '08

27 Nov '08

--text follows this line-- i wrote a http_query function that allows kamailio to make an http request and get access to parts of the reply. see trunk/modules/utils/README for details. -- juha

7 19

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