[Siproxd-users] ERROR:I'm trying to delete a VIA but it's not mine!
Status: Beta
Brought to you by:
tries
From: Colin G. <gm...@co...> - 2007-06-21 11:50:32
|
Hi, I've just starting using siproxd as it appears to be the ideal solution to my network setup. We have a small office and are behind a NAT router and want to use several hardware phones and Ekiga in our office. Everything is routed through our main office server which runs siproxd but it does not do the NAT, this is left to our ADSL Modem which also DNATs ALL traffic back to this server for incoming connections. On this server the external network is connected to via eth0 and the internal via eth1. The external subnet (to talk to the router) is 192.168.0.0/24 and the internal is 192.168.112.0/24. My /etc/siproxd.conf is as below. Through trial and error, I have found that I need to connect via an outgoing proxy in order to make things work. Not doing so will give the above errors (as per the subject). Unfortunately, recently I've found that even doing so still appears to log the occasional error about deleting a VIA that is not mine, even tho' the full error lists the IP address specified in host_outbound. I would have through that siproxd should consider the host_outbound IP to be "one of it's own!"? Also I found I needed the three part outbound proxy for things to work reliably. This was also through trial and error. I would have thought that no proxy should be needed here and that I SHOULD be able to connect siproxd directly to the internet due to the fact that all incoming connections are DNAT'ed back to the server from the firewall? Or is there perhaps a problem in that the outgoing packets from the server are NATed by the router? If so should I try to disable this? (e.g. move the NATing to the server?) From what I've read this does not appear to be a problem. The phones in question are not setup to use STUN or any other NAT technique. They are just configured to use an outgoing proxy which points to the internal machine. I have another problem relating to a message "Unable to Parse SIP message. This is not good." but I'll write about that in another mail. If someone could say what they would need from a debug log for helping to fix this I could make sure this is done correctly first post. Also any advice as to what to blank out would help! Generally I find that even when things work for the most part, I will have to reset all the phones once a day which is very annoying! I am using the latest snapshot build of siproxd. FWIW I'm connecting to Gradwell's VOIP service. I know this list does not have much traffic so if there is a better way to request some help then please let me know! Thanks. Col if_inbound = eth1 if_outbound = eth1 host_outbound = <OUR EXTERNAL STATIC IP> hosts_allow_reg = 192.168.0.0/16 sip_listen_port = 5060 daemonize = 1 silence_log = 1 log_calls = 1 user = siproxd registration_file = /var/lib/siproxd/siproxd_registrations autosave_registrations = 300 pid_file = /var/run/siproxd/siproxd.pid rtp_proxy_enable = 1 rtp_port_low = 7070 rtp_port_high = 7089 rtp_timeout = 300 rtp_dscp = 46 rtp_input_dejitter = 100000 rtp_output_dejitter = 100000 default_expires = 600 debug_level = 0x00000004 debug_port = 0 outbound_domain_name = lon-pbx-3.gradwell.net outbound_domain_host = nat1.gradwell.net outbound_domain_port = 5082 pi_shortdial_enable = 0 pi_shortdial_akey = *00 pi_shortdial_entry = 17474743246 pi_shortdial_entry = 17474745000 |