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.
----- Original Message ----
From: samuel <samu60@gmail.com>
To: Mahatma Sarasvati <gnoahhb@yahoo.com>
Cc: serusers@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@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@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers