MobileConnect CLID Wrong when call is through Unity Handler

justincohen · ‎11-17-2008

MobileConnect is fully working for this customer..

We are having a problem with Caller ID not showing up correctly on the users cell phone..

What works....

- Call from ext to ext, shows the calling ext on the cell

- call from dedicated DID to extension shows proper outside calling information extended to cell

What doesn't work...

-- Call into main number, answered by Unity Connection call handler, caller dials users extension - when call is extended to cell, they see the DN of the voicemail port...

This is similiar to the issues seen when connecting a M1/Nortel system with a CUCM.

It looks like Unity Connection is not releasing control of the call to CUCM, the funny thing is -- the users see proper CLID on their phone from a Handler initiated transfer -- but the cell phone doesn't...

System Specs: CUCM-BE 6.1.2, Unity Connection, 2811 Gateway with MGCP PRI to a DMS-100

Thanks!

carenas123 · ‎11-24-2008

Extension patterns provide direct inward dialing (DID) information. If a call is placed from an internal extension to an extension configured for Mobile Connect, and then a remote destination picks up the call, the default treatment is for the caller ID to show only the internal extension. Using extension patterns, you can instruct the system to display the fully qualified PSTN number.

loganseth · ‎12-17-2008

I have this exact same issue, but our integrator (INX), pointed us in the right direction.

Change the 'DISPLAY ORIGINAL CALLING NUMBER ON TRANSFER FROM CISCO UNITY' in the Service Paramters to 'TRUE' - it is set to false by default.

Worked like a charm. We have Cisco Unity 4.0(5), but I would assume it'll work for Unity Connection.

We also run 6.1(2) on an MGCP controlled 2811.

NOW, the last thing we haven't got is the OPERATOR TRANSFER (well, any transfer) to show the orignal calling party...it shows the caller-id of the phone that transferred...

Thoughts?