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!

Trunk to Trunk Issue 1

Status
Not open for further replies.

jamcb80

Technical User
Jun 7, 2006
81
US
I am having an issue with transfers:

I have an ISDN (tru #2) feeding all of our 800 numbers which is connected to an 8500 (cm2.2). One 800 number is routed to an another call center in a different location (8300 LSP). The 8300 has a VDN that the reps use for a local office where there are several requests for transfers. The PRI that is local there (tru #51) is giving me a denial event/COR restrict of 1761 on the attempts. I thought about changing the route pattern for the string in the remote office to stay/dial out over #2. Then I realized that that would be dumb...unnecessary LD charges for a transfer that is 6 blocks away. I have checked the COR on the trunks and the settings in change system-parameters features but alas, still getting the COR errors. Any help here would be greatly appreciated.

Thanks,

Joe
 
Check to see if you have Trunk to Trunk feature turned on...

display system-parameters features

Page 1:
Trunk-to-Trunk Transfer: all

Enabling this feature is considered a toll fraud risk.

Thanks,

Wildcard
 
Thanks for the response Wildcard...and yes, it is set to all.

What if I set the Disconnect Supervision Out to Y on the originating Trunk? Would that make any difference?
 
No, Disconnect Supervision just tells the PBX to monitor the trunks as call are disconnected, so say, if someone calls into voicemail and hangs up, the call doesn't get stuck there recording dead air.
 
It should be a COR issue....as the denial event indicates. I should have gone to this originally... Check the COR of each point the call would touch... station, vdn's trunks etc... In particular look at page 3 of the COR's and make sure the COR has permission to call the other COR... along the whole path of the call. It also could be the FRL, or the calling party restriction on the COR as well.

I don't think it has anything to do with disconnect Supervision... I've been wrong before though...

Thanks,

Wildcard

 
Thanks I got it... Trunk to Trunk Transfer Override set to N in the COS.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top