Nortel - Cisco integration - UNITY & sets with DDGD

[Barbarian7]

Hi.
we have a largely successful Nortel (81C) integration with Cisco Call Manager.
We recently moved everyone on the Nortel side over to UNITY for voice msg'g. Most things worked just fine with a little tweaking.

Our UNITY pilot number (on the Nortel side) is an ACD with MWC=Yes and NCFW=another DN which in turn is CDP'd across to a Cisco gateway.

But we have stumbled onto one we cannot fix:
a number of Nortel sets are CLS DDGD to get privacy of their DNs.
But now when someone calls one of these locals, and the call CFNA/HUNTs to the UNITY pilot number, the originally called DN is lost and UNITY does not know which mailbox this is for.

This is not surprising, since DDGD is used so these people can block their phone# from showing on other sets's call display, and now they are just hiding from the "set" that is the ACD over to UNITY.

The old Meridian Mail did not have a problem with this.

Any idea what special thing Mermail did to get around this?

Thanks,
Barbarian

 

[911guru]

You bet, and again a classic example of Cisco just not getting the whole picture and doing it the right way.

Meridian Mail looked at the originally dialled DN or ORIG_DN as it's called. Regardless of where the call came from, or how, the ORIG_DN was used for mailbox resolution.

I call DN XXXX originally, if I go to Mail, then that's the mailbox I should get, was the way of thinking there.

It appears that Unity is looking at the CFW_DN and resolving the mailbox on that number. If you look into the Q.Sig message, you will see the ORIG_DN number there, even though you have DDGD on the sets.

Hope this helps!

911Guru

http://pbx-e911.com

 

[Barbarian7]

911guru :
Bingo.

Debugs on the Cisco PRI gateway CLEARLY show "Original Called Number" and "Redirecting Number" with the correct info in them (ie: the DN of the DDGD'd set)...
yet when you look in Call Viewer on UNITY, those fields are blissfully-blank. Nice.


Thanks - now we know which "throat to choke"

Cheers,
B

 

[x11tech]

Nice to know that Cisco is still acting the 500 lb gorilla.

 

[911guru]

Yeah, with the same level of intelligence to boot. To Cisco, a standard is only a standard if they happen to support it. If the don't the rest of the world is wrong in their eyes. I think that is what ticks me off the most about them. Plain and simple arrogance. No place for it in my world.

911Guru

http://pbx-e911.com

 

[Barbarian7]

Yes: Cisco bad (and we have the sniffer traces to prove it).

So here's another wrinkle on this same issue.
When someone calls a DN that's MARPed on a set that is DDGA, but that DN is SCN'd on another set that is DDGD, the CFNA'd call over to UNITY has no called/forwarding number info (same as calling a DN that is MARPed on a DDGD'd set).

So. Question: can anybody think of a way to get those DNs onto the DDGD'd sets as line appearances without calls "inheriting" the DDGD ?

(I know: we *are* beating up Cisco, but in the mean time, we are short on work-arounds).

Thanks,
B

 

[StanleySteamer]

On a Nortel incoming route there is a PII option for Privacy Indicator Ignore.
Maybe there is a corresponding option on the Cisco incoming route?
Don't know if that would help or not.

 

[Barbarian7]

Hmmm.
An interesting line of thought, StanleySteamer.

I set PII = YES on my RDB entry - didn't improve things (but you did say this was for "incoming", ya?).

I also looked (high & low) for *anything* resembling that in the Cisco world... with no luck. It's going to be something goofy like that though.

Thanks
B