unispeech / unimrcp

Open source cross-platform implementation of MRCP protocol
http://www.unimrcp.org
Apache License 2.0
374 stars 165 forks source link

Client error: tport_vsend Invalid argument, nta: INVITE Invalid argument (22) #304

Closed QrFaq closed 2 years ago

QrFaq commented 2 years ago

Hi! I'm trying to connect to the docker with unimrcp-server on a remote machine, and got stuck with an error:

tport_vsend(0x7f3ee0006210): Invalid argument with (s=16 */REMOTEserverPUBLICip:18060)
nta: INVITE (963217549): Invalid argument (22) with */[REMOTEserverPUBLICip]:18060

I did a couple of tests, and here are my results:

Test 1 (remote server connection) Remote Server OS: ubuntu 20.04

Docker launch cmd: docker run --rm -p 16011-16014:16011-16014 -p 11544:11544 -p 11554:11554 -p 18060:18060 -p 18062:18062 -p 16006-16010:16006-16010 -p 18001:18001 -p 15060:15060 -p 14900:14900 -p 10554:10554 TESTIMGNAME

And I'm having the error above at the client side, while docker server has launched properly.

Test 2 Although I did another local test on VM with ubuntu 20.04 (i.e. the client and the server are inside VM):

Server OS VM: ubuntu 20.04

Test 3 Another try was on a local machine without VM: server OS: ubuntu 18.04

As a result I got the same error at the end.

Test 4 The working tests were on localhost only (os 18.04 or 20.04), i.e.

Test 5 After that, I've tried to configure remote docker-server with a client to work via tcp/udp only (expose on build stage, make ports public), and it gave the same error from the title.

Would you mind to tell, is there any way to overcome this issue?

Thanks in advance.

cfg and logs in attachments log_conf.zip client.log server.log

achaloyan commented 2 years ago

Sorry, I am not able to carefully follow all your attempts. Maybe you can get started with the attached artifacts that are known to work. Docker.zip

QrFaq commented 2 years ago

Thx, for a fast response and sharing. I did an additional study of SIP and architecture usability under NAT in details vs. RTSP. So, I should use RTSP in my case, and there is nothing wrong here. I'm closing an issue.