CID/ANI Passthrough with UCXN Call Handler Transfers? 1

[MitelInMyBlood]

CUCM 8.5(1)
UCXN 8.0.2

I have a CTI RP ahead of a call handler in UCXN to perform standard and closed call transfers to both internal & external DNs. No caller input, just simple blind call transfers to two different numbers depending on a schedule. Is it possible to pass the original CNID info with the transferred call? Presently the destination sees only the VM pilot number. (The client is asking because we were able to do this with our previous voice mail system)

Thanks in advance


Original MUG/NAMU Charter Member

 

[whykap]

this is what you are looking for

http://www.tek-tips.com/viewthread.cfm?qid=1659635&page=1

 

[MitelInMyBlood]

Thanks - I had forgotten all about that thread and it was even recent. See what happens when you get old? This will happen to you someday too


Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

OKAY - - now that this is working so exceedingly well, it seems that one of my users is disgruntled and would prefer to see the callerID of the trasnfering party (UCXN's DN in other words rather than the original caller) This is coming through a multi-branch call handler in a drill-down auto att. application.

As this was a system option setting I didn't think we had the luxury of altering the ANI/DNIS digits on a case-by-case basis, but thought I'd better ask because this guy may try to pursue it and I don't want him finding out something else if we tell him it can't be done.

Thanks

Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

(addt'l)

Would it be possible to use dummy numbers and send those back to CUCM to a TP and monkey with the Transformations?

Any tips on how to do it would be appreciated (use calling or called party - which? I get confused here)

What about connected party ? Can I send out another mask? IE, could I spoof the outbound CID to be the 10-digit incoming toll-free number?

Thanks

Original MUG/NAMU Charter Member

 

[whykap]

You could do it with what you said I suppose. Never done it. It will also take some messing with partitions and css as well.I would have to dupicate what you are doing in our lab and mess with it.
Do you work for a government entity by any chance?

 

[MitelInMyBlood]

No gov't entity, but just as well be as we're under massive regulation from FERC. Curious why ask?

I was able to successfully do what I described using a T.P. - played with it for an hour or so. It's actually quite easy to do but as I discovered, does not change the CPN when calling through the AA from on on-net extension (or MGCP trunk). Non-issue anyway but tripped me up at first. By contrast, ext'nl calls entering CUCM through H323 PRIs and then driling down through the AA and then the AA handing off to a dummy (non-DID) number for which you've built a T.P. will use the calling pty transformation mask (must check the box) then enter your own 10-digit mask w/no prefix digits and all other Calling pty transformation settings at their default values. The intended destination digits of course get entered into the Called party transformation.

Only thing left to do is verify that the call doesn't tie up a UCXN port (or two) - it shouldn't, but once burned twice wise.

There's likely other (perhaps cleaner) ways to do it in the CUCM with part'ns and CCS (to avoid having to build a separate T.P for each destination) - this was just an exercise to prove to myself it could be done. It also taught me that transformation patterns (apparently) only apply to H323 calls, not internal (nor MGCP/Q.sig).


Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

OKAY I found an even better/simpler way to insert a specific CallerID into a call handler AA... - also better/simpler (IMO) than adding partitions & CCS.

Instead of building a bunch of translation patterns (one for each AA destination) I found you can accomplish the same thing by making only one T.P. and do it on the input side of the call handler rather than the output side.

For example, we today have Unity & CUCM set up to pass the original calling party CID through to the AA destination. Most users want that, but not all do. If we want to change this on-the-fly just for specific call handler AA's without impacting them all, we can do it by simply building only one translation pattern (with a transformation pattern as previously described) then setting the called party transformation mask to the pilot number of the Call Handler. In this way every AA option of this C.H. sees the spoofed number instead of the original caller.




Original MUG/NAMU Charter Member