New subject: [Serusers] error revisited: I won't send a reply for ACK!!

23 Feb 2005

Thanks,

That is correct, it hits this part:

        if (!mf_process_maxfwd_header("10")) {
                sl_send_reply("483", "Too Many Hops");
                break;
        };

And that is because the ACK keeps getting back at the SER. (It gets
routed back to the SER itself, as described below). I want to solve this
problem; the ACK should be routed to my UA, but apparently it does not
since it's local IP address it not stated in the SIP header. (Only the
public IP address of the SER-machine is stated in the SIP header.)

Any other ideas?

Roel

...
  -----Original Message-----
 From: Java Rockx [mailto:javarockx@gmail.com]
 Sent: Wednesday, February 23, 2005 13:17
 To: Roel van Dijk
 Cc: serusers(a)lists.iptel.org
 Subject: Re: [Serusers] error revisited: I won't send a reply for ACK!!
...

 I had this problem just a while ago. It was report to me, from Richard
 I think, that somewhere in my ser.cfg an ACK was hitting an
 sl_send_reply() which is incorrect.

 ACK messages must hit a t_relay() to avoid this message.

 Regards,
 Paul

RE: [Serusers] error revisited: I won't send a reply for ACK!!