[Serusers] SER issue on startup

Thanks Javarockx That fixed the error and yes I had it running already Thank you _____ From: Java Rockx [mailto:javarockx@gmail.com] Sent: Monday, 11 April 2005 9:50 AM To: Mr Greg Plater Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] SER issue on startup Greg, Could you have multiple instances of ser running? Also, perhaps you can just add this to the top of your ser.cfg: listen=192.168.1.4 port=5060 Regards, Paul On Apr 10, 2005 7:16 PM, Mr Greg Plater <gplater(a)da-bratz.com> wrote: I seen to have mis configured my ser.cfg file in some way. Can anyone tell me what I have done wrong [root@altcall2 ser]# /usr/local/sbin/ser -D -E 0(1832) WARNING: fix_socket_list: could not rev. resolve 1.1.1.1 0(1832) WARNING: fix_socket_list: could not rev. resolve 1.1.1.1 Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 1.1.1.1 [1.1.1.1]:5060 udp: 192.168.1.4 [192.168.1.4]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 1.1.1.1 [1.1.1.1]:5060 tcp: 192.168.1.4 [192.168.1.4]:5060 Aliases: tcp: altcall2:5060 tcp: altcall2.altcall.com:5060 tcp: localhost:5060 udp: altcall2:5060 udp: altcall2.altcall.com:5060 udp: localhost:5060 stateless - initializing [root@altcall2 ser]# 0(0) Maxfwd module- initializing textops - initializing 0(0) ERROR: tcp_init: bind(7, 0x8132bfc, 16) on 127.0.0.1: Address already in use _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers