Yeah,

I tried that as well, I will try again and see. It seems like everything else works.

Just for some reason when I disconnect one leg of the call the BYE messages don't seem to get routed properly.


On 5/21/10 3:56 PM, Daniel Goepp wrote:
I'm not sure what is happening for you there, but I see on my outbound INVITE to the callee:

Via: SIP/2.0/UDP PUBLIC_IP;branch=z9hG4bKa03a.4c4a9294.0;i=e.
Via: SIP/2.0/TCP PRIVATE_IP:5065;rport=6545;received=PUBLIC_IP;branch=z9hG4bK66e33da44ca16500.

I'm also using record_route_preset, are you using this method also?

-dg


On Fri, May 21, 2010 at 11:00 AM, David J. <[email protected] <mailto:[email protected]>> wrote:

    Daniel,

    I am calling fix_nated_register() on REGISTER and on INVITE
    fix_nated_contact()


    On 5/21/10 1:46 PM, Daniel Goepp wrote:
    Ah yes, are you also doing NAT detection and fixing contact?

    -dg


    On Fri, May 21, 2010 at 10:40 AM, David J. <[email protected]
    <mailto:[email protected]>> wrote:

        Yes, I did that, but I am not seeing those changes in the Via
        Tag, although I do see them as Appended if that is the
        correct behavior?

        Via: SIP/2.0/UDP PRIVATE_IP:5061;branch=0;received=PUBLIC_IP.


        On 5/21/10 12:43 PM, Daniel Goepp wrote:
        Did you make the change recommended by Bogdan?

        --clip
        yes, you can set and advertised port and IP to be used
        (instead of the
        actual listening IP:port). See:
           advertise_address
        http://www.opensips.org/Resources/DocsCoreFcn16#toc24
           advertise_port
        http://www.opensips.org/Resources/DocsCoreFcn16#toc25
        --clip

        I am not experiencing the same problem you are.

        -dg


        On Fri, May 21, 2010 at 9:05 AM, David J.
        <[email protected] <mailto:[email protected]>> wrote:

            Daniel,

            You said you got opensips/rtp-proxy working on EC2, when
            testing it, I see the VIA headers have the EC2 internal
            ip and the BYE messages not getting routed correctly,
            any advice on how to solve that?

            Thanks



            On 5/21/10 12:02 PM, Daniel Goepp wrote:
            You need to be careful though because you will likely
            not get media then.  We could not find a way to get
MediaProxy to work, but we did patch rtpproxy to work. We just added a -A parameter which is the publicly
            advertised address.  See:

            
http://opensips-open-sip-server.1449251.n2.nabble.com/Rtpproxy-behind-the-NAT-td5008041.html#none

            -dg


            On Fri, May 21, 2010 at 1:34 AM, Bogdan-Andrei Iancu
            <[email protected]
            <mailto:[email protected]>> wrote:

                Hi Stefano,

                yes, you can set and advertised port and IP to be
                used (instead of the
                actual listening IP:port). See:
                   advertise_address
                http://www.opensips.org/Resources/DocsCoreFcn16#toc24
                   advertise_port
                http://www.opensips.org/Resources/DocsCoreFcn16#toc25

                Regards,
                Bogdan

                Stefano Pisani wrote:
                > I need to put opensips 1.6.2 behind a firewall.
                > In this case the server has an internal IP
                (192.168.x.x)
                > There is a way to configure the extern (public)
                IP in opensis, in this
                > way all the headers of messagges will be correct.
                >
                > stefano
                >
                > _______________________________________________
                > Users mailing list
                > [email protected]
                <mailto:[email protected]>
                >
                http://lists.opensips.org/cgi-bin/mailman/listinfo/users
                >
                >


                --
                Bogdan-Andrei Iancu
                www.voice-system.ro <http://www.voice-system.ro>


                _______________________________________________
                Users mailing list
                [email protected]
                <mailto:[email protected]>
                http://lists.opensips.org/cgi-bin/mailman/listinfo/users



            _______________________________________________
            Users mailing list
            [email protected]  <mailto:[email protected]>
            http://lists.opensips.org/cgi-bin/mailman/listinfo/users


            _______________________________________________
            Users mailing list
            [email protected] <mailto:[email protected]>
            http://lists.opensips.org/cgi-bin/mailman/listinfo/users



        _______________________________________________
        Users mailing list
        [email protected]  <mailto:[email protected]>
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users


        _______________________________________________
        Users mailing list
        [email protected] <mailto:[email protected]>
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users



    _______________________________________________
    Users mailing list
    [email protected]  <mailto:[email protected]>
    http://lists.opensips.org/cgi-bin/mailman/listinfo/users


    _______________________________________________
    Users mailing list
    [email protected] <mailto:[email protected]>
    http://lists.opensips.org/cgi-bin/mailman/listinfo/users



_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to