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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to access PRA using remote Tie Trunks ?

Status
Not open for further replies.

golfdoctor

Technical User
Dec 1, 2004
148
CA
The installation of the second networked switch is going well with this forums valueable assistance. Basically installed in the lab I have an Opt 11(c) connected to my main site via H323 virtual Trunks. The main site is an Opt 81 (C). I am using H323 virtual trunks between the sites. Believe it or not the setup works sort of neat. I have everything up and working within reason;(ext to ext, centralized call pilot, centralized attendant) except for the ability of the remote site to utilize the main sites PSTN trunks which are PRA(I). Basically for all PSTN calls I am trying to have the remote site utilize the virtual tie trunks and then use the main sites PRA to access the PSTN world. Trying to leveredge the existing trunks and avoid installing a bunch COT's at the remote site.

I have tried DSC, TSC to access the PSTN network from the remote site however I believe my issue is at the main site. NARS/BARS have been implemented at both sites. I have read that PRA(I's) cannot be accessed via their ACOD and I am becoming a believer! When I check the DCH output at the remote end (Opt 11C)the digit translations are leaving the switch however the call disconnects because no channel is available. I tried the same scenario per say at the main site dialling the ACOD of the outgoing trunk route and tried to call a local NXX and the call also fails.(ACOD+9+nxxyyyy)

Is there a trick to accessing the PRA (I's) from a virtual tie trunk or do I have to think of another option for PSTN access at the remote site?


Any thoughts or suggestions


TGD
 
Is the DCH message arrives at Main site?
If no, NRS make the call to fails. If yes, did you have the AC1 to the outgoing call going through H323?

Give DCH traces for both sites
 
Hi dlesap !

Thanks for replying, you have been right on the money ! I have tried various scenarios however with no luck. I thought if I used the ACOD of the PRI and from the remote end used it as a TSC it should work ? I think the print out seems to say that the NRS is working ?

I tried the ACOD at the main site from the main site and it provides dial tone when the same sequence of digits is entered but even from the main site it will not allow the call to be completed. (ie 7222 9 882 9142)

Any thoughts ?


TGD


REMOTE SITE - Opt 11C

DCH 10 OMSG SETUP REF 000001A0 CH 99 0 0 31 TOD 15:31:26
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:5399 NUM PLAN: E164/SUBSCRIBER (NXX)/LOCL
CALLED #:722298829142 NUM PLAN: E164/SUBSCRIBER (NXX)/LOCL

DCH 10 IMSG CALLPROC REF 000001A0 CH 99 0 0 31 TOD 15:31:26

DCH 10 IMSG DISC REF 000001A0 CH 99 0 0 31 TOD 15:31:26
CAUSE :CALL REJECTED
DIAG: 101
--------------------------------------------------------
---------------------------------------------------------
MAIN SITE opt 81C with PRA


DCH 10 IMSG SETUP REF 00008181 CH 160 0 0 0 TOD 15:31:30
FEAT :NCID
PROGRESS: CALL IS NOT END TO END ISDN
CALLING #:5399 NUM PLAN: E164/SUBSCRIBER (NXX)
CALLED #:722298829142 NUM PLAN: E164/SUBSCRIBER (NXX)

* ERR404 08/05/06 15:31:32 114821
OPRDATA: 0

DCH 10 OMSG REL COMP REF 00008181 CH 160 0 0 0 TOD 15:31:30
CAUSE :CALL REJECTED
DIAG: 101

 
Sure NRS if working. If i understand clearly, from the main site you are not able to dial 7 222 98829142. So the problem is at main site...
What 7 is at your main site? Is it AC1 or AC2?
How the following digits are configured?
Give LD 90 config or LD 87 CDP and LD 86 RLI config also
 
Hi dlesap,

After your first post I started to reevaluate my configuration and the light bulb might have come on.(scary I know) You mentioned is AC1 from the remote site being sent to the H323. It is NOT. The NRS is configured for the digits however they were not being sent from the Opt 11C like the other DSC because AC1 (9) was active in the remote switch. So before I waste your time let me change the remote site(Opt 11C) AC1 which is presently(9)to(8) I tried before but the remote switch would not let me. (said 9 is being used) So what I did at the time without removing AC1 at the remote switch is configure a DMI table to delete the number 9 if entered at the remote site and insert the main site ACOD for the outgoing PRA as a TSC within the remote switch . That is where the number 7222 comes from. (ACOD of outgoing PRA trunk at main site)

I hope if I change AC1 to (8) at the remote switch and enter 9 into the CDP and TSC of the remote switch, hopefully the main switch will recognize the digits. Both sites prior to me doing this were set up with AC1 (9). Neither site uses AC2

I will try this when I get to work tomorrow. If I cannot get PSTN access I will post the info for the main and remote site.

Thanks again for all your help !
 
Well still no luck- I changed the remote site AC1 to 8.
When I checked both ends for DCH action the main site did not receive anything. So I proceeded to add (9) to the NRS in Level 0 and 1 Regional also. Previously the only entries in level 0 were the extension DSC's.(I left the E164 dialling plan for (9)in NRS also) Once I did that it looks like both DCH are talking ?, however I cannot seem to get PSTN access.I have attached both site settings and a copy of the latest dch messages (x2)

Any thoughts ?


TGD
---------------------------------------------
---------------------------------------------
Remote Site - Opt 11C


DCH 10 OMSG SETUP REF 000001A0 CH 99 0 0 31 TOD 7:18:24
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:5399 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)
CALLED #:93107973 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)

DCH 10 IMSG CALLPROC REF 000001A0 CH 99 0 0 31 TOD 7:18:24

DCH 10 IMSG DISC REF 000001A0 CH 99 0 0 31 TOD 7:18:24
CAUSE :SWED EQIP CONGESTION
DIAG: 042

DCH 10 OMSG RELEASE REF 000001A0 CH 99 0 0 31 TOD 7:18:24

DCH 10 IMSG REL COMP REF 000001A0 CH 99 0 0 31 TOD 7:18:24
------------------------------------------------------------

DCH 10 OMSG SETUP REF 000001A0 CH 99 0 0 31 TOD 7:18:50
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:5299 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)
CALLED #:93107973 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)

DCH 10 IMSG CALLPROC REF 000001A0 CH 99 0 0 31 TOD 7:18:50

DCH 10 IMSG DISC REF 000001A0 CH 99 0 0 31 TOD 7:18:50
CAUSE :SWED EQIP CONGESTION
DIAG: 042

DCH 10 OMSG RELEASE REF 000001A0 CH 99 0 0 31 TOD 7:18:50

DCH 10 IMSG REL COMP REF 000001A0 CH 99 0 0 31 TOD 7:18:50
------------------------------------------------------------

>LD 86
ESN000

REQ PRT CUST 0
FEAT ESN

MXLC 1000
MXSD 256
MXIX 5
MXDM 20
MXRL 50
MXFC 30
MXFS 255
MXSC 300
NCDP 4
AC1 8
AC2
DLTN YES
ERWT YES
ERDT 6
TODS 0 00 00 23 59
RTCL DIS
NCOS 0 - 0
NCOS 1 - 0
NCOS 2 - 0
NCOS 3 - 0
NCOS 4 - 0
NCOS 5 - 0
NCOS 6 - 0
NCOS 7 - 0
NCOS 8 - 0
NCOS 9 - 0
NCOS 10 - 0
ETOD
TGAR NO


>LD 90
ESN000

MEM AVAIL: (U/P): 2770217 USED U P: 183492 77330 TOT: 3031039
DISK RECS AVAIL: 1152
REQ PRT
CUST 0
NXX 310
NXX 310
RLI 1
SDRR NONE
ITEI NONE



LD 86
CUST 0 FEAT RLB
RLI 1

RLI 1
ENTR 0
LTER NO
ROUT 30
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
SCNV NO
CNV NO
EXP NO
FRL 1
DMI 1
ISDM 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ENTR 1
LTER NO
ROUT 30
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
SCNV NO
CNV NO
EXP NO
FRL 1
DMI 2
ISDM 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 1
OVLL 0


FEAT RLB
RLI 10

RLI 10
ENTR 0
LTER NO
ROUT 30
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
SCNV NO
CNV NO
EXP NO
FRL 0
DMI 0
ISDM 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ENTR 1
LTER NO
ROUT 30
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
SCNV NO
CNV NO
EXP NO
FRL 0
DMI 0
ISDM 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 0
OVLL 0


>LD 87
FEAT DGT
DMI


DMI 1
DEL 0
ISPN YES
CTYP NCHG

DMI 2
DEL 0
ISPN YES
CTYP NCHG

-------------------------------------------------
-------------------------------------------------

MAIN SITE - with PRA (Opt81-C)

DCH 10 IMSG SETUP REF 00008181 CH 160 0 0 0 TOD 7:17:53
FEAT :NCID
PROGRESS: CALL IS NOT END TO END ISDN
CALLING #:5399 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)
CALLED #:93107973 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)

DCH 10 OMSG REL COMP REF 00008181 CH 160 0 0 0 TOD 7:17:53
CAUSE :SWED EQIP CONGESTION
DIAG: 042
------------------------------------------------------------

DCH 10 IMSG SETUP REF 00008181 CH 160 0 0 0 TOD 7:18:19
FEAT :NCID
PROGRESS: CALL IS NOT END TO END ISDN
CALLING #:5299 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)
CALLED #:93107973 NUM PLAN: PRIVATE/UNKNOWN UNKNOWN)

DCH 10 OMSG REL COMP REF 00008181 CH 160 0 0 0 TOD 7:18:19
CAUSE :SWED EQIP CONGESTION
DIAG: 042


>ld 86
ESN000
FEAT esn
MXLC 5
MXSD 256
MXIX 5
MXDM 5
MXRL 50
MXFC 30
MXSC 300
NCDP 4
AC1 9
AC2
DLTN YES
ERWT YES
ERDT 6
TODS 0 00 00 23 59
RTCL DIS
NCOS 0 - 0
NCOS 1 - 0
NCOS 2 - 0
NCOS 3 - 0
NCOS 4 - 0
NCOS 5 - 0
NCOS 6 - 0
NCOS 7 - 0
NCOS 8 - 0
NCOS 9 - 0
NCOS 10 - 0
NCOS 87 - 0
NCOS 88 - 0
NCOS 89 - 0
NCOS 90 - 0
NCOS 91 - 0
NCOS 92 - 0
NCOS 93 - 0
NCOS 94 - 0
NCOS 95 - 0
NCOS 96 - 0
NCOS 97 - 0
NCOS 98 - 0
NCOS 99 - 0
ETOD
TGAR NO



REQ 90

>ld 90 ESN000
REQ prt
CUST 0 FEAT net TRAN ac1 TYPE nxx
NXX 310
NXX 310
RLI 1
SDRR NONE
ITEI NONE

>ld 86
CUST 0 FEAT rlb
RLI 1
RLI 1
ENTR 0
LTER NO
ROUT 23
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 1
DMI 0
FCI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ YES

ENTR 1
LTER NO
ROUT 12
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 1
DMI 0
FCI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ YES

ISET 2
NALT 5
MFRL 1
OVLL 0


 
I had this type of config working at a location that I don't have access to anymore but I will see what I can come up with.
try playing with the TRMB in RDB



It's only dialtone-VZ
 
Golfdoctor I would get the main site to dial the test number and work backwards

"tried the ACOD at the main site from the main site and it provides dial tone when the same sequence of digits is entered but even from the main site it will not allow the call to be completed. (ie 7222 9 882 9142)"

unless I'm missing something

after dialing your ACOD 7222 you should not dial your AC1 9
at the main location.

create a set with a CLS of UNR MTA
in the RDB I would change TARG to 0

good luck


It's only dialtone-VZ
 
Hi vztech, appreciate the response. Have been spinning my wheels , dlesap has tried to assist also. Hopefully I have not mislead you guys. As a test only I was trying to access the PRA trunk ACOD from my main site which the PRA(I)is connected, just to see if I could seize the trunk via an ACOD. The reason I thought it might help is because I had configured the NRS to recognize the ACOD as a TSC from the remote site. No such luck in either case.I think this might be normal for PRA(I) trunks.(These trunks are on MegaLink) The main site COT (PRA) is set with a TARG of 0 and it does not check for NCOS. Again the main site works fine. I am not quite sure if the fault at present lies with my NRS configuration or if the main site PBX is actually blocking the call. Have gone back and am reading the NTP (IP Peer networking) trying to see if something hits me between the eyes.

The functionality of 4 digit dialling, extension to extension between the sites works great. Still have to test transfer etc but I have CLID, voicemail, MWI etc. coming over the virtual trunks. One of the areas that is also confusing me is that the DCH's between the main and remote site tie trunks seem to be communicating when I enter the DN digit (9) in NRS under Level 0 or Level 1 Regional. When the DN (9) was configured under E164 Nat,E164 INTL,and E164 Local which made sense to me, the Main site did not receive any DCH info from the remote site. I have both types of entries in at present and will check again as I am presently redoing my RLB,AC1, DGT, SPN at the remote site to reflect the proper call type association within the DMI. I reimplemented AC1 as (9) at the remote switch also. Not sure if this will help as I have done so many configuration changes to try and break dial tone, I thought it best to get back to a known entity.

Will try your suggestions and thanks again


TGD
 
Hello

With your 1st config, messages comes at main site. So NRS was fine. With that other config NRS doesn't accept your call anymore. You have to play with the type of call in the NRS (SPN, NXX, blablabla) or also can change the type of call by using a DMI with CTYP SPN or NXX or CDP or....
The message appearing in your DCH must apply call type define in NRS.
Also in NRS you can have the same digit with differents type of calls.
 
Hi dlesap,

We have success! Went back and played with NRS again (reread IP Peer Networking for the 40th time and previous posts- slow learner I guess!)as that is where I went wrong. Basically I had the digit 9 as part of the E164 DN number to be recognized.I also needed to implement INAC at both sites which I had not done as I thought if I sent the digit "9" as a DMI entry things would be good. (wrong) I had also tried INAC before at the main site only but with no success.

Appreciate all your assistance, for if I was on the ball I would have picked up on your first post about AC1 and 2nd about NRS.

Thanks again for everyones assistance, just a super site !


TGD

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top