No, you are not dealing with a buggy client.
As Carlos pointed out, you are dealing with standard SIP loose routing
mechanism.
Time to read the RFC :)
Regards,
Ovidiu Sas
On Wed, Mar 5, 2014 at 2:24 PM, Marc Soda wrote:
> Yeah, I think I'm dealing with a buggy client...
>
> Thanks all.
>
>
> On
Yeah, I think I'm dealing with a buggy client...
Thanks all.
On Wed, Mar 5, 2014 at 1:57 PM, Carlos Ruiz Díaz
wrote:
> Why is erroneous to have the contact header with the backend IP?
>
> With the record-route on the 200 Ok, the ACK should be directed to the
> backend IP, but containing a route
Why is erroneous to have the contact header with the backend IP?
With the record-route on the 200 Ok, the ACK should be directed to the
backend IP, but containing a route header pointing to the Kamailio IP.
Kamailio will loose_route() this request and send it to the backend server
as expected.
Re
Thanks Olle. I am calling record_record() on the initial INVITE. In fact,
the OK has a Record-Route header:
1.1.1.1 is the endpoint
2.2.2.2 is the kamailio proxy
3.3.3.3 is the backend server
SIP/2.0 200 OK
Via: SIP/2.0/UDP 1.1.1.1:60077
;rport=46110;branch=z9hG4bK-d8754z-eb9768c7e3a2d1e7-1---d
On 05 Mar 2014, at 18:30, Marc Soda wrote:
> I have Kamailio setup as a proxy in front of a backend server (Asterisk).
> When I make a call through the proxy, the Contact header in the 200 OK that
> is returned to the client has the IP of the backend server in it. Thus, the
> client is send
I have Kamailio setup as a proxy in front of a backend server (Asterisk).
When I make a call through the proxy, the Contact header in the 200 OK
that is returned to the client has the IP of the backend server in it.
Thus, the client is sending it's ACK directly to the backend server.
Is there a
