ISDN PRI pilot number alone not working on hipath 4000 V4

[ashutosh2501]

We are facing an emergency on one of sites.
There are two PRI working with 2 different Pilot numbers and around 700 MSN numbers.
\incoming and outgoing works fine.
suddenly one of the pilot numbers which was routed on attendant console AC-win, stopped landing.
THEn MSN is virtual number for PABX
we found that the 2500 parameters show TIE as type.

\tried deleting, modifying, forwarding .... it repeats the following errors.

WHAT I DOUBT IS THE DAR TIE IS THE CULPRIT. PLEASE ADVISE


log file- 2500 & 2700

------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE |NODE/DIGIT| RESERVED/CONVERT |
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 2186 - 2375 |. .**** ***** **... ..... .*| STN | |
| | | |DESTNO 0 |
| | | |DNNO 10- 10-100*|
| 2376 |. .**** ***** **... ..... .*| STN | R |
| | | |DESTNO 0 |
| | | |DNNO 10- 10-100*|
| 2377 - 2499 |. .**** ***** **... ..... .*| STN | |
| | | |DESTNO 0 |
| | | |DNNO 10- 10-100*|
| 2500 |. .**** ***** **... ..... .*| TIE | |
| 2501 - 2699 |. .**** ***** **... ..... .*| STN | |
| | | |DESTNO 0 |
| | | |DNNO 10- 10-100*|
| 2700 |. ..... *.... ..... ..... ..| ATNDDID | |
| 2700 |. .**** .**** **... ..... .*| STN | |
| | | |DESTNO 0 |
| | | |DNNO 10- 10-100*|



in above log file we found that the 2500 is configured with TIE
and the working Number 2700 is configured with ATNDDID

Que- Who to change this type TIE to ATND

the data for 2099 did 2500 non working with DID

ATNDNO = 2099
DIS-ACSU:2099;
H500: AMO ACSU STARTED
+--------------------------------------------------------------+
| ASSIGNED DATA FOR ATTENDANT TERMINAL |
+----------+------------------------++--------+----------------+
| ATNDNO | 2099 || ACTYPE | ACWMQIP |
| ===== || ATNDGR | 0 |
| --------------------------------- || PEN | 1- 1- 79- 1 |
| SRCGRP | ( 1)|| NNO | 1- 1-100 |
| DPLN | 0 || SPDC1 | 0 |
| COS | 10 || SPDC2 | |
| LCOSV | 1 || LANG | ENG |
| CLASSMRK | G711 EC || EOVR | NO |
| | G729AOPT || SATNDNO| NO |
| PUBNUM | || | |
| TON | || | |
| NPI | || | |
| STNOOOS | || | |
| STNOAPE | || | |
| AMOALTRT | NO || CLUSTID| 0 |
| DMCALLWD | NO || IPCODEC| G711P |
| IPPASSWD | || HMUSIC | 0 |
| CLASSSEC | SECURE || IPADDR |163.157. 31.123 |
+--------------------------------------------------------------+

AMO-ACSU -111 ATTENDANT CONSOLE CONFIGURATION
DISPLAY COMPLETED;

the data for working atnd Console 2098

ATNDNO = 2098
DIS-ACSU:2098;
H500: AMO ACSU STARTED
+--------------------------------------------------------------+
| ASSIGNED DATA FOR ATTENDANT TERMINAL |
+----------+------------------------++--------+----------------+
| ATNDNO | 2098 || ACTYPE | ACWMQIP |
| ===== || ATNDGR | 0 |
| --------------------------------- || PEN | 1- 1- 79- 40 |
| SRCGRP | ( 1)|| NNO | 1- 1-100 |
| DPLN | 0 || SPDC1 | 0 |
| COS | 10 || SPDC2 | |
| LCOSV | 1 || LANG | ENG |
| CLASSMRK | G711 EC || EOVR | NO |
| | G729AOPT || SATNDNO| NO |
| PUBNUM | || | |
| TON | || | |
| NPI | || | |
| STNOOOS | || | |
| STNOAPE | || | |
| AMOALTRT | NO || CLUSTID| 0 |
| DMCALLWD | NO || IPCODEC| G711P |
| IPPASSWD | || HMUSIC | 0 |
| CLASSSEC | SECURE || IPADDR |163.157. 19.110 |
+--------------------------------------------------------------+

AMO-ACSU -111 ATTENDANT CONSOLE CONFIGURATION
DISPLAY COMPLETED;



we have restart the attendance console

REST-DSSUEN,1-1-79-1;
H500: AMO DSSU STARTED
H03: PEN 1-1-79-1 DEACTIVATED, ACTIVATION STARTED
H31: PEN 1-1-79-1 ACTIVATED
CIRCUIT DATA LOADING INITIATED

AMO-DSSU -111 DEVICE SWITCH OF SWITCHING UNIT
RESTART COMPLETED;

 

[Moriendi]

If 2500 was a TIE but routed to a local console, then either you used RERTINT in LDAT to keep the call within the 4K, it went through a back to back trunk, or you sent it to another node which sent it back.

A trace of a failed call would be useful here.

Or check the routing for 2500, see if the trunk it's pointing to is in service.
dis-ldpln:cd,2500;

That will give you an LDPNO.
dis-ldpln:ldp,0,LDPNO;

That will give you an LROUTE
dis-ldat:lcr,LROUTE;

That will give you a TGRP for first choice, maybe a second choice too.
(also look for RERTEINT under LATTR, in which case you need to DIS-LODR:ODRNUM)
dis-buend:TGRP;


In BUEND you will see something like 1-1-49-0, or 1-2-1-0. You get the picture. Display the status of that circuit. Swap the 1,1,49,0 below with whatever you see as the port in BUEND.
dis-sdsu:all,,pen,per3,1,1,49,0;

If you want to delete the 2500 like you mentioned in the other post, you will need to delete the LDPLN that is using it first. You can't delete a TIE code while routes are using it.

An ISDN trace from 4K would really tell you what is happening.

 

[donb01]

If 2500 is supposed to ring in on a console it needs to be DAR of atnddid, atndind or a 3rd one I can't remember without looking. I don't think it could get changed to TIE by accident though. Maybe it is routed to a console at another location that has its own numbering plan?

Just some random thoughts.

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA