sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

RE: [Users] SER as proxy in front of Asterisk
by Thomas Deillon 09 Jan '07

09 Jan '07

Behind a PIX, it works Behind a SonicWall without the SIP_aware option, it doesn't work Behind a Watchguard, it doesn't work too (and there is no SIP_aware option) In fact, I have a centrex IP and many clients in the country with, many different configurations and I have to be sure that all works. It's why I have no enable the SIP_aware option in the sonicwall. Thanks for your help, Thomas -----Message d'origine----- De : users-bounces(a)openser.org [mailto:users-bounces@openser.org] De la part de Thomas Deillon Envoyé : mercredi, 3. janvier 2007 17:06 À : daniel(a)voice-system.ro Cc : users(a)openser.org Objet : RE: [Users] SER as proxy in front of Asterisk Hi, In fact, now, every phone does not response. The options didn't go thought the FW, so, the phone cannot answer. I don't understand why the traffic don't go thought it !! I have test this configuration with two firewall: a sonicwall and a soho. Cheers, Thomas -----Message d'origine----- De : Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Envoyé : mercredi, 3. janvier 2007 14:52 À : Thomas Deillon Cc : users(a)openser.org Objet : Re: [Users] SER as proxy in front of Asterisk Hello, what is the type of NAT/Firewall you have in front of Thomson? As I can see from the diagram, the phone does not reply to OPTIONS request, and I guess, the nat/firewall needs outward traffic to keep the pinhole open. Check why thomson ignores the options requests. Cheers, Daniel On 01/03/07 15:17, Thomas Deillon wrote: > > Hi, > > I have made more tries and now, all my phones don't work ... > > The firewall opens a connection to REGISTER phone but after a while > the OPTION message from the Asterisk will be DROP by the FW ... > > You can find a diagram of the exchange here: > http://deillon.eu/tmp/exchange_sip.png > > A list of all exchange: http://deillon.eu/tmp/ip_sip.txt > > And all sip message: http://deillon.eu/tmp/message.txt > > Thanks a lot for your help, > > Thomas > > ------------------------------------------------------------------------ > > *De :* users-bounces(a)openser.org [mailto:users-bounces@openser.org] > *De la part de* Thomas Deillon > *Envoyé :* mardi, 2. janvier 2007 11:44 > *À :* users(a)openser.org > *Objet :* [Users] SER as proxy in front of Asterisk > > Hi all, > > I wish you first a happy new year !! > One again, I ask you some help. Thanks a lot for your patience and > your answers that really helped me. > > So, I want to put a SER in front of one Asterisk for the moment (more > after). > All Servers have public IP address and so, I don't care about the > RTP/SDP messages. > All phones are behind NAT somewhere in Switerland :) > > > I have the configuration below in openser: > > > modparam("dispatcher", "list_file", "/etc/openser/dispatcher.list") > #modparam("dispatcher", "force_dst", 1) > modparam("dispatcher", "flags", 2) > > modparam("usrloc", "db_mode", 0) > #modparam("rr", "enable_full_lr", 1) > > route{ > > > xlog("L_ALERT", "[$rm] from [$fu] to [$tu]\n"); > > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > exit; > }; > > if (msg:len >= 2048 ) { > sl_send_reply("513", "Message too big"); > exit; > }; > > # if (search("User-Agent:.*Thomson.*")) { > # }; > > > if ((src_ip==212.xxx.xxx.152) || (src_ip==212.xxx.xxx.153)) { > if(method=="OPTIONS") { > }; > avp_pushto("$ru","$tu"); > forward(); > > }else { > fix_nated_contact(); > force_rport(); > if(method=="REGISTER"){ > ds_select_dst("4", "0"); > t_relay(); > } > else { > ds_select_dst("0", "4"); > forward(); > } > } > } > > > And in my dispatcher.list I have: > > 0 sip:212.xxx.xxx.153:5060 > 4 sip:212.xxx.xxx.153:5060 > > > > With this configuration, a snom phone, a X-lite phone and a Cisco > phone seams to work .... > But with the Thomson ST2030, it doesn't work. > In fact, the Thomson REGISTER on asterisk, the Asterisk send a OPTION > message to the FW IP adress and the right port where the thomson is > and then, after a while, the FW close the connection. The thomson > phone is so "UNREACHABLE" on asterisk status and nobody can call it. > I'm not sure that my configuration is ok in ser but I think that is a > problem with the Thomson2030. Do you had the same kind of problem or > do you understand the problem here ? > > > Thanks for your help, > > Thomas Deillon > > ------------------------------------------------------------------------ > > _______________________________________________ > 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

2 1

[Users] Failover with messages BYE
by Jose Gil Navarrete 09 Jan '07

09 Jan '07

Hi list. I try to use the module dispatcher like failover, when the call is established and after the proxy is down then resend the BYE message at the next proxy using ds_select_dst("2", "4") and forward the message, but I obtain the message 503 of the failure_route[2], Any idea?? Thanks in advance In my route seccion I made the next: if (loose_route()) { if (search("Path")) { route(1); }; if (!add_path_received()) { sl_send_reply("503", "Internal Path Error"); exit; }; route(5); }; route[5] { t_on_failure("2"); t_relay(); exit; } failure_route[2] { #500, 503, 504 if ( t_check_status("408") | t_check_status("500") | t_check_status("503") | t_check_status("504") ) { if (ds_next_domain()) { #if (ds_next_dst()) { # On Failure: Choose next Proxy t_on_failure("2"); # Relay to Proxy t_relay(); } else { t_reply("503", "Service not available"); return; } }; } __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/

2 1

[Serusers] Work with a new column in SER.subscriber
by inge 09 Jan '07

09 Jan '07

Hi all, I add a new column named "client" in subscriber table. Next, I want to do a test wich seems like that in SQL : "SELECT client FROM subscriber WHERE username = "actual calling number" => equivalent of avp_db_load I think ? Then, I think I must do a test on the previous values with an if and avp_check I think. But my problem is to do this both requests with SER syntax in ser.cfg. Someone can help me ? Thanks

3 8

[Serusers] ser_ctl: (111, 'Connection refused'): error
by "tzieleniewski" 09 Jan '07

09 Jan '07

Hi ! I've set up the ser 0.10.99, basic functionality works - ser registers users and establishes the media sessions correctly. Now I tried to use the new serctl tool: version 0.3.17. When I try to invoke for instance #ser_ctl ps while ser is running I get the following: ser_ctl: (111, 'Connection refused'): error my ser.cfg file part: port=5060 ... modparam("ctl", "binrpc", "unixs:/tmp/ser_ctl") modparam("ctl", "fifo", "fifo:/tmp/ser_fifo") modparam("ctl", "mode", 0666) and my serctl.conf and serctl/config.py files lines: .. SER_URI = 'http://localhost:5060/' ... Please point me what do I need to do to make it work. Best Tomasz

3 6

Re: Re: Re: [Serusers] ser_ctl: (111, 'Connection refused'): error
by Michal Matyska 08 Jan '07

08 Jan '07

I did copy&paste from one of my testing scripts I have on disk .... as it contained the create_via (which is not neccesary now) it was designed for the older xml-rpc way of handling. You can safely use the code from the CVS ser.cfg example, it's kept up to date. Michal On Mon, 2007-01-08 at 19:55 +0100, =?UTF-8?Q? tzieleniewski ?= wrote: > I have something like this > if ((method=="POST" || method=="GET") & src_ip==127.0.0.1) { > if (msg:len >= 8192) { > sl_send_reply("513", "Request to big"); > drop; > } > dispatch_rpc(); > drop; > } > taken from the latest cvs etc/ser.cfg file. > Is this rewriteuri(...) required? Does it imply that sip:xmlrpc.. is somehow reserved? > > > > The ctl module serves the sercmd (utils/sercmd). > > > > If you want to use ser_ctl then you have to support it in the script > > file like this: > > > > if (method=="POST" || method=="GET") { > > # create_via(); shouldn't be required with the latest CVS source > > rewriteuri("sip:xmlrpc@127.0.0.1:5060"); > > dispatch_rpc(); > > drop; > > } > > > > Michal > > > > On Mon, 2007-01-08 at 17:26 +0100, =?UTF-8?Q? tzieleniewski ?= wrote: > > > Results in the attached files > > > > > > tomasz > > > > > > > Plese, try 'netstat -tupan' and 'ser_ctl -Gg ps' and post results. -- hallik > > > > > > > > On Mon, Jan 08, 2007 at 04:41:59PM +0100, =?UTF-8?Q? tzieleniewski ?= wrote: > > > > > Hi ! > > > > > > > > > > I've set up the ser 0.10.99, basic functionality works - ser registers users > > > > > and establishes the media sessions correctly. Now I tried to use the new serctl > > > > > tool: version 0.3.17. When I try to invoke for instance #ser_ctl ps while ser is > > > > > running I get the following: > > > > > ser_ctl: (111, 'Connection refused'): error > > > > > > > > > > my ser.cfg file part: > > > > > port=5060 > > > > > ... > > > > > modparam("ctl", "binrpc", "unixs:/tmp/ser_ctl") > > > > > modparam("ctl", "fifo", "fifo:/tmp/ser_fifo") > > > > > modparam("ctl", "mode", 0666) > > > > > > > > > > and my serctl.conf and serctl/config.py files lines: > > > > > .. > > > > > SER_URI = 'http://localhost:5060/' > > > > > ... > > > > > > > > > > Please point me what do I need to do to make it work. > > > > > Best > > > > > Tomasz > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Serusers mailing list > > > > > Serusers(a)lists.iptel.org > > > > > http://lists.iptel.org/mailman/listinfo/serusers > > > _______________________________________________ > > > Serusers mailing list > > > Serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > >

1 0

Re: Re: Re: [Serusers] ser_ctl: (111, 'Connection refused'): error
by Michal Matyska 08 Jan '07

08 Jan '07

serctl (note the missing underscore) was the only tool for ser < 0.9.x ser 0.10 introduced xmlrpc interface (basically the dispatch_rpc in the script calls the function) and ser_ctl family of tools was introduced (ser_rpc just for the XML-RPC call, ser_user, ser_domain, ..... specialized (the name suggests what they do), ser_ctl as the shell around all of them. They are written in python. Due to the fact of XML parsing, etc. the binary protocol was re-introduced. You need to load the ctl module, set the protocol, address, port) and use sercmd as cli. All methods which are callable via XML-RPC are visible via sercmd, it is just protocol between ser and controller. So if you have configured both was you can use ser_rpc and sercmd interchangeable. For the methods available use: sercmd system.listMethods Michal P.S. Please keep always the list in To/Cc to follow the thread. Somebody else might be interested as well. On Mon, 2007-01-08 at 20:01 +0100, =?UTF-8?Q? tzieleniewski ?= wrote: > Just to make sure:) > So sercmd is a tool used to send command directly so through ser unix socket and rpc calls are entrily handled by xmlrpc module after dispatch_rpc() method?? > > > > The ctl module serves the sercmd (utils/sercmd). > > > > If you want to use ser_ctl then you have to support it in the script > > file like this: > > > > if (method=="POST" || method=="GET") { > > # create_via(); shouldn't be required with the latest CVS source > > rewriteuri("sip:xmlrpc@127.0.0.1:5060"); > > dispatch_rpc(); > > drop; > > } > > > > Michal > > > > On Mon, 2007-01-08 at 17:26 +0100, =?UTF-8?Q? tzieleniewski ?= wrote: > > > Results in the attached files > > > > > > tomasz > > > > > > > Plese, try 'netstat -tupan' and 'ser_ctl -Gg ps' and post results. -- hallik > > > > > > > > On Mon, Jan 08, 2007 at 04:41:59PM +0100, =?UTF-8?Q? tzieleniewski ?= wrote: > > > > > Hi ! > > > > > > > > > > I've set up the ser 0.10.99, basic functionality works - ser registers users > > > > > and establishes the media sessions correctly. Now I tried to use the new serctl > > > > > tool: version 0.3.17. When I try to invoke for instance #ser_ctl ps while ser is > > > > > running I get the following: > > > > > ser_ctl: (111, 'Connection refused'): error > > > > > > > > > > my ser.cfg file part: > > > > > port=5060 > > > > > ... > > > > > modparam("ctl", "binrpc", "unixs:/tmp/ser_ctl") > > > > > modparam("ctl", "fifo", "fifo:/tmp/ser_fifo") > > > > > modparam("ctl", "mode", 0666) > > > > > > > > > > and my serctl.conf and serctl/config.py files lines: > > > > > .. > > > > > SER_URI = 'http://localhost:5060/' > > > > > ... > > > > > > > > > > Please point me what do I need to do to make it work. > > > > > Best > > > > > Tomasz > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Serusers mailing list > > > > > Serusers(a)lists.iptel.org > > > > > http://lists.iptel.org/mailman/listinfo/serusers > > > _______________________________________________ > > > Serusers mailing list > > > Serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > >

1 0

[Users] Caller-ID setup help
by Chahn Kim 08 Jan '07

08 Jan '07

Hi, a Happy New Year to all. Looking for help to get our caller-id working for outging PSTN calls. We have 3rd party PSTN gateway service and all our callee gets the gateway phone number as CID for all of our sip calls to PSTN. I had implemented so far sip-rpid, remote-party-id, through avp, append_rpid_hf() and confirmed rpid headers on all pstn outgoing frames. However, callee only see the SP's PSTN gateways number as incoming caller-id. Is there other way of implementing caller-id for sip calls before I bring the subject to PSTN service providor? Or is it most likely SP's policy setup? Thanks in advnace. John K

3 4

[Serusers] Instant Messaging Chat/Presence Client Please
by Gould, Aaron 08 Jan '07

08 Jan '07

Does anyone know of a free SIP IM/Presence Chat client that allows for multiple users conferencing? Aaron

2 1

[Users] Chunking Messages
by Danilo Vilela Dantas 08 Jan '07

08 Jan '07

Hi Congratulations! Does Openser supports chunking messages? Is it support at MSRP Relay? Thanks! Danilo

2 1

Re: [Serusers] Problemswith compiling ser 0.10.99
by Dmitry Isakbayev 08 Jan '07

08 Jan '07

Hi, The OSP toolkit project is being moved from sipfoundry to sourceforge. It should be available shortly. Meanwhile, the latest snapshot of the toolkit can be downloaded from http://www.transnexus.com/OSP%20Toolkit/OSP%20Toolkit.htm Regards, Dmitry > Date: Mon, 08 Jan 2007 11:25:24 +0100 > From: "tzieleniewski" <tzieleniewski(a)o2.pl> > Subject: [Serusers] Problemswith compiling ser 0.10.99 > To: serusers(a)lists.iptel.org > Message-ID: <54c54dce.20e2e287.45a21c14.f0624(a)o2.pl> > Content-Type: text/plain; charset="utf-8" > > Hi All!! > I am trying to compile the lattest cvs version of ser but I get errors > which I cann't handle myself so i kindly ask for your help:) > What I want to achive basically is the ser instance with presence > support. > I am compiling ser in the following way: > make group_include="standard standard-dep stable" all > I read that osp requires osptoolkit i tried to get it from sipfoundry > but i couldn't find any source of that. > I also cann't fight problems with tls i didn't includethe experimental > modules(tls) but still I get some errors. > Below is the make output > > >

1 0

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