Upgraded my test environment to the latest 4.4,
all works OK now, so this GRUU-some problem was not XX-8834?!
I will have to schedue an emergency upgrade for my prod environment to get
the C40's up and running.
FYI: The C40's are very different from the older MXP3000's, can't say that
I like the whole config etc of the new models.
The camera on the thing is absolutely great though, from superwide to
super tele with 12x zoom.
Paul
----- Forwarded by Paul Scheepens/EPO on 13-05-2011 13:31 -----
> I've tried to create a way to prove the problem and it worked
eventually.
>
> See the attached sipx-network-trace (nice command).
>
> In frame 3 the INVITE comes in, is handled internally and send on.
> In frame 51 the ACK from Tandberg MXP3000 comes in.
> In frame 52 its send to port 5070 (registrar)
> In frame 54 you see the ACK with completely different formatting
> send from 47246 ? to 5060.
> Then from frame 56 to 75 it's looped internally on port 5060 (proxy).
>
> This repeats a few times further on in the trace.
>
> From frame 182 onwards the ACK comes in and is send from different
> ports to 5060.
>
> I am running 4.2.1 at the moment.
>
> Can a GRUU specialist tell me whether this is fixed/fixable in a
> current version (XX-8834 has fix version 4.6)
> or whether another issue applies, or a new one is needed? (I am not
> so GRUU-some:).
>
> Regards, Paul
>
>
>
> [email protected] wrote on 12-05-2011 17:32:10:
>
> > Sorry for the bad formatting, (I can't work with/hate Lotus Notes).
> >
> > I've made a snapshot after putting sipXproxy and sipXregistrar to
> > debug, what files should I look at and what to look for.
> > Or do I need to put other processes in debug mode?
> > What is the real filename of your "ack-misrouted-patch2.xml" file in
> > XX-8834? How can I produce it?
> >
> > [email protected] wrote on 12-05-2011 16:48:43:
> >
> > > On 12 maj 2011, at 15.26, [email protected] wrote:
> > >
> > >> 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 MXP3000 the same happens, the ACK is
eaten.
> > >
> > > The sympton sounds a lot like X-8834. You have to turn on debugging
> > > in sipX and check the messages sent between the sipXproxy and the
> > > sipXregistrar. This is where
> > > I had errors with not correctly replacing the GRUU contact (and then
> > > not correctly routing it).
> > >
> > >> Is this a new problem or is it related to X-8834.
> > >> As said, I don't have any NAT.
> > >
> > > Need more details to make sure, but it sounds related.
> > >
> > > Btw, the issue I'm having now is that the Tandberg E20 negotiates
> > > multiple codecs and that is not working well with my Polycom phone.
> > > So, I need to trigger a hold/resume from
> > > the Tandberg unit in order to reverse SDP Offer/Answer and then
> > > everything works fine... Funny =)
> > >
> > > //Staffan
> > >
> > >
> > >
> > > --
> > > 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 "sipxtrace.pcap" deleted by Paul Scheepens/EPO]
> _______________________________________________
> 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/
