Hey Tom,
I just fixed the issue you reported in the email bellow. If you want to
try, it is commit into SVN trunk, 1.0 & 1.1 branches.
Cheers
Raphael.
Tom van der Geer wrote:
Stefan Sayer writes:
Hi,
o Tom van der Geer [05/19/09 08:46]:
Hi,
A quick not of what I've found using SipSpy for debugging my
application. I noticed that SEMS sends the ACKs to a 200 OK (+SDP)
from port 5080 (as configured), but the Via header line reads:
Via: SIP/2.0/UDP 80.95.168.133;branch=z9hG4bKN8OcdaNq
while I expected that it should also specify port 5080 in this line.
All other SIP messages from SEMS have a Via header that reads:
Via: SIP/2.0/UDP 80.95.168.133:5080;branch=z9hG4bKL8OcdaCo
could you verify that the Via in the message on the wire really is
like that? (and could you try running it with -Dstrict.addresses=true ?)
when sipSpy was released, I had this discussion with Elias, and the
result was that parameter... here is the explanation about
-Dstrict.addresses=true :
http://www.wesip.com/mediawiki/index.php/Sipspy_docu
Stefan
I double checked with tcpdump. The Via line in the ACK in response to
a 200 OK + SDP is missing the port specification. In the same dialog
there's another ACK (to a 407 Proxy Authentication Required) but that
ACK has a correct port specification in the Via line. Both ACK packets
are sent from port 5080.
I understand how "-Dstrict.addresses=true" would help in presenting
the dialog correctly in SipSpy, but that was not really a problem
anyway. It's just that I noted this small thing and thought I'd share
this with you in case anybody might run into problems with it. It's
not causing problems for me now.
Thanks for your time!
Regards,
Tom
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
