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

IP Trunking

Status
Not open for further replies.

corrupthalo

IS-IT--Management
Feb 24, 2005
61
US
Hi hope you guys can help with this one...

I have installed IP virtual h323 trunks on my option 61 rls 4. The gatekeeper is in New York however the option 61 is in London. The London switch is registered ok on the gatekeeper.

The NY switch or any switch connected to the gatekeeper can ring me in London. However when I try to return the call, i get destination busy. The routing is setup via nloc and loc codes. When I dial the ac2 and use my hloc, i can ring any extn in the building ok.

When I try to make a IP trunk call I dont see any notification from the dch messaging to see even if the call is going out. I suspect that the call isnt routing correctly to the h323 virtual trunks.

Below I will paste a few of the key elements of the setup for you guys to investigate.

EQ prt
CUST 0
FEAT net
TRAN ac2
TYPE loc

LOC 258

LOC 258
FLEN 7
RLI 35
ITEI NONE
LDN 1000
DID YES
MNXX NO
SAVE 4
RNGE 0001 9999

EQ prt
CUST 0
FEAT rlb
RLI 35


RLI 35
ENTR 0
LTER NO
ROUT 22
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
BNE NO
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 0
OVLL 0

EQ: ltm
CUST 0
ROUT 22
TYPE TLST
TKTP TIE
ROUT 22
DES IP TRUNKING H323
TN 124 0 00 00 MBER 1 H323
TN 124 0 00 01 MBER 2 H323
TN 124 0 00 02 MBER 3 H323
TN 124 0 00 03 MBER 4 H323
TN 124 0 00 04 MBER 5 H323
TN 124 0 00 05 MBER 6 H323
TN 124 0 00 06 MBER 7 H323
TN 124 0 00 07 MBER 8 H323
TN 124 0 00 08 MBER 9 H323
TN 124 0 00 09 MBER 10 H323

ES H323
TN 124 0 00 00 VIRTUAL
TYPE IPTI
CDEN 8D
CUST 0
XTRK VTRK
ZONE 005
LDOP BOP
TIMP 600
BIMP 600
AUTO_BIMP NO
TRK ANLG
NCOS 0
RTMB 22 1
CHID 1
TGAR 0
STRI/STRO IMM IMM
SUPN YES
AST NO
IAPG 0
CLS CTD DIP WTA LPR APN THFD XREP
P10 NTC MID
TKID
AACR NO
DATE 21 MAR 2006

Sorry for such a long post... Hope you guys can help....
 
looks clean, i would build a dsc to test, that will let you know if it's in your routing as opposed to somewhere else.. because the d never sees the call, trouble locates back the that switch... when testing i use dsc's to force a call out, without an ac for a temp workaround test...

john poole
bellsouth business
columbia,sc
 
Print and post route 22 and appropriate dchannel? Also, stat the dchannel in LD 96 and post. What happens when you dial the ACOD of the route? Do you even get dialtone?

Rob
 
Well I dial the acod I do get dialtone but still see no messaging on the d channel. I have tried dsc to force the call out and still no message on the d channel.

I dont think the d channel or route is at fault because the US can call across the link to the site.
 
How would i do that? what do i need to look for?

i thought if the switch is working etc for tie lines already and outgoing lines that ncos/frl/nfcr wouldnt affect it? or am i wrong....known to happen occasionally...lol
 
If you have the same problem after using ACOD and getting dialtone, I don't think it is an NCOS/FRL issue. ACOD bypasses this. Are you sure there is a gatekeeper entry for the digits you are dialing to the other end. You say you are registered fine, but that doesn't mean there are entries for the other end. Assuming there are, post the dchannel from LD 22 and route from LD 21. I would think the route is not associated with the correct dchannel, or you are trying to monitor the wrong dchannel number.

Hope this helps
Rob
 
There is a FRL check in RDB . Even after you get a dialtone it controls dialed digits according to NFCR tree.
 

You may need to check you dial plan in Gatekeeper and make sure that all digits expected are covered and re-transmit to the ITGCard.

 
In your GK, routing plan must exist reagrding directions you want to reach. I guess dialing digits to London exist, but not the one to NY.
Connect in Element Manager, choose Network Routing Service, Log on GK, choose Configuration tab, Gateway entries, and look on the right side of NY site if routing entries exist. If so click on it and check if digits are correct. Make new entry if missing (Standby database, routing entries, Then tools/Cutover and commit) and return to active database to check again.
 
Hi
I don't know if you already solved the problem, if yes, good.
But if the problem still persists, I notice that on the trunk config. the - STRI/STRO - by the book is suppose to be WNK WNK (wink) not IMM IMM (imediat) , I don't know if it makes a lot of doff , but try it if all the rest is correct.

good luck
 
Hi guys thanks for all your suggestions. Still not working. In the process of getting a print out of route 22 and the appropriate dch info.

The problem with checking the GK is that its maintained by an american company, so they are very reluctant to give me access to their GK, understandable.

I just really need confirmation that everything is ok on our end before I pass it back..

Just one question, if their GK was wrong and didnt have the digits in for dialling to NY etc wouldnt I still see the call trying to go out over the dch?

Cheers
 
ADAN DCH 20
CTYP DCIP
DES IPTrunking
USR ISLD
ISLM 4000
SSRC 1800
OTBF 32
NASA NO
IFC SL1
CNEG 1
RLS ID 25
RCAP
MBGA NO
H323
OVLR NO
OVLS NO

 
>ld 96DCH000
.stat dch
DCH 016 : OPER RLS AUTO DES : HAWLEYCRESCENT
DCH 018 : OPER EST ACTV AUTO DES : HAWLEYCRES2_3
DCH 020 : OPER EST ACTV AUTO DES : IPTrunking
.
 
TYPE RDB
CUST 00
ROUT 22
DES IP TRUNKING H323
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
IDEF NET
RCLS EXT
VTRK YES
ZONE 005
PCID H323
CRID NO
NODE 1
DTRK NO
ISDN YES
MODE ISLD
DCH 20
IFC SL1
PNI 00001
NCNA YES
NCRD NO
FALT NO
CTYP LOC
INAC YES
ISAR NO
DAPC NO
PTYP ATT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7122
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
SIGO STD
STYP SDAT
MFC NO
ICIS YES
OGIS YES
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896


PAGE 002

GTI 896
SFB 3
NBS 2048
NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
EESD 1024
SST 5 0
DTD NO
SCDT NO
2 DT NO
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS NO
PANS YES
RACD NO
MANO NO
FRL 0 0
FRL 1 1
FRL 2 2
FRL 3 3
FRL 4 4
FRL 5 5
FRL 6 6
FRL 7 7
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 7122 22
ATRR NO
TRRL NO
SGRP 0
AACR NO

Here you go guys.....lets hope we can get it sorted...
 
I guess so.
Once I had the same problem, and I dialed the ACOD of the VTRK route and I could see the DCH MSG's, you can even activate the enhanced trace of your phone to check if you're "picking" a VTRK.
 
sounds like the NRS on the gatekeeper to me. I would check the end point as dlesap suggested.

It's only dialtone-VZ
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top