WCS 5.2 (Amazon Firewall + NAT Environment) SIP Connection Error

sangsoo

Member
Hello?
I am configuring SIP functionality on an Amazon public IP.
I installed Asterisk 22.7 (pjsip) on another server to connect between public IPs, but it is failing. (Attached logs)

-----Version info-----
wcs_version=5.2.2309-be82b7474f2bb543491f92db3c7b2ab5bca9d49d
wcs_client_version=2.0.266-0841f86b0a63cabd109750e7f8130ddc3b48824d

After opening the two windows below:
~/client2/examples/demo/sip/phone/phone.html

- Set asterisk pjsip.conf value to register on port 2000
- Call port 2000 from port 1000
- Ring comes in, but call disconnects when Answer is pressed

The connection isn't working as expected, possibly due to firewall and NAT policy mismatches.
After registering, a ring comes in on another extension, and the call disconnects when Answer is pressed.

The SIP logs show DTLS errors. Is this a network issue? (The ports between servers are open.)
It worked fine in another development environment configured the same way, using only internal IPs.

For reference, if I register a softphone and call the same number (1000) using the same method, it connects successfully.

- pjsip.conf ; direct_media=no

Have I configured it incorrectly?
I would appreciate your thoughts.

delete~

The same log is visible in Asterisk.

delete~
 
Last edited:

Max

Administrator
Staff member
Good day.
Seems like the problem is between browser and WCS, not between WCS and Asterisk:
1764719407605.png

This occurs at callee side when incoming call is initiating between WCS and Chrome 140 and above. See this thread.
The issue was fixed in WCS build 5.3.165. Please update and check.
Note that WCS 5.3 branch supports JDK 17 and above only, JDK 21 is recommended. So you should update JDK to 21 before WCS updating.
 

sangsoo

Member
Thank you Max

After updating to 5.3.243, the 8444 website does not loading.
I installed jdk17 version. (JDK 21 didn't work either.)

This is the startup.log. Is it a permission issue?
I did run set-permissions.


Loading now.
It happened because wss.jks was missing after the new installation.
(*Oh, Since build version 245, are not downloading now. - permission denied)
 
Last edited:
Top