sr-users May 2006

sr-users@lists.kamailio.org

195 participants
503 discussions

[Users] IMPORTANT: Repository migration
by Bogdan-Andrei Iancu 13 May '06

13 May '06

Hi everybody, as SF seams to have problems with CVS access, problems that cannot be reasonable (as time) solved, the board of the project decided to migrate the project repository from CVS to SVN (still being hosted on SF). Starting from now, all CVS access will be blocked as the migration process will start. The complete process may take couple of days (migration and SVN configuration), so please be patience - I will let you know as soon as public and developer access to SVN is available. thanks for understanding, Bogdan

1 1

[Serusers] Error : modparam("usrloc", "db_ur1"..
by Americania .it 12 May '06

12 May '06

I succeded in running ser with mysql , but when I enable the line with db_ur1 I receive the following error : FROM MY SER.CFG: modparam("usrloc", "db_mode", 2) modparam("usrloc", "db_ur1", "mysql://ser:heslo@localhost/ser") ------- this is rhe error : 0(10432) set_mod_param_regex: usrloc matches module usrloc 0(10432) set_mod_param_regex: parameter <db_ur1> not found in module <usrloc> 0(10432) parse error (59,20-21): Can't set module parameter

2 1

[Serusers] SER cannot connect to MySQL after upgrade
by Stephen Helfen 12 May '06

12 May '06

I just upgraded one of my proxies from SER (0.8.12) and MySQL (4.0.20-0) to SER (0.9.6-6) and MySQL (4.1.19-0). I have a custom module for ser that I have rebulit using the 0.9.6 source and can bring up ser, but cannot make any calls. I can register my UA with ser, but get immediate 404 not found fast busy when attempting to make a call. I am 99% sure that this is because my database access is not happening, but am not seeing any messages in /var/log/messages. Any suggestions??

2 3

[Serusers] serweb ctd problems
by Andrey Kouprianov 12 May '06

12 May '06

Hi, I got an "away" message back from serusers list, so Im re-sending this email again. Im trying to use CTD from serweb 0.9.4 (as well as directly by executing ctd.sh with arguments) and it always returns me 503 Service Unavailable (my SER distro is 0.9.6). /var/log/serweb only shows this May 12 22:02:26 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:02:26 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. May 12 22:02:30 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:02:30 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. May 12 22:04:00 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:04:00 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. ( What does that mean, by the way?? ) /var/log/messages would display an error like the following May 12 22:04:26 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,528,0,0x284bd210,16): Host is down(64) May 12 22:04:26 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:04:26 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:08:18 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,530,0,0x284bd210,16): Host is down(64) May 12 22:08:18 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:08:18 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:10:27 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:11:16 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,485,0,0x284bd210,16): Host is down(64) May 12 22:11:16 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:11:16 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:12:03 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,485,0,0x284bd210,16): Host is down(64) May 12 22:12:03 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:12:03 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) and ngrep does not catch any INVITEs or REFERs. Im using eyeBeam to test this functionality. Does anyone have an idea what could be wrong?? Thanx in advance, Andrey.

1 0

[Serusers] serweb ctd
by Andrey Kouprianov 12 May '06

12 May '06

Hi, Im trying to use CTD from serweb 0.9.4 (as well as directly by executing ctd.sh with arguments) and it always returns me 503 Service Unavailable (my SER distro is 0.9.6). /var/log/serweb only shows this May 12 22:02:26 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:02:26 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. May 12 22:02:30 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:02:30 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. May 12 22:04:00 serweb [debug] Html form was not assigned to APU apu_aliases3. Useing default. May 12 22:04:00 serweb [debug] Html form was not assigned to APU apu_acl4. Useing default. ( What does that mean, by the way?? ) /var/log/messages would display an error like the following May 12 22:04:26 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,528,0,0x284bd210,16): Host is down(64) May 12 22:04:26 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:04:26 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:08:18 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,530,0,0x284bd210,16): Host is down(64) May 12 22:08:18 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:08:18 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:10:27 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:11:16 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,485,0,0x284bd210,16): Host is down(64) May 12 22:11:16 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:11:16 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) May 12 22:12:03 sip /usr/local/sbin/ser[18155]: ERROR: udp_send: sendto(sock,0x284bdc18,485,0,0x284bd210,16): Host is down(64) May 12 22:12:03 sip /usr/local/sbin/ser[18155]: msg_send: ERROR: udp_send failed May 12 22:12:03 sip /usr/local/sbin/ser[18155]: Warning: run_failure_handlers: no UAC support (0, 256) and ngrep does not catch any INVITEs or REFERs. Im using eyeBeam to test this functionality. Does anyone have an idea what could be wrong?? Thanx in advance, Andrey.

1 0

RE: [Serusers] How to use record route to change path of BYE messages
by İlker Aktuna (Koç.net) 12 May '06

12 May '06

Hi, No actually they don't come to SER. I've already checked with ngrep. I also check them with Ethereal on the client side. They are directly sent to the destination where RTP is established. This is how Eyebeam acts. (I use Counterpath's Eyebeam softphone and they said that they are forwarding the BYE message to RTP sender and I should change route path on my SIP proxy) How can I do that ? Thanks, ilker -----Original Message----- From: Michal Matyska [mailto:michal.matyska@iptel.org] Sent: Friday, May 12, 2006 5:13 PM To: İlker Aktuna (Koç.net); serusers(a)lists.iptel.org Subject: Re: [Serusers] How to use record route to change path of BYE messages Hi, Yes I know and still I think your BYE messages went through SER, but you expect them at wrong place of the script. Run "ngrep -d any -p port 5060 -W byline" or "tethereal -i any -p port 5060" and you'll find them out. What I wanted to say is, that they come to SER and due to the predefined route set, they leave SER at the point route(1) is callend within the loose_route check. I expect you have the route[1] look like this: { if !t_relay() { sl_reply_error(); } } Well you can e.g. add if (method==BYE) { # handle the bye message .... # e.g. xlog("L_ERR","My message: %mb\n"); } between append_hf() and route(1) in your script Michal On Fri, May 12, 2006 at 04:25:04PM +0300, İlker Aktuna (Koç.net) wrote: > Hi, > > Thanks for your reply. > But I didn't understand what to do. I already have that configuration in the ser.cfg. > What should I add to it so that BYE messages would allways go through SER ? > > Thanks, > ilker > > -----Original Message----- > From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] > On Behalf Of Michal Matyska > Sent: Friday, May 12, 2006 1:32 PM > To: serusers(a)lists.iptel.org > Subject: Re: [Serusers] How to use record route to change path of BYE > messages > > On Fri, May 12, 2006 at 10:38:51AM +0300, İlker Aktuna (Koç.net) wrote: > > Hi everyone, > > > > I am still trying to find a solution to my problem with BYe messages that are not going through SER. > > Maybe someone with enough knowledge about route recording could help me with the configuration: > > > > My main problem with BYE messages is that they are not going through SER; the client sends it directly to my rtp proxy. as the RTP is established with it. > > I need them to go through SER. How can I achieve this ? > > > > I don't know how to use route recording, could you explain what > > following config block does ? (this is in the default configuration > > but doesn't make BYE messages to go through SER) > > > > It does (you can check by ethereal, ngrep etc.), > > > if (!method=="REGISTER") { > > record_route(); > > } > > but as it has another Route header pointing to the RTP proxy it leaves SER within the next block which is entered when loose_route() function has found any reasonable target in the Route headers to forward the request to .... > > > if (loose_route()) { > > # mark routing logic in request > > append_hf("P-hint: rr-enforced\r\n"); > > so you can add your logic either here or into route[1] block, which > might be called from other places as well (be aware) > > > route(1); > > break; > > }; > > > > And you'll get all the subsequent dialog request and target refresh requests (not only BYE) from both parties, which basically means the To and From could be swapped (e.g. BYE is sent by the proxy, net the client). > > > thanks, > > ilker > > > Hope Google will index this to help more people :-) Michal > <http://387555.sigclick.mailinfo.com/sigclick/070A040C/040C4A07/0C004F0B/242…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

2 1

[Users] OpenSER log rotation
by Mike Williams 12 May '06

12 May '06

I've updated my little tutorial on logging and OpenSER, and would like some other, more knowledgable admins to check my logrotate configuration. You can find it in the wiki. Please mail problems back to the mailing list so I don't receive duplicate reports. Thanks. ---Mike

1 0

RE: [Serusers] How to use record route to change path of BYE messages
by İlker Aktuna (Koç.net) 12 May '06

12 May '06

Hi, Thanks for your reply. But I didn't understand what to do. I already have that configuration in the ser.cfg. What should I add to it so that BYE messages would allways go through SER ? Thanks, ilker -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Michal Matyska Sent: Friday, May 12, 2006 1:32 PM To: serusers(a)lists.iptel.org Subject: Re: [Serusers] How to use record route to change path of BYE messages On Fri, May 12, 2006 at 10:38:51AM +0300, İlker Aktuna (Koç.net) wrote: > Hi everyone, > > I am still trying to find a solution to my problem with BYe messages that are not going through SER. > Maybe someone with enough knowledge about route recording could help me with the configuration: > > My main problem with BYE messages is that they are not going through SER; the client sends it directly to my rtp proxy. as the RTP is established with it. > I need them to go through SER. How can I achieve this ? > > I don't know how to use route recording, could you explain what > following config block does ? (this is in the default configuration > but doesn't make BYE messages to go through SER) > It does (you can check by ethereal, ngrep etc.), > if (!method=="REGISTER") { > record_route(); > } but as it has another Route header pointing to the RTP proxy it leaves SER within the next block which is entered when loose_route() function has found any reasonable target in the Route headers to forward the request to .... > if (loose_route()) { > # mark routing logic in request > append_hf("P-hint: rr-enforced\r\n"); so you can add your logic either here or into route[1] block, which might be called from other places as well (be aware) > route(1); > break; > }; > And you'll get all the subsequent dialog request and target refresh requests (not only BYE) from both parties, which basically means the To and From could be swapped (e.g. BYE is sent by the proxy, net the client). > thanks, > ilker > Hope Google will index this to help more people :-) Michal _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers <http://387555.sigclick.mailinfo.com/sigclick/03010604/01044804/070E4D03/109…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

1 0

RE: [Serusers] How to use record route to change path of BYE messages
by İlker Aktuna (Koç.net) 12 May '06

12 May '06

Hi everyone, I am still trying to find a solution to my problem with BYe messages that are not going through SER. Maybe someone with enough knowledge about route recording could help me with the configuration: My main problem with BYE messages is that they are not going through SER; the client sends it directly to my rtp proxy. as the RTP is established with it. I need them to go through SER. How can I achieve this ? I don't know how to use route recording, could you explain what following config block does ? (this is in the default configuration but doesn't make BYE messages to go through SER) if (!method=="REGISTER") { record_route(); } if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; thanks, ilker ________________________________ From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net) Sent: Friday, May 05, 2006 12:09 AM To: fay butt; serusers(a)lists.iptel.org Subject: RE: [Serusers] How to use record route to change path of BYE messages Hi, Thanks for your reply but this is totally a different case. In my case the problem is not CANCEL messages but BYE and ACK messages. BYE message (and also ACK) is sent to the contact of the RTP stream instead of the SER proxy. But I want these messages to be sent to SER. That's why I should somehow make them to be sent to SER. So It should be done by either recording route or changing contact header. How can I do that ? Thanks, ilker ________________________________ From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of fay butt Sent: Thursday, May 04, 2006 7:08 PM To: serusers(a)lists.iptel.org Subject: Re: [Serusers] How to use record route to change path of BYE messages hi, i had that problem a time ago. I just put this messege and now it's working fine. if (method == "CANCEL" ) { if (uri =~"^sip:4[0-9]*@localhost") { forward ( asterisk , 5060 ); t_relay(); break; }; }; "Ýlker Aktuna (Koç.net)" <ilkera(a)koc.net> wrote: Hi, For voice communication I use a SIP+RTP proxy together with SER. For PSTN calls SER routes the INVITE messages to the RTP proxy. Everything works fine there, but when the call is ended by one client (which is connected to SER) or the PSTN user, the BYE message does not arrive to SER. If our RTP proxy does not see the message coming from SER, call doesn't end. That's why I need all of the BYE messages to go through SER. How can I do that ? In the default configuration there is a record route process for every message other than REGISTER. But still BYE and ACK messages are not sent to SER. Should I change the contact header of the messages arriving from RTP proxy ? If so, how can I do it ? What does following configuration block do ? if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; Thanks, ilker <http://387555.sigclick.mailinfo.com/sigclick/050A0207/00044F03/01004900/662…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

2 1

[Serusers] Two BYE's for same call
by mkumar＠mantragroup.com 12 May '06

12 May '06

Hi All, I was able to install SER and SERWEB successfully and use them. Recently I came across a problem with SER call recodring's (CDR's),few of the calls are recoded as two calls dialed at the same time to same number and when I see the call log in SERWEB I find two calls at the sametime with 3 or 4 seconds difference in their call duration. When I checked the SER DataBase I found two BYE's for the same call and SERWEB is showing them as two different calls. Please tell me how can I fix this? I am unable to get minutes dialed out by a customer for a period properly because of this. Thanks, Manoj.

1 0

← Newer
1
...
29
30
31
32
33
34
35
...
51
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 May 2006