RE: [Serusers] fix_socket_list: could not rev. resolve .....

Hi,       SER cannot listen on private IP addresses, the listen address should be the public address of the interface on which SER is running. The address(es) should not be 127.* or 192.* To eliminate this problem, use either of the two simple approaches; 1. EITHER use the command line “ser –l xxx.xxx.xxx.xxx” where xxx.xxx.xxx.xxx is the public ip of the machine 2. OR, insert the line “listen= xxx.xxx.xxx.xxx” on top variable declarations sections of your ser.cfg file. This approach is a better one. Hope that helps. Regards, Ashutosh ________________________________________ From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Linh Pham Sent: Tuesday, August 09, 2005 8:13 AM To: serusers(a)lists.iptel.org Subject: [Serusers] fix_socket_list: could not rev. resolve ..... Hi I'm new to Linux and SER so bear with me :) Yesterday I installed FC4 and SER (tar.gz). SER runs OK and I was able to capture some packets with Ethereal. However, this morning SER is not working. I didn't change anything in the config file. The line 'fifo=/tmp/ser_fifo' still in the config file. What should I do to make SER run again? And please explain what 'Segmentation fault' in ser -c means. Thank you. [root@localhost /]# ser -c  0(5050) WARNING: fix_socket_list: could not rev. resolve 192.168.1.10  0(5050) WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Listening on              udp: 127.0.0.1 [127.0.0.1]:5060              udp: 192.168.1.10 [192.168.1.10]:5060              tcp: 127.0.0.1 [127.0.0.1]:5060              tcp: 192.168.1.10 [192.168.1.10]:5060 Aliases:              tcp: localhost:5060              tcp: localhost.localdomain:5060              udp: localhost:5060              udp: localhost.localdomain:5060 config file ok, exiting... Segmentation fault [root@localhost /]# uname -a Linux localhost.localdomain 2.6.11-1.1369_FC4smp #1 SMP Thu Jun 2 23:08:39 EDT 2005 i686 i686 i386 GNU/Linux [root@localhost /]# serctl ps Error opening ser's FIFO /tmp/ser_fifo Make sure you have line fifo=/tmp/ser_fifo in your config [root@localhost /]# var/log/messages: Aug  9 09:04:44 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:04:44 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:04:44 localhost ser[4815]: Maxfwd module- initializing Aug  9 09:05:46 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:05:46 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:05:46 localhost ser[4847]: Maxfwd module- initializing Aug  9 09:08:06 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:08:06 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:08:06 localhost ser[4881]: Maxfwd module- initializing Aug  9 09:08:09 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:08:09 localhost ser: WARNING: fix_socket_list: could not rev. resolve 192.168.1.10 Aug  9 09:08:09 localhost ser[4884]: Maxfwd module- initializing -- Best regards, Linh Pham