[OpenSIPS-Users] RTPPRoxy behind NAT
SamyGo
govoiper at gmail.com
Mon Sep 10 13:31:36 CEST 2012
Hi,
Nick what is your NAT type? how is your network topology working !!
BR
Sammy
P.S: The blog only takes care of configurations of RTPproxy with servers on
Public IPs and clients behind NAT using Kamailio - This won't make much
sense here. Also alot of things have evolved in kamailio since I wrote that
post.
On Mon, Sep 10, 2012 at 4:13 PM, Binan AL Halabi <binanalhalabi at yahoo.com>wrote:
> Hi Nick,
> see this link posted by Qasim,
> http://saevolgo.blogspot.com/2012/03/making-rtpproxy-work.html
>
> I like it really, you can read it and adjust it as u need,
>
>
> //Binan
>
> --- On *Mon, 9/10/12, Nick Chang <nick.chang at kland.com.tw>* wrote:
>
>
> From: Nick Chang <nick.chang at kland.com.tw>
> Subject: Re: [OpenSIPS-Users] RTPPRoxy behind NAT
> To: "'OpenSIPS users mailling list'" <users at lists.opensips.org>
> Date: Monday, September 10, 2012, 2:16 AM
>
>
> Dear Binan
>
>
>
> Yes, It’s my setting.
>
>
>
> route[nat_fixups] {
>
> #---- RTP Proxy handling ---#
>
> if (is_method("BYE|CANCEL")) {
>
> unforce_rtp_proxy();
>
> } else if (is_method("INVITE")){
>
> #---- Activates the RTP Proxy for the CALLEE ---#
>
> rtpproxy_offer(“cowf”,”202.55.233.194”);
>
> };
>
> # catch and fix replies
>
> t_on_reply("2");
>
> }
>
>
>
> onreply_route[2] {
>
> #xlog("incoming reply\n");
>
>
>
> #---- Handling of the SDP for the 200 or 183 reply ----#
>
> #---- If behind nat (flags 5 or 6) start RTP Proxy ----#
>
> #---- Activates the RTP Proxy for the CALLER ----#
>
> if ( is_method("INVITE") &&
>
> (isflagset(5) || isbflagset(6)) &&
>
> has_body("application/sdp") ){
>
> rtpproxy_answer(“cowf”,”202.55.233.194”);
>
> }
>
>
>
> #---- If the CALLEE is behind NAT, fix the CONTACT HF ----#
>
> if (isbflagset(6)) {
>
> fix_nated_contact();
>
> search_append('Contact:.*sip:[^>[:cntrl:]]*', ';nat=yes');
>
> }
>
> exit;
>
> }
>
>
>
> Thanks
>
> Nick
>
>
>
> *From:* users-bounces at lists.opensips.org [mailto:
> users-bounces at lists.opensips.org] *On Behalf Of *Binan AL Halabi
> *Sent:* Monday, September 10, 2012 5:12 PM
> *To:* OpenSIPS users mailling list
> *Subject:* Re: [OpenSIPS-Users] RTPPRoxy behind NAT
>
>
>
> Hi Nick,
> and you are setting *rtpproxy_offer()* for Invite right !
>
> //Binan
>
> --- On *Mon, 9/10/12, Nick Chang <nick.chang at kland.com.tw<http://mc/compose?to=nick.chang@kland.com.tw>
> >* wrote:
>
>
> From: Nick Chang <nick.chang at kland.com.tw<http://mc/compose?to=nick.chang@kland.com.tw>
> >
> Subject: Re: [OpenSIPS-Users] RTPPRoxy behind NAT
> To: "'OpenSIPS users mailling list'" <users at lists.opensips.org<http://mc/compose?to=users@lists.opensips.org>
> >
> Date: Monday, September 10, 2012, 2:02 AM
>
> Hi Binan
>
>
>
> But, My problem still it.
>
> It’s not work for this setting.
>
>
>
> Or Do you have any suggest?
>
>
>
> Thanks
>
> Nick
>
>
>
>
>
>
>
> *From:* users-bounces at lists.opensips.org<http://mc/compose?to=users-bounces@lists.opensips.org>[
> mailto:users-bounces at lists.opensips.org<http://mc/compose?to=users-bounces@lists.opensips.org>]
> *On Behalf Of *Binan AL Halabi
> *Sent:* Monday, September 10, 2012 4:57 PM
> *To:* OpenSIPS users mailling list
> *Subject:* Re: [OpenSIPS-Users] RTPPRoxy behind NAT
>
>
>
> Hi Nick,
> thank you too,
>
> //Binan
>
> --- On *Mon, 9/10/12, Nick Chang <nick.chang at kland.com.tw>* wrote:
>
>
> From: Nick Chang <nick.chang at kland.com.tw>
> Subject: Re: [OpenSIPS-Users] RTPPRoxy behind NAT
> To: "'OpenSIPS users mailling list'" <users at lists.opensips.org>
> Date: Monday, September 10, 2012, 1:46 AM
>
> Hello Binan
>
>
>
> force_rtp_proxy do not support opensips 1.8.1. It is old function.
>
>
>
> You can saw this page
> http://www.opensips.org/Resources/DocsMigration163to164
>
>
>
> Now, I setting “rtpproxy_answer("cowf","202.55.233.194")”
>
>
>
> Thanks
>
> Nick
>
>
>
> *From:* users-bounces at lists.opensips.org [
> mailto:users-bounces at lists.opensips.org] *On Behalf Of *Binan AL Halabi
> *Sent:* Monday, September 10, 2012 4:37 PM
> *To:* OpenSIPS users mailling list
> *Subject:* Re: [OpenSIPS-Users] RTPPRoxy behind NAT
>
>
>
> Hi Nick,
> use force_rtp_proxy
> here is the link:
>
> http://www.opensips.org/html/docs/modules/1.4.x/nathelper.html#id271191
>
> //Binan
>
> --- On *Mon, 9/10/12, Nick Chang <nick.chang at kland.com.tw<http://mc/compose?to=nick.chang@kland.com.tw>
> >* wrote:
>
>
> From: Nick Chang <nick.chang at kland.com.tw<http://mc/compose?to=nick.chang@kland.com.tw>
> >
> Subject: [OpenSIPS-Users] RTPPRoxy behind NAT
> To: "'OpenSIPS users mailling list'" <users at lists.opensips.org<http://mc/compose?to=users@lists.opensips.org>
> >
> Date: Monday, September 10, 2012, 1:01 AM
>
> Hello
>
>
>
> My RTPPRoxy and Opensips installed on the same server.
>
> Then It behind a NAT.
>
>
>
> It’s my log. How to change “c=IN IP4 10.1.1.51” to “c=IN IP4 public IP”
>
>
>
> U 2012/09/10 15:57:22.704873 10.1.2.103:5060 -> 111.81.182.252:2151
>
> INVITE sip:0939723377 at 111.81.182.252:2151;line=d210bc79dfd2c52 SIP/2.0.
>
> Record-Route: <sip:202.55.233.194;lr;ftag=3554;did=72b.08b17766>.
>
> Via: SIP/2.0/UDP 202.55.233.194;branch=z9hG4bK6aff.e20d892.0.
>
> Via: SIP/2.0/UDP 10.1.1.51:5060
> ;received=118.163.61.141;rport=40696;branch=z9hG4bK3339.
>
> From: <sip:886988000076 at 202.55.233.194>;tag=3554.
>
> To: <sip:0939723377 at 202.55.233.194>.
>
> Call-ID: 32313.
>
> CSeq: 20 INVITE.
>
> Contact: <sip:886988000076 at 118.163.61.141:40696;nat=yes>.
>
> Content-Type: application/sdp.
>
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO.
>
> Max-Forwards: 69.
>
> User-Agent: Linphone/3.5.2 (eXosip2/3.6.0).
>
> Subject: Phone call.
>
> Content-Length: 337.
>
> .
>
> v=0.
>
> o=886988000076 1752 1752 IN IP4 10.1.1.51.
>
> s=Talk.
>
> c=IN IP4 10.1.1.51.
>
> t=0 0.
>
> m=audio 7078 RTP/AVP 112 111 110 3 0 8 9 101.
>
> a=rtpmap:112 speex/32000.
>
> a=fmtp:112 vbr=on.
>
> a=rtpmap:111 speex/16000.
>
> a=fmtp:111 vbr=on.
>
> a=rtpmap:110 speex/8000.
>
> a=fmtp:110 vbr=on.
>
> a=rtpmap:9 G722/8000.
>
> a=rtpmap:101 telephone-event/8000.
>
> a=fmtp:101 0-11.
>
>
>
> Thanks
>
> Nick
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org <http://mc/compose?to=Users@lists.opensips.org>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org <http://mc/compose?to=Users@lists.opensips.org>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120910/b15cf509/attachment-0001.htm>
More information about the Users
mailing list