OK, twice sorry, the wiresharks got a hold of me....
Bria does ACK the 200OK, but this never reaches the Tandberg C40, so this 
ACK is definitely eaten by SipX.
Also making a call from an MXP300 the same happens, the ACK is eaten.

Is this a new problem or is it related to X-8834. 
As said, I don't have any NAT.

Paul



----- Forwarded by Paul Scheepens/EPO on 12-05-2011 15:16 -----

[email protected] wrote on 12-05-2011 14:24:03:

> 
> Sorry, the 200OK was tcp ACK-ed but not SIP-ACK-ed by Bria. 
> I will have to dig deeper (the C40 also does not work with a 
> Tandberg MXP3000). 
> 
> Paul 
> ----- Forwarded by Paul Scheepens/EPO on 12-05-2011 14:21 ----- 
> 
> [email protected] wrote on 12-05-2011 14:11:38:
> 
> 
> > Hi Staffan, 
> > 
> > My C40 is not behind NAT, still does not work. 
> > The 200OK is simply not ACK-ed. 
> > The 200OK makes it to the other side (Bria) and is ACK-ed so Bria is
> > sending audio and video. 
> > The C40 shows it's accepting Audio and Video in its STATUS screen, 
> > but it's not sending anything (because the ACK is not received). 
> > After 45 seconds the Tandberg drops the call (the Bye that was 
> > 481'ed), this Bye never reaches Bria, who stays in a call. 
> > 
> > This could be a new problem then? 
> > 
> > Paul 
> > 
> 
> > 
> > From: 
> > 
> > Staffan Kerker <[email protected]> 
> > 
> > To: 
> > 
> > Discussion list for users of sipXecs software <sipx-
> [email protected]> 
> > 
> > Date: 
> > 
> > 12-05-2011 13:56 
> > 
> > Subject: 
> > 
> > Re: [sipx-users] Tandberg GRUU problem 
> > 
> > Sent by: 
> > 
> > [email protected] 
> > 
> > 
> > 
> > 
> > 
> > Hi, 
> > 
> > My work-around is to make sure that the Tandberg endpoint is on a 
> > non-NAT:ed access. Without NAT 
> > at least in my basic scenarios the Tandberg E20 seems to work. 
> > 
> > I tried getting Tandberg to include an option to disable GRUU, but 
> > haven't seen it yet. 
> > 
> > //Staffan 
> > 
> > 
> > 
> > 
> > On 12 maj 2011, at 13.51, [email protected] wrote: 
> > 
> > I've got a Tandberg C40 codec and as it seems I have issues with GRUU. 

> > I don't use NAT or anything. 
> > 
> > I think http://track.sipfoundry.org/browse/XX-8834  will fully fix 
> > the GRUU problem. 
> > In the mean time it would be nice if we could get this beast to 
> workproperly.
> > 
> > Does anybody (Staffan..) know a trick to make it work. 
> > Is there an emergency patch for 4.2.1/4.4? 
> > 
> > Attached the SIP part of the conversation (i left out most of the 
> > RTP traffic). 
> > The 200OK (frames 8, 13, 18 etc) is not ACK-ed, the C40 keeps trying. 
> > In the end (frame 45) the C40 sends a Bye which is answered with a 
> > "481 Call/transaction does not exist". 
> > 
> > Paul 
> > 
> > 
> > 
> > <SIPpart.pcap>_______________________________________________
> > sipx-users mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipx-users/ 
> > 
> > -- 
> > Staffan Kerker 
> > mail/sip/xmpp: [email protected] 
> > 
> > "Don't get involved in politics man, just play the gig..." /Sgt 
> > Floyd, Electric Mayhem Band 
> > 
> > 
> > 
> > _______________________________________________
> > sipx-users mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipx-users/ 
> > _______________________________________________
> > sipx-users mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/

Attachment: BriACK.pcap
Description: Binary data

Attachment: MXP3000-sip.cap
Description: Binary data

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to