Re: [OpenSIPStack] STUN support bug?
Brought to you by:
joegenbaclor
Menu
▾
▴
Re: [OpenSIPStack] STUN support bug?
|
From: Ilian J. C. P. <ip...@so...> - 2007-07-25 13:07:11
|
Hi Tom, It works fine in my end. However, you could try moving ATLSIP->InitializeSIP() to void DoLogin() from System::Void Form1_Load. I'm assuming you're using the OSSPhone .NET version. This guarantees that the transport is initialized *AFTER* setting the STUN address. But I'm encountering one-way audio (inbound is silent) with calls using STUN. Logs says I'm in a Port Restricted NAT. I'll still have to check why this is happening. Regards, Ilian Ilian Jeri C. Pinzon wrote: > Hi Tom, > > Thanks for reporting this. I'll have to confirm this first and see > what's wrong. > > Regards, > Ilian > > tomach wrote: > >> Sorry but I do not know whats wrong. I tried to use STUN server. So in OSSPhone I set everthing as it should be: >> Registrar, OutboundProxy and STUN server >> >> then I tried to register and I got no respond from my registrar server. >> >> Using ethereal I sniffed my eth and I noticed that: >> 1. Ossphone sends request to stun. >> 2. Stun answers with this kind of answer. (public address of ossphone is 192.168.2.14 and local is 192.168.44.46): >> >> Simple Traversal of UDP Through NAT >> Message Type: Binding Response (0x0101) >> Message Length: 0x0044 >> Message Transaction ID: 0163E14BE5515702A2407C07C23C6073 >> Attributes >> Attribute: MAPPED-ADDRESS >> Attribute Type: MAPPED-ADDRESS (0x0001) >> Attribute Length: 8 >> Protocol Family: IPv4 (0x0001) >> Port: 50666 >> IP: 192.168.44.46 (192.168.44.46) >> Attribute: SOURCE-ADDRESS >> Attribute Type: SOURCE-ADDRESS (0x0004) >> Attribute Length: 8 >> Protocol Family: IPv4 (0x0001) >> Port: 3478 >> IP: 192.168.44.254 (192.168.44.254) >> Attribute: CHANGED-ADDRESS >> Attribute Type: CHANGED-ADDRESS (0x0005) >> Attribute Length: 8 >> Protocol Family: IPv4 (0x0001) >> Port: 3479 >> IP: 192.168.2.14 (192.168.2.14) >> Attribute: XOR_MAPPED_ADDRESS >> Attribute Type: XOR_MAPPED_ADDRESS (0x8020) >> Attribute Length: 8 >> Protocol Family: IPv4 (0x0001) >> Port (XOR-d): 50313 >> Port: 50666 >> IP (XOR-d): 193.203.205.101 (193.203.205.101) >> IP: 192.168.44.46 (192.168.44.46) >> Attribute: SERVER >> Attribute Type: SERVER (0x8022) >> Attribute Length: 16 >> Server version: Vovida.org 0.96 >> >> 3. Then ossphone sends register message to sipserver. Where Contact and Via headers have incorrect ossphone address. Should be public 192.168.2.14 and there is local 192.168.44.46. >> 4. Sip server does not response because in Contact and Via headers is wrong ossphone address. >> >> Do you have the same behaviour? why Contact field and via arent changed to public in register message? >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> opensipstack-devel mailing list >> ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >> >> >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
