Re: [SR-Users] NO_DTLS_FINGERPRINT when calling from webrtc to webrtc client

2014-09-17 Thread Daniel-Constantin Mierla
On 17/09/14 17:19, Paweł Sternal wrote: Thanks Daniel, you save my day :-) You're welcome! Great to see you ended up with more than expected :-) Cheers, Daniel Two rtpengine solves my problem and works perfect. This solution also adds me the possibility to record calls, when between two rtpe

Re: [SR-Users] NO_DTLS_FINGERPRINT when calling from webrtc to webrtc client

2014-09-17 Thread Paweł Sternal
Thanks Daniel, you save my day :-) Two rtpengine solves my problem and works perfect. This solution also adds me the possibility to record calls, when between two rtpengine instances I will put rtpproxy. Regards, Pawel 2014-09-17 9:35 GMT+02:00 Daniel-Constantin Mierla : > Hello, > > I would add

Re: [SR-Users] NO_DTLS_FINGERPRINT when calling from webrtc to webrtc client

2014-09-17 Thread Daniel-Constantin Mierla
Hello, I would add the RTP-WebRTC gateway between SIP Kamailio and SIP UAC, from resources point of view, it is the only leg that needs encryption/decryption. Otherwise, you can try to work with two rtpengine instances (sets) in WS Kamailio, one to use for ws client to proxy and the other on

[SR-Users] NO_DTLS_FINGERPRINT when calling from webrtc to webrtc client

2014-09-15 Thread Paweł Sternal
Hi. Another topic about WebRTC, websockets with kamailio and rtpengine ;-) My problem is how to distinguish a call to WS UAC and how to SIP UAC in scenarios: 1) WS client1 -> WS kamailio -> SIP kamailio -> SIP UAC 2) WS client1 -> WS kamailio -> SIP kamailio -> WS kamailio -> WS client2 WS k