2 Replies Latest reply on Apr 7, 2014 9:59 AM by levi

    ip rtp firewall command

    adam.lay New Member

      We recently connected a 6355 to our network to provide failover for our nocc center. Unfortunately, when migrating our nocc over to the 6355 from our Cisco switch we have run into issues with connection on certain programs. We still get access for our Polycom phones and basic network connectivity. Certain programs for our telecommunications side of business fail at certain points including a program called Panorama which is located on its own server. Certain areas can be accessed but over time the connection times out. Looking at some configs I can see that we are missing the command ip rtp firewall-traversal policy-timeout XXX. We have a working 6355 in a different location which I am trying to recreate for this new one. Could anyone tell me if this command may have to do with our issues or maybe something else we are missing.

       

      Thanks,

      Adam

        • Re: ip rtp firewall command
          jayh Hall_of_Fame

          ip rtp firewall-traversal policy-timeout XXX isn't likely to be your problem.  This is used for SIP ALG calls, examining the SDP and setting up NAT traversal parameters for the RTP voice packets. If you are experiencing one-way or no audio on voice calls using NAT through the box then this might be a factor but it won't affect anything other than SIP voice calls.

           

          I would look towards either a spanning-tree problem or possibly a duplex mismatch.  Are there errors, runts, or collisions accumulating on any interfaces?  Are there multiple switches in the network with possible loops, and if so is the spanning-tree configuration consistent and stable?  When there is a failure is it isolated to certain network segments or VLANs?  Can you ping the affected hosts?

           

          Are you using VLANs?  Are there Cisco switches still in the mix using their proprietary ISL encapsulation?

           

          The ISO 7-layer stack is useful as a troubleshooting tool.  Start with physical (are the connectors tight, fiber clean with the right mode jumpers, etc.) and work up the stack. 

          1 of 1 people found this helpful
          • Re: ip rtp firewall command
            levi Employee

            adam.lay:

             

            I went ahead and flagged this post as "Assumed Answered." If any of the responses on this thread assisted you, please mark them as Correct or Helpful as the case may be with the applicable buttons. This will make them visible and help other members of the community find solutions more easily. If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

            Thanks,

             

            Levi