Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • troubleshooting sip trunks

    Hello all,

    I am new to the community here and also to Shoretel.
    Thank you to those who run the site for providing this resource.

    Now, my first question...

    How can I troubleshoot my SIP trunks? Is there a diag interface? A log?

    My VOIP provider is telling me that they are not recieving registrations from Shoretel. I have checked firewall(works fine with a SIP ATA and SIP softphone).

    Me, My shoretel dealer, and my voip provider are all stumped. BTW the VOIP provider uses Asterisk.

  • #2
    Hi,

    U can enable sip debug on that particular Shoregear and it will show u all the SIP messages.

    Comment


    • #3
      Are you using a SIPerator between the Carrier and your Shoretel system? Shoretel SIP does not exactly conform with carrier SIP, which is why you have to add a SIP erator to translate. It's usually issues with SIP REFER, and the like, but if they are not even seeing you, then it maybe a different issue. Is your Firewall allow SIP transversal (SIP aware)?

      Who is the carrier? Maybe somebody else has heard of them, and has similar issues.

      Charles

      Comment


      • #4
        Thanks so much for the replies!

        Ken, how can I enable sip-debug? is it a telnet interface? Do you have a manual for it?


        Charles,

        I am trying to avoid SIPerator. I am using Teliax (www.teliax.com) for VOIP...

        What exactly doesnt work without the ingate? all i have talked to so far are sales people adn they dont really know...


        BTW, I am using a Netscreen 5GT for firewall and have tested via Xten softphone firewall setup.
        Last edited by PhiberOptik957; 05-20-2008, 02:18 PM.

        Comment


        • #5
          ShoreTel's implementation of SIP trunking is fairly limited. With SIP there are often a couple of ways to accomplish the same thing and when a vendor wants to implement SIP they have to decide which "standard" they will use. ShoreTel chose one and uses the InGate devices to translate if the ITSP uses another way.

          The other thing that the InGate devices do is firewall traversal. SIP uses dynamic ports for the RTP and I prefer to have the InGate setup with one interface in a DMZ with a dedicated public IP address and the other in the LAN.

          Comment


          • #6
            Anybody have this info on enabling sip debug???

            Comment


            • #7
              Hi PhiberOptik957,

              I guess your main objective is to decode the SIP messages.
              U can acheive that using a IP sniffer program like ethereal, u might need a ethernet hub or mirror one of the ethernet switch.
              If u want to enable SIP debug on the SG, u can do it via Telnet or the management port.
              They do cover this in the advanced troubleshooting course.
              U will need to "gotoShell".
              Then from the vxworks CLI,

              sip_debug_level=2
              trunk_debug_level=6

              Please use with caution using the vxworks interface, running commands can degrade performance on the switch.

              Comment


              • #8
                just a friendly reminder... when you done with the debugging, set the level back to zero/nomral:
                sip_debug_level=0
                trunk_debug_level=0

                otherwise you SG switch will be flooded with debugging msg.

                Originally posted by Ken View Post
                Hi PhiberOptik957,

                I guess your main objective is to decode the SIP messages.
                U can acheive that using a IP sniffer program like ethereal, u might need a ethernet hub or mirror one of the ethernet switch.
                If u want to enable SIP debug on the SG, u can do it via Telnet or the management port.
                They do cover this in the advanced troubleshooting course.
                U will need to "gotoShell".
                Then from the vxworks CLI,

                sip_debug_level=2
                trunk_debug_level=6

                Please use with caution using the vxworks interface, running commands can degrade performance on the switch.

                Comment

                Working...
                X