12-11-2002 02:41 PM - edited 03-12-2019 09:55 PM
Does anyone know if CM even sends the original calling party number when it forwards a call? I have Unity accepting calls as an auto-attendant. I have some users on a legacy phone system connected via PRI. If a call comes in that should go to the legacy system the call is routed by CM. The caller id on the legacy phone system shows the port number of Unity. I was told that there may be some setting on the legacy system that I could set to show the original calling party number but does CM even send those over in the first place?
12-18-2002 09:08 AM
Did you ever get an answer on this?
12-19-2002 09:27 PM
Not until now. Could you elaborate on the gateway config please?
12-18-2002 12:27 PM
on the gateway config on the prisection there is a required parameter that allows you to set the calling party. it usually defaults to originator but it can be changed to be the redirecting party's number.
hope this helps
scott
12-20-2002 09:51 AM
Call manager can send the originating partys CLI on a forwarded call but I'm not sure it can for a transfered call. Set the Calling party selection to be the originator.
Like I said Not sure about for transfered calls which is what you have when Unity is redirecting them. I doubt you can do this though as the new call leg is set up by a unity port and so the Unity port CLI will be sent to the PBX as the calling party, even though Unity then completes the transfer and hangs up. Because Call manager then can't signal to the PBX the connected party CLI (the caller) it can't change the CLI being sent. This may change in 3.3 with Q.sig but I wouldn't hold your breath.
paul
12-23-2002 09:20 PM
Yeah, the Calling Party Selection field on the gateway config page only applies for calls that are forwarded without being answered. That feature does not apply to calls that are answered and then transferred. As far as I know there is no way to do what you're asking, at least not until CallManager supports sending the Connected Number IE for PRI gateways.
12-31-2002 12:16 PM
You may have gotten a work around in place but in case, we had the same issue. Using Unity as an AA killed all caller ID. We worked on this forever and finally got confirmation from TAC that it was functioning as designed... joy. To solve the issue, we put in place a CRS server and setup the AA as a CRS script. CM is now responsible for routing calls to either legacy system via PRI or IP systems via network. All is happy with caller ID. The only caveat we found was CRS did not function properly with ActiveDirectory on dial-by-name so we pass it to Unity therefore anyone calling through dial-by-name will not send caller ID but that is a minimal amount.
12-31-2002 12:38 PM
Thanks for the follow up! I am going to look into this more. Sounds lke the answer.
ps, my daughter just got a build-a-bear monkey from Nana the other day. Monkey pinkey is her name!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide