Situation when using TURN over TCP in pjsua

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

 



Hello,

I am using pjsua Library to use TURN over TCP.. I am using following
related config...

1- STUN is disabled.
2- Turn is enabled with following options.
        media_cfg.enable_turn=true;
        media_cfg.turn_conn_type=PJ_TURN_TP_TCP;
        media_cfg.turn_server=192.168.2.5:5743
        media_cfg.turn_auth_cred.type=PJ_STUN_AUTH_CRED_STATIC;
        media_cfg.turn_auth_cred.data.static_cred.username="test";
        media_cfg.turn_auth_cred.data.static_cred.realm=pj_str("domain.org
");

media_cfg.turn_auth_cred.data.static_cred.data_type=PJ_STUN_PASSWD_PLAIN;
        media_cfg.turn_auth_cred.data.static_cred.data="test;

 My call works with RTP flow both ways through Turn Server but from traces
I see that pjsua sends RTP to 192.168.2.5:5743 (which is Turn server TCP
listen port) . I was under the impression that pjsua will send to the IP
and port received from "Allocate Success" response from Turn server. Though
RTP flow is both ways but i know something is wrong as for each call pjsua
sends RTP to same IP and port !!

What could I be doing wrong?

J. Nash
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20121117/e4a9777b/attachment-0001.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