USERNAME in PJNATH Stun request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



*>From: Sean Bright <sean@xxxxxxxxxxxxx <sean at malleable.com>>*
*>To: pjsip list <pjsip at lists.pjsip.org <pjsip at lists.pjsip.org>>*
*>Subject: Re: USERNAME in PJNATH Stun request*
*>Message-ID: <547DD310.9040700 at malleable.com
<547DD310.9040700 at malleable.com>>*
*>Content-Type: text/plain; charset=windows-1252; format=flowed*

*>On 12/2/2014 9:36 AM, Jose Luis Benitez Crespo wrote:*
*>> I'm running an Asterisk 12 with STUN and Username in STUN Message does*
*>> not conform to RFC, being 49 chars when its length should be 4 chars*
*>> multiple.*

*>This was a bug in the Asterisk STUN implementation which has already*
*>been resolved in the Asterisk 12 branch:*


Thank you Sean,

I've patched the stun.c file but the problem is still there. I thought that
pjsip uses pjnath which is the ICE protocol responsible (and STUN
implementation, messages, etc). As you can see in this log, SOFTWARE
attribute indicates pjnath-2.3.0 and USERNAME its a nonsense string that I
don't know where can I change it. PASSWORD attribute is not present,
too...I think the problem is the fact that USERNAME is present but I
haven't found nothing related to definition of this attribute or where can
I define it.

I'm trying to make a WebRTC call using chan_sip stack, don't know if this
could be the problem...

[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         icess0x7f50c40
Starting checklist periodic check
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         icess0x7f50c40
.Sending connectivity check for check 4: [1] 192.168.253.151:14752-->
192.168.1.36:0
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         stuse0x7f50c40
...TX 144 bytes STUN message to 192.168.1.36:0:
--- begin STUN message ---
STUN Binding request
 Hdr: length=124, magic=2112a442, tsx_id=00001c9056d008ac624498dc
 Attributes:
  PRIORITY: length=4, value=1862270975 (0x6effffff)
  ICE-CONTROLLED: length=8, data=6066c6d40e2b7f04
  SOFTWARE: length=12, value="pjnath-2.3.0"
  USERNAME: length=49,
value="jHtaC7/mvnmSDIC7:40f98f2117ee183d327ae2862bb2fbf0"
  MESSAGE-INTEGRITY: length=20,
data=47f537629c9d5c84a5ceb5c582c138e0b706abad
  FINGERPRINT: length=4, value=898782782 (0x3592563e)
--- end of STUN message ---

[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         utsx0x7f50cc00
...STUN client transaction created
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         utsx0x7f50cc00
...STUN sending message (transmit count=1)
*[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         utsx0x7f50cc00
....STUN error sending message: Invalid argument*
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         stun_session.c
...tdata 0x7f50cc003558 destroy request, force=0, tsx=0x7f50cc003730
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         utsx0x7f50cc00
...STUN transaction 0x7f50cc003730 schedule destroy
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         stuse0x7f50c40
...Error sending STUN request: Invalid argument
[2014-12-02 17:41:26] ERROR[7348]: pjsip:0 <?>:         icess0x7f50c40
..Error sending STUN request: Invalid argument
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         utsx0x7f50c403 STUN
sending message (transmit count=2)
[2014-12-02 17:41:26] DEBUG[7348]: pjsip:0 <?>:         utsx0x7f50cc00 STUN
sending message (transmit count=2)

Many thanks.

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20141202/a40ee8c7/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux