[Spce-user] webRTC in production

[Nikita Stashkov]

This is Apple mail. It changed ‘’ to ». I can do nothing wit it.
> 23 нояб. 2014 г., в 10:49, Nikita Stashkov <snl at sipmobile.org> написал(а):
> 
> Sorry, I can not share my script.
> What can you do.
> Look the script /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2
> Of course, before modifying copy it to proxy.cfg.customtt.tt2
> I think, webrtc endpoint automatic detection is not working for you.
> It must look like this:
> 
> if($(ru{uri.param,transport}) == "ws" || $(ru{uri.param,transport}) == "wss»)
> 
> Then check flags you are sending to rtpengine.
> To call SIP clients you must use flag rtcp-mux-demux
> 
> Regards,
> Nikita Stashkov
> 
> 
>> 22 нояб. 2014 г., в 20:28, H Yavari <hyavari at rocketmail.com <mailto:hyavari at rocketmail.com>> написал(а):
>> 
>> Hi,
>> I checked you site. it seems that is a good webRTC solution.
>> Can you share with us your experience to solve our problem? or any script modifications?
>> 
>> 
>> Regards,
>> H.Yavari
>> 
>> From: Nikita Stashkov <snl at sipmobile.org <mailto:snl at sipmobile.org>>
>> 
>> You can try with my site - www.sipmobile.org <http://www.sipmobile.org/>.
>> Create accounts: https://www.sipmobile.org/register/ <https://www.sipmobile.org/register/>
>> And try to call with webRTC client and SIP.
>> I have modified some Kamailio SPCE scripts.
>> 
>> Regards,
>> Nikita Stashkov
>> 
>> 
>>> 22 нояб. 2014 г., в 16:04, Thomas Odorfer <odotom at gmail.com <mailto:odotom at gmail.com>> написал(а):
>>> 
>> 
>> 
>> 
>> Hi,
>> not sure if I understood correctly which scenario works and which not. 
>> So browser to soft phone is now working, but what is the meaning of browser to client? Which client?
>> 
>> I tested myself and I have to confess that I had to do some changes in the account configs for soft phones where I am not happy about.
>> It only worked between browser-webrtc  and soft phone when the corresponding account for the soft phone - nat & media flow control had been changed to "force avp"“ and "force rtp“ ie. no encryption.
>> (I have to investigate that one - could be related to an upgrade I had performed last week - usually srtp should also work with softphones, within the ftp.log there was „SRTP output wanted but no crypto suite was negotiated“).
>> However, after my changes the following tests had been successful:
>> browser webrtc  to  softphone (eg. jitsi,  counterpath x-lite - should be software compatible with eyebeam)
>> browser webrtc to  another browser webrtc (jssip-0.50)
>> browser webrtc to pstn via sip trunking  (standard sip trunk, peer settings for media  force „rtp“, „force rtp“, „always with plain SDP“)
>> 
>> That is based on the latest SPCE version 3.6.1.
>> What does not seem to be achievable at the moment that you can have an account that supports „standard“ and webrtc simultaneously ( at least I haven’t succeeded with such a setup, maybe some sipwise/kamailio/rtpengine  expert knows the trick). And I do not have a solution yet how to share one phone number between two accounts with different profiles.
>> The only solution I have at the moment is that I put a webrtc gateway (similar to webrtc2sip  from doubango) in front of SPCE for webrtc clients.
>> 
>> For your particular problem, maybe you have to check whether your domain settings allow „bypass rtp proxy“ behind the same NAT - assuming you are testing wthin your LAN - this should be set to never.
>> 
>> Good luck
>> Thomas
>> 
>> 
>> Am 22.11.2014 um 12:49 schrieb H Yavari <hyavari at rocketmail.com <mailto:hyavari at rocketmail.com>>:
>> 
>>> Hi,
>>> 
>>> I did this configs:
>>> use_rtpproxy:   „Always with rtpptoxy as only ICE candidate“ 
>>> rtcp_feedback:  „Force AVP“ 
>>> srtp_transcoding:    „Force RTP“
>>> 
>>> now calls between browser to soft phone is ok, but browser to client and browser to browser receive this error "Failed to get local SDP"
>>> and calls not be established. Have you any idea about this situation? 
>>> Thanks for helps.
>>> 
>>> Regards,
>>> H.Yavari
>>> 
>> 
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
>> 
>> 
>> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20141123/0709a4ed/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3903 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20141123/0709a4ed/attachment-0001.p7s>