cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
vjoukov
New Contributor

Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

We are an alarm company and use the PRI to transmit alarm signals to a receiver. When we switch from one ISP to our back up ISP

our ADTRAN doesn't send the right DNIS to the receiver;the Substitution Template is correct and works fine with our primary ISP.)

instead of sending the correct DNIS it sends only one DNIS (which doesn't exist in the template) and it looks like the last 4 digit of the

ISP pilot phone# for this PRI...

So the question is - is there any place in Adtran programing where I have "to enable" the alternate pilot

phone# and associate it with the existing Substitution Template?

Has anyone run into this problem before?

Thanks.

0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

My guess would be that 700-800-9999 (or "800-9999" or even just "9999") is being sent as the DNIS when calls come in from the secondary PRI. Again, you will need to set up some logging (at least set ISDN EVENTS to INFO) to view the number the ATLAS is receiving in the SETUP.

View solution in original post

0 Kudos
12 Replies
jayh
Honored Contributor
Honored Contributor

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

How are the calls coming in to you? Via SIP or via PRI?

How are the calls being delivered to the alarm receiver? Via SIP or PRI?

vjoukov
New Contributor

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

Hi

                                       

Anonymous
Not applicable

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

The substitution template is under the DIAL PLAN and then in the USER TERM, just past the IFCE CONFIG (so it is off-screen when you first look at the USER TERM entries).

You should see the DNIS ORIG # and DNIS SUBST # in here. To add a new entry you highlight one of the line numbers (under the "#") and hit the letter "i" for INSERT. So the ORIGINAL will be the number that is coming in on the PRI, and the SUBSTITUTE is whatever you need it to be when it is sent out to the alarm receiver.

Hope this helps,

Patrick

vjoukov
New Contributor

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

Hi Patrick, thanks for replying.

It is not a problem for me to add the new SUBSTITUTE entry. The problem is: when I switch my PRI from primary ISP to backup all the calls are coming (I can see all of them by the phone## on my SG System III receiver as a blocked), but the SUBSTITUTE doesn't work for all these calls. All of them come with the one DNIS (the only one DNIS for all the incoming calls) not existing in my SUBSTITUTE!

All the same (except the ISP Provider) but it works for the primary and doesn't for the backup....

Anonymous
Not applicable

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

There is nothing that can be done in the ATLAS if all the calls that come from the "backup" provider use the same DNIS. That is handled by the provider. The ATLAS can't change the inbound call it receives.

Under the SYSTEM CONFIG and in EVENT LOGGING, set the ISDN EVENTS to INFO. (If you are familiar with ISDN L2-Formatted messages, and have it set up to send events to a syslog server, you can set these to INFO as well, but they are very verbose so without a syslog server you won't be able to view more than one call at a time in the log.) Then monitor the inbound calls under SYSTEM STATUS in the EVENT LOG. You should see "Call to Atlas:" followed by the the DNIS digits we receive. This is what is sent in the SETUP message. If it is wrong, then you need to discuss this with the provider.

vjoukov
New Contributor

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

Thanks for replying. Still couldn't resolve the issue. May be you can tell me this:

We have 25 Phone## for the our SG receiver and the 25 DNIS for each of these Phone## are programmed

in Adtran:

007.jpg

When we use the backup PRI Adtran sends to SG System III Receiver the DNIS which does not exist! This DNIS

is not programmed in the Adtran at all:

008.jpg

Somehow It sends to Receiver  4 last digits of the  PRI Pilot Phone# as a DNIS

So could you tell me where it is coming from? Why the Adtran sends not programmed DNIS?

Anonymous
Not applicable

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

My guess would be that 700-800-9999 (or "800-9999" or even just "9999") is being sent as the DNIS when calls come in from the secondary PRI. Again, you will need to set up some logging (at least set ISDN EVENTS to INFO) to view the number the ATLAS is receiving in the SETUP.

0 Kudos
vjoukov
New Contributor

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

Thanks Patrick.

I can setup some logging not sure is the right logging or not 😞  ...

Here is an example (of the good PRI)  below please, here is an issue for me - I can read the signal on receiver

(I know the format of the signal) but not the signals in the logged file.

IF you can read it I can run the logging for the PRI which doesn't work for me...

===============================================================

...................................................

4 Recd 0 2

4 Nor     87 Channel:7  

4      83 Numb/Map:NUM

4          Chan. Sel:FO

4          D-Chan Indic

4          Pref/Excl:EX

4                 Intfc ID:IMP

4              A9 Primary Rate

4 Nor L2-Fo IE - 18 CHANNEL ID 

4 Nor L2-Fo M - 02 CALL_PROC    

4 Nor L2-Fo        Prot:08  CRL:2  CRV:9

4 Nor L2-Fo        Ctl:INFO     Ns:17

4 Sent = Sapi:00  C/R:R Tei:00

4 ============================

4 Inf L2-Me Sent  = 00 01 22 08 08 02 99

4 Inf L2-Me Sent  = 02 01 01 08        

4 Inf Calling Name:     

4 IE - 1C FACILITY   

4 87 Channel:7  

4      83 Numb/Map:NUM

6 8

6 8 Description:

6 0 Location:U 

6 IE - 1E PROGRESS IND

6 M - 03 PROGRESS     

6 Prot:08  CRL:2  CRV:9

6 Ctl:INFO     Ns:19  

6 Sent = Sapi:00  C/R:R Tei:00

6 ============================

6 Inf L2-Me Sent  = 00 01 26 0C 08 02 9C

6 Inf L2-Me Sent  = 02 01 01 0C        

6 M - 5A RELEASE_CMP

6        Prot:08  CRL:2  CRV:

6        Ctl:INFO     Ns:5   N

6 Nor L2-Fo Recd = Sapi:00  C/R:C Tei:00

6 Nor L2-Fo ============================

6 Me Recd  = 02 01 0A 26 08 02 03

6 Inf L2-Me Recd  = 00 01 01 26    

6 M - 4D RELEASE   

6 Prot:08  CRL:2  CRV:8

7 C

7 3 Channel:3  

7 3 Numb/Map:NUM

7         Chan. Sel:FO

7          D-Chan Indic

7          Pref/Excl:EX

7          Intfc ID:IMP

7              A9 Primary Rate

7         IE - 18 CHANNEL ID 

7 Nor L2-Fo        M - 02 CALL_PROC    

7 Nor L2-Fo        Prot:08  CRL:2  CRV:8

7 Ctl:INFO     Ns:21

7 Sent = Sapi:00  C/R:R Tei:0

7 ============================

7 Inf L2-Me Sent  = 00 01 2A 0E 08 02 8D

7 Inf L2-Me Sent  = 02 01 01 0E        

7 Fo          Calling Name: T&T S

7 Nor L2-Fo         IE - 1C FACILITY

7       83 Channel:3

7       83 Numb/Map:NUM

E

8 Description:

0 Location:U 

IE - 1E PROGRESS IND

M - 03 PROGRESS     

Prot:08  CRL:2  CRV:9

Ctl:INFO     Ns:22  

Sent = Sapi:00  C/R:R Tei:00

============================

Inf L2-Me Sent  = 00 01 2C 0E 08 02 99

Inf L2-Me Recd  = 00 01 01 2C        

       83 Channel:3

             83 Numb/Map:NUM

                 Chan. Sel:FO

Nor L2-Fo                 D-Chan Indic

Nor L2-Fo                 Pref/Excl:EX

Nor        Intfc ID:IMP

      A9 Primary Rate

IE - 18 CHANNEL ID

M - 02 CALL_PROC    

9 Sent 2 18

9 M - 0F CONNECT_ACK  

9 Prot:08  CRL:2  CRV:0

9 Ctl:INFO     Ns:11  

9 Recd = Sapi:00  C/R:C Tei:00

9 ============================

9 Inf L2-Me Recd  = 02 01 16 36 08 02 03

9 Inf L2-Me Recd  = 00 01 01 36        

9        M - 07 CONNECT      

9 Nor L2-Fo        Prot:08  CRL:2  CRV:8

9 Nor L2-Fo        Ctl:INFO     Ns:26

9 Sent = Sapi:00  C/R:R Tei:00

9 ============================

9 Inf L2-Me Sent  = 00 01 34 16 08 02 83

9 Inf L2-Me Sent  = 02 01 01 16        

9 M - 5A RELEASE_CMP  

9 Prot:08  CRL:2  CRV:1

9 Ctl:INFO     Ns:10  

9 Recd = Sapi:00  C/R:C Tei:00

9 ============================

20 Recd 0 3A

20 5A RELEASE_CMP

20 8

20 28

20 Sent R

20

20 Sent 0 01 38 1A 81

20 Sent 2 1A

20 4D RELEASE

20 0

20 12

20 Recd C

20

20 Recd 2 01 18 38 01

20 Recd 0 38

20       90 Cause:NORMAL

20       80 Location:U 

  IE - 08 CAUSE   

       M - 45 DISCONNECT   

        Prot:08  CRL:2  CRV:8

...................................................

Anonymous
Not applicable

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

I'm afraid these are incomplete messages. The SETUP should have a CALLING PARTY # and a CALLED PARTY # near the bottom of it.

You may have better luck only having ISDN EVENTS set to INFO and everything else set to MINOR. With ISDN EVENTS set to INFO you should see something like "Call to Atlas: 5551111" (or whatever the received DNIS is).

vjoukov
New Contributor

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

Thanks Patrick!

I was looking in the wrong direction! Now I hope I have the right logg (see bellow please) The BOLD text is the Backup PRI, the only one call. (I can't leave the station w/o the signals for the long time),

On my understanding the backup ISP some how replaces the receiver Phone #  with the Pilot #  so when the receiver is trying to call back to panel it takes the Pilot# instead of the Panel Phone#... :

Aug 21 12:25:32  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to ATLAS:'6047398466' from '6047185883'.

Aug 21 12:25:32  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Incoming call to '6047398466' accepted

Aug 21 12:25:32  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Name sent to dest endpoint by FacilityInd

Aug 21 12:25:38  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '6047316816' cleared from ATLAS end

Aug 21 12:25:38  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '6047398466' connected.

Aug 21 12:25:41  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to ATLAS:'6047300542' from '6048827862'.

Aug 21 12:25:41  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Incoming call to '6047300542' accepted

Aug 21 12:25:41  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Name sent to dest endpoint by FacilityInd

Aug 21 12:25:45  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '6047398466' disconnected by far end.

Aug 21 12:25:47  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '6047300542' connected.

Aug 21 12:25:47  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to ATLAS:'6047300542' from '6045745047'.

Aug 21 12:25:47  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Incoming call to '6047300542' accepted

Aug 21 12:25:47  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Name sent to dest endpoint by FacilityInd

Aug 21 12:25:54  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '6047300542' connected.

Aug 21 12:25:55  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '6047300542' cleared from ATLAS end

Aug 21 12:26:02  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '6047300542' disconnected by far end.

Aug 21 12:26:15  192.168.1.205  ATLAS 550 Main[ADTRAN]:T1|Ntw1|1|T1 Yellow Alarm Active

Aug 21 12:26:20  192.168.1.205  ATLAS 550 Main[ADTRAN]:T1|Ntw1|1|T1 Yellow Alarm Cleared

Aug 21 12:26:23  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to ATLAS:'7789451121' from '6048220985'.

Aug 21 12:26:23  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Incoming call to '7789451121' accepted

Aug 21 12:26:29  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '7789451121' connected.

Aug 21 12:26:33  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|Call to '7789451121' cleared from ATLAS end

Aug 21 12:26:53  192.168.1.205  ATLAS 550 Main[ADTRAN]:T1|Ntw1|1|T1 Yellow Alarm Active

Aug 21 12:27:01  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|D channel is DOWN

Aug 21 12:27:08  192.168.1.205  ATLAS 550 Main[ADTRAN]:T1|Ntw1|1|T1 Yellow Alarm Cleared

Aug 21 12:27:12  192.168.1.205  ATLAS 550 Main[ADTRAN]:ISDN|Ntw1|1|D channel is UP

Anonymous
Not applicable

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

I believe that is correct. The Syslog in bold is a call to 7789451121. If this isn't the number the panel dialed, but the pilot number, then it is being changed in the network before reaching the ATLAS.

vjoukov
New Contributor

Re: Switching from Primary PRI to Backup, Losing The Substitution Template

Jump to solution

Thanks a lot Patrick for your help!

Now I have in my hand that what I can show to my ISP to discuss the problem.

Have a great day!