Hi Bogdan,

I'm not using alias.

I've realized that if I request authorization for the initial INVITE,
everything works like a charm.

If I just by pass (using allow_trusted) it doesn't work and opensips
route the ACK to itself.

If you don't mind follow attached my cfg. It's "simple".

Thanks,

Noel

On Fri, Mar 20, 2009 at 2:54 PM, Bogdan-Andrei Iancu
<[email protected]> wrote:
> Hi Noel,
>
> it looks like OpenSIPS is doing strict routing on the received ACK.
>
> This happens if it finds out in RURI an IP/address which is considered local
> - in the case the RURI will be consumed and use the Route as new RURI...
>
>
> So are you sure there is no misconfiguration in the alias params ?
>
> Regards,
> Bogdan
>
> Noel R. Morais wrote:
>>
>> Hi guys,
>>
>> I'm having problems about loose_route(). Opensips is routing ACK
>> requests to itself.
>>
>> I know that posting code and traces are ugly, but I think I do not
>> have choices. Sorry.
>>
>> Follow bellow the code regarding loose_route:
>> if (has_totag()) {
>>                if (loose_route()) {
>>                        if(method=="INVITE") {
>>                                route(5); #Check authentication of
>> re-invites
>>                        }
>>                        route(1);
>>                } else {
>>                        if ( is_method("ACK") ) {
>>                                if ( t_check_trans() ) {
>>                                        route(1);
>>                                }
>>                }
>>        }
>> }
>>
>>
>> Follow bellow the trace, 192.168.191.188 is the opensips ip address:
>> U 2009/03/11 14:46:53.950565 192.168.191.188:5060 -> 192.168.192.233:5060
>> SIP/2.0 200 OK.
>> Via: SIP/2.0/UDP 192.168.192.233;branch=z9hG4bKac74079177.
>> Contact: <sip:[email protected]:5060>.
>> Record-Route:
>> <sip:192.168.191.188;lr=on;ftag=1c74077990;did=f9e.d32b00d2>.
>> Call-ID: [email protected].
>> From: "Jeff002" <sip:[email protected]>;tag=1c74077990.
>> To:
>> <sip:[email protected];user=phone>;tag=a94c095b773be1dd6e8d668a785a9c8469ec.
>> CSeq: 1 INVITE.
>> Server: Cantata-SIP/10.3.2.51932 IMG 0.
>> Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, INFO.
>> Supported: path.
>> Accept: application/sdp.
>> Content-Type: application/sdp.
>> Content-Length: 236.
>> .
>> v=0.
>> o=Cantata_SDP 0 1 IN IP4 192.168.193.20.
>> s=Cantata-SIP.
>> c=IN IP4 192.168.193.21.
>> t=0 0.
>> m=audio 8944 RTP/AVP 18 101.
>> a=rtpmap:18 G729/8000.
>> a=rtpmap:101 telephone-event/8000.
>> a=fmtp:101 0-15.
>> a=silenceSupp:off - - - -.
>> a=ptime:20.
>>
>>
>> U 2009/03/11 14:46:53.997019 192.168.192.233:5060 -> 192.168.191.188:5060
>> ACK sip:[email protected]:5060 SIP/2.0.
>> Via: SIP/2.0/UDP 192.168.192.233;branch=z9hG4bKac82192814.
>> Max-Forwards: 70.
>> From: "Jeff002" <sip:[email protected]>;tag=1c74077990.
>> To:
>> <sip:[email protected];user=phone>;tag=a94c095b773be1dd6e8d668a785a9c8469ec.
>> Call-ID: [email protected].
>> CSeq: 1 ACK.
>> Contact: <sip:[email protected]>.
>> Route: <sip:192.168.191.188;lr=on;ftag=1c74077990;did=f9e.d32b00d2>.
>> Supported: em,timer,replaces,path.
>> Allow:
>> REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE.
>> User-Agent: Audiocodes-Sip-Gateway-MP-102 FXS/v.4.60A.035.001.
>> Content-Length: 0.
>> .
>>
>>
>> U 2009/03/11 14:46:53.998178 192.168.191.188:5060 -> 192.168.191.188:5060
>> ACK sip:192.168.191.188;lr=on;ftag=1c74077990;did=f9e.d32b00d2 SIP/2.0.
>> Record-Route: <sip:192.168.191.188;lr=on;ftag=1c74077990>.
>> Via: SIP/2.0/UDP 192.168.191.188;branch=z9hG4bKef17.5d8b81f4.2.
>> Via: SIP/2.0/UDP 192.168.192.233;branch=z9hG4bKac82192814.
>> Max-Forwards: 69.
>> From: "Jeff002" <sip:[email protected]>;tag=1c74077990.
>> To:
>> <sip:[email protected];user=phone>;tag=a94c095b773be1dd6e8d668a785a9c8469ec.
>> Call-ID: [email protected].
>> CSeq: 1 ACK.
>> Supported: em,timer,replaces,path.
>> Allow:
>> REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE.
>> User-Agent: Audiocodes-Sip-Gateway-MP-102 FXS/v.4.60A.035.001.
>> Content-Length: 0.
>>
>> _______________________________________________
>> Users mailing list
>> [email protected]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>

Attachment: opensips.m4
Description: Binary data

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to