On 1 nov 2010, at 08.41, Tony Graziano wrote:
Are you able to build a system from the latest snapshot rpm's to determine
if the issue is resolved up to the point when the gruu is not behind nat?
I did a fresh installation with the latest snapshot (0.0.4.3.2.-ab50055
2010-10-29T20:13:27
Hi Staffan,
Thanks for the effort. I appreciate it. I will find time to review the
logs and get back to the list with my findings.
On Wednesday, 03 November, 2010 07:16 PM, Staffan Kerker wrote:
On 1 nov 2010, at 08.41, Tony Graziano wrote:
Are you able to build a system from the
On 1 nov 2010, at 08.41, Tony Graziano wrote:
Are you able to build a system from the latest snapshot rpm's to determine
if the issue is resolved up to the point when the gruu is not behind nat?
Will try a fresh install on a system and get back to the list with the GRUU/ACK
results.
is looking at getting the patch committed.
--martin
-Original Message-
From: Worley, Dale R (Dale) [mailto:dwor...@avaya.com]
Sent: Monday, October 11, 2010 3:55 PM
To: Staffan Kerker
Cc: Martin Steinmann; 'sipx-users'
Subject: RE: [sipx-users] ACK misrouted in SipXProxy with Tandberg
Cc: 'sipx-users' sipx-users@list.sipfoundry.org
Sent: Mon Nov 01 02:38:59 2010
Subject: Re: [sipx-users] ACK misrouted in SipXProxy with Tandberg
terminal
Hi
Just noticed in the 4.4 testplan,
(https://spreadsheets.google.com/ccc?key=0AuPpSsuc5u0RdHRLajBmUThJQTlqSENaM1FIX1B0RGchl=enauthkey
On 11 okt 2010, at 22.28, Worley, Dale R (Dale) wrote:
That would work, I think, but it might be easier to fix the NAT traversal
problem.
That's off course the best thing to do. =)
/Staffan
--
Staffan Kerker
mail/sip/xmpp: staf...@kerker.se
There is absolutely no money above the 5th
From: Staffan Kerker [ietf-li...@kerker.se]
The patches applied to sipXregistry so far, are they now in the main/devel
branch so that GRUU now and forward on works at least
when remote users are not behind NAT?
I
I think Joegen is looking at getting the patch committed.
--martin
-Original Message-
From: Worley, Dale R (Dale) [mailto:dwor...@avaya.com]
Sent: Monday, October 11, 2010 3:55 PM
To: Staffan Kerker
Cc: Martin Steinmann; 'sipx-users'
Subject: RE: [sipx-users] ACK misrouted in SipXProxy
From: Staffan Kerker [ietf-li...@kerker.se]
Wouldn't it be nice to make GRUU support in SipX a configurable item? At least
giving the admin the possibility
to turn the feature OFF for remote users needing remote NAT traversal?
On 8 okt 2010, at 23.23, Worley, Dale R (Dale) wrote:
Ugh, that's not going to be simple to fix. For the time being, GRUU just
won't work with far-end NAT traversal.
Dale
Wouldn't it be nice to make GRUU support in SipX a configurable item? At least
giving the admin the possibility
to
From: Staffan Kerker [ietf-li...@kerker.se]
Note, this is a slightly different call scenario due to some changes in my
setup, but the problem is the same. The call is initiated from an incoming SIP
trunk, forks to two phones behind NAT, one answers (200
On 6 okt 2010, at 23.45, Worley, Dale R (Dale) wrote:
I now have time to look into this.
Great!
It looks like this is a problem with the remote NAT traversal feature. It's
possible that it isn't specific to GRUU processing. I will talk to our
expert on NAT Traversal.
OK, just let me
From: Staffan Kerker [ietf-li...@kerker.se]
The sipXregistrar now seems to do the right stuff, but now it looks to me as if
the sipXproxy
is messing up the Request-URI and not using the correct one (public IP address)
that is
received from sipXregistry.
Haven't been really following this thread - but...
I did connect to a tandberg device at Bowie, MD without issues - I did have to
use the public IP when dialing - the @domain didn't connect (again, this may
not be at all relevant to the issue at hand)...
This message and any files transmitted
...@avaya.com]
Sent: Wednesday, September 08, 2010 6:21 PM
To: Staffan Kerker; Martin Steinmann
Cc: 'sipx-users'
Subject: RE: [sipx-users] ACK misrouted in SipXProxy with Tandberg
terminal
From: Staffan Kerker [ietf-li...@kerker.se]
Seems like a new
To: Staffan Kerker; Martin Steinmann
Cc: 'sipx-users'
Subject: RE: [sipx-users] ACK misrouted in SipXProxy with Tandberg
terminal
From: Staffan Kerker [ietf-li...@kerker.se]
Seems like a new minor issue happends after this patch is applied. The
ACK is now
From: Staffan Kerker [ietf-li...@kerker.se]
Snapshot linked below:
http://www.kerker.se/files/sipx-snapshot-sipx.kerker.se-patch2.tar.gz
I'm getting a 404 on that URL (at Wed Sep 8 19:25:14 UTC 2010).
Dale
From: Staffan Kerker [ietf-li...@kerker.se]
Seems like a new minor issue happends after this patch is applied. The ACK is
now lost
in the sipxregistrar again.
Yes, the Registrar is not handling Route headers in
:21 PM
To: Staffan Kerker; Martin Steinmann
Cc: 'sipx-users'
Subject: RE: [sipx-users] ACK misrouted in SipXProxy with Tandberg
terminal
From: Staffan Kerker [ietf-li...@kerker.se]
Seems like a new minor issue happends after this patch is applied
On 30 aug 2010, at 04.11, Martin Steinmann wrote:
Staffan
Try this:
http://track.sipfoundry.org/secure/attachment/26604/sipxregistry-4.3.0-01902
2-patch2.sipxbuild.i386.rpm
--martin
Seems like a new minor issue happends after this patch is applied. The ACK is
now lost
in the
From: Staffan Kerker [ietf-li...@kerker.se]
Hopefully better this time... Updated on tracker and on the following link:
http://www.kerker.se/files/sipx-snapshot-sipx.kerker.se-2.tar.gz
OK, the problem there is
On 29 aug 2010, at 20.09, Worley, Dale R (Dale) wrote:
OK, the problem there is that the header parameters in the new target URI
aren't being turned into headers and as a result, the routing is getting
messed up. The attached patch (in addition to the previous one) should fix
that.
)
Sent: Sunday, August 29, 2010 2:09 PM
To: Staffan Kerker
Cc: sipx-users
Subject: Re: [sipx-users] ACK misrouted in SipXProxy with Tandberg
terminal
From: Staffan Kerker [ietf-li...@kerker.se]
Hopefully better this time... Updated on tracker
From: Staffan Kerker [staf...@kerker.se]
The Request-URI in the ACK returned from sipxregistry is still the long
name-addr and not a URI.
However, I've noted that the ACK is different now from the previous trace.
Please see tracefile below (adding
to
On 26 aug 2010, at 18.02, Worley, Dale R (Dale) wrote:
Can you set the proxy and registrar to log at DEBUG level, execute one of
these calls, and then obtain a snapshot (that includes the logs for the call)?
I've uploaded the snapshot to the tracker. You can also download using this
link:
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of Staffan Kerker
[ietf-li...@kerker.se]
http://www.kerker.se/files/sipx-snapshot-sipx.kerker.se.tar.gz
I tried to narrow the snapshot down to the very few
On 24 aug 2010, at 23.37, Martin Steinmann wrote:
I attached an RPM to the issue
I've updated my system with the attached rpm
(sipxregistry-4.3.0-019022.sipxbuild.i386.rpm) but I'm still seeing
the same issue. I updated my entire system using the
'sipxecs-centos-testing.repo' (to version
On 25 aug 2010, at 18.37, Staffan Kerker wrote:
The Request-URI in the ACK returned from sipxregistry is still the long
name-addr and not a URI.
However, I've noted that the ACK is different now from the previous trace.
Please see tracefile below (adding
to tracker as well)
Hi
Ah, sorry, thought I added the data needed...
- No HA system, single install (vmware though, but everything else works fine)
- SipXecs 4.2.1-018932
- Polycom Soundpoint IP 335, v3.2.1 (as delivered)
- I have two aliases set, the FQDN of the SipX server as well as the IP address
of the SipX
In looking at the sip trace, I don't see the IP of the tandberg
(192.168.0.116 at all listed).
I also see a contact at:
sip:~~gr~xpldpp9uhe9bc...@kerker.se;gr;transport=tcp
Does the tandberg register somewhere? What is the contact uri for the
tandberg?
I also am pretty sure that with sipx you
On 24 aug 2010, at 12.16, Tony Graziano wrote:
In looking at the sip trace, I don't see the IP of the tandberg
(192.168.0.116 at all listed).
Frame 24 show the SIP INVITE going from SipXproxy to the Tandberg (behind NAT)
address, 85.24.160.19:43272. You
will see that the SIP Request URI
://www.myitdepartment.net/gethelp/
- Original Message -
From: Staffan Kerker ietf-li...@kerker.se
To: Tony Graziano tgrazi...@myitdepartment.net
Cc: sipx-users sipx-users@list.sipfoundry.org
Sent: Tue Aug 24 07:02:50 2010
Subject: Re: [sipx-users] ACK misrouted in SipXProxy with Tandberg terminal
On 24 aug 2010, at 13.19, Tony Graziano wrote:
The tandberg is not registered to the proxy, correct?
Wrong. Both endpoints (Tandberg/Polycom) are registered to the same
SipXproxy/SipRegistrar on the same SipXecs.
They are both local endpoints, registered on the same AOR (yes, call is
-users] ACK misrouted in SipXProxy with Tandberg terminal
On 24 aug 2010, at 13.19, Tony Graziano wrote:
The tandberg is not registered to the proxy, correct?
Wrong. Both endpoints (Tandberg/Polycom) are registered to the same
SipXproxy/SipRegistrar on the same SipXecs.
They are both local
Are you able to disable GRUU in the tandberg? We had a nasty bug with Aastra
and GRUU and the only fix was to disable GRUU as SipX did not route it
properly. It was a sipx bug.
-M
Staffan Kerker ietf-li...@kerker.se 08/24/10 7:52 AM
On 24 aug 2010, at 13.19, Tony Graziano wrote:
The
On 24 aug 2010, at 15.29, Tony Graziano wrote:
What does the registration look like for the tandberg in sipx?
sip:staf...@kerker.se
sip:staf...@85.24.160.19:43272;transport=tcp;x-sipX-privcontact=192.168.0.116%3A5060%3Btransport%3Dtcp
97 urn:uuid:736346f2-a91a-5fdd-9102-25cb28ddc2cf
Note
On 24 aug 2010, at 15.53, Matt White wrote:
Are you able to disable GRUU in the tandberg? We had a nasty bug with Aastra
and GRUU and the only fix was to disable GRUU as SipX did not route it
properly. It was a sipx bug.
At the moment, no. I'm trying to get Tandberg to give me the
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of Staffan Kerker
[ietf-li...@kerker.se]
See the Sipviewer trace:
http://www.kerker.se/files/tandberg-polycom-ack-misrouted.xml
The sipXproxy.log gives
Can you apply the attached patch and see if it eliminates the problem? (I'm
not in a good position to test the patch myself right now.)
Dale
19049.diff
Description: 19049.diff
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive:
White
Cc: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] ACK misrouted in SipXProxy with Tandberg terminal
On 24 aug 2010, at 15.53, Matt White wrote:
Are you able to disable GRUU in the tandberg? We had a nasty bug with
Aastra and GRUU and the only fix was to disable GRUU as SipX
*From:* sipx-users-boun...@list.sipfoundry.org [mailto:
sipx-users-boun...@list.sipfoundry.org] *On Behalf Of *Staffan Kerker
*Sent:* Tuesday, August 24, 2010 10:33 AM
*To:* Matt White
*Cc:* sipx-users@list.sipfoundry.org
*Subject:* Re: [sipx-users] ACK misrouted in SipXProxy with Tandberg
...@myitdepartment.net]
Sent: Tuesday, August 24, 2010 3:34 PM
To: Martin Steinmann
Cc: Staffan Kerker; Matt White; sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] ACK misrouted in SipXProxy with Tandberg terminal
I think the first one is the primary issue.
http://track.sipfoundry.org
On 24 aug 2010, at 21.45, Martin Steinmann wrote:
From comments on the list and Dale’s patch I would conclude that this is a
sipXecs bug for which we need a new issue to track this.
I created one, http://track.sipfoundry.org/browse/XX-8834.
I haven't tried the patch since I'm using RPMs and
Hi
I've seen this problem before and thought it was GRUU related (see
http://track.sipfoundry.org/browse/XTRN-970) but I now have a similar issue
with another phone.
My Tandberg E20 video terminal fails to establish inbound calls because the ACK
is stuck in the SipXproxy. The GRUU parts look
Is this a HA system?
What version sipx? What version firmware on the polycom phone?
Do you have an IP alias on your sipxsystem (not exactly applicable if a HA
system)? Do you have a user alias of staffan entered in on your account?
On Mon, Aug 23, 2010 at 4:01 PM, Staffan Kerker
45 matches
Mail list logo
