Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

10 digit ARS to remote Legend's POTS trunk

Status
Not open for further replies.

cybertheque

Technical User
May 15, 2011
30
US
I am experimenting with two networked Legend R7.0 V10.0 systems
connected with a T1 crossover cable between 100D(CD) cards.
Currently I have UDP set up so that extensions on each system
appear as local extensions on the other system. System A has
one POTS line for use by both systems (System B has none).

I set up ARS on System B to route local and toll (tables 17 and
18) to System A, and on System A the same tables are set up to
route the same kinds of calls to the POTS trunk (and absorb an
additional 9 and two pauses which is necessary as the trunk
is actually just an internal business line on a separate PBX).
Ten digit calls dialed from phones on System A route to the
outside correctly, but ten digit calls dialed from phones on
System B get an oscillating error tone (after being sent across
the PRI connection, as the cards blink amber just before the
tone).

Keep in mind that extension to extension calls in either direction
from one system to the other work correctly.

Looking at the description of setting up ARS for this scenario
in the Rel 7 System Programming Manual shows selections for
dialplan types that don't apply, like 6 digit, 1+7 digit, etc.
Should I be setting up a pattern of UDP routing for the trunks
as if they were extensions, or how should I do this?

Thanks,

Michael
 
It's been a long time since I set one up, but

SYS PROGRAM > LINES/TRUNK > REMOTE ACCESS > NONTIE/TIELINES > RESTRICTIONS

When programming the default COR, change the Calling Restriction option to
unrestricted (the factory setting is outward restricted).

Be sure to download the Legend network reference from the Avaya support site.
 
Thanks for your reply. No luck after making those changes.
The error tone is identical to what is heard when dialing an
invalid extension. I also lowered the FRL value on a few routes
in case that was an issue (which will explain the discrepancy in
the printouts).

Configuration printouts ('all') for both systems are here:

Only what was necessary to network the systems and set up the
extensions and one outside trunk (on system a) has been configured.

Thanks for looking...
 
System B
SYSTEM DEFAULT CLASS OF RESTRICTIONS (TIE)

Restriction : OUTWARD RESTRICTED
ARS Restriction Level: 3
Allowed Lists :
Disallowed Lists :
But this may have been captured before you made changes

AUTOMATIC ROUTE SELECTION



TABLE 18: Default Local Output Table

Pool Absorb Other Digits FRL Call type Start Pattern
1)890- 00 -------------------- 2 BOTH --:-- A
2)---- -- -------------------- - ----- --:-- A
3)---- -- -------------------- - ----- --:-- A
4)---- -- -------------------- - ----- --:-- A
5)---- -- -------------------- - ----- --:-- A
6)---- -- -------------------- - ----- --:-- A

Pool Absorb Other Digits FRL Call type Start Pattern
1)890- 00 9pp----------------- 2 BOTH --:-- B
2)---- -- -------------------- - ----- --:-- B
3)---- -- -------------------- - ----- --:-- B
4)---- -- -------------------- - ----- --:-- B
5)---- -- -------------------- - ----- --:-- B
6)---- -- -------------------- - ----- --:-- B
Put this in your Sub-A settings


 
Thanks, sorry I missed the Sub-A settings - that fixed it.

BTW, what is/are the command chain(s) for this item?:

SYSTEM DEFAULT CLASS OF RESTRICTIONS (TIE)

Restriction : OUTWARD RESTRICTED
ARS Restriction Level: 3
Allowed Lists :
Disallowed Lists :

Even though it's working without changing that, for completeness
it would be good to know.

Thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top