Andreas Granig schrieb:
Hi all,
I just tried a setup like
[UA] --> [pub][Firewall][priv] --> [priv][Kam]
where the Firewall maps the public IP reachable by UAs to a private IP
where Kamailio is listening. If I run sipsak on the Kamailio-machine, I
can register fine, but as soon as the requ
Hello,
On 05/11/2009 12:54 PM, Andreas Granig wrote:
> Inaki, Daniel,
>
> In debug mode, it only shows that in auth/api.c:check_response the
> result doesn't match.
>
> Since I managed to authenticate sipsak and qutecom, but not linphone, I
> also guess there must be something wrong with the imp
Inaki, Daniel,
In debug mode, it only shows that in auth/api.c:check_response the
result doesn't match.
Since I managed to authenticate sipsak and qutecom, but not linphone, I
also guess there must be something wrong with the implementation.
Strange thing is that it works in a setup without FW
Juha,
Seems you're right, I managed to register with sipsak using -p for
outbound proxy, and also with Qutecom, if uri is set to the 172.17.10.50
ip. Funny thing is that linphone refuses to register (error code for
"wrong password" in Kamailio) although the Authorization header looks
the same
Hello,
running in debug mode should reveal also more details about where the
issue actually resides.
Cheers,
Daniel
On 05/10/2009 06:10 PM, Iñaki Baz Castillo wrote:
> El Domingo, 10 de Mayo de 2009, Andreas Granig escribió:
>
>> So the only thing referring to the public Firewall IP is in th
El Domingo, 10 de Mayo de 2009, Andreas Granig escribió:
> So the only thing referring to the public Firewall IP is in the R-Uri of
> the registration and in the Authorization-uri-token. Is this token also
> used to calculate the auth hashes somehow?
> Username looks fine in the Authorization heade
Andreas Granig writes:
> So how does the IP of Kamailio actually influence authentication? Do I
> have to set something special on Kamailio to make this work?
i don't think ip addresses have anything to do with authentication. in
your example, request uri should have the domain the registrati
Hi all,
I just tried a setup like
[UA] --> [pub][Firewall][priv] --> [priv][Kam]
where the Firewall maps the public IP reachable by UAs to a private IP
where Kamailio is listening. If I run sipsak on the Kamailio-machine, I
can register fine, but as soon as the request goes via Firewall,
auth
