1 Reply Latest reply on May 8, 2013 8:29 AM by patrick

    Remove Redirecting Number from outgoing PRI messages.

    metropark_scott New Member

      this is the scenario. Incoming call is answered by an auto attendant in my SIP phone system using an audiocodes mediant 2000. I dial a users extension (4999). This extension is forwarded to my cell phone. The outbound call is rejected by the telco.

      The system is sending the redirecting number to the audiocodes gateway, which is putting the information in to the PRI messages. The adtran 550 has 2 T1 network boards, network 1 is connected to telco, network 2 is connected to the gateway. it is simply passing calls thru it. I was hoping the Adtran would removed the Redirecting Number message from the PRI messaging. is there anything i can do in the Adtran to get rid of the Redirecting Number in the PRI messages?

      following is a debug captured by the telco, the offending line is in red.

      Thank You

       

       

      Apr  4 10:02:12.781 PDT: %ISDN-6-CONNECT: Interface Serial1/0:1 is now connected to 4261 N/A

      .Apr  4 10:02:14.565 PDT: ISDN Se1/0:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num 5125556033

      .Apr  4 10:02:14.569 PDT: ISDN Se1/0:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Called num 2085554582

      .Apr  4 10:02:14.569 PDT: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8  callref = 0x19A2

              Bearer Capability i = 0x8090A2

      Standard = CCITT

      Transfer Capability = Speech

      Transfer Mode = Circuit

      Transfer Rate = 64 kbit/s

              Channel ID i = 0xA98383

      Exclusive, Channel 3

              Facility i = 0x9F8B0100A115020165020100800D52433320544553542036303333

      Protocol Profile =  Networking Extensions

      0xA115020165020100800D52433320544553542036303333

      Component = Invoke component

      Invoke Id = 101

      Operation = CallingName

      Name Presentation Allowed Extended

      Name = RC3 TEST 6033

              Calling Party Number i = 0x2180, '5125556033'

      Plan:ISDN, Type:National

              Called Party Number i = 0xA1, '2085554582'

      Plan:ISDN, Type:National

      .Apr  4 10:02:14.605 PDT: ISDN Se1/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0x99A2

              Channel ID i = 0xA98383

      Exclusive, Channel 3

      .Apr  4 10:02:14.741 PDT: ISDN Se1/0:23 Q931: RX <- SETUP pd = 8  callref = 0x7913

              Bearer Capability i = 0x9090A2

      Standard = CCITT

      Transfer Capability = 3.1kHz Audio

      Transfer Mode = Circuit

      Transfer Rate = 64 kbit/s

              Channel ID i = 0xA18396

      Preferred, Channel 22

              Facility i = 0x9F8B0100A115020101020100800D52433320544553542036303333

      Protocol Profile =  Networking Extensions

      0xA115020101020100800D52433320544553542036303333

      Component = Invoke component

      Invoke Id = 1

      Operation = CallingName

      Name Presentation Allowed Extended

      Name = RC3 TEST 6033

              Calling Party Number i = 0x80, '2085554581'

      Plan:Unknown, Type:Unknown

              Called Party Number i = 0x80, '13145555976'

      Plan:Unknown, Type:Unknown

              Redirecting Number i = 0x000082, '4999'

      Plan:Unknown, Type:Unknown

      .Apr  4 10:02:14.745 PDT: ISDN Se1/0:23 Q931: extract_redirect_orig_called_ie: IE type redirecting num 4999 reason 2 cnt -1 plan 0 type 0 pres 0

      .Apr  4 10:02:14.773 PDT: ISDN Se1/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0xF913

              Channel ID i = 0xA98396

      Exclusive, Channel 22

      .Apr  4 10:02:14.837 PDT: ISDN Se1/0:23 Q931: RX <- PROGRESS pd = 8  callref = 0x99A2

              Progress Ind i = 0x8088 - In-band info or appropriate now available

      .Apr  4 10:02:14.845 PDT: ISDN Se1/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0xF913

              Cause i = 0x82B9 - Bearer capability not presently authorized

      .Apr  4 10:02:14.881 PDT: ISDN Se1/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x7913

      .Apr  4 10:02:14.885 PDT: ISDN Se1/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0xF913

      .Apr  4 10:02:14.893 PDT: ISDN Se1/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x99A2

              Cause i = 0x8092 - No user responding

      .Apr  4 10:02:14.897 PDT: ISDN Se1/0:23 Q931: TX -> RELEASE pd = 8  callref = 0x19A2

      .Apr  4 10:02:14.905 PDT: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x99A2

        • Re: Remove Redirecting Number from outgoing PRI messages.
          patrick Employee

          Thank you for using the ADTRAN Support Forums.

           

          Technically, the ATLAS does not support the redirecting number field. This information cannot be manipulated by the ATLAS. It is simply passed through. We actually have very little experience with this in the ATLAS. You can try downgrading the Firmware, but I'm afraid I don't have any recommendations. It's possible earlier FW did not pass the redirecting number, but it's not something I've ever tested.

           

          Even if you find a version of FW that does not pass the redirecting number, you will then need the CALLING PARTY NUMBER to be a valid number for the PRI (which I'm assuming it currently is not - but is the original calling party number). Your best solution will be to have the Redirecting Number transmitted as the full 10-digit number, and not the 4-digit extension.

           

          Thank you,

          Patrick