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!

CS1000E Rls5.5 PRI connection to 3COM NBX -Ring back timer

Status
Not open for further replies.

iso30

Technical User
Dec 28, 2008
30
LB
Hi

I have a pri connection from CS1000E Rls5.5 to 3COM NBX,
when we dial the 3com extension we have a 10seconds delay before we hear ring back tone at cs1000e extension;
however if we dial from 3com to cs1000e extension we don't have this issue.

any ideas??
 
Hi

I did this test already when using trunk route access code of the Nortel PRI the delay is around 10sec, however if i use CDP-DSC for same call delay is around 5 seconds.Still a big value to wait for :)

Thanks
 
You could try making the FLEN of the CDP number match the number of digits in LD 87 so that it isn't waiting for additional digits.

REQ: CHG
CUST: 0
FEAT: CDP
TYPE: DSC
DSC: xxxx
FLEN: 3 or 4 or however many digits are in the extension being dialed

 
Hi

It is the same number of digits 4.

Could it be any timer changes on dchannel programming or route programming??

>ld 21
PT1000

REQ: prt
TYPE: rdb
CUST 0
ROUT 20

TYPE RDB
CUST 00
ROUT 20
DES PRI3COM
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC ESIG
SBN NO
PNI 00000
NCNA YES
NCRD NO
CTYP UKWN
INAC NO
ISAR NO
CPFXS YES
DAPC NO
INTC NO
MBXR NO
DSEL VOD
PTYP DTT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH RRB
TRMB YES
STEP
ACOD 9989
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
SIGO STD
MFC NO
ICIS YES
OGIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
NBS 2048
NBL 4096



PAGE 002

IENB 5
TFD 0
VSS 0
VGD 6
DTD NO
SCDT NO
2 DT NO
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS YES
MRT 19
PANS YES
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
PLEV 2
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 87 20
SGRP 0
ARDN NO
AACR NO

REQ: end
>ld 22
PT2000

REQ prt
TYPE adan dch 9

ADAN DCH 9
CTYP MSDL
MG_CARD 008 1 04
PORT 1
DES 3COMPRI
USR PRI
DCHL 128
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ESIG
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE NET
CNEG 1
RLS ID **
QCHID YES
RCAP MWI COLP
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7

Thanks
 
hi

yes FLEN is already 4 in the LD87 Steering code entries;

i also tried to change rgv, eod and odt to 256 but same result,

Could it be some settings on the 3 com side???

overlap/ enbloc signaling???

Thanks
 
Is the 3COM is waiting for more digits? If the 3COM has it's own DID, and calls are not delayed, one could compare the settings on that trunk group to that of the group connecting to the Nortel switch.

Also - check the Nortel trunk TNs - make sure they say CLS DTN and not DIP?


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
 
Hi

on the nortel side it is dtn;

i will check with 3com technicien on the settings in his side.

Thanks
 
itoh is set to no, do u suggest change it to yes??
 
Good Morning iso30, Did you guys use published documentation from 3COM to make the DCH ESIG protocol or was that trial and error? A more drastic change, but works between a Nortel and Avaya and also Nortel and Cisco is DCH protocol ISGF. Under RCAP program COLP NDI CCBI CCNI PRI DV3I QMWI. Of course, you would have to tear everything down and rebuild. If you do this, remember to change the IFC to ISGF in the route as well.
 
is there still a delay when you terminate the dialled number with a #, also do you see the call hitting the DCH straight away or is there a delay?

Remember if it doesn't work hit it harder

Scott UK
 
sorry forgot to add, if the call hits the DCH straight away its not the CS1k

Remember if it doesn't work hit it harder

Scott UK
 
Hi telebub

There are no published documentation from 3COM or nortel for interoperability. We made the DCH ESIG protocol by trial and error :) and it worked however we have this ringback delay issue when calling from nortel to 3com.
We will try your suggestion.
Thanks
 
Hi

We changed some settings on 3COM side and now we have the following:

if we dial acod + 3com extension we have a delay ringback tone of 4 sec.
however if we dial acod + 3com extension + # we get direct ringback tone.
(Also using cdp gives direct ringback tone).
however customer wants to use acod + ext cause he has same range of ext at nortel and 3com side.

Regards
 
Hi

We changed some settings on 3COM side and now we have the following:

if we dial acod + 3com extension we have a delay ringback tone of 4 sec.
however if we dial acod + 3com extension + # we get direct ringback tone.
(Also using cdp gives direct ringback tone).
however customer wants to use acod + ext cause he has same range of ext at nortel and 3com side.
How can we overcome this # issue???
Regards
 
Here is how we do it:

Don't use the route ACOD but find an available number to use in its place, for example 75. Or change your route ACOD and use the number of preference in the example below.

1) Create a DMI table in LD 86:
REQ: NEW
CUST: 0
TYPE: DGT
DMI: (pick an available DMI table)
DEL: 2
INST: (just hit return)
CTYP: NCHG

2) Change your existing RLI to use the DMI table you created

3) Create a CDP distant steering code in LD 87 of "75" (whatever your access code is) with FLEN 6.

You would dial 75xxxx which will strip the 75 and dial the 4 digit extension across to the 3com.







War Eagle!!
 
I'm sure you are aware but in case, if you are using a 3 digit access code, you will DEL 3 in the DMI and your FLEN will be 7.

War Eagle!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top