7 Replies Latest reply on Nov 7, 2012 11:45 AM by matt

    FXO offhooked.

    ing_gomez_clevermx New Member

      Good afternoon forum, i have the next issues with the NV7100:

       

      1. FXO unhooked. I have 2 FXO connected to my 7100, i can make phone calls perfectrly, but i have a serious problem when i reciebe a phone call and it is not answered by an extention, because the line keeps in a offhook state. Does enny one has presented this problem?

       

      2. Talking about both FXO lines, how can I make outgoing calls take one or another line? I have configured 2 trunk groups, but there is no difference, because the 7100 takes a line interchangeably

      doesn't matter the prefix or the group.

       

      Thankyou for reading, comments welcome!!

        • Re: FXO offhooked.
          Employee

          ing_gomez_clevermx,

           

          For issue #1 have you tried running the ERL tool on the unit?  You can read detailed instructions on using the ERL tool in this guide: Analog Configuration and Trunk Troubleshooting Guide.  We always recommend running it on any analog line connected to the NetVanta 7100.  If running the ERL tool does not help (please try that first) can you post the results of the following show commands and debugs while recreating the issue:

           

          debug interface fxo

          debug voice verbose

          show run interface fxo 0/1

          show run interface fxo 0/2

          show run voice trunk

          show run voice grouped-trunk

           

          For issue number 2, you can create two separate grouped trunks: one for each FXO interface.  You can then modify the accept template for both trunks to specify which numbers should get routed out each trunk.  Below is a very stripped down example that would send all inbound calls on either trunk to an auto-attendant at extension 8001, route all 7 digit outbound calls to trunk T01 connected to FXO 0/1, and route all 10 digit outbound calls to trunk T02 connected FXO 0/2.  If you want to route outbound calls based on what user is placing the call you can use Source and ANI Based Routing in AOS Voice Products.

           

          !

          voice trunk T01 type analog supervision loop-start

            caller-id

            trunk-number 8001

            connect fxo 0/1

            rtp delay-mode adaptive

            codec-group g711_first

          !

          !

          voice trunk T02 type analog supervision loop-start

            caller-id

            trunk-number 8001

            connect fxo 0/2

            rtp delay-mode adaptive

            codec-group g711_first

          !

          !

          voice grouped-trunk ANALOG_LOCAL

            trunk T01

            accept NXX-XXXX cost 0

          !

          !

          voice grouped-trunk ANALOG_LONG_DISTANCE

            trunk T02

            accept NXX-NXX-XXXX cost 0

          !

           

           

          Thanks,

          Matt

          1 of 1 people found this helpful
          • Re: FXO offhooked.
            ing_gomez_clevermx New Member

            The debugs attached

             

            Message was edited by: matt - removed sensitive information

            • Re: FXO offhooked.
              Employee

              If the ERL results came back as 0 dB there is a problem with the line.  Anything less than 10 dB is unacceptable.  Can you paste in the output of a show interface fxo 0/1 and show interface fxo 0/2 to confirm?

               

              Thanks,

              Matt

              • Re: FXO offhooked.
                Employee

                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,
                Matt