strange problem calling a remote PBX over PRI TIE trunks

[steve64]

When calling a number programmed on a remote PBX, Opt 11C rel 4.5, from a local phone on a CS1000M MG rel 7.0 connected via PRI TIE trunks we get a fast busy. The problem is that this only occurs on one of the remote PBXs connected to the CS1000M. If a call comes in from the PSTN or another remote PBX and only routes through the CS1000M the calls complete properly. The RDBs, CDP, RLB entries have all been checked and verified. A line by line comparison between the malfunctioning Route and a properly working Route has been done with no differences found except for those that should be different. Test calls have been made from several telephones programmed in different groups on the CS1000M with the same results. Incomming calls from the "bad" site all work properly. Has anyone ever seen something like this or have any ideas?

 

[Tman45]

For me you will need to print the phones you are trying to call and the digits dialed and at what point in dialing you receive the fast busy. Could be a NARS/BARS issue or DSP issue perhaps ...
Just seems we need more info to try to troubleshoot your issue.

 

[steve64]

The reorder busy is immediate after the 5th digit, (we use 5 digit internal numbers). The numbers for the site are in CDP as DSC entries as are the dns for the other sites that work. If I place a call from our main PBX, another CS1000M MG the the "problem site" we insert a "9" so we send 9+xxxxx to the other CS1000M. That PBX strips the "9" and attempts to send the xxxxx to the remote Opt 11C. The call completes properly. The same is true if I place a call to the remote Opt11C from my cell. If I place the call from any set programmed on the CS1000M that has the TIE trinks to the 11C it fails. Doing an ENTC for a phone on the CS1000M making a call the origin and destination numbers appear correctly but instead of connecting to one of the TIE trunks I just shows "reorder". If a call is placed to another 11C off of that CS1000M the call is sent to trunk. The problem exist for all DNs on the problem 11C. The bottom line is that any phone in our system can call the 11C except phones programmed on the CS1000M that feeds has the TIE trunks to the 11C.

 

[lgjc]

Have you tried dialing the access code to the route then dialing aset at that site thus bypassing any ESN programming ? The set you use to dial the access code must be unrestricted (UNR).

 

[trvlr1]

What happens if you dial the 5 digit number without the 9 in front?

 

[steve64]

If we dial the access code for the Route + the 5 digit dn the call goes through. We do not dial 9+ the internal DN. We have changed the RT (to a PSTN route) in the RLB entry 0 for the RLI and the call goes to the PSTN and we get their message about a non working number or something.

 

[trvlr1]

If you do not have a point to point circuit and you have to send the call to the Telco, you will have to insert the missing numbers in front of the digits you are sending using a DMI.

 

[bhassell2000]

do yiou have a FLEN set on it

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[steve64]

Changing the route was just a test to see if the rlb would even send the call. It does. The circuit is point to point of a private network (Doesn't touch telco or any other carrier). We have tried it both ways with the FLEN none set and set to 5. Like I said before this isn't the only one of these circuits out of this PBX. All of the others work fine and we have verified all of the programming is the same on all of the ckts except for the the circuit specific entries, route, DCH, etc. The PBX and Sig Servers are up to date on their patches. Calls from other PBXs in our network can place calls to the PBX.

 

[trvlr1]

Going back to your original posting. You state calls from the PSTN work ok. Have you tried monitoring one of these calls to see exactly what digits are being sent and then comparing it to the internal calls?
Does the far end really need 5 digits or is it just 4 and the initial digit is a "steering code" to get it to the right route?

 

[abe3]

Are the PRI tie trunks 3VCE?

 

[steve64]

It is not a steering code. We use 5 digit dialing.
Yes we have monitored the output digits and they are correct. The output format is eactly the same as for another site that is configured the same. The far end on but sites are Opt 11C running the same software release, 4.5. One works and the other doesn't.

TIE trunks are VOD. As above one site works and the other doesn't.

 

[lgjc]

If you can call dialing the access code to the route then it is something in your esn programming. I would look at your tgar, ncos and frl settings. It looks like the sets on the cs1000m do not have a high enough ncos to frl setting go out on that tie route.

 

[steve64]

The two TIE routes and trunks to remote opt11Cs are identical in all respects except for the RLIs, Route, and Trunk TN numbers. One site works and the other doesn't. NCOS and FRL are not the problem.

 

[lgjc]

How about the trunks themselves for Tgar and Ncos? The CLS should be DTN and are probably CTD. Could try changing the trunks to UNR in the CLS and see if that makes a difference. You also mentioned Sig Servers. Do you have NRS and is that site registered? Is there entries for routing in the NRS?

 

[steve64]

The trunks in this PBX are all UNR and DTN. There is nor NRS on this PBX The only connection to the remote site is via 1 PRI circuit that works fine from all other PBXs in our system that route through this CS1000M.

 

[SL1M1]

If your using a DMI check the CTYP (CallType) settings maybe

Cheers!!

 

[lgjc]

You can dial the access code to the route and the call goes thru so it seems like something in the programming is stopping it. SLIM1 may be on to something. You must have a DSC programmed on that switch which defines which RLI it will use. The DSC should have the FLEN set to 5. The RLI will tell it what route it will go out on (the PRI ties). You may not need a DMI but I have had in some situations that I had to assign a DMI that did nothing (no deletions or insertions)but it needed the CTYP to be either UKWN or NCHG. Sounds like you have everything right especially if the other PBX's can call to that one going thru your trouble switch. Just kind of grasping here but it may be something to try!

 

[SL1M1]

If its not the DMI CTYP setting
Maybe change to TSC (TrunkSteeringCode)

Cheers!!

 

[djstandridge]

Sometimes when going across ties your route number must be above 90. I have seen this happen in a few instances. I would give that a try.