3 Replies Latest reply on Oct 19, 2017 12:18 PM by karl_

    TA 908 - command line : media-gateway ip

    karl_ New Member

      Hello, question for your guys. this is related to VoIP,  a TA from a customer feed  IP phones, and it's working well.

      Now we setup tunnel interface in case of wan link failure, Do I need to  put the cli command line : "media-gateway ip " on my tunnel interface ?  this exact same command is on my ethernet interface to reach service provider on which is working well... so I guess I also need this command on my tunnel interface right ?       When wan fiber is UP, no failure on wan side, VoIP is working correctly, but when I shut down the port on the CE of service provider(wan) and I should fall-back on tunnel interface it's not working, tunnel are correctly built , data trafic is working well on tunnel to reach others sites... and  What makes me think this absent command is the bug.... it's because an other site have this command(media-gateway ip loopback 5) on it's tunnel interface and in case of  wan side  failure VoIP is working through tunnel, only difference is  this command.  So Do I'm correct to think that  "media-gateway ip "  cli command must be present ?

       

      Thanks !

        • Re: TA 908 - command line : media-gateway ip
          jayh Hall_of_Fame

          The media-gateway ip command defines the IP address to and from which the device will send voice packets. Where you put it depends on the nature of your failover setup. If you have a loopback interface that is properly routed over both the primary and backup WAN, then specify that loopback as the media-gateway IP on all of the egress interfaces. This has the advantage of keeping SIP registrations and call flows intact when a failover occurs, except for a brief delay as routing to the loopback reconverges.

           

          If, on the other hand, you have two different ISPs with different subnets and you can't maintain the same outside-facing IP address during a failover, then use media-gateway ip primary on both. This means that calls will drop and SIP registrations will need to refresh when a failover occurs (and when it restores). Obviously the other end of the connection must be capable of reaching both the primary and backup IP and not firewalled from either.

           

          With a tunnel, you could use a loopback or the tunnel interface itself provided that the IP assigned to the media gateway is reachable and configured for VoIP on the other side.

           

          Short version: Every outside-facing IP-enabled interface used for voice needs a media-gateway ip statement, either primary if that interface itself is to be used or a loopback if that is to be used.

           

          Inside-facing ones need it as well if there are SIP phones on the inside. If just analog and PRI on the inside, then the WAN side is all you need to worry about.