ISDN calls are not going out trough an other PBX any more

[Hamid2018]

thread965-1739382

Dears
Hi
I have a Openscape 4000 V7 and all out going calls are through a E1 link to a Panasonic TDE-600 temporary.
we have been asked to configure an E1 link to ISDN network (to separate the Openscape ISDN calls from Panasonic) to test the ISDN network and ISDN network did not work properly so we decided to rule back.
this was the original kndef:

ADD-KNDEF:1-1-101,OWN,,,,,EXT,,,,,EXT,,,,,,,;
CHANGE-KNDEF:1-1-101,,,,,,,,,,,,,,Y,,,0;
ADD-KNDEF:1-1-1,OWN,,,,,EXT,,,,,EXT,,,,,,,;
CHANGE-KNDEF:1-1-1,,,,,,,,,,,,,,,,,0;
ADD-KNDEF:0-0-0,FOREIGN,,,,,EXT,,,,,EXT,,,,,,,;
CHANGE-KNDEF:0-0-0,,,,,,,,,,,,,,,,,0;

and 1-1-101 is used in all trunk modules and stations and also zand ALLDATA , PNNO.

I inserted the following line in process of test:
ADD-KNDEF:NNO=1-1-101,TYPE=OWN,ISDNCC=0,ISDNAC=0,ISDNLC=2555,ISDNSK=4,ISDNUL=EXT,PNPUL=EXT;

but now all calls to panasonic are working properly except ISDN calls.

how should I rule back the command.

I monitored all trunk ports and no call is being logged for an ISDN call but other calls are going OK.

 

[thepfy]

Suspect it could be a Trunk to Trunk allow issue.

 

[Moriendi]

I don't think so. I might be wrong but....

...it sounds like the 4K had a TDCSU to Panasonic. Panasonic received all outgoing traffic from 4K, both for the Panasonic and ISDN CO.

Now a CO has been added directly to the 4K, but it didn't work. They made some changes including to KNDEF but it still doesn't work.

They've routed all calls back to Panasonic, but have now found they've broke something. I think, and I'm not 100% sure, that calls to Panasonic are OK, but not out to ISDN CO. Or maybe it's the other way round.

If they've changed KNDEF they will have adjusted the calling line ID for calls to central office, although you can't tell from above if the Panasonic was configured as CO or TIE.

So to put KNDEF back the way it was, try

CHA-KNDEF:1-1-101,*,*,**********,0;

 

[Hamid2018]

Dear Thepfy and Moriendy

thank you for your fast responses.

I tried the command you specified and kndef was still as:
ADD-KNDEF:NNO=1-1-101,TYPE=OWN,ISDNCC=0,ISDNAC=0,ISDNLC=2555,ISDNSK=0,ISDNUL=EXT,PNPUL=EXT;

the problem is solved by changing whole system node number is zand and sdat of all stations and also trunks as needed, and a system reset.

Best Regards

 

[Moriendi]

What was the output of the command?

Completed or Not Completed?

The line I sent works for me, but this is V8.

  <ADD-KNDEF:NNO=1-1-101,TYPE=OWN,ISDNCC=0,ISDNAC=0,ISDNLC=2555,ISDNSK=4,ISDNUL=
EXT,PNPUL=EXT;
ADD-KNDEF:NNO=1-1-101,TYPE=OWN,ISDNCC=0,ISDNAC=0,ISDNLC=2555,ISDNSK=4,
ISDNUL=EXT,PNPUL=EXT;
H500:  AMO KNDEF STARTED
H01: NNO 1-1-101 ADDED

AMO-KNDEF-111       VIRTUAL NODES                                               
ADD COMPLETED;
  <reg-kndef:1-1-101;
REG-KNDEF:1-1-101;
H500:  AMO KNDEF STARTED
ADD-KNDEF:1-1-101,OWN,0,0,2555,4,EXT,           
          ,,,,EXT,,,,,                   
           ,,;
CHANGE-KNDEF: 1-  1-101,,,,,,,,,,,,,, ,,,  0;
H08:  VNR IS NOT CONFIGURED

AMO-KNDEF-111       VIRTUAL NODES                                               
REGENERATE COMPLETED;
  <CHA-KNDEF:1-1-101,*,*,**********,0;
CHA-KNDEF:1-1-101,*,*,**********,0;
H500:  AMO KNDEF STARTED
H06:  PARAMETERS DPLN AND ADPLN HAVE NO EFFECT                                  
      AS THE VIRTUAL DIALING PLAN FEATURE IS NOT ACTIVE.
H02: NNO 1-1-101 CHANGED

AMO-KNDEF-111       VIRTUAL NODES                                               
CHANGE COMPLETED;
  <reg-kndef:1-1-101;
REG-KNDEF:1-1-101;
H500:  AMO KNDEF STARTED
ADD-KNDEF:1-1-101,OWN,,,,,EXT,           
          ,,,,EXT,,,,,                   
           ,,;
CHANGE-KNDEF: 1-  1-101,,,,,,,,,,,,,, ,,,  0;
H08:  VNR IS NOT CONFIGURED

AMO-KNDEF-111       VIRTUAL NODES                                               
REGENERATE COMPLETED;

It may be you have a bug in the older KNDEF AMO.