https//:localhost:8444/ not opening

[Max]

I have two SIP web accounts ,which i call on the single web page its not working, if i open in different pages its working fine....

SIP registration is bound to websocket session. So there should be one websocket session per account. Usually, one session is implemented per one webpage to prevent echo if you calling simultaneously.

 

[SAGARVG]

SIP registration is bound to websocket session. So there should be one websocket session per account. Usually, one session is implemented per one webpage to prevent echo if you calling simultaneously.

Thank you for your reply,,

how we can call two account from single account.....

for example: 1005 SIP Account from web page ....and want to call remote SIP accounts 1002 and 1003

How this can be achieved .....

 

[Max]

how we can call two account from single account.....

for example: 1005 SIP Account from web page ....and want to call remote SIP accounts 1002 and 1003

You can not simultaneously call from the same SIP account to two or more SIP accounts. This is SIP conference case, so you should configure a conferencve at SIP PBX, assing an extension (for exampe 1010) to the conference. Then users 1002, 1003 and 1005 call to the conference, and can talk to each other. Please see details in you SIP PBX documentation.

 

[SAGARVG]

whether we can use dyn dns for public IP as its keep on changing every time....

 

[Max]

whether we can use dyn dns for public IP as its keep on changing every time....

You can set ip parameter to DNS name:

ip=my.cool.domain
ip_local=192.168.1.100

Note that this domain name should be resolvable from WCS host. Also, you cannot use domain name in ip_local parameter because local ports to listen are bound to this address.

 

[SAGARVG]

You can set ip parameter to DNS name:

ip=my.cool.domain
ip_local=192.168.1.100

Note that this domain name should be resolvable from WCS host. Also, you cannot use domain name in ip_local parameter because local ports to listen are bound to this address.

hi

i am getting established status not registered, SSH i updated

 

[Max]

We checked the server. Seems like you're using self signed SSL certificate, so both WCS and SIP BPX claim Cetrtificate Unknown when trying to establish SIP TLS connection

Please use a valid certificate or try to add self signed certificate to Java local storage as described here.

 

[SAGARVG]

We checked the server. Seems like you're using self signed SSL certificate, so both WCS and SIP BPX claim Cetrtificate Unknown when trying to establish SIP TLS connection
View attachment 2939
Please use a valid certificate or try to add self signed certificate to Java local storage as described here.

i get this error, as i installed java14 ,keytool not found

 

[Max]

i get this error, as i installed java14 ,keytool not found

Use full path to run keytool:

sudo /usr/java/jdk-14.0.1/bin/keytool ...

 

[SAGARVG]

Use full path to run keytool:

sudo /usr/java/jdk-14.0.1/bin/keytool ...

while logging in webcall server not secure and proceed option i get, how to make this secure without any prompt ...

 

[Max]

while logging in webcall server not secure and proceed option i get, how to make this secure without any prompt ...

You should buy a valid SSL certificate, then import it via web intefrace as described here.

 

[SAGARVG]

You should buy a valid SSL certificate, then import it via web intefrace as described here.

hello

I imported SSL certificate still i get not secure

 

[Max]

I imported SSL certificate still i get not secure

Please check if you opening a page using domain name for whiccertificate was imported. When opening the same page by IP address Chrome will display it as unsecure.
If you're using domain name, and problem still persists, please provide SSH access to the server using this form

 

[SAGARVG]

Please check if you opening a page using domain name for whiccertificate was imported. When opening the same page by IP address Chrome will display it as unsecure.
If you're using domain name, and problem still persists, please provide SSH access to the server using this form

SSH form updated, domain name updated

 

[Max]

Seems like you've applied certificate from a different domain:

You've imported SSL certificate for domain *.ae, but WCS responds on domain *.com. So you should either import certificate *.com for WCS domain or move domain *.ae to WCS instance.

 

[SAGARVG]

hello ,

how we can we open webcall server on normal 443 port instead of 8443 , so that

domain we enter in webpage it should open webcall server

https://mydomianname

 

[Max]

how we can we open webcall server on normal 443 port instead of 8443 , so that

domain we enter in webpage it should open webcall server

You can change Websocket port with the following parameter

wss.port=443

Or you can setup reverse proxy using Nginx.

 

[SAGARVG]

You can change Websocket port with the following parameter

wss.port=443

Or you can setup reverse proxy using Nginx.

You can change Websocket port with the following parameter

wss.port=443

Or you can setup reverse proxy using Nginx.

Similary for https://domain name:8444 whether we can change it to https://domain name

 

[Max]

Similary for https://domain name:8444 whether we can change it to https://domain name

Use the following parameter

https.port=443

Please note that you cannot set the same port for REST API, web interface etc and websocket port. But, if you set up Nginx as reverse proxy, you can use a different URLs on the same port, for example:

# Websocket
location /wss {
    proxy_set_header Host $host;
    proxy_pass https://localhost:8443;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}
# HTTPS
location / {
    proxy_set_header Host $host;
    proxy_pass https://localhost:8444;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}

In this case, you can use https://domain/[ICODE] for REST API queries and [ICODE]https://domain/wss[ICODE] for websocket connections.

 

[SAGARVG]

Use the following parameter

https.port=443

Please note that you cannot set the same port for REST API, web interface etc and websocket port. But, if you set up Nginx as reverse proxy, you can use a different URLs on the same port, for example:

# Websocket
location /wss {
    proxy_set_header Host $host;
    proxy_pass https://localhost:8443;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}
# HTTPS
location / {
    proxy_set_header Host $host;
    proxy_pass https://localhost:8444;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}

In this case, you can use https://domain/[ICODE] for REST API queries and [ICODE]https://domain/wss[ICODE] for websocket connections.

Use the following parameter

https.port=443

Please note that you cannot set the same port for REST API, web interface etc and websocket port. But, if you set up Nginx as reverse proxy, you can use a different URLs on the same port, for example:

# Websocket
location /wss {
    proxy_set_header Host $host;
    proxy_pass https://localhost:8443;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}
# HTTPS
location / {
    proxy_set_header Host $host;
    proxy_pass https://localhost:8444;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}

In this case, you can use https://domain/[ICODE] for REST API queries and [ICODE]https://domain/wss[ICODE] for websocket connections.

we are not able to register, form has been updated