19 Jul
2013
19 Jul
'13
12:33 a.m.
Richard,
to be frank, I tried Sipwise's distribution of Kamailio (NGCP 2.8). Thanks
for configured distro image as well :) Spending some time with tracing the
config file brought the call stack: ROUTE_INVITE
->...->ROUTE_BRANCH_ACC_RTP. However I've added "sp" flags into
rtpproxy_offer function among other flags into ROUTE_BRANCH_ACC_RTP.
That was the shortest way to figure out how mediaproxy works with media
translation feature J Other reason for using the prepared distro is that
I'm completely new to the Kamailio scripting and there are no other live
examples for mediaproxy-ng usage.
Regarding "s" flag..Hm...Just haven't thought that version of rtpproxy-ng
might be out of date... Seems that I need to compile module from your Git
branch.
/Alexey
2013/7/18 Richard Fuchs <rfuchs(a)sipwise.com>
Hi,
On 07/18/13 08:48, Alexey Rybalko wrote:
Just suggest someone already tried mediaproxy-ng with conversion
RTP/SRTP. Few examples of options' usage
would be very appreciated! May
authors bring them into the tutorial?
E.g. caller invokes RTP/SAVPF profile (SIP over WS), but calle supports
RTP/AVP only. During the simple tests I've put
/rtpproxy_offer("spFRWOCII1-")**/ into the INVITE route. However it
doesn't work as was expected: mediaproxy offers the same SDP for callee.
SIP 488 (Not Acceptable) as a result for caller.
Your usage is correct, but it doesn't seem to match the log lines you
posted (those are for an "answer", not an "offer"). Where exactly did
you
get the module from? Did you perhaps grab an older version, one that
doesn't have the 's' flag implemented yet?
cheers
______________________________**_________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http:/…