Thank you Marc.
On Thu, Feb 12, 2015 at 11:51 PM, Marc Soda wrote:
> Our config is based on the example config and the WebRTC bits are based on
> Carlos'.
> I've attached the relevant parts. It's pretty heavily customized to our
> specific environment. The main differences are the way that w
Our config is based on the example config and the WebRTC bits are
based on Carlos'.
I've attached the relevant parts. It's pretty heavily customized to our
specific environment. The main differences are the way that we detect a
video call, how we route to our backend servers, and that we send vi
Gentle Reminder !
Thanks
Warm Regds,
Rahul
On Thu, Feb 12, 2015 at 12:13 AM, Rahul MathuR
wrote:
> Thanks guys !
>
> I did further investigation of the Chrome logs and found that... (this is
> really interesting), even though I disabled Video; still JSsip was sending
> video information in the
Thanks guys !
I did further investigation of the Chrome logs and found that... (this is
really interesting), even though I disabled Video; still JSsip was sending
video information in the m & a lines.
The fact that I was trying to call PSTN number made it mandatory to set
video port to '0' in 183
We are in the middle of designing a similar solution with Kamailio and
rtpengine and after some initial problems things are going really well. I
can tell you that we ended up going with SIPjs over JSSip and it handled a
lot of the weird browser specific issues we were having.
I'm not sure about t
Maybe you could include you config also?
On 10 February 2015 at 15:01, Rahul MathuR wrote:
> Hello gents,
>
> I was trying my hands on getting a successful RTCweb call (JSsip, since
> Peter Dunkley mentioned that he's been using JSsip for most of the testing
> scenarios..) to PSTN, making my kam
