Open rgarrigue opened 3 years ago
Can you look at the second log file (more verbose) result.json.pjsua
-o,--output <result.json> json result file name, another file suffixed with ".pjsua" will also be created with all the logs from PJ-SIP
The ICE negotiation and TURN is quite verbose. I need to expose authentication password type, in case this is your problem.
acc_cfg.natConfig.turnPasswordType = PJ_STUN_PASSWD_PLAIN; // PJ_STUN_PASSWD_HASHED;
The second log file ".json.pjsua" file is pasted above, the first one ".json" being empty
I'm 100% sure about the password, I made some test using our softphone app, it worked properly
You need to use the latest master, TURN action was added recently This is not the right log file
Once you run ./voip_patrol -p 1234 -c xml/your_test.xml
You will have a file called results.json.pjsua witch will contain all the logs about ICE/TURN
14:05:55.275 pjsua_media.c .Call 0: initializing media..
14:05:55.275 icetp00 ..Creating ICE stream transport with 2 component(s)
14:05:55.275 icetp00 ...Comp 1/0: host candidate 192.168.0.111:6965 (tpid=64) added
14:05:55.275 icetp00 ...Comp 1/1: host candidate 192.168.0.132:6965 (tpid=64) added
14:05:55.275 udprel0x55a26c14ccc0 ...TURN client session created
14:05:55.275 udprel0x55a26c14ccc0 ...Resolving 32.117.21.130 with DNS A
14:05:55.275 udprel0x55a26c14ccc0 ...State changed Null --> Resolving
14:05:55.275 icetp00 ...TURN client state changed Null --> Resolving
14:05:55.275 udprel0x55a26c14ccc0 ...State changed Resolving --> Resolved
14:05:55.275 icetp00 ...TURN client state changed Resolving --> Resolved
14:05:55.275 udprel0x55a26c14ccc0 ...Connecting to 32.117.21.130:3678
14:05:55.275 udprel0x55a26c14ccc0 ...State changed Resolved --> Allocating
14:05:55.275 icetp00 ...TURN client state changed Resolved --> Allocating
14:05:55.276 udprel0x55a26c14ccc0 ....TX 52 bytes STUN message to 32.117.21.130:3678:
--- begin STUN message ---
STUN Allocate request
Hdr: length=32, magic=2112a442, tsx_id=000018d74fe5af045b39d0d4
Attributes:
REQUESTED-TRANSPORT: length=4, value=285212672 (0x11000000)
SOFTWARE: length=17, value="pjnath-2.10.0-dev"
--- end of STUN message ---
So, I cloned the repo, built the container (build_image.sh), then run it with the above mentioned turn configuration, no mention of STUN / TURN / ICE in the logs again.
Can you c/c your conf.xml file producing your log ?
build_image.sh
will run docker build
using the Dockerfile
, it was building the previous tag 0.2.5
I just made a patch release to 0.2.7
I also added the parameter password_hashed
defaulting to plain.
I will also update the image in the public docker repo.
You can test again after pulling from master.
Hi there
I'm interested in using voip_patrol to test a high availability TURN setup (using coturn). How can I test that ? Tried a naive
/git/voip_patrol/voip_patrol -c ./test.xml -o result.json
with this test.xmlNote, I intend turn.test to answer at least 2 IPs, this is what I meant by high availability
The output said
result.json is empty, result.json.pjsua says
As I said, I tried the naive way, I guess I need some more configuration. Could you provide me some guidance about how to setup a meaningful test ? The best would be a call over the TURN, dunno if there is an easy setup to achieve that, like a mock server ?