On 29.04.2013, at 15:58, Grant Bagdasarian wrote: > Cool. Thanks! > > Which parameter should be configured to apply this in SEMS?
It is explained in the docs: doc/Readme.sbc.txt. There are a couple of paragraphs on RTP relay. The options you need are: enable_rtprelay=yes rtprelay_msgflags_symmetric_rtp=yes Cheers Raphael. > > -----Original Message----- > From: Raphael Coeffic [mailto:[email protected]] > Sent: Monday, April 29, 2013 3:48 PM > To: Grant Bagdasarian > Cc: [email protected] > Subject: Re: [Sems] SEMS SIP/RTP passthrough > > > On 29.04.2013, at 15:44, Grant Bagdasarian wrote: > >> Hello, >> >> Consider the following architecture: >> >> SUPPLIER ------------- SEMS -------------- KAMAILIO&RTPPROXY >> >> - The supplier sends a SIP INVITE to SEMS. >> - SEMS forwards the INVITE to Kamailio (does not create new call >> leg) >> - Kamailio engages RTP Proxy >> - .... >> >> Outcome: >> - Both signaling and media is sent from the supplier to SEMS >> - SEMS sends its signaling to Kamailio and the media stream to RTP >> Proxy. >> >> What I require here is: >> - SEMS (or the application replacing SEMS) must be able to forward >> SIP messages without creating new call legs >> - Send its signaling to Kamailio and Media to RTP Proxy. >> >> Is this possible? >> >> I don't know if SEMS is the correct application to do this with. If not, any >> suggestions? >> > > No problem, you can configure whether or not RTP proxying should be applied > within SEMS. > You can also force symmetric RTP to be used if you which (some UAs do not > signal it properly). > > Cheers > Raphael. > >> Regards, >> >> Grant >> >> _______________________________________________ >> Sems mailing list >> [email protected] >> http://lists.iptel.org/mailman/listinfo/sems _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
