[reSIProcate] [reTurn-devel] Issues with Turn test client

[Scott Godin]

Hi Jatinder,

The TURN RFC specifies that Turn Allocate requests must be authenticated.
 There is no MessageIntegrity header on the allocate request coming from
nICEr - so it looks like the reTurn server is behaving correctly.

Perhaps nICEr project hasn't implemented authentication yet.  The nICEr
project was contributed a few years back to the resip repository by a
company called Network Resonance (the n and r part surrounding ICE).  I'm
not aware of any anyone active on the forums at this time that have actually
used this code yet - so it may be difficult to track down support/help for
this API right now.

Scott

On Sat, Feb 5, 2011 at 8:27 AM, jatinder goswami <jatinder.goswami at gmail.com
> wrote:

> Hi All,
>
>
> I am running turn test client available in reciprocate (*resiprocate/nICEr/src/stun/test/turn_test_client.c).
> *
>
> Following is is the command which I am running:
>
> *./turn_test_client <TurnServerIP>
> *
> When my turn client sends *"Allocate request"*,  I am observing that
> server responds with error no. 401 *(Error Reason Phrase: Unauthorized (no
> MessageIntegrity)). *
> My client keeps on retransmitting same request and it does not succeed.
> This behavior is also observed in loopback case (running turn test client
> and reTurnServer
> on same machine).
>
> I am attaching the wireshark capture logs for the complete message
> transactions.
> Please share your ideas what could be the issues. Thanks in advance !
>
>
> Regards,
> Jatinder
>
> _______________________________________________
> reTurn-devel mailing list
> reTurn-devel at resiprocate.org
> List Archive: http://resiprocate.org/archive/return-devel/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20110210/f0b32981/attachment.htm>