[Serusers] Problems with ACK

[Ricardo Martinez]

Hello Jiri,  hello Andrei.
	Thanks for your answers.
	I made a mistake posting the trace and I missed the ACK with problems.
I'm attaching the full trace.

(ack_full_trace.cap)

Just for you to know, the setting is exactly as Jiri pointed.

.100/UAC -----NAT/.248----> SER outbound @ .246 -----> GW @ .239

Can you guide me and tell me in which part of the RFC is this "3261 style transaction matching" rule?
Thanks guys for your help.

Best Regards,
Ricardo Martinez
RedVoiss Chile.

-----Mensaje original-----
De: Jiri Kuthan [mailto:jiri at iptel.org]
Enviado el: martes, 27 de marzo de 2007 17:24
Para: Ricardo Martinez; serusers at iptel.org
Asunto: RE: [Serusers] Problems with ACK


I think the key message for problem analysis, client's ACK, is missing. This is the setting,
right:?

.100/UAC -----NAT/.248----> SER outbound @ .246 -----> UAS @ .239

The ACK in your message dump is only that one sent from proxy (246) to UAS
(.239). The ACK which can possibly mismatch and produce the error message
you mentioned must come from upstream. To be properly formatted, it must
have Via identical to that of initial INVITE 
(        Via: SIP/2.0/UDP 192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087)

-jiri


At 17:50 27/03/2007, Ricardo Martinez wrote:
No.     Time        Source                Destination           Protocol Info
>     14 6.102719    100.100.100.239         100.100.100.246         SIP      Status: 487 Request Terminated
>Session Initiation Protocol
>    Status-Line: SIP/2.0 487 Request Terminated
>        Status-Code: 487
>        Resent Packet: False
>    Message Header
>        Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
>        Via: SIP/2.0/UDP 192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087

 
>No.     Time        Source                Destination           Protocol Info
>     15 6.103011    100.100.100.246         100.100.100.239         SIP      Request: ACK sip:005622408196 at 100.100.100.239
>Session Initiation Protocol
>    Request-Line: ACK sip:005622408196 at 100.100.100.239 SIP/2.0
>        Method: ACK
>        Resent Packet: False
>    Message Header
>        Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0
>        f: "cl" <sip:cl at sipvoiss.desa.redvoiss.net>;tag=1587516403
>            SIP Display info: "cl" 
>            SIP from address: sip:cl at sipvoiss.desa.redvoiss.net
>            SIP tag: 1587516403
>        i: <mailto:e94a98aa177e8579e5242a2091c0ac5f at 192.168.1.100>e94a98aa177e8579e5242a2091c0ac5f at 192.168.1.100
>        To: <sip:0299005622408196 at sipvoiss.desa.redvoiss.net>;tag=9146c297a4
>Thanks
> 
>Ricardo.-
>_______________________________________________
>Serusers mailing list
>Serusers at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers



--
Jiri Kuthan            http://iptel.org/~jiri/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ack_full_trace.cap
Type: application/octet-stream
Size: 23341 bytes
Desc: ack_full_trace.cap
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20070328/3d0a4458/attachment.obj>