PRI issue

[BristolD]

I have a system that I moved from one site to another. It is an LSP and everything came back up without issue

I connected the 2 PRI trunks and waited for Colt to bring them online, When the trunks came online I made a successful incoming and outgoing call but within minutes the incoming calls stopped working.

When I do a list trace tac I can see the outgoing call but cannot see anything on incoming.

Colt are insisting that the calls are hitting the PBX and giving a "network out of service". but there is nothing showing on the trace on either trunk. so I keep passing it back to Colt.

If anyone could suggest anything, I am back onsite tomorrow and could do with getting these up and running correctly.
Thanks in advance

Here is colts reply

Here is what I have checked and the results of it. I recommend you contact your PBX equipment on site maintaner to find out why the calls are being rejected.
Traver (route translation from BT - since the range 2077105630 to 2077105699 ) is ported in into Colt with correct porting prefix. Below is the translation output from the transit Node:
>traver tr BTAXT0CRTNGBW 52800302077105630 nt
DIGIT TRANSLATION ROUTES
1 CLTKJLCRT00BW 52800302077105630 ST
2 CLTKJLCRT02BW 52800302077105630 ST
3 CLTMBTCRT00BW 52800302077105630 ST
and on the destination switch:
>traver tr CLTCRTKJL00BW 52800302077105630 nt
DIGIT TRANSLATION ROUTES
1 INTERACT_Q N CDN E164 NA 5630 NIL_NSF BC SPEECH
2 CLTPBLKJL00BW 02077105630 ST
As youc an see it is routed correctly to your trunk INTERACT_Q (contains circuits LON/LON/E1X140233 and LON/LON/E1X140234)
BUT is sent to your PBX equiment NOT as a full number but as only the last 4 digits (this is how this circuits were asked to be presented) so 5630 in the above example.
After our call have been forcing calls to the number and I can see taht the calls presented to the Trunk are increasing, yet they don't get connected as your equipment returns "network out of service" -- see attached screen capture -- to Colt, which in turn forwards this message to the originating calling number (so you hear a fast busy tone)

 

[jimbojimbo]

When posting include your software version and patch release.

You might want to ask the question what type of central office system the vendor is running. This sounds similar to a b/d protocol (service versus restart) issue where the central office switch is a DMS100 or 500 and the DS1s should be protocol D. You may also want to verify the idle code the carrier is expecting.

 

[RedTech443]

Things I usually try.


busy board 001v3 (assuming the pri is on gateway 001 and slot v3)
release board 001v3 (same note as above)
busy port 001v324 (to busy the D channel of the pri/board)
release port 001v324
busy trunk x
release trunk x

Make sure you know what the vendor is sending your for protocol version below is chart. That can be adjusted on change ds1 001v324 (assuming ds1 is gateway 001 module 3 port 24)

'a' = AT&T Custom (4ESS)
'b' = NI2 (5ESS)
'c' = DMX250
'd' = Telecordia

If all else fails reset the gateway, shell into it and type "reset" In the past this has worked for me, when it comes back up, magically the PRI might work.

 

[mattKnight]

Colt will virtually certainly be running ETSI as a protocol - while the advice regarding protocols is valid for other regions, in the UK it's inappropriate. (It is incredibly rare - i.e. I've never seen an ISDN that isn't broadly ETSI compliant - yeah yeah I421 isn't 100%, but its still broadly)

What status do you see for the trunk group, if any are showing OOS/PINS, you need to flip the disable restarts flag on the signal group.

Do you have access to a TREND ISDN tester?

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[BristolD]

Thanks for your replies

I reset everything in order (which I had done on a previous visit) nothing worked until I reset the gateway inbound calls started working.

I presume between my last visit and this one Cold has made a change and it just needed a kick to re sync.

Thanks again