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 >> _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
