Hi
I'm using SER from fresh (today) CVS on linux-router with two NIC's, one with public IP, and other with private, and when trying to call from private LAN to public SIP-gateway, on remote side I see that packets have incorrect source address:
17:36:45.131465 172.20.0.202.5060 > xxx.xxx.xxx.147.5060: udp 561 (DF) 17:36:45.156165 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 311 17:36:48.456464 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 637
How can I fix this?
Try to turn on the "mhomed" config option.
Out of curiosity -- how do you deal with natted media?
-jiri
At 05:06 PM 4/1/2003, Michael Vasilenko wrote:
Hi
I'm using SER from fresh (today) CVS on linux-router with two NIC's, one with public IP, and other with private, and when trying to call from private LAN to public SIP-gateway, on remote side I see that packets have incorrect source address:
17:36:45.131465 172.20.0.202.5060 > xxx.xxx.xxx.147.5060: udp 561 (DF) 17:36:45.156165 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 311 17:36:48.456464 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 637
How can I fix this?
-- Michael Vasilenko _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Jiri Kuthan (jiri@iptel.org) wrote:
Try to turn on the "mhomed" config option.
ok now i've got segfault:
[root@cool ser]# ser 0(27418) WARNING: could not rev. resolve 172.20.0.202 Listening on 213.186.192.134 [213.186.192.134]::5060 172.20.0.202 [172.20.0.202]::5060 Aliases: cool.dg.net.ua:5060 [root@cool ser]# mysql - initializing stateless - initializing Maxfwd module- initializing 0(27420) mod_init(): Database connection opened successfuly 0(0) INFO: udp_init: SO_RCVBUF is initially 65535 0(0) INFO: udp_init: SO_RCVBUF is finally 524280 0(0) INFO: udp_init: SO_RCVBUF is initially 65535 0(0) INFO: udp_init: SO_RCVBUF is finally 524280 9(0) INFO: fifo process starting: 27438 9(27438) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... 13(0) INFO: SIGCHLD received: we do not worry about grand-children 15(27454) BUG: tcp_main_loop: dead child 11 15(27454) BUG: tcp_main_loop: dead child 12 15(27454) BUG: tcp_main_loop: dead child 13 15(27454) BUG: tcp_main_loop: dead child 14 0(27420) child process 27453 exited by a signal 11 0(27420) core was not generated 0(27420) child process 27452 exited by a signal 11 0(27420) core was not generated 0(27420) child process 27451 exited by a signal 11 0(27420) core was not generated 0(27420) child process 27450 exited by a signal 11 0(27420) core was not generated 0(27420) INFO: terminating due to SIGCHLD 1(27422) INFO: signal 15 received 2(27423) INFO: signal 15 received 3(27424) INFO: signal 15 received 4(27430) INFO: signal 15 received 5(27431) INFO: signal 15 received 6(27432) INFO: signal 15 received 7(27436) INFO: signal 15 received 8(27437) INFO: signal 15 received 9(27438) INFO: signal 15 received 10(27449) INFO: signal 15 received 15(27454) INFO: signal 15 received 0(27420) db_close(): Invalid parameter value
my config is very close to one in the source tree
Out of curiosity -- how do you deal with natted media?
-jiri
At 05:06 PM 4/1/2003, Michael Vasilenko wrote:
Hi
I'm using SER from fresh (today) CVS on linux-router with two NIC's, one with public IP, and other with private, and when trying to call from private LAN to public SIP-gateway, on remote side I see that packets have incorrect source address:
17:36:45.131465 172.20.0.202.5060 > xxx.xxx.xxx.147.5060: udp 561 (DF) 17:36:45.156165 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 311 17:36:48.456464 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 637
How can I fix this?
-- Michael Vasilenko _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Michael Vasilenko (acid@dg.net.ua) wrote:
Jiri Kuthan (jiri@iptel.org) wrote:
Try to turn on the "mhomed" config option.
ok now i've got segfault:
it seems to be that ser going to segfault with fork=yes in config
[root@cool ser]# ser 0(27418) WARNING: could not rev. resolve 172.20.0.202 Listening on 213.186.192.134 [213.186.192.134]::5060 172.20.0.202 [172.20.0.202]::5060 Aliases: cool.dg.net.ua:5060 [root@cool ser]# mysql - initializing stateless - initializing Maxfwd module- initializing 0(27420) mod_init(): Database connection opened successfuly 0(0) INFO: udp_init: SO_RCVBUF is initially 65535 0(0) INFO: udp_init: SO_RCVBUF is finally 524280 0(0) INFO: udp_init: SO_RCVBUF is initially 65535 0(0) INFO: udp_init: SO_RCVBUF is finally 524280 9(0) INFO: fifo process starting: 27438 9(27438) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... 13(0) INFO: SIGCHLD received: we do not worry about grand-children 15(27454) BUG: tcp_main_loop: dead child 11 15(27454) BUG: tcp_main_loop: dead child 12 15(27454) BUG: tcp_main_loop: dead child 13 15(27454) BUG: tcp_main_loop: dead child 14 0(27420) child process 27453 exited by a signal 11 0(27420) core was not generated 0(27420) child process 27452 exited by a signal 11 0(27420) core was not generated 0(27420) child process 27451 exited by a signal 11 0(27420) core was not generated 0(27420) child process 27450 exited by a signal 11 0(27420) core was not generated 0(27420) INFO: terminating due to SIGCHLD 1(27422) INFO: signal 15 received 2(27423) INFO: signal 15 received 3(27424) INFO: signal 15 received 4(27430) INFO: signal 15 received 5(27431) INFO: signal 15 received 6(27432) INFO: signal 15 received 7(27436) INFO: signal 15 received 8(27437) INFO: signal 15 received 9(27438) INFO: signal 15 received 10(27449) INFO: signal 15 received 15(27454) INFO: signal 15 received 0(27420) db_close(): Invalid parameter value
my config is very close to one in the source tree
Out of curiosity -- how do you deal with natted media?
-jiri
At 05:06 PM 4/1/2003, Michael Vasilenko wrote:
Hi
I'm using SER from fresh (today) CVS on linux-router with two NIC's, one with public IP, and other with private, and when trying to call from private LAN to public SIP-gateway, on remote side I see that packets have incorrect source address:
17:36:45.131465 172.20.0.202.5060 > xxx.xxx.xxx.147.5060: udp 561 (DF) 17:36:45.156165 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 311 17:36:48.456464 xxx.xxx.xxx.147.5060 > 172.20.0.202.5060: udp 637
How can I fix this?
-- Michael Vasilenko _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
-- Michael Vasilenko _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
At 06:19 PM 4/1/2003, Michael Vasilenko wrote:
Michael Vasilenko (acid@dg.net.ua) wrote:
Jiri Kuthan (jiri@iptel.org) wrote:
Try to turn on the "mhomed" config option.
ok now i've got segfault:
it seems to be that ser going to segfault with fork=yes in config
Try now -- some of missing pieces have been committed. You would be probably safer with CVS snapshot as of Mar 13th, 6pm.
-Jiri
-
Jiri Kuthan -
Michael Vasilenko