27 Sep
2006
27 Sep
'06
6:42 p.m.
Hello!
I've tried to modify my setup to use rtpproxy, following the guide
posted at http://siprouter.onsip.org/doc/gettingstarted/, most of it
works fine, but i have a small but annoying problem:
When i receive a invite from a UA, i verify the identity with
proxy_authorize. However, the proxy-authenticate-request is not sent
to the originating sip-port of the UA but to 5060 for some reason.
In my old setup this worked flawless, the proxy authorize request is
sent to the correct external port of the phone.
To me it seems there is no difference in this part of the route-plan,
so how does this happen?
I have attached both config-files and a ngrep of the requests(*.old
is the working setup, *.rtpproxy is the new setup that doesn't work),
maybe someone can help me with this? Thanks in advance!
Regards
Christian
27 Sep
27 Sep
7:22 p.m.
New subject: [Users] Re: proxy authorization required sent to the wrong port
sorry for the attachments, here they are as txt-files...
28 Sep
28 Sep
9:21 a.m.
New subject: [Users] Re: proxy authorization required sent to the wrong port
In the old version you've got the next lines:
if( nat_uac_test( "19" ) ) {
fix_nated_contact();
if ( ! search( "^Content-Length:\ 0" ) ) {
fix_nated_sdp( "3" );
};
force_rport();
setflag( 6 );
};
BEFORE the proxy_authorize call which means that you will use rport in
the challenge and returned the reply to the port the request came
from.
In the new version, you moved these lines AFTER the proxy_authorize
and therefore there is no rport/fix_* in the digest authorization
message exchange.
So:
Reorder the NAT detection&solution BEFORE the proxy_authorize call.
Samuel.
2006/9/27, Benko <benkokakao(a)gmail.com>om>:
sorry for the attachments, here they are as
txt-files...
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
10:28 a.m.
New subject: [Users] Re: proxy authorization required sent to the wrong port
Ah! Cool! Thanks a lot for your answer, that was unobviously obvious(at
least for me) ;-) working now...
guess i need more openser dialplan training till i get the logic...
thx
christian
On Thu, 28 Sep 2006 09:21:12 +0200
samuel <samu60(a)gmail.com> wrote:
In the old version you've got the next lines:
if( nat_uac_test( "19" ) ) {
fix_nated_contact();
if ( ! search( "^Content-Length:\ 0" ) ) {
fix_nated_sdp( "3" );
};
force_rport();
setflag( 6 );
};
BEFORE the proxy_authorize call which means that you will use rport in
the challenge and returned the reply to the port the request came
from.
In the new version, you moved these lines AFTER the proxy_authorize
and therefore there is no rport/fix_* in the digest authorization
message exchange.
So:
Reorder the NAT detection&solution BEFORE the proxy_authorize call.
Samuel.
2006/9/27, Benko <benkokakao(a)gmail.com>om>:
> sorry for the attachments, here they are as txt-files...
>
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
>
>
>
6638
days inactive
6639
days old
3 comments
2 participants
participants (2)
-
Benko -
samuel