Calls to a phantom diverted externally being rejected from switchboard

[plunet]

Hope someone here can point me in the right direction.

We have a couple of Nortel Meridian PBXs.
Our console (switchboard, M2250s) are attached to an Option 61.
There is also an Option 11. The two switches are interconnected via a DPNSS trunk.
There is another switch in the network (non-Nortel) but it's not involved in any of this.

The console cannot put calls through to Phantom DNs hosted on the Option 11.
The Phantom DN is diverting to an external number (FTR CFW 12 and FTR DCFW 12 9xxxxxxxxx) and the calls would be presented out of a trunk that is directly connected to the Option 11.

Any other extension in the network (either Option 61 and Option 11) irrespective of NCOS can call the Phantom DN without an issue. And DDI calls that are presented into either Option 61 and Option 11 switch via an external trunk can call the Phantom DN. Just calls that have gone via the switchboard are affected.

The Phantom DN is set up with no TGAR (set to 0) and has an unrestricted NCOS (set to 0) and CLS CFXA.
The trunks on the Option 11 (both the inbound DPNSS trunk and outbound PSTN trunk) have no TARG and allows TRMB.
For calls being denied, the switchboard will be presenting the call across the DPNSS trunk from the Option 61 to the Option 11, and then the Option 11 will try to divert the call externally out of one of its local ISDN trunks (not back down the DPNSS trunk). It doesn't matter how the call got to switchboard, internal, external etc.

We've long since had ACD's being used to divert calls around but have recently started to use Phantoms to assist with a transition off to a hosted PBX system. The divert works if we use an ACD NCFW (including for the console) but we need more capacity than we will have just using ACDs so was hoping to use Phantoms.

What have I forgotten to review in all of this that is preventing the console placing calls to a Phantom that is diverted externally?

Thanks

 

[Tacosoup]

Usually an NCOS of 0 is going to only be internal extension to extension calls.
Just a suggestion, but you may want to change to a higher NCOS, try cross referencing a phone that can dial the number.

** Proofread carefully to see if you any words out.

 

[plunet]

The NCOS on the phantom doesn't appear to be the problem. I've tried changing this from 0 to 4 and it doesn't appear to make any difference.

It's just the attendant console that appears to be affected.

Does anyone else have any ideas, or some steps I can go through to troubleshoot?

 

[plunet]

Hvaing just tried something else, I've realsied that BARS is causing the problem, but I don't understand why.

The Phantom was programmed to use 9 plus the external number, ie.
FTR DCFW 12 902012345678

I've changed this to use the ACOD of the primary trunk, and it now works
FTR DCFW 15 169902012345678

But why is BARS mucking around on a call extended from the console on an adjacent switch connected via DPNSS whereas other calls (including DDI calls) are not affected. What is different to this call as opposed to any other call?

Also, why would an ACD that diverts to 902012345678 work whereas a phantom that diverts to 902012345678 doesn't?

I would prefer to use AC1 code of 9 as this gives me resilient routing, what steps would I need to take to fix this?
I guess I possibly need to add the range of numbers I'm diverting to in one of the FRLs, but which one?

Thanks

 

[trvlr1]

Try transferring the Phantom to a dummy extension back on the 61. On the 61 build a phantom that sends it out with "9". Does that work?
Second question: If this is only a Dummy, why send it to the 11, why not just send it out from the 61 directly and not worry about using 2 channels between the 61 and the 11?

 

[plunet]

Thanks trvlr1

I could bounce the call from a Phantom on the Option 11 back to a Phantom on the 61 to then be placed as an outbound call. However I will probably run out of Phantoms and it will get quite messy quickly.

And I could, as you say, create a Phantom - or use some IDGT translation on the 61 and never let the call get to the 11 in the first place. But as I'm using a CDP (co-ordinated dial plan) between the switches this will be awkward to do for individual numbers until all extensions in a block of numbers have been migrated. I need something to allow individual numbers to transition without breaking everything.

I've got a workaround of using the ACOD to route the calls now, I was just hoping for something that was a bit more resilient.

 

[Wooliepride]

What is happening when the console tries to access the phantom?
What is the NCOS on the console?