[Serusers] cisco 7905G

Alberto alberto.ipt at telefonica.net
Tue Sep 27 17:44:10 CEST 2005


Thanks, I did it.

I use the  force_rport() function before to authorize the 7905G.

My code is based of OnSIP.org examples. My final ser.cfg is:

route[3] {

        # -----------------------------------------------------------------
        # INVITE Message Handler
        # -----------------------------------------------------------------

        if (client_nat_test("3")) {          # <---------- In the original 
ser.cfg (OnSIP.org) this code was after next "if"
                setflag(7);
                force_rport();
                fix_nated_contact();
        };

        if (!allow_trusted()) {

                if (!proxy_authorize("","subscriber")) {
                        proxy_challenge("","0");
                        break;
                } else if (!check_from()) {
                        sl_send_reply("403", "Use From=ID");
                        break;
                };

                consume_credentials();
        };

       ...............................................




----- Original Message ----- 
From: "Nils Ohlmeier" <lists at ohlmeier.org>
To: <serusers at lists.iptel.org>
Cc: "Alberto" <alberto.ipt at telefonica.net>
Sent: Tuesday, September 27, 2005 1:25 PM
Subject: Re: [Serusers] cisco 7905G


> It seems like the phone does not provide the rport parameter in the Via
> header. Either you turn it on at the phone. Otherwise the phone is almost
> unusable behind NATs. Anyway you could still try to detect this phone 
> models
> and use force_rport (I dont remember the exact spelling, but there should 
> be
> a function like this), then the rport parameter is added by SER.
>
>  Nils
>
> On Tuesday 27 September 2005 11:00, Alberto wrote:
>> Hi,
>> I have the next scheme:
>>
>>     7905G ------- NAT ------- Internet ------ SER+mediaproxy
>>
>> When the 7905G sends a INVITE the ser responds:
>>    Status: 407 Proxy Authentication Required.
>>
>> This is right, but the destination port this packet not is right because
>> the ser sends the packet with
>> destination port 5060  (private port) and not the (public port). If I 
>> open
>> this port all it is right, I do not
>> want to open no port.
>>
>> This single problem happens to me with 7905G (no linksys, no X-Ten, ...).
>>
>> I do not understand what it is happening.
>>
>> Thanks for your aid.
>>
>> --
>> Alberto
>>
>> _______________________________________________
>> Serusers mailing list
>> serusers at lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers 




More information about the sr-users mailing list