Vacant Number to TIE Trunk CS1000M

[ddickenson]

I've done some searching for this and I'm beginning to get discouraged.

I've tied my Nortel and Asterisk system together with QSIG tie trunks and I'm looking for a way to do what I can already do in Asterisk to get to extensions on Nortel, that is when you dial 4 digits it searches through the local database and if it's a "vacant number" it sends the call out the tie trunk to check the other system.

I've thought of some work arounds like making a phantom DN that is forwarded to an NXX that uses that TIE trunk and then stripping the NXX on the Asterisk side but that's messy and I have to add EVERY number that's on the Asterisk side to the Nortel in that fashion.

It seems logical that you could use vacant number routing in a way to do this like you do for sending it to RAN. What's the feature name I'm looking for?

 

[ddickenson]

Ahh, also I'm on Rls. 4.50.

 

[KCFLHRC]

Why not just create a CDP entry ?

 

[ddickenson]

Doesn't that require that you dial a code prior to the extension?

Basically what I'm trying to do is transition a good number of my 2616's over to SIP endpoints on the Asterisk side. So they will be the same extension range, ie. 4xxx or whatever. Its very possible that I don't understand CDP enough but it sounds like you would need to either dial an extra digit to tell the system where the extension was or have all the extensions on the other system be in a different range like day 6xxx in order to dial only 4 digits. Is that correct or can I actually have 4xxx extensions on both systems and have CDP send the ones not on Nortel over the TIE?

 

[Splic3d]

You don't need an extra digit to send the calls through CDP. CDP uses the rli entries to send the call to the route you need to go to. You can do that individually (dn's) if needed. The is a limit setting for the number of cdp entries you need as well in the CDP setup.

http://www.i3techgroup.com

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[KCFLHRC]

CDP is coordinated dialing, you put the 4 digits in a CDP entry and then point it to the correct RLI, that's it. Then you dial those 4 digits and it goes.

 

[ddickenson]

Ohhhh, I see so every extension that I move to Asterisk I could put a CDP entry in there and point it to RLI 1 or something that sends calls out that trunk. Beautiful. Thanks a lot.

 

[KCFLHRC]

You got it. You can also do a range of numbers. For example if you want to do Extension
3000 to 3009 you can just put in 300 and that will cover all 10 numbers. Or if you want to do 3000 to 3099 you can put in the entry 30.

 

[ddickenson]

All that worked beautifully and I've had one department up on the system for a week or so now and they are able to make calls over the tie and all is well, or so I thought.

I've come across an issue now that my thru-dial on callpilot (that's handling our auto attendant) is not working for those numbers that have been set up as DSC in the system. I can dial them from a Nortel phone and thru-dial works for numbers not set up as DSC but when I call one of the numbers I've transitioned over to the new system I get a pause, then a beep, then "number not in system" or something similar.

From what I've been reading it is possibly an issue with my RPL in callpilot. It's using a list called On Switch, I say that because I'm not sure if it's a default list or not. The restrict has : 1, 9 and the Allow has: 2,3,4,5,6,7,8. All the numbers in question are 3xxx or 4xxx numbers. Any ideas?

side note: other 3xxx and 4xxx numbers that are not DSC work fine.

 

[trvlr1]

It could be that trunk to trunk transfer is not working as you want it to, when you call in to a DID it comes in on one trunk, then transferring it to the other system tries to send it on another trunk, but the system may not be set up to allow it. Check out NEDC and FEDC values on the trunks to start with, also TARG values.

 

[KCFLHRC]

I would also check out your trunk to trunk connections programming in the CDB under FTOP, by default this is restricted.

FTOP Flexible Trunk to Trunk Options. basic-23
(FRES) Flexible Trunk to Trunk Connections
Restricted. FTT feature is inactive.
TBFT Trunk Barring Flexible Trunk to Trunk
Connections. FTT adds new restrictions on
connections not barred by TBAR
FTTB Flexible Trunk to Trunk connections Trunk
Barring. FTT lifts TBAR restrictions for routes
barred by TBAR. FTT cannot add any new
restrictions for non-barred routes.
FTLY Flexible Trunk to Trunk Connections Only. All
set based trunk to trunk connections for
Transfer and Conference are controlled by
FTT only

 

[ddickenson]

It turns out that I had forgotten to setup the TGAR and NCOS values on the voicemail ports and that was causing it to be restricted from dialing out to the route I needed to hit. The sets had proper TGAR so they could dial the TIE trunk without issue. Thanks guys