Option 11C - DSC Issue

[ba7389]

As part of my continuing saga to merge two Option 11C locations into one, will be asking LEC to port numbers currently pointed at a PRI in one switch over to a PRI in the other. In the final state, all will be moved to the destination location, and there should be no issue. While both switches are in operation, however, there will be 4XXX extensions working in both.

To begin to test, I have created a DSC of 4703 that is pointed to an RLI that uses a tie route that connects the two switches. Have also created an extension pickup of 4703 on a phone in the destination switch, and have asked the carrier to port the number. Issue, which seems minor, is that calls to DSC 4703 in the local switch receive intercept treatment rather than routing through the tie route to the destination switch. Have a feeling that there is an RDR_Data OPT setting or similar that I need, but don't know what that is. Ideas?

Thanks,

Bruce

 

[ba7389]

After reading over what I posted, think issue may not be clear. Purpose of doing this interim DSC thing is to allow 4-digit CDP to function with 4XXX extensions residing in 2 switches.

 

[trvlr1]

Is this a new tie line between the PBX or is it an existing line that was in use prior to this. If older line, what else works on it and is there a DSC on the other end that is pointing your call straight back to yourself?
You may also want to make a test call and then trace in LD 80 to see if it is getting to the right route/circuit, if it is a PRI, you can also turn on D channel messaging for that circuit and see if you see the call hitting it.
To make sure the circuit works you could also dial the ACOD of the tie circuit from your phone, then the extension and see if that works.

 

[ba7389]

On your first two thoughts - it is an existing route and there is not a DSC on the destination end pointing back to the originating switch.

I have traced call, and it lands at the receptionist on the originating switch.

Good thought on the ACOD - feel certain that will work, but if it doesn't, I can go think about something else.

Thanks,

Bruce

 

[ba7389]

Sorry for inaccurate start to this. Wrong information was provided previously - I made an assumption that was not correct, and trvlr1 pointed me to check that. When I turned on D channel monitor, saw calls moving across tie route.

Calls ARE routing correctly, but problem is this - If the destination user picks up the call, all is well. If he doesn't, however, call is CFNAd to a Dialogic Media Gateway that is IP-connected to an Exchange Server running the Unified Messaging role. The station information needed by the Unified Messaging Server to route the call to the appropriate mailbox greeting is not provided by the PBX to the Media Gateway Server. Thoughts?

 

[johnpoole]

most of the time that is caused when the nortel sends the media server the original dialed dn as opposed to the ext dn of the non answering set. you can not change that in the nortel.. you can adjust the media server or build a work around.

john poole
bellsouth business
columbia,sc

 

[ba7389]

That's what I've found John.

I've found ways to make everything work, but it's a little more cobbed up than hoped. It still seems like a better alternative than investing heavily in Nortel upgrades, particularly given the uncertain future of the combined companies (Avaya/Nortel).

Thanks to all for help.

-Bruce