Hi all.
I just tried to replace RTPProxy with RTPEngine. I did the change as I was
getting one-way audio previously. However, one connection seems
inconsistent (One-way audio) sometimes and the other connection does not
actually even ring a bell. I have tried with both devices on the same Wi-Fi
an
Hi All ,
I am not able to take incoming call from a gateways with tls
connection in opensips-1.11.
my config file looks like bellow .
listen=udp:107.170.x.y:5508
listen=tls:107.170.x.y:5063
tls_verify_server = 1
tls_verify_client = 1
tls_require_client_certificate = 0
tls_method = TLSv1
tl
Hi, Sasmita!
Did you follow the WS tutorial[1]? You need to use the
fix_nated_register(); function for REGISTER messages, to overwrite the
contact with the IP&portthe message was received from.
[1] http://www.opensips.org/Documentation/Tutorials-WebSocket-2-2
Best regards,
Răzvan Crainea
Op
I think path is not getting saved in the location table in oepnsips-2.2 but
its getting saved in opensips-1.11 .
Is there any difference saving path in the location table on case of
opensips-2.2 . If yes then what ?
*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3C
Hi All ,
The wss authentication is working now . Thank you for your suggestion
.
But now I am facing another issue . When I am registering a number
from SIPML5 in contact the hostname is somehow "df7jal23ls0d.invalid"
like this . And when I am dialing that number opensips is giving
Sasmita,
I am using the following which works well with sipml5 and sipjs
loadmodule "proto_wss.so"
modparam("proto_wss", "wss_max_msg_chunks", 8)
modparam("tls_mgm", "certificate","/etc/opensips/tls/domain.com.crt")
modparam("tls_mgm", "private_key","/etc/opensips/tls/domain.com.key")
m
Hi All ,
I am running opensips-2.2 with , tls_mgm , proto_tls , proto_wss .
my config look like bellow .
listen=udp:x.x.x.x.:5507
listen=tcp:x.x.x.x:5060
listen=tls:x.x.x.x:5061
listen=wss:x.x.x.x:5062
listen=ws:x.x.x.x:5063
alias="domain.com"
alias="domain.com:5507"
alias="domain.com:50
Thank you so much .
*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
On Tue, Feb 7, 2017 at 2:30 PM, Răzvan Crainea wrote:
> Hi, Sasmita!
>
> Yes, both proto_ws, proto_wss and rtpengine modules are mature enough and
> are ready to use.
>
> Be
Hi, Sasmita!
Yes, both proto_ws, proto_wss and rtpengine modules are mature enough
and are ready to use.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 02/07/2017 10:47 AM, Sasmita Panda wrote:
Hi All ,
I am quite intrested to use opensips-2.2 with rtp
Hi All ,
I am quite intrested to use opensips-2.2 with rtpengine . Is this
working good or there is any open issue till now with this module .
And what about proto_ws and proto_wss . Are these modules working
fine ? Please let me know if any precausion I need to take before using
thi
10 matches
Mail list logo
