Not able to access trunks of the route every time using TSC

[nortelhawk]

Hi,

i have a peculiar problem in hand. i have configured a pri E1 link (opt 11C) to CISCO call manager .

Now my PRI is configured as NET with ESGF interface. I have configured TSC concept as follows

ld 87
tsc 43
flen 0
itoh no
ccba no
rli 30

ld 86
rli 30
enter 0
rout 18 ----------> this is route no i gave to my PRI
dmi 89

ld 86
dmi 89
del 2
inst 8 ----------------->it goes to cisco call manager for
ctyp nchg call routing

so now using tsc+extn i.e suppose 43296 calls shud go but problem is on dialling 43296 many many times it is going through once or twice .
whereas another PRI with route no 17 and TSC 70 which was configured previously is working fine with the same cisco device with same protocols, on dialing 70296(TSC+extn) every time my call gets completed.

Please help me in identifying wot can be wrong or missing.......

Thanx in advance

 

[johnpoole]

if it works once, the tsc's and rlb are doing their job.. are the trunks remaining "hung" after the call? i've seen that cause a fail condition due to all trunks busy while waiting for a timer to do a release.. i would do some entc commands and mon the trunks in the cisco cm to see what the trouble is.. more then likey i would start with timers on both ends..

john poole
bellsouth business
columbia,sc

 

[nortelhawk]

hi johnpoole,
thanx for the tips .....thats better way to monitor things and i did that but still didnt had any luck. then i outed whole dch pri config and did it again from scratch and then tested and everything were up and running smooth like anything ........nortel is no doubt very superior product but sometimes its problems r amazing !!!!

thanx again

 

[johnpoole]

yes and it's hard to think that the build will work one and then fail.. then get well and work again.. i'vs seen stranger.. the enl msgi/o commmands in 96 are very dependable...

john poole
bellsouth business
columbia,sc