sr-users May 2007

sr-users@lists.kamailio.org

164 participants
296 discussions

[Users] question about the openserctl ping command
by Papadopoulos Georgios 24 May '07

24 May '07

Hello all, I am using the openserct ping command to periodically check whether openser is working properly (If there is a better way to do this, please let me know). My script looks like this: SIP_URI="sip:213.5.xxx.xxx:5060" OPENSER_DIR=/root/openser TMP_FILE=/tmp/openser_ping.result $OPENSER_DIR/bin/openserctl ping $SIP_URI > $TMP_FILE 2>&1 Sometimes in TMP_FILE I see the following type of message: mkfifo: cannot create fifo `/tmp/openser_receiver_26907': File exists anaconda-ks.cfg install.log install.log.syslog mbox openser ERROR: error opening read fifo /tmp/openser_receiver_26907 At the same time openser seems to be working fine, however because the script gets this error, it restarts the server (the idea is that if ping fails then restart). Any idea why this is happening? What is the best way to make sure openser is working properly? I am assuming that a succesful ping only proves that one child is working properly. Thank you for any help George Disclaimer The information in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.

3 2

[Users] One way communication on calls from PSTN, two way on outbound
by Aaron Seelye 24 May '07

24 May '07

Hello all, I've based my config on the one found at http://siprouter.onsip.org/doc/gettingstarted/ch10.html, coming up with the one found here http://209.213.8.4/openser.cfg (all the xlog's are so I can follow what's going on when I run openser in a non-forking mode). I'm trying to get a simple system working where clients behind nat'ing firewalls can both send and receive calls. Currently outbound calls work fine, with two way communication, but inbound calls only have one way communication, from the nat'd client to the pstn. If anyone could give me some pointers as to what's going wrong, I'd appreciate it. TIA, Aaron Seelye

1 0

Re: [Serusers] Frustrating error - please help
by Mahatma Sarasvati 24 May '07

24 May '07

Also a good idea. Still no effect. This installation was working great for a while. Is it possible that some other software I've installed is causing the problem? This is 2.0.0 rc2 from CVS. M ----- Original Message ---- From: Andrey Kuprianov <andrey.kouprianov(a)gmail.com> To: "serusers(a)iptel.org" <serusers(a)iptel.org> Sent: Thursday, May 24, 2007 8:23:14 AM Subject: Re: [Serusers] Frustrating error - please help Maybe just try setting fork=yes ?... On 5/24/07, Mahatma Sarasvati <gnoahhb(a)yahoo.com> wrote: > > A good hint, but no. I'm using the standard version 1.4 ser.cfg. I've only > added my 10.10.10.41 ip address. The "fork=no" command is commented out. > > Is there something else that would cause ser to start in non-forking mode? > > Thanks, > M > > > ----- Original Message ---- > From: samuel <samu60(a)gmail.com> > To: Mahatma Sarasvati <gnoahhb(a)yahoo.com> > Cc: serusers(a)iptel.org > Sent: Thursday, May 24, 2007 12:40:41 AM > Subject: Re: [Serusers] Frustrating error - please help > > Are you starting SER in non-forking mode? It looks like SER is not binding > to the 10.10.10.41 IP, only to the local IP (127.0.0.1) and that's why you > see in the logs that it's not able to send to a "standard" IP address: > WARNING: xl_mod_init: more IP 10.10.10.41 not used > CRITICAL: invalid sendtoparameters one possible reason is the server is > bound to localhost and attempts to send to the net > > Case you need to use 2 interfaces, I would recommend using mhomed=yes (don't > recall the exact syntax right now..). > > Hope it helps, > Samuel. > > 2007/5/24, Mahatma Sarasvati <gnoahhb(a)yahoo.com>: > > Hi All, > > > > This ser installation was working fine and I can't figure out why its not > working now. > > I'm getting an error (see last log line) every time I attempt a call to > local users. Calling out to PSTN works great. ngrep reveals that SER is not > sending any messages to the callee location. > > > > There are 2 registered local users, one registered twice. > > > > I have no idea what is going on. I'm using an unmodified version 1.4 > ser.cfg file on CentOS 5. > > > > I suspect some server configuration error? ? ? ? > > > > > > Thanks, > > M > > > > > > > > Here are the logs. > > > > > > May 23 16:03:38 vx1 ser: init_tcp: using epoll_lt as the io watch method > (auto detected) > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: Maxfwd module- initializing > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: WARNING: xl_mod_init: more > IP 10.10.10.41 not used > > May 23 16:03:38 vx1 last message repeated 8 times > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: AVPops - initializing > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: DEB: IP address of RTPPROXY > is /var/run/rtpproxy.sock > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: xlog null is "<null>" > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is initially 109568 > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is finally 262142 > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is initially 109568 > > May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF > is finally 262142 > > . > > . > > . > > . > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: rtpp_test: RTP proxy > <unix:/var/run/rtpproxy.sock> found, support for it re-enabled > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: udp_send: > sendto(sock,0xb62048f4,1773,0, 10.10.100.103:5060,16): Invalid argument(22) > > > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: CRITICAL: invalid > sendtoparameters one possible reason is the server is bound to localhost > > and attempts to send to the net > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: msg_send: ERROR: udp_send > failed > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: t_send_branch: > sending request on branch 0 failed > > May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: sl_reply_error used: > Unfortunately error on sending to next hop occurred (477/SL) > > > > > > > > When I start SER I get this response: > > > > [root@vx1 ~]# service ser restart > > Stopping ser: > [ OK ] > > Starting ser: Listening on > > udp: 127.0.0.1 [127.0.0.1]:5060 > > udp: 10.10.10.41 [10.10.10.41]:5060 > > tcp: 127.0.0.1 [127.0.0.1]:5060 > > tcp: 10.10.10.41 [10.10.10.41]:5060 > > Aliases: > > tcp: vx1:5060 > > tcp: vx1.velocity11.com:5060 > > tcp: localhost:5060 > > tcp: localhost.localdomain:5060 > > udp: vx1:5060 > > udp: vx1.velocity11.com:5060 > > udp: localhost:5060 > > udp: localhost.localdomain:5060 > > > > > [ OK ] > > [root@vx1 ~]# > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________Ready > for the edge of your seat? > > Check out tonight's top picks on Yahoo! TV. > > http://tv.yahoo.com/ > > _______________________________________________ > > Serusers mailing list > > Serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > ________________________________ > Sucker-punch spam with award-winning protection. > Try the free Yahoo! Mail Beta. > _______________________________________________ > 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 ____________________________________________________________________________________Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php

2 1

Re: [Serusers] Frustrating error - please help
by Mahatma Sarasvati 24 May '07

24 May '07

A good hint, but no. I'm using the standard version 1.4 ser.cfg. I've only added my 10.10.10.41 ip address. The "fork=no" command is commented out. Is there something else that would cause ser to start in non-forking mode? Thanks, M ----- Original Message ---- From: samuel <samu60(a)gmail.com> To: Mahatma Sarasvati <gnoahhb(a)yahoo.com> Cc: serusers(a)iptel.org Sent: Thursday, May 24, 2007 12:40:41 AM Subject: Re: [Serusers] Frustrating error - please help Are you starting SER in non-forking mode? It looks like SER is not binding to the 10.10.10.41 IP, only to the local IP (127.0.0.1) and that's why you see in the logs that it's not able to send to a "standard" IP address: WARNING: xl_mod_init: more IP 10.10.10.41 not used CRITICAL: invalid sendtoparameters one possible reason is the server is bound to localhost and attempts to send to the net Case you need to use 2 interfaces, I would recommend using mhomed=yes (don't recall the exact syntax right now..). Hope it helps, Samuel. 2007/5/24, Mahatma Sarasvati <gnoahhb(a)yahoo.com>: Hi All, This ser installation was working fine and I can't figure out why its not working now. I'm getting an error (see last log line) every time I attempt a call to local users. Calling out to PSTN works great. ngrep reveals that SER is not sending any messages to the callee location. There are 2 registered local users, one registered twice. I have no idea what is going on. I'm using an unmodified version 1.4 ser.cfg file on CentOS 5. I suspect some server configuration error? ? ? ? Thanks, M Here are the logs. May 23 16:03:38 vx1 ser: init_tcp: using epoll_lt as the io watch method (auto detected) May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: Maxfwd module- initializing May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: WARNING: xl_mod_init: more IP 10.10.10.41 not used May 23 16:03:38 vx1 last message repeated 8 times May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: AVPops - initializing May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: DEB: IP address of RTPPROXY is /var/run/rtpproxy.sock May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: xlog null is "<null>" May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF is initially 109568 May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF is finally 262142 May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF is initially 109568 May 23 16:03:38 vx1 /usr/local/sbin/ser[1692]: INFO: udp_init: SO_RCVBUF is finally 262142 . . . . May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: rtpp_test: RTP proxy <unix:/var/run/rtpproxy.sock> found, support for it re-enabled May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: udp_send: sendto(sock,0xb62048f4,1773,0, 10.10.100.103:5060,16): Invalid argument(22) May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: CRITICAL: invalid sendtoparameters one possible reason is the server is bound to localhost and attempts to send to the net May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: msg_send: ERROR: udp_send failed May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: t_send_branch: sending request on branch 0 failed May 23 16:09:15 vx1 /usr/local/sbin/ser[1781]: ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) When I start SER I get this response: [root@vx1 ~]# service ser restart Stopping ser: [ OK ] Starting ser: Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 10.10.10.41 [10.10.10.41]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.10.10.41 [10.10.10.41]:5060 Aliases: tcp: vx1:5060 tcp: vx1.velocity11.com:5060 tcp: localhost:5060 tcp: localhost.localdomain:5060 udp: vx1:5060 udp: vx1.velocity11.com:5060 udp: localhost:5060 udp: localhost.localdomain:5060 [ OK ] [root@vx1 ~]# ____________________________________________________________________________________Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/ _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ____________________________________________________________________________________ Need Mail bonding? Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=list&sid=396546091

2 1

[Users] Sometime t_really() func seem to be endless
by Bodin Bruno 24 May '07

24 May '07

Hi, I don't now why, but when call is cancel or unavaible t_relay is endless and never return anything. anyone know why ? Thank

4 15

[Serusers] SER User Group Meeting In Oslo
by Martin Hoffmann 24 May '07

24 May '07

Heisann, we are currently in the planning stage of the Second SER User Group Meeting. We agreed back in Prague to try to have it in Oslo in summer (no point in coming here in the dark season). The preliminary date for the meeting is Friday, July 13, 2007. However, since this is in the middle of the holiday seasons, I'd rather ask if this suits you all or whether we should move it to September. A more formal invitation will follow later. Best regards, Martin

6 7

[Users] failure_route problem
by Yago Bargalló 24 May '07

24 May '07

Hello, First of all thaks to Kraus for his quick reply on my last question. However I can't do openser work fine. I'm trying to use failure_route as follows, can anybody tell me which could be the problem?? (...) modparam("tm", "fr_inv_timer" , 10) # timer for response to a request modparam("tm","fr_timer", 4) # ------------------------- request routing logic ------------------- # main routing logic route{ (...) if (uri==myself) { (...) # Redirecciono cap a l'asterisk si marquen una extensió que comença per 3 if(uri=~"sip:2[0-9]+@" && method=="INVITE") { t_on_failure("1"); } (...) route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; } failure_route[1]{ rewritehostport("172.16.51.160"); #asterisk rewriteuser("2002"); append_branch(); t_relay(); exit; } With this openser.cfg the call is cancelled after fr_inv_timer and failure_route[1] doesn't work but, however, if I do this: route{ (...) if (uri==myself) { (...) # Redirecciono cap a l'asterisk si marquen una extensió que comença per 3 if(uri=~"sip:2[0-9]+@" && method=="INVITE") { à rewritehostport("172.16.51.160"); #asterisk à rewriteuser("2002"); t_relay(); exit; } (...) route(1); } If I use this the call is redirected to my asterisk but using the failure_route as my first openser.cfg it does't work. Which is my problem?? Thanks....

3 2

[Serusers] SIP Gateway
by David Borgesen 24 May '07

24 May '07

Hello, We are trying to find a SIP to SIP gateway and we fell across this project. Can someone tell me if we can accomplish the following with this software. 1) Our DID/SIP telephone provider does not support the Refer method, and as a result our SipX IP PBX can not transfer calls from extension to extension. 2) As a work around we are thinking that we could install a gateway between the DID provider and SipX where the gateway would support the Refer method and handle the transfers. This method is not ideal because all phone traffic would need to go through the gateway as opposed to a direct connection between the DID/SIP provider and the end user extension, but we can't see any other solution. So, can Ser act as a gateway as needed, or is there another solution that anyone of you can think of. Thanks DB

1 0

[Serusers] t_relay() TCP errors
by tzieleniewski 24 May '07

24 May '07

Hi, When I try to t_relay() a message through SER i get the following errors: May 22 10:31:21 rd ser[22137]: ERROR: tcp_blocking_connect: timeout 10 s elapsed from 10 s May 22 10:31:21 rd ser[22137]: ERROR: tcpconn_connect: tcp_blocking_connect failed May 22 10:31:21 rd ser[22137]: ERROR: tcp_send: connect failed May 22 10:31:21 rd ser[22137]: msg_send: ERROR: tcp_send failed Please point me what could be the reason for this? Maybe such situation is possible in case of non tcp server socket listening?? Cheers Tomasz

2 1

[Serusers] mysql dies -- accounting stopped -- call continues
by Nhadie 24 May '07

24 May '07

Hi All How can i make sure that when mysql dies, ser will not allow calls anymore? Because i had a problem, when mysql died, ser still continued to allow calls and i was not able to account it. How can i resolve this. Thank You in Advance. Regards Ronald

5 11

← Newer
1
...
7
8
9
10
11
12
13
...
30
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 2007