1. Seems you try open url in your browser. Just try to read documentation and add repository to sources.list file on debian system. If you really want to check something using wget - try: wget http://pkg.yeti-switch.org/debian/jessie/dists/stable/Release
2. https://github.com/yeti-switch/yeti-node But our SBC intended to run as part of YETI system. So it is not possible(without patches) build it as standalone system. On 12/25/2015 07:38 PM, Serge S. Yuriev wrote: > 1. http redirects to https and end the same :( > 2. I don't mind to write some scripts if this possible fg w/DSM. But > after reading throughout docs I can't if this ever possible. > Is your product closedsourced or maybe you have some github fork? > > -- > Wbr, Serge via mobile > > 25.12.2015, 16:57, "Dmitry Sinina" <[email protected]>: >> >> 1) Use http instead https(as described in documentation). >> 2) I think SEMS - is excellent platform for developer but not for user. >> >> On 12/25/2015 03:37 PM, Serge S. Yuriev wrote: >> >>> 1. >>> http://pkg-old.yeti-switch.org/debian >>> http://pkg.yeti-switch.org/debian/jessie >>> >>> nevian@rositten:/tmp$ wget --no-check-certificate >>> https://pkg.yeti-switch.org/debian/jessie >>> --2015-12-25 16:33:11-- https://pkg.yeti-switch.org/debian/jessie >>> Resolving pkg.yeti-switch.org (pkg.yeti-switch.org)... >>> 193.186.15.12, 193.186.15.22, 2001:67c:1324:101::12, ... >>> Connecting to pkg.yeti-switch.org >>> (pkg.yeti-switch.org)|193.186.15.12|:443... connected. >>> WARNING: no certificate subject alternative name matches >>> requested host name `pkg.yeti-switch.org'. >>> HTTP request sent, awaiting response... 301 Moved Permanently >>> Location: https://a.onat.edu.ua/admin [following] >>> --2015-12-25 16:33:11-- https://a.onat.edu.ua/admin >>> Resolving a.onat.edu.ua (a.onat.edu.ua)... 193.186.15.12, >>> 193.186.15.22, 2001:67c:1324:101::22, ... >>> Connecting to a.onat.edu.ua (a.onat.edu.ua)|193.186.15.12|:443... >>> connected. >>> HTTP request sent, awaiting response... 403 Forbidden >>> 2015-12-25 16:33:11 ERROR 403: Forbidden. >>> >>> 2. It's pity.. I believe fully opaque SBC is more important, for >>> many of us >>> >>> On 25/12/15 15:46, Dmitry Sinina wrote: >>>> 1) What repo is not accessible? Can you tell more details? >>>> 2) Upstream not interested in our patches, because they mainly >>>> intended for "SBC with routing in SQL". >>>> Additionally we use old SEMS network subsystem(based on epoll, not >>>> libevent) without TCP support. So it is not easy task to merge code >>>> with upstream. >>>> >>>> On 12/25/2015 02:24 PM, Serge S. Yuriev wrote: >>>>> Did you managed to fix your repo? They are not accessible at least >>>>> from Russia. >>>>> Or better would you consider to send patches upstream? >>>>> >>>>> -- >>>>> Wbr, Serge via mobile >>>>> >>>>> 25.12.2015, 14:02, "Dmitry Sinina" <[email protected]>: >>>>>> >>>>>> No. You can't configure local re-invite processing with vanilla SEMS. >>>>>> >>>>>> We had same task and we wrote additional code to do it in our >>>>>> product. >>>>>> >>>>>> On 12/24/2015 06:14 PM, Serge S. Yuriev wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Anyone? >>>>>>> Can we make full opaque media anchoring on SEMS? >>>>>>> >>>>>>> On 04/12/15 20:38, Serge Yuriev wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I try to avoid spamming our peers w/unnecessary traces of >>>>>>>> internal PBX >>>>>>>> F.g >>>>>>>> 1 Invite ->sems >>>>>>>> 2 Sems->peer >>>>>>>> 3 Peer->sems >>>>>>>> 4 ReINVITEs from pbx ->sems >>>>>>>> 5 Bye->sems >>>>>>>> 6 Sems->peer >>>>>>>> >>>>>>>> So I want process ReINVITEs locally (they change only RTP >>>>>>>> source, way of doing hold and transfer within PBX). >>>>>>>> Sems is in RTP proxy mode. >>>>>>>> >>>>>>>> How I can achieve this? >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Sems mailing list >>>>>> [email protected] >>>>>> http://lists.iptel.org/mailman/listinfo/sems >>>>>> >>>> >>> >> >> >> -- -- Regards, Dmitry Sinina _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
