sr-users May 2007

sr-users@lists.kamailio.org

164 participants
295 discussions

by Adrian Georgescu

Change log xcap-lite (0.9.3) unstable; urgency=low * Fixed sync of active_watchers and watchers tables xcap-lite (0.9.2) unstable; urgency=low * Fixed fetch attribute to work with MDB2 driver * Added Content-length header The software can be downloaded from: http://download.dns-hosting.info/XCAP/xcap-lite-0.9.3.tar.gz Regards, Adrian

17 years, 6 months

[Serusers] dns failover

by Mário Ferreira

Hi, I am interested in using SER DNS failover, but I am getting some problems. A failure can be a 503 error response, ICMP errors or a timeout due to a not received response. Does anyone know if SER is able to detect these failures and then select an alternative destination for the message? If the ICMP errors can't be detected, can this be solved with timers? I turned on use_dns_cache and use_dns_failover, but when the message fails to be delivered to the first destination, SER never tries the second destination, which was configured with DNS SRV. regards, Mário Ferreira

17 years, 6 months

[Serusers] Question about SER 2.0 config item

by SIP

While I'm attempting to redo our SER 0.9.6 config in SER 2.0, I have a question concerning migration from an OpenSER 0.9.X module that we user in our SER config, alias_db. Currently, all our aliases lookups are done via alias_db. Since we provision DIDs on the fly via the web, and all our DIDs are E164 format forwarded to our SER server, it didn't make sense to add in the security issue of direct server access from the web server to reload the SER config anytime there was a change to the aliases. Instead, we opted for having everything in the DB where it should be, and we use the alias_db module to keep track of our aliases accordingly. So the question arises... how does one migrate this to the new SER 2.0? I'm still only barely able to grasp the whole concept of Aliases in the new SER 2.0 stuff, but our current table has information like: | 18005551212 | ourproxy.com | 1234567 | ourproxy.com | This gives the alias of 18005551212(a)ourproxy.com a rewrite of 1234567(a)ourproxy.com Simple enough concept. We add or remove aliases from the DB as necessary, and never have to touch the running SER server. So... how does one do this sort of thing now? N.

17 years, 6 months

[Users] SIPit 20 summary

by Klaus Darilion

http://www1.ietf.org/mail-archive/web/sip/current/msg18959.html regards klaus

17 years, 6 months

Re: [Users] avp question

by Jeremy George

Aargh, I swear I checked that. Thanks, Steve. - Jeremy >-----Original Message----- >From: Steve Blair [mailto:blairs@isc.upenn.edu] >Sent: Sunday, May 13, 2007 02:21 PM >To: 'Jeremy George' >Cc: ''Bogdan-Andrei Iancu'', users(a)openser.org >Subject: Re: [Users] avp question > > >Jeremy: > > The number of parenthesis in the avp_db_load call is unbalanced. > >-steve > >Jeremy George wrote: > >>Bogdan, >> >> Thank you very much. I'm a step closer, but I've still got something >>wrong. This code: >> >>modparam("avpops", "avp_url", "mysql://openser:<XXX>@localhost/openser2") >>modparam("avpops", "avp_table", "usr_preferences") >> >>route { >> >> if (avp_db_load("$ru/username", "$avp(s:anonreject)")) { >> >> if (avp_check("$avp(s:anonreject)", "eq/y/i)") && >> search("^(f|F)rom:.*(a|A)nonymous")) { >> >> avp_delete("$avp(s:anonreject)"); >> }; >> }; >>} >> >>yields these error messages: >> >>WARNING: no fork mode >> 0(3491) init_tcp: using epoll_lt as the io watch method (auto detected) >> 0(0) INFO: statistics manager successfully initialized >> 0(0) StateLess module - initializing >> 0(0) TM - initializing... >> 0(0) ACC - initializing >> 0(0) Maxfwd module- initializing >> 0(0) INFO:ul_init_locks: locks array size 512 >> 0(0) AUTH module - initializing >> 0(0) AUTH_DB module - initializing >> 0(0) TextOPS - initializing >> 0(0) EXEC - initializing >> 0(0) AVPops - initializing >> 0(0) ERROR:avpops:parse_check_value: unknown flag <)> >> 0(0) ERROR:avpops:fixup_check_avp: failed to parse checked value >> 0(0) ERROR: fix_actions: fixing failed (code=-1) at cfg line 74 >> 0(0) ERROR: fix_expr : fix_actions error >>ERROR: error -1 while trying to fix configuration >> 0(0) INFO:mi_fifo:mi_destroy: process hasn't been created -> nothing to >>kill >> >> Thanks for the help; I appreciate it. >> >>- Jeremy >> >> >>-----Original Message----- >>From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] >>Sent: Thursday, May 10, 2007 12:05 PM >>To: Jeremy George >>Cc: users(a)openser.org >>Subject: Re: [Users] avp question >> >>Hi Jeremy, >> >>For openser 1.2 it will be: >> >> if (avp_db_load("$ru/username", "$avp(s:anonreject)")) { >> if (avp_check("$avp(s:anonreject)", "eq/y/i)") && >>search("^(f|F)rom:.*(a|A)nonymous")) { >> avp_delete("$avp(s:anonreject)"); >> >> >>regards, >>bogdan >> >>PS: see http://www.openser.org/docs/modules/1.2.x/avpops.html >> >>Jeremy George wrote: >> >> >>> Can someone help me with translating this ser config snippet to openser? >>>Thanks. >>> >>> if (avp_db_load("$ruri/username", "s:anonreject")) { >>> if (avp_check("s:anonreject", "eq/y/i)") && >>>search("^(f|F)rom:.*(a|A)nonymous")) { >>> avp_delete("$avp(s:anonreject)"); >>> >>>- Jeremy >>> >>> >>>_______________________________________________ >>>Users mailing list >>>Users(a)openser.org >>>http://openser.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >>> >> >> >> >> >>_______________________________________________ >>Users mailing list >>Users(a)openser.org >>http://openser.org/cgi-bin/mailman/listinfo/users >> >> >> >

17 years, 6 months

[Serusers] nathelper support for Ottendorf

by Ladislav Andel

Hi all, I have added nathelper support to basic ser.cfg file of Ottendorf release. It is a simple setup without any complexity of using other features such as connectivity_realm etc. You can download it at http://www.iptel.org/ser/howtos/optimizing_the_use_of_rtp_proxy File is called ser_config_2_0.txt The more complex one will come with updated document soon. Lada

17 years, 6 months

Re: [Serusers] SER/PSTN Gateway conf

by flavio

Hi to all, I've updated my ser.cfg file as follow. Essentially I've updated "Call Type Processing" Section, with introduction of BYE SIP message handlling, and route[2] section. So SER now reply to BYE message from PSTN Gateway (in my scenario Phone --> PSTN --> Gateway --> SER --> SIP Phone) just with 200 OK, but does not forward BYE to SIP Phone. I hope this may be helpfully! Thanks, flavio debug=3 fork=no log_stderror=yes listen=10.28.19.202 # INSERT YOUR IP ADDRESS HERE port=5060 children=4 dns=no rev_dns=no fifo="/tmp/ser_fifo" fifo_db_url="mysql://root@10.28.19.202/ser" loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/lib/ser/modules/auth_db.so" loadmodule "/usr/local/lib/ser/modules/uri_db.so" loadmodule "/usr/local/lib/ser/modules/avpops.so" loadmodule "/usr/local/lib/ser/modules/permissions.so" modparam("auth_db|permissions|uri_db|usrloc", "db_url", "mysql://root@10.28.19.202/ser") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("usrloc", "db_mode", 2) modparam("rr", "enable_full_lr", 1) modparam("tm", "fr_inv_timer", 27) modparam("tm", "fr_inv_timer_avp", "inv_timeout") modparam("permissions", "db_mode", 1) modparam("permissions", "trusted_table", "trusted") modparam("permissions", "default_allow_file", "/usr/local/etc/ser/permissions.allow") modparam("permissions", "default_deny_file", "/usr/local/etc/ser/permissions.deny") route { # ----------------------------------------------------------------- # Sanity Check Section # ----------------------------------------------------------------- if (!mf_process_maxfwd_header("16")) { sl_send_reply("483", "Too Many Hops"); break; }; if (msg:len > max_len) { sl_send_reply("513", "Message Overflow"); break; }; # ----------------------------------------------------------------- # Record Route Section # ----------------------------------------------------------------- if (method!="REGISTER") { record_route(); }; # ----------------------------------------------------------------- # Loose Route Section # ----------------------------------------------------------------- if (loose_route()) { if (method=="INVITE") { if (!allow_trusted()) { if (!proxy_authorize("","subscriber")) { proxy_challenge("","0"); break; } else if (!check_from()) { sl_send_reply("403", "Use From=ID"); break; }; consume_credentials(); }; }; route(1); break; }; # ----------------------------------------------------------------- # Call Type Processing Section # ----------------------------------------------------------------- if (uri!=myself) { route(1); break; }; if (method=="ACK") { route(3); route(1); break; } if (method=="INVITE") { route(3); break; } else if (method=="REGISTER" || method=="BYE") { route(2); break; }; lookup("aliases"); if (uri!=myself) { route(1); break; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); break; }; route(1); } route[1] { # ----------------------------------------------------------------- # Default Message Handler # ----------------------------------------------------------------- if (!t_relay()) { sl_reply_error(); }; } route[2] { # ----------------------------------------------------------------- # REGISTER Message Handler # ---------------------------------------------------------------- sl_send_reply("100", "Trying"); if (!allow_trusted()){ if (!www_authorize("","subscriber")) { www_challenge("","0"); break; }; if (!check_to()) { sl_send_reply("401", "Unauthorized"); break; } }; consume_credentials(); if (!save("location")) { sl_reply_error(); }; } route[3] { # ----------------------------------------------------------------- # INVITE Message Handler # ----------------------------------------------------------------- if (!allow_trusted()) { if (!proxy_authorize("","subscriber")) { proxy_challenge("","0"); break; } else if (!check_from()) { sl_send_reply("403", "Use From=ID"); break; }; consume_credentials(); } lookup("aliases"); if (uri!=myself) { route(1); break; }; if (!lookup("location")) { if (uri=~"^sip:0[0-9]*@") { # Domestic PSTN #strip(0); route(4); break; }; if(uri=~"^sip:3[0-9]*@") { route(4); break; }; if (allow_trusted()) { if (!proxy_authorize("","subscriber")) { proxy_challenge("","1"); break; }; }; sl_send_reply("404", "User Not Found"); break; }; route(1); } route[4]{ #----------------------------------------------------------------- # PSTN Handler # ----------------------------------------------------------------- rewritehost("10.28.52.105"); # INSERT YOUR PSTN GATEWAY IP ADDRESS avp_write("i:45", "inv_timeout"); route(1); }

17 years, 6 months

[Serusers] Around the world to get to my....

by SIP

Is the developer documentation on the Iptel.org site even close to still valid? We've just created a semi-complex AGI in Asterisk to sort of act as a gateway for locked SEMS conferences. Our users can create a conference number (if it's available), assign a pin, and then everyone who calls that conference is required to enter the correct pin in order to join. We keep track of the users logged in (contact info, since it's not always local users), and the owner has the ability to limit the number of users, etc. Ideally, I'd like to task one of my C developers to create a similar sort of gateway module for SER instead of, as we currently do, shunting everyone over to the Asterisk server for processing and logic (and voice prompts) and then shunting them over to the SER/SEMS server if they're authenticated. Of course, such a module would need to be able to do things like complete take apart the SEMS pin-collect module (we're not interested in using python for anything, nor in using XMLRPC) and hack it up to collect the right DTMF signals, passing that data on to a proper SER module. I'm just wondering if the developer docs for SER are up to date enough to even point my developers in that direction for information on the SER portion of things. N.

17 years, 6 months

[Users] call park/pickup using openser

by zm23

Hi All. Has anyone implemented call park / pickup feature using OpenSER and asterisk? Or maybe OpenSER and something else ? Any help / suggestion is greatly appreciated. Thanks. -- Zahid

17 years, 6 months

[Serusers] Proper handling of REFER

by Steve Blair

We just started experiencing a problem with call transfers. This use to work but we cannot figure out what broke. We are investigating our gateway software but I wanted to check with the SER community too. If we receive a REFER method we simply t_relay(). Is this the correct handling ? Thanks,Steve

17 years, 6 months

← Newer
1
...
19
20
21
22
23
24
25
...
30
Older →

Jump to page:

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 2007