On Nov 13, 2006 at 14:03, Gustavo Passos Tourinho
<gustavo.passos.tourinho(a)gmail.com> wrote:
Hi There
Yeap, ACK should be forwarded to callee. In fact, the proxy is doing
such thing. But, when it does, it puts a route at the end of ACK message.
You mean a Record-Route? If so I don't understand what the problem is
(you have an extra RR in the ACK which will be ignored).
If you want to avoid it, make sure record_route() is not called for
ACKs (if (method!="ACK") { record_route(); } ).
If is really a Route then please dump the sip traffic before and after
leaving ser and post the bad call and the bad ACK.
Actually I have a "record_route()"
function.
Ill try to read more about ser.cfg to find out some solution.
Thanks,
Tourinho
Andrey Kuprianov wrote:
>Hi,
>
>Sure. It should forward ACK to the callee, right? Otherwise, how can
>the callee know whether the connection is established properly (i.e.
>3-way handshake, unless your transport is TCP) :)
>
>Plus, ACK is a request, isnt it? You configuration file probably has
>this part somewhere at the beginning:
>
>if(method!="REGISTER") {
> record_route();
>};
>
>This means that SER will attach route headers to every request except
>REGISTER.
>
> Good luck,
>
> Andrey.
>
>
>
>On 11/13/06, Gustavo Passos Tourinho
><gustavo.passos.tourinho(a)gmail.com> wrote:
>>Hey There.
>>
>>I'm having a weird signaling. When the proxy receives an ACK from
>>caller, it puts an route at the end of packet and then forwards it.
>>
>>I have no idea what i could be.
>>
>>Does anyone have a clue?
>>
>>Thanks in advanced,
>>Tourinho
Andrei