Hey there,
Once again, many thanks for a swift response Andrei! No, the machine does not have two interfaces, it's a single public ip address. What do you mean about ingress filtering? Which network dumps would be helpful?
Many thanks again!
D -----Original Message----- From: Andrei Pelinescu-Onciul [mailto:pelinescu-onciul@fokus.fraunhofer.de] Sent: 17 July 2004 09:00 To: Dave Bath Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Problem with messages + msilo
On Jul 16, 2004 at 23:44, Dave Bath dave@fuuz.com wrote:
Daniel,
many thanks for swift response!. If I set fork=yes I get the same
error.
If I set listen=<ip> then strange things break.. calls are no longer connected properly, and UAs cant log in.
Any more suggestions?!
Do you have multiple network interfaces on the machine, and UAs on both "sides"? If so turn off ingress filtering on your machine or try to add mhomed=1 in your ser.cfg.
Also send some networks dumps along with the log entries.
Andrei
On Jul 19, 2004 at 13:32, Dave Bath dave@fuuz.com wrote:
Hey there,
Once again, many thanks for a swift response Andrei! No, the machine does not have two interfaces, it's a single public ip address. What do you mean about ingress filtering? Which network dumps would be helpful?
If it's a single ip, than don't worry about ingress filtering. Just dump the udp traffic to your machine port 5060 until you get one of the log error message (sendto ...) and then send use the log and the dump. The message might also be caused by some UA using a 0 source port (which is highly broken), or a 0 destination port or ip in the message uri.
Andrei
-
Andrei Pelinescu-Onciul -
Dave Bath