The non-200 ACK is hop-by-hop an belongs to the INVITE transaction. It is not routed with record routing. In your case it's the responsability of the proxy to generate an ACK for the hop between proxy and dest (which can happen as soon as the 401 response arrives at the proxy).
Am Wed, 25 Jan 2012 13:39:02 -0500 schrieb Peter Loeppky <[email protected]>: > It appears that _trans_layer::send_non_200_ack() is not working with > loose routing. > > In my case, I have sems configured as a sbc pointing to a load > balancing proxy server then to destination. > > Sems proxy dest > |INVITE ------->| > | |INVITE ------>| > | |<----------401| > |<-----------401| > |ACK----------->| > > There is what I see as the last two messages: > > SIP/2.0 401 Unauthorized > Via: SIP/2.0/UDP > xxxxxxxxxx:xxxx;received=xxxxxxxxxx;branch=z9hG4bKNhgUJab9;rport=xxxx > Record-Route: <sip:xxxxxxxxxx;lr> > Record-Route: > <sip:xxxxxxxxxx;lr;ftag=642E8657-4F1EFE5C000428EB-B6E17B90> To: > <sip:Xxxxxxxxxxx@xxxxxxxxxx> From: > <sip:xxxxxxxxxx@xxxxxxxxxx>;tag=642E8657-4F1EFE5C000428EB-B6E17B90 > Call-ID: 452BAC97-4F1EFE5C000428F0-B6E17B90 CSeq: 10 INVITE > Server: Sippy > WWW-Authenticate: Digest > realm="xxxxxxxxxx",nonce="2768bdf413db29e8ef8c5590c4a87715ef6f" > Content-Length: 0 > > > ACK sip:xxxxxxxxxx@xxxxxxxxxx;transport=tcp SIP/2.0 > Via: SIP/2.0/UDP xxxxxxxxxx:xxxx;branch=z9hG4bKNhgUJab9;rport > From: > <sip:xxxxxxxxxx@xxxxxxxxxx>;tag=642E8657-4F1EFE5C000428EB-B6E17B90 > To: <sip:xxxxxxxxxx@xxxxxxxxxx> Call-ID: > 452BAC97-4F1EFE5C000428F0-B6E17B90 CSeq: 10 ACK > -- Emil Kroymann VoIP Services Engineer Email: [email protected] Tel: +49-30-203899885 Mobile: +49-176-38389303 ISACO GmbH Kurfürstenstraße 79 10787 Berlin Germany Amtsgericht Charlottenburg, HRB 112464B Geschäftsführer: Daniel Frommherz
signature.asc
Description: PGP signature
_______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
