configuring PRI2 on Opt 81 1

[steve64]

I'm sure there is something I'm missing but I have an opt81 that currently has 4 regular PRI ckts up and working (all MU law). I have been asked to implement an E1 (PRI2) to a local telco. When it was first installed I failed to realize that the local telco was running A law and the voice quality, well there was none but a call could be connected both in comming and out bound. I have changed the Trunks (TIE) to A law and now quality is fine and I can make outgoing calls, well at least to some numbers. That problem I believe is in the telco translations, but now I am not able to receive any incoming calls at all. On an incoming call I see no messages on the D channel monitoring and the from the calling phone line appears to go dead until it times out then I get reorder busy. Anyone have any ideas? I don't know whether this is a telco problem or some I gotcha in the Opt 81. Also when doing a stat on the loop in LD 60 it says clock disabled, is that normal? All of the PRIs indicate "Tracking" which is what I would expect to see. If you have any suggestions I'm will to try most anything that won't take the PRIs off line.

 

[bignose21]

If you are see nothing on the DCH monitoring then the call is not getting to you, so that would be a Telco problem. If you had something wrong on your switch programming you would still see the Incomming Call Setup message. To check your clocking just ssck 0 or ssck 1 (stat system clock) one will be active the other standby and you will see which source loop you are using.

 

[steve64]

The clocks 0 and 1 are working properly clock 0 is active with no errors and clock 1 is standby no errors. The regular PRIs all indicate tracking. The PRI2 is the only one indicating "disable". As for the DCH messages my suspicion was that it was a telco problem, but convencining them of this is going to be a challenge. They also have some number traslation problems as there are many numbers we can even dial out to. Fun in the 3rd world.

 

[bignose21]

This is info for stat loop:


STAT loop Get status of digital loop. Sample output:

AAA TRK LOOP x - BBBB
SERVICE RESTORE: YES/NO
YEL ALM PROCESS: YES/NO
ALARM STATUS: NO ALARM/RED(local) ALARM

Where: AAA may be:
DTI
DTI2
PRI
PRI
TIE
DID
DTI LINK (DTI link loop = DLI)

Where: BBBB may be:
DSBL = Hardware of specified digital loop is disabled
ENBL = Hardware of specified digital loop is enabled
RLBK = Hardware of specified digital loop is in remote loop back mode
DISI PENDING = DSI command is in progress
TRACKING = System clock is tracked to this loop

 

[bignose21]

Sorry rest of that follows on as:

IDLE = Hardware of specified digital loop is idle

When AAA = TIE, IDLE ISPC indicates that the channel is an established

ISPC link ready to be used by any end users having access to the associated ISPC route.

SERVER RCVY = server has not recovered status of DTI LINK loop. Channels will not be allocated for call processing until this status is removed by the server

BUSY = Hardware of specified digital loop is busy

When AAA = TIE, BUSY ISPC indicates that the channel is an
established ISPC link which is used by end users on the PBXs.

When AAA = DID, BUSY ISPC indicates that the ISPC link is established to the Central Office. The status “BUSY” is independent to ISL feature usage of the ISPC link.

MBSY = Hardware of specified digital loop is in make busy mode

When AAA = TIE, MBSY ISPC indicates that the configured ISPC link is one of the following:
a not established yet b established, but the ISL D-channel which controls its usage not established

Where: SERVICE RESTORE may be:
YES = restore service automatically if alarm is removed
NO = loop can only be manually enabled

Where: YEL ALARM PROCESS may be:
YES = Yellow alarm processing is enabled
NO = Yellow alarm processing is disabled

Where: ALARM STATUS may be:
NO ALARM = no alarm active
RED = Red (local) alarm active

 

[marc3lo]

The clock is disable because you can’t have clock reference on PBX on T1 Cards and on E1 Cards it has to be one or the other. If your DCH is establish you should talk to the Telco and say that you can receive calls, I don’t know where you are installing the service, but some carriers need to do some route changes to you be able to receive calls.

 

[steve64]

marc3lo you have said what I suspected that clocking on either T! or E1 cards is mutualy exclusive. We have 5 PRI/T1s connected via satellite and the 1 E1 to the local telco. They are using some Chinese switch that no one in the west have ever heard of and couple that with the language barrier and it makes for instant problems. I have the outgoing calls from the PBX working fine and yesterday I deleted all but 1 trunk and made many many incoming calls on the E1. On all but two of the calls I never got the set uo messsage on the DCH. On the two I got the message and everything worked correctly. I am fairly certain they have a routing issue in the CO. They also have routing issues on out going as we can only dial 1 what would be our NXX. All others are rejected. Well if they would ever quit having holidays here I could get them to work on it again. I've worked on straight E1 switches before but this is the first with both E1 and T1.. Learn something now all the time.

 

[steve64]

The CO finally Fixed their problem!