[Users] ACK transaction

[Bogdan-Andrei Iancu]

Hi Tamas,

I guess you are using an version older than 1.1.x of openser - starting 
with 1.1.0, the e2e ACKs do have a distinct branch (and not 0 as prior).

but anyhow, the ACK acc should work - maybe the ACK received by openser 
does not match the INVITE, so it is not accounted. try to run in debug 
mode to see if the ACK match the INVITE. Look for something like:
   
DEBUG: t_lookup_request: e2e proxy ACK found


regards,
bogdan

Cseke Tamas wrote:
> Hello,
>
> I'd like to relay sip calls from openserto another sip proxy 
> (asterisk), and i have a problem with radius
> accounting, i 'd like to report acks, but openser doesn't send 
> accounting packet on it.
> As i understand ack requests must match a transaction flaged to 
> accounting.
>
> Config look like this, so i think all transaction is flaged.
>
> modparam("acc", "report_ack", 1)
> modparam("acc", "radius_flag", 1)
> modparam("acc", "radius_missed_flag", 2)
>
> route{
>       ...
>     setflag(1);
>      setflag(2);
>       ...
> }
>
>
> Asterisk retransmit the 200 ok, so i think there is something mistake 
> in the ack.
> as i read in rfc 3261,
> ACK must match the dialog, callid, from, to, fromtag, to, tag, and 
> sequence number is relevant.
> and ack on a 200 ok, is always a new transaction, however i see branch 
> parameter is 0 in the ack, it must start with the magic cookie 
> z9hG4..., isn't it?
>
> I dont understand what could be the problem, why 200 ok is 
> retransmitted, and why not openser send acctpacket to radius.
>
> Please someone take a look at the sip messages
>
> openser->asterisk
>
> INVITE sip:0619997400 at 127.0.0.1:5061 SIP/2.0
> Record-Route: <sip:217.116.32.20;lr=on;ftag=LAWYzDCZnyMjZxIp>
> Via: SIP/2.0/UDP 217.116.32.20;branch=z9hG4bKde6a.a93de1c7.0
> Via: SIP/2.0/UDP 
> 192.168.1.150:1720;received=217.116.36.22;branch=z9hG4bKvDD2OX3SfnAE6cR5;rport=1720 
>
> Max-Forwards: 69
> User-Agent: PA168S V1.53.006 CFG0
> From: "222" <sip:222 at siptest>;tag=LAWYzDCZnyMjZxIp
> To: "0619997400" <sip:0619997400 at siptest>
> Call-ID: x3Gd6ZKUB9IeRuPO at 192.168.1.150
> Contact: <sip:222 at 217.116.36.2:1720>
> CSeq: 2 INVITE
> Supported: replaces
> Content-Type: application/sdp
> Content-Length: 275
>
> [sdp]
>
>
> asterisk->openser
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 
> 217.116.32.20;branch=z9hG4bKde6a.a93de1c7.0;received=217.116.32.20
> Via: SIP/2.0/UDP 
> 192.168.1.150:1720;received=217.116.36.2;branch=z9hG4bKvDD2OX3SfnAE6cR5;rport=1720 
>
> Record-Route: <sip:217.116.32.20;lr=on;ftag=LAWYzDCZnyMjZxIp>
> From: "222" <sip:222 at siptest>;tag=LAWYzDCZnyMjZxIp
> To: "0619997400" <sip:0619997400 at siptest>;tag=as37b57c9f
> Call-ID: x3Gd6ZKUB9IeRuPO at 192.168.1.150
> CSeq: 2 INVITE
> User-Agent: eWorld Com
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Contact: <sip:0619997400 at 217.116.32.20:5061>
> Content-Type: application/sdp
> Content-Length: 206
>
> [sdp]
>
> openser->asterisk
>
> <-- SIP read from 217.116.32.20:5060:
> ACK sip:0619997400 at 127.0.0.1:5061 SIP/2.0
> Record-Route: <sip:217.116.32.20;lr=on;ftag=LAWYzDCZnyMjZxIp>
> Via: SIP/2.0/UDP 217.116.32.20;branch=0
> Via: SIP/2.0/UDP 
> 192.168.1.150:1720;received=217.116.36.2;branch=z9hG4bKKysauOpwGdpnsmlS;rport=1720 
>
> Route: <sip:217.116.32.20;lr=on;ftag=LAWYzDCZnyMjZxIp>
> Max-Forwards: 69
> User-Agent: PA168S V1.53.006 CFG0
> From: "222" <sip:222 at siptest>;tag=LAWYzDCZnyMjZxIp
> To: "0619997400" <sip:0619997400 at siptest>;tag=as37b57c9f
> Call-ID: x3Gd6ZKUB9IeRuPO at 192.168.1.150
> Contact: <sip:222 at 217.116.36.2:1720>
> Authorization: Digest username="222", realm="siptest", 
> nonce="45dea111f92e1d1f9bf408a3996413168c304ee9", 
> uri="sip:0619997400 at 217.116.32.20:5061", 
> response="50419464515ca2771ec4b2bde7147219", algorithm=MD5
> CSeq: 2 ACK
> Content-Length: 0
>
> Thanks any help,
> Tamas
>
>
> _______________________________________________
> Users mailing list
> Users at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>