I fixed the problem. It was the weirdest thing: the broadcast address of the interface went bananas, and displayed a really wrong IP. I had to put in a new IP in there, and then go back to the old one before the broadcast recalculated itself properly.
-----Original Message----- From: Igor Selivanov [mailto:iselivanov@tevue.com] Sent: August 26, 2004 8:18 AM To: serusers@lists.iptel.org Subject: RE: [Serusers] Ser question
Thank you, it certainly is useful, but my problem seems to be on the network level. Regardless if SER is only running on public interface, all responses are being sent back over the privete interface. And it doesn't seem to be just SER. I guess I better ask about this problem in another forum, but if anyone here has any ideas, I would be very gratefull
Igor
--- Zeus Ng zeus.ng@isquare.com.au wrote:
In your ser.cfg file, specify listen=xxxx where xxxx is the interface card that has public address, like eth0.
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of
Igor Selivanov
Sent: Thursday, 26 August 2004 2:55 PM To: serusers@lists.iptel.org Subject: [Serusers] Ser question
I am having a rather odd problem. I had the Ser server working for a while, but all the sudden, strange stuff started happening. I have it
running on
Redhat AS3 Server, with 2 network cards, one with
a
public, and another with a private address. I
have
the sip phones configured to have the public
address
as the as their sip server. The strange thing is, though, when I sniff, I see the darn server get
the
Register request on the public interface, but
sending
the OK response on the private one! I tried
turning
the private IP interface off alltogether, but then
it
simply sends nothing back at all...it has been
very
frustrating, as it was working fine before.
Serusers mailing list serusers@lists.iptel.org
-
Igor Selivanov