On Tue, Mar 25, 2008 at 2:22 AM, P.J. Cast. <pjcast at yahoo.com> wrote: > Hello, > > I could find this mentioned on the list specifically, > so figure I am doing something wrong. > > I am trying to setup a jstun server (is there > something better? runs on solaris would be best?) What about http://sourceforge.net/projects/stun ? > using 0.7.1 release (I think latest from Dec). > However, pjsip Stun (a couple month old SVN Rev) > refuses to work with this jstun server. (The jstun > client connects and determines Nat type correctly). On > the server side: > > Jstun dumps out: > de.javawi.jstun.attribute.MessageAttributeException: > Message attribute change request is not set. > at > de.javawi.jstun.test.demo.StunServer$StunServerReceiverThread.run(StunServer.java:114) > > >From a little tracing, I can see first message pjsip > sends out is correct. And jstun sends a response. > Then, the next message is simply 0x000100000000... no > other data, so jstun (seems to) correctly identify a > parsing issue. Note that pjsua sends multiple STUN requests simultaneously on startup (one NAT type checker, one for SIP, and one for each media transports. Each will have different source port) so you need to find out which request triggers the error in JStun. And what you see as 0x010000... packet actually is a valid STUN packet. It is STUN Binding request packet (0x0100 is the method in network byte order) and with other fields set to zero. I don't know what's wrong. Can you capture the packet with Wireshark and find out which STUN request is not responded, and perhaps compare the request with the request sent by jstun client? Cheers Benny > With some other Stun servers, pjsip seems to work > correctly, but not with jstun. Anyone know what > configuration issue I did wrong? I gave it two public > IP addresses, first port 3478, second port 3479. > > Thanks > > > ____________________________________________________________________________________ > Never miss a thing. Make Yahoo your home page. > http://www.yahoo.com/r/hs > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
