Legend R-7 UDP issues 3

[phonesrus]

I have a reconfigured Legend that is in a plant that now has a second switch UDP'd via a fiber T-1 emulation. Both sides are R-7's. The main has POTS Trunking with a PRI ETN link to side "B". The voice mail is in "B".
I can call internally ext to ext from either side and voice mail answers correctly for either side, so the "tie" is working. I have done a "D" channel trace on the PRI using my test set.
The FRL of the PRI tie is set at "0" the route patterns are FRL "2" the users are FRL "3". Outbound Trunk routes on "A" and "B" are FRL "2". Only Default Toll and Local ARS tables are currently used.
I can make outbound calls from the main on the POTS trunks.
I cannot make outbound calls from the "B" side using "A" side trunks. I see the setup message on the "D" channel sending 9 +10 digit number for call (9 inserted in route pattern). As soon as the yellow lamp on the 100D T-1 card lights, indicating a "B" channel siezure I get a "turkeytone" failure on the call. I see a normal "call-clearing" and "disconnect complete" message on the "D" channel when I hang up the phone. There are no "B" side trunks other than the "tie". It appears to be an issue with the "A" side, but I cannot see it, any suggestions?

 

[SYQUEST]

You could check the Feature Reference and the Network Reference documents for examples and descriptions dealing with UDP and Tandem Switching. Those can be downloaded from support.avaya.com.

I would check and verify the Class-of-Restriction settings in the non-local switch. That may provide some clues as to what is not working.

Hope this helps!

....JIM....

 

[phonesrus]

Jim,
I have the documents, and I have ARS, PRI, UDP, and other prints of the configs and have compared them. What bugs me is I cannot see what is wrong, With the fact that switch to switch calls work fine, I am wondering if the Legend is having an issue jumping off a Tie-PRI on to POTS trunks. I have done UDP before sucessfully, but with PRI dialtone. If this was a Definity, I would have been finished 2-days ago.
I did not design the systen, nor install it: I just have to make it work.
Another issue is the operator is at switch "B" so I have to make all lines ring to a Calling group with 1 non-local member to send them to the operator, and seperate groups for each of the fax machines. That's not working like it should either.
So far I have about 20 hours invested, not counting study time

 

[merlinman]

You need to configure REMOTE ACCESS to UNRESTRICTED on Tie Lines and NON-Tie Lines.

Sys Prog > Lines & Trunks > Remote Access > TIE Lines > Restriction > CHANGE IT to UNRESTRICTED


Sys Prog > Lines & Trunks > Remote Access > Non-TIE > Restriction > CHANGE IT to UNRESTRICTED

 

[TouchToneTommy]

Also Loop Start Reliable Disconnect need to be enabled

 

[phonesrus]

MM
I have the Remote Access Tie Lines set to unrestricted, what the reason be for NON-tie to be unrestricted since the systems are co-located, for the local CO Trunks to Pass thru? I will make note of that.

 

[merlinman]

Well, I think I don't know.

I would just be willing to bet that if you change it, it will work.

I am not sure if it sees PRI as NON-Tie or what, but I think it does.

I just looked at my records on one that I implemented a few years ago, and that is the way we set it up.

It's worth a shot.

But I am rather certain that will fix your trouble.

After all, the operation you are trying to do IS A TRUNK TO TRUNK TRANSFER.

 

[phonesrus]

For security purposes, the system applies the default class-of-restriction (COR) calling restrictions that you
assign to all tie (T1-emulated voice or data, or analog) or non-tie (PRI) trunks, ignoring the barrier code requirement setting. If remote users connect to your
system via tandem PRI facilities, the non-tie restrictions apply; otherwise, the tie restrictions apply. You can program both types of COR if needed."

MM, I think you may have a point there, according to the networking doc text above.
Unfortunately I lost many switch docs that I had in a hard drive crash on my laptop a couple of years ago, a couple of "UDP's" included. It is hard to see things when you stare at it for so long.

 

[merlinman]

Hard Drives, they are like RC Model Planes;

It's not a matter of IF they will crash, but WHEN they will crash.

To that point, I am trying to create a BOOTABLE, SOLID STATE HD. (Using an 8GB Compact Flash)

So far, no luck.

I have lost so many things due to HD Crashes.

 

[phonesrus]

MM
Changing the NON-Tie Remote access to un-restricted cured the issue with the outbound from "B" and the inbounds to the faxes. Thanks! (One for my Tek-Tips binder)

However, I have another question. We set TG 70 on "A" to ring to CG 771 with 1 non-local member, the operator (x110)on "B". The PRI trunk appearances were removed from the set (x110) and 8 SA buttons were added, but it appears that only 2 inbound outside calls will appear and ring, a third call receives a busy. We didn't get a chance to do too much testing because the IT guy wanted to go home, he was a bit PO'd that it was taking so long to get this setup working. Any thoughts or suggestions on the matter??

 

[merlinman]

OK, this is just a FIRST BLUSH, FIRE THE IT GUY!

No, No, just kidding....

What kind of SA Buttons were added?

Print & Post the Extension Info & we can figure it out....

(Maybe)

 

[phonesrus]

Not sure on the buttons, they were added by one of the guys I was assisting, I will have to find out or go back (which I need to do, to capture prints anyway) I had to leave to continue work on a dedicated l/d trunk that has been down since about 0700 on Friday, Standard finger pointing going on, plus everyone left for the weekend at the carrier and the lec.