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/
